reduced delay harq process timeline for fdd-tdd carrier aggregation

专利摘要:
1/1 summary reduced delayed harq process timeline for fdd-tdd carrier aggregation. methods, systems and devices for multi-carrier programming in wireless communication networks. The described techniques may be employed to minimize the delay of hybrid auto repeat (harq) requests on a wireless communication network using one or more component tdd carriers and one or more component fdd carriers. udink (ul) and downlink (dl) tdd programming can be determined based on the fdd component carrier. Several harq processes can be determined for a tdd component carrier based on the dl / ul configuration of the tdd component carrier. programming may include overwriting certain harq transfers. The techniques described may apply to any Tdd dl / ul configuration.
公开号:BR112016006592A2
申请号:R112016006592
申请日:2014-09-26
公开日:2020-05-12
发明作者:Damnjanovic Jelena；Gaal Peter；Chen Wanshi
申请人:Qualcomm Inc；
IPC主号:

专利说明:

HARQ PROCESS TIME LINE WITH REDUCED DELAY TO
AGGREGATION OF FDD-TDD CARRIER.
CROSS REFERENCES
[0001] This Patent Application claims the priority of US Patent Application No. 14 / 497,268 by Gaal et al., Entitled Reduced Delay HARQ Process Timeline For FDD-TDD Carrier Aggregation, filed on September 25, 2014, and Application US Provisional Patent No. 61 / 883,173 by Gaal et al., entitled Reduced Delay HARQ Process Timeline For FDD-TDD Carrier Aggregation, filed on September 26, 2013, each of which is assigned to the assignee of the present invention.
BACKGROUND
[0002] Wireless communication systems are widely used to provide various telecommunications services, such as voice, video, packet data, messages, transmissions, and the like. These wireless networks can be multiple access networks capable of supporting multiple users by sharing available network resources.
[0003] A wireless communication network can include multiple base stations that can support communication to multiple mobile devices. A mobile device can communicate with a base station through downlink (DL) and uplink (UL) transmissions. The downlink (or direct link) refers to the communication link from the base station to the mobile device, and uplink (or reverse link) refers to the communication link from the mobile device to the base station.
[0004] Multiple access technologies can use Frequency Division Duplexing (FDD) or Time Division Duplexing (TDD) to provide uplink and downlink communications over one or more
2/54 carriers. TDD operation offers flexible implementations without the need for paired spectrum resources. TDD formats include transmission of data frames, each including a number of different subframes in which different subframes can be uplink or downlink subframes. In systems that operate using TDD, different formats can be used in which uplink and downlink communications can be asymmetric. The flexible TDD DL / UL configuration offers efficient ways to utilize unpaired spectrum resources and the TDD configuration can be adaptive based on traffic conditions (for example, UL / DL load at the base station or mobile device).
[0005] Wireless communication networks including base stations and UEs can support operation on multiple carriers, which can be called aggregation. Carrier aggregation can be used to increase throughput between a base station that supports multiple component carriers and a mobile device and mobile devices can be configured to communicate using multiple component carriers associated with multiple base stations. Other techniques for increasing throughput using multiple carriers can be used when base stations that perform joint operations have a non-ideal return transport channel (for example, dual connectivity, etc.).
[0006] In some cases, transmission errors between mobile devices and base stations are avoided or corrected by using an automatic repetition request (ARQ) scheme. An ARQ scheme can be used to detect whether an incoming packet is in error. For example, in an ARQ scheme, a receiver can notify a transmitter with a positive acknowledgment (ACK) when
3/54 a packet is received without errors; and the receiver can notify the transmitter with a negative acknowledgment (NAK) if an error is detected. In some cases, a hybrid ARQ (HARQ) scheme is used to correct some errors and to detect and discard some incorrigible packages. In some multi-carrier scenarios, however, the global HARQ delay can cause certain deficiencies in wireless communications.
SUMMARY
[0007] Methods, systems and devices that minimize HARQ delay for multi-carrier programming in a wireless communication network using one or more TDD component carriers and one or more FDD component carriers are described. The HARQ periodicity can be adjusted, and tools and techniques for programming the UL and DL TDD concessions and HARQ indicators can be employed.
[0008] A wireless communication method is described. The method may include determining a configuration for a set of component carriers in the carrier aggregation, the set of component carriers including a time division duplexing (TDD) secondary component carrier (SCC) and a division duplexing SCC frequency (FDD), identify a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based at least in part on a time duration of each TDD SCC frame and communication with a node with based at least in part on the identified programming timing and FDD SCC HARQ uplink timing.
[0009] Equipment for wireless communication is also described. The equipment may include a processor, memory in electronic communication with the
4/54 processor and instructions stored in memory. Instructions can be executable by the processor to determine a configuration for a set of component carriers in the carrier aggregation, the set of component carriers including a time division duplexing (TDD) secondary component carrier (SCC) and an SCC frequency division duplexing (FDD), identifying a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based at least in part on a time duration of each TDD SCC frame and communication with a node based at least in part on the identified programming timing and FDD SCC HARQ uplink timing.
[0010] An additional equipment for wireless communication is also described. The equipment may include means for determining a configuration for a set of component carriers in the carrier aggregation, the set of component carriers including a time division duplexing (TDD) secondary component carrier (SCC) and a duplexing SCC by frequency division (FDD), means to identify a schedule timing and a FDD SCC hybrid automatic repeat request (HARQ) timing based at least in part on a time duration of each TDD SCC frame and means for communication with a node based at least in part on the identified programming timing and FDD SCC HARQ uplink timing.
[0011] A non-transitory, computer-readable media is also described. The computer readable media non-transitory method may include code comprising instructions for determining a configuration
5/54 for a set of component carriers in carrier aggregation, the set of component carriers including a time division duplexing (TDD) secondary component carrier (SCC) and a frequency division duplexing SCC (FDD) ), identify a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based at least in part on a time duration of each TDD SCC frame and communication with a node based on at least part of the identified programming timing and FDD SCC HARQ uplink timing.
[0012] An additional method for wireless communication is also described. The method may include configuring a set of component carriers in the carrier aggregation to serve user equipment (UE), where the set of component carriers can include a time division duplexing (TDD) secondary component carrier (SCC) ) and a frequency division duplexing (FDD) SCC, determine a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based at least in part on a time frame of each frame in the TDD SCC and communication with the UE based at least in part on the determined schedule timing and FDD SCC HARQ uplink timing.
[0013] An additional equipment for wireless communication is also described. The equipment may include a processor, memory in electronic communication with the processor and instructions stored in memory. Instructions can be executable by the processor to configure a set of component carriers in the carrier aggregation, the set of component carriers including a secondary component carrier
6/54 (SCC) time division duplexing (TDD) and frequency division duplexing SCC (FDD), determine a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing with based at least in part on a time span of each TDD SCC frame and communicating with a node based at least in part on the identified programming timing and FDD SCC HARQ uplink timing.
[0014] An additional equipment for wireless communication is also described. The equipment may include means for configuring a set of component carriers in the carrier aggregation to serve a user equipment (UE), where the set of component carriers may include a time-division duplexing secondary component carrier (SCC) (TDD) and a frequency division duplexing (FDD) SCC, means for determining a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based at least in part on a length of time of each TDD SCC framework and means for communicating with the UE based at least in part on the determined schedule timing and FDD SCC HARQ uplink timing.
[0015] An additional non-transitory computer-readable media is described. Non-transitory computer-readable media may include code comprising instructions for configuring a set of component carriers in the carrier aggregation to serve a user device (UE), where the set of component carriers can include a secondary component carrier (SCC) ) time division duplexing (TDD) and frequency division duplexing SCC (FDD), determine a time delay
7/54 FDD SCC hybrid uplink automatic repeat (HARQ) request scheduling and timing based at least in part on a time duration of each TDD SCC frame and communication with the UE based at least in part on timing programming and timing of the FDD SCC HARQ uplink.
[0016] In some examples of the methods, equipment or computer-readable media described above, the length of time for each TDD SCC frame can
be ten (10) milliseconds. In some examples, the timing programming FDD SCC it's four (4) milliseconds.[0017] In some examples From methods, equipment or readable media per computer described above, the timing programming of FDD SCC Can be
a time difference between an uplink lease or physical hybrid indicator channel (PHICH) transmission and a physical uplink shared channel transmission (PUSCH), and the timing of the FDD SCC HARQ uplink can be a time difference between the PUSCH transmission and a subsequent PHICH transmission. In some examples, the set of component carriers further comprises a primary cell (PCC) for frequency division duplexing (FDD). FDD SCC can be programmed cross carrier from TDD SCC. Additionally or alternatively, the TDD SCC may include a downlink-uplink configuration (DL / UL) selected from a plurality of DL / UL configurations.
[0018] Some examples of the computer-readable method, apparatus or media described above still include features of, means for, or instructions for indicating the configuration of the set of component carriers for the
8/54
UE through radio resource control (RRC) signaling.
[0019] The foregoing considerations outlined the features and technical advantages of the examples according to the disclosure quite broadly, so that the following detailed description can be better understood. An additional scope of the applicability of the described methods and equipment will be evident from the following detailed description, claims and drawings. The detailed description and specific examples are given by way of illustration only, since various changes and modifications within the spirit and scope of the description, will be evident to those skilled in the art.
BRIEF DESCRIPTION OF THE DRAWINGS
[0020] A further understanding of the nature and advantages of the present invention can be realized by reference to the following drawings. In the attached figures, components or similar resources may have the same reference label. In addition, several components of the same type can be distinguished, following the reference label by a dash and a second label that distinguishes between similar components. If only the first reference label is used in the specification, the description applies to any similar component with the same first reference label regardless of the second reference label.
[0021] FIG. 1 shows a diagram illustrating an example of a wireless communication system;
[0022] FIG. 2 shows a frame structure for a TDD carrier;
[0023] FIG. 3 shows a system that employs carrier aggregation;
9/54
[0024] FIGS. 4A and 4B show a device (s) configured for multi-carrier programming;
[0025] FIG. 5 shows a block diagram of a MIMO communication system;
[0026] FIG. 6 shows a block diagram of a user equipment configured for multi-carrier programming;
[0027] FIG. 7 shows a system configured for multi-carrier programming;
[0028] FIGS. 8A-8E show multi-carrier programming diagrams;
[0029] FIG. 9 shows a flow chart in one method (s) programming in multi-carrier; [0030] FIG. 10 shows a flow chart in one method (s) programming in multi-carrier; [0031] FIG. 11 shows a flow chart in one method (s) programming in multi-carrier; [0032] FIG. 12 shows a flow chart in one method (s) programming in multi-carrier; and [0033] FIG. 13 shows a flow chart in one method (s) programming in multi-carrier.
DETAILED DESCRIPTION
[0034] The examples described are intended for methods, systems and devices that minimize HARQ delay for multi-carrier programming on a wireless communication network using one or more TDD component carriers and one or more FDD component carriers . The methods, systems and devices include tools and techniques to adjust the HARQ periodicity that schedules the TDD UL and DL transmission, grants and transfers to minimize the round-trip delay (RTT) of the HARQ process.
10/54
[0035] The techniques described here can be used for various wireless communication systems such as cellular wireless systems, wireless peer communication, wireless local area access networks (WLANs), ad-hoc networks, satellite communication systems and other systems. The terms system and network are often used interchangeably. These wireless communication systems can employ a variety of radio communication technologies, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA ( OFDM), Single Carrier FDMA (SC -FDMA), or other radio technologies. Wireless communications are generally conducted in accordance with a standardized implementation of one or more radio communication technologies called Radio Access Technology (RAT). A wireless communications system or network that implements a Radio Access Technology can be called a Radio Access Network (RAN).
[0036] Examples of Radio Access Technologies that employ CDMA techniques include CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Versions 0 and A are commonly referred to as CDMA2000 IX, IX, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 lxEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Broadband CDMA (WCDMA) and other CDMA variants. Examples of TDMA systems include several implementations of the Global System for Mobile Communication (GSM). Examples of Radio Access Technologies that employ OFDM or OFDMA include Ultra Mobile Broadband (UMB), Evolved UTRA (EUTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the System
11/54 Universal Mobile Telecommunication (UMTS). Long Term Evolution of 3GPP (LTE) and Advanced LTE (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization called Partnership Project 3 Generation (3GPP). CDMA2000 and UMB are described in documents from an organization called Partnership Project 3 Generation 2 (3GPP2). The techniques described here can be used for the radio systems and technologies mentioned above as well as other radio systems and technologies.
[0037] Thus, the description below provides examples and is not limiting the scope, applicability or configuration presented in the claims. Changes can be made to the function and arrangement of the elements discussed, without departing from the spirit and scope of the revelation. Various modalities may omit, replace, or add various procedures or components, as appropriate. For example, the methods described can be performed in a different order than described, and several steps can be added, omitted or combined. In addition, the features described in relation to certain modalities can be combined in other modalities.
[0038] With reference to FIG. 1, a diagram illustrates an example of a wireless communication system 100. System 100 includes base stations (or cells) 105, communication devices 115 and a core network 130. Base stations 105 can communicate with communication devices 115 under the control of a base station controller (not shown), which can be part of core network 130 or base stations 105 in various embodiments. Base stations 105 can communicate control information and user data to central network 130 via links
12/54 of the return transport channel 132. The return transport channel links 132 can be wired return transport channel links (for example, copper, fiber, etc.) or return transport channel links wireless (eg microwave, etc.). In the embodiments, the base stations 105 can communicate, either directly or indirectly, with each other via return transport channel links 134, which can be wired or wireless communication links. System 100 can support operation on multiple carriers (waveform signals of different frequencies). Multi-port transmitters can simultaneously transmit modulated signals over multiple carriers. For example, each communication link 125 can be a multi-port signal modulated according to the various radio technologies described above. Each modulated signal can be sent on a different carrier and can carry control information (for example, reference signals, control channels, etc.), overhead information, data, etc.
[0039] Base stations 105 can communicate remotely with devices 115 through one or more antennas of the base station. Each of the base station 105 locations can provide communication coverage for a respective coverage area 110. In some embodiments, base stations 105 can be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a set of basic services (BSS), a set of extended services (ESS), a Node B, eNode B (eNB), NodeB Homemade, a eNode B Homemade, or some other suitable terminology. Coverage area 110 for a base station can be divided into sectors that constitute only a part of the coverage area (not shown). System 100 may include base stations 105 of
13/54 different types (for example, macro, micro, or pico base stations). There may be overlapping coverage areas for different technologies.
[0040] Communication devices 115 are dispersed throughout the wireless network 100, and each device can be stationary or mobile. A communication device 115 can also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, an appliance, a user agent, a user equipment, a customer mobile, a client, or some other appropriate terminology. A communication device 115 can be a cell phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a portable device, a tablet computer, a portable computer, a cordless phone, a station local wireless circuit (WLL), or similar. A communication device may be able to communicate with macro base stations, peak base stations, femto base stations, retransmission base stations, and the like.
[0041] Transmission links 125 shown on network 100 may include uplink (UL) transmissions from a mobile device 115 to a base station 105, or downlink (DL) transmissions from a base station 105 to a mobile device 115 Downlink streams can also be called direct link streams while uplink streams can also be called reverse link streams.
14/54
[0042] In the modalities, system 100 is an LTE / LTE-A network. In LTE / LTE-A networks, the terms Evolved Node B (ENB) and user equipment (UE) can generally be used to describe base stations 105 and communication devices 115, respectively. System 100 can be a heterogeneous LTE / LTE-A network in which different types of eNB provide coverage for different geographic regions. For example, each eNB 105 can provide communication coverage for a macro cell, a peak cell, a femto cell, or other types of cells. A macro cell usually covers a relatively large geographical area (for example, several kilometers in radius) and can allow unrestricted access by UEs with service subscriptions with the network provider. A peak cell usually covers a relatively smaller geographical area and can allow unrestricted access by UEs with service subscriptions with the network provider. A femto cell could also generally cover a relatively small geographical area (for example, a home) and, in addition to unrestricted access, it can also provide restricted access for UEs that have an association with the femto cell (for example, UEs of a closed subscriber group (CSG), UEs for users in the house, and so on). An eNB for a macro cell can be referred to as an eNB macro. An eNB for a cell peak can be referred to as an eNB peak. And an eNB for a femto cell can be referred to as a femto eNB or homemade eNB. An eNB can support one or more (for example, two, three, four and the like) cells.
[0043] Communication system 100 according to an LTE / LTE-A network architecture can be referred to as an Evolved Packet System (EPS) 100. EPS 100 can include one or more UEs 115, a Radio Access Network
15/54
Terrestrial UMTS Evolved (E-UTRAN), an Evolved Packet Core (EPC) 130 (for example, core network 130), a Home Subscriber Server (HSS), and an operator's IP Services. EPS can interconnect with other access networks that use other Radio Access Technologies. For example, EPS 100 can interconnect with a UTRAN-based network or a CDMA-based network through one or more Service GPRS Support Nodes (SGSN). To support mobility of UEs 115 or load balancing, EPS 100 can support handover of UEs 115 between a source eNB 105 and target eNB 105. EPS 100 can support intra-RAT handover between eNBs 105 or base stations of a same RAT (for example, other E-UTRAN networks) and inter-RAT handovers between eNBs or base stations of different RAT (for example, E-UTRAN for CDMA, etc.). EPS 100 can provide packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure can be extended to networks that provide circuit-switched services.
[0044] E-UTRAN may include eNBs 105 and may provide terminations of user plan and control plan protocol towards UEs 115. eNBs 105 may be connected to other eNBs 105 via a transport channel of return 134 (for example, an X2 interface and the like). ENBs 105 can provide an access point for EPC 130 for UEs 115. eNBs 105 can be connected via return transport channel links 132 (for example, an SI interface and the like) to EPC 130. Logical nodes with EPC 130 may include one or more Mobility Management Entities (MMEs), one or more Service Ports and one or more Packet Data Network Ports (PDN) (not shown). Generally, MME can
16/54 provide carrier and connection management. All user IP packets can be transferred through the Service Port, which in turn can be linked to the PDN port. The PDN Port can provide UE IP address allocation, as well as other functions. The PDN port can be connected to the Operator's IP networks and IP Services. Logical nodes can be implemented on separate physical nodes or one or more can be combined into a single physical node. Operator's IP networks / IP Services may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS), or a PS Streaming Service (PSS).
[0045] UEs 115 can be configured to communicate collaboratively with various eNBs 105 through, for example, Multiple Input Multiple Output (MIMO), Multi-Point Coordinated (CoMP) or other schemes. MIMO techniques use multiple antennas at base stations or multiple antennas in the UE to take advantage of multipath environments to transmit multiple data streams. CoMP includes techniques for dynamically coordinating transmission and reception across multiple eNBs to improve the overall quality of transmission to UEs, as well as increasing the network and spectrum usage. Generally, CoMP techniques use return transport channel links 132 or 134 for communication between base stations 105 to coordinate communications from the control plane and user plane to the UEs 115.
[0046] The communication networks that can accommodate some of the various modalities revealed may be packet-based networks that operate according to a layered protocol stack. At the user level, communications on the carrier or Packet Data Convergence Protocol (PDCP) layer can be based on
17/54
IP. A Radio Link Control (RLC) layer can perform packet segmentation and reassembly to communicate through logical channels. A Media Access Control (MAC) layer can perform priority management and multiplexing of logical channels in transport channels. The MAC layer can also use hybrid automatic retry request (HARQ) techniques to provide retransmission at the MAC layer to ensure reliable data transmission. In the control plane, the Radio Resource Control (RRC) protocol layer can provide for establishing, configuring, and maintaining an RRC connection between the UE and the network used for the user plan data. In the physical layer, transport channels can be mapped to Physical channels.
[0047] Physical downlink channels can include at least one of a physical downlink control channel (PDCCH) or enhanced PUCCH (PDCCH), a physical HARQ indicator channel (PHICH), and a shared physical downlink channel (PDSCH). Physical uplink channels can include at least one of a physical uplink control channel (PUCCH) and a shared physical uplink channel (PUSCH). The PDCCH can carry downlink control information (DCI), which can indicate data transmissions to the UEs in the PDSCH, as well as providing UL resource grants to UEs for the PUSCH. The UE can transmit the control information in the PUCCH in the resource blocks assigned in the control section. The UE can transmit only data or both data and the control information in the PUSCH in the resource blocks assigned in the data section.
[0048] LTE / LTE-A uses multiple access by orthogonal frequency division (OFDMA) on the downlink and multiple access by single carrier frequency division (SC-FDMA) on the uplink. One OFDMA or SC18 / 54 carrier
FDMA can be divided into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins or the like. Each subcarrier can be modulated with data. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can be dependent on the system's bandwidth. For example, K can be 72, 180, 300, 600, 900, or 1200, with a 15 kilohertz (kHz) subcarrier spacing for a corresponding system bandwidth (with guard range) of 1, 4, 3, 5, 10, 15 or 20 mega-hertz (MHz), respectively. The system bandwidth can also be divided into sub-bands. For example, a sub-band can span 1.08 MHz, and there can be 1, 2, 4, 8 or 16 sub-bands [0049] Carriers can transmit bidirectional communications using the FDD operation (for example, using spectrum resources paired) or TDD (for example, using unpaired spectrum resources). Frame structures for FDD (for example, frame type 1) and TDD (for example, frame type 2) can be defined. Time intervals can be expressed in multiples of a basic time unit = 1/30720000. Each frame structure can have a radio frame length T, = 307200 · T _s = 10 ms and can include two half frames or partitions of length 153680 · = 5 ms each. Each half frame can include five subframes of length 30720 T, = 1 ms.
[0050] LTE / LTE-A networks support HARQ Type II multi-process with a configurable number of independent HARQ processes. Each HARQ process waits to receive an acknowledgment (ACK) before transmitting a new data or transport block. LTE / LTE-A uses the
19/54 asynchronous HARQ transmission on the downlink and synchronous HARQ transmission on the uplink. In both asynchronous and synchronous HARQ, ACK / NAK information can be provided to a number of subframes after a DL or UL transmission. Generally, for FDD LTE / LTE-A carriers, the ACK / NAK information for a transmitted HARQ process is 4 subframes after a data transmission. In asynchronous HARQ, a DL or UL programmed for subsequent transmissions is not predetermined and the eNB provides instructions to the UE on which HARQ processes are transmitted in each subframe. For FDD synchronous HARQ, the UEs perform a second transmission of a particular HARQ process, a predetermined number of subframes after receiving a NAK. Generally, for FDD LTE / LTE-A carriers subsequent UL transmissions of the same HARQ process occur 4 subframes after receiving a NAK. For synchronous HARQ in the TDD, ACK / NAK information can be received in a subframe i associated with UL transmissions in a subframe i-k, where k can be defined according to the DL / UL configuration of the TDD. Subsequent transmissions of certain HARQ processes can be performed in a subframe n for a NAK received in a subframe n-k, where k can be defined according to the DL / UL configuration of the TDD.
[0051] FIG. 2 illustrates a frame structure 200 for a TDD carrier. For TDD frame structures, each subframe 210 can carry UL or DL traffic, and special subframes (S) 215 can be used to switch between DL to UL transmission. The allocation of UL and DL subframes within radio frames can be symmetrical or asymmetric and can be reconfigured semi-statically or dynamically. Special subframes 215 can carry some DL and UL traffic and may include
20/54 a Guard Period (GP) between DL and UL traffic. Switching from UL to DL traffic can be achieved by defining the timing advance in UEs without the use of special subframes or a guard period between UL and DL subframes. TDD configurations with switching periodicity equal to the frame period (eg 10 ms) or half the frame period (eg 5 ms) can be supported. For example, TDD frames can include one or more Special frames, and the period between Special frames determines the periodicity switching from DL point to UL from TDD to the frame.
[0052] For LTE / LTE-A, seven different DL / UL configurations of TDD are defined that provide between 40% and 90% of DL subframes as illustrated in Table 1.
Table 1: TDD configurations
settingsTDD Period(ms) Subframe 0 1 2 3 4 5 6 7 8 9 0 5 D s U U U D s U U U 1 5 D s u U D D s U U D 2 5 D s u D D D s U D D 3 10 D s u U U D D D D D 4 10 D s u U D D D D D D 5 10 D s u D D D D D D D 6 5 D s u U U D s U U D
[0053] Because some DL / UL configurations of
TDD has fewer UL subframes than DL subframes, several techniques can be used to transmit ACK / NAK information to an association set within a
21/54 PUCCH transmission in the uplink subframe. For example, grouping can be used to combine ACK / NAK information to reduce the amount of ACK / NAK information to be sent. The ACK / NAK grouping can combine the ACK / NAK information for a single bit which is defined as a recognition value (ACK) only if the ACK / NAK information for each subframe of the association set is an ACK. For example, the ACK / NAK information can be a binary 1 to represent the ACK and a binary 0 to represent a negative acknowledgment (NAK) for a specific subframe. ACK / NAK information can be grouped using a logical AND operation on the association set ACK / NAK bits. Grouping reduces the amount of information to be sent through the PDCCH and, therefore, increases the return efficiency of HARQ's ACK / NAK. Multiplexing can be used to transmit multiple bits of ACK / NAK information in an uplink subframe. For example, up to four ACK / NAK bits can be transmitted using the PUCCH lb format with channel selection.
[0054] Wireless network 100 can support multi-carrier operation, which can be referred to as carrier aggregation (CA) or multi-port operation. A carrier can also be referred to as a component carrier (CC), a layer, a channel, etc. The terms carrier, layer, CC and channel can be used interchangeably here. A carrier used for the downlink can be referred to as a downlink CC, and a carrier used for the uplink can be referred to as an uplink CC. A combination of a downlink CC and an uplink CC can be referred to as a cell. It is also possible to have a cell that consists of only one downlink CC. A UE 115 can be configured with multiple downlink CCs and one or more uplink CCs for aggregating the
22/54 carrier. Multilayer eNB 105 can be configured to support communication with more UEs through multiple CCs on the downlink and uplink. Thus, a UE 115 can receive data and control information on one or more downlink CCs from a multilayer eNB 105 or from several eNB 105 (for example, single or multilayer eNBs). The UE 115 can transmit data and control information on one or more uplink CCs to one or more eNB 105. Carrier aggregation can be used with both FDD and TDD component carriers. For the aggregation of the DL carrier, multiple ACK / NAK bits are returned when multiple DL transmissions occur in a subframe. Up to 22 ACK / NAK bits can be transmitted using the PUCCH 3 format for DL carrier aggregation.
[0055] FIG. 3 shows a system 300 that employs carrier aggregation according to various modalities. System 300 can illustrate aspects of system 100. System 300 can include one or more eNBs 105 that use one or more carriers of component 325 (CCi-CC _N ) to communicate with UEs 115. eNBs 105 can transmit information to UEs 115 through downlink channels on component 325 carriers. In addition, UEs 115 can transmit information to eNBs 105-a through reverse channels (uplink) on component 325 carriers. In the description of the various entities of the FIG. 3, as well as other figures associated with some of the disclosed modalities, for the purpose of explanation, the nomenclature associated with a 3GPP LTE or LTE-A wireless network is used. However, it should be considered that the system 300 can operate on other networks, such as, but not limited to, an OFDMA wireless network, a CDMA network, a 3GPP2 CDMA2000 network and the like. One or more of the CCi-CC _N 325 component carriers can be in the same band
23/54 frequency operating (intra-band) or in different operating bands (inter-band) and intra-band CCs can be contiguous or non-contiguous within the operating band.
[0056] In system 300, UEs 115 can be configured with multiple CCs associated with one or more eNBs 105. A CC is designed as the primary CC (PCC) for a UE 115. PCCs can be configured semi-statically by layers higher (for example, RRC, etc.) on a per EU basis. Certain uplink control information (UCI) (eg, ACK / NAK, channel quality information (CQI), programming requests (SR), etc.), when transmitted in PUCCH are loaded by the PCC. Thus, UL's SCC may not be used for PUCCH for a given UE. 115 UEs can be configured with asymmetric DL to UL CC assignments. In LTE / LTE-A, up to 5: 1 mapping is supported. Thus, a UL CC (eg, PCC UL) can load the UCIs (eg, ACK / NAK) in the PUCCH for up to 5 DL CCs.
[0057] In the example illustrated in FIG. 3, UE 115a is configured with PCC 325-a and SCC 325-b associated with eNB 105-a and SCC 325-c associated with eNB 105-b. System 300 can be configured to support carrier aggregation using various combinations of FDD and TDD CCs 325. For example, some system configurations 300 may support AC for FDD CCs (eg, an FDD PCC and one or more FDD SCCs). Other configurations may support AC using TDD CCs (eg, a TDD PCC and one or more TDD SCCs). In some examples, TDD to AC SCCs have the same DL / UL configuration while other examples support TDD AC with CCs of different DL / UL configurations.
[0058] In some modalities, the system 300 can support the joint operation of TDD-FDD, including CA and other types of joint operation (eg, connectivity
24/54 double when the eNBs 105 of the various CCs configured for an UE 115 have reduced return transport channel capacities, etc.). The joint operation of TDD-FDD can allow UEs 115 that support the operation of CA FDD and TDD to access both FDD and TDD CCs using AC or in single DC mode. In addition, legacy UEs with various capacities (eg, single-mode UEs, UEs capable of the FDD CA, UEs capable of the TDD CA, etc.) can connect to the FDD or TDD carriers of the 300 system.
[005 9] In CA scenarios that employ a TDD CC and an FDD CC, HARQ UL processes can follow a TDD timeline. In cases of cross-carrier programming using an FDD PCC, an UL HARQ process on a TDD SCC can follow the FDD PCC timeline. For example, in DL, a data transmission and corresponding concession to CC TDD can be sent in the same subframe. Then, an ACK / NAK for TDD DL data transmission can be sent four milliseconds (4 ms) later via the UL FDD PCC. At UL, a TDD UL transmission can be sent 4 ms after grant or a NAK at FDD PCC. Then, an ACK / NAK for the UL TDD subframe can be sent 4 ms later. Thus, programming can generally include 4 ms spaces between a lease, UL transmissions, and ACK / NACKs.
[0060] In some cases, the delay of the return can be minimized for the cross-carrier programming FDD PCC and TDD SCC by using the programming with these 4 ms spaces. In other cases, however, an FDD HARQ timeline aligns with a TDD SCC subframe timeline in such a way that the overall HARQ RTT is substantially larger than the FDD HARQ timeline. If, for example, an UL HARQ process with a periodicity of eight milliseconds (8 ms) is used with the
25/54
SCC TDD following the FDD PCC HARQ timeline, and the TDD SCC has a ten millisecond (10 ms) radio frame configuration, a retransmission of UL HARQ to a specific HARQ process can occur several frames after an initial transmission. As an example, in a cross-carrier scenario involving an FDD PCC with an 8 ms HARQ process, a TDC SCC using a DL-UL 5 configuration would perceive a forty millisecond (40 ms) HARQ retransmission RTT, if programmed according to the typical 4 ms FDD HARQ spacing described above.
[00 61] To minimize the HARQ RTT, a periodicity of the TDD SCC HARQ process with an FDD PCC can be adjusted to correspond to the periodicity of the subframe of a TDD SCC. UL transmissions and ACK / NAK transfers can be programmed accordingly.
[0062] A programming delay between a first uplink concession and a corresponding uplink transmission for the TDD SCC can be determined based on a programming delay of the FDD PCC. A number of HARQ UL processes can be determined based on a SCC TDD DL / UL configuration. Then UL transmissions and ACK / NAK transfers can be made according to the given programming timing and the given number of HARQ uplink processes. In some embodiments, a SCC TDD HARQ process timeline is adjusted such that the total number of subframes between data transmissions and corresponding ACK / NAK indicators, and the number of subframes between ACK / NAK indicators and retransmissions of the HARQ process corresponds to the number of subframes in a period of the SCC TDD framework. In some embodiments, the HARQ process timelines are adjusted for TDD SCC HARQ processes that are programmed for cross-carrier in the FDD PCC.
26/54
In other embodiments, the HARQ process timelines are adjusted for all HARQ processes including HARQ processes programmed at the FDD PCC.
[0063] In one embodiment, the programming timing for PCC FDD and CA SCC TDD together includes: sending a UL TDD 4 ms subframe after a PDCCH channel lease; receive an ACK / NAK (eg, PHICH), which can be sent 4 ms after the UL TDD subframe; and send a subsequent OL TDD subframe 6 ms after a NAK. Such HARQ rules can be applied to various TDD DL / UL configurations. In addition, the number of HARQ UL processes for a SCC TDD with a PCC FDD can be based on the DL / UL configuration of the SCC TDD.
[0064] Another programming delay can also lead to reductions in the HARQ delay. For example, a UL TDD subframe is sent 4 ms after a PDCCH lease, then a PHICH ACK / NAK is sent 6 ms after the UL TDD subframe, and a subsequent UL TDD subframe is sent 4 ms after a PHICH NAK.
[0065] In addition or alternatively, an ACK / NAK can be overwritten by a subsequent concession sent in the PDCCH. In some cases, a lease on the PDCCH sent two milliseconds (2 ms) (for example, 2 subframes) after an ACK / NAK can replace the ACK / NAK. For example, if the PHICH NAK is received in a current subframe, n, and a corresponding HARQ retransmission would be programmed for 6 ms later in the n + 6 subframe (as previously described), the HARQ retransmission can be replaced or overwritten when coincided with a UL transmission programmed by a PDCCH received in subframe n + 2 (also programmed to occur in subframe n + 6 due to the 4 ms spacing). In other modalities,
27/54 a concession sent in the same subframe as the ACK / NAK may override the ACK / NAK.
[0066] Returning to FIG. 4A, showing a block diagram 400 of a device 405 for multi-carrier programming according to various modalities. Device 405 can illustrate, for example, aspects of UEs 115 illustrated in FIG. 1 or FIG. 3. Additionally or alternatively, device 405 can illustrate aspects of the eNBs 105 described with reference to FIG. 1 or FIG. 3. Device 405 can include a receiver module 410, a multi-carrier programming module 415 and a transmitter module 420. Each of these components can be in communication with each other. In some embodiments, the 405 device is a processor.
[0067] The 405 device can be configured for operation in an AC scheme including a TDD CC and an FDD CC. In some cases, the multi-carrier programming module 415 is configured to determine, based on the PCC FDD, a programming time between a transfer from the control channel (eg, a lease on the PCC FDD's PDCCH or EPDCCH), and a corresponding UL transmission on a TDC SCC. The multi-carrier programming module 415 can also be configured to determine a number of UL HARQ processes for the TDD SCC based on a DL / UL configuration of the TDD SCC.
[0068] Receiver module 410 can receive a resource grant in the PDCCH, and transmitter module 420 can transmit a TDD UL subframe according to the grant. Receiver module 410 can also receive an ACK / NAK on the PDCCH and transmitter module 420 can transmit a subsequent TDD UL subframe in response to a received NAK. In some cases, the receiver module 410 may
28/54 receive a concession at the PDCCH that overwrites an ACK / NAK received earlier.
[0069] Next, FIG. 4B shows a block diagram 400-a of a device 405-a for multi-carrier programming according to various modalities. Device 405-a can illustrate, for example, aspects of UEs 115 illustrated in FIG. 1 or FIG. 3. In some cases, device 405-a illustrates aspects of the eNBs 105 described with reference to FIG. 1 or FIG. 3. Device 405 may include a receiver module 410-a, a multi-carrier programming module 415-a and a transmitter module 420-a. Each of these components can be in
communication one with the other; and each can accomplish substantially at same functions that the modules corresponding at FIG. 4A. According with some
modalities, the 405-a device is a processor.
[0070] The multi-channel programming module 415-a can be configured with a timing determination module 450, a HARQ determination module 460, a cross programming module 470, a time span determination module 480 , and a 490 override module. The modules, alone or in combination, can be a means to perform various functions described here. For example, the timing determination module can be configured to determine a schedule delay between a first control channel transfer and a corresponding uplink transmission to a TDD SCC based on the schedule delay to a FDD PCC. In some cases, the timing determination module 450 determines (eg, establishes or identifies) a 4 ms gap between a concession in the PDCCH and a corresponding UL transmission.
29/54
[0071] The HARQ determination module 4 60 can be configured to determine a number of uplink HARQ processes for a TDD CC based on a DL / UL configuration of the TDD CC. For example, the HARQ determination module 4660 can determine whether the HARQ uplink process number for the SCC TDD is equal to a number of uplink subframes in a SCC TDD frame. In some embodiments, a given number of UL subframes of a common UL HARQ process includes a space of ten milliseconds (10 ms).
[0072] Receiver module 410-a and transmitter module 420-a can receive and transmit control signals and data, respectively, according to the determined programming timing and the determined HARQ uplink processes.
[0073] In some modalities, the cross programming module 470 can be configured to cross program the component carriers, so that the DL / UL transmission in one DC is based on the concessions loaded by another CC. For example, UL transmissions from one TDC SCC may be based on concessions from another CC (eg, PCC FDD, etc.).
[0074] Timing space determination module 480 can be configured to determine a space between transfers of the HARQ indicator and UL transmissions. For example, the timing space determination module 480 can determine a timing space between a UL transmission and a corresponding ACK / NAK. In some cases, the time delay determined is 6 ms. In other modalities, the time delay determined is 4 ms. Additionally or alternatively, the timing space determination module 480 can be configured to determine a timing space between a NAK and a retransmission
Corresponding 30/54. For example, such a space can be 6ms, or it can be 4ms.
[0075] In some modalities, the overwrite module 490 is configured to overwrite an ACK / NAK with a subsequent or simultaneous concession, for example, in the PDCCH. The overwrite module 490 can be configured to overwrite an HARQ retransmission triggered by an ACK / NAK sent 2 ms or two subframes earlier, when it would coincide with a UL concession programmed by the PDCCH. In other cases, the overwrite module 490 is configured to overwrite an ACK / NAK sent in the same subframe.
[0076] The components of devices 405 and 405-a can, individually or collectively, be implemented with one or more integrated circuits of specific application (ASIC), adapted to perform some or all of the functions applicable in hardware. Alternatively, the functions can be performed by one or more other processing units (or cores), on one or more integrated circuits. In other modalities, other types of integrated circuits (for example, Structured / Platform ASICs, Field Programmable Door Arrangements (FPGAs) and other Semi-Customized ICs) can be used, which can be programmed in any manner known in the art. The functions of each unit can also be implemented, in whole or in part, with instructions incorporated in a memory, formatted to be executed by one or more general purpose or specific application processors.
[0077] FIG. 5 is a block diagram of a MIMO 500 communication system including a base station or eNB 105-c and a mobile device or UE 115-b. Base station 105-c can be an example of base stations 105 of FIG. 1 or FIG. 2, while the mobile device 115-b can
31/54 be an example of communication devices 115 of FIG. 1 or FIG. 3. System 500 can illustrate aspects of system 100 of FIG. 1 or system 300 or FIG. 3. Base station 105c can be equipped with M antennas 534-a to 534-x, and mobile device 115-b can be equipped with N antennas from 552-a to 552-y. In system 500, base station 105-c can employ multiple antenna techniques for transmission over communication links. For example, base station 105-c can employ transmission diversity to improve the robustness of transmissions received by mobile device 115b. The mobile device 115-b can employ diversity reception using multiple receiving antennas to combine signals received on multiple antennas.
[0078] At base station 105-c, a transmission processor (TX) 520 can receive data from a data source. The transmission processor 520 can process the data. The transmission processor 520 can also generate reference symbols, and a specific cell reference signal. A transmission processor (Tx) MIMO 530 can perform spatial processing (eg, precoding) on data symbols, control symbols or reference symbols, if applicable, and can provide output symbol streams to 532 transmission modulators -aa 532-m. Each modulator 532 can process a respective output symbol stream (eg, for OFDM, etc.) to obtain an output sample stream. Each 532 modulator can further process (eg, convert to analog, amplify, filter and overconvert) the output sample stream to obtain a downlink (DL) signal. In one example, DL signals from modulators 532-a to 532-m can be transmitted through antennas 534-a to 534-x, respectively.
32/54
[0079] In the mobile device 115-b, the antennas of the mobile device 552-a to 552-n can receive the DL signals from the base station 105-c and can provide the received signals to the demodulators 554-a to 554-n, respectively. Each demodulator 554 can condition (eg, filter, amplify, subconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 554 can further process the input samples (eg, for OFDM, etc.) to obtain received symbols. A MIMO 556 detector can obtain received symbols from all demodulators 554-a to 554-n, perform MIMO detection on received symbols if applicable, and provide the detected symbols. A receiving (Rx) 558 processor can process (eg, demodulate, deinterleave and decode) the detected symbols, providing decoded data to the mobile device 115-b for data output, and providing the decoded control information to a processor 580, or memory 582.
[0080] In the base station 105-c or the mobile device 115-b can use multi-port programming. By way of example, either processor 540 or processor 580, or both, can determine the number of HARQ processes and timelines of the HARQ process based on the CA FDD-TDD configuration. For example, the HARQ process timelines for HARQ processes using cross carrier programming can be adjusted to match the number of subframes in a SCC TDD frame. In some examples, the number of HARQ UL processes for SCC TDD processes can be determined based on a SCC TDD DL / UL configuration. Then UL transmissions and ACK / NAK transfers can be made according to the
33/54 determined programming timing and the determined number of uplink HARQ processes.
[0081] In the uplink (UL), in the mobile device 115-b, a transmission processor (Tx) 564 can receive and process data from a data source or a processor 540 coupled to memory 542. The transmission processor 564 can also generate reference symbols for reference signal. The symbols from the transmission processor 564 can be precoded by a transmission MIMO processor (Tx) 566 if applicable, further processed by demodulators 554-aa 554-n (eg, for SC-FDMA, etc.), and be transmitted to base station 105c according to the transmission parameters received from base station 105-c. At base station 105-c, UL signals from mobile device 115-b can be received by antennas 534, processed by demodulators 532, detected by a MIMO detector 536 if applicable, and further processed by a receiving processor (Rx) 538. The receiving processor 538 can provide decoded data to the data output and to the processor 540.
[0082] The components of the base station 105-c can, individually or collectively, be implemented with one or more Specific Application Integrated Circuits (ASIC) adapted to perform any or all of the functions applicable in hardware. Each of the observed modules can be a means to perform one or more functions related to the operation of the 1000 system. Similarly, the components of the mobile device 115-b can, individually or collectively, be implemented with one or more Application Integrated Circuits Specifies (ASIC) adapted to perform any or all functions applicable in hardware. Each of the observed components can be a means for
34/54 perform one or more functions related to system 1000 operation.
Turning now to
FIG.
a block diagram 600 of a mobile device 115-c configured for HARQ in CA FDD-TDD according to various modalities. The 115c mobile device can have any of several configurations, such as personal computers (eg, laptop computers, netbook computers, tablet computers, etc.), cell phones, PDAs, smartphones, digital video recorders (DVRs), internet equipment, game consoles, e-readers, etc. The mobile device 115-c may have an internal power supply (not shown), such as a small battery, to facilitate mobile operation. In some embodiments, the mobile device 115-c can be the mobile device 115 of FIG. 1, FIG. 3 or FIG. 5.
mobile device
115-c can generally include components for bidirectional data and voice communications including components for transmitting communications and components for receiving communications. The mobile device 115-c may include a transceiver module 610, antenna (s) 605, memory 680 and a processor module 670, which each can communicate, directly or indirectly, with each other (eg, through one or more buses 675). The 610 transceiver module can be configured to communicate bidirectionally, via antenna (s) 605 or one or more wired or wireless links, with one or more networks, as described above. For example, transceiver module 610 can be configured to communicate bidirectionally with base stations 105 of FIG. 1 or FIG. 3. The 610 transceiver module may include a modem configured to modulate the packets and deliver the modulated packets to the 605 antenna (s) for transmission, and
35/54 to demodulate packets received from antenna (s) 605. While mobile device 115-c may include a single antenna 605, mobile device 115-c may have multiple antennas 605 capable of simultaneously transmitting and receiving multiple transmissions wireless. The transceiver module 610 may be able to communicate simultaneously with multiple eNB 105 through multiple component carriers.
[0085] Memory 680 may include random access memory (RAM) and read-only memory (ROM). The 680 memory can store computer readable software / firmware code 685 computer executable containing instructions that are configured to, when executed, cause the 670 processor module to perform various functions described here (for example, call processing, database, handover delay capture, etc.). Alternatively, the software / firmware code 685 may not be directly executable by the 670 processor module, but may be configured to cause a computer (for example, when compiled and executed) to perform the functions described here.
[0086] The 670 processor module may include an intelligent hardware device, for example, a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), etc. The mobile device 115-c may include a speech encoder (not shown) configured to receive audio through a microphone, convert audio into packets (e.g., 20 ms long, 30 ms long, etc.) representative of the audio received, provide the audio packages for the 610 transceiver module and provide indications as to whether a user is speaking.
36/54
[0087] According to the architecture of Fig. 6, the mobile device 115-c can further include a multi-carrier programming module 415-b, which can be substantially the same as the multi-carrier programming devices 415 of FIGS. 4A and 4B. In some cases, the multi-carrier programming device 415-b is configured to perform the functions of one or more of modules 450, 460, 470, 480, or 490 of FIG. 4B. For example, the multi-carrier programming module 415-b may be a component of the mobile device 115-c communicating with some or all of the other components of the mobile device 115-c via a bus. Alternatively, the functionality of these modules can be implemented as a component of the 610 transceiver module, as a computer program product, or as one or more elements of the 670 processor module controller.
[0088] The mobile device 115-c can be configured to perform HARQ for CA FDD-TDD, as described above. The components for the mobile device 115-c can be configured to implement aspects discussed above with respect to the UEs 115 of FIG. 1 or FIG. 3 or devices 405 and 405-a of FIGS. 4A and 4B. For example, UE 115-c can be configured to determine, based on the CA FCC-TDD, a programming time between a transfer from the control channel (eg, a lease on the PDCCH or EPDCCH), and a corresponding UL transmission for a TDD SCC. The multi-carrier programming module 415 can also be configured to determine a UL HARQ process number for the UL TDD based on a DL / UL configuration of the TDD SCC.
[0089] FIG. 7 shows a block diagram of a communication system 700 that can be configured for multi-carrier programming according to various
37/54 modalities. This system 700 can be an example of the aspects of systems 100 or 300 illustrated in FIG. 1 or FIG. 3. System 700 includes a base station 105-d configured to communicate with UEs 115 via wireless communication links 125. Base station 105-d may be able to receive communication links 125 from other base stations ( not shown). The base station 105-d can be, for example, an eNB 105 as illustrated in systems 100 or 300.
[0090] In some cases, the 105-d base station may have one or more wired return transport channel links. Base station 105-d can, for example, be an eNB 105 macro that has a return transport channel link (e.g., SI interface, etc.) to core network 130-a. Base station 105-d can also communicate with other base stations 105, such as base station 105-m and base station 105-n via interstation base communication links (for example, interface X2, etc.). Each of the base stations 105 can communicate with UEs 115 using the same or different wireless communication technologies. In some cases, the base station 105-d can communicate with other base stations, such as 105-m and 105-n using the communication module of the base station 715. In some embodiments, the communication module of the base station 715 can provide a X2 interface within an LTE / LTE-A wireless network technology to provide communication between some of the base stations 105. In some embodiments, the base station 105-d can communicate with other base stations over the core network 130 um . In some cases, base station 105-d can communicate with core network 130-a via network communications module 765.
38/54
[0091] The components for the base station 105d can be configured to implement aspects discussed above with respect to the base stations 105 of FIG. 1 and FIG. 3 or devices 405 and 405-a of FIGS. 4A and 4B, and may not be repeated here for the sake of brevity. For example, base station 105-d can be configured to determine, based on the CA FCC-TDD, a programming time between a transfer from the control channel (eg, a lease on the PDCCH or EPDCCH), and a UL transmission corresponding to a TDD SCC. The 415 multi-carrier programming module can also be configured to determine a number of TDD UL UL HARQ processes based on a TDD SCC DL / UL configuration.
[0092] The base station 105-d may include antennas 745, transceiver modules 750, memory 770, and a processor module 7 60, which each may be in communication, directly or indirectly, with each other (for example, through 780 bus system). The transceiver modules 750 can be configured to communicate bidirectionally, via antennas 745, with UEs 115, which can be multimode devices. The transceiver module 750 (or other components of the base station 105-d) can also be configured to communicate bidirectionally, through antennas 745, with one or more other base stations (not shown). The transceiver module 750 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 745 for transmission, and to demodulate the packets received from the antennas 745. The base station 105-d may include several transceiver modules 750 each one with one or more associated antennas 745.
[0093] The 770 memory can include random access memory (RAM) and read-only memory (ROM). THE
39/54 memory 770 can also store computer-readable, computer-executable software code 775 containing instructions that are configured to, when executed, cause the 760 processor module to perform various functions described here (for example, call processing, management database, message routing, etc.). Alternatively, the 775 software may not be directly executable by the 760 processor module, but be configured to make the computer, for example, when compiled and run, perform the functions described here.
[0094] The processor module 760 may include an intelligent hardware device, for example, a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), etc. The 760 processor module can include several special-purpose processors, such as encoders, queue processing modules, baseband processors, radio head controllers, digital signal processors (DSPs), and the like.
[0095] According to the architecture of Fig. 7, the base station 105-d can also include a communication management module 740. The communications management module 740 can manage communications with other base stations 105. The communications management module can include a controller or programmer to control communications with UEs 115 in cooperation with other base stations 105. For example, the communications management module 740 can perform programming for transmissions to UEs 115 or various mitigation techniques interference, such as beam formation or joint transmission.
40/54
[0096] Additionally or alternatively, the base station 105-d may include a multi-carrier programming module 415-c, which can be configured in substantially the same manner as the devices 415 and 415-b of FIGS. 4A and 4B. In some cases, the multi-carrier programming device 415-c is configured to perform the functions of at least one of modules 450, 460,
470, 480, or 490 of FIG. 4B. In some modalities, the module of multi-programming -carrier 415-c it is a component gives season base 105-c in communication with some or all the others components base station 105-d through in one bus. Alternatively, the functionality of these modules of scheduling multi-
carrier 415-c can be implemented as a component of the transceiver module 750, as a computer program product, as one or more elements of the processor module controller 760, or as an element of the communication management module 740,
[0097] Turning now to FIGS. 8A, 8B, 80, 8D and 8E, which show CA FDD-TDD diagrams according to various modalities. FIG. 8A shows a set of CCs 800-a. CC-800s include a TDC SCC 805-a (with a DL / UL 5 configuration), an FDD DL PCC 810-a, and an FDD UL PCC 815-a. The TDC SCC 805-a has a 10 ms subframe 820-a configuration, and the FDD DL PCC 810-a has UL HARQ 825-a process identification. A grant can be transmitted, and a corresponding UL subframe sent, as shown with arrows 830-a. In 800-a, the FDD DL PCC 810-a has an UL HARQ periodicity of 8 ms. Thus, if a space of 4 ms is used between a TDD UL subframe and an ACK / NAK, a specific HARQ process can have an RTT of 40 ms.
41/54
[0098] FIG. 8B shows a set of CCs 800-
B. The CC-set 800-b includes a TDC SCC 805-b (with a DL / UL 5 configuration), an FDD DL PCC 810-b, and an FDD UL PCC 815-b. The SCC 805-b TDD has a 10 ms 820-b subframe configuration, and the FDD DL PCC 810-b has UL HARQ 825-b process identification. A grant can be sent, and a corresponding UL subframe transmitted, as shown with arrows 830-b. According to the present disclosure, FIG. 8B shows an adjustment for the SCC TDD HARQ timeline so that the number of HARQ processes is based on the SCC TDD DL / UL configuration. In 800-b, the SCC UL TDD 805-b has a 10 ms HARQ UL periodicity. In 800-a, a UL grant for every 10 ms is associated with HARQ UL processes 0, 2, 4, 6, 0.. etc. In 800-a, a UL grant for every 10 ms is associated with the HARQ UL 0 process. A space of 4 ms is used between a UL TDD subframe and an ACK / NAK. Thus, at 800-b, the HARQ retransmission to a specific HARQ process has a shorter delay than 800-a (eg, 10 ms instead of 40 ms).
[0099] FIG. 8C shows a set of 800-
ç. The CC-set 800-c includes a TDC SCC 805-c (with a DL / UL 0 configuration), an FDD DL PCC 810-c, and an FDD UL PCC 815-c. The TDC SCC 805-c has a 10 ms subframe 820-c configuration, and the FDD DL PCC 810-c has UL HARQ 825-c process identification. A grant can be sent, and a corresponding UL subframe transmitted, as shown with arrows 830-c. In 800-c, the TDD UL PCC 805-c has a UL HARQ periodicity of 10 ms. In 800-c, a UL grant for every 10 ms is associated with a fixed UL HARQ process 0, 1, 2, 3, 4 or 5. A space of 4 ms is used between a UL TDD subframe and an ACK / NAK. Thus, in 800-c, the HARQ relay to a HARQ process
42/54 has a lower delay than 800-a (eg, 10 ms instead of 40 ms).
[0100] FIG. 8C shows a set of CC 800-d. The CC 800-d set includes a TDC SCC 805-d (with a DL / UL 5 configuration), an FDD DL PCC 810-d, and an FDD UL PCC 815-d. The SCC 805-d TDD has a 10 ms 820-d subframe configuration, and the FDD DL PCC 810-d has UL HARQ 825-d process identification. A grant can be sent, and a corresponding UL subframe transmitted, as shown with arrows 830-d. In 800-d, the TDD UL PCC 805-d has a UL HARQ periodicity of 10 ms. A 6 ms gap is used between a UL TDD subframe and an ACK / NAK. At 800-d, the HARQ retransmission for a specific HARQ process has a shorter delay than 800-a (eg, 10 ms instead of 40 ms).
[0101] FIG. 8E shows a set of CCs 800e. The set of CCs 800-e includes a TDD SCC 805-e (with a DL / UL 0 configuration), an FDD DL PCC 810-e, and an FDD UL PCC 815-e. The TDC SCC 805-e has a 10 ms subframe 820-e configuration, and the FDD DL PCC 810-e has UL HARQ 825-e process identification. A grant can be sent, and a corresponding UL subframe transmitted, as shown with arrows 830-e. In 800-e, the TDD UL PCC 805-e has a UL HARQ periodicity of 10 ms. A 6 ms gap is used between a UL TDD subframe and an ACK / NAK. At 800-e, the HARQ retransmission for a specific HARQ process has a shorter delay than 800-a (eg, 10 ms instead of 40 ms).
[0102] Those skilled in the art will recognize that the above programming delay (eg, a UL TDD subframe sent 4 ms after a lease, ACK / NAK sent 6 ms after the UL TDD subframe, and a subsequent UL TDD subframe sent 4 ms after a NAK; or a UL subframe
43/54
TDD sent 4 ms after a lease, ACK / NAK sent 4 ms after the UL TDD subframe, and a subsequent UL TDD subframe sent 6 ms after a NAK) can be applied to any DL / UL configuration, and can result in an HARQ delay 10 ms when the HARQ UL periodicity corresponds to the SCC TDD subframe configuration.
[0103] In some embodiments, the number of UL HARQ processes equals the number of UL subframes in a frame based on the DL / UL configuration. Table 2 shows the number of HARQ UL processes for each SCC TDD DL / UL configuration.
Table 2: UL HARQ Processes by TDD DL / UL Configuration
Configuration NumberUL ProcessesHARQ TDDDL / UL SCC 0 6 1 4 2 2 3 3 4 2 5 1 6 5
[0104] According to some modalities, for the DL, a concession and a data transmission are in the same subframe and the asynchronous HARQ is employed. In such cases, no strict HARQ DL timeline or periodicity is defined. But in some cases, a number of HARQ DL processes can be defined. For example, the number of HARQ processes can be defined in such a way that the same HARQ process can be reused in a first available DL subframe separated by at least eight
44/54 milliseconds (8 ms) from the previous transmission of the same HARQ process. Table 3 shows the number of HARQ DL processes for each SCC TDD DL / UL configuration for such cases.
Table 3: DL HARQ Processes by TDD DL / UL Configuration
Configuration Number of ProcessesHARQ DL TDDDL / UL SCC0 4 1 6 2 7 3 7 4 8 5 8 6 56 * or
* For some modalities, such as those that employ the soft buffer division of LTE Version 8.
[0105] Next, FIG. 9 shows a flow chart of a 900 method for performing HARQ for CA FDDTDD according to various modalities. Method 900 can be implemented by base stations 105 and UEs 115 of FIG. 1, FIG. 3, FIG. 5, FIG. 6 or FIG. 7 or by the devices 405 and 405-a of FIGS. 4A and 4B.
[0106] In block 905, the method may include determining a programming delay between a first control channel transfer and a corresponding uplink transmission to a TDD CC based on the programming delay to a FDD CC. Operations in block 905 can, in some modalities, be performed by multi-carrier programming modules
45/54
415 of FIGS. 4A, 4B, 6, or 7 or by the timing determination module 450 of FIG. 4B. The programming delay can be 4 ms. In some modalities, the TDD CC is a SCC and the FDD CC is a PCC. The transfer of the control channel can be a resource grant in the PDCCH or EPDCCH.
[0107] In block 910, the method may involve determining a number of UL HARQ processes for the TD TD CC based on a DL TD UL UL configuration. The operations in block 910 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the HARQ determination module 470 of FIG. 4B. In some embodiments, the determined number of uplink subframes of a common UL HARQ process includes 10 ms.
[0108] In block 915, the method can include communication based on the timing of the determined schedule and the determined number of HARQ uplink processes. The operations in block 915 are, in various modalities, performed by the receiver modules 410 of FIGS. 4A or 4B, the transmitter modules 420 of FIGS. 4A or 4B, the transceiver modules 610 of FIG. 6, or the transceiver modules 750 of FIG. 7.
[0109] Next, FIG. 10 illustrates a flow chart of a method 1000 to perform HARQ in CA FDDTDD according to various modalities. Method 1000 can be implemented by base stations 105 and UEs 115 of FIG. 1, FIG. 3, FIG. 5, FIG. 6 or FIG. 7 or by the devices 405 and 405-a of FIGS. 4A and 4B.
[0110] In block 1005, the method can include determining a programming delay between a first control channel transfer and a corresponding uplink transmission to a TDD CC based on the programming delay to a FDD CC. At
46/54 operations in block 1005 can, in some modalities, be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the timing determination module 450 of FIG. 4B.
[0111] In block 1010, the method may involve determining a number of UL HARQ processes for the TDD CC based on a DL / UL configuration of the TDD CC. The operations in block 1010 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the HARQ determination module 470 of FIG. 4B.
[0112] In block 1015, the method can include communication based on the timing of the determined schedule and the determined number of HARQ uplink processes. The operations in block 1015 are, in various modalities, performed by the receiver modules 410 of FIGS. 4A or 4B, the transmitter modules 420 of FIGS. 4A or 4B, the transceiver modules 610 of FIG. 6, or the transceiver modules 750 of FIG. 7.
[0113] In block 1020, the method may include the transmissions of cross carrier programming on the TDD CC from the FDD CC. The operations in block 1020 are, in some cases, performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the cross-programming module 470 of FIG. 4B.
[0114] FIG. 11 shows a flow chart of a 1100 method for multi-carrier programming according to various modalities. Method 1100 can be implemented by base stations 105 and UEs 115 of FIG. 1, FIG. 3, FIG. 5, FIG. 6 or FIG. 7 or by the devices 405 and 405-a of FIGS. 4A and 4B.
[0115] In block 1105, the method may include determining a programming delay between a first control channel transfer and a
47/54 corresponding uplink transmission to a TDD CC based on the programming timing for a CC FDD. The operations in block 1105 can, in some modalities, be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the timing determination module 450 of FIG. 4B.
[0116] In block 1110, the method may involve determining a number of UL HARQ processes for the DC TDD based on a DL / UL configuration of the TDD CC. The operations in block 1110 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the HARQ determination module 470 of FIG. 4B.
[0117] In block 1115, the method can include communication based on the timing of the determined schedule and the determined number of HARQ uplink processes. The operations in block 1115 are, in various modalities, performed by the receiver modules 410 of FIGS. 4A or 4B, the transmitter modules 420 of FIGS. 4A or 4B, the transceiver modules 610 of FIG. 6, or the transceiver modules 750 of FIG. 7.
[0118] In block 1120, the method may involve determining a first timing space between a first UL shared channel transmission and a corresponding HARQ indicator channel transfer (eg, an ACK / NAK). The operations in block 1120 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the time slot determination module 480 of FIG. 4B. In some embodiments, the first time interval determined is 6 ms. In other cases, the first time interval determined is four milliseconds 4 ms.
[0119] In block 1125, the method may also involve determining a second timing space between
48/54 the transfer of the HARQ indicator channel (eg, NAK) and a second uplink shared channel transmission, which can be a HARQ retransmission. The operations in block 1125 can be performed by the multiport programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the time slot determination module 480 of FIG. 4B. In some cases, the first time interval determined is four milliseconds 4 ms. But in other modalities, the first time interval determined is 6 ms.
[0120] FIG. 12 shows a flow chart of a 1200 method for multi-carrier programming according to various modalities. Method 1200 can be implemented by base stations 105 and UEs 115 of FIG. 1, FIG. 3, FIG. 5, FIG. 6 or FIG. 7 or by the devices 405 and 405-a of FIGS. 4A and 4B.
[0121] In block 1205, the method may include determining a programming delay between a first control channel transfer and a corresponding uplink transmission to a TDD CC based on the programming delay to a FDD CC. The operations in block 1205 can, in some modalities, be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the timing determination module 450 of FIG. 4B.
[0122] In block 1210, the method may involve determining a number of UL HARQ processes for the TDD CC based on a DL / UL configuration of the TDD CC. The operations in block 1210 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the HARQ determination module 470 of FIG. 4B.
[0123] In block 1215, the method can include communication based on the timing of the determined schedule and the determined number of HARQ processes
49/54 uplink. The operations in block 1215 are, in various modalities, performed by the receiver modules 410 of FIGS. 4A or 4B, the transmitter modules 420 of FIGS. 4A or 4B, the transceiver modules 610 of FIG. 6, or the transceiver modules 750 of FIG. 7.
[0124] In block 1220, the method may involve determining a first time slot between a first UL shared channel transmission and a corresponding HARQ indicator channel transfer (eg, an ACK / NAK). The operations in block 1220 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the time slot determination module 480 of FIG. 4B.
[0125] In block 1225, the method may also involve determining a second timing space between the transfer of the HARQ indicator channel (eg, NAK) and a second uplink shared channel transmission, which may be a HARQ retransmission. The operations in block 1225 can be performed by the multiport programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the time slot determination module 480 of FIG. 4B.
[0126] In block 1230, the method may also include overriding the transfer of the HARQ indicator channel (eg, ACK / NAK) with a second control channel transfer. Operation on block 1230 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or the overwrite module 490 of FIG. 4B. In some cases, the second control channel transfer is a lease on the PDCCH or EPDCCH sent 2 ms (or two subframes) after the ACK / NAK. In other modalities, the second control channel transfer is a concession that is carried out on the PDCCH or EPDCCH in the same subframe as the ACK / NAK.
50/54
[0127] Next, FIG. 13 shows a flow chart of a 1300 method for multiport programming according to various modalities. The method 1300 can be implemented by the base stations 105 and UEs 115 of FIG. 1, FIG. 3, FIG. 5, FIG. 6 or FIG. 7 or by the devices 405 and 405-a of FIGS. 4A and 4B.
[0128] In block 1305, the method may include configuring a set of component carriers in the carrier aggregation. In some examples, this may include configuring component carriers for a base station; and the configuration can be indicated for a UE - eg, by means of the RRC signaling. In other cases, a UE may determine a configuration of a set of component carriers - for example, by the received RRC signaling. The set of component carriers can include a SCC TDD and a SCC FDD, which can be programmed by a cross carrier from one another. Operation on block 1305 can be performed by multi-port programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the cross-programming module 470 of FIG. 4B.
[0129] In block 1310, the method may include determining a scheduling delay, a HARQ UL timing of a SCC FDD based, in whole or in part, on a time duration of a TDC SCC. In some examples, a UE may identify the schedule delay and the HARQ UL delay based on RRC signaling from a base station. Operation on block 1310 can be performed by the multi-carrier programming modules 415 of FIGS. 4A, 4B, 6, or 7 or by the timing determination module 450 of FIG. 4B, or by the HARQ determination module 460 of FIG. 4B.
51/54
[0130] In block 1315, the method can include communication based on the timing of the determined schedule and the determined number of the UL HARQ process. Operation on block 1315 can be performed by the receiver modules 410 of FIGS. 4A or 4B, the transmitter modules 420 of FIGS. 4A or 4B, the transmitting module 610 and the receiving module 615 of FIG. 6, or the transceiver modules 750 of FIG. 7.
[0131] Those skilled in the art will recognize that methods 900, 1000, 1100, 1200 and 1300 are exemplary implementations of the tools and techniques described here. The methods can be carried out in more or less steps; and they can be performed in an order other than that indicated.
[0132] The detailed description presented above, in connection with the attached drawings, describes exemplary modalities and does not represent the only modalities that can be implemented or that are within the scope of the claims. The term exemplary used throughout this description means to serve as an example, case, or illustration, and not preferred or advantageous over other modalities. The detailed description includes specific details for the purpose to provide an understanding of the techniques described. These techniques, however, can be practiced without these specific details. In some cases, well-known structures and devices are shown in the form of a block diagram, in order to avoid obscuring the concepts of the described modalities.
[0133] Information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signs, bits, symbols,
52/54 and chips that can be referred to in the entire description above can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0134] The various blocks and illustrative modules described in connection with the description here can be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an array of field programmable port (FPGA) or other programmable logic device, discrete or transistor logic port, discrete hardware components, or any combination thereof designed to perform the functions described here. A general purpose processor can be a microprocessor, but, alternatively, the processor can be any conventional processor, controller, microcontroller, or conventional state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other type of configuration.
[0135] The functions described here can be implemented in hardware, software / firmware, or any combination thereof. If implemented in software / firmware, the functions can be stored in or transmitted via one or more instructions or code in a computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and attached claims. For example, due to the nature of the software / firmware, the functions described above can be implemented using software / firmware
53/54 executed by, eg, a processor, hardware, hardwiring, or combinations thereof. Resources that implement the functions can also be physically located in various positions, including being distributed so that portions of the functions are implemented in different physical locations. Also, as used here, including in the claims, or, as used in a list of items preceded by at least one of, indicates a disjunctive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or AC or ABC (ie, A and B and C).
[0136] Computer-readable media includes computer storage and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not by way of limitation, computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used. used to transport or store media of desired program code in the form of instructions or data structures and which can be accessed by a general purpose computer or special purpose computer, or a general purpose processor or special purpose processor. Also, any connection is properly called a computer-readable media. For example, if the software / firmware is transmitted from a website, server, or other remote source over a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies, such
54/54 such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of media. Disc and floppy disk, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disc and Blu-ray disc where floppy disks generally reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0137] The previous description of the disclosure is provided to allow a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other variations without departing from the spirit and scope of the disclosure. Throughout this disclosure, the term example or example indicates an example or instance and does not imply or require any preference for the example observed. Thus, the description should not be limited to the examples and drawings described here, but should be in accordance with the broadest scope consistent with the principles and new features described here.

