WO2014056430A1

WO2014056430A1 - Methods and apparatus for transmission parameter control

Info

Publication number: WO2014056430A1
Application number: PCT/CN2013/084903
Authority: WO
Inventors: Insung Kang; Surendra Boppana; Shiau-He Tsai; Zhibin DANG; Aamod Dinkar Khandekar; Chao JIN
Original assignee: Qualcomm Incorporated
Priority date: 2012-10-10
Filing date: 2013-10-09
Publication date: 2014-04-17
Also published as: WO2014056158A1

Abstract

Methods and apparatus for communication comprise transmitting one or more data packets on an uplink channel to a network entity. The methods and apparatus further comprise receiving one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel. Additionally, the methods and apparatus comprise adjusting one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

Description

METHODS AND APPARATUS FOR TRANSMISSION PARAMETER

CONTROL

CLAIM OF PRIORITY

[0001] The present Application for Patent claims priority to International Patent

Application No. PCT/CN2012/082710 entitled "HIGH SPEED UPLINK PACKET ACCESS (HSUPA) POWER CONTROL" filed October 10, 2012 and International Patent Application No. PCT/CN2012/082698 entitled "HIGH SPEED UPLINK PACKET ACCESS (HSUPA) RATE CONTROL" filed October 10, 2012, both of which are assigned to the assignee hereof and hereby expressly incorporated by reference herein.

BACKGROUND

Field

[0002] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to controlling one or more transmission parameters for enhanced uplink communication.

Background

[0003] Wireless communication networks are widely deployed to provide various communication services such as telephony, video, data, messaging, broadcasts, and so on. Such networks, which are usually multiple access networks, support communications for multiple users by sharing the available network resources. One example of such a network is the Universal Terrestrial Radio Access Network (UTRAN). The UTRAN is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3 GPP). The UMTS, which is the successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as Wideband-Code Division Multiple Access (W-CDMA), Time Division-Code Division Multiple Access (TD-CDMA), and Time Division-Synchronous Code Division Multiple Access (TD-SCDMA). For example, China is pursuing TD- SCDMA as the underlying air interface in the UTRAN architecture with its existing GSM infrastructure as the core network. The UMTS also supports enhanced 3G data communications protocols, such as High Speed Downlink Packet Data (HSDPA), which provides higher data transfer speeds and capacity to associated UMTS networks.

[0004] As the demand for mobile broadband access continues to increase, research and development continue to advance the UMTS technologies not only to meet the growing demand for mobile broadband access, but to advance and enhance the user experience with mobile communications.

[0005] In some wireless communication networks, user equipment configuration by a network may result in significant degradations in wireless communication performance and quality. Further, in such scenarios, limitations may exist in remedying the degradations caused by poor or ineffective user equipment configuration by the network. Thus, improvements in transmission parameter management are desired.

SUMMARY

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] In one aspect, a method of communication comprises transmitting one or more data packets on an uplink channel to a network entity. The method further comprises receiving one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel. Moreover, the method comprises adjusting one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

[0008] Further aspects include an apparatus for communication comprising means for transmitting one or more data packets on an uplink channel to a network entity. The apparatus further comprises means for receiving one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel. Moreover, the apparatus comprises means for adjusting one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

[0009] In another aspect, a computer program product comprising a computer- readable medium including at least one instruction executable to cause a computer to transmit one or more data packets on an uplink channel to a network entity. The computer-readable medium further including at least one instruction executable to cause a computer to receive one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel. Moreover, the computer-readable medium includes at least one instruction executable to cause a computer to adjust one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

[0010] In an additional aspect, an apparatus comprising a memory storing executable instructions and at least one processor in communication with the memory, wherein the processor is configured to execute the instructions to transmit one or more data packets on an uplink channel to a network entity. The at least one processor id further configured to receive one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel. Moreover, the at least one processor is configured to adjust one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

[0011] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The features, nature, and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters identify correspondingly throughout and wherein:

[0013] Fig. 1 is a schematic diagram of a communication network including an aspect of a user equipment that may adjust one or more transmission parameters;

[0014] Fig. 2 is a schematic diagram of an aspect of the transmission adjustment component of Fig. 1;

[0015] Fig. 3 is a conceptual diagram of an aspect of a transmission parameter adjustment scheme, e.g., according to Fig. 1;

[0016] Fig. 4, is a conceptual diagram of another aspect of a transmission parameter adjustment scheme, e.g., according to Fig. 1;

[0017] Fig. 5 is a table diagram of an aspect of the adjustment features with respect to specific transmission parameters according to the aspects described herein;

[0018] Fig. 6 is a flowchart of an aspect of the transmission parameter adjustment features according to the aspects described herein;

[0019] Fig. 7 is a block diagram conceptually illustrating an example of a wireless communication system including an aspect of the user equipment and network entity described herein, e.g., according to Fig. 1;

[0020] Fig. 8 is a block diagram conceptually illustrating an example of a frame structure in a wireless communication system including an aspect of the user equipment and network entity described herein, e.g., according to Fig. 1; and

[0021] Fig. 9 is a block diagram conceptually illustrating an example of the network entity of Fig. 1, in communication with the user equipment of Fig. 1, in a wireless communication system.

