JP2019097191A - Base station and method - Google Patents

Abstract

To provide a base station communicating in a communication system when reconstructing from a source uplink/downlink structure to a target uplink/downlink structure, and a method.SOLUTION: A base station includes: a transmission part transmitting a DCI transmission restructuring a communication on a prescribed sub-frame N in a top of a radio frame to a mobile station; and a reception part receiving a PUSCH transmission. In response to the DCI transmission, a source uplink/downlink structure is applied to the PUSCH transmission containing a sub-frame N-6 in regard to the DCI transmission received from the mobile station until the sub-frame N-6. The uplink/downlink structure previously defined is applied to the PUSCH transmission in regard to the DCI transmission received from the mobile station to between sub-frames N-5 to N-1. A target uplink/downlink structure is applied to the PUSCH transmission in regard to the DCI transmission received by the mobile station after the sub-frame N.SELECTED DRAWING: Figure 11

Description

  The present invention relates to a base station and method.

Long Term Evolution (LTE)

  Third generation mobile communication systems (3G), based on WCDMA® radio access technology, are being deployed on a wide scale in the world. High-speed downlink packet access (HSDPA) and enhanced uplink (also referred to as high-speed uplink packet access (HSUPA)) are introduced as the first steps in enhancing or evolving / evolving this technology, An extremely competitive wireless access technology is provided.

  In order to meet the ever-increasing demand from users and to ensure competitiveness against new radio access technologies, 3GPP introduced a new mobile communication system called Long Term Evolution (LTE). LTE is designed to provide the carriers required for high speed transmission of data and media and high capacity voice support for the next 10 years. The ability to provide high bit rates is an important measure in LTE.

  The specifications of work items (WI) for LTE (Long Term Evolution) are E-UTRA (Evolved UMTS Terrestrial Radio Access (UTRA): Evolved UMTS Terrestrial Radio Access) and E-UTRAN (Evolved UMTS Terrestrial Radio Access Network (UTRAN) It is called the evolved UMTS Terrestrial Radio Access Network) and is finally released as Release 8 (LTE Release 8). The LTE system is a packet-based efficient radio access and radio access network, providing full IP-based functionality with low latency and low cost. In LTE, scalable transmission bandwidths (eg, 1.4 MHz, 3.0 MHz, 5.0 MHz, 10.0 MHz, 15.0 MHz, etc.) to achieve flexible system deployment using a given spectrum And 20.0 MHz) are specified. For downlink, radio access based on OFDM (Orthogonal Frequency Division Multiplexing) is adopted. Because such wireless access is inherently less susceptible to multipath interference (MPI) due to the low symbol rate, it also uses cyclic prefix (CP), and accommodates various transmission bandwidth configurations. It is because it is possible. For uplink, radio access based on SC-FDMA (Single-Carrier Frequency Division Multiple Access) is adopted. This is because, given the limited transmission power of the user equipment (UE), it is prioritized to provide a wider coverage area than to improve the peak data rate. In LTE Release 8/9, a number of key packet radio access technologies (eg, MIMO (Multi-Input Multi-Output) channel transmission technology) are employed to achieve a high efficiency 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. The E-UTRAN is configured of an eNodeB, and the eNodeB terminates a protocol of a user plane (PDCP / RLC / MAC / PHY) and a control plane (RRC) of E-UTRA for the UE. The eNodeB (eNB) is a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, and a packet data control protocol (PDCP) layer (these layers are user plane header compression and encryption Host functions). The eNB also provides a radio resource control (RRC) function corresponding to the control plane. eNB performs radio resource management, admission control, scheduling, uplink QoS (Quality of Service) by negotiation, broadcast of cell information, encryption / decryption of user plane data and control plane data, downlink / uplink It performs many functions, such as user plane packet header compression / decompression. The plurality of eNodeBs are connected to each other by the X2 interface.

  In addition, a plurality of eNodeBs are EPC (Evolved Packet Core: evolved packet core) by S1 interface, more specifically, MME (Mobility Management Entity: mobility management entity) by S1-MME, serving gateway by S1-U SGW: Connected to Serving Gateway). The S1 interface supports a many-to-many relationship between MME / serving gateway and eNodeB. The SGW, while routing and forwarding user data packets, acts as a mobility anchor for the user plane at handover between eNodeBs, and further, 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 for that user equipment arrives. The SGW manages and stores the user equipment context (e.g. IP bearer service parameters, network internal routing information). Furthermore, the SGW performs replication of user traffic in case of lawful interception.

  MME is a main control node of 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 further selects the SGW of the user equipment at the time of initial attach and at the time of intra-LTE handover with relocation of core network (CN) node It 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 the roaming restrictions of the user equipment. 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. Furthermore, the MME provides a control plane function for mobility between LTE access network and 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 carriers in 3GPP LTE (release 8 and later) are 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 a 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 OFDM symbol covering the entire bandwidth of the component carrier . Thus, each OFDM symbol, as also shown in FIG. 4, consists of a plurality of modulation symbols transmitted on N ^DL _RB × N ^RB _sc respective subcarriers.

For example, considering a multi-carrier communication system using, for example, OFDM, used in 3GPP LTE (long term evolution), the smallest unit of resources that can be allocated by the scheduler is one "resource block". A physical resource block (PRB), as exemplarily shown in FIG. 4, includes N ^DL _symb consecutive OFDM symbols (eg, 7 OFDM symbols) in the time domain and N ^RB _sc in the frequency domain. It is defined as consecutive subcarriers (e.g. 12 subcarriers of component carrier). Therefore, in 3GPP LTE (Release 8), the physical resource block consists of N ^DL _symb × N ^RB _sc resource elements, corresponding to one slot in the time domain and 180 kHz in the frequency domain (related to the downlink resource grid) For further details, see, for example, section 6.2 of Non-Patent Document 1 (available at the 3GPP web site, and incorporated herein by reference).

One subframe consists of two slots, so there are 14 OFDM symbols in the subframe when so called "normal" CP (cyclic prefix) is used, so-called "extended" CP is used There are 12 OFDM symbols in a subframe when it is active. As a terminology, in the following, a time-frequency resource equal to the same N ^RB _sc consecutive subcarriers across subframes, a "resource block pair", or in the same sense an "RB pair" or a "PRB pair" It is 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 of 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 of the component carrier structure apply to subsequent releases.

Logical channel and transport channel

  The MAC layer provides data transmission service to the RLC layer through logical channels. The logical channel is either a control logical channel carrying control data such as RRC signaling or a traffic logical channel carrying user plane data. 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 the transport channel. Data is multiplexed to the transport channel according to the wireless 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, while uplink shared channel (UL-SCH) is used. And random access channels (RACH) are uplink transport channels.

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

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

  Layer 1 / Layer 2 control signaling is used to inform the scheduling target user of the user's assignment status, transport format, and other data related information (eg, HARQ information, transmission power control (TPC) command). It is sent on the downlink along with the data. Layer 1 / Layer 2 control signaling is multiplexed together with downlink data in subframes (assuming that user assignments may change on a subframe basis). It should be noted that user allocation may 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 may be constant for all users in the service area, may be different for each user, or may be dynamic for each user. Layer 1 / Layer 2 control signaling generally needs to be transmitted only once per TTI. Without loss of generality, it is assumed below that TTI is equal to one subframe.

  Layer 1 / Layer 2 control signaling is transmitted on the physical downlink control channel (PDCCH). The PDCCH carries a message as downlink control information (DCI), which in most cases includes resource allocation information of the mobile terminal or the group of user equipment and other control information. 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, information sent in Layer 1 / Layer 2 control signaling for allocating uplink or downlink radio resources (in particular, LTE (−A) Release 10) can be classified into the following items.
-User ID. Indicates the user to be assigned. This is generally 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. It should be noted that the number of RBs allocated by the user may be dynamic.
-Carrier indicator. The control channel transmitted on the first carrier is used when allocating resources related to the second carrier, ie 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) or redundancy version (RV) which is particularly useful in retransmitting data packets or parts thereof.
-Power control commands to adjust the transmission power of the transmission of assigned uplink data and control information.
Reference signal information such as applied cyclic shift and orthogonal cover code index. It is used to transmit or receive reference signals related to assignment.
-An uplink or downlink assignment index used to identify the order of assignment. It is particularly useful in TDD systems.
-Hopping information. For example, indicate whether and how to apply resource hopping to increase frequency diversity.
-CSI request. Used to trigger the transmission of channel state information on the allocated resources.
-Multi-cluster information. A flag used to indicate and control whether transmission is to be done in one cluster (consecutive set of RBs) or in multiple clusters (at least two non-consecutive sets of contiguous RBs). Multi-cluster assignment has been introduced since 3GPP LTE- (A) Release 10.

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

  Downlink control information may be in several formats, with different overall sizes and information contained in the field. The various DCI formats currently defined in LTE are as follows, 5.3.3 in Non-Patent Document 2 (available at the 3GPP website and incorporated herein by reference): It is described in detail in Section 1. For further details regarding the DCI format and the specific information sent in the DCI, please refer to chapter 9.3 of the technical standard or non-patent document 3 (incorporated herein by reference).

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

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

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

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

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 to signal paging messages and broadcast system information messages.

Format 1D : DCI format 1D is used to compactly signal resource assignments 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 two UEs. Future versions of LTE may extend this to accommodate more 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 transmitted information is the same as format 2, but there is no precoding information if the eNodeB has 2 transmit antenna ports, and 2 bits are used to indicate the transmit rank if there are 4 antenna ports The point is different.

Format 2B : introduced in Release 9, used to transmit PDSCH resource assignments for dual layer beamforming.

Format 2C : introduced in Release 10, used to transmit PDSCH resource assignments for up to eight layers of closed loop single or multiple 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 send PUCCH and PUSCH power control commands, including 2 bit or 1 bit power adjustment values, respectively. These DCI formats include individual power control commands for groups of UEs.

