WO2016056971A1

WO2016056971A1 - Methods of operating wireless terminals and related wireless terminals

Info

Publication number: WO2016056971A1
Application number: PCT/SE2015/050805
Authority: WO
Inventors: Gunnar Bergquist; Robert Karlsson; Emre YAVUZ; Mikael WITTBERG; Magnus Stattin
Original assignee: Telefonaktiebolaget L M Ericsson (Publ)
Priority date: 2014-10-09
Filing date: 2015-07-07
Publication date: 2016-04-14
Also published as: AR102218A1

Abstract

Methods of operating wireless terminals in communication with a base station of a radio access network and wireless terminals are discussed. Responsive to providing an uplink data unit at a buffer of a wireless terminal for transmission to the base station, an inhibit timer corresponding to the uplink data unit may be initiated (503). After providing the uplink data unit at the buffer, transmission of a request may be blocked (507, 509) responsive to providing the uplink data unit for a duration of the inhibit timer.

Description

METHODS OF OPERATING WIRELESS TERMINALS AND RELATED WIRELESS

TERMINALS BACKGROUND

An objective of 3GPP EPS (Evolved Packet System) QoS (Quality of Service) provisioning is to allow the PLMN (Public Land Mobile Network) operator to differentiate packet flows and assign QoS levels based on end-user content. Packets are mapped onto dedicated bearers through policies that are provisioned by the PLMN operator into the network policy and charging resource function (PCRF).

Accordingly, it may be possible for the PLMN operator to enforce separate forwarding and charging policies per each service or group of services, and for that purpose and with each individual UE connection, a multitude of user plane tunnels may be provided more or less in parallel (e.g., one dominated by packets for streaming internet video, a second for some particular internet web content, a third for conversational IMS voice/audio, a fourth for the screen input of IMS video, etc.) all alongside default tunnels which are used to send unmanaged data.

In an uplink (UL), the logical channels may be grouped into logical channel groups (LCGs). The logical channel groups may be used when scheduling a UE (also referred to as user equipment, a user equipment node, a wireless terminal, etc.) in the UL, because the UE will report in a buffer status report (BSR) message(s) how much data it has to send for each given logical channel group.

In LTE, a UE in a RRC (Radio Resource Control) connected state that does not have a grant pending shall send a scheduling request to the eNB if new UL data arrives from a higher layer(s) for a logical channel.

A scheduling request (SR) may be sent as a dedicated SR (D-SR) if resources for D-SR have been configured by RRC, or the scheduling request may be sent as RA-SR by triggering a Random Access (RA) request for new UL scheduling resources.

When a D-SR has been configured it is associated with a specific static periodicity, which currently can be set to some values in the range of 1 to 80 milliseconds. A UE will be allocated specific subframes for D-SR transmissions with this given periodicity, and these subframes are referred to as SR opportunities.

A UE that has transmitted a scheduling request on dedicated or random access channels may thus need to stay awake and listen for a responsive grant from the base station (also referred to as a NodeB, an eNodeB, etc.). Differentiation of user plane tunnels in the UL direction may be bound by the MAC (Medium Access Control) protocol which may only provide 4 logical channel groups LCGs. This limited number of LCGs may make objectives of the QoS provisioning difficult to achieve, because separate policies may be required for SRB (Signaling Radio Bearer) data, for packets belonging to certain session initiation protocols, and/or for conversational services like VoLTE (Voice over LTE).

As a result, all internet data, which may make up a major bulk of traffic volume in modern mobile telephony (and internet) systems, must typically merge in one single LCG. Also, if the PLMN operator differentiates internet packet flows in separate EPS bearers, the separate internet protocol packet flows may all be mapped onto that single group without possibilities to apply differentiated policies. For example, eye-ball MBB (Mobile Broad Band) content

(observed by a user of the UE) may be merged with low priority background data.

In the situations where higher priority data is merged in a same LCG with lower priority data, the low priority data may generate significant load on system resources. In some cases, the lower priority data may generate proportionally as much or more UL load on system resources as the higher priority data in the same LCG. For example, the lower priority data may trigger SRs (scheduling requests) using substantially the same rules and priority as that of any higher priority data merged in the same LCG. In addition, SRs triggered by lower priority data may result in UL transmission grants using the same rules and priority as that of the higher priority data of the same LCG.

The UE may persistently transmit a SR at each available SR opportunity until a UL grant is provided. The SR may provide no information on the timing aspect of the UL data that has triggered the SR to be sent. The timing aspect of the SR may be the same regardless of the priority and PDB (Packet Delay Budget) of the buffered data, both in terms of how quickly the SR is first triggered and how frequently and persistently the SR is repeated. The eNB (also referred to as an eNodeB, a NodeB, a base station, etc.) may be required to assume a priority and provide transmission grants which often may not correlate with the PDB (Packet Delay Budget) of the EPS (Evolved Packet System) bearer. Once the UE has sent an SR, the UE must stay awake as long as a transmission grant is pending.

Conversational services are examples of services for which there are very determined packet delay budgets PDBs. A packet (also referred to as a data block or a data unit) in such a data flow (which is mapped to a logical channel or data radio bearer) can sustain a certain delay as long as the delay is not too long. At the same time and as far as they can be recognized, the PLMN operator may also provision conversational services with a high priority. This means that a conversational service will be provided a high priority as soon the eNB recognizes that the content of a buffer (of a logical control channel) includes data of a conversational service.

As used herein a data flow refers to a flow of data packets/blocks for a particular service/application, and multiple data flows may be mapped to a same logical channel (also referred to herein as a data radio bearer). Moreover, multiple logical channels may be included in a Logical Channel Group (LCG) using a same LCG uplink data buffer at the UE. In addition, a UE may support multiple Logical Channel Groups using respective different LCG uplink data buffers.

Transmitting SRs too soon and/or with too much repetition, however, may result in unnecessary waste of UE battery resources.