DETAILED DESCRIPTION

[0022] The detailed description set forth below, in connection with the appended drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts. [0023] The present aspects generally relate to enhancements in management or control of one or more transmission parameters at a user equipment (UE). Specifically, transmission parameters may be provided by the network (e.g., via network entity) to the UE for configuration of one or more operational or communication (e.g., power, data rate, etc.) related characteristics of the UE. For example, the network may provide a transmission parameter including or in the form of a power control command to the UE in order to manage or control the output power of the UE during communication. In another example, the network may provide a transmission parameter including or in the form a data rate command in order to manage or control the uplink and/or downlink data rate at which UE may communicate with network entity. However, in some cases, the UE may not be permitted to control or adjust the transmission parameters (e.g., power, data rate, etc.) based on communication indications from the network and/or network entity.

[0024] For example, in the aspect where the transmission parameter includes or is in the form of a power control command, power control may be used by the base station and/or the UE to ensure that sufficient quality of service signals are received at the base station and/or the UE as the UE moves throughout the wireless communication system. For instance, the power at which a UE transmits uplink data in a high speed uplink packet access (HSUPA) system may be controlled by the network. In such cases, the network may send a power control command to the UE instructing the UE to transmit uplink data at an expected transmission power. The network may further send power control commands instructing the UE to increase/decrease the expected transmission power. Increasing or decreasing the expected transmit power may occur in discrete steps. For example, the power control command may instruct the UE to increase or decrease the expected transmit power by 1 dB.

[0025] In some aspects, power control commands received from the network are inconsistent with a block error rate (BLE ) associated with the UE. The BLER associated with the UE may be defined as a ratio of the number of erroneous blocks to the total number of blocks transmitted by the UE. For example, the network may send a power control command instructing the UE to decrease the expected transmit power even though network channel conditions are poor. Unfortunately, uplink throughput may deteriorate when the received power control commands are inconsistent with the BLER associated with the UE. [0026] Further, for instance, in the aspect where the transmission parameter includes or is in the form of a data rate command, the base station may limit the maximum data rate of uplink transmissions for each UE by providing a data rate command. This limitation may be based on, for example, the resource availability in the network and/or channel conditions. However, transmission by the UE at the maximum allowable data rate may not always result in optimal throughput for the uplink transmission.

[0027] As such, according to aspects of the present apparatus and methods, an implementation of a transmission parameter adjustment scheme may be made to enhance one or more corresponding communication or operational aspects of a UE. Accordingly, in some aspects, the present methods and apparatuses may provide an efficient solution, as compared to current solutions, to continuously adjust one or more transmission parameters (e.g., power, data rate, etc.) based on one or more network indications in order to improve overall communication quality.

[0028] Referring to Fig. 1, in one aspect, a wireless communication system 10 includes at least one UE 12 in communication coverage of at least one network entity, such as network entity 14. UE 12 may communicate 19 with network 16 by way of, for instance, network entity 14. Further, in such aspects, UE 12 may communicate with network entity via one or more communication channels 18. Such communication along or using one or more communication channels 18 may include, but is not limited to, one or more data packets 30, one or more acknowledgments 24, and one or more negative acknowledgments 26. In some non-limiting aspects, the one or more acknowledgments and/or negative acknowledgments may be in the form of messages/indications. Additionally, UE 12 may communicate with network entity 14 via the one or more communication channels 18 utilizing one or more radio access technologies (RATs) (e.g., TD-SCDMA). In such aspects, the one or more communication channels 18 may enable communication on both the uplink and downlink between UE 12 and network entity 14 to facilitate communication 19 with network 16.

[0029] Further, it should be understood that one or more communication channels 18 may include one or more high speed communication channels facilitating high speed communication on one or both the uplink and downlink. In aspects employing high speed communication, HSUPA operation allows UE 12 to transmit at high data rates upon a scheduling grant from the network entity 14. An enhanced dedicated transport channel (E-DCH) may be used to carry HSUPA data traffic. Four physical channels may be provided: E-PUCH (enhanced physical uplink channel), E-AGCH (E-DCH absolute grant channel), E-UCCH (E-DCH uplink control channel), and E-HICH (E- DCH HA Q (hybrid automatic repeat request) indicator channel).

[0030] E-PUCH is the uplink physical channel mapping to E-DCH. The E-PUCH may be used as a service channel by UE 12 to carry E-DCH transmission channel data. E-UCCH is the uplink physical channel carrying control information including an enhanced transport format combination identifier (E-TFCI) and power control (e.g., transmit power control (TPC) command). An E-TFCI may be a representation of communication data rate operation indicating, for instance, a transport block size. E- AGCH is the downlink physical channel carrying the serving network entity grant that allocates radio resources of E-PUCH (e.g., including power, timeslot and code). The E-HICH is a physical layer control channel used for a network entity (e.g., base station or NodeB) to carry hybrid automatic repeat request (HARQ) indication information.