Format 4 : DCI format 4 is used to schedule PUSCH using closed loop spatial multiplexing transmission in uplink transmission mode 2.

  The following table gives some overview and typical bit numbers of the available DCI formats, but for the sake of explanation it is assumed that eNodeB has 50 RBs of system bandwidth and 4 antennas. The number of bits shown in the right column contains bits for the CRC of a particular DCI.

  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 received the PDCCH transmission correctly. Furthermore, it is necessary that the UE can identify the PDCCH intended for itself. This can in theory be achieved by appending 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 calculated 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 same section describes a scheme in which error detection is provided to DCI transmission through cyclic redundancy check (CRC). A brief summary is given below.

  Calculate the parity bits of the CRC using the entire payload. Calculate the parity bit and add it. If the UE's transmit antenna selection is not configured or is not applicable, scramble the CRC parity bits with the corresponding RNTI after addition.

  Scrambling may also depend on the UE's selection of transmit antennas, as is evident from [2]. The transmit antenna selection of the UE is configured and, if applicable, scramble the CRC parity bits with the antenna selection mask and the corresponding RNTI after attachment. In either case, since the RNTI is involved in the scrambling operation, for the sake of brevity and without loss of generality, in the following description of the embodiment, the CRC is simply scrambled with the RNTI (and, if applicable) It is said to be unscrambled) and therefore, regardless of such description, RNTI should be understood as yet another element in the scrambling process, eg antenna selection mask.

  Correspondingly, the UE descrambles the CRC by applying the "UE ID", and if no CRC error is detected, it is assumed that the UE is transmitting its control information for the PDCCH. to decide. The terms "mask" and "unmasking" are also used in the above process of scrambling the CRC with an ID.

  Although the SI-RNTI (System Information Radio Network Temporary Identifier) can be used as the above-mentioned "UE ID" that can scramble the CRC of the DCI, the 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. The SI-RNTI is usually fixed in the specification, so it is known to all UEs in advance.

  There are various types of RNTI used for different purposes. The following table, taken from Section 7.1 of [4], provides an overview of the various 16-bit RNTIs and their use.

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. Multiple PDCCHs can be transmitted in one subframe.

The PDCCH to the user equipment is the first N ^PDCCH _symb OFDM symbols in a _subframe (usually one, two or three OFDM symbols (indicated by PCFICH), two in exceptional cases , 3 or 4 OFDM symbols (denoted by the PCFICH), the OFDM symbols extend over the entire system bandwidth. System bandwidth is generally equal to the range of cells or component carriers. 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 across N ^DL _RB x N ^RB _sc subcarriers in the frequency domain are referred to as PDSCH domain or shared channel domain (Described later).

  In downlink grant (ie resource allocation) for physical downlink shared channel (PDSCH), 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 a subframe is distributed over time-frequency control resources. Multiple CCEs can be combined to effectively reduce the control channel coding rate. The CCEs are combined in a predetermined manner using a tree structure to achieve different coding rates.

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

  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" in 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 the parameter k for TDD configurations 0-6, where k is the target positive offset for uplink resource allocation received in subframes Indicates For TDD configuration 0, there are additional definitions of timing for uplink subframes 3 and 8, but are omitted here for the sake of brevity. For example, the parameter k is 6 in subframe 1 of TDD configuration 1 and this means that the assignment of uplink resources received in subframe 1 of TDD configuration 1 targets subframe 1 + 6 = 7 of TDD configuration 1 Sub-frame 7 is actually an uplink sub-frame and so on.

Hybrid ARQ scheme

  A widely used technique for error detection and correction of unreliable channels in packet transmission systems is called 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 can not decode the packet correctly (errors are usually checked with a cyclic redundancy check (CRC)), the receiver retransmits the packet. Request to send. Generally (and throughout this document) transmission of additional information is referred to as "retransmission of (packets)," but this retransmission does not necessarily mean transmitting the same encoding information, but information (belonging to that packet) ( For example, it may mean transmission of additional redundant information).

  Depending on the information making up the transmission (generally code bits / symbols) and on how the receiver processes the information, the following hybrid ARQ schemes are defined:

  In Type I HARQ scheme, if the receiver can not decode the packet correctly, the information of the coded packet is discarded and retransmission is required. This means that every transmission is decoded one by one. In general, retransmissions contain exactly the same information (code bits / symbols) as the first transmission.

  In the Type II HARQ scheme, if the receiver can not decode the packet correctly, retransmission is required, and the receiver soft information (soft bit) of the coded packet (received with error) / Symbol) is stored. This means that the receiver needs a soft buffer. 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 / symbols). When receiving the retransmission, the receiver combines the information stored in the soft buffer with the information received this time, and tries to decode the packet based on the combined information. (The receiver can also try to decode the transmissions individually, but generally combining transmissions improves performance.) Combining transmissions is called so-called "soft-combining", The plurality of received code bits / symbols are likelihood combined and the single received code bits / symbols are code combined. A commonly used soft combining method is Maximum Ratio Combining (MRC) and Log-likelihood-ratio (LLR) combining of received modulation symbols (LLR combining is a code bit) Only valid).

  The Type II scheme is more sophisticated than the Type I scheme because the probability of correctly receiving a packet increases with each retransmission received. This increase is traded for requiring a soft buffer for hybrid ARQ at the receiver. Using this scheme, dynamic link adaptation can be performed by controlling the amount of retransmitted information. For example, if the receiver detects that the decryption is "almost" successful, the receiver will request to transmit only small information (a smaller number of code bits / symbols than the previous transmission) on the next retransmission be able to. In this case, it is theoretically possible that the packet can not be correctly decoded only by examining the retransmission itself (non-self-decoding retransmission).

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

  Synchronous HARQ means that retransmissions of HARQ blocks are performed at predefined periodic intervals. Thus, no explicit signaling is necessary to inform the receiver of the retransmission schedule.

  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 enable correct combining and protocol operation. In the 3GPP LTE system, HARQ operation with eight processes is used. The HARQ protocol operation for transmitting downlink data may be similar to HSDPA or may be identical to HSDPA.

  In uplink HARQ protocol operation, there are two different options for scheduling retransmissions. Retransmissions are either "scheduled" with NACK (also called synchronous non-adaptive retransmission) or explicitly scheduled by the network by transmitting PDCCH (also called synchronous adaptive retransmission). It is one. For synchronous non-adaptive retransmissions, retransmissions use the same parameters as previous uplink transmissions. That is, retransmissions are signaled on the same physical channel resource and each use the same modulation scheme / transport format.

  Since synchronous adaptive retransmissions are explicitly scheduled via the PDCCH, it is possible for the eNodeB to change certain parameters for retransmissions. Retransmissions can also be scheduled on different frequency resources, for example, to avoid fragmentation in the uplink, or the eNodeB changes the modulation scheme or informs the user equipment of the redundant version to use for retransmissions. It can also be done. It should be noted that HARQ feedback (ACK / NACK) and PDCCH signaling are performed at the same timing. Thus, the user equipment may trigger synchronous non-adaptive retransmission (ie whether only NACK is received), or does the eNodeB request synchronous adaptive retransmission (ie PDCCH is signaled) I need only check once.

HARQ and control signaling for TDD operation

  As described above, when transmitting downlink or uplink data in HARQ, an acknowledgment (ACK or negative ACK) is sent in the opposite direction, and the transmitting side determines whether the packet has been successfully or unsuccessfully received. Need to be notified.

  For FDD operation, the Acknowledgment indicator associated with data transmission in subframe n is transmitted in the opposite direction at subframe n + 4 and is paired between the moment the transport is transmitted and the corresponding acknowledgment. There is one synchronized mapping. On the other hand, in the case of TDD operation, subframes are designated per cell as uplink or downlink or special (see the next chapter), whereby resource grants, data transmissions, acknowledgments, and retransmissions Limit the time you can send in your own direction. Thus, the TDD LTE design supports transmission of grouped ACKs / NACKs to convey multiple acknowledgments in one subframe.

  In uplink HARQ, sending multiple acknowledgments (in one downlink subframe) on the Physical Hybrid ARQ Indicator Channel (PHICH) is not a problem. This is because, from the viewpoint of the eNodeB, this is not significantly different from the case where one acknowledgment is sent to multiple UEs simultaneously. However, for downlink HARQ, the uplink control signaling (PUCCH) format of FDD is insufficient to convey additional ACK / NACK information if the asymmetry is biased towards the downlink. Each TDD subframe configuration in LTE (see below and FIG. 5) has its own such mapping predefined between downlink subframes and uplink subframes for HARQ, This mapping is designed to achieve a balance between making the acknowledgment delay as small as possible and evenly distributing the ACKs / NACKs in the available uplink subframes. Further details are provided in chapter 7.3 of Non-Patent Document 5 and incorporated herein by reference.

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

  Table 10.1.3-1 of Non-Patent Document 5 reproduced in FIG. 6 shows the index of the downlink correspondence set of ACK / NACK / DTX response for subframes of radio frames, and supports TDD configuration The number in the box indicates the negative offset of the subframe in which the HARQ feedback of 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 coded version than the original TB at retransmission, so the UE may use incremental redundancy (IR) combining [8] to gain combining. In addition, additional coding gains can be obtained. However, in a real system, although eNB transmits TB to one specific UE in one resource segment, there is a possibility that UE can not detect data transmission because DL control information is lost. In that case, IR combining has a very low ability to decode retransmissions, since no systematic data is available at the UE. To alleviate this problem, the UE should feed back a third state, discontinuous transmission (DTX) feedback, to indicate that TB is not detected in the associated resource segment (this Are different from NACKs that indicate a decoding failure).