权利要求:
Claims (24)
[1]
1. A method of wireless communication, comprising:
determining a configuration for a set of component carriers in the carrier aggregation, the set of component carriers comprising a time division duplexing (TDD) secondary component carrier (SCC) and a frequency division duplexing SCC (FDD) );
Identify a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based at least in part on a time duration of each TDD SCC frame; where the programming time comprises a time difference between the first downstream control transfer and a corresponding upward transmission, and where the HARQ time comprises a time difference between the upstream transmission and a second channel control transfer descending, and communication with a node based at least in part on the identified programming timing and FDD SCC HARQ uplink timing.
[2]
The method according to claim 1, the time duration of each frame of the TDD SCC comprising ten (10) milliseconds.
[3]
3. The method according to claim 2, with the TDD SCC programming timing comprising four (4) milliseconds.
[4]
4. The method, according to claim 1, being that:
the FDD SCC programming timing comprises a time difference between an uplink lease or physical hybrid indicator channel transmission
2/7 (PHICH) and a physical uplink shared channel transmission (PUSCH); and the timing of the FDD SCC HARQ uplink comprises a time difference between the PUSCH transmission and a subsequent PHICH transmission.
[5]
The method according to claim 1, wherein the set of component carriers further comprises the primary cell (PCC) for frequency division duplexing (FDD).
6. 0 method, in according to claim 1, being that FDD SCC is cross carrier from TDD SCC. 7. 0 method, in according to claim 1,
the TDD SCC comprises the downlinkuplink configuration (DL / UL) selected from a plurality of DL / UL configurations.
[6]
8. A wireless communication method, comprising:
configuring a set of component carriers in the carrier aggregation to serve user equipment (UE), the set of component carriers comprising a time division duplexing (TDD) secondary component carrier (SCC) and a duplexing SCC by frequency division (FDD); where the programming time comprises a time difference between the first downstream control transfer and a corresponding upward transmission, and where the HARQ time comprises a time difference between the upstream transmission and a second channel control transfer downward; and communication with the UE based at least in part on the determined schedule timing and FDD SCC HARQ uplink timing.
3/7
[7]
The method according to claim 8, the time duration of each frame of the TDD SCC comprising ten (10) milliseconds.
[8]
10. The method according to claim 9, the TDD SCC programming timing comprising four (4) milliseconds.
[9]
11. The method according to claim 8, being that:
the FDD SCC programming timing comprises a time difference between a physical hybrid indicator channel (PHICH) uplink concession or transmission and a physical uplink shared channel transmission (PUSCH); and the timing of the FDD SCC HARQ uplink comprises a time difference between the PUSCH transmission and a subsequent PHICH transmission.
[10]
12. The method according to claim 8, the set of component carriers further comprising a primary component carrier (PCC) of FDD.
13. 0 method, according with the claim 8, being what The FDD SCC is a cross carrier from the TDD SCC. 14. 0 method, according with the claim 8, being what The TDD SCC understands the downlink configuration-
uplink (DL / UL) selected from a plurality of DL / UL configurations.
[11]
The method according to claim 8, further comprising:
Indicate the configuration of the component carrier set for the UE through the radio resource control (RRC) signaling.
[12]
16. Wireless communication equipment, comprising:
means for determining a configuration for a set of component carriers in the carrier aggregation, the set of component carriers comprising a time division duplexing (TDD) secondary component carrier (SCD) and a frequency division duplexing SCC (FDD);
means for identifying a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based at least in part on a time duration of each TDD SCC frame; where the programming time comprises a time difference between the first downstream control transfer and a corresponding upward transmission, and where the HARQ time comprises a time difference between the upstream transmission and a second channel control transfer downward; and means for communicating with a node based at least in part on the identified programming timing and FDD SCC HARQ uplink timing.
[13]
17. The equipment according to the claim
16, with the duration of time for each TDD SCC frame comprising ten (10) milliseconds.
[14]
18. The equipment, according to the claim
17, and the TDD SCC programming timing comprises four (4) milliseconds.
[15]
19. The equipment according to claim 16, being that:
the FDD SCC programming timing comprises a time difference between an uplink lease or physical hybrid indicator channel transmission
5/7 (PHICH) and a physical uplink shared channel transmission (PUSCH); and
HARQ uplink timing from FDD SCC
it comprises a time difference between the PUSCH transmission and a subsequent PHICH transmission.
[16]
20. The equipment, according to the claim
16, with the set of component carriers
also comprises the primary cell (PCC) duplexing
frequency division (FDD).
21. The equipment, according to claim 16, and FDD SCC is a cross-carrier from TDD
SCC.
22. The equipment, according to claim 16, and the TDD SCC comprises a configuration
downlink-uplink (DL / UL) selected from a plurality of DL / UL configurations.
[17]
23. Wireless communication equipment, comprising:
means for configuring a set of component carriers in the carrier aggregation to serve user equipment (UE), the set of component carriers comprising a time division duplexing (TDD) secondary component carrier (SCC) and a SCC frequency division duplexing (FDD); in
that the programming time comprises a difference of
time between the first downstream control transfer and a corresponding upstream transmission, and where the HARQ time comprises a time difference between the upstream transmission and a second downstream control transfer;
means for determining a schedule timing and a FDD SCC hybrid uplink automatic repeat request (HARQ) timing based on ξ> / Ί less in part over a time span of each TDD SCC frame; and means for communicating with the UE based at least in part on the determined schedule timing and timing of the FDD SCC HARQ uplink.
[18]
24. The equipment according to the claim
23, with the duration of time for each TDD SCC frame comprising ten (10) milliseconds.
[19]
25. The equipment according to the claim
24, and the TDD SCC programming timing comprises four (4) milliseconds.
[20]
26. The equipment according to claim 23, being that:
the FDD SCC programming timing comprises a time difference between a physical hybrid indicator channel (PHICH) uplink concession or transmission and a physical uplink shared channel transmission (PUSCH); and the timing of the FDD SCC HARQ uplink comprises a time difference between the PUSCH transmission and a subsequent PHICH transmission.
[21]
27. The equipment, according to the claim
23, and the set of component carriers also comprises a primary component carrier (PCC) of FDD.
[22]
28. The equipment according to claim 23, the FDD SCC being a cross carrier from the TDD SCC.
[23]
29. The equipment according to claim 23, the TDD SCC comprising a downlink-uplink configuration (DL / UL) selected from a plurality of DL / UL configurations.
7/7
[24]
30. The equipment, according to claim
23, further comprising:
means for indicating the configuration of the set of component carriers for the UE through radio resource control (RRC) signaling.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112016006592A2|2020-05-12|reduced delay harq process timeline for fdd-tdd carrier aggregation