[0031] According to the present aspects, UE 12 may include transmission adjustment component 20, which may be configured to adjust one or more transmission parameters 22 according to or based on one or more ACKs 24 and NACKs 26 received from network entity 14. For example, transmission adjustment component 20 may be configured to autonomously and continuously adjust one or more transmission parameters 22 including or related to the output power of UE 12 for subsequent communications of one or more data packets and/or a data rate based on whether an ACK 24 or a NACK 26 has been received by transmission adjustment component 20 for a previous communication of one or more data packets 30.

[0032] In an aspect, UE 12 may communicate with network entity 14 according to one or more transmission parameters 22. For example, the transmission parameters 22 may include a parameter configuring or controlling the output power of UE 12 during communication. In some cases, transmission adjustment component 20 may be configured to detect or otherwise determine whether to increase or decrease the one or more transmission parameters including or related to the output power based on an ACK 24 or a NACK 26. Further, in other cases, transmission adjustment component 20 may be configured to detect or otherwise determine whether to increase or decrease the one or more transmission parameters including or related to the data rate based on an ACK 24 or a NACK 26. As such, in order to maintain continuity in at least adequate wireless communication, and to avoid service limitations (e.g., high number of NACKs), UE 12 may engage in one or more adjustment of transmission parameters 22 according to at least one of an ACK 24 and/or a NACK 26. Further aspects of transmission adjustment component 20 are described herein with respect to Fig. 2.

[0033] UE 12 may include communication component 28, which may be configured to facilitate wireless communication with at least network entity 14. For example, communication component 28 may enable UE 12 to communicate with network entity 14 on one or more uplink and/or downlink data communication channels (e.g., communication channel 18). Further, communication on the one or more uplink and/or downlink communication channels may be conducted using time slots (e.g., time division multiplexing). Additionally, communication component 28 may be configured to transmit or receive one or more data packets 30, and optionally an ACK 24 and/or a NACK 26.

[0034] In some aspects, UE 12 may 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, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.

[0035] Additionally, network entity 14 may be a macrocell, picocell, femtocell, access point, wireless local access network, relay, Node B, mobile Node B, UE (e.g., communicating in peer-to-peer or ad-hoc mode with UE 12), or substantially any type of component that can communicate with UE 12 to provide wireless network access at the UE 12.

[0036] Referring to Fig. 2, an aspect of transmission adjustment component 20 may include various components and/or subcomponents, which may be configured to enhance high speed uplink communication by continuously monitoring communications from a network entity (e.g., network entity 14) for one or more ACKs 24 and NACKs 26 so as to accordingly adjust one or more transmission parameters 22. For example, transmission adjustment component 20 may be configured to initially receive one or more transmission parameters 22 from network entity 14 (e.g., via communication component 28).

[0037] In such an example, transmission adjustment component 20 may be configured to optionally receive transmit power control parameter 32. Transmit power control parameter 32 may configure UE 12 (Fig. 1) to communicate or operate according to a specified output power. Specifically, for instance, transmit power control parameter 32 may include or be in the form of a transmit power control (TPC) command supplied by network 16 (Fig. 1) via network entity 14 (Fig. 1) to control the output power by which UE 12 (e.g., communication component 28) may communicate with one or more connected network entities. In other words, transmit power control parameter 32 may control the amount of power by which UE 12, or more specifically, communication component 28, may transmit one or more data packets 30.

[0038] In order to better manage the power consumption of UE 12 (Fig. 1), transmit power control parameter 32 may be controlled according to or based on an ACK 24 and NACK 26. Specifically, for instance, following transmission of one or more data packets on an uplink channel to network entity 14 (Fig. 1), transmission adjustment component 20 may be configured to receive at least one of the ACK 24 and the NACK 26, indicating or signaling a successful or unsuccessful communication of one or more data packets. As such, transmission adjustment component 20 may be configured to adjust the transmit power control parameter 32 based at least in part on receiving one of the ACK 24 and the NACK 26 from the network entity 14 (Fig. 1).

[0039] For example, transmission adjustment component 20 may be configured to increase transmit power control parameter 32 in response to receiving the NACK 26 from network entity 14 (Fig. 1). In some aspects, increasing the transmit power control parameter may be based at least in part on a block error rate (BLE ). That is, the increase may be based on a ratio of a target BLER over a difference of an integer value and the target BLER (e.g., BLER_TARGET/1-BLER_TARGET). In other aspects, transmission adjustment component 20 may be configured to increase transmit power control parameter 32 (e.g., TPC), thereby increasing the output power of a subsequent communication when a NACK 26 is received. In such aspects, the increase may be based or according to a configurable db value (e.g., 1 db). Further, transmission adjustment component 20 may be configured to adjust transmit power control parameter 32 when the one or more data packets 30 (Fig. 1) comprise a new transmission of one or more data packets on the uplink channel to network entity 14 (Fig. 1).

[0040] In further aspects, transmission adjustment component 20 may be configured to optionally receive transport format parameter 34. Transport format parameter 34 may configure UE 12 (Fig. 1) to communicate or operate according to a specified data rate. Specifically, for instance, transmit power control parameter 32 may include or be in the form of an E-TFCI, which may be communicated over the E-UCCH uplink physical channel. An E-TFCI may indicate a maximum amount of data that is sent in each uplink transmission within, for instance, a transport block set size. However, transmission by UE 12 at the maximum allowable data rate may not always result in optimal throughput for the uplink transmission. As such, transmission adjustment component 20 may continuously monitor the communications from network entity 14 (Fig. 1) for an ACK 24 or a NACK 26 to adjust transport format parameter 34.