Time Division Duplex: TDD

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

  The term "duplexing" refers to bi-directional communication between two devices, as distinguished from unidirectional communication. In the bi-directional case, transmission over the link in each direction can occur simultaneously (full duplex) or alternately (half duplex).

  In the case of 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 radio frame subframes is available for downlink transmission . The remaining subframes are used for uplink transmission or for special subframes. Special subframes are important to advance the timing of uplink transmissions to ensure that the signals transmitted from each UE (ie, the uplink) arrive at the eNodeB almost simultaneously. Because the propagation delay of the signal relates to the distance between the transmitter and the receiver (ignoring reflections and other similar effects), this means that the signal transmitted from UEs near the eNodeB is far from the eNodeB This means that the travel time is shorter than the signal transmitted from the UE. In order to arrive simultaneously, the distant UEs have to transmit signals earlier than the close UEs, which is solved by the so-called "timing advance" procedure of the 3GPP system.

  In TDD, this results in the additional situation that transmission and reception occur on the same carrier frequency, ie 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, the downlink signal is received earlier towards the nearer UEs than far UEs. Guard times are defined in special subframes so that the circuit can switch from DL reception to UL transmission. To further address the timing advance problem, the guard time for distant UEs needs to be longer than for close UEs.

  In 3GPP LTE Release 8 and later, this TDD structure is known as "frame structure type 2" and seven different uplink-downlink configurations are defined, which allow various downlink-uplink configurations. Ratios and switching cycles are possible. FIG. 5 shows a table of seven different TDD uplink-downlink configurations (numbers 0 to 6), where "D" means downlink subframes and "U" uplink subframes. By "S" we mean special subframes. As can be understood from the table, seven available TDD uplink-downlink configurations can provide 40% to 90% of the downlink subframes (parts of special subframes are available for downlink transmission) Because, for the sake of simplicity, special subframes are regarded as downlink subframes).

  FIG. 5 particularly shows frame structure type 2 for 5 ms switching point periodicity (ie TDD configurations 0, 1, 2, 6).

  FIG. 8 shows a radio frame that is 10 ms in length and two corresponding half frames of 5 ms each. The radio frame is composed of 10 subframes of 1 ms each, and each subframe is uplink, down 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, subframe # 6 is a special subframe in the case of TDD configurations 0, 1, 2 and 6, and TDD configurations 3, 4 and 3 are used. , 5 are downlink subframes. The special subframe includes, as three fields, DwPTS (downlink pilot time slot), GP (guard period), and UpPTS (uplink pilot time slot). The following table shows information on 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 configurations applied in the system are a number of operations performed in mobile stations and base stations, such as radio resource management (RRM) measurements, channel state information (CSI) measurements, channel estimation, PDCCH detection, HARQ timing etc. Affect.

  In particular, the user equipment is aware of the TDD configuration in its current cell by reading system information, ie subframes to monitor for measurement, subframes to monitor for CSI measurement and reporting, channel estimation Recognize subframes to monitor for time domain filtering to obtain H.sub.1, subframes to monitor for detection of PDCCH, or subframes to monitor for UL / DL ACK / NACK feedback.

