The present invention is related to a wireless communications. More particularly, the present invention is related to an enhanced uplink (EU) operation during a soft handover.
Cellular wireless communication networks are divided into a plurality of coverage regions. Each coverage region in the network is served by a Node-B. As a wireless transmit/receive unit (WTRU) travels, it may move from one coverage region to another in the network.
The WTRU is served by the designated Node-B for a particular coverage region. The regions covered by Node-Bs overlap each other, and at the boundary of the region a WTRU can establish connections with more than one Node-B. As the WTRU moves from one coverage region to another in the network, the WTRU goes through handover. Soft handover is widely used to ensure communication without interruption while roving around a plurality of cells.
Soft handover occurs when a WTRU is connected to two or more Node-Bs simultaneously, on the same frequency. In soft handover, all Node-Bs serving the WTRU process the received data, which is then routed to a radio network controller (RNC) for macro diversity combining. For simplicity, the RNC may use an error detection technique such as a Cyclic Redundancy Check (CRC) and may accept a packet that passes the CRC.
Softer handover is a special case of soft handover. When a WTRU is in softer handover, the WTRU is connected to two or more cells belonging to the same Node-B. In contrast to soft handover, in softer handover macro diversity with or without maximum ratio combining can be performed in the Node-B.
Automatic repeat request (ARQ) is a technique whereby the receiver requests a retransmission of packets by the transmitter if errors are detected. Hybrid ARQ (H-ARQ) is a technique whereby transmitted data blocks are encoded for partial error correction at the receiver, and only data blocks with uncorrected errors are retransmitted. In prior art, i.e. in high speed downlink packet access (HSDPA), the H-ARQ functionality is terminated and controlled by the Node-B, (a technique called Node-B-controlled H-ARQ), allowing for rapid transmissions and retransmissions of erroneously received packets. This feature was both highly desirable and practical because H-ARQ in HSDPA was not required for soft handover. This feature would be highly desirable for EU also, but problems exist because it is intended for EU (and H-ARQ) to operate during soft handover.
One of the problems with Node-B-controlled H-ARQ in soft handover is the link imbalance. Since the associated uplink (UL) and downlink (DL) control signaling does not benefit from the soft handover gain, it might be error prone and require significant power offsets. In the DL direction, the WTRU may not be able to receive the acknowledge (ACK) or non-acknowledge (NACK) signals from all involved Node-Bs. In the UL, not all involved Node-Bs may be able to receive the associated control signaling from the WTRU, which may lead to soft buffer corruption.
A soft buffer is a buffer for implementing H-ARQ in a Node-B. Data packets received, but not acknowledged, by the Node-B are temporarily stored in the soft buffer for incremental combining. Therefore, a data packet transmitted, but not acknowledged previously, is combined with a retransmission of the same data packet transmitted in response to NACK signaling. Chase combining is a special case of an incremental combining. The soft buffer corruption causes misalignment of an H-ARQ protocol state among different Node-Bs and leads to loss of the soft handover gain. It would be desirable to achieve efficient H-ARQ operation without the problems associated with prior art systems.
Node-Bs can often make more efficient decisions and manage UL radio resources on a short-term basis better than an RNC, even if the RNC retains overall control over Node-Bs. In order for a Node-B to assign UL radio resources to WTRUs in EU operation, the Node-B must know several WTRU-specific parameters. Under the current 3GPP standard, only the RNC can know the WTRU-specific parameters by means of radio resource control (RRC) messages. Therefore, it is necessary to forward the information to the Node-B for proper scheduling of radio resources in EU transmissions.
An RNC maintains an active set of cells for each WTRU in soft handover. The RNC bases its decision to add to or remove cells from the WTRU's active set upon measurements provided by a WTRU and a Node-B and on management of available radio resources in each cell. Under the current 3GPP standards, the RNC applies RRC radio bearer (RB) control procedures to coordinate active set cells with the WTRU, and Node-B application part/radio network subsystem application part (NBAP/RNSAP) radio link procedures to coordinate active set cells with each Node-B.
During soft handover, some information should be communicated between network entities to support EU operation. The information includes, but is not limited to, information related to an active set, information regarding a Node-B that controls transmissions during soft handover, EU scheduling information during soft handover, and ACK/NACK status information during soft handover. The current 3GPP standards do not define specific protocols to transfer necessary information which are imperative in operation of EU during soft handover. Therefore, it is necessary to define a protocol for transferring WTRU-specific information and other EU related information among an RNC, a Node-B, and a WTRU so that a Node-B is enabled to schedule radio resources and EU connections are handed over properly during soft handover.
The present invention is related to EU operation during a soft handover in a wireless communication system. The wireless communication system comprises a WTRU, at least two Node-Bs, and an RNC. In accordance with one embodiment of the present invention, for each WTRU one Node-B is designated as a primary Node-B and any other Node-B within the EU active set as a non-primary Node-B. The primary Node-B controls EU operation during soft handover including EU scheduling and H-ARQ. Soft buffer corruption is avoided by controlling H-ARQ during soft handover only by the primary Node-B. Alternatively, an RNC may control EU operation during soft handover including H-ARQ. In this case, an RNC generates final ACK/NACK decision based on the error check results of the Node-Bs.
The present invention will be described with reference to the drawing figures wherein like numerals represent like elements throughout.
When referred to hereafter, the terminology “WTRU” includes but is not limited to a user equipment, a mobile station, fixed or mobile subscriber unit, pager, or any other type of device capable of operating in a wireless environment. When referred to hereafter, the terminology “Node-B” includes but is not limited to a base station, site controller, access point or any other type of interfacing device in a wireless environment.
One Node-B in a group of Node-Bs in an “active set” is designated as a primary Node-B 104a, while other Node-Bs in the active set are designated as non-primary Node-Bs 104b. An RNC 106 or the WTRU 102 makes this decision (step 152). If it is decided by an RNC 106, the RNC 106 informs all Node-Bs 104a, 104b and the WTRU 102. If it is decided by a WTRU 102, the WTRU 102 informs either all Node-Bs 104a, 104b or the RNC 106 which in turn informs all the Node-Bs 104a, 104b.
In making a decision regarding the primary Node-B 104a, the RNC 106 may use statistics, i.e. the number of successful decodings of particular WTRUs transmissions by each Node-B 104a, 104b, to identify the Node-B 104a, 104b with the best UL performance. It is the performance of the best cell controlled by a Node-B that is evaluated, not the performance of all cells associated with a Node-B. The RNC 106 may also select the primary Node-B 104a by evaluating both UL performance as described above and DL performance as obtained from WTRU 102 measurements. The RNC 106 then notifies the Node-Bs 104a, 104b and the WTRU 102 regarding which one will be the primary Node-B 104a via Iub signaling and RRC signaling, respectively. The WTRU 102 may also be informed of the primary Node-B 104a by fast layer 1 signaling from Node-B.
The primary Node-B 104a employs incremental combining, while non-primary Node-Bs 104b may or may not use incremental combining. If the non-primary Node-Bs 104b do not use incremental combining, the non-primary Node-Bs 104b may use simple ARQ, and may always refresh their buffers and not perform any combining. This scheme eliminates the problem of soft buffer corruption in soft handover. If both a primary Node-B 104a and non-primary Node-Bs 104b perform incremental combining, soft buffer corruption may be eliminated with a new data indicator or a sequence number in physical control signaling sent by the WTRU 102 to inform Node-Bs 104a, 104b which data packet is being transmitted, and thereby the Node-Bs 104a, 104b can manage soft buffer without corruption.
All Node-Bs 104a, 104b in the active set receive a data packet from the WTRU 102 (step 154). Each Node-B 104a, 104b performs an error check on the data packet and generates an indication of success or failure in decoding the data packet (step 156). Determining whether a data packet is successfully received is performed via an error check procedure; such as implementing a cyclic redundancy check (CRC). The indication of success or failure in decoding the data packet by the Node-Bs can be configured in a variety of different forms, but will be referred to hereinafter as a CRC result, or an ACK/NACK, in all embodiments of the present invention. However, any type of error checking may be performed in accordance with the teachings of the present invention, and it should be understood that the term “CRC” or “ACK/NACK” is used only as an illustration, not as a limitation, of the present invention.
When a Node-B 104a, 104b correctly decodes the data packet as determined by the error check, the Node-B 104a, 104b transmits the data packet to the RNC 106. If the primary Node-B 104a derives an ACK from the data packet, it transmits an ACK signal to the WTRU 102 and the RNC 106 without waiting for the CRC results from non-primary Node-Bs 104b, and refreshes soft buffer (step 158). If the primary Node-B 104a derives a NACK from the data packet, it transmits a NACK to the RNC and waits for the final decision from the RNC or CRC results from non-primary Node-Bs forwarded through the RNC 106 (step 158). The primary Node-B 104a may set a timer as will be explained hereinafter. The primary Node-B 104a transmits an ACK/NACK signal to the WTRU 102 in accordance with the final decision made by the RNC 106 or CRC results forwarded from non-primary Node-Bs 104b.
Non-primary Node-Bs 104b transmit a data packet to the RNC 106 only if they derive an ACK from the data packet (step 158). The RNC 106 makes an ACK/NACK decision (step 160). If the RNC 106 receives at least one ACK from Node-Bs 104a, 104b, the RNC 106 makes an ACK decision, and if the RNC 106 receives no ACK from Node-Bs 104a, 104b within a predetermined time period, the RNC 106 makes a NACK decision. The RNC 106 transmits an ACK/NACK decision to the primary Node-B 104a. The RNC 106 may not send an ACK decision to the primary Node-B 104a when the primary Node-B 104a derives an ACK. The RNC 106 optionally transmits the ACK/NACK decision to the non-primary Node-Bs 104b for soft buffer management depending on the scheme of incremental combining at the non-primary Node-Bs 104b.
It is optional for the RNC 106 to use the packets delivered from non-primary Node-Bs 104b. If the RNC 106 uses the packet from non-primary Node-Bs 104b, a media access control (MAC) function of the RNC 106 performs an in-sequence delivery mechanism over all the received packets from all the involved Node-Bs 104a, 104b. If a Radio Link Control (RLC) layer realized an out of sequence transmission it assumes data is lost and requests retransmission. If the RNC 106 does not use the packets from non-primary Node-Bs 104b, the RNC 106 processes only the packets received from the primary Node-B 104a. The RNC 106 extracts and enters the data packet into the MAC level reordering buffer. After the RNC MAC performs the re-sequencing process, it sends the data to the RLC layer. Missed packets are identified and notified to the WTRU 102 through RLC messaging.
Optionally, a streamlined connection may be implemented in transmission of the result of the error check between Node-Bs and an RNC. A fast streamlined connection is explained with reference to
A fast streamlined connection 510a, 510b may be implemented in accordance with two alternatives. In accordance with the first alternative, two logical channels are established between an RNC 506 and two Node-Bs 504a, 504b, respectively. The RNC 506 receives H-ARQ signaling 510b from one Node-B 504b and processes it before forwarding it 510a to another Node-B 504a. The RNC 506 recognizes the status of H-ARQ process of each Node-B 504a, 504b by processing the signaling. As explained above, the CRC results are processed by the RNC 506 and the RNC 506 makes a final ACK/NACK decision and transmits the ACK/NACK decision to the Node-Bs 504a, 504b.
Upon reception of the first ACK from any Node-B 504a, 504b in the RNC 506, the RNC 506 transmits ACK decision to all Node-Bs 504a, 504b. In the case that all Node-Bs 504a, 504b derive a NACK, it takes some time to wait for all Node-Bs 504a, 504b to provide the CRC results. Therefore, optionally the RNC 506 may set a timer waiting for all Node-B's responses and if the timer expires the RNC 506 transmits a NACK to all Node-Bs 504a, 504b.
In accordance with the second alternative, a single logical channel between two Node-Bs 504a, 504b via an RNC 506 is established. The RNC 506 receives CRC results from one Node-B 504b and just forwards it to another Node-B 504a without processing it. This process is fast since the signaling is just routed between Node-Bs 504a, 504b without processing at the RNC 506. Therefore, it avoids the processing delay and protocol delay at the RNC 506. Each Node-B 504a, 504b derives the final ACK/NACK decision based on the collected CRC results from all the involved Node-Bs 504a, 504b in the active set. If there is at least one ACK from any Node-B, a final ACK decision will be made at each Node-B 504a, 504b. Otherwise, a final decision of NACK will be made by the Node-B 504a, 504b. As stated above, each Node-B 504a, 504b generates an ACK decision upon reception of the first ACK from any Node-B 504a, 504b. The Node-Bs 504a, 504b may set a timer waiting for an ACK from other Node-Bs 504a, 504b, and if the Node-Bs 504a, 504b do not receive any ACK before the expiration of the timer, the Node-Bs 504a, 504b generates a NACK decision.
The streamlined connection 510a, 510b between Node-Bs 504a, 504b and an RNC 506 may be implemented in any embodiment of the present invention described herein.
With reference to
A WTRU 202 establishes connections with at least two cells controlled by different Node-Bs 204a, 204b for soft handover, and data packets transmitted from the WTRU 202 are received and processed separately by the Node-Bs 204a, 204 b (step 252). Each Node-B 204a, 204b performs an error check on the data packet and generates a CRC result (step 254). Each Node-B 204a, 204b transmits the CRC result to the RNC 206. Simultaneously, each Node-B 2041, 204b transmits the CRC result to the WTRU 202 as well (step 256). The WTRU 202 makes a determination regarding whether there is at least one ACK received from Node-Bs 204a, 204b (step 258). The WTRU 202 may receive both ACK and NACK signals from the Node-Bs 204a, 204b. If the WTRU 202 receives no ACK, it schedules retransmission of the data packet (step 264). The Node-Bs 204a, 204b perform incremental combining of the retransmission with the previous transmission. If the WTRU 202 receives at least one ACK from any Node-B 204a, 204b, the WTRU 202 transmits the next data packet (step 262).
The RNC 206 also makes an ACK/NACK decision based on collected ACK/NACK signals from the Node-Bs 204a, 204b (step 260). The RNC 206 generates and transmits an ACK decision (step 268) if the RNC 206 receives at least one ACK from the Node-Bs 204a, 204b. Otherwise, the RNC 206 generates and transmits a NACK decision to the Node-Bs 204a, 204b (step 270). The ACK/NACK decision is transmitted to the Node-Bs 204a, 204b. Each Node-B 204a, 204b refreshes its soft buffer once it receives ACK decision from the RNC 206 (step 272). With this scheme, soft buffer corruption is eliminated.
If the results of the error check from all Node-Bs 304a, 304b fail, (i.e. all of the Node-Bs 304a, 304b generate NACKs) or a response timer Node-B coordinator expires, the Node-B coordinator 308 informs all of the Node-Bs 304a, 304b that they failed to successfully decode the transmitted data packet and that they should prepare for retransmission of the data packet (step 364). In response, the Node-Bs 304a, 304b send an NACK to the WTRU 302 (step 366).
Each Node-B 404a, 404b transmits a CRC result to the RNC 406 (step 456). If the Node-B 404a, 404b succeeds in decoding the data packet, the Node-B 404a, 404b sends an ACK to the RNC 406 along with the data packet. If the Node-B 404a, 404b fails in decoding the data packet, the Node-B 404a, 404b sends a NACK to the RNC 406. An ACK and NACK may be sent with each data block within Iub/Iur frame protocols between Node-Bs 404a, 404b and the RNC 406. The RNC 406 makes a final ACK/NACK decision regarding the transmission of the data packet from the error check results conducted by the Node-Bs 404a, 404b (step 458). The RNC 406 makes an ACK decision if the RNC 406 receives at least one ACK from the Node-Bs 404a, 404b. Otherwise the RNC 406 makes a NACK decision. The ACK or NACK decision made by the RNC 406 is then transmitted back to the Node-Bs 404a, 404b at steps 460 and 464, respectively. Each Node-B 404a, 404b clears its buffer upon receipt of the ACK decision from the RNC 406. All Node-Bs 404a, 404b transmit the same ACK or NACK signal made by the RNC 406 to the WTRU 402 regardless of the CRC result that each Node-B 404a, 404b individually derived from the data packet (steps 462 and 466). In this case, the WTRU 402 may apply maximum ratio combining (MRC) to the received ACK/NACK feedback signals from the Node-Bs 404a, 404b.
The soft buffer in each Node-B 404a, 404b is managed according to the ACK/NACK decision made by the RNC 406, regardless of the associated error check result derived by the Node-Bs 404a, 404b. Consequently, the fourth embodiment of the present invention allows the RNC 406 to align the soft buffer status in each Node-B 404a, 404b. Additionally, the WTRU 402 can benefit from the soft handover gain for the ACK/NACK signaling, since identical ACK/NACK signaling is transmitted by all Node-Bs 404a, 404b. As such, the WTRU 402 may perform macro diversity combining (maximum ratio combining) for ACK/NACK signaling, since the ACK/NACK signals transmitted back to the WTRU 402 from all the involved Node-Bs 404a, 404b are identical.
A fifth embodiment of the present invention will be explained with reference to
In accordance with the first alternative, the Node-B 804 receives data packets from all the involved cells 808 and combines them using a technique, such as maximum ratio combining, before performing error check on the data packet. The resulting combined data packet is error checked at the Node-B 804.
In accordance with the second alternative, each cell 808 processes the data packet individually determining error check on the data packet received from the WTRU 802. The Node-B 804 accepts the data packet that the error check has passed in any of the cells 808 within the active set.
In downlink, the Node-B 804 sends messages including ACK/NACK to the WTRU 802 via all the involved cells 808 (step 858). The WTRU 802 needs to monitor all channels, preferably shared channels, from the involved cells 808 to detect downlink messages. The number of shared channels that the WTRU 802 should monitor from each cell 808 may be limited, such as up to 4 channels.
One of the cells 808 may be designated as a primary cell 808a, while other cells are designated as non-primary cells 808b. The primary cell 808a sends a message on any of the downlink shared channels allocated to the WTRU 802. The message carries a shared channel indicator for non-primary cells 808b. The non-primary cells 808b send messages on the channel indicated by the shared channel indicator. In order to implement this scheme, there is a timing offset between the transmission of the shared channel indicator from the primary cell 808a and the transmission of messages from non-primary cells 808b. The WTRU 802 first monitors all shared channels from the primary cell 808a. Once the WTRU 802 detects that one of the shared channels carry messages to the WTRU 802, the WTRU 802 reads shared channel indicator along with the downlink messages from the primary cell 808a. Then, the WTRU 802 receives messages from the non-primary cells 808b indicated by the shared channel indicator. With this scheme, it is possible to lower the number of channels that the WTRU 802 should monitor. The WTRU 802 then combines the messages received from all the involved cells 808 using a technique, such as maximum ratio combining.
Alternatively, for the DL, only the primary cell 808a may transmit messages to the WTRU 802. The Node-B 804 transmits downlink messages via the primary cell 808a, while all non-primary cells 808b switch off the downlink signaling to the WTRU 802. With this scheme, the WTRU 802 receive processing is simplified and downlink interference is reduced.
An RNC 1006 maintains an active set of cells for handover. The RNC 1006 selects and removes cells in the active set based on measurements reported from Node-Bs 1004a, 1004b and the WTRU 1002 and on available radio resources. Once the RNC 1006 selects cells for the active set, the RNC 1006 sends messages to the Node-Bs 1004a, 1004b and the WTRU 1002 to inform the selected cells for the active set to support soft handover for EU. The RNC 1006 also sends messages to update the active set each time the RNC 1006 adds or removes a cell in the active set. The messages may be transmitted using existing RRC and NBAP/RNSAP active set management procedures or new procedures.
Either the RNC 1006 or the Node-Bs 1004a, 1004b and the WTRU 1002 may designate one Node-B as a primary Node-B 1004a and other Node-Bs in the active set as non-primary Node-Bs 1004b during soft handover. The selection of the primary Node-B 1004a is based on UL performance measured and reported by each Node-B 1004a, 1004b and/or DL performance measured and reported by the WTRU 1002.
During soft handover, only the primary Node-B 1004a performs scheduling and assigning radio resources to the WTRU 1002. The primary Node-B 1004a informs the RNC 1006 of scheduled EU transmissions via Iub NBAP signaling or within the EU frame protocol. The RNC 1006 then informs non-primary Node-Bs 1004b of the allocation of radio resources for EU and routing of received data. This is also signaled over NBAP or within the EU frame protocol. Alternatively, non-primary Node-Bs 1004b may be informed by Iub NBAP procedures of sets of EU physical channels for the period each cell is within the active subset. Each non-primary Node-B 1004b within the active set continuously receives these channels independent of radio resources allocation scheduled by the primary Node-B 1004a.
Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention.
This application is a continuation of U.S. patent application Ser. No. 17/008,178, filed Aug. 31, 2020, which is a continuation of U.S. patent application Ser. No. 16/533,320 filed on Aug. 6, 2019, which issued as U.S. Pat. No. 10,764,803 on Sep. 1, 2020, which is a continuation of U.S. patent application Ser. No. 15/212,403, filed on Jul. 18, 2016, which issued as U.S. Pat. No. 10,390,279 on Aug. 20, 2019, which is a continuation of U.S. patent application Ser. No. 13/236,133 filed on Sep. 19, 2011, which issued as U.S. Pat. No. 9,438,381 on Sep. 6, 2016, which is a continuation of U.S. patent application Ser. No. 10/925,426, filed on Aug. 25, 2004, which issued as U.S. Pat. No. 8,023,463 on Sep. 20, 2011, which claims priority from U.S. Provisional Application Nos. 60/497,747 filed on Aug. 25, 2003; 60/507,554 filed on Oct. 1, 2003; 60/508,797 filed on Oct. 3, 2003; 60/520,207 filed on Nov. 14, 2003 and 60/585,174 filed on Jul. 2, 2004, which are incorporated by reference as if fully set forth. This application is related to U.S. patent application Ser. No. 15/212,402, filed Jul. 18, 2016, which issued as U.S. Pat. No. 10,251,106 on Apr. 2, 2019. This application is related to co-pending U.S. patent application entitled “Method and Apparatus for Monitoring Downlink Channels of a Plurality of Cells and Receiving Data Over a Downlink Channel”, attorney docket number SIG-2-0644US10, filed Nov. 16, 2020, and co-pending U.S. patent application entitled “Method and Apparatus for Transmitting Data Over a Downlink Channel of at Least One of a Plurality of Cells, attorney docket number SIG-2-0644US11, filed Nov. 16, 2020.
Number | Name | Date | Kind |
---|---|---|---|
5628631 | Aneha | May 1997 | A |
5794149 | Hoo | Aug 1998 | A |
5933787 | Gilhousen et al. | Aug 1999 | A |
5946320 | Decker et al. | Aug 1999 | A |
6351460 | Tiedemann, Jr. et al. | Feb 2002 | B1 |
6414947 | Legg | Jul 2002 | B1 |
6434396 | Rune | Aug 2002 | B1 |
6507567 | Willars | Jan 2003 | B1 |
6628631 | Mazawa et al. | Sep 2003 | B1 |
6643813 | Johansson et al. | Nov 2003 | B1 |
6650905 | Toskala et al. | Nov 2003 | B1 |
6678249 | Toskala et al. | Jan 2004 | B2 |
6678523 | Ghosh | Jan 2004 | B1 |
6690939 | Jonsson et al. | Feb 2004 | B1 |
6754496 | Mohebbi et al. | Jun 2004 | B2 |
6778830 | Oizumi et al. | Aug 2004 | B1 |
6829482 | Rune et al. | Dec 2004 | B2 |
6850771 | Malladi et al. | Feb 2005 | B2 |
6892071 | Park et al. | May 2005 | B2 |
6907245 | Ohlsson et al. | Jun 2005 | B2 |
6915465 | Fujiwara et al. | Jul 2005 | B2 |
6970716 | Rune et al. | Nov 2005 | B2 |
6977888 | Frenger et al. | Dec 2005 | B1 |
7013143 | Love et al. | Mar 2006 | B2 |
7026911 | Aono et al. | Apr 2006 | B2 |
7046648 | Zhang et al. | May 2006 | B2 |
7054633 | Seo et al. | May 2006 | B2 |
7065359 | Chuah et al. | Jun 2006 | B2 |
7082304 | Wakabayashi | Jul 2006 | B2 |
7103729 | Altahan et al. | Sep 2006 | B2 |
7124350 | Chao et al. | Oct 2006 | B2 |
7158504 | Kadaba et al. | Jan 2007 | B2 |
7185256 | Miki et al. | Feb 2007 | B2 |
7206598 | Attar et al. | Apr 2007 | B2 |
7212824 | Terry | May 2007 | B2 |
7266384 | Kim et al. | Sep 2007 | B2 |
7269420 | Heo et al. | Sep 2007 | B2 |
7277407 | Kim et al. | Oct 2007 | B2 |
7283508 | Choi et al. | Oct 2007 | B2 |
7283509 | Moon et al. | Oct 2007 | B2 |
7283782 | Sinnarajah et al. | Oct 2007 | B2 |
7315741 | Chun | Jan 2008 | B2 |
7317700 | Hwang | Jan 2008 | B2 |
7346035 | Lee et al. | Mar 2008 | B2 |
7366538 | Seki et al. | Apr 2008 | B2 |
7372898 | Shin et al. | May 2008 | B2 |
7403513 | Lee et al. | Jul 2008 | B2 |
7414989 | Kuchibhotla et al. | Aug 2008 | B2 |
7428424 | Hwang et al. | Sep 2008 | B2 |
7433337 | Chao et al. | Oct 2008 | B2 |
7519016 | Lee et al. | Apr 2009 | B2 |
7558230 | Lee et al. | Jul 2009 | B2 |
7606205 | Ranta-Aho et al. | Oct 2009 | B2 |
7848290 | Cheng et al. | Dec 2010 | B2 |
7903610 | Cheng | Mar 2011 | B2 |
7974630 | Haumont et al. | Jul 2011 | B1 |
8023463 | Dick | Sep 2011 | B2 |
8682325 | Cooper | Mar 2014 | B1 |
9438381 | Dick | Sep 2016 | B2 |
9763156 | Zhang | Sep 2017 | B2 |
10390279 | Dick et al. | Aug 2019 | B2 |
20010020285 | Fujiwara et al. | Sep 2001 | A1 |
20020080719 | Parkvall et al. | Jun 2002 | A1 |
20020093937 | Kim et al. | Jul 2002 | A1 |
20020095635 | Wager et al. | Jul 2002 | A1 |
20020115460 | Rune et al. | Aug 2002 | A1 |
20020115467 | Hamabe | Aug 2002 | A1 |
20020141360 | Baba | Oct 2002 | A1 |
20020172208 | Malkamaki | Nov 2002 | A1 |
20020191544 | Cheng et al. | Dec 2002 | A1 |
20020198025 | Brownlee et al. | Dec 2002 | A1 |
20030002470 | Park et al. | Jan 2003 | A1 |
20030007480 | Kim et al. | Jan 2003 | A1 |
20030031119 | Kim et al. | Feb 2003 | A1 |
20030043786 | Kall et al. | Mar 2003 | A1 |
20030054824 | Choi et al. | Mar 2003 | A1 |
20030081692 | Kwan et al. | May 2003 | A1 |
20030123403 | Jiang | Jul 2003 | A1 |
20030123470 | Kim et al. | Jul 2003 | A1 |
20030131124 | Yi et al. | Jul 2003 | A1 |
20030147370 | Wu | Aug 2003 | A1 |
20030161284 | Chen | Aug 2003 | A1 |
20030171118 | Miya | Sep 2003 | A1 |
20030176195 | Dick et al. | Sep 2003 | A1 |
20030202500 | Ha et al. | Oct 2003 | A1 |
20030210668 | Malladi et al. | Nov 2003 | A1 |
20040004954 | Terry et al. | Jan 2004 | A1 |
20040072567 | Cao et al. | Apr 2004 | A1 |
20040085934 | Balachandran et al. | May 2004 | A1 |
20040109433 | Khan | Jun 2004 | A1 |
20040120306 | Wigard et al. | Jun 2004 | A1 |
20040160925 | Heo et al. | Aug 2004 | A1 |
20040202129 | Kolding et al. | Oct 2004 | A1 |
20040203991 | Chen et al. | Oct 2004 | A1 |
20040219917 | Love et al. | Nov 2004 | A1 |
20040219919 | Whinnett et al. | Nov 2004 | A1 |
20040219920 | Love et al. | Nov 2004 | A1 |
20040228313 | Cheng et al. | Nov 2004 | A1 |
20050041694 | Liu | Feb 2005 | A1 |
20050047354 | Zeira et al. | Mar 2005 | A1 |
20050048920 | Liu | Mar 2005 | A1 |
20050083888 | Smee et al. | Apr 2005 | A1 |
20050207374 | Petrovic et al. | Sep 2005 | A1 |
20060045010 | Baker et al. | Mar 2006 | A1 |
20060105796 | Malladi et al. | May 2006 | A1 |
20060274712 | Malladi et al. | Dec 2006 | A1 |
20070047501 | Usuda et al. | Mar 2007 | A1 |
20070079207 | Seidel et al. | Apr 2007 | A1 |
Number | Date | Country |
---|---|---|
10225428 | Dec 2003 | DE |
0 977 393 | Feb 2000 | EP |
1 217 777 | Jun 2002 | EP |
2 353 439 | Feb 2001 | GB |
04-157821 | May 1992 | JP |
2000-217139 | Aug 2000 | JP |
2001-8251 | Jan 2001 | JP |
2001-128209 | May 2001 | JP |
2002-009741 | Jan 2002 | JP |
2003-134180 | May 2003 | JP |
2003-163960 | Jun 2003 | JP |
2007-511135 | Apr 2007 | JP |
20020095231 | Dec 2002 | KR |
20030003943 | Jan 2003 | KR |
20030040972 | May 2003 | KR |
2003112283 | Dec 2005 | RU |
2005110767 | Oct 2006 | RU |
536896 | Jun 2003 | TW |
200303689 | Sep 2003 | TW |
99027740 | Jun 1999 | WO |
0035226 | Jun 2000 | WO |
00074263 | Dec 2000 | WO |
0201893 | Jan 2002 | WO |
0237572 | May 2002 | WO |
02037872 | May 2002 | WO |
02047317 | Jun 2002 | WO |
02082108 | Oct 2002 | WO |
02101966 | Dec 2002 | WO |
02102109 | Dec 2002 | WO |
03003643 | Jan 2003 | WO |
03026231 | Mar 2003 | WO |
03037027 | May 2003 | WO |
03047155 | Jun 2003 | WO |
03053087 | Jun 2003 | WO |
2003049481 | Jun 2003 | WO |
03067953 | Aug 2003 | WO |
03088545 | Oct 2003 | WO |
2005048503 | May 2005 | WO |
Entry |
---|
3GPP TS 25.133 V6.2.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; “Requirements For Support of Radio Resource Management” (FDD); (Release 6); (Jun. 2003). |
3GPP TS 25.133 V6.6.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; “Requirements for Support of Radio Resource Management” (FDD); (Release 6); (Jun. 2004). |
3GPP TS 25.308 V5.4.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; “High Speed Downlink Packet Accees (HSDPA)”; Stage 2 (Release 5); (Mar. 2003). |
3GPP TS 25.308 V6.1.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; “High Speed Downlink Packet Accees (HSDPA)”; Stage 2 (Release 6); (Mar. 2004). |
3GPP TS 25.309 V0.2.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; “FDD Enhanced Uplink”; Stage 2 (Release 6); (Jun. 2004). |
3GPP, 3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Feasibility Study for Enhanced Uplink for UTRA FDD”, (Release 6, 3GPP TR 25.896, V.0.4.2 (R1-030952) (Sep. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 6),” 3GPP TS 25.321 V6.2.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical Layer Procedures (FDD) (Release 6),” 3GPP TS 25.214 V6.2.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical Layer Procedures (FDD) (Release 5),” 3GPP TS 25.214 V5.9.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical Layer Procedures (FDD) (Release 5),” 3GPP TS 25.214 V5.5.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical Layer Procedures (FDD) (Release 4),” 3GPP TS 25.214 V4.6.0 (Mar. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical Layer Procedures (FDD) (Release 1999),” 3GPP TS 25.214 V3.12.0 (Mar. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 1999),” 3GPP TS 25.321 V3.17.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 1999),” 3GPP TS 25.321 V3.15.0 (Mar. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 5),” 3GPP TS 25.321 V5.5.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 5),” 3GPP TS 25.321 V5.6.0 (Sep. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 4),” 3GPP TS 25.321 V4.10.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 4),” 3GPP TS 25.321 V4.8.0 (Mar. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 5),” 3GPP TS 25.321 V5.9.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA)”; Stage 2 (Release 5), 3GPP TS 25.308 V5.5.0 (Mar. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (FDD) (Release 1999),” 3GPP TS 25.211 V3.12.0 (Sep. 2002). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (FDD) (Release 4),” 3GPP TS 25.211 V4.6.0 (Sep. 2002). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (FDD) (Release 5),” 3GPP TS 25.211 V5.5.0 (Sep. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (FDD) (Release 5),” 3GPP TS 25.211 V5.4.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (FDD) (Release 6),” 3GPP TS 25.211 V6.1.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of radio resource management (FDD) (Release 5),” 3GPP TS 25.133 V5.11.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of radio resource management (FDD) (Release 5),” 3GPP TS 25.133 V5.7.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of radio reeource menagement (FDD) (Release 4),” 3GPP TS 25.133 V4.12.0 (Mar. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of radio resource management (FDD) (Release 4),” 3GPP TS 25.133 V4.9.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of radio resource management (FDD) (Release 1999),” 3GPP TS 25.133 V3.18.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for support of radio resource management (FDD) (Release 1999),” 3GPP TS 25.133 V3.14.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Feasibility Study for Enhanced Uplink for UTRA FDD (Release 6),” 3GPP TR 25.896 V6.0.0 (Mar. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Multiplexing and channel coding (FDD) (Release 1999),” 3GPP TS 25.212 V3.11.0 (Sep. 2002). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Multiplexing and channel coding (FDD) (Release 4),” 3GPP TS 25.212 V4.6.0 (Sep. 2002). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Multiplexing and channel coding (FDD) (Release 5),” 3GPP TS 25.212 V5.9.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Multiplexing and channel coding (FDD) (Release 6),” 3GPP TS 25.212 V6.2.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Multiplexing and channel coding (FDD) (Release 5),” 3GPP TS 25.212 V5.5.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC) protocol specification (Release 1999),” 3GPP TS 25.331 V3.15.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC) protocol specification (Release 1999),” 3GPP TS 25.331 V3.19.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 4),” 3GPP TS 25.331 V4.10.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 4),” 3GPP TS 25.331 V4.14.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 5),” 3GPP TS 25.331 V5.5.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol specification (Release 5),” 3GPP TS 25.331 V5.9.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 6),” 3GPP TS 25.331 V6.2.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub interface NBAP signaling (Release 1999),” 3GPP TS 25.433 V3.14.1 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub interface NBAP signaling (Release 1999),” 3GPP TS 25.433 V3.13.0 (Mar. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub interface NBAP signaling (Release 4),” 3GPP TS 25.433 V4.9.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub interface NBAP signaling (Release 4),” 3GPP TS 25.433 V4.12.0 (Mar. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub interface NBAP signaling (Release 5),” 3GPP TS 25.433 V5.5.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub interface NBAP signaling (Release 5),” 3GPP TS 25.433 V5.9.0 (Jun. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub interface NBAP signalihg (Release 6),” 3GPP TS 25.433 V6.2.0 (Jun. 2004). |
3GPP, 3rd Generation Partnership Project; Technical Specification, Universal Mobile Telecommunications System; Multiplexing and Channel Coding (FDD), 3GPP TS 25.212, V6.7.0, Release 6, (Dec. 2015). |
3GPP, 3rd Generation Partnership Project; Technical Specification, Universal Mobile Telecommunications System; FDD Enhanced Uplink; Overall Description; Stage 2, 3GPP TS 25.309, V6.6.0, Release 6, (Mar. 2006). |
3GPP2 C.20003-C, “Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems”, 3rd Generation Partnership Project 2 “3GPP2”, Version 2.0, Release C, (Aug. 2004). |
3GPP2 C.S0002-C, “Physical Layer Standard for cdma2000 Spread Spectrum Systems”, 3rd Generation Partnership Project 2 “3GPP2”, Version 2.0, Revision C, (Jul. 23, 2004). |
3GPP2 C.S0004-C, “Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems”, 3rd Generation Partnership Project 2 “3GPP2”, Version 2.0, Revision C, (Jul. 23, 2004). |
3GPP2 C.S0005-C, “Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems”, 3rd Generation Partnership Project 2 “3GPP2”, Version 2.0, Revision 6, (Jul. 23, 2004). |
3rd Generation Partnership Project: Technical Specification Group Radio Access Network; Feasibility Study For Enhanced Uplink For Utra FDD; (Release 6), 3GPP TR 25.896 V0.2.1 (Feb. 2003) R1-030372, pp. 14-17 (Feb. 26, 2003). |
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Feasibility Study for Enhanced Uplink for UTRA FDD; (Release 6), 3GPP TR 25.896 V1.0.2 (Oct. 2003). |
Ericsson et al., “Hybrid ARQ text proposal for Section 7 of TR25.896” TSG-RAN WG1 #31, R1-030208, Tokyo, Japan, 4 pages (Feb. 18-21, 2002). |
ETSI, UMTS XX.15 V0.3.0, UTRA Handover, 22 pp. (Jan. 1999). |
Heck et al., “Diversity Effects on the Soft Handover Gain in UMTS Networks,” Proceedings of the IEEE Vehicular Technology Conference, vol. 2, pp. 1269-1273 (Sep. 2002). |
Interdigital, “Performance Analysis of HARQ in Soft Handover,” 3GPP TSG-RAN WG1 #34 meeting, R1-030979 (Oct. 6-10, 2003). |
Motorola, “Improvements to Site Selection Diversity Transmission (SSDT)”, TSG-RAN Working Group 1 Meeting #3, 22-26, Stockholm, Sweden, pp. 1-5 (Mar. 1999). |
Panasonic, “Harq Operation During Soft Handover,” 3GPP TSG-RAN WG1 Meeting #33 R1-030802, 3GPP, (Aug. 25, 2003). |
Qualcomm, “Impact of Downlink Support Channels,” 3GPP TSG RAN WG1 #32, Tdoc R1-03-0433, Paris, France (May 19-23, 2003). |
Qualcomm, “Channel Structure for Consideration in Enhanced Uplink” 3GPP TSG RAN WG1 #31, Tdoc R1-03-0273 Tokyo, Japan, (Feb. 18-21, 2003). |
R1-030733, “HARQ overhead issues”, Nokia, TSG-RAN1 #33 (Aug. 25-29, 2003). |
R1-030765, “HARQ performance in soft handover”, Samsung, TSG RAN1 #33 (Aug. 25-29, 2003). |
R1-030803, “HARQ operation during Soft Handover”, Panasonic, TSG RAN1 #33 (2003). |
Samsung Electronics, “Harq Structure” 3GPP TSG-RAN WG1 #31 Meeting R1-030247, (Feb. 17, 2003). |
Samsung, “Transport Channel Multiplexing Options Considering SHO,” 3GPP TSG RAN WG1 #33 R1-030767, (Aug. 20, 2003). |
Ericsson, “E-DCH multiplexing and transport channel structure,” TSG-RAN Working Group 2 meeting #42, Tdoc R2-040917, Montreal, Canada, (May 2004). |
Holma et al., “WCDMA for UMTS—Radio Access for Third Generation Mobile Communications,” First Edition, (2000). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub Interface User Plane Protocols for Common Transport Channel data streams (Release 5),” 3GPP TS 25.435 V5.5.0 (Jun. 2003). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN lub Interface User Plane Protocols for Common Transport Channel data streams (Release 6),” 3GPP TS 25.435 V6.1.0 (Mar. 2004). |
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio resource management strategies (Release 5),” 3GPP TR 25.922 V5.0.0 (Mar. 2002). |
Universal Mobile Telecommunications System (UMTS); “Radio resource management strategies (3GPP TR 25.922 version 6.0.1 Release 6),” ETSI TR 125 922 V6.0.1 (Apr. 2004). |
Number | Date | Country | |
---|---|---|---|
20210068023 A1 | Mar 2021 | US |
Number | Date | Country | |
---|---|---|---|
60497747 | Aug 2003 | US | |
60507554 | Oct 2003 | US | |
60508797 | Oct 2003 | US | |
60520207 | Nov 2003 | US | |
60585174 | Jul 2004 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17008178 | Aug 2020 | US |
Child | 17099193 | US | |
Parent | 16533320 | Aug 2019 | US |
Child | 17008178 | US | |
Parent | 15212403 | Jul 2016 | US |
Child | 16533320 | US | |
Parent | 13236133 | Sep 2011 | US |
Child | 15212403 | US | |
Parent | 10925426 | Aug 2004 | US |
Child | 13236133 | US |