[0041] In order to better manage the power consumption and/or data rate of UE 12

(Fig. 1), transport format parameter 34 may be controlled according to or based on an ACK 24 and NACK 26. Specifically, for instance, following transmission of one or more data packets on an uplink channel to network entity 14 (Fig. 1), transmission adjustment component 20 may be configured to receive at least one of the ACK 24 and the NACK 26, indicating or signaling a successful or unsuccessful communication of one or more data packets. As such, transmission adjustment component 20 may be configured to adjust the transport format parameter 34 based at least in part on receiving one of the ACK 24 and the NACK 26 from the network entity 14 (Fig. 1).

[0042] For example, transmission adjustment component 20 may be configured to increase transport format parameter 34 in response to receiving the ACK 24 from network entity 14 (Fig. 1). In such aspects, increasing transport format parameter 34 may be based at least in part on the BLE . For instance, the increase may be based on the BLER (e.g., an increment value equal to BLER/(1-BLER)). Further, transmission adjustment component 20 may be configured to decrease transport format parameter 34 in response to receiving the NACK 26 from network entity 14 (Fig. 1). For instance, the decrease may be according to an integer value representing a step size (e.g., integer value of "1" representing a single unit). [0043] In further aspects, transmission adjustment component 20 may be configured to group one or more of transport format parameters (e.g., including transport format parameter 34) into one or more transport format parameter groups. In some aspects, each transport format parameter group comprises one or more transport format parameters (e.g., including transport format parameter 34) of an identical packet data unit (PDU) size. Moreover, transmission adjustment component 20 may then be configured to select a transport format parameter group from the one or more transport format parameter groups based at least on one of an ACK rate and a NACK rate. In such aspects, transmission adjustment component 20 may select the transport format parameter from the selected transport format parameter group having a lowest padding value (e.g., lowest number of dummy bits).

[0044] For example, in the non-limiting case where transport format parameter 34 includes or is in the form of an E-TFCI, consecutive E-TFCI communication data rates that are specified for a same amount of PDUs may be grouped together. In some aspects, transport format parameter 34 in the form of, for example, an E-TFCI, a data rate with the same amount of PDUs but with different amount of paddings may be grouped together, and as such, may have consecutive E-TFCIs. In this configuration, an uplink data rate (e.g., transport block set size specified in E-TFCI) may be selected based on data rates indexed by the grouping of the same amount of PDUs. As such, the uplink data rate may be selected based at least in part on an amount of padding within each of the consecutive communication data rates, or in other words, the data rates indexed by the grouping of the same amount of PDUs. Further, the uplink data rate may be selected based at least in part on an ACK/NACK rate. In one configuration, the E-TFCI with the least amount of padding is selected. Alternatively, or in addition, the uplink data rate for a current uplink transmission may be selected based on whether an ACK or a NACK was received for a previous uplink transmission. In this manner the uplink data rate is continually adjusted for each uplink transmission.

[0045] Referring to Fig. 3, an aspect of a transmit power control parameter adjustment scheme 40 is illustrated. For instance, UE 12 may initially, or at some point in time prior to the transmission of one or more first data packets 42, receive transmit power control parameter 32. As such, UE 12 may be initially configured to operate and/or communicate according to the power specifications specified by transmit power control parameter 32. In some aspects, transmit power control parameter 32 may be a TPC specifying a power command for UE 12.

[0046] In such aspects, UE 12 may transmit one or more first data packets 42 to network entity 14. Following transmission, network entity 14 may indicate to UE 12 a corresponding first ACK 46 or first NACK 47 which may indicate to UE 12 whether network entity 14 successfully received the one or more first data packets 42. Upon receiving first ACK 46 or first NACK 47, transmission adjustment component 20 may accordingly adjust the transmit power control parameter 32 (e.g., TPC). For example, transmission adjustment component 20 may decrease transmit power control parameter 32, thereby decreasing the output power used in a subsequent communication (e.g., one or more second data packets 44) when a first ACK 46 is received.

[0047] In some aspects, the decrease may be made when one or more first data packets 42 correspond to a new uplink transmission and the BLE (e.g., BLERTARGET/1-BLERTARGET))- On the other hand, transmission adjustment component 20 may increase transmit power control parameter 32 (e.g., TPC), thereby increasing the output power of a subsequent communication (e.g., one or more second data packets 44) when a first NACK 47 is received. In some aspects, the increase may be based or according to a configurable db value (e.g., 1 db). Moreover, continuous adjustments may be made according to subsequent transmissions of one or more data packets (e.g., one or more second data packets 44) and based on subsequent ACKs/NACKs (e.g., second ACK 48 and/or second NACK 49).

[0048] Referring to Fig. 4, an aspect of a transport format parameter adjustment scheme 50 is illustrated. For example, UE 12 may initially, or at some point in time prior to the transmission of one or more first data packets 52, receive transport format parameter 34. As such, UE 12 may be initially configured to operate and/or communicate according or at the data rate specified by transport format parameter 34. In some aspects, transport format parameter 34 may be an ETFCI including a transport block size indication specifying the block size in which UE 12 may communicate with network entity 14.

