The present invention is related to a wireless communication system including at least one wireless transmit/receive unit (WTRU), at least one Node-B and a radio network controller (RNC). More particularly, the present invention is related to a method and apparatus for implementing a data lifespan timer for supporting enhanced dedicated channel (E-DCH) transmissions.
Methods for improving uplink (UL) coverage, throughput, and transmission latency are currently being investigated in Release 6 of the Third Generation Partnership Project (3GPP). In order to achieve these goals, the Node-B will take over responsibility of scheduling and assigning UL resources to WTRUs. The Node-B can make more efficient decisions and manage UL radio resources on a short-term basis better than an RNC. The RNC still retains coarse overall control of the cell with enhanced uplink (EU) services so that the RNC can perform functions such as call admission control and congestion control.
Hybrid-automatic repeat request (H-ARQ) techniques provide a procedure for generating transmissions and retransmissions with low latency. A primary aspect of H-ARQ techniques is that data received in failed transmissions is soft combined with successive retransmissions to increase the probability of successful reception.
When an H-ARQ scheme and Node-B scheduling of transmissions is used, the time required to successfully transmit data will vary. Applications requiring very low latency transmission can be adversely effected by significantly delayed transmissions. For example, delayed data may be considered to be a failed transmission and end up being unnecessarily retransmitted by the application. Therefore, a mechanism that limits transmission latency is required.
The present invention is implemented in a wireless communication system which supports E-DCH data transmissions. The wireless communication system includes a wireless transmit/receive unit (WTRU), at least one Node-B and a radio network controller (RNC). The WTRU includes a data buffer, a data lifespan timer, a data retransmission counter, a hybrid-automatic repeat request (H-ARQ) process and a controller. The lifespan timer establishes a lifespan for at least one data block stored in the buffer. The WTRU is configured to (i) periodically determine whether the lifespan timer has expired, (ii) determine whether the data block was previously transmitted, (iii) determine whether the lifespan timer is close to expiration, and (iv) determine whether physical resources have been allocated. If physical resources have not been allocated for a data block associated with a lifespan timer that is close to expiration, the WTRU sends an urgent channel allocation request to the Node-B. If physical resources have been allocated, the data block is prioritized for transmission with respect to other data blocks. The data block is discarded if the lifespan timer expires or if the WTRU receives feedback information indicating that the data block was successfully received by the Node-B.
A more detailed understanding of the invention may be had from the following description of a preferred embodiment, given by way of example and to be understood in conjunction with the accompanying drawing wherein:
Hereafter, the terminology “WTRU” includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a 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, a site controller, an access point or any other type of interfacing device in a wireless environment.
The features of the present invention may be incorporated into an integrated circuit (IC) or be configured in a circuit comprising a multitude of interconnecting components.
The RNC 106 controls overall EU operation of the system 100 by configuring EU parameters for the Node-B 104 and the WTRU 102 such as the lifespan time for transport channel (TrCH) or logical channel data, initial transmit power level, maximum allowed EU transmit power or available channel resources per Node-B 104. E-DCH is established for supporting EU transmissions between the WTRU 102 and the Node-B 104.
For the E-DCH transmissions, the WTRU 102 sends a channel allocation request to the Node-B 104 via a UL EU signaling channel 110. The channel allocation request, (or other UL EU signaling), may be transmitted via the E-DCH 108 instead of the UL EU signaling channel 110. In response, the Node-B 104 sends channel allocation information to the WTRU 102 via a downlink (DL) EU signaling channel 112. After EU radio resources are allocated for the WTRU 102, the WTRU 102 transmits data via an E-DCH 108. In response to the E-DCH data transmission, the Node-B 104 sends an acknowledgement (ACK) or non-acknowledgement (NACK) message for H-ARQ operation via the DL EU signaling channel 112.
When a new data block is received for transmission via the E-DCH 108, the controller 122 activates a data lifespan timer 124 for the data block, associates an H-ARQ process 128 with the data block and the new data block waits in the buffer 126 (step 202). The RNC configures the data lifespan for each E-DCH TrCH or for each E-DCH logical channel. Upon reception in MAC or RLC for UL transmission the timer is initialized for each transmission.
The value of E-DCH data lifespan timer 124 may be determined by the controller 122 in the WTRU 102 considering several factors such as maximum allowed transmission latency, RLC configuration, and the TrCH block error ratio (BLER) requirement, or the like. For example, the maximum allowed latency determines how long the data can be buffered before delivery. Furthermore, the BLER determines the number of H-ARQ retransmissions which effect transmission latency. The value assigned to the data lifespan timer 124 may also take into account WTRU data processing external to a medium access control entity for EU (MAC-e) in the WTRU 102.
Application protocols, (e.g., TCP/IP), require minimal transmission latency and variance in transmission latency to achieve maximum throughput. When transmission delays occur, data is expected to be failed and discarded, not delayed and retransmitted. This results in an inefficient behavior of the application.
For each TTI at step 204, the controller 122 determines whether the data lifespan timer 124 for the data block in the buffer 126 of the WTRU 102 has expired (step 206). If the data lifespan timer 124 has expired, the controller 122 discards the data block and releases the associated H-ARQ process 128 (step 208). The WTRU 102 may report this event to either the RNC 106 or the Node-B 104 (step 210). The WTRU 102 may further report to the Node-B 104 that physical resources allocations are not sufficient by sending a channel allocation request with a unique indication.
Referring back to step 206, if the data lifespan timer 124 for the data block has not expired, the controller 122 determines whether the data block in the buffer 126 of the WTRU 102 was previously transmitted by the WTRU 102 (step 212). If the data block had been previously transmitted, it is further determined whether data feedback information associated with the data block was received from the Node-B 104 (step 214). If an acknowledgement (ACK) message indicating successful transmission of the data block is received, the data block is discarded from the buffer 126, the associated H-ARQ process 128 becomes available for supporting another data block and the data lifespan timer is reset (step 216). If no feedback message is received, the WTRU 102 waits for the feedback message until the next TTI (step 218).
If, at step 212, it is determined that the data block had not been previously transmitted by the WTRU 102, or that the data block has been transmitted but a non-acknowledgement (NACK) message indicating unsuccessful transmission of the data block is received, the data block is retransmitted. The controller 122 determines whether the data lifespan timer 124 for the data block is close to expiration (step 220). If the data lifespan timer 124 is not close to expiration, a normal H-ARQ operation is initiated for transmitting the data block (step 222).
In step 224, the controller 122 determines whether physical resources have been allocated when the data lifespan timer 124 is close to expiration (step 224). If physical resources have been allocated, the controller 122 may optionally prioritize transmission of the data block (step 226). If physical resources have not been allocated, the controller 122 may optionally send an urgent channel allocation request to the Node-B for supporting the transmission of the data block (step 228).
Referring back to step 214, if a NACK message has been received, the data block is retransmitted, the controller 122 may determine whether the retransmission counter 130 has reached a maximum retransmission limit (step 230). The retransmission counter 130 is incremented each time the data block is retransmitted, and the maximum retransmission limit is configured by the RNC 106. If the retransmission counter 130 does not reach the maximum retransmission limit, the process 200 proceeds to step 220. If the retransmission counter 130 reaches the maximum retransmission limit, the controller 122 reinitializes the H-ARQ process 128 as long as the data lifespan timer 124 for the data block has not expired (step 232). The retransmission counter 130 is initialized and a new data indicator is incremented to indicate re-initiation of the H-ARQ process 128.
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. 12/652,082, filed Jan. 5, 2010, which is a continuation of U.S. patent application Ser. No. 11/117,579, filed Apr. 28, 2005, now U.S. Pat. No. 7,643,419, which claims the benefit of U.S. Provisional Application No. 60/568,937, filed May 7, 2004, which are incorporated by reference as if fully set forth.
Number | Name | Date | Kind |
---|---|---|---|
6424625 | Larsson et al. | Jul 2002 | B1 |
6519223 | Wager et al. | Feb 2003 | B1 |
6628946 | Wiberg et al. | Sep 2003 | B1 |
6665416 | Choi | Dec 2003 | B1 |
6901063 | Vayanos et al. | May 2005 | B2 |
6952411 | Sinnarajah et al. | Oct 2005 | B2 |
6987780 | Wei et al. | Jan 2006 | B2 |
7061913 | Abrol et al. | Jun 2006 | B1 |
7161916 | Malladi et al. | Jan 2007 | B2 |
7164904 | Nagy | Jan 2007 | B2 |
7197313 | Sohn | Mar 2007 | B1 |
7260401 | Chen et al. | Aug 2007 | B2 |
7301988 | Kanterakis | Nov 2007 | B2 |
7366477 | Sebire et al. | Apr 2008 | B2 |
7436795 | Jiang | Oct 2008 | B2 |
7436834 | Zhang | Oct 2008 | B1 |
7505774 | Trott | Mar 2009 | B1 |
7512051 | Hayashi | Mar 2009 | B2 |
7545765 | Larsson et al. | Jun 2009 | B2 |
8094647 | Elliott | Jan 2012 | B2 |
20020015419 | Kim et al. | Feb 2002 | A1 |
20020172208 | Malkamaki | Nov 2002 | A1 |
20030095519 | Kuo et al. | May 2003 | A1 |
20030112824 | Acosta | Jun 2003 | A1 |
20030123403 | Jiang | Jul 2003 | A1 |
20030147348 | Jiang | Aug 2003 | A1 |
20030210669 | Vayanos et al. | Nov 2003 | A1 |
20030214935 | Khan et al. | Nov 2003 | A1 |
20040037224 | Choi et al. | Feb 2004 | A1 |
20040037327 | Torsner et al. | Feb 2004 | A1 |
20040156332 | Terry et al. | Aug 2004 | A1 |
20040208160 | Petrovic et al. | Oct 2004 | A1 |
20040252658 | Hosein et al. | Dec 2004 | A1 |
20050149470 | Fujie | Jul 2005 | A1 |
20050207359 | Hwang et al. | Sep 2005 | A1 |
20070008990 | Torsner | Jan 2007 | A1 |
20130107837 | Terry | May 2013 | A1 |
Number | Date | Country |
---|---|---|
1 447 943 | Aug 2004 | EP |
1 838 057 | Sep 2007 | EP |
10-056480 | Feb 1998 | JP |
11-331261 | Nov 1999 | JP |
2001-197078 | Jul 2001 | JP |
2003-078565 | Mar 2003 | JP |
2003-244087 | Aug 2003 | JP |
0060799 | Oct 2000 | WO |
0199353 | Dec 2001 | WO |
03039074 | May 2003 | WO |
03058852 | Jul 2003 | WO |
04049648 | Jun 2004 | WO |
04073273 | Aug 2004 | WO |
Entry |
---|
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.S0003-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.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 c, Jul. 23, 2004. |
Motorola et al., “AH64: Text proposal for the TR—Section 7.5,” 3GPPRAN1#31, R1-03-0359, Tokyo, Japan (Feb. 18-21, 2003). |
Nokia, “Enhanced Uplink DCH,” TSG-RAN WG1 #31 meeting, R1-03-0176, Tokyo, Japan (Feb. 18-21. 2003). |
Samsung, “Relationship between scheduling and HARQ,” 3GPP TSG-RAN WG1 #35 Meeting, R1-031224, Lisbon, Portugal (Nov. 17-21, 2003). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; FDD Enhanced Uplink; Overall description; Stage 2 (Release 6),” 3GPP TS 25.309 V6.2.0 (Mar. 2005). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 1999),” 3GPP TS 25.321 V3.16.0 (Sep. 2003). |
Third 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). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 4),” 3GPP TS 25.321 V4.9.0 (Sep. 2003). |
Third 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). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 6),” 3GPP TS 25.321 V6.1.0 (Mar. 2004). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 6),” 3GPP TS 25.321 V6.4.0 (Mar. 2005). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 5),” 3GPP TS 25.321 V5.8.0 (Mar. 2004). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 5),” 3GPP TS 25.321 V5.10.0 (Dec. 2004). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (TDD) (Release 6),” 3GPP TS 25.221 V6.3.0 (Mar. 2005). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (TDD) (Release 6),” 3GPP TS 25.221 V6.0.0 (Dec. 2003). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (TDD) (Release 5),” 3GPP TS 25.221 V5.5.0 (Jun. 2003). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (TDD) (Release 4),” 3GPP TS 25.221 V4.7.0 (Dec. 2002). |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (TDD) (Release 1999),” 3GPP TS 25.221 V3.11.0 (Sep. 2002). |
Number | Date | Country | |
---|---|---|---|
20180041313 A1 | Feb 2018 | US |
Number | Date | Country | |
---|---|---|---|
60568937 | May 2004 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12652082 | Jan 2010 | US |
Child | 15783772 | US | |
Parent | 11117579 | Apr 2005 | US |
Child | 12652082 | US |