Disadvantages of current semi-static TDD uplink / downlink configurations

  The current mechanism for adapting the UL-DL assignment is based on the system information acquisition procedure or the system information change procedure, and according to the TIB configuration parameters in SIB, in this case specifically SIB1, a specific UL-DL TDD The configuration is shown (for details of broadcast of system information, refer to section 8.1.1 of Non-Patent Document 6. This document 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. With the reuse of ETWS (Earthquake Tsunami Warning System), the supported time scale for UL-DL TDD reconfiguration is more than every 320 ms depending on the default paging cycle being set.

  Nevertheless, the semi-static assignment of TDD UL / DL configurations may or may not reflect instantaneous traffic conditions. The system information change procedure takes too long for dynamic TDD UL / DL reconfiguration when changing from uplink dominant traffic conditions to downlink dominant traffic conditions rapidly. Thus, 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, to mitigate interference to uplink or downlink communications and communications with neighboring cells In order to dynamically generate more downlink subframes to increase the downlink bandwidth and to generate more blank uplink subframes dynamically, it is expected.

  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 being considered. Such signaling mechanism allows instantaneous distribution of information about TDD UL / DL reconfiguration within the communication system and allows mobile stations / base stations to reconfigure TDD UL / DL configuration without delay. Make it

  It has been found that currently used RRC signaling mechanisms can not guarantee the short TDD UL / DL reconfiguration intervals needed to meet the dynamic TDD UL / DL reconfiguration needs. In this regard, it is currently expected that DCI signaling mechanisms will be defined to enable dynamic TDD UL / DL reconfiguration. It is assumed that the reconfiguration is valid for 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 in each TDD configuration, but also the timing between PDSCH and HARQ-ACK. Inconsistencies between relationships must be overcome.

  As described above, for each of TDD configurations 0 to 6, the timing between uplink resource allocation (eg, UL grant) in DCI format 0/4 message and target PUSCH transmission in corresponding uplink subframe. Relationships are defined. Specifically, the timing relationship between the DCI and the PUSCH allows for scheduling of target PUSCH transmissions that overlap at the 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 radio frame relates to DCI transmission performed in the previous radio frame.

  Similarly, for each of TDD configurations 0-6, a timing relationship between one or more PDSCH transmissions and one or more subsequent hybrid ARQ-ACK transmissions is defined. Also 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 one radio frame relates to PDSCH transmission performed in two radio frames preceding it.

  In this regard, in TDD UL / DL reconfiguration between subsequent subframes, it is possible to continuously allocate resources for all supported uplink subframes even when applying the timing relationship between corresponding DCI and PUSCH Can not. Such uplink resource allocation inconsistency is illustrated below, but in this case the UL grant is in DCI transmissions sent before TDD reconfiguration is effective and PUSCH transmissions related to the DCI transmissions Are scheduled after TDD reconfiguration is enabled.

  As an example, TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6 is shown in FIG. 9A. In TDD configuration 3 and TDD configuration 6 respectively, timing relationships between DCI and PUSCH are indicated by dashed arrows. Correspondingly, the DCI transmissions associated with each PUSCH transmission are indicated as the origin of the dashed arrows, in order to assign PUSCH transmissions (ie uplink transmissions) to subframes supporting uplink transmissions.

  However, due to TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6, PUSCH transmission by subframes having index 24 is not possible. In particular, TDD configuration 6 is used after TDD UL / DL reconfiguration is enabled (ie after subframe 20), and the timing relationship between DCI and PUSCH in TDD configuration 6 results DCI transmission where PUSCH transmission may be performed in subframes of index 24 is not possible. In FIG. 9A, this can be understood by the absence of an arrow ending at the PUSCH of subframe 24.

  Even if it is assumed that PUSCH transmission related to DCI transmission before TDD UL / DL reconfiguration is performed after TDD UL / DL reconfiguration, for example, as shown in PUSCH transmission of subframes having indexes 22 and 23 As a result, there is no possibility of DCI transmissions where PUSCH transmissions are scheduled in index 24 subframes.

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

  Therefore, the uplink bandwidth can not 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, TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6 is also shown in FIG. 9B. The timing relationship between PDSCH and HARQ-ACK for each of TDD configuration 3 and TDD configuration 6 is indicated by a dashed arrow. Correspondingly, for HARQ-ACK transmission in subframes supporting uplink transmission, PDSCH transmission related to each HARQ-ACK transmission is indicated as the origin of the dashed arrow.

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

  TDD HARQ-ACK transmissions related to PDSCH transmissions performed prior to TDD UL / DL reconfiguration, as shown for example in HARQ-ACK transmissions related to PDSCH transmissions in subframes of indices 15, 16 and 19 Even assuming that it is performed after UL / DL reconfiguration, there is no possibility of HARQ-ACK transmission which will be notified of reception of PDSCH transmission in subframes of index 11, 17, and 18.

  Thus, the assigned hybrid ARQ functionality can not be immediately utilized after TDD UL / DL reconfiguration, as the timing relationship between PDSCH and HARQ-ACK is predefined for each TDD configuration.

  At the recent 3GPP LTE meeting, various approaches for TDD UL / DL reconfiguration were considered. Specifically, the reference configurations are defined separately for the timing relationship between DCI and PUSCH and the timing relationship between PDSCH and HARQ-ACK, which must be applied continuously after TDD UL / DL reconfiguration. It was suggested to do. As an example, although the SIB1 TDD configuration is being operated, the UE will continuously apply the timing relationships specified in the newly defined reference configuration.

  However, such an approach has the following disadvantages. First, additional upper layer configuration is required. Second, the timing relationship of the reference configuration must be applied even when it is not necessary (e.g. when it is not necessary).

  In the exemplary case of the SIB1 TDD configuration, this results in an unnecessarily long delay in some HARQ-ACK transmissions and an unnecessary long delay between DCI and PUSCH transmissions in some TDD configurations. HARQ-ACK transmissions are 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 Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 11) TS 36.213 v11.1.0 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, the timing relationship between DCI and PUSCH, and / or the timing relationship between PDSCH and HARQ-ACK. Based on the notion that it should be applied in form (ie individually). This distinction between TDD radio frame structure and timing relationship is performed only during a short period before and / or after reconfiguration becomes effective.

  In particular, the predefined TDD radio frame configuration or TDD configuration can be configured to reserve subframes in a radio frame in the downlink (abbreviated as "D") subframes, in the uplink (abbreviated as "U") subframes, or It is defined as a special (abbreviated as "S") subframe. In this regard, when performing TDD UL / DL reconfiguration, the source TDD configuration defines the reservation of subframes before the reconfiguration becomes effective, and the target TDD configuration is a sub after the reconfiguration becomes effective. Define frame reservations.

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

  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 effective. The target TDD configuration 6 then defines the reservation of subframes in the radio frame after reconfiguration. In this regard, in the TDD communication scheme, the TDD configuration pattern “D, S, U, U, U, D, D, D, D, D” is used before reconfiguration becomes effective, and the reconfiguration becomes effective. After that, the TDD configuration pattern “D, S, U, U, U, D, S, U, U, D” is used.

  According to the invention, the timing relationship between the DCI and the PUSCH and / or the timing relationship between the PDSCH and the HARQ-ACK may be sourced / d during a certain period before and / or after the TDD UL / DL reconfiguration becomes effective. It is applied differently to the target TDD configuration. In other words, although each source / target TDD configuration defines the timing relationship between DCI and PUSCH and / or the timing relationship between PDSCH and HARQ-ACK, according to the present invention, TDD UL / DL reconfiguration is effective. The rules of this provision are broken for a short period of time before and / or after.

  In particular, the term "timing relationship between DCI and PUSCH" defines when (i.e. in which subframe) PUSCH transmission relating to DCI transmission must be performed. In particular, since the PUSCH transmission needs a UL grant preceding it, the DCI transmission to which the PUSCH transmission relates is essentially a DCI transmission that carries the UL grant. In other words, in LTE Release 11, the corresponding DCI transmission is in 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 PDSCH. It should be interpreted in the sense 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, the timing relationships related between DCI and PUSCH and / or PDSCH and HARQ-ACK, which are predefined for TDD configuration during TDD UL / DL reconfiguration, respectively, of uplink bandwidth It applies differently to TDD radio frame configuration to improve utilization and / or to enable hybrid ARQ functionality.

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

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

  If communication between the mobile station and the base station is to be reconfigured for a given subframe N at the beginning of a radio frame, subframes before subframe N for which reconfiguration is effective are based on the source TDD configuration. In contrast to subframes that are configured, subframes after subframe N are configured based on the target TDD configuration.

  Also, if the mobile station detects one or more downlink control information (DCI) transmissions conveying a UL grant, 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 for PUSCH transmissions related to DCI transmissions received by the mobile station by subframe N-6 including subframe N-6. Specifically, the mobile station may source TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey respective UL grants received during their subframes. The timing relationships defined in the configuration are applied to determine when that one or more PUSCH transmissions will occur.

  For PUSCH transmissions related to DCI transmissions received by the mobile station between subframe N-5 and subframe N-1 (including subframe N-5 and subframe N-1), the mobile station is intermediate Apply the (ie predefined) TDD configuration of Specifically, the mobile station is intermediate to one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received during their subframes. Apply the timing relationships defined in the (ie, predefined) TDD configuration 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 target TDD on one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received in their subframes. The timing relationships defined in the configuration are applied to determine when one or more PUSCH transmissions will occur.

  The intermediate (i.e., predefined) TDD configuration is one of a plurality of TDD configurations set in advance, for example, any one of TDD configurations 0 to 6.

  In particular, by applying an intermediate (ie, pre-defined) TDD configuration to the PUSCH transmissions involved in DCI transmissions just before TDD UL / DL reconfiguration (and hence target TDD configuration) becomes effective, Uplink bandwidth utilization can be improved.

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

  The source TDD configuration is one of a plurality of TDD configurations set in advance. 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.

  If communication between the mobile station and the base station is to be reconfigured for a given subframe N at the beginning of a subframe, then the radio frame prior to subframe N for which reconfiguration is effective is based on the source TDD configuration. In contrast to the setting, radio frames after subframe N are set based on the target TDD configuration.

  Furthermore, if the mobile station detects one or more downlink control information (DCI) transmissions conveying a UL grant, the mobile station responds to the detected DCI transmissions according to the following scheme: Perform uplink shared channel (PUSCH) transmission.

  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 source TDD to one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received during their subframes. Apply the timing relationships defined in the configuration.

  The mobile station applies the target TDD configuration for PUSCH transmissions related to DCI transmissions received by the mobile station after subframe N + 1. Specifically, the mobile station may target TDD on one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received in their subframes. Apply the timing relationships defined in the configuration.

  In particular, by applying the target TDD configuration to the PUSCH transmissions related to DCI transmissions received immediately after TDD UL / DL reconfiguration is enabled (ie subframe N), the uplink bandwidth in the communication system is Utilization 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 designated using another improved TDD UL / DL reconfiguration. Communication is reconfigured from a source TDD configuration to a target TDD configuration.

  The source and target uplink / downlink configurations are TDD configurations among multiple TDD configurations. For example, the source and target TDD configurations are any one of a plurality of TDD configurations 0 to 6 set in advance.

  If communication between the mobile station and the base station is to be reconfigured for a given subframe N at the beginning of a subframe, then the radio frame prior to subframe N for which reconfiguration is effective is based on the source TDD configuration. In contrast to the setting, radio frames after subframe N are set based on the target TDD configuration.

  Furthermore, 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.

  The mobile station applies the source TDD configuration for hybrid ARQ-ACK transmissions sent from the mobile station up to subframe N-1 (including subframe N-1). Specifically, the mobile station may, during those subframes, transmit one or more HARQ-ACKs to be transmitted 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 may, during those subframes, transmit one or more HARQ-ACKs to be transmitted 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 above. Another intermediate TDD configuration is one of multiple TDD configurations.

  The mobile station applies the target TDD configuration for hybrid ARQ-ACK transmissions sent from the mobile station after subframe N + 13. Specifically, the mobile station is targeted in one or more HARQ-ACK transmissions transmitted in response to one or more PDSCH transmissions previously received by the mobile station in those subframes. Apply the timing relationships defined in the TDD configuration.

  In particular, by applying another intermediate (ie, predefined) TDD configuration to the HARQ-ACK transmissions 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 invention, a method is proposed for communicating between a mobile station and a base station in a communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of the plurality of uplink / downlink configurations, and the target uplink / downlink configuration is any of the plurality of uplink / downlink configurations It is one. Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the communication system responds to downlink control information (DCI) transmission by subframe N-6, which includes subframe N-6. The source uplink / downlink configuration applies to PUSCH transmissions related to received DCI transmissions, and pre-defined for PUSCH transmissions related to DCI transmissions received during subframes N-5 to N-1 Physical uplink shared channel (PUSCH) as applying the configured uplink / downlink configuration and applying the target uplink / downlink configuration to PUSCH transmissions related to DCI transmissions received after subframe N Transmit and pre-defined uplink / downlink configurations, the above multiple uplinks / downlink configurations 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 plurality of uplink / downlink configurations are uplink / downlink configurations 0-6 and the source uplink / downlink configurations are uplink / downlink configurations 1 The predefined uplink / downlink configuration is an uplink / downlink configuration 6, which is one of the subsets of ̃6.

  According to a second embodiment according to the second aspect of the present invention, a method is proposed for communicating between a mobile station and a base station in a communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source uplink / downlink configuration is a predefined one of the plurality of uplink / downlink configurations, and the target uplink / downlink configuration is any of the plurality of uplink / downlink configurations It is one of the Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the communication system may receive DCI received by subframe N including subframe N in response to downlink control information (DCI) transmission. Apply the source uplink / downlink configuration to the PUSCH transmissions involved in the transmission, apply the target uplink / downlink configuration to the PUSCH transmissions involved in the DCI transmissions received after subframe N + 1, etc. physical Perform uplink shared channel (PUSCH) transmission.

  According to a more detailed embodiment of this method, the plurality of 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, a plurality of uplink / downlink configurations each determine a timing offset between the DCI transmission and the corresponding PUSCH transmission.

  According to yet another more detailed embodiment of the method, the source uplink / downlink configuration is configured such that subframes are reserved for downlink transmission until subframe N-1 including subframe N-1 Or indicate a special subframe that supports both downlink transmission and uplink transmission, or target uplink / downlink configuration for subframe N or later, It indicates whether the subframe is reserved for downlink transmission or reserved for uplink transmission, or indicates a special subframe that supports both downlink transmission and uplink transmission.

  According to yet another more detailed embodiment of this method, the information informing that communication between the mobile station and the base station is to be reconfigured is distributed in the communication system, and the information is in subframe N-14. When the information is distributed within the interval from the subsequent to the subframe N-5 including the subframe N-5, the communication is reconfigured for the predetermined subframe N, and N is at the beginning of the radio frame. It is a subframe.

  According to a third embodiment according to the third aspect of the invention, a method is proposed for communicating between a mobile station and a base station in a communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source and target uplink / downlink configurations are uplink / downlink configurations among multiple uplink / downlink configurations. Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the communication system is responsive to the physical downlink shared channel (PDSCH) transmission to subframe N-1 including subframe N-1. Apply the source uplink / downlink configuration for hybrid ARQ-ACK transmission and apply another predefined uplink / downlink configuration for hybrid ARQ-ACK transmission during subframes N to N + 12. , Apply the target uplink / downlink configuration to the hybrid ARQ-ACK transmission in subframe N + 13 or later, perform hybrid ARQ-ACK transmission, wherein said another predefined uplink / downlink configuration is In one of several 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 a further more detailed embodiment of this method, said another predefined uplink, wherein any one of a plurality of uplink / downlink configurations applies to hybrid ARQ-ACK transmission during subframe N to N + 12. Information indicating whether to correspond to the / downlink configuration is distributed in the communication system.

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

  According to a further more detailed embodiment of this method, in response to the physical downlink shared channel (PDSCH) transmission, a source uplink / downlink configuration is applied, if the source uplink / downlink configuration is applied, Define a hybrid ARQ-ACK transmission up to subframe N-1 comprising subframe N-1, if said hybrid ARQ-ACK transmission relates to said PDSCH transmission, and said another predefined uplink / down If a link configuration is applied, that other predefined uplink / downlink configuration defines a hybrid ARQ-ACK transmission during subframe N to N + 12, said hybrid ARQ-ACK transmission being said PDSCH. If it relates to transmission, the mobile station may 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 this method, said further predefined uplink / downlink configuration is applied, and said further predefined uplink / downlink configuration is uplink. Define hybrid ARQ-ACK transmission between subframes N to N + 12 for at least one subframe configured to support transmission only, said at least one subframe comprising subframes N-11 to subframe N If the mobile station is within the interval up to subframe N-1 including -1, the mobile station may perform hybrid ARQ involving only subframes configured to support downlink transmission during subframes N to N + 12. Transmit an ACK, or the mobile station may transmit 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, for the first embodiment, a mobile station is proposed which communicates with a base station in a communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of the plurality of uplink / downlink configurations, and the target uplink / downlink configuration is any of the plurality of uplink / downlink configurations It is one. Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the mobile station responds to downlink control information (DCI) transmission by subframe N-6 including subframe N-6. The source uplink / downlink configuration applies for PUSCH transmissions related to received DCI transmissions, and is pre-defined 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 transmissions received after subframe N, applying different uplink / downlink configurations Pre-defined uplink / downlink configurations, the above 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 plurality of uplink / downlink configurations are uplink / downlink configurations 0-6 and the source uplink / downlink configurations are uplink / downlink configurations The predefined uplink / downlink configuration is uplink / downlink configuration 6, which is one of 1 to 6 subsets.

  In addition, for the second embodiment, a mobile station is proposed which communicates with a base station in a communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source uplink / downlink configuration is a predefined one of the plurality of uplink / downlink configurations, and the target uplink / downlink configuration is any of the plurality of uplink / downlink configurations It is one of the Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the mobile station may receive DCI received by subframe N including subframe N in response to downlink control information (DCI) transmission. Apply the source uplink / downlink configuration to the PUSCH transmissions involved in the transmission, apply the target uplink / downlink configuration to the PUSCH transmissions involved in the DCI transmissions received after subframe N + 1, etc. physical Perform uplink shared channel (PUSCH) transmission.

  According to a more detailed embodiment of this mobile station, the plurality of 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 mobile station, a plurality of uplink / downlink configurations each determine a timing offset between the DCI transmission and the corresponding PUSCH transmission.

  According to a further 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 comprising subframe N-1. Or indicate special subframes that support both downlink transmission and uplink transmission, and the target uplink / downlink configuration is for sub-frame N and subsequent sub-frames. It indicates whether the frame is reserved for downlink transmission or uplink transmission, or indicates a special subframe that supports both downlink transmission and uplink transmission.

  According to yet another more detailed embodiment of the mobile station, information informing that communication between the mobile station and the base station is to be reconfigured is distributed in the communication system, and the information is transmitted in subframe N- When the information is distributed from the 14th onwards to the subframe N-5 including the subframe N-5, the communication of the predetermined subframe N is reconstructed by the distribution of the information, and N is the beginning of the radio frame. It is a sub-frame in

  Furthermore, in the third embodiment, a mobile station that communicates with a base station in a communication system is proposed. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source and target uplink / downlink configurations are uplink / downlink configurations among multiple uplink / downlink configurations. Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the mobile station responds to the physical downlink shared channel (PDSCH) transmission to subframe N-1 including subframe N-1 Apply the source uplink / downlink configuration for hybrid ARQ-ACK transmission and apply another predefined uplink / downlink configuration for hybrid ARQ-ACK transmission during subframes N to N + 12. , Apply the target uplink / downlink configuration to the hybrid ARQ-ACK transmission in subframe N + 13 or later, perform hybrid ARQ-ACK transmission, wherein said another predefined uplink / downlink configuration is It is one of multiple 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 uplink / downlink configuration 5.

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

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

  According to a further more detailed embodiment of the mobile station, in response to a physical downlink shared channel (PDSCH) transmission, a source uplink / downlink configuration is provided, if the source uplink / downlink configuration is applied. , 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 pre-defined uplink described above If another downlink / downlink configuration is applied, that other predefined uplink / downlink configuration defines a hybrid ARQ-ACK transmission between subframes N to N + 12, said hybrid ARQ-ACK transmission In the case of the PDSCH transmission, the mobile station may 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, the above-mentioned another predefined uplink / downlink configuration is applied, and the other predefined uplink / downlink configuration is up. Define hybrid ARQ-ACK transmission between subframes N to N + 12 for at least one subframe set to support only link transmission, said at least one subframe being from subframe N-11 to subframe If within the interval up to subframe N-1, including N-1, the mobile station is a hybrid ARQ involving only subframes configured to support downlink transmission during subframes N to N + 12. Transmit an ACK, or the mobile station may transmit at least one subframe. 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.

  Further, for the first embodiment, a computer readable medium is proposed which stores instructions which, when executed by a processor of a mobile station, cause the mobile station to communicate with a base station in the communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of the plurality of uplink / downlink configurations, and the target uplink / downlink configuration is any of the plurality of uplink / downlink configurations It is one. Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the mobile station responds to downlink control information (DCI) transmission by subframe N-6 including subframe N-6. The source uplink / downlink configuration applies to PUSCH transmissions related to received DCI transmissions, and pre-defined for PUSCH transmissions related to DCI transmissions received during subframes N-5 to N-1 Physical uplink shared channel (PUSCH) as applying the configured uplink / downlink configuration and applying the target uplink / downlink configuration to PUSCH transmissions related to DCI transmissions received after subframe N Transmit, pre-defined uplink / downlink configurations, multiple uplinks / downlinks It is one of the link configuration.

  Further, for the second embodiment, a computer readable medium is proposed which stores instructions which, when executed by a processor of a mobile station, cause the mobile station to communicate with a base station in the communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source uplink / downlink configuration is a predefined one of the plurality of uplink / downlink configurations, and the target uplink / downlink configuration is any of the plurality of uplink / downlink configurations It is one of the Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the mobile station may receive DCI received by subframe N including subframe N in response to downlink control information (DCI) transmission. Apply the source uplink / downlink configuration to the PUSCH transmissions involved in the transmission, apply the target uplink / downlink configuration to the PUSCH transmissions involved in the DCI transmissions received after subframe N + 1, etc. physical Perform uplink shared channel (PUSCH) transmission.

  In addition, for the third embodiment, a computer readable medium is proposed which stores instructions which, when executed by a processor of a mobile station, cause the mobile station to communicate with a base station in the communication system. Communication is reconfigured from the source uplink / downlink configuration to the target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of multiple uplink / downlink configurations, and the target uplink / downlink configuration is any one of those multiple uplink / downlink configurations It is. Multiple uplink / downlink configurations are preconfigured for time division duplex (TDD) communication. When reconfiguring communication for a given subframe N at the beginning of a radio frame, the mobile station responds to the physical downlink shared channel (PDSCH) transmission to subframe N-1 including subframe N-1 Apply the source uplink / downlink configuration for hybrid ARQ-ACK transmission and apply another predefined uplink / downlink configuration for hybrid ARQ-ACK transmission during subframes N to N + 12. , Apply the target uplink / downlink configuration to the hybrid ARQ-ACK transmission in subframe N + 13 or later, perform hybrid ARQ-ACK transmission, wherein said another predefined uplink / downlink configuration is It is one of multiple uplink / downlink configurations.

  In the following, the invention will be described in more detail with reference to the attached drawings.