[0049] In such aspects, UE 12 may transmit one or more first data packets 52 to network entity 14. Following transmission, network entity 14 may indicate to UE 12 a corresponding first ACK 56 or first NACK 57 which may indicate to UE 12 whether network entity 14 successfully received the one or more first data packets 52. Upon receiving first ACK 56 or first NACK 57, transmission adjustment component 20 may accordingly adjust the transport format parameter 34 (e.g., transport block size). For example, transmission adjustment component 20 may increase transport format parameter 34, thereby increasing the transport block size of a subsequent communication (e.g., one or more second data packets 54) when a first ACK 56 is received.

[0050] In some aspects, the increase may be based on the BLE (e.g., an increment value equal to BLER/(1-BLER)). On the other hand, transmission adjustment component 20 may decrease transport format parameter 34, thereby decreasing the transport block size of a subsequent communication (e.g., one or more second data packets 54) when a first NACK 57 is received. In some aspects, the decrease may be according to an integer value representing a step size (e.g., integer value of "1" representing a single unit). Moreover, continuous adjustments may be made according to subsequent transmissions of one or more data packets (e.g., one or more second data packets 54) and based on subsequent ACKs/NACKs (e.g., second ACK 58 and/or second NACK 59).

[0051] Referring to Fig. 5, a table diagram 60 illustrates an aspect of a relationship between the one or more transmission parameters 22 (Figs. 1 and 2) and one or more ACKs 24 and/or NACKs received from a network entity. For example, the table diagram 60 may be implemented in or used to configure one or more components and/or subcomponents of transmission adjustment component 20. In such aspects, for instance, the relationships or features of table diagram 60 may be implemented as part of the transmission adjustment rules 36. It should be understood that the relationships demonstrated in table diagram 60 are non- limiting examples.

[0052] In an aspect, table diagram 60 demonstrates a relationship between transmit power control parameter 32 (e.g., TPC), ACK 24 and NACK 26. For instance, table diagram 60 indicates that when an ACK 24 is received from a network entity, transmission adjustment component 20 may decrease transmit power control parameter 32 (e.g., decrease output power). Further, when a NACK 26 is received from a network entity, transmission adjustment component 20 may increase transmit power control parameter (e.g., increase output power). In such aspects, the adjustments to transmit power control parameter 32 may be made to manage or control the output power of UE 12 (Fig. 1) during transmission of a subsequent communication (e.g., data packets) to a network entity.

[0053] In further aspects, table diagram 60 demonstrates a relationship between transport format parameter 34 (e.g., ETFCI), ACK 24 and NACK 26. For example, table diagram 60 indicates that when an ACK 24 is received from a network entity, transmission adjustment component 20 may increase transport format parameter 34 (e.g., increase transport block size). Moreover, when a NACK 26 is received from a network entity, transmission adjustment component 20 may decrease transport format parameter 34 (e.g., decrease transport block size). In such aspects, the adjustments to transport format parameter 34 may be made to manage or control the data rate (e.g., specified in ETFCI) during transmission of a subsequent communication (e.g., data packets) to a network entity.

[0054] Referring to Fig. 6, in operation, a UE such as UE 12 (Fig. 1) may perform one aspect of a method 70 for managing or controlling one or more transmission parameters. While, for purposes of simplicity of explanation, the methods herein are shown and described as a series of acts, it is to be understood and appreciated that the methods are not limited by the order of acts, as some acts may, in accordance with one or more aspects, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, it is to be appreciated that the methods could alternatively be represented as a series of interrelated states or events, such as in a state diagram.

[0055] Moreover, not all illustrated acts may be required to implement a method in accordance with one or more features described herein. As described in further detail below, the functional block diagram 70 provides a process tailored to avoid, or at least to reduce, service interruption experienced by UE 12 (Fig. 1) by continuously tuning or adjusting one or more transmission parameters based on feedback (e.g., ACK/NACK) from the network entity.

[0056] In an aspect, at block 72, method 70 includes transmitting one or more data packets on an uplink channel to a network entity. For example, as described herein, UE 12 (Fig. 1) may execute communication component 28 to transmit one or more data packets 30 on an uplink channel (e.g., communication channel 18) to the network entity 14. [0057] Moreover, at block 74, method 70 may include receiving one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel. For instance, as described herein, UE 12 (Fig. 1) may execute at least one of transmission adjustment component 20 and communication component 28 to receive one of an acknowledgement 24 and a negative acknowledgment 26 from the network entity 14 in response to transmitting the one or more data packets 30 on the uplink channel (e.g., communication channel 18).

[0058] In addition, at block 76, method 70 may include adjusting one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity. For example, as described herein, UE 12 (Fig. 1) may execute transmission adjustment component 20 to adjust one or more transmission parameters 22 based at least in part on receiving one of the acknowledgement 24 and the negative acknowledgment 26 from the network entity 14.