---

KR102339312B1|2021-12-13|Timing alignment procedures for dual pucch

---

AU2015339822B2|2020-04-02|Two-stage PDCCH with DCI flag and DCI format size indicator

---

KR101756958B1|2017-07-11|Lte hierarchical burst mode

---

US20180332605A1|2018-11-15|Device and methods for multiplexing transmissions with different tti duration

---

BR112019026490A2|2020-07-21|wireless transmission / reception unit, and, method of transmitting an uplink control information.

---

KR20170103798A|2017-09-13|Control information feedback for ecc on pcell

---

JP2018510534A|2018-04-12|Low latency in time division duplex

---

US9107191B2|2015-08-11|System and method for managing simultaneous uplink signal transmissions in carrier aggregation systems

---

JP2017509223A|2017-03-30|MBSFN and RS considerations in bundle transmission design

---

KR20160113156A|2016-09-28|Carrier aggregation with dynamic tdd dl/ul subframe configuration

---

US10764012B2|2020-09-01|Reducing processing time for low latency transmission and reception

---

US10091808B2|2018-10-02|System and method for handling uplink transmissions

---

CA3098577A1|2021-05-07|Wireless communications for scheduling transmissions

---

US20210029706A1|2021-01-28|Communication and Data Processing in Wireless Communications