1 illustrates an exemplary architecture of a 3GPP LTE system. Fig. 3 shows an exemplary overview of the entire 3 GPP LTE E-UTRAN architecture. Fig. 6 shows an exemplary subframe boundary of downlink component carriers defined in 3GPP LTE (at the time of release 8/9). Fig. 6 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 in each and switching point periodicity are shown. The timing of the HARQ ACK / NACK / DTX feedback of the static TDD structures 0-6 defined by 3GPP LTE is shown. FIG. 16 illustrates timing of physical uplink shared channel (PUSCH) transmission in response to downlink control information (DCI) transmission for static TDD configurations 0-6 defined in 3GPP LTE. The structure of a radio frame consisting of two half-frames, 10 subframes is shown in the case of 5 ms switching point periodicity. 9A and 9B illustrate exemplary radio frame ordering and its drawbacks for three types of TDD UL / DL reconfiguration operations. Fig. 6 illustrates exemplary radio frame ordering and its drawbacks for three types of TDD UL / DL reconfiguration operations. FIG. 11A shows an exemplary TDD UL / DL reconfiguration operation including improved assignment of PUSCH transmissions according to the first embodiment of the present invention, and FIG. 11B shows a second embodiment of the present invention, 7 illustrates an example TDD UL / DL reconfiguration operation that includes improved HARQ-ACK transmission assignment. Fig. 7 illustrates an exemplary TDD UL / DL reconfiguration operation including different realizations of the improved PUSCH transmission assignment according to the third embodiment of the present invention.

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

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

  In the context of the present invention, TDD UL / DL reconfiguration using the terms "source TDD configuration" or "source uplink / downlink configuration" as well as "target TDD configuration" or "target uplink / downlink configuration" Emphasize the concept of Nevertheless, it should be clear that the source TDD configuration is not the first configuration to be applied to communication between the mobile station and the base station in the communication system. Similarly, the target TDD configuration is also not the last TDD configuration to be applied to communications in the communication system.

  Specifically, in the context of the present invention, the terms source and target TDD configuration may be configured such that if TDD UL / DL reconfiguration is enabled in subframe N, then the source TDD configuration is in the first embodiment an interval [N -K, N-6], at least k> = 10, and in the second embodiment, interpreted at least in the interval [N-k, N], meaning that 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 at least applied to [N + 1, N + j] in the second embodiment, j It is> = 10. Similar considerations apply equally to the third and fourth embodiments.

  Hereinafter, some embodiments of the present invention will be described in detail. It should be understood that these descriptions do not limit the invention, but are merely exemplary of embodiments of the invention in order to provide a thorough understanding of the invention. It will be appreciated by those skilled in the art that the general principles of the invention as set forth in the claims can be applied to different scenarios or can be applied in a manner not explicitly described herein. . Thus, the following scenario, which is assumed for the purpose of describing the various embodiments, does not limit the invention.

  The various embodiments described in the context of the present invention generally refer to TDD configurations, and in particular provide an improved, more flexible TDD configuration and the mechanisms / processes associated therewith.