[0059] Turning now to Fig. 7, a block diagram is shown illustrating an example of a telecommunications system 200 in which UE 12 including transmission adjustment component 20, may operate, such as in the form of or as a part of UEs 210 and Node Bs 208. The various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards. By way of example and without limitation, the aspects of the present disclosure illustrated in Fig. 7 are presented with reference to a UMTS system employing a TD-SCDMA standard. In this example, the UMTS system includes a (radio access network) RAN 202 (e.g., UTRAN) that provides various wireless services including telephony, video, data, messaging, broadcasts, and/or other services.

[0060] The RAN 202 may be divided into a number of Radio Network Subsystems

(RNSs) such as an RNS 207, each controlled by a Radio Network Controller (RNC) such as an RNC 206. For clarity, only the RNC 206 and the RNS 207 are shown; however, the RAN 202 may include any number of RNCs and RNSs in addition to the RNC 206 and RNS 207. The RNC 206 is an apparatus responsible for, among other things, assigning, reconfiguring and releasing radio resources within the RNS 207. The RNC 206 may be interconnected to other RNCs (not shown) in the RAN 202 through various types of interfaces such as a direct physical connection, a virtual network, or the like, using any suitable transport network.

[0061] The geographic region covered by the RNS 207 may be divided into a number of cells, with a radio transceiver apparatus serving each cell. A radio transceiver apparatus is commonly referred to as a Node B in UMTS applications, but may also be referred to by those skilled in the art as a base station (BS), a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), or some other suitable terminology. For clarity, two Node Bs 208 are shown, however, the RNS 207 may include any number of wireless Node Bs. The Node Bs 208 provide wireless access points to a core network 204 for any number of mobile apparatuses.

[0062] initiation protocol (SIP) phone, a laptop, a notebook, a netbook, a smartbook, a personal digital assistant (PDA), a satellite radio, a global positioning system (GPS) device, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, or any other similar functioning device. The mobile apparatus is commonly referred to as user equipment (UE) in UMTS applications, but may also be referred to by those skilled in the art as a mobile station (MS), 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 (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. For illustrative purposes, three UEs 210 are shown in communication with the Node Bs 208, each of which may include transmission adjustment component 20 of UE 12 (Fig. 1). The downlink (DL), also called the forward link, refers to the communication link from a Node B to a UE, and the uplink (UL), also called the reverse link, refers to the communication link from a UE to a Node B.

[0063] The core network 204, as shown, includes a GSM core network. However, as those skilled in the art will recognize, the various concepts presented throughout this disclosure may be implemented in a RAN, or other suitable access network, to provide UEs with access to types of core networks other than GSM networks.

[0064] In this example, the core network 204 supports circuit-switched services with a mobile switching center (MSC) 212 and a gateway MSC (GMSC) 214. One or more RNCs, such as the RNC 206, may be connected to the MSC 212. The MSC 212 is an apparatus that controls call setup, call routing, and UE mobility functions. The MSC 212 also includes a visitor location register (VLR) (not shown) that contains subscriber-related information for the duration that a UE is in the coverage area of the MSC 212. The GMSC 214 provides a gateway through the MSC 212 for the UE to access a circuit-switched network 216. The GMSC 214 includes a home location register (HLR) (not shown) containing subscriber data, such as the data reflecting the details of the services to which a particular user has subscribed. The HLR is also associated with an authentication center (AuC) that contains subscriber-specific authentication data. When a call is received for a particular UE, the GMSC 214 queries the HLR to determine the UE's location and forwards the call to the particular MSC serving that location.

[0065] The core network 204 also supports packet-data services with a serving GPRS support node (SGSN) 218 and a gateway GPRS support node (GGSN) 220. GPRS, which stands for General Packet Radio Service, is designed to provide packet-data services at speeds higher than those available with standard GSM circuit-switched data services. The GGSN 220 provides a connection for the RAN 202 to a packet- based network 222. The packet-based network 222 may be the Internet, a private data network, or some other suitable packet-based network. The primary function of the GGSN 220 is to provide the UEs 210 with packet-based network connectivity. Data packets are transferred between the GGSN 220 and the UEs 210 through the SGSN 218, which performs primarily the same functions in the packet-based domain as the MSC 212 performs in the circuit-switched domain.

[0066] The UMTS air interface is a spread spectrum Direct-Sequence Code Division

Multiple Access (DS-CDMA) system. The spread spectrum DS-CDMA spreads user data over a much wider bandwidth through multiplication by a sequence of pseudorandom bits called chips. The TD-SCDMA standard is based on such direct sequence spread spectrum technology and additionally calls for a time division duplexing (TDD), rather than a frequency division duplexing (FDD) as used in many FDD mode UMTS/W-CDMA systems. TDD uses the same carrier frequency for both the uplink (UL) and downlink (DL) between a Node B 208 and a UE 210, but divides uplink and downlink transmissions into different time slots in the carrier. [0067] Fig. 8 shows a frame structure 250 for a TD-SCDMA carrier, which may be used in communications between UE 12 (Fig. 1) including transmission adjustment component 20 and at least one network entity (e.g., network entity 14, Fig. 1) discussed herein. The TD-SCDMA carrier, as illustrated, has a frame 252 that may be 10 ms in length. The frame 252 may have two 5 ms sub frames 254, and each of the subframes 254 includes seven time slots, TS0 through TS6. The first time slot, TS0, may be allocated for inter/intra frequency measurements and/or downlink communication, while the second time slot, TS1, may be allocated for uplink communication.

[0068] The remaining time slots, TS2 through TS6, may be used for either uplink or downlink, which allows for greater flexibility during times of higher data transmission times in either the uplink or downlink directions. A downlink pilot time slot (DwPTS) 256, a guard period (GP) 258, and an uplink pilot time slot (UpPTS) 260 (also known as the uplink pilot channel (UpPCH)) are located between TS0 and TS1. Each time slot, TS0-TS6, may allow data transmission multiplexed on a maximum of, for instance, 16 code channels. Data transmission on a code channel includes two data portions 262 separated by a midamble 264 and followed by a guard period (GP) 268. The midamble 264 may be used for features, such as channel estimation, while the GP 268 may be used to avoid inter-burst interference.

[0069] Fig. 9 is a block diagram of a Node B 310 in communication with a UE 350 in a RAN 300, where RAN 300 may be the same as or similar to RAN 202 in Fig. 7, the Node B 310 may be the same as or similar to Node B 208 in Fig. 7, and the UE 350 may be the same as or similar to UE 210 in Fig. 7 or the UE 12 in Fig. 1 including transmission adjustment component 20. In the downlink communication, a transmit processor 320 may receive data from a data source 312 and control signals from a controller/processor 340. The transmit processor 320 provides various signal processing functions for the data and control signals, as well as reference signals (e.g., pilot signals). For example, the transmit processor 320 may provide cyclic redundancy check (CRC) codes for error detection, coding and interleaving to facilitate forward error correction (FEC), mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), and the like), spreading with orthogonal variable spreading factors (OVSF), and multiplying with scrambling codes to produce a series of symbols.