---

US20220045806A1|2022-02-10|Control Channel Repetition

---

EP3895353A1|2021-10-20|Acknowledgment transmission in wireless communications systems

---

CA3126539A1|2022-01-28|Control channel repetition using multiple coresets

---

WO2021091966A1|2021-05-14|Uplink transmission in new radio unlicensed band

---

WO2021207470A1|2021-10-14|Pending harq feedback transmission

---

CA3090156A1|2021-02-14|Random access procedures

同族专利:

---

公开号 | 公开日

---

US20150085720A1|2015-03-26|

---

EP3050240B1|2021-10-20|

---

JP2016533653A|2016-10-27|

---

KR102313331B1|2021-10-14|

---

CN105580304A|2016-05-11|

---

EP3050240A1|2016-08-03|

---

CN105580304B|2019-07-05|

---

WO2015048404A1|2015-04-02|

---

KR20160064153A|2016-06-07|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN101902820B|2009-05-25|2013-04-03|电信科学技术研究院|Method and system for transmitting uplink data and device|

---

WO2012124996A2|2011-03-15|2012-09-20|엘지전자 주식회사|Method for transmitting/receiving signal and device therefor|

---

CN102752090B|2011-04-22|2017-06-16|北京三星通信技术研究有限公司|A kind of method that synchronous HARQ for supporting PUSCH is transmitted|