First embodiment

  In the context of the summary of the invention, the various embodiments relate to TDD radios for TDD UL / DL reconfiguration, the timing relationship involved between DCI and PUSCH and / or between PDSCH and HARQ-ACK, in TDD radio. It has already been emphasized that it is based on the concept of applying differently than the frame structure. This distinction between TDD radio frame configuration and timing relationship is made only for a short period of time before and / or after reconfiguration is enabled.

  According to a 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 during a short period before reconfiguration becomes effective so that utilization of uplink bandwidth in the communication system can be improved. To fit.

  An exemplary TDD UL / DL reconfiguration operation according to the first embodiment is shown in FIG. 11A, which highlights the benefits of TDD radio frame configuration and the distinction between DCI and PUSCH timing relationships. 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. Reconstruction takes effect at 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 a source TDD configuration to a target TDD configuration. In order to make this first embodiment applicable, the source TDD configuration is one of a subset of multiple TDD configurations, and the target TDD configuration is any one of the multiple TDD configurations. It is. It should be emphasized that the term "reconfiguration" essentially defines that the source TDD configuration is different from the target TDD configuration.

  In an advantageous implementation, subsets of TDD configurations correspond to TDD configurations 1-6, and multiple 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 still the timing relationship between adapted DCI and PUSCH is that the source TDD configuration has TDD configuration It can be applied to the TDD UL / DL reconfiguration of the first embodiment, which is zero.

  Information is distributed in the communication system including the mobile station and the base station in order to reconstruct the communication between the mobile station and the base station. With this information distribution, the communication between the mobile station and the base station is reconstructed for a given subframe N, which is at the beginning of the radio frame.

  According to an exemplary implementation, subframe N for which reconstruction is enabled corresponds to the first subframe in the 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) transmissions are performed by the mobile station according to the timing relationship between DCI and PUSCH defined in this embodiment. To be done. Specifically, the term "timing relationship between DCI and PUSCH" means the timing offset defined by the 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 the PUSCH transmission related to DCI transmission received by the mobile station up to subframe N-6 including subframe N-6. Specifically, the mobile station may source TDD to one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received during their subframes. Apply the timing relationships defined in the configuration.

  Then, by the mobile terminal, to PUSCH transmission related to DCI transmission received by the mobile station between subframe N-5 to subframe N-1 (including subframe N-5 and subframe N-1) The (pre-defined) TDD configuration is applied. Specifically, the mobile station is intermediate to one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received during their subframes. Apply the timing relationships defined in the (ie predefined) TDD configuration.

  Finally, the target TDD configuration is applied by the mobile terminal to the PUSCH transmission related to DCI transmissions received by the mobile station after subframe N. Specifically, the mobile station may target TDD on one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received in their subframes. Apply the timing relationships defined in the configuration.

  According to an advantageous implementation, the intermediate (i.e. predefined) TDD configuration applied to PUSCH transmissions related to DCI transmissions between subframes N-5 to N-1 is different from the source TDD configuration. In this regard, the communication system is enabled to apply TDD configuration as an intermediate (ie, pre-defined) TDD configuration defining the timing relationship between DCI and PUSCH, thereby providing source TDD configuration and target The loss of uplink bandwidth resulting from the transition between TDD configurations is mitigated.

  According to an advantageous implementation of the first embodiment, the intermediate (ie predefined) TDD configuration is TDD configuration 6 as defined in FIG. In this TDD configuration 6, DCI transmission capable of carrying UL grants for the three subframes of the next radio frame is possible. In particular, in TDD configuration 6, DCI transmission in subframes 5, 6 and 9 enables PUSCH transmission of subframes (5 + 7) = 12, (6 + 7) = 13, and (9 + 5) = 14, respectively. In this regard, in TDD configuration 6, perform PUSCH transmission in all subframes of the first half of the next radio frame (ie subframes 2, 3 and 4) that can be configured to support uplink transmission (See Figure 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 shaded subframes in FIG. 11A). Specifically, applying TDD configuration 6 to PUSCH transmissions related to DCI subframes received in subframes 15, 16 and 19 and TDD configuration 6 enabled TDD UL / DL reconfiguration The PUSCH transmission to be performed later is defined in subframes 22, 23, and 24 (see the dashed arrows in FIG. 11A).

  In this regard, in the first embodiment, the timing relationship between DCI and PUSCH, i.e. the timing relationship corresponding to the intermediate (i.e. predefined) TDD configuration, during a short period before the reconfiguration becomes effective. It can be adapted. Thereby, it is possible to avoid PUSCH subframes that can not be allocated, and improve the utilization of uplink bandwidth in the communication system.

  Specifically, when TDD configuration 6 is used as an intermediate (ie, predefined) TDD configuration to determine the timing relationship between DCI and PUSCH of DCI transmissions between subframes N-5 to N-1 , All subframes in the first half of the next radio frame can be allocated for PUSCH transmission. Specifically, the next radio frame is the first radio frame for which TDD UL / DL reconfiguration is effective.

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 of time after reconfiguration becomes effective, so that utilization of uplink bandwidth in the communication system can be improved. Make it

  Also in the second embodiment, communication between the mobile station and the base station in the communication system is assumed. Communication is reconfigured from a source TDD configuration to a 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. It is one. It should be emphasized that the term "reconfiguration" essentially defines that the source TDD configuration is different from the target TDD configuration.

  In an advantageous implementation, an intermediate (i.e., 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 to 6. In the above advantageous implementation, TDD configurations 1 to 6 seem to be inconvenient as the source TDD configuration of the second embodiment, but still the timing relationship between the adapted DCI and PUSCH is the source TDD configuration It can be applied to the TDD UL / DL reconfiguration of the second embodiment, which is one of the TDD configurations 1 to 6.

  Information is distributed in the communication system including the mobile station and the base station in order to reconstruct the communication between the mobile station and the base station. With this information distribution, the communication between the mobile station and the base station is reconstructed for a given subframe N, which is at the beginning of the radio frame.

  According to an exemplary implementation, subframe N for which reconstruction is enabled corresponds to the first subframe in the 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) transmissions are performed by the mobile station according to the timing relationship between DCI and PUSCH defined in this embodiment. To be done. Specifically, the term "timing relationship between DCI and PUSCH" means the timing offset defined in 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 transmissions related to DCI transmissions received by the mobile station by subframe N including subframe N. Specifically, the mobile station may source TDD to one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received during their subframes. Apply the timing relationships defined in the configuration.

  The target TDD configuration is then applied by the mobile terminal to PUSCH transmissions related to DCI transmissions received by the mobile station after subframe N + 1. Specifically, the mobile station may target TDD on one or more PUSCH transmissions scheduled in response to one or more DCI transmissions that convey the respective UL grants received in their subframes. Apply the timing relationships defined in the configuration.

  Since TDD UL / DL reconfiguration is set to be valid for subframes with index N at the beginning of a 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 PUSCH transmissions related to DCI transmissions received in one radio frame, and target TDD configuration to PUSCH transmissions related to DCI transmissions received in another (ie next) subframe There is also no possibility of being applied.

  In other words, by defining the subframe N at the beginning of the radio frame, switching between application of the source TDD configuration and application of the target TDD configuration is not performed at the boundary of the radio frame. This applies only if the source TDD configuration is applied to PUSCH transmissions related to DCI transmissions received by 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 the assignment of the PUSCH transmission to the subframe 24 can not be guaranteed without doing so. As can be easily understood from FIG. 7, in TDD configuration 0, TDD transmission capable of carrying UL grants related to two subframes of the next radio frame is possible. In particular, in TDD configuration 0, DCI transmission in subframes 5 and 6 enables PUSCH transmission in subframes (5 + 7) = 12 and (6 + 7) = 13, respectively. However, it is also possible to configure subframe 14 to support PUSCH transmission.

  In this regard, TDD configuration 0 also applies to PUSCH transmissions related to DCI transmissions received in subframe N (eg subframe 0, 10, 20), whereby subframe N + 4 (eg subframe 4). , 14, 24) are enabled. In other words, when TDD configuration 0 is used as an intermediate (ie, predefined) TDD configuration to determine the timing relationship between DCI and PUSCH in 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. Thus, TDD configuration 0 defines the PUSCH transmission to be performed in subframe 24 after TDD UL / DL reconfiguration is enabled (see dashed arrows in FIG. 12).

  In general, in the first and second embodiments, each of a plurality of TDD configurations determines the timing offset between the one or more DCI transmissions and the corresponding PUSCH transmissions. 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.

  Furthermore, in the first and second embodiments, the source TDD configuration is configured such that subframes are reserved for downlink transmission, or subframes up to subframe N-1, including subframe N-1. Indicate a special subframe that supports both downlink transmission and uplink transmission, target TDD configuration is for subframe N or later, and subframes for downlink transmission Designate if reserved or reserved for uplink transmission, or indicate special subframes that support both downlink and uplink transmission. In this regard, reconfiguration of the TDD radio frame structure is valid for subframe N, which includes the indicated subframe N.