[0070] Channel estimates from a channel processor 344 may be used by a controller/processor 340 to determine the coding, modulation, spreading, and/or scrambling schemes for the transmit processor 320. These channel estimates may be derived from a reference signal transmitted by the UE 350 or from feedback contained in the midamble 214 (Fig. 7) from the UE 350. The symbols generated by the transmit processor 320 are provided to a transmit frame processor 330 to create a frame structure. The transmit frame processor 330 creates this frame structure by multiplexing the symbols with a midamble 214 (Fig. 7) from the controller/processor 340, resulting in a series of frames. The frames are then provided to a transmitter 332, which provides various signal conditioning functions including amplifying, filtering, and modulating the frames onto a carrier for downlink transmission over the wireless medium through smart antennas 334. The smart antennas 334 may be implemented with beam steering bidirectional adaptive antenna arrays or other similar beam technologies.

[0071] At the UE 350, a receiver 354 receives the downlink transmission through an antenna 352 and processes the transmission to recover the information modulated onto the carrier. The information recovered by the receiver 354 is provided to a receive frame processor 360, which parses each frame, and provides the midamble 214 (Fig. 8) to a channel processor 394 and the data, control, and reference signals to a receive processor 370. The receive processor 370 then performs the inverse of the processing performed by the transmit processor 320 in the Node B 310. More specifically, the receive processor 370 descrambles and despreads the symbols, and then determines the most likely signal constellation points transmitted by the Node B 310 based on the modulation scheme.

[0072] These soft decisions may be based on channel estimates computed by the channel processor 394. The soft decisions are then decoded and deinterleaved to recover the data, control, and reference signals. The C C codes are then checked to determine whether the frames were successfully decoded. The data carried by the successfully decoded frames will then be provided to a data sink 372, which represents applications running in the UE 350 and/or various user interfaces (e.g., display). Control signals carried by successfully decoded frames will be provided to a controller/processor 390. When frames are unsuccessfully decoded by the receiver processor 370, the controller/processor 390 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.

[0073] In the uplink, data from a data source 378 and control signals from the controller/processor 390 are provided to a transmit processor 380. The data source 378 may represent applications running in the UE 350 and various user interfaces (e.g., keyboard). Similar to the functionality described in connection with the downlink transmission by the Node B 310, the transmit processor 380 provides various signal processing functions including C C codes, coding and interleaving to facilitate FEC, mapping to signal constellations, spreading with OVSFs, and scrambling to produce a series of symbols. Channel estimates, derived by the channel processor 394 from a reference signal transmitted by the Node B 310 or from feedback contained in the midamble transmitted by the Node B 310, may be used to select the appropriate coding, modulation, spreading, and/or scrambling schemes.

[0074] The symbols produced by the transmit processor 380 will be provided to a transmit frame processor 382 to create a frame structure. The transmit frame processor 382 creates this frame structure by multiplexing the symbols with a midamble 214 (FIG. 2) from the controller/processor 390, resulting in a series of frames. The frames are then provided to a transmitter 356, which provides various signal conditioning functions including amplification, filtering, and modulating the frames onto a carrier for uplink transmission over the wireless medium through the antenna 352.