---

CN103313380A|2012-03-16|2013-09-18|北京三星通信技术研究有限公司|Uplink scheduling method and equipment|

---

CN103580830B|2012-07-18|2018-11-27|北京三星通信技术研究有限公司|A method of sending HARQ-ACK feedback information|

---

US9544885B2|2012-07-31|2017-01-10|Lg Electronics Inc.|Method and user device for receiving downlink signal, and method and base station for transmitting downlink signal|

---

US8811332B2|2012-10-31|2014-08-19|Sharp Laboratories Of America, Inc.|Systems and methods for carrier aggregation|

---

EP3624379B1|2013-03-28|2021-04-21|NEC Corporation|Method and apparatus for determining harq timing in communication systems|

---

US9538503B2|2013-03-28|2017-01-03|Samsung Electronics Co., Ltd.|Aggregation of FDD and TDD cells|

---

EP3036856B1|2013-08-23|2019-08-14|Telefonaktiebolaget LM Ericsson |A node and method for uplink scheduling and hybrid automatic repeat request timing|

---

US9319211B2|2013-08-23|2016-04-19|Telefonaktiebolaget Lm Ericsson |Node and method for downlink scheduling and hybrid automatic repeat request timing|US9936470B2|2013-02-07|2018-04-03|Commscope Technologies Llc|Radio access networks|