Third embodiment

  In relation to the third embodiment of the present invention, various embodiments relate to the timing relationship related between DCI and PUSCH and / or between PDSCH and HARQ-ACK for TDD UL / DL reconfiguration. It is emphasized again that it is based on the concept of applying differently to the TDD radio frame configuration. This distinction between TDD radio frame configuration and timing relationship is made only for a short period of time before and / or after reconfiguration is enabled.

  According to a third embodiment, the timing relationship between PDSCH and HARQ-ACK is adapted to enable advantageous TDD UL / DL reconfiguration. Specifically, in this embodiment, during the short period after the reconfiguration becomes effective, the timing relationship between PDSCH and HARQ-ACK is adapted so that the hybrid ARQ function can always be used.

  An exemplary TDD UL / DL reconfiguration operation according to the third embodiment is shown in FIG. 11B, which shows the benefits of distinguishing TDD radio frame configuration and timing relationships between PDSCH and HARQ-ACK. It emphasizes. 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. Reconstruction takes effect at 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 a source TDD configuration to a target TDD configuration. The source TDD configuration and the target TDD configuration are any TDD configurations of multiple TDD configurations. It should be emphasized that the term "reconfiguration" 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 TDD configurations 0-6 and the target TDD configuration corresponds to another one of TDD configurations 0-6.

  Information is distributed in the communication system including the mobile station and the base station in order to reconstruct the communication between the mobile station and the base station. With this information distribution, the communication between the mobile station and the base station is reconstructed for a given subframe N, which is at the beginning of the radio frame.

  According to an exemplary implementation, subframe N for which reconstruction is enabled corresponds to the first subframe in the 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 physical downlink shared channel (PDSCH) transmissions, the associated hybrid ARQ-ACKnowledgement (HARQ-ACK) transmissions have a timing relationship between PDSCH and HARQ-ACK as defined in this embodiment. According to the mobile station. Specifically, the term "timing relationship between PDSCH and HARQ-ACK" means the timing offset defined by the TDD configuration between one or more PDSCH transmissions and their corresponding HARQ-ACK transmissions.

  First, the source TDD configuration is applied by the mobile station to the hybrid ARQ-ACK transmission up to subframe N-1, which includes subframe N-1. Thus, based on the source TDD configuration, the mobile station may or may not perform one or more HARQ-ACK transmissions for each subframe up to subframe N-1, including subframe N-1. To judge. Specifically, to which of the one or more PDSCH transmissions (if performed) the mobile station has shown the source TDD configuration indicates HARQ-ACK transmission in each subframe. Determine

  Then, for the hybrid ARQ-ACK transmission between subframe N including subframe N to subframe N + 12 including subframe N + 12, another intermediate (ie, predefined) TDD configuration is applied by the mobile station Ru. Thus, the mobile station has another intermediate (i.e. predefined) whether it has to carry out one or more HARQ-ACK transmissions for each subframe during subframes N to N + 12. It makes a decision based on the TDD configuration. Specifically, the mobile station may have another intermediate (ie, predefined) TDD configuration for any of the previously performed one or more PDSCH transmissions (ie, with PDSCH transmissions), It is determined whether HARQ-ACK transmission in each subframe is indicated.

  Finally, the target TDD configuration is applied by the mobile station to the hybrid ARQ-ACK transmission on and after subframe N + 13. Therefore, the mobile station determines, based on the target TDD configuration, whether or not one or more HARQ-ACK transmissions should be performed for each subframe after subframe N + 13. Specifically, for any of the one or more PDSCH transmissions (i.e., where there is PDSCH transmission) the mobile station, the target TDD configuration transmits the HARQ-ACK transmission in each subframe. Determine if it shows.

  According to an advantageous implementation, the other intermediate (i.e., 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 may be able to apply TDD configuration as an intermediate (ie, pre-defined) TDD configuration defining the timing relationship between PDSCH and HARQ-ACK, thereby providing a source TDD configuration. The hybrid ARQ function can always be used while transitioning from H.264 to the target TDD configuration.

  According to an advantageous implementation of the third embodiment, another intermediate (ie predefined) TDD configuration is 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 two preceding radio frames is possible. Specifically, TDD configuration 5 relates to PDSCH transmission received by the mobile terminal in subframe 2, 13, 12, 9, 8, 7, 5, 4, 11, and 6 subframes respectively in subframe 2 Two HARQ-ACK transmissions can be combined.

  Referring to the example illustrated in FIG. 11B, TDD configuration 5 is applied to determine the timing relationship between PDSCH and HARQ-ACK for HARQ transmission between subframes 20 and 32 (shaded subframes in FIG. 11B). Please refer to). Specifically, TDD configuration 5 is applied to HARQ-ACK transmission in subframes 22 and 32, and TDD configuration 5 is PDSCH transmission that involves HARQ-ACK transmission after TDD UL / DL reconfiguration is enabled. (See the dashed arrow in FIG. 11B).

  In this regard, the third embodiment addresses the timing relationship between PDSCH and HARQ-ACK, ie, another intermediate (ie, pre-defined) TDD configuration, during a short period of time before reconfiguration becomes effective. Timing relationships can be adapted. As a result, it is possible to avoid PDSCH subframes in which HARQ-ACK is transmitted, and make it possible to always use the hybrid ARQ function.

First implementation

  According to the first implementation of the third embodiment, the other intermediate (ie, predefined) TDD configurations are no longer considered as static configurations of the communication system. Instead, other intermediate (i.e., predefined) TDD configurations applied to HARQ-ACK transmission during subframes N to N + 12 are signaled in the communication system.

  Specifically, information indicating a TDD configuration corresponding to another intermediate (ie, predefined) TDD configuration among the 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 proceeds to the other intermediate (ie, predefined) TDD configuration for subsequent TDD UL / DL retransmissions. It applies during the configuration, i.e. subframes N to N + 12, where subframe N denotes the subframe for which the reconstruction is valid from then on.

  Optionally, the information indicating other intermediate (ie, predefined) TDD configurations may be combined with the information indicating subframes from which communications in the communication system are to be reconstructed.

Second implementation

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

  Specifically, a plurality of HARQ-ACK transmissions are performed as a result of one PDSCH transmission, in which case the mobile terminal can transmit PDSCHs up to subframe N-1 whose source TDD configuration includes subframe N-1. It defines related HARQ-ACK transmissions, and determines that other intermediate (i.e., predefined) TDD configurations specify HARQ-ACK transmissions between subframes N to N + 12 related to the same PDSCH transmission.

  According to a second implementation, the mobile station additionally determines, for one PDSCH transmission, which of a plurality of possible HARQ-ACK transmissions should be performed. More specifically, in response to one PDSCH transmission, application of the source TDD configuration defines HARQ-ACK transmission up to subframe N-1, which includes subframe N-1 pertaining to that PDSCH transmission; The mobile node includes subframe N-1 if application of an intermediate (ie, pre-defined) TDD configuration to define HARQ-ACK transmission during subframes N to N + 12 related to that PDSCH transmission. Only the HARQ-ACK transmission up to subframe N-1 is performed, or the mobile node only performs the HARQ-ACK transmission during subframes N to N + 12.

  Specifically, when the mobile terminal performs only HARQ-ACK transmission up to subframe N-1 including subframe N-1, the delay related to HARQ-ACK feedback can be reduced. Furthermore, the payload resulting from HARQ-ACK transmission during subframes N to N + 12 can be reduced.

  According to an advantageous variation of the second implementation, when multiple HARQ-ACK transmissions are performed for one PDSCH transmission, the mobile station may transmit HARQ-ACK up to subframe N-1 including subframe N-1. It will transmit and additionally perform HARQ-ACK transmission including predefined information, eg discontinuous transmission (DTX) information, 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, which includes subframe N-1 pertaining to that PDSCH transmission; The mobile node includes subframe N-1 if application of an intermediate (ie, pre-defined) TDD configuration to define HARQ-ACK transmission during subframes N to N + 12 related to that PDSCH transmission. HARQ-ACK transmission is performed up to subframe N-1, 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 (i.e. predefined) TDD configurations, but this HARQ-ACK transmission is for PDSCH transmissions. It relates to a preceding subframe that has never been reserved.

  As already described in detail with respect to the third embodiment, applying other intermediate (ie, predefined) TDD configurations, for each of the previously performed PDSCH transmissions, subframe N to It is determined whether HARQ-ACK transmission should be performed during N + 12. This is separate from the TDD radio frame configuration specified in the source TDD configuration up to subframe N-1 including subframe N-1, and the TDD radio frame configuration specified in the target TDD configuration for subframe N and subsequent To be done.

  In other words, the other intermediate (ie, pre-defined) TDD configurations reflect different TDD radio frame configurations, and different (ie more) PDSCH transmissions from the subframes actually reserved in the source TDD configuration. Indicate a subframe of trust.

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

  Advantageously, pre-defined information may indicate that the at least one sub-frame only supports uplink transmission and is not relevant 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.

  With the distribution of the information, the communication between the mobile station and the base station is reconfigured for a given subframe N, which is at the beginning of the radio frame.

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

  Advantageously, the information informing the reconstruction is only moved if it is distributed within the interval from subframe N-14 to subframe N-5 (including subframe N-14 and subframe N-5) As considered by the station and / or the base station, subframe N indicates when the reconfiguration is valid. In order to reduce the risk of the mobile station accidentally detecting and applying a reconfiguration, a reconfiguration may also be indicated if and only if information notifying the reconfiguration has been detected more than once, for example twice, during said interval. It is further advantageous for the UE to apply reconfiguration only if is the same at multiple times. For example, if the probability of erroneously detecting one piece of reconstruction information is 1%, the probability of erroneously detecting one piece of reconstruction information will be 0.01%. These approaches are particularly useful when the reconstruction is signaled by an explicit message, ie a signal containing at least the target configuration as information.

  An alternative method to determine the reconfiguration more implicitly is uplink transmission or uplink for PUSCH according to uplink subframe timing according to source UL / DL configuration (or UL / DL configuration indicated by SIB1) It is to check that resource allocation does not exist (or is lacking). For example, referring to FIGS. 5 and 7, the following table shows how a lack of PUSCH assignment for subframe j can indicate a reconfiguration to a target TDD configuration according to the source TDD configuration. 1 shows a preferred embodiment. In the advanced method, the reconstruction is determined only by the lack of PUSCH assignment 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. The additional lack of PUSCH assignment for subframe 4 of the same radio frame does not further change the target configuration.

