Patent Grant
RE44797
The exemplary and non-limiting embodiments of this invention relate generally to wireless communication systems, apparatus and methods and, more specifically, relate to wireless communication system techniques for enabling the grant of uplink resources to user equipment.
The following abbreviations are defined as follows:
Of interest herein is the uplink DCH (EDCH) for packet data traffic in, for example, Release 6 of 3 GPP TS 25.309, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; FDD Enhanced Uplink; Overall Description; Stage 2 (Release 6), which is attached to the incorporated provisional patent application as Exhibit A.
In HSUPA, certain attempts at enhancements are currently approached by distributing some of the packet scheduler functionality to the Node-Bs to provide faster scheduling of bursty, non-real-time traffic than can be provided by the Layer 3 (L3, Network Layer) of the RNC. The idea is that with faster link adaptation it is possible to more efficiently share the uplink power resource between packet data users, as when packets have been transmitted from one user the scheduled resource can be made available immediately to another user. This technique attempts to avoid the peaked variability of noise rise, such as when high data rates are being allocated to users that are running bursty, high data-rate applications.
In the current architecture, the packet scheduler is located in the RNC and therefore is limited in its ability to adapt to the instantaneous traffic, because of bandwidth constraints on the RRC signaling interface between the RNC and the UE. Hence, to accommodate the variability, the packet scheduler must be conservative in allocating uplink power to take into account the influence from inactive users in the following scheduling period. This solution can be spectrally inefficient for high allocated data-rates and long release timer values.
Thus, with E-DCH much of the packet scheduler functionality is transferred to the Node-B, i.e., there is a Node-B scheduler that is responsible for allocating uplink resources.
For transmission of data, the UE selects a TFC that suits the amount of data to be transmitted in a RLC buffer of the UE, subject to constraints on the maximum transmission power of the UE and the maximum power allowed by the Node-B scheduler.
As is currently described in subclause 3.1.2 of 3GPP TS 25.321, V6.8.0 (2006-03), “Medium Access Control (MAC) protocol specification” (attached to the incorporated provisional patent application in its entirety as Exhibit B), the state variable Serving_Grant indicates the maximum E-DPDCH to DPCCH power ratio that the UE 10 is allowed to use for scheduled data in the following transmission. The value in the appropriate state variable is provided to an E-TFC selection function to help in selecting the best format for the upcoming transmission. Possible values are: “Zero_Grant” and numerical values.
For efficient Node-B scheduling, some information is required from the UE, including the UE buffer status (e.g. how full it is), power status (e.g., how much power remains), and priority information regarding MAC-d flows or logical channels that are being used. All of this information is collectively referred to as the SI and is carried in the UL. Based on the SI, the Node-B decides whether to grant or not grant additional resources by responding with (data) rate grant messages in DL serving relative grant (RG) messages or absolute grant (AG) messages.
More specifically, 3GPP TS 25.321 defines UL Scheduling Information in subclause 9.2.5.3 as follows.
The Scheduling Information is located at the end of the MAC-e PDU and is used to provide the serving Node-B with a better view of the amount of system resources needed by the UE and the amount of resources it can actually make use of. The transmission of this information will be initiated due to the quantization of the transport block sizes that can be supported or based on the triggers defined in subclause 11.8.1.6. When a Scheduling Information is transmitted, its contents shall always be updated in new transmissions with the buffer status after application of the E-TFC selection procedure described in subclause 11.8.1.4. The logical channels for which a non-scheduled grant is configured shall never be taken into account when putting together this information. In addition, the RRC may restrict applicability for logical channels for which no non-scheduled grant was configured.
This information includes the following fields:
Highest priority Logical channel ID (HLID): The HLID field identifies unambiguously the highest priority logical channel with available data. If multiple logical channels exist with the highest priority, the one corresponding to the highest buffer occupancy will be reported. The length of the HLID is 4 bits. In case the TEBS is indicating index 0 (0 byte), the HLID shall indicate the value “0000”.
Fields related to amount of available data:
Total E-DCH Buffer Status (TEBS): The TEBS field identifies the total amount of data available across all logical channels for which reporting has been requested by the RRC and indicates the amount of data in number of bytes that is available for transmission and retransmission in RLC layer. When MAC is connected to an AM RLC entity, control PDUs to be transmitted and RLC PDUs outside the RLC Tx window shall also be included in the TEBS. RLC PDUs that have been transmitted but not negatively acknowledged by the peer entity shall not be included in the TEBS.
The length of this field is 5 bits. The values taken by TEBS are shown in Table 9.2.5.3.2.1.
Highest priority Logical channel Buffer Status (HLBS): The HLBS field indicates the amount of data available from the logical channel identified by HLID, relative to the highest value of the buffer size range reported by TEBS when the reported TEBS index is not 31, and relative to 50000 bytes when the reported TEBS index is 31. The length of HLBS is 4 bits. The values taken by HLBS are shown in table 9.2.5.3.2.2. In case the TEBS field is indicating index 0 (0 byte), the HLBS field shall indicate index 0.
UE Power Headroom (UPH): The UPH field indicates the ratio of the maximum UE transmission power and the corresponding DPCCH code power defined in 3GPP TS 25.215 “Physical Layer-Measurements (FDD)”. The length of UPH is 5 bits.
As is currently described in 3GPP TS 25.321 the serving RG messages are taken into account by the UE if there was a scheduled transmission in the previous TTI of the HARQ process. This specified procedure does not address a transmission in the previous TTI where there was SI only.
The foregoing and other problems are overcome by the use of the exemplary embodiments of this invention.
In an aspect the exemplary embodiments of this invention provide a method, a computer program product and a device operable, in response to operation during a baseline procedure when no absolute grant is received from a wireless network node, to determine if there was a scheduled transmission in a previous transmission time interval of a hybrid automatic repeat request process and, if there was, to use a serving relative grant; and if it is determined instead that there was not a scheduled transmission in the previous transmission time interval of the hybrid automatic repeat request process, to not use the serving relative grant if it is determined that there was a scheduling information event alone in the previous transmission time interval of the hybrid automatic repeat request process.
In accordance with another embodiment is a method to operate a wireless user equipment. In this method, in response to operation during a baseline procedure when no absolute grant is received from a wireless network node, it is determined if there was a scheduled transmission in a previous transmission time interval of a hybrid automatic repeat request process and, if there was, using a serving relative grant. Also, if it is determined instead that there was not a scheduled transmission in the previous transmission time interval of the hybrid automatic repeat request process, the serving relative grant is used if it is determined that there was a scheduling information event in the previous transmission time interval of the hybrid automatic repeat request process.
In accordance with another embodiment of the invention is a computer program product embodied in a computer readable medium and comprising instructions the execution of which by a data processor of a wireless user equipment results in performing operations that include, in response to operation during a baseline procedure when no absolute grant is received from a wireless network node, determining if there was a scheduled transmission in a previous transmission time interval of a hybrid automatic repeat request process. If it is determined that there was, then a serving relative grant is used. If it is determined instead that there was not a scheduled transmission in the previous transmission time interval of the hybrid automatic repeat request process, then the serving relative grant is used if it is determined that there was a scheduling information event in the previous transmission time interval of the hybrid automatic repeat request process.
In yet another embodiment of the invention is a wireless user equipment that includes a wireless transceiver for communication with a wireless network node. Coupled to the wireless transceiver is a means, responsive to operation during a baseline procedure when no absolute grant is received from the wireless network node, for using a serving relative grant after determining: (a) that there was a scheduled transmission in a previous transmission time interval of a hybrid automatic repeat request process; or, if there was not a scheduled transmission in the previous transmission time interval of the hybrid automatic repeat request process, (b) that there was a scheduling information event in the previous transmission time interval of the hybrid automatic repeat request process.
These and other aspects are detailed further below and with reference to the drawings.
Reference is made first to
In general, the various embodiments of the UE 10 can include, but are not limited to, cellular telephones, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, as well as portable units or terminals that incorporate combinations of such functions.
The exemplary embodiments of this invention may be implemented by computer software executable by the DP 10A of the UE 10 and the other DPs, or by hardware, or by a combination of software and hardware.
The MEMs 10B, 12B and 14B may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The DPs 10A, 12A and 14A may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multicore processor architecture, as non-limiting examples.
In accordance with the exemplary embodiments of this invention, the problems discussed previously are overcome by providing that when the SI is sent alone (i.e., without scheduled data), the SI is used as a reference for disregarding the serving RG. That is, the serving RG are made inapplicable for those cases where only the SI was sent by the UE 10 in the previous TTI of the process.
As is presently provided for in 3GPP TS 25.321 in Clause 11.8, entitled Control of E-DCH transmission and reception, Subclause 11.8.1, entitled UE operation, subclause 11.8.1.3, entitled Serving Grant Update, and more specifically in subclause 11.8.1.3.1, entitled Baseline Procedure:
The Serving Grant Update procedure shall be applied at every TTI boundary and shall take into account the Absolute Grant message, Serving Relative Grant and non-serving Relative Grants that apply to the TTI.
The UE shall:
The text above indicated in italic bold is the portion of subclause 11.8.1.3.1 of most concern to the exemplary embodiments of this invention.
Related to the portion of the foregoing that is of most interest to the exemplary embodiments of this invention, 3GPP TS 25.321 defines in subclause 3.1.2 the AG-Time as a timer (10E in
The referenced subclause 9.2.5.2.1 is directed to Relative Grants, and defines same as follows.
Serving Relative Grant: Transmitted on the downlink on the E-RGCH from all cells in the serving E-DCH RLS, the serving relative grant allows the Node-B scheduler to incrementally adjust the serving grant of UEs under its control. By definition, there can only be one serving relative grant command received at any one time. This indication can take three different values, “UP”, “DOWN” or “HOLD”.
Non-serving Relative Grant: Transmitted on downlink on the E-RGCH front a non-serving E-DCH RL, the non-serving relative grant allows neighboring Node-Bs to adjust the transmitted rate of UEs that are not under their control in order to avoid overload situations. By definition, there could be multiple non-serving relative grant commands received by MAC at any time. This indication can take two different values, “DOWN” or “HOLD”.
It is no that the Absolute Grant is defined in subclause 9.2.5.2.2 as follows.
The absolute grant message is sent on downlink, on the configured E-AGCH, from the serving E-DCH cell and allows the Node-B scheduler to directly adjust the granted rate of UEs under its control. The E-AGCH is a shared channel that uses an E-RNTI specific CRC in order to address messages to specific users. The RRC may configure the MAC-e with two different E-RNTIs, one primary and one secondary. Based on the identity that is used, the following information will be conveyed implicitly when an absolute grant message is received:
Identity Type: This variable will take the value “Primary” or “Secondary” respectively based on whether the message was addressed to the primary or the secondary E-RNTI.
The absolute grant message itself includes multiple fields that are multiplexed together into 6 bits inside the MAC-e of the Node-B and then submitted to the physical layer for transmission on the E-AGCH. These fields are:
Absolute Grant Value: This field indicates the maximum E-DCH traffic to pilot ratio (E-DPDCH/DPCCH) that the UE is allowed to use in the next transmission. The length of the Absolute Grant Value field is 5 bits.
Absolute Grant Scope: This field indicates the applicability of the Absolute Grant. It can take two different values, “Per HARQ process” or “All HARQ processes”, allowing to indicate whether the HARQ process activation/de-activation will affect one or all processes. The Absolute Grant Scope is encoded in 1 bit, When the E-DCH is configured with 10 ms TTI, only the value “All HARQ processes” is valid (see subclause 10). In case Identity Type is “Secondary”, only the value “All HARQ processes” is valid in this version of the protocol.
In accordance with a first exemplary embodiment of this invention the emphasized portion of the Baseline Procedure of subclause 11.8.1.3.1, specifically:
is modified as follows (only the modification is shown in bold italics):
In this case the presence of the Scheduling Information (alone) is used to exclude taking into account the serving RG by the UE 10.
In accordance with a second exemplary embodiment of this invention the emphasized portion of the Baseline Procedure of subclause 11.8.1.3.1 (again specifically):
is modified as follows (only the modification is shown in bold italics):
In this case the presence of the Scheduling Information without scheduled data is added as a trigger for taking into account the serving RG by the UE 10.
In accordance with these two exemplary embodiments the presence of Scheduling Information sent alone, and Scheduling Information, sent with non-scheduled data (and without scheduled data), may be used as a decision criteria for whether or not the UE 10 takes into account the serving RG, and thus whether the UE 10 is or is not required to revert to the use of the AG under these conditions.
Referring to
Referring to
A clear advantage of the use of the exemplary embodiments of the invention is that the usefulness of the RG signaling is maximized.
Based on the foregoing it should be apparent that the exemplary embodiments of this invention provide a method, apparatus and computer program product(s) to operate the UE 10 during a Baseline Procedure, when no Absolute Grant is received, to determine if there was a scheduled transmission in the previous TTI of the HARQ process or if there was a SI, alone or with non-scheduled data and without scheduled data, in the previous TTI of the HARQ process, and if so, to use the Serving Relevant Grant.
It is noted that it is within the scope of the exemplary embodiments of this invention to not allow the E-RGCH (i.e., for the UE 10 to not use the Serving Relative Grant) if a SI is sent alone by the UE 10
That is, it is within the scope of the exemplary embodiments of this invention to operate the UE 10 such that, in response to operation during a Baseline Procedure when no Absolute Grant is received from the wireless network node (e.g., from the Node-B), to determine if there was a scheduled transmission in a previous transmission time interval of a Hybrid Automatic Repeat Request process and, if there was, to use a Serving Relative Grant and, if it is determined instead that there was not a scheduled transmission in the previous transmission time interval of the Hybrid Automatic Repeat Request process, to not use the Serving Relative Grant if it is determined that there was a Scheduling Information event alone in the previous transmission time interval of the Hybrid Automatic Repeat Request process.
It is also within the scope of this invention to use the E-RGCH (i.e., for the UE 10 to use the Serving Relative Grant) if a SI is sent alone by the UE 10, or if SI is sent with unscheduled data by the US 10. Embodiments for this aspect may be a method, a computer program product, and a wireless user equipment as detailed above.
In general, the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the exemplary embodiments of this invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
The exemplary embodiments of the inventions may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.
Programs, such as those provided by Synopsys, Inc. of Mountain View, Calif. and Cadence Design, of San Jose, Calif. automatically route conductors and locate components on a semiconductor chip using well established rules of design as well as libraries of pre-stored design modules. Once the design for a semiconductor circuit has been completed, the resultant design, in a standardized electronic format (e.g., Opus, GDSII, or the like) may be transmitted to a semiconductor fabrication facility or “fab” for fabrication.
Various modifications and adaptations to the foregoing exemplary embodiments of this invention may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this invention.
Furthermore, some of the features of the various non-limiting and exemplary embodiments of this invention may be used to advantage without the corresponding use of other features. As such, the foregoing description should be considered as merely illustrative of the principles, teachings and exemplary embodiments of this invention, and not in limitation thereof.
This application is a reissue of U.S. patent application Ser. No. 11/788,540, filed Apr. 19, 2007, now issued as U.S. Pat. No. 7,693,156, claims priority to U.S. Provisional Patent Application No. 60/793,429, filed on Apr. 19, 2006 and hereby incorporatedincorporate all by reference in itstheir entirety, including exhibits.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7480269 | Heo et al. | Jan 2009 | B2 |
| 7551625 | Ahn et al. | Jun 2009 | B2 |
| 8081595 | Zhang et al. | Dec 2011 | B2 |
| 8271016 | Kwak et al. | Sep 2012 | B2 |
| 20070025300 | Terry et al. | Feb 2007 | A1 |
| 20070042785 | Nakamata | Feb 2007 | A1 |
| 20070054652 | Pan et al. | Mar 2007 | A1 |
| 20070218907 | Jiang | Sep 2007 | A1 |
| 20070297360 | Joachim et al. | Dec 2007 | A1 |
| 20080214197 | Englund et al. | Sep 2008 | A1 |
| 20080273483 | Zhang et al. | Nov 2008 | A1 |
| Entry |
|---|
| 3GPP TS 25.309, V6.6.0 (Mar. 2006), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; FDD Enhanced Uplink; Overall description; Stage 2 (Release 6), 34 pgs. |
| 3GPP TS 25.321, V7.0.0 (Mar. 2007), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 7), 94 pgs. |
| Number | Date | Country | |
|---|---|---|---|
| 60793429 | Apr 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11788540 | Apr 2007 | US |
| Child | 13440893 | US |