---

US9414399B2|2013-02-07|2016-08-09|Commscope Technologies Llc|Radio access networks|

---

US9380466B2|2013-02-07|2016-06-28|Commscope Technologies Llc|Radio access networks|

---

CN105612708B|2013-10-07|2020-03-10|Lg 电子株式会社|Method and apparatus for transmitting ACK/NACK by terminal in wireless communication system|

---

EP3657882A1|2014-06-09|2020-05-27|Commscope Technologies LLC|Radio access networks using plural remote units|

---

US9935742B2|2014-10-20|2018-04-03|Apple Inc.|Adaptive HARQ for half duplex operation for battery and antenna constrained devices|

---

EP3038285A3|2014-12-22|2016-10-26|Industrial Technology Research Institute|Method of handling communication operation in communication system and related apparatus|

---

US10693574B2|2015-07-02|2020-06-23|Qualcomm Incorporated|Method and apparatus for efficient data transmissions in half-duplex communication systems with large propagation delays|

---

US10785791B1|2015-12-07|2020-09-22|Commscope Technologies Llc|Controlling data transmission in radio access networks|

---

CN108472694A|2015-12-23|2018-08-31|波恩莱茵弗里德里希·威廉大学|The network retained for stabilizing gas under liquid|

---

US10430374B2|2016-06-29|2019-10-01|Mellanox Technologies, Ltd.|Selective acknowledgement of RDMA packets|