Fourth embodiment

  According to a fourth embodiment, the inventive concept also applies to the transmission power control (TPC) command signaling. TPC commands are distributed within the communication system to indicate the transmit power to be used at the mobile station. Thus, upon receiving a TPC command, the mobile station considers the value sent in that command for future uplink transmissions.

  In 3GPP LTE, TPC commands are specified to indicate only the differential power variation of the transmit power performed by the mobile terminal. For example, the TPC command may instruct the mobile terminal to increase the transmit power by a value included in the command or to decrease the transmit power by another value included in the command. In this regard, continuously signaling TPC commands improves the flexibility of the 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, based on the received TPC command, the mobile terminal calculates the transmission power of each subframe before actual uplink transmission. Thus, permanently, one or more TPC commands are received and the transmission power is evaluated by the mobile terminal on a per subframe basis.

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

  The PUSCH TPC command is included in DCI transmission carrying UL grant or DCI transmission of transmission power control (TPC) command. The DCI transmission including the PUSCH TPC command is in format 0/4 or format 3 / 3A and corresponds to the DCI transmission related to PUSCH transmission discussed in relation to the first and second embodiments. Nevertheless, different timing relationships are defined as the PUSCH TPC commands can also be received and processed as part of PUSCH power control via DCI transmission without scheduling the PUSCH, such as by DCI formats 3 and 3A.

  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 a part of PUSCH power control. As a part, the timing relationship between the transmission of the PUSCH TPC command and its processing is defined. 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 previous TPC commands corresponding to PUSCH transmission up to subframe ik including subframe ik. In other words, subframe number i shown in Table 5.1.1.1-1 corresponds to PUSCH transmission received k subframes earlier than subframe i of which number 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 between the mobile terminal and the base station It can be done separately when reconfiguring communication or it can be combined with any of the above embodiments.

  According to one variation, it is assumed that the mobile station communicates with the base station in the communication system. Communication is reconfigured from a source TDD configuration to a target TDD configuration. Further, the source TDD configuration is one of a subset of multiple TDD configurations, and the target TDD configuration is any one of the multiple 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 in accordance with the TPC command of PUSCH transmission according to the following scheme.

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

  According to another variation, it is again assumed that the mobile station communicates with the base station in the communication system. Communication is reconfigured from a source TDD configuration to a 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 in accordance with the TPC command of PUSCH transmission according to the following scheme.

  First, the source TDD configuration is applied to perform PUSCH power control on subframes related to TPC commands corresponding to PUSCH transmission received up to subframe N including subframe N. Then, apply a target TDD configuration to perform PUSCH power control on subframes related to TPC commands corresponding to PUSCH transmission received after subframe N + 1. Advantageously, the source TDD configuration is TDD configuration 0.

  According to a further variation, it is again assumed that the mobile station communicates with the base station in the communication system. Communication is reconfigured from a source TDD configuration to a target TDD configuration. Furthermore, the source and target TDD configurations are any TDD configurations of multiple 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 power control adjustment of PUSCH transmission according to the TPC command of PUSCH transmission according to the following scheme.

  First, the source TDD configuration is applied to perform PUSCH power control on subframes related to TPC commands corresponding to PUSCH transmission received up to subframe N including subframe N. Then, apply a target TDD configuration to perform PUSCH power control on subframes related to TPC commands corresponding to PUSCH transmission 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 up to subframe N + 1 including subframe N + 1, the source TDD configuration is applied, and in which subframe the corresponding TPC command is included judge. Then, apply an intermediate (ie, predefined) TDD configuration to perform power control adjustments for PUSCH transmissions in subframes N + 2 to N + 4, and in which subframe is the corresponding TPC command included? Determine Finally, in order to make power control adjustments for PUSCH transmission in subframe N + 5 and beyond, the target TDD configuration is applied to determine which subframe contains the corresponding TPC command. Alternatively, the last subframe in which the source TDD configuration is applied may be N-1 or N, and the first subframe in which the intermediate (ie, predefined) TDD configuration is applied is N or N + 1 respectively It may be. The intermediate (ie, pre-defined) TDD configuration is one of the plurality of TDD configurations. Advantageously, the intermediate (ie predefined) TDD configuration is different from the source TDD configuration, preferably TDD configuration 6.

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

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

  In this regard, in order to enable continuous PUCCH power control at the mobile terminal during TDD UL / DL reconfiguration, the same considerations as in the above embodiment are reflected in the following mechanism, which comprises the mobile terminal and the base station Can be done separately when reconfiguring the communication between the two or can be combined with any of the above embodiments.

  According to yet another variation, it is assumed that the mobile station communicates with the base station in the communication system. Communication is reconfigured from a source TDD configuration to a 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 given subframe N at the beginning of a radio frame, the mobile station performs PUCCH power control in response 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 by subframe N-1 including subframe N-1. In order to perform PUCCH power control during subframes N to N + 12, apply another intermediate (ie, predefined) TDD configuration. Finally, the target TDD configuration is applied to perform PUCCH power control in subframe N + 13 and later. Here, the other intermediate (ie, pre-defined) TDD configuration is one of the plurality of TDD configurations. Advantageously, the intermediate (ie predefined) TDD configuration is different from the target TDD configuration, preferably TDD configuration 5.

Hardware and software implementation of the invention

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

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

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

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

  It will be understood by those skilled in the art that various changes and / or modifications can be made to the present invention shown in the specific embodiments without departing from the broad concept or scope of the present invention. It will be understood. Accordingly, the embodiments set forth herein are considered in all respects to be illustrative and not restrictive.

Claims (14)

A base station communicating with a mobile 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 plurality of uplink / downlink configuration subsets, and the target uplink / downlink configuration is one of the plurality of uplink / downlink configurations. The plurality of uplink / downlink configurations are pre-configured for time division duplex (TDD) communication;
The base station is
A transmitter for transmitting to the mobile station downlink control information (DCI) transmission, which reconstructs the communication for a predetermined subframe N at the beginning of a radio frame;
The physical uplink shared channel (PUSCH) transmission relating to the DCI transmission received by the mobile station by the subframe N-6 comprising the subframe N-6 in response to the DCI transmission, the source uplink // The downlink configuration is applied and
A predefined uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmissions received by the mobile station during subframes N-5 to N-1,
The target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmissions received by the mobile station after subframe N,
A receiver unit for receiving PUSCH transmissions;
The predefined uplink / downlink configuration is one of the plurality of uplink / downlink configurations,
base station. The predefined uplink / downlink configuration is different from the source uplink / downlink configuration,
The base station 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 base station according to claim 1 or 2. A base station communicating with a mobile 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 plurality of uplink / downlink configurations, and the target uplink / downlink configuration is one of the plurality of uplink / downlink configurations. The plurality of uplink / downlink configurations are pre-configured for time division duplex (TDD) communication,
The base station is
A transmitter for transmitting to the mobile station downlink control information (DCI) transmission, which reconstructs the communication for a predetermined subframe N at the beginning of a radio frame;
The physical uplink shared channel (PUSCH) transmission relating to the DCI transmission received by the mobile station by the subframe N-1 comprising the subframe N-1 in response to the DCI transmission, said source uplink // The downlink configuration is applied and
The target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmissions received by the mobile station after subframe N,
A receiver unit for receiving PUSCH transmissions;
base station. The plurality of uplink / downlink configurations are uplink / downlink configurations 0-6,
The source uplink / downlink configuration is uplink / downlink configuration 0,
The base station according to claim 4. The plurality of uplink / downlink configurations each determine a timing offset between the DCI transmission and the corresponding PUSCH transmission,
The base station according to any one of claims 1 to 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 Indicate whether it is a special subframe that supports both the downlink transmission and the uplink transmission, or
The target uplink / downlink configuration indicates whether each subframe after subframe N is the downlink subframe, the uplink subframe, or the special subframe.
The base station according to any one of claims 1 to 6. Information indicating that communication between the mobile station and the base station should be reconfigured is distributed in the communication system, and the information includes subframes N-14 to N including subframe N-5. When distributed within an interval up to -5, distribution of the information reconfigures the communication for the given subframe N, where N is the subframe at the beginning of the radio frame,
The base station according to any one of claims 1 to 7. The mobile station is responsive to a physical downlink shared channel (PDSCH) transmission,
The source uplink / downlink configuration is applied to the hybrid ARQ-ACK transmission up to subframe N-1 including subframe N-1,
For hybrid ARQ-ACK transmission during subframes N to N + 12 apply another predefined uplink / downlink configuration,
The target uplink / downlink configuration is applied to hybrid ARQ-ACK transmission after subframe N + 13,
Perform hybrid ARQ-ACK transmission,
The another predefined uplink / downlink configuration is one of the plurality of uplink / downlink configurations,
The base station according to any one of claims 1 to 8. The further predefined uplink / downlink configuration is different from the target uplink / downlink configuration,
The base station according to claim 9. Said another predefined uplink / downlink configuration is an uplink / downlink configuration 5,
A base station according to claim 9 or 10. Information indicating which of the plurality of uplink / downlink configurations correspond to the other predefined uplink / downlink configurations applied to hybrid ARQ-ACK transmission during subframe N to N + 12 Are distributed within the communication system,
The base station according to any one of claims 9 to 11. The plurality of uplink / downlink configurations each determine a timing offset between the PDSCH transmission and a corresponding hybrid ARQ-ACK transmission,
The base station according to any one of claims 9 to 12. A method performed by a base station communicating with a mobile 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 plurality of uplink / downlink configuration subsets, and the target uplink / downlink configuration is one of the plurality of uplink / downlink configurations. The plurality of uplink / downlink configurations are pre-configured for time division duplex (TDD) communication;
The method is
Transmitting to the mobile station downlink control information (DCI) transmission, which reconstructs the communication for a given subframe N at the beginning of a radio frame;
The physical uplink shared channel (PUSCH) transmission relating to the DCI transmission received by the mobile station by the subframe N-6 comprising the subframe N-6 in response to the DCI transmission, the source uplink // The downlink configuration is applied and
A predefined uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmissions received by the mobile station during subframes N-5 to N-1,
The target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmissions received by the mobile station after subframe N,
Receive PUSCH transmission,
The predefined uplink / downlink configuration is one of the plurality of uplink / downlink configurations,
Method.