[0075] The uplink transmission is processed at the Node B 310 in a manner similar to that described in connection with the receiver function at the UE 350. A receiver 335 receives the uplink transmission through the antenna 334 and processes the transmission to recover the information modulated onto the carrier. The information recovered by the receiver 335 is provided to a receive frame processor 336, which parses each frame, and provides the midamble 214 (Fig. 7) to the channel processor 344 and the data, control, and reference signals to a receive processor 338. The receive processor 338 performs the inverse of the processing performed by the transmit processor 380 in the UE 350. The data and control signals carried by the successfully decoded frames may then be provided to a data sink 339 and the controller/processor, respectively. If some of the frames were unsuccessfully decoded by the receive processor, the controller/processor 340 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.

[0076] The controller/processors 340 and 390 may be used to direct the operation at the Node B 310 and the UE 350, respectively. For example, the controller/processors 340 and 390 may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The computer readable media of memories 342 and 392 may store data and software for the Node B 310 and the UE 350, respectively. A scheduler/processor 346 at the Node B 310 may be used to allocate resources to the UEs and schedule downlink and/or uplink transmissions for the UEs.

[0077] Several aspects of a telecommunications system has been presented with reference to a TD-SCDMA system. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards. By way of example, various aspects may be extended to other UMTS systems such as W- CDMA, High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+) and TD-CDMA. Various aspects may also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD, or both modes), LTE-Advanced (LTE-A) (in FDD, TDD, or both modes), CDMA2000, Evolution-Data Optimized (EV-DO), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and/or other suitable systems. The actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0078] Several processors have been described in connection with various apparatuses and methods. These processors may be implemented using electronic hardware, computer software, or any combination thereof. Whether such processors are implemented as hardware or software will depend upon the particular application and overall design constraints imposed on the system. By way of example, a processor, any portion of a processor, or any combination of processors presented in this disclosure may be implemented with a microprocessor, microcontroller, digital signal processor (DSP), a field-programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable processing components configured to perform the various functions described throughout this disclosure. The functionality of a processor, any portion of a processor, or any combination of processors presented in this disclosure may be implemented with software being executed by a microprocessor, microcontroller, DSP, or other suitable platform.

[0079] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium. A computer- readable medium may include, by way of example, memory such as a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disc (CD), digital versatile disc (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, or a removable disk. Although memory is shown separate from the processors in the various aspects presented throughout this disclosure, the memory may be internal to the processors (e.g., cache or register).

[0080] Computer-readable media may be embodied in a computer-program product.

By way of example, a computer-program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0081] It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. A phrase referring to "at least one of a list of items refers to any combination of those items, including single members. As an example, "at least one of: a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §212, sixth paragraph, unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for."

Claims

CLAIMS What is claimed is:

1. A method of communication, comprising:

transmitting one or more data packets on an uplink channel to a network entity; receiving one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel; and

adjusting one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

2. The method of claim 1, wherein adjusting one or more transmission parameters comprise adjusting at least one of a transmit power control parameter and a transport format parameter.

3. The method of claim 2, wherein adjusting the transmit power control parameter comprises increasing the transmit power control parameter in response to receiving the negative acknowledgment from the network entity.

4. The method of claim 3, wherein increasing the transmit power control parameter is based at least in part on a block error rate.

5. The method of claim 2, wherein adjusting the transmit power control parameter comprises decreasing the transmit power control parameter in response to receiving the acknowledgment from the network entity.

6. The method of claim 2, wherein adjusting the transmit power control parameter occurs when the one or more data packets comprise a new transmission of one or more data packets on the uplink channel to the network entity.

7. The method of claim 2, wherein adjusting the transport format parameter comprises increasing the transport format parameter in response to receiving the acknowledgment from the network entity.

8. The method of claim 7, wherein increasing the transport format parameter is based at least in part on a block error rate.

9. The method of claim 2, wherein adjusting the transport format parameter comprises decreasing the transport format parameter in response to receiving the negative acknowledgment from the network entity.

10. The method of claim 2, wherein adjusting the transport format parameter comprises:

grouping one or more of transport format parameters into one or more transport format parameter groups, wherein each transport format parameter group comprises one or more transport format parameters of an identical packet data unit size; and

selecting a transport format parameter group from the one or more transport format parameter groups based at least on one of an acknowledgment rate and a negative acknowledgment rate.

11. The method of claim 10, wherein adjusting the transport format parameter comprises selecting the transport format parameter from the selected transport format parameter group having a lowest padding value.

12. The method of claim 2, wherein the transport format parameter comprises enhanced dedicated channel transport format combination indicator (E- TFCI).

An apparatus for communication, comprising: means for transmitting one or more data packets on an uplink channel to a network entity;

means for receiving one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel; and

means for adjusting one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

14. A computer program product, comprising:

a computer-readable medium, including:

at least one instruction executable to cause a computer to transmit one or more data packets on an uplink channel to a network entity;

at least one instruction executable to cause a computer to receive one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel; and

at least one instruction executable to cause a computer to adjust one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.

15. An apparatus, comprising:

a memory storing executable instructions; and

at least one processor in communication with the memory, wherein the processor is configured to execute the instructions to:

transmit one or more data packets on an uplink channel to a network entity;

receive one of an acknowledgement and a negative acknowledgment from the network entity in response to transmitting the one or more data packets on the uplink channel; and adjust one or more transmission parameters based at least in part on receiving one of the acknowledgement and the negative acknowledgment from the network entity.