3 GPP R2-144153 ("Prohibiting SR for Low Priority Bearers," 3 GPP TSG-RAN WG2 Meeting #87bis, Shanghai, China, 6 - 10 October 2014), R2-144154 ("Prohibiting SR for Low Priority Bearers," 3 GPP TSG-RAN WG2 Meeting #87, Dresden, Germany, 18 - 22 August 2014), R2-144155 ("Prohibiting SR for Low Priority Bearers," 3 GPP TSG-RAN WG2 Meeting #87, Seoul, Korea, 19 - 23 May 2014), R2-144156 ("Prohibiting SR for Low Priority Bearers," 3 GPP TSG-RAN WG2 Meeting #87, Dresden, Germany, 18 - 22 August 2014), and R2-144157 ("Prohibiting SR for Low Priority Bearers," 3 GPP TSG-RAN WG2 Meeting #87, Seoul, Korea, 19 - 23 May 2014) provide proposals to reduce SR load due to low priority background data.

To stop/reduce low priority bearers from requesting resources, R2-144153 proposes to: apply a mask similar to the logicalChannelSR-Mask; or use a logical channel priority threshold to control the request of UL resources. By stopping low priority bearers from requesting resources, data for the logical channel may risk being not sent at all or may be delayed for a long time, because the UE may not trigger an SR for a potentially very long time, and it can happen that the UE is requested to go to RRC (Radio Resource Control) idle state before having had the possibility to send an SR. A risk is that the logical channel may never be reported in a BSR

(Buffer Status Report) and that the eNB will not know how much data is buffered for that logical channel, possibly resulting in inaccurate scheduling.

SUMMARY

According to some embodiments of inventive concepts, a method may be provided to operate a wireless terminal in communication with a base station of a radio access network. The method may include initiating an inhibit timer corresponding to the uplink data unit responsive to providing an uplink data unit at a buffer of the wireless terminal for transmission to the base station. After providing the uplink data unit at the buffer, transmission of a request may be blocked responsive to providing the uplink data unit for a duration of the inhibit timer.

The uplink data unit may be a first uplink data unit, and the inhibit timer may be a first inhibit timer. After initiating the first inhibit timer and before expiration of the first inhibit timer, a second uplink data unit may be provided at the buffer of the wireless terminal. Responsive to providing the second uplink data unit at the buffer, a second inhibit timer corresponding to the second uplink data unit may be initiated, and responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, a request corresponding to the first uplink data unit may be transmitted to the base station. After transmitting the request to the base station, an uplink grant may be received from the base station. Responsive to receiving the uplink grant from the base station, a buffer status report for the buffer may be transmitted to the base station, with the buffer status report being based on both the first and second data units provided at the buffer of the wireless terminal.

Responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, the second inhibit timer may be terminated without transmitting a request corresponding to the second uplink data unit.

Responsive to receiving the uplink grant from the base station, data of at least one of the first and/or second uplink data units may be transmitted to the base station.

The first and second uplink data units may be first and second uplink data units of a same logical channel and/or bearer, and the first and second inhibit timers may have a same duration.

The first and second uplink data units may include first and second data units of a same data flow.

The request may be a scheduling request, such as, a dedicated scheduling request or a random access scheduling request. In addition, providing the uplink data unit may include storing the uplink data unit in the buffer of the wireless terminal.

According to some other embodiments of inventive concepts, a wireless terminal may be provided for communication with a base station of a radio access network, RAN. More particularly, the wireless terminal may be adapted to initiate an inhibit timer corresponding to an uplink data unit responsive to providing the uplink data unit at a buffer of the wireless terminal for transmission to the base station. The wireless terminal may also be adapted to block transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer after providing the uplink data unit at the buffer.

According to still other embodiments, a wireless terminal may include a transceiver configured to provide wireless communications between the wireless terminal and a base station of a radio access network, RAN, and a processor coupled with the transceiver, wherein communications with the base station are provided though the transceiver. More particularly, the processor may be configured to initiate an inhibit timer corresponding to an uplink data unit responsive to providing the uplink data unit at a buffer of the wireless terminal for transmission to the base station. The processor may also be configured to block transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer after providing the uplink data unit at the buffer.

By delaying transmission of a request (such as a scheduling request) after providing a first uplink data unit at a buffer for uplink transmission, additional uplink data units may be received before transmitting the request, and a resulting buffer status report may reflect the multiple uplink data units. Accordingly, a frequency of scheduling requests may be reduced, power consumption at the wireless terminal may be reduced, and/or network load may be reduced, to thereby increase resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

Figures 1 A and IB are block diagrams illustrating base stations and wireless terminals according to some embodiments of inventive concepts;

Figure 2 is a block diagram illustrating wireless terminals and a radio access network including base stations according to some embodiments of inventive concepts;

Figure 3 is a block diagram illustrating a base station of Figure 2 according to some embodiments of inventive concepts;

Figure 4 is a block diagram illustrating a wireless terminal of Figure 2 according to some embodiments of inventive concepts;

Figures 5 is a flow chart illustrating wireless terminal operations according to some embodiments of inventive concepts;

Figures 6 and 7 are timing diagrams illustrating aspects of timer operations of Figure 5 according to some embodiments of inventive concepts; and

Figures 8A and 8B are flow charts illustrating wireless terminal operations according to some embodiments of inventive concepts. DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

For purposes of illustration and explanation only, these and other embodiments of inventive concepts are described herein in the context of operating in a RAN (Radio Access Network) that communicates over radio communication channels with wireless terminals (also referred to as UEs). It will be understood, however, that inventive concepts are not limited to such embodiments and may be embodied generally in any type of communication network. As used herein, a legacy or non-legacy wireless terminal (also referred to as a UE, user equipment node, mobile terminal, etc.) can include any device that receives data from and/or transmits data to a communication network, and may include, but is not limited to, a mobile telephone

("cellular" telephone), laptop/portable computer, pocket computer, hand-held computer, and/or desktop computer.

Note that although terminology from 3 GPP (3rd Generation Partnership Project) LTE

(Long Term Evolution) has been used in this disclosure to provide examples embodiments of inventive concepts, this should not be seen as limiting the scope of inventive concepts to only the aforementioned system. Other wireless systems, including WCDMA, WiMax, UMB and GSM, may also benefit from exploiting ideas/concepts covered within this disclosure.

Also, note that terminology such as eNodeB (also referred to as a base station, eNB, etc.) and UE (also referred to as a wireless terminal, mobile terminal, etc.) should be considering non- limiting and does not imply a certain hierarchical relation between the two. In general,

"eNodeB" could be considered as a first device and "UE" could be considered as a second device, and these two devices may communicate with each other over some radio channel.

When an LCG (Logical Channel Group) aggregates several bearers (also referred to as channels or logical channels) that carry data (e.g., IP or Internet Protocol data) with different delay tolerance, bearer specific SR inhibit timers can be used to realize relative priorities of bearers within that group. Certain bearers with data which is User Initiated can be configured with inhibit timer values that do not significantly delay the initial SR, and that corresponds to the delay tolerance of the user, while bearers with other (lower priority) data (such as Background data) can be configured with a larger delay timer values. In either case, the inhibit timer may only delay/inhibit the initial SR from being triggered and sent, without further

inhibiting/delaying any subsequent repetitions of SRs and/or without delaying/inhibiting the triggers to update the BSR (Buffer Status Report) to include true estimates of the buffer status of all logical channels included in a LCG.

According to some embodiments disclosed herein, data (e.g., IP or Internet Protocol data) for different bearers/channels sharing a same LCG buffer may be differentiated. The UE can provide a true estimate of all buffered data in an LCG buffer including also such parts of internet data that are considered to be low priority background data. The inhibit timers allow the load on the UL channels and consequently on the UL scheduler to be controlled and/or reduced.

According to some embodiments, services with low priority may be delayed and/or inhibited during time periods when there is high load in the network.

According to some embodiments, the frequency of triggered Scheduling Requests (SRs) from UEs having resources for D-SR configured and/or Random Accesses from UEs not having such resources may be reduced to reduce load on system resources.

According to some embodiments, buffer estimation may be provided in the e B that predicts when and what amount of data arrives at the UE without the UE having to waste energy to send SRs.

By way of example, a voice service that produces a packet every 20 ms in talk state and every 160 ms in silent state can be configured to bundle voice packets on a DRB (Data Radio Bearer) with a "DRB SR inhibit time" close to the PDB, e.g. -70 ms.

In machine type communications (MTC) scenarios, an SR inhibit timer may be set to allow the eNB to schedule the UE before it sends an SR.

According to some embodiments, energy consumption (battery time) may be reduced at the UE and system capacity may be preserved by enabling the UE to not send a D-SR or RA-SR for new UL data too soon after the UL data has been received at a LCG buffer in the UE. This may reduce load on PUCCH (Physical UpLink Control Channel) and/or RACH (Random Access CHannel), which may improve performance in scenarios with many UEs that want to

communicate.

By way of example, a bearer of an LCG may support Uplink VoIP (voice over Internet Protocol) where packets arrive at regular intervals (and the eNB can predict these intervals) in an active state and silence indicators are sent at regular intervals in a silent state but a new talk packet can arrive at any time. According to another example, a bearer of an LCG may support low priority background data where packets can be delivered with relaxed delay requirements. According to some embodiments, configuration of a delay can be enabled (e.g., using an SR inhibit timer) and used as follows.

For a UE in RRC connected state:

• A delay may be introduced after UL data becomes available for transmission (e.g., UL data is received at an UL LCG buffer) until the SR is triggered/transmitted.

• After UL data for a logical channel is transmitted and there is no more UL data available for the same logical channel, a delay timer may be introduced during which new UL data for the same logical channel will be delayed until the timer expires and the SR is triggered/transmitted for that logical channel.

For a UE in RRC idle state:

• A delay may be introduced from the time an UL access request is triggered until an RRC Connection Request procedure is initiated to request the UE to go to RRC connected state. The UL access can be requested due to, for example, initiating a service to receive

DL data, initiating a signaling procedure such as a mobility management procedure, or initiating a service to transmit UL data.

The delay can, for example, be configured individually per UE data buffer, per logical channel (LC) data buffer, per logical channel group (LCG) data buffer, per radio bearer data buffer, and/or per EPS bearer data buffer; all of which may be denoted as a "UL data type" in the text to follow.

The timing delay to send a D-SR, an RA-SR, or an access request on the random access channel may e.g. be specified differently for an UL data buffer in any of the following ways:

• Use a UL data type specific minimum timing delay from the time new UL data of the type related to the timing delay arrives at the UL data buffer from a higher layer or a UL access is requested for the UL data related to the timing delay, until a D-SR , a RA-SR or an access request on the random access channel is triggered/transmitted;

• Use a UL data type specific minimum timing delay from the last time the UE has moved from an RRC idle state to an RRC connected state, until an UL access is requested for

UL data related to the timing delay by triggering SR;

• Use a UL data type specific minimum timing delay from the last time the UE has moved from RRC connected to RRC idle state, until an UL access is requested for the UL data related to the timing delay by triggering an access request on the random access channel; • Use a UL data type specific minimum timing delay from the last time the UE received an UL grant until an SR or an access request on the random access channel is triggered or transmitted for the UL data related to the timing delay ;

• Use a UL data type specific minimum timing delay from the last time the UE transmitted data related to the timing delay , until an SR or an access request on the random access channel is triggered or transmitted for UL data related to the timing delay;

• Use a UL data type specific minimum timing delay from the last time the UE triggered or transmitted an SR or an access request on the random access channel , until an SR or an access request on the random access channel is triggered or transmitted the next time for UL data related to the timing delay;

• Use a UL data type specific minimum timing delay from the last time the UE triggered or transmitted an SR or an access request on the random access channel for any data buffer, until an SR or an access request on the random access channel is triggered or transmitted the next time for UL data related to the timing delay;

· Delay the triggering or transmission of an SR or an access request on the random access channel until a specified time slot. The time slot can be any specific time period which is known by the UE and the network, such as:

OnDuration DRX period, for either short or long DRX;

OnDuration DRX for only long DRX;

A paging opportunity for the UE.

The usage and amount of the delay for transmission of an SR or an RA may also be conditionally changed based on certain rules, such as:

• The given delay may have a fixed value, a random value, a configured value, or a value that is dynamically adapted. If a delay value of "infinite" is set, the transmission of the SR or the triggering of an access request on the random access channel may be prohibited;

• The size of the UL data received from the higher layer may be used to decide which

delay will be used for the transmission of an SR or an access request on the random access channel for a data buffer. For example, a UL data buffer specific minimum timing delay or no additional delay may be used if the size of the UL data for the data buffer is below a certain threshold or above a certain threshold;

• The priority of UL data, for example, control messages associated to the data buffer such as RLC status PDUs might have higher priority than RLC data PDUs in the data buffer; The UE receives an e B broadcasted delay or other parameter;

Use a UL data buffer specific minimum timing delay or no additional delay for the time between the last X number of transmissions (i.e., a group of X transmissions) that happens within a time period Y, for a data buffer;

The used delay may be based on parameters acquired from previous accesses, such as:

Average throughput rate at last access;

Indication from the network of current load estimate.

Note that there may be other conditions causing an SR to be sent or an access request on the random access channel to be triggered earlier than what the delay given above specifies which only specifies delay requirements for one or more data buffers. If an SR or an access request on the random access channel is triggered earlier due to other conditions (e.g., data that is incoming to a data buffer which is not associated with a delay, which has a shorter delay, or for which the delay first expires), this may mean that there is no need for an additional SR or access request on the random access channel to be sent or triggered later according to the delay rules above, and hence the delayed SR or an access request on the random access channel may be prohibited.

Performance impact at, e.g., state mismatch (between eNB and UE) and overload situations when eNB or the base station cannot schedule a UE due to other higher prioritized traffic, can be reduced/minimized by applying normal timing for transmission of SR, etc. after the timing delay for the data buffer has passed.

Some embodiments of inventive concepts are described with respect to a wireless communication system of Figure 1 A-IB where a UE (101) needs to inform the base station (201) with a scheduling request signal (SR), when it has data to transmit on an uplink, the base station (201) transmits a grant to the UE (101) with information needed for the UE (101) to transmit the data.

Some embodiments of inventive concepts may be realized partly in the base station controller as a Request Controller RC (202) that decides if and when the UE (101) should transmit a scheduling request (SR). As input, the RC may use (but not limited to this list) one or more elements of the following information:

• Time since arrival of new or old UL data;

• Time since and time between transmissions of data;

• Time since transmission of a scheduling request (SR); • Number of scheduling requests (SR), and the priority of them, transmitted without receiving a grant;

• If the UE has dedicated resources for scheduling request (SR) transmissions;

• Priority of new or old UL data;

• Amount of new and old data to transmit;

• A hard coded time delay;

• A configured time delay;

• A calculated time delay;

• Information broadcasted by a base station (for example a load measure for the random access channel);

• Availability of data transmission grants (for example (A) might decide to not send a

scheduling request (SR) if the user (101) has a grant where data can be transmitted). According to some other embodiments, a Request Unit RU (102) may be provided in user equipment node UE (101). The Request Controller RC (202) controls in which way the arrival of new UL data of some certain type should result in the transmission of an SR to inform a base station (101) of the need to transmit data, and when the transmission of SR should take place. The Request Unit RU (102) executes the decision and applies the delay for the associated data buffers. As Input the RU may use (but not limited to this list) one or more elements of the following information:

• Time since arrival of new or old UL data;

• Time since and time between transmissions of data;

• Time since transmission of a scheduling request (SR);

• Number of scheduling requests (SR), and the priority of them, transmitted without

receiving a grant;

• Priority of new or old UL data;

• Amount of new and old data to transmit;

• A hard coded time delay;

• A configured time delay;

• A calculated time delay;

• Information broadcasted by a base station (for example a load measure for the random access channel); • Availability of data transmission grants (for example (A) might decide to not send a scheduling request (SR) if the user (101) has a grant where data can be transmitted). According to some embodiments of inventive concepts, new data may be allowed to be included in BSRs triggered responsive to UL data of some other type (e.g., logical channels of higher priority), but triggering of SR for this new data (of lower priority) may be delayed. By delaying SR transmissions for UL data of a type that is tolerant to delay (e.g. lower priority logical channels), UE battery energy may be conserved, and/or consumption of capacity in the network may be reduced.

Figure 2 is a block diagram illustrating a Radio Access Network (RAN) according to some embodiments of present inventive concepts. As shown, communications between a plurality of base stations BS-A, BS-B, and BS-C may be provided using respective X2

Interfaces, and communications between base stations and one or more core nodes MME/S-GW may be provided using respective SI interfaces. Each base station BS may communicate over a radio interface (including uplinks and downlinks) with respective wireless terminals UEs in a respective cell or cells supported by the base station. By way of example, base station BS-A is shown in communication with wireless terminals UE-l and UE-2, base station BS-B is shown in communication with wireless terminals UE-3 and UE-4, and base station BS-C is shown in communication with wireless terminals UE-5 and UE-6.

Figure 3 is a block diagram illustrating elements of a base station BS of Figure 2. As shown, a base station BS may include a transceiver circuit 301 (also referred to as a transceiver) configured to provide radio communications with a plurality of wireless terminals, a network interface circuit 305 (also referred to as a network interface) configured to provide

communications with other base stations of the RAN (e.g., over the X2 interface), and a processor circuit 303 (also referred to as a processor) coupled to the transceiver circuit and the network interface circuit, and a memory circuit 307 coupled to the processor circuit. The memory circuit 307 may include computer readable program code that when executed by the processor circuit 303 causes the processor circuit to perform operations according to

embodiments disclosed herein. According to other embodiments, processor circuit 303 may be defined to include memory so that a memory circuit is not separately provided. Operations of Request Controller 202 discussed above with respect to Figure 1 may be performed by base station processor 303 of Figure 3.

Figure 4 is a block diagram illustrating elements of a wireless terminal UE of Figure 2. As shown, a wireless terminal UE may include a transceiver circuit 401 (also referred to as a transceiver) configured to provide radio communications with a base station BS, a processor circuit 403 (also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 407 coupled to the processor circuit. The memory circuit 407 may include computer readable program code that when executed by the processor circuit 403 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 403 may be defined to include memory so that a memory circuit is not separately provided. Memory 407 may also provide storage for logical channel uplink buffers disclosed herein. Operations discussed of Request Unit 102 discussed above with respect to Figure 1 may be performed by wireless terminal (UE) processor 403 of Figure 4.

Figure 5 is a flow chart illustrating operations of wireless terminal processor 403 according to some embodiments of inventive concepts. As discussed herein operations of Figure 5 may be separately performed for each UpLink (UL) data unit generated by a higher

communication layer for transmission through transceiver 401 to base station 201. Stated in other words, operations of Figure 5 may be independently initiated/performed for each uplink data unit that is stored in a logical channel buffer of wireless terminal.

Operations of Figure 5 may be initiated at block 501 responsive to providing an uplink

(UL) data unit for a data flow mapped to a logical channel of a logical channel group LCG associated with an LCG buffer. As discussed above, one or more data flows may be mapped to a logical channel, and multiple logical channels may be included in a logical channel group. A UL data unit may be provided by a higher protocol layer for transmission through transceiver 401 to base station 201. According to some embodiments, the uplink data unit may be a Service Data Unit (SDU), a Protocol Data Unit (PDU), a Radio Link Protocol (RLC) Service Data Unit (SDU), and/or an RLC data Protocol Data Unit (PDU).

Responsive to providing an uplink data unit at the LCG buffer of wireless terminal 101 for transmission to base station 201 at block 501, processor 403 may initiate an inhibit timer corresponding to the uplink data unit at block 503, and store the UL data unit in the LCG buffer at block 505. A transmit request, however, is not immediately transmitted to base station 201 responsive to the UL data unit. As discussed in greater detail below, a transmit request for the UL data unit is either temporarily blocked until expiration of the associated inhibit timer or permanently blocked if a transmit request for another UL data unit of the same LCG buffer is transmitted before expiration of the inhibit timer. After providing the uplink data unit at the buffer, transmission of a request responsive to providing the uplink data unit is blocked for a duration of the inhibit timer at blocks 507 and 509. With respect to the UL data unit that is now saved in the LCG buffer, processor 403 may wait at blocks 507 and 509 until either a request for another data unit of the LCG buffer is transmitted at block 507 or the inhibit timer for the UL data unit expires at block 509.

If a request is triggered responsive to any other UL data unit at block 507 (i.e., upon expiration of a separate inhibit timer associated therewith) before expiration of the inhibit timer for the current UL data unit, processor 403 may terminate the inhibit timer for the current UL data unit at block 511 so that a separate request for the current UL data unit is not transmitted, and processor 403 may proceed with operations of blocks 515 to 521. Otherwise, upon expiration of the inhibit timer associated with the current UL data unit (i.e., the inhibit timer has run for its full duration) without any requests having been triggered for other UL data units of the LCG buffer, processor 403 may proceed with operations of blocks 515 to 521.

Whether a transmit request is triggered responsive to the current UL data unit (at block 509) or another UL data unit for the LCG buffer (at block 507), a single request may be transmitted through transceiver 401 to base station 201 at block 515. The request may be a scheduling request, a dedicated scheduling request, a random access scheduling request, a Radio Resource Control (RRC) Connection Request using a random access procedure, and/or a RRC Reestablishment Request using a random access procedure.

Once the request is received through transceiver 301 at base station 201, base station 201 may transmit an uplink grant to wireless terminal 101 identifying uplink resources to be used by wireless terminal 101 to transmit data from the LCG buffer.

Upon receipt of the UL grant at block 517 (with the grant being received at processor 403 through transceiver 401), processor 403 may generate and transmit a buffer status report for the LCG buffer through transceiver 401 to base station 201 at block 519. More particularly, the buffer status report is based on all data units (not just the current data unit or a flow or logical channel associated therewith) stored in all the LCG buffers. Stated in other words, the buffer status report is based on all data units of all data flows of all logical channels currently stored in all the LCG buffers.

At block 521, processor 403 may also transmit data of the data unit (and/or data of another/other data unit/units of the buffer) responsive to the grant. For example, the UL grant may define sufficient UL resources to allow transmission of the buffer status report together with some or all of the UL data unit and/or other UL data units stored in the buffer. According to some other embodiments, the buffer status report may be transmitted initially without transmitting data of buffered data units, and processor 403 may wait to receive additional grants before transmitting data of buffered data units at block 521. For example, base station processor 303 may use information from the buffer status report to determine UL grants to be used to transmit data of buffered data units. According to some embodiments, data of uplink data units may be transmitted by processor 403 through transceiver 401 on a Radio Link Protocol (RLC) layer and/or a Packet Data Convergence Protocol (PDCP) layer.

An example of operations of Figure 5 will now be discussed with respect to Figure 6 where first and second UL data units of a same data flow are received at the LGC buffer.

Processor 403 may thus separately perform operations of Figure 5 for each of the first and second data units. Moreover, because the first and second belong to the same data flow and thus the same logical channel, the inhibit timers for the first and second data units may have the same duration.

At time tl, the first UL data unit may be provided from the higher layer and stored in the LCG buffer (see blocks 501 and 505), and a first inhibit timer may be initiated for the first UL data unit (see block 503). As indicated by the arrow, the first inhibit timer has a duration such that it will expire at time t2 (see block 509).

At time t3, the second UL data unit may be provided from the higher layer and stored in the LCG buffer (see blocks 501 and 505), and a second inhibit timer may be initiated for the second UL data unit (see block 503). As indicated by the arrow, the second inhibit timer has a duration such that it will expire at time t4.

In the example of Figure 6, the first inhibit timer will expire after initiation of the second inhibit timer, but before expiration of the second inhibit timer. Accordingly, operations of Figure 5 with respect to the first data unit and the first inhibit timer will proceed at block 509 upon expiration of the first inhibit timer at time t2 thereby triggering transmission of the request at block 515 before expiration of the second inhibit timer. In contrast, operations of Figure 5 with respect to the second data unit and the second inhibit timer will proceed at blocks 507 and 511 thereby terminating the second inhibit timer before time t4 as indicated by the "X" in Figure 6. A single request will thus be transmitted even though two data units have been provided by the higher layer.

The example of Figure 6 may also apply if the first and second data units are for different data flows assigned to the same logical channel, because the same inhibit timer duration may be used for all data units of a same logical channel. More generally, the example of Figure 6 may apply any time a second data unit is received while the first inhibit timer is running, and a duration of the second inhibit timer extends beyond that of the first inhibit timer, even if the duration of the second inhibit timer is greater than or less than that of the first inhibit timer. Another example of operations of Figure 5 will now be discussed with respect to Figure 7 where first and second UL data units of different data flows assigned to different logical channels are received at the LCG buffer. Processor 403 may thus separately perform operations of Figure 5 for each of the first and second data units. More particularly, in the example of Figure 7, a duration of the second inhibit timer is less than a duration of the first inhibit timer.

At time t3, the second UL data unit may be provided from the higher layer and stored in the LCG buffer (see blocks 501 and 505), and a second inhibit timer may be initiated for the second UL data unit (see block 503). As indicated by the arrow, the second inhibit timer has a duration such that it will expire at time t4 (before time t2). The first data unit may thus belong to a relatively low priority data flow and/or logical channel, and the second data unit may belong to a relatively high priority data flow and/or logical channel.

In the example of Figure 7, the second inhibit timer will expire before expiration of the first inhibit timer. Accordingly, operations of Figure 5 with respect to the second data unit and the second inhibit timer will proceed at block 509 upon expiration of the second inhibit timer at time t4 thereby triggering transmission of the request at block 515 before expiration of the first inhibit timer. In contrast, operations of Figure 5 with respect to the first data unit and the first inhibit timer will proceed at blocks 507 and 511 thereby terminating the first inhibit timer before time t2 as indicated by the "X" in Figure 7. A single request will thus be transmitted even though two data units have been provided by the higher layer.

In Figure 7, the first data unit may belong to a data flow and/or logical channel having low priority. By providing a sufficiently long duration for the first inhibit timer for low priority data, data units of this data flow and/or logical channel are unlikely to independently generate scheduling requests because higher priority data units (with shorter inhibit timer durations) will likely trigger scheduling requests before the long duration inhibit timer expires.

As discussed above, operations of Figure 5 may be performed separately for each uplink data unit generated by a higher communication layer for transmission through transceiver 401 to base station 201. To facilitate discussion of separate processing relative to first and second uplink data units according to some embodiments, Figure 8A is provided to illustrate operations performed with respect to a first uplink data unit using the reference numbers of Figure 5, and Figure 8B is provided with prime notation to indicate operations performed with respect to a second uplink data unit. Because the processing is shown separately for the two uplink data units, outputs of the "Terminate Inhibit Timer" blocks 511 and 51 Γ of Figures 8 A and 8B go to the "End" to illustrate that operations relating to the scheduling request (e.g., a dedicated scheduling request or a random access scheduling request) may be handled by the process for the other uplink data unit.

In the example discussed below, Figure 8A illustrates operations performed with respect to a first uplink data unit provided from a higher layer for uplink transmission at time tl of Figure 6, and Figure 8B illustrates operations performed with respect to a second uplink data unit provided from a higher layer for uplink transmission at time t3 of Figure 6. As shown, the uplink data units may trigger respective first and second inhibit timers at times tl and t3.

Moreover, expiration of the first inhibit timer at time t2 at block 509 before expiration of second inhibit timer may cause the process of Figure 8 A to trigger the scheduling request (e.g., dedicated scheduling request or a random access scheduling request) that is transmitted at block 515 and subsequent operations of blocks 517, 519, and 521, and the process of Figure 8B may terminate the second inhibit timer at block 511 ' without requiring separate operations of blocks 515', 517', 519', and 521 ' .

At block 501 of Figure 8 A and time tl of Figure 6, processor 403 may provide a first uplink data unit (e.g., from a higher layer) for transmission to base station 201. Responsive to providing the first uplink data unit, processor 403 may initiate a first inhibit timer corresponding to the first uplink data unit as shown at time tl of Figure 6 at block 503, and processor 403 may store the first uplink data unit in the buffer (e.g., an LCG buffer) at block 505.

After providing the first uplink data unit at the buffer, processor 403 may block transmission of a scheduling request (shown at block 515) responsive to the first uplink data unit for a duration of the first inhibit timer at blocks 507 and 509. More particularly, processor 403 may block transmission of the scheduling request until either a scheduling request for another uplink data unit is triggered at block 507 or the first inhibit timer expires at block 509. In the example discussed with respect to Figures 8A-B and 6, the first inhibit timer for the first UL data unit may run to expiration at time t2 (without a scheduling request for another UL data unit being triggered between times tl and t2).

After performing operations 501, 503, and 505 of Figure 8A with respect to the first UL data unit as discussed above and before expiration of the first timer at time t2, processor 403 may provide a second uplink data unit (e.g., from a higher layer) for transmission to base station 201 at time t3 and block 501 ' of Figure 8B. Responsive to providing the second uplink data unit, processor 403 may initiate a second inhibit timer corresponding to the second uplink data unit as shown at time t3 of Figure 6 at block 503' of Figure 8B, and processor 403 may store the second uplink data unit in the buffer at block 505'.

After providing the second uplink data unit at the buffer, processor 403 may block transmission of a scheduling request responsive to the second uplink data unit until either a scheduling request for another uplink data unit (e.g., the first uplink data unit) is triggered at block 507' (e.g., based on expiration of the first inhibit timer at block 509 of Figure 8 A and time t2 of Figure 6) or the second inhibit timer expires at block 509' . In the example discussed with respect to Figures 8A-B and 6, the second inhibit timer for the second UL data unit may be terminated at block 511 ' responsive to the first inhibit timer expiring at time t2 and at block 509 of Figure 8 A and block 507' of Figure 8B.

Responsive to expiration of the first inhibit timer at time t2 before expiration of the second inhibit timer, processor 403 may transmit a scheduling request corresponding to the first uplink data unit to base station 201 at block 515 of Figure 8 A, and processor 403 may terminate the second inhibit timer at blocks 507' and 51 Γ of Figure 8B. After transmitting the scheduling request to the base station at block 515, processor 403 may receive an uplink grant from base station 201 at block 517, and responsive to receiving the uplink grant from base station 201, processor 403 may transmit a buffer status report for the buffer to base station 201 at block 519 of Figure 8 A. More particularly, the buffer status report may be based on both the first and second data units provided at the buffer of wireless terminal 101.

As discussed above, the second inhibit timer may be terminated at block 511 ' of Figure

8B responsive to expiration of the first inhibit timer at time t2 at block 509 of Figure 8 A and block 507' of Figure 8B. Accordingly, processor 403 may omit separate scheduling request operations of blocks 515', 517', 519' and 52 of Figure 8B relating to the second uplink data unit because the scheduling request operations of 515, 517, 519, and 521 of Figure 8 A (including the buffer status report based on both uplink data units) may be performed for both uplink data units. Accordingly, the second inhibit timer may be terminated at block 507' and 511 ' without transmitting a separate scheduling request corresponding to the second uplink data unit.

Responsive to receiving the uplink grant from base station 201 at block 517, processor 403 may transmit data of at least one of the first and/or second uplink data units to the base station 201 at block 521.

According to some embodiments of Figures 8 A and 8B, the first and second uplink data units may be first and second uplink data units of a same logical channel and/or bearer, and the first and second inhibit timers may have a same duration. Moreover, the first and second uplink data units may be first and second data units of a same data flow. Example Embodiments:

Embodiment 1. A method of operating a wireless terminal in communication with a base station of a radio access network, the method comprising: responsive to providing an uplink data unit at a buffer of the wireless terminal for transmission to the base station, initiating an inhibit timer corresponding to the uplink data unit; and after providing the uplink data unit at the buffer, blocking transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer.

Embodiment 2. The method of Embodiment 1 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, the method further comprising: after initiating the first inhibit timer and before expiration of the first inhibit timer, providing a second uplink data unit at the buffer of the wireless terminal; responsive to providing the second uplink data unit at the buffer, initiating a second inhibit timer corresponding to the second uplink data unit; responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, transmitting a request corresponding to the first uplink data unit to the base station; after transmitting the request to the base station, receiving an uplink grant from the base station;

responsive to receiving the uplink grant from the base station, transmitting a buffer status report for the buffer to the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

Embodiment 3. The method of Embodiment 2 further comprising: responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, terminating the second inhibit timer without transmitting a request corresponding to the second uplink data unit.

Embodiment 4. The method of any of Embodiments 2-3 further comprising: responsive to receiving the uplink grant from the base station, transmitting data of at least one of the first and/or second uplink data units to the base station.

Embodiment 5. The method of any of Embodiments 1-4 wherein the first and second uplink data units are first and second uplink data units of a same logical channel and/or bearer, and wherein the first and second inhibit timers have a same duration.

Embodiment 6. The method of any of Embodiments 2-5 wherein the first and second uplink data units comprise first and second data units of a same data flow.

Embodiment 7. The method of any of Embodiments 2-5 wherein the first and second uplink data units comprises data units of different data flows.

Embodiment 8. The method of Embodiment 1 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, the method further comprising: after initiating the first inhibit timer and before expiration of the first inhibit timer, providing a second uplink data unit at the buffer of the wireless terminal; responsive to providing the second uplink data unit at the buffer, initiating a second inhibit timer corresponding to the second data unit; responsive to expiration of the second inhibit timer before expiration of the first inhibit timer, transmitting a request corresponding to the second uplink data unit to the base station; after transmitting the request to the base station, receiving an uplink grant from the base station; and responsive to receiving the uplink grant from the base station, transmitting a buffer status report for the buffer to the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

Embodiment 9. The method of Embodiment 8 further comprising: responsive to expiration of the second inhibit timer before expiration of the first inhibit timer, terminating the first inhibit timer without transmitting a request corresponding to the first uplink data unit.

Embodiment 10. The method of Embodiment 9 wherein the first and second uplink data units are first and second uplink data units of respective first and second logical channels and/or bearers, and wherein the first and second inhibit timers have respective first and second durations, wherein the first and second logical channels and/or bearers are different, and wherein the second duration is less than the first duration.

Embodiment 11. The method of any of Embodiments 8-10 further comprising:

responsive to receiving the uplink grant from the base station, transmitting data of at least one of the first and/or second uplink data units to the base station.

Embodiment 12. The method of any of Embodiments 8-11 wherein the first and second uplink data units comprises data units of different data flows.

Embodiment 13. The method of any of Embodiments 1-12 wherein the first and second uplink data units are first and second uplink data units of respective first and second logical channels and/or bearers, and wherein the first and second inhibit timers have respective first and second durations, wherein the first and second logical channels and/or bearers are different, and wherein the first and second durations are different.

Embodiment 14. The method of any of Embodiments 1-13 wherein the request is a scheduling request.

Embodiment 15. The method of Embodiment 14 wherein the scheduling request is one of a dedicated scheduling request or a random access scheduling request.

Embodiment 16. The method of any of Embodiments 1-15 wherein the request is a Radio Resource Control (RRC) Connection Request using a random access procedure.

Embodiment 17. The method of any of Embodiments 1-15 wherein the request is a RRC Reestablishment Request using a random access procedure. Embodiment 18. The method of any of Embodiments 1-17 wherein the buffer is a

Logical Channel Group (LCG) buffer.

Embodiment 19. The method of any of Embodiments 1-18 wherein providing the uplink data unit includes storing the uplink data unit in the buffer of the wireless terminal.

Embodiment 20. The method of any of Embodiments 1-19 wherein the uplink data unit is available for transmission to the base station on a Medium Access Control (MAC) layer.

Embodiment 21. The method of any of Embodiments 1-20 wherein the uplink data unit is available for transmission to the base station on a Radio Link Protocol (RLC) layer.

Embodiment 22. The method of any of Embodiments 1-21 wherein the uplink data unit is available for transmission to the base station on a Packet Data Convergence Protocol (PDCP) layer.

Embodiment 23. The method of any of Embodiments 1-22 wherein the uplink data unit comprises at least one of a Service Data Unit (SDU) and/or a Protocol Data Unit (PDU).

Embodiment 24. The method of any of Embodiments 1-23 wherein the uplink data unit comprises at least one of a Radio Link Protocol (RLC) Service Data Unit (SDU) and/or an RLC data Protocol Data Unit (PDU) and/or a Medium Access Control (MAC) SDU and/or a MAC PDU.

Embodiment 25. A wireless terminal adapted to perform according to any one of Embodiments 1-24.

Embodiment 26. A wireless terminal comprising: a transceiver configured to provide wireless communications between the wireless terminal and a base station of a radio access network; and a processor coupled with the transceiver, wherein the processor is configured to perform methods according to any of Embodiments 1-24 wherein communications with the base station are provided though the transceiver.

Embodiment 27. A wireless terminal comprising: a transceiver configured to provide wireless communications between the wireless terminal and a base station of a radio access network, RAN; and a processor coupled with the transceiver, wherein communications with the base station are provided though the transceiver, and wherein the processor is configured to, initiate an inhibit timer corresponding to an uplink data unit responsive to providing the uplink data unit at a buffer of the wireless terminal for transmission to the base station, and block transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer after providing the uplink data unit at the buffer.

Embodiment 28. The wireless terminal of Embodiment 27 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, wherein the processor is further configured to, provide a second uplink data unit at the buffer of the wireless terminal after initiating the first inhibit timer and before expiration of the first inhibit timer, initiate a second inhibit timer corresponding to the second uplink data unit responsive to providing the second uplink data unit at the buffer, transmit a request corresponding to the first uplink data unit to the base station responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, receive an uplink grant from the base station after transmitting the request to the base station, and transmit a buffer status report for the buffer to the base station responsive to receiving the uplink grant from the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

Embodiment 29. The wireless terminal of Embodiment 28 , wherein the processor is further configured to, terminate the second inhibit timer without transmitting a request corresponding to the second uplink data unit responsive to expiration of the first inhibit timer before expiration of the second inhibit timer.

Embodiment 30. The wireless terminal of any of Embodiments 28-29, wherein the processor is further configured to, transmit data of at least one of the first and/or second uplink data units to the base station responsive to receiving the uplink grant from the base station.

Embodiment 31. The wireless terminal of any of Embodiments 28-30 wherein the first and second uplink data units are first and second uplink data units of a same logical channel and/or bearer, and wherein the first and second inhibit timers have a same duration.

Embodiment 32. The wireless terminal of any of Embodiments 28-31 wherein the first and second uplink data units comprise first and second data units of a same data flow.

Embodiment 33. The wireless terminal of any of Embodiments 27-32 wherein the request is a scheduling request.

Embodiment 34. The wireless terminal of Embodiment 33 wherein the scheduling request is one of a dedicated scheduling request or a random access scheduling request.

Embodiment 35. The wireless terminal of any of Embodiments 27-34 wherein providing the uplink data unit includes storing the uplink data unit in the buffer of the wireless terminal.

Embodiment 36. A wireless terminal for communication with a base station of a radio access network, RAN, wherein the wireless terminal is adapted to initiate an inhibit timer corresponding to an uplink data unit responsive to providing the uplink data unit at a buffer of the wireless terminal for transmission to the base station, and block transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer after providing the uplink data unit at the buffer. Embodiment 37. The wireless terminal of Embodiment 36 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, wherein the wireless terminal is further adapted to provide a second uplink data unit at the buffer of the wireless terminal after initiating the first inhibit timer and before expiration of the first inhibit timer, initiate a second inhibit timer corresponding to the second uplink data unit responsive to providing the second uplink data unit at the buffer, transmit a request corresponding to the first uplink data unit to the base station responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, receive an uplink grant from the base station after transmitting the request to the base station, and transmit a buffer status report for the buffer to the base station responsive to receiving the uplink grant from the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

Embodiment 38. The wireless terminal of Embodiment 37 wherein the wireless terminal is further adapted to terminate the second inhibit timer without transmitting a request

corresponding to the second uplink data unit responsive to expiration of the first inhibit timer before expiration of the second inhibit timer.

Embodiment 39. The wireless terminal of any of Embodiments 37-38 wherein the wireless terminal is further adapted to transmit data of at least one of the first and/or second uplink data units to the base station responsive to receiving the uplink grant from the base station.

Embodiment 40. The wireless terminal of any of Embodiments 37-39 wherein the first and second uplink data units are first and second uplink data units of a same logical channel and/or bearer, and wherein the first and second inhibit timers have a same duration.

Embodiment 41. The wireless terminal of any of Embodiments 37-40 wherein the first and second uplink data units comprise first and second data units of a same data flow.

Embodiment 42. The wireless terminal of any of Embodiments 36-41 wherein the request is a scheduling request.

Embodiment 43. The wireless terminal of Embodiment 42 wherein the scheduling request is one of a dedicated scheduling request or a random access scheduling request.

Embodiment 44. The wireless terminal of any of Embodiments 36-43 wherein providing the uplink data unit includes storing the uplink data unit in the buffer of the wireless terminal.

Embodiment 45. A wireless terminal comprising: means for initiating an inhibit timer corresponding to an uplink data unit responsive to providing the uplink data unit at a buffer of the wireless terminal for transmission to a base station of a radio access network, RAN; and means for blocking transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer after providing the uplink data unit at the buffer.

Embodiment 46. The wireless terminal of Embodiment 45 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, the wireless terminal further comprising: means for providing a second uplink data unit at the buffer of the wireless terminal after initiating the first inhibit timer and before expiration of the first inhibit timer; means for initiating a second inhibit timer corresponding to the second uplink data unit responsive to providing the second uplink data unit at the buffer; means for transmitting a request corresponding to the first uplink data unit to the base station responsive to expiration of the first inhibit timer before expiration of the second inhibit timer; means for receiving an uplink grant from the base station after transmitting the request to the base station; and means for transmitting a buffer status report for the buffer to the base station responsive to receiving the uplink grant from the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

Embodiment 47. The wireless terminal of Embodiment 46 further comprising: means for terminating the second inhibit timer without transmitting a request corresponding to the second uplink data unit responsive to expiration of the first inhibit timer before expiration of the second inhibit timer.

Embodiment 48. The wireless terminal of any of Embodiments 46-47 further

comprising: means for transmitting data of at least one of the first and/or second uplink data units to the base station responsive to receiving the uplink grant from the base station.

Embodiment 49. The wireless terminal of any of Embodiments 46-48 wherein the first and second uplink data units are first and second uplink data units of a same logical channel and/or bearer, and wherein the first and second inhibit timers have a same duration.

Embodiment 50. The wireless terminal of any of Embodiments 46-49 wherein the first and second uplink data units comprise first and second data units of a same data flow.

Embodiment 51. The wireless terminal of any of Embodiments 45-50 wherein the request is a scheduling request.

Embodiment 52. The wireless terminal of Embodiment 51 wherein the scheduling request is one of a dedicated scheduling request or a random access scheduling request.

Embodiment 53. The wireless terminal of any of Embodiments 45-52 wherein providing the uplink data unit includes storing the uplink data unit in the buffer of the wireless terminal.

The means of the wireless terminal according to Embodiments 45-53 above may in some embodiments be implemented as computer programs stored in memory (e.g. in the memory circuit 407 of Figure 4) for execution by one or more processors (e.g. the processor circuit 403 of Figure 4).

ABBREVIATIONS:

BSR Buffer Status Report (a MAC control element)

DRB Data Radio Bearer

D-SR Dedicated SR

EPS Evolved Packet System

IMS IP Multimedia Services

IP Internet Protocol

LC Logical Channel

LCG Logical Channel Group

MAC Medium Access Control

MBB Mobile Broad Band

MTC Machine Type Communication

PCRF Policy and Charging Routing Function

PDB Packet Delay Budget

PDCP Packet Data Convergence Protocol

PDU Protocol Data Unit

PLMN Public Land Mobile Network

PUCCH Physical Uplink Control Channel

RA Random Access

RACH Random Access Channel

RA-SR Random Access SR

QoS Quality of Service

RAN Radio Access Network

RLC Radio Link Control

RRC Radio Resource Control

SDU Service Data Unit

SR Scheduling Request

SRB Signaling Radio Bearer

UL UL

UL-SCH Uplink Shared (a Transport Channel)

VoIP Voice over IP

VoLTE Voice over LTE aka VoIP over LTE Further Definitions:

When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or one or more intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like nodes/elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or", abbreviated "/", includes any and all combinations of one or more of the associated listed items.

As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, nodes, steps, components or functions but do not preclude the presence or addition of one or more other features, integers, nodes, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another

element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. Examples of embodiments of aspects of present inventive concepts explained and illustrated herein include their complimentary counterparts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit (also referred to as a processor) of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks.

A tangible, non-transitory computer-readable medium may include an electronic, magnetic, optical, electromagnetic, or semiconductor data storage system, apparatus, or device. More specific examples of the computer-readable medium would include the following: a portable computer diskette, a random access memory (RAM) circuit, a read-only memory (ROM) circuit, an erasable programmable read-only memory (EPROM or Flash memory) circuit, a portable compact disc read-only memory (CD-ROM), and a portable digital video disc readonly memory (DVD/BlueRay).

The computer program instructions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.

It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, the present specification, including the drawings, shall be construed to constitute a complete written description of various example combinations and

subcombinations of embodiments and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Other network elements, communication devices and/or methods according to embodiments of inventive concepts will be or become apparent to one with skill in the art upon review of the present drawings and description. It is intended that all such additional network elements, devices, and/or methods included within this description, be within the scope of the present inventive concepts. Moreover, it is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.

Claims

1. A method of operating a wireless terminal (101) in communication with a base station (201) of a radio access network, RAN, the method comprising:

responsive to providing an uplink data unit at a buffer of the wireless terminal (101) for transmission to the base station (201), initiating (503) an inhibit timer corresponding to the uplink data unit; and

after providing the uplink data unit at the buffer, blocking (507, 509) transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer.

2. The method of Claim 1 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, the method further comprising:

after initiating the first inhibit timer and before expiration of the first inhibit timer, providing (50 ) a second uplink data unit at the buffer of the wireless terminal;

responsive to providing the second uplink data unit at the buffer, initiating (503') a second inhibit timer corresponding to the second uplink data unit;

responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, transmitting (515) a request corresponding to the first uplink data unit to the base station; after transmitting the request to the base station, receiving (517) an uplink grant from the base station; and

responsive to receiving the uplink grant from the base station, transmitting (519) a buffer status report for the buffer to the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

3. The method of Claim 2 further comprising:

responsive to expiration of the first inhibit timer before expiration of the second inhibit timer, terminating (51 Γ) the second inhibit timer without transmitting a request corresponding to the second uplink data unit.

4. The method of any of Claims 2-3 further comprising:

responsive to receiving the uplink grant from the base station, transmitting (521) data of at least one of the first and/or second uplink data units to the base station.

5. The method of any of Claims 2-4 wherein the first and second uplink data units are first and second uplink data units of a same logical channel and/or bearer, and wherein the first and second inhibit timers have a same duration.

6. The method of any of Claims 2-5 wherein the first and second uplink data units comprise first and second data units of a same data flow.

7. The method of any of Claims 1-6 wherein the request is a scheduling request.

8. The method of Claim 7 wherein the scheduling request is one of a dedicated scheduling request or a random access scheduling request.

9. The method of any of Claims 1-8 wherein providing the uplink data unit includes storing the uplink data unit in the buffer of the wireless terminal.

10. A wireless terminal (101) for communication with a base station (201) of a radio access network, RAN, wherein the wireless terminal (101) is adapted to:

initiate an inhibit timer corresponding to an uplink data unit responsive to providing the uplink data unit at a buffer of the wireless terminal (101) for transmission to the base station (201); and

block transmission of a request responsive to providing the uplink data unit for a duration of the inhibit timer after providing the uplink data unit at the buffer.

11. The wireless terminal (101) of Claim 10 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, wherein the wireless terminal (101) is further adapted to:

provide a second uplink data unit at the buffer of the wireless terminal after initiating the first inhibit timer and before expiration of the first inhibit timer;

initiate a second inhibit timer corresponding to the second uplink data unit responsive to providing the second uplink data unit at the buffer;

transmit a request corresponding to the first uplink data unit to the base station responsive to expiration of the first inhibit timer before expiration of the second inhibit timer;

receive an uplink grant from the base station after transmitting the request to the base station; and transmit a buffer status report for the buffer to the base station responsive to receiving the uplink grant from the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

12. The wireless terminal (101) of Claim 11 wherein the wireless terminal (101) is further adapted to:

terminate the second inhibit timer without transmitting a request corresponding to the second uplink data unit responsive to expiration of the first inhibit timer before expiration of the second inhibit timer.

13. The wireless terminal (101) of any of Claims 11-12 wherein the wireless terminal (101) is further adapted to:

transmit data of at least one of the first and/or second uplink data units to the base station responsive to receiving the uplink grant from the base station.

14. The wireless terminal (101) of any of Claims 11-13 wherein the first and second uplink data units are first and second uplink data units of a same logical channel and/or bearer, and wherein the first and second inhibit timers have a same duration.

15. The wireless terminal (101) of any of Claims 11-14 wherein the first and second uplink data units comprise first and second data units of a same data flow.

16. The wireless terminal (101) of any of Claims 10-15 wherein the request is a scheduling request.

17. The wireless terminal (101) of Claim 16 wherein the scheduling request is one of a dedicated scheduling request or a random access scheduling request.

18. The wireless terminal (101) of any of Claims 10-17 wherein providing the uplink data unit includes storing the uplink data unit in the buffer of the wireless terminal.

19. A wireless terminal (101) comprising:

a transceiver (401) configured to provide wireless communications between the wireless terminal (101) and a base station (201) of a radio access network, RAN; and a processor (403) coupled with the transceiver, wherein communications with the base station are provided though the transceiver, and wherein the processor is configured to,

initiate an inhibit timer corresponding to an uplink data unit responsive to providing the uplink data unit at a buffer of the wireless terminal for transmission to the base station, and

20. The wireless terminal (101) of Claim 19 wherein the uplink data unit is a first uplink data unit, wherein the inhibit timer is a first inhibit timer, wherein the processor (403) is further configured to,

provide a second uplink data unit at the buffer of the wireless terminal after initiating the first inhibit timer and before expiration of the first inhibit timer,

initiate a second inhibit timer corresponding to the second uplink data unit responsive to providing the second uplink data unit at the buffer,

transmit a request corresponding to the first uplink data unit to the base station responsive to expiration of the first inhibit timer before expiration of the second inhibit timer,

receive an uplink grant from the base station after transmitting the request to the base station, and

transmit a buffer status report for the buffer to the base station responsive to receiving the uplink grant from the base station, wherein the buffer status report is based on both the first and second data units provided at the buffer of the wireless terminal.

21. The wireless terminal (101) of Claim 20 , wherein the processor (403) is further configured to,

22. The wireless terminal (101) of any of Claims 20-21 , wherein the processor (403) is further configured to,

23. The wireless terminal (101) of any of Claims 20-22 wherein the first and second uplink data units are first and second uplink data units of a same logical channel and/or bearer, and wherein the first and second inhibit timers have a same duration.

24. The wireless terminal (101) of any of Claims 20-23 wherein the first and second uplink data units comprise first and second data units of a same data flow.

25. The wireless terminal (101) of any of Claims 19-24 wherein the request is a scheduling request.

26. The wireless terminal (101) of Claim 25 wherein the scheduling request is one of a dedicated scheduling request or a random access scheduling request.

27. The wireless terminal (101) of any of Claims 19-26 wherein providing the uplink data unit includes storing the uplink data unit in the buffer of the wireless terminal.