---

US10728852B2|2016-07-18|2020-07-28|Qualcomm Incorporated|Efficient power utilization for enhanced component carriers|

---

CN107733578B|2016-08-12|2020-03-24|电信科学技术研究院|Method and device for feeding back downlink data|

---

US10342021B1|2016-12-02|2019-07-02|Sprint Spectrum L.P.|Minimizing interference in wireless networks|

---

US10448421B2|2017-03-20|2019-10-15|Qualcomm Incorporated|Cross-carrier scheduling for wireless devices|

---

GB201707226D0|2017-05-05|2017-06-21|Vodafone Ip Licensing Ltd|Transmission schedulling for low latency comuunication|

---

US11012141B1|2017-06-09|2021-05-18|Sprint Spectrum L.P.|Systems and methods for selecting a donor for a relay wireless device|

---

US10820341B2|2018-02-12|2020-10-27|Mediatek Inc.|Determination of requirement of UE processing time in NR|

---

WO2019236689A1|2018-06-08|2019-12-12|Commscope Technologies Llc|Automatic transmit power control for radio points of a centralized radio access network that primarily provide wireless service to users located in an event area of a venue|

法律状态:
2018-11-06| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2020-08-04| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201361883173P| true| 2013-09-26|2013-09-26|

---

US14/497,268|US20150085720A1|2013-09-26|2014-09-25|Reduced delay harq process timeline for fdd-tdd carrier aggregation|

---

PCT/US2014/057656|WO2015048404A1|2013-09-26|2014-09-26|Reduced delay harq process timeline for fdd-tdd carrier aggregation|

---