Patent Description:
Semi-persistent scheduling has been considered for Voice over IP in the 3GPP Long Term Evolution. With semi-persistent scheduling, after an initial resource assignment, the same resource is used on an ongoing basis for a given wireless terminal. Between periods of active speech, so-called talk-spurt states, there is a silent period. A concern that has been expressed is how to efficiently handle the silent period between speech talk-spurts while using semi-persistent scheduling. In persistent scheduling, a resource is pre-allocated for a wireless terminal. During a silent period, if no indication that the resource will not be used by the wireless terminal is signalled, the resource will not be available to be reallocated for use by another wireless terminal, since the assumption must be made that the resource is needed. For very simple persistent scheduling without any enhancements, this means that considerable uplink capacity is lost.

For semi-persistent scheduling, in order to free up the resource during periods of silence state, the resource needs to be re-configured between periods of activity (talk-spurt state periods) and periods of silence state (silence state period) and vice versa. During the silent period, Silence Descriptor (SID) frames may be transmitted, for example to satisfy application layer constraints.

State transition includes the following two cases: transition from talk-spurt state to silence state and the transition from silence state to talk-spurt state. Note that the state transitions are aperiodic in the time domain. In one simple way to implement these transitions, whenever a silence state period is detected by the wireless terminal, the wireless terminal sends resource-release signalling to the network to free the pre-allocated resource through the random access channel (RACH) and whenever a talk-spurt is coming, the user will send an explicit request through the existing RACH resource request mechanism for the reestablishment of the semi-persistent resource for transmission of the talk-spurt state. Further, for the SID transmission during silence state, an explicit request is used to ask for the resource, again through the existing RACH resource request mechanism.

<NPL>, relates to proposals to minimize the overhead of scheduling commands and scheduling requests for VoIP in long term evolution (LTE) systems.

<NPL>, relates to proposals to clarify which allocation type is necessary (or suitable) for efficient resource allocation for various services. Three alternative uplink resource assignment schemes are presented. <NUM> requires a resource request to be sent after every fixed RU allocation. <NUM> requires a release request to be sent for every fixed RU allocation not required. <NUM> requires both release requests and resource requests to be sent via L1 signaling.

The invention relates to a method performed by a user equipment (UE) according to claim <NUM>, to a method performed by a wireless base station according to claim <NUM>, and to UEs/base stations configured to perform these methods. Aspects and embodiments described below except for those related to <FIG>, <FIG> do not fall within the scope of the claims and are to be interpreted as examples useful for understanding the invention.

A broad aspect may provide a method comprising receiving transmissions from a wireless terminal on a first uplink wireless transmission resource that is semi-persistently allocated to a wireless terminal such that the first uplink wireless transmission resource is allocated to the wireless terminal for periods that the wireless terminal is in an active state; determining when the wireless terminal has transitioned from the active state to an inactive state; determining when the wireless terminal has transitioned from inactive state to active state by receiving a layer <NUM> indication from the wireless terminal; while the wireless terminal is in the inactive state, making the first uplink wireless transmission resource available for re-allocation for other purposes.

Another broad aspect may provide a method comprising a wireless terminal, while in an active state, transmitting uplink communications , , , , using a first wireless transmission resource that is semi-persistently allocated to the wireless terminal in the sense that the first wireless transmission resource is allocated to the wireless terminal while in the active state; after completing a transmission while in the active state, the wireless terminal transitioning from the active state to an inactive state; in order to start transmitting in the active while in the inactive state, the wireless terminal transitioning from the inactive state to the active state and transmitting a layer <NUM> indication to indicate the transition from the inactive state to the active state.

Another broad aspect may provide an apparatus comprising an access network element that receives transmissions from a wireless terminal on a first uplink wireless transmission resource that is semi-persistently allocated to a wireless terminal such that the first uplink wireless transmission resource is allocated to the wireless terminal for periods that the wireless terminal is in an active state, and that also receives a layer <NUM> indication from the wireless terminal that indicate when the wireless terminal has transitioned from the active state to an inactive state; a scheduler with layer <NUM> state feedback processing function that determines when the wireless terminal has transitioned from the active state to an inactive state, determines when the wireless terminal has transitioned from inactive state to active state by processing the layer <NUM> indications received from the wireless terminal that indicate when the wireless terminal has transitioned from the inactive state to an active state, and while the wireless terminal is in the inactive state, makes the first uplink wireless transmission resource available for re-allocation for other purposes.

Another broad aspect may provide a wireless terminal comprising a wireless access radio <NUM>-<NUM> that, while in an active state, transmits uplink communications using a first wireless transmission resource that is semi-persistently allocated to the wireless terminal in the sense that the first wireless transmission resource is allocated to the wireless terminal while in the active state, and after completing a transmission while in the active state the wireless terminal transitioning from the active state to an inactive state; a layer <NUM> state feedback generator that, in order to start transmitting in the active while in the inactive state, generates a layer <NUM> indication to indicate the transition from the inactive state to the active state for transmission by the wireless access radio.

Another broad aspect may provide a method comprising: receiving transmissions from a wireless terminal on a first uplink wireless transmission resource that is semi-persistently allocated to a wireless terminal such that the first uplink wireless transmission resource is allocated to the wireless terminal for periods that the wireless terminal is in an active state; determining when the wireless terminal has transitioned from the inactive state to an active state; determining when the wireless terminal has transitioned from active state to inactive state by receiving a state transition indication from the wireless terminal; while the wireless terminal is in the inactive state, making the first uplink wireless transmission resource available for re-allocation for other purposes.

In some embodiments, receiving a state transition indication from the wireless terminal may comprise one of:.

Another broad aspect may provide a method comprising a wireless terminal, while in an active state, transmitting uplink communications using a first wireless transmission resource that is semi-persistently allocated to the wireless terminal in the sense that the first wireless transmission resource is allocated to the wireless terminal while in the active state; after completing a transmission while in the active state, the wireless terminal transitioning from the active state to an inactive state and transmitting a state transition indication to indicate the transition from the inactive state to the active state; in order to start transmitting in the active while in the inactive state, the wireless terminal transitioning from the inactive state to the active state.

In some embodiments, transmitting the state transition indication may comprise one of:.

Embodiments and examples will now be described with reference to the attached drawings in which:.

In the Background section, reference is made to a RACH based mechanism for signalling state transitions between talk-burst and silence state. Since voice state transitions may be frequent for a user, and considering the number of VoIP users that might be supported is very large, the incurred overhead with this approach could be very large. Furthermore, since RACH employs a contention based access mechanism, a heavy RACH load may result in an access delay that is long when a talk-spurt state is coming, particularly considering frequent transitions and a large number of VoIP users. This could have a negative effect on the voice quality.

Referring now to <FIG>, shown is a block diagram of an example communication system <NUM>-<NUM> that employs layer <NUM> fast state feedback for resource scheduling and allocation purposes. The communication system <NUM>-<NUM> has a wireless network <NUM>-<NUM>, a wireless terminal <NUM>-<NUM> (also referred to as a UE (user element)), and other wireless terminals <NUM>-<NUM>; the communication system <NUM>-<NUM> may have other components, but they are not shown for sake of simplicity. For example, the wireless terminal and the network will each have transmitters and receivers, having one or more antennas each. The wireless terminal <NUM>-<NUM> has a wireless access radio <NUM>-<NUM>, a processor <NUM>-<NUM>, and a layer <NUM> state feedback generator <NUM>. The wireless terminal <NUM>-<NUM> may have other components, but they are not shown for sake of simplicity. The other wireless terminals <NUM>-<NUM> may each have components similar to those of the wireless terminal <NUM>-<NUM>. Alternatively, some or all of the other wireless terminals <NUM>-<NUM> may have different components than those of the wireless terminal <NUM>-<NUM>. The wireless network <NUM>-<NUM> has a scheduler <NUM> that includes a layer <NUM> state feedback processing function <NUM>.

In operation, the wireless terminal <NUM>-<NUM> communicates with the wireless network <NUM>-<NUM> using its wireless access radio <NUM>-<NUM>. The wireless communication is over a wireless connection <NUM>-<NUM> between the wireless terminal <NUM>-<NUM> and the wireless network <NUM>-<NUM>. The other wireless terminals <NUM>-<NUM> may similarly communicate with the wireless network <NUM>-<NUM> over respective wireless connections (not shown). The communication with the wireless network <NUM>-<NUM> might for example be telephony, or other forms of communication such as email. The layer <NUM> state feedback generator <NUM> generates layer <NUM> feedback that signals to the network when the wireless terminal is transitioning from silence state to talk-spurt state. While in a talk-spurt state, the wireless terminal transmits using a first semi-persistent allocation. In some embodiments, the wireless terminal <NUM>-<NUM> also generates signalling that indicates when there is a transition from talk-spurt state to silence state. This may be performed using the layer <NUM> state feedback generator <NUM>, but other mechanisms are also contemplated, for example MAC layer signalling is employed in some embodiments. Furthermore, in some embodiments, the network autonomously detects this transition without any signalling from the wireless terminal <NUM>-<NUM>. A layer <NUM> resource is specifically allocated for the purpose of state transition signalling.

In the wireless network <NUM>-<NUM>, the scheduler <NUM> is responsible for scheduling and allocating uplink wireless transmission resources. It does this by allocating a resource that is to be used by the wireless terminal while it is in a talk-spurt state. The layer <NUM> state feedback processing function <NUM> processes the layer <NUM> feedback received from the wireless terminal to determine when there is a transition from silence state to talk-spurt state. The scheduler <NUM> also determines when the wireless terminal is in silence state. It can do this as a function of layer <NUM> feedback, MAC-layer in band indications, or it can determine this autonomously. For periods that the scheduler <NUM> concludes that the wireless terminal is in the silence state, the resource that was allocated to the wireless station is available for other uses. For example, it might be used to allocate to the same or different wireless stations for signalling or data communications. However, as soon as the scheduler <NUM> concludes that the wireless terminal has transitioned back to the talk-spurt state, the resource is again allocated to the wireless terminal. The resource is persistently allocated in the sense that it is the same resource that is allocated; particulars of the resource are not required except at the start.

In the illustrated example, the layer <NUM> state feedback generator <NUM> is implemented as software and is executed on the processor <NUM>-<NUM>. However, more generally, the layer <NUM> state feedback generator <NUM> may be implemented as software, hardware, firmware, or any appropriate combination thereof. Similarly, the scheduler <NUM> may be implemented as software, hardware, firmware, or any appropriate combination thereof.

<FIG> is an exemplary environment in which a wireless communication system <NUM> in accordance with some embodiments may be practiced. Communications between illustrated network elements can be implemented using the above-summarized layer <NUM> state feedback mechanisms. The exemplary wireless communication system <NUM> includes a plurality of host services (three shown, <NUM>, <NUM>, and <NUM>), each of which may have a plurality of services such as, but not limited to, e-mail, calendar, Internet web browser, and other applications, available to their subscribers. In this particular example, the host services <NUM>, <NUM>, and <NUM> are typically configured as servers, each containing at least one processor, a storage means and each using a network interface over which communications with a communication network <NUM> such as the Internet can be effectuated. The host services <NUM>, <NUM> and <NUM> send and receive messages over communications network <NUM> to and from wireless router system <NUM> allowing communication between the host services <NUM>, <NUM>, and <NUM> and the wireless router system <NUM>.

The wireless router system <NUM> is connected to a plurality of wireless networks (three shown, <NUM>, <NUM>, and <NUM>), each of which may support a plurality of wireless terminals (one in each wireless network is shown, <NUM>, <NUM>, and <NUM>). The wireless networks <NUM>, <NUM>, and <NUM> may be a cellular telephone network, such as a global system for mobile communication (GSM) network, or a code division multiple access (CDMA) network, a two-way paging network, a short range wireless network such as Bluetooth™, an IEEE <NUM> compliant network, and others alike. The wireless terminals <NUM>, <NUM>, and <NUM> are devices compatible with the corresponding wireless network.

Wireless terminals <NUM>, <NUM> and <NUM> are two-way communication devices with advanced data communication capabilities having the capability to communicate with other wireless terminals or computer systems, such as host services <NUM>, <NUM>, <NUM>, through a network of transceiver stations, including wireless router <NUM> and communication network <NUM>. The mobile communication devices <NUM>, <NUM> and <NUM> may also have the capability to allow voice communication. Depending on the functionality provided, it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device (with or without telephony capabilities). The preceding list is not meant to be exhaustive; the embodiments described herein can be practiced with any type of wireless terminal, whether listed above or not. In the example shown in <FIG>, wireless terminals <NUM>, <NUM> and <NUM> each contain a processor, a radio, an information storage means and at least one software module adapted to perform tasks. In someimplementations, wireless terminals <NUM>, <NUM> and <NUM> are capable of sending and receiving messages using the radio. Also in someimplementations, the at least one software module includes an event generator module, adapted to generate events, and a communications module, adapted to send and receive messages using the wireless terminal's radio.

Wireless terminals are generally capable of communicating over multiple communication channels. For example, short message service (SMS) messages arrive over the voice communication channel, whereas email messages arrive over a data communication channel. As explained above, the wireless terminal <NUM> includes modules, software for example, which are adapted to perform various tasks when executed in wireless terminal <NUM>'s processor. In oneimplementation, the wireless terminal <NUM> contains both a communication module and an event generator module. The communication module is adapted to execute in wireless terminal <NUM>'s processor and in cooperation with the wireless terminal <NUM>'s radio is capable of sending and receiving messages. The event generator module is also adapted to execute in wireless terminal <NUM>'s processor and is capable of generating events in one of two ways: user generated events and device generated events. User generated events include such things as the user of wireless terminal <NUM> opening a messaging application resident in wireless terminal <NUM>, such as an email application, the user of wireless terminal <NUM> rolling a wheel input device, such as a thumbwheel, the user of wireless terminal <NUM> pressing a key on wireless terminal <NUM>'s keyboard, the user of wireless terminal <NUM> logging in to wireless terminal <NUM> or the user of wireless terminal <NUM> electing to maintain an active session by responding to a prompt from wireless terminal <NUM>. Device generated events include such things as the expiry of a timer, wireless terminal <NUM> generating a ping message to keep a session alive with the network or wireless terminal <NUM> commencing a data session, such as a PDP context, with a network.

One of the primary purposes of host services <NUM>, <NUM> and <NUM> is to process information received from other sources, such as mail servers (not shown) and wireless terminals <NUM>, <NUM>, <NUM>, and send the information on to the appropriate recipient, typically a different host service <NUM>, <NUM>, <NUM>, mail server or wireless terminal <NUM>, <NUM> or <NUM>. Host services <NUM>, <NUM> and <NUM> are configured to send and receive email messages and as such typically communicate with a mail server. Mail servers could include for example a Microsoft® Exchange® server, a Lotus® Domino® server, a Novell® GroupWise® server, an IMAP Server, a POP Server or a webmail server or any other mail server as would be understood by those in the art. The host services <NUM>, <NUM> and <NUM> also contain a software module, which executes in their processor to achieve the desired sending and receiving of messages as well as the appropriate processing of information. In some implementations the software module of each host service <NUM>, <NUM>, <NUM> is a messaging module, the messaging module is adapted to receive messages from at least one external mail server, send messages to wireless terminals <NUM>, <NUM>, <NUM>, receive messages from the same wireless terminals and send messages to the at least one external mail server(s). The at least one external mail server(s) could also be at least one mobile data server(s) for example. The wireless router system <NUM> may also be directly connected to a host service, such as a local service <NUM>, without the communication network <NUM>. In another implementation, it is possible for host services <NUM>, <NUM> and <NUM> to communicate directly with wireless terminals <NUM>, <NUM> and <NUM>. In this implementation, host services <NUM>, <NUM> and <NUM> must be capable of addressing communications to wireless terminals <NUM>, <NUM> and <NUM> without the aid of the wireless router system <NUM>.

In the environment described in <FIG>, messaging occurs between wireless terminals <NUM>, <NUM> and <NUM> and host services <NUM>, <NUM> and <NUM>. It is possible for wireless terminals <NUM>, <NUM> and <NUM> to send messages to and receive messages from host services <NUM>, <NUM> and <NUM>. As an example, when a message is received by any one of host services <NUM>, <NUM>, <NUM>, the intended recipient, wireless terminals <NUM>, <NUM> and <NUM> is informed by the host service <NUM>, <NUM> and <NUM> that a message has arrived which needs to be retrieved by way of an enable message. Host service <NUM>, <NUM> and <NUM> may send a plurality of enable messages to wireless terminal <NUM>, <NUM> and <NUM> or host service <NUM>, <NUM> and <NUM> may choose to send one enable message until wireless terminal <NUM>, <NUM> and <NUM> fetches the pending message(s). A fetch command is issued by the wireless terminal <NUM>, <NUM> and <NUM> upon the generation of an event by an event generator after an enable message has been received and is sent to host service <NUM>, <NUM> and <NUM>. The generated event and the enable message are independent and neither one influences the occurrence or likelihood of the other. When host service <NUM>, <NUM> and <NUM> receives a fetch command, host services <NUM>, <NUM> and <NUM> will send the pending message or messages to wireless terminals <NUM>, <NUM> and <NUM> which issued the fetch command. Both the enable messages and the fetch message may or may not contain message identifiers. A message identifier uniquely identifies a message for wireless terminals <NUM>, <NUM> and <NUM> and allows wireless terminals <NUM>, <NUM> and <NUM> to retrieve specific messages. The host service <NUM>, <NUM>, <NUM> may send all pending messages should multiple messages be pending for the wireless terminals <NUM>, <NUM> and <NUM> which issued the fetch command.

Referring now to <FIG>, shown is a block diagram of a mobile communication device <NUM> that may implement wireless terminal related methods described herein. It is to be understood that the wireless terminal <NUM> is shown with very specific details for example purposes only.

A processing device (a microprocessor <NUM>) is shown schematically as coupled between a keyboard <NUM> and a display <NUM>. The microprocessor <NUM> controls operation of the display <NUM>, as well as overall operation of the wireless terminal <NUM>, in response to actuation of keys on the keyboard <NUM> by a user.

The wireless terminal <NUM> has a housing that may be elongated vertically, or may take on other sizes and shapes (including clamshell housing structures). The keyboard <NUM> may include a mode selection key, or other hardware or software for switching between text entry and telephony entry.

In addition to the microprocessor <NUM>, other parts of the wireless terminal <NUM> are shown schematically. These include: a communications subsystem <NUM>; a short-range communications subsystem <NUM>; the keyboard <NUM> and the display <NUM>, along with other input/output devices including a set of LEDS <NUM>, a set of auxiliary I/O devices <NUM>, a serial port <NUM>, a speaker <NUM> and a microphone <NUM>; as well as memory devices including a flash memory <NUM> and a Random Access Memory (RAM) <NUM>; and various other device subsystems <NUM>. The wireless terminal <NUM> may have a battery <NUM> to power the active elements of the wireless terminal <NUM>. The wireless terminal <NUM> is in some implementations a two-way radio frequency (RF) communication device having voice and data communication capabilities. In addition, the wireless terminal <NUM> in some implementations has the capability to communicate with other computer systems via the Internet.

Operating system software executed by the microprocessor <NUM> may be stored in a persistent store, such as the flash memory <NUM>, but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element. In addition, system software, specific device applications, or parts thereof, may be temporarily loaded into a volatile store, such as the RAM <NUM>. Communication signals received by the wireless terminal <NUM> may also be stored to the RAM <NUM>.

The microprocessor <NUM>, in addition to its operating system functions, enables execution of software applications on the wireless terminal <NUM>. A predetermined set of software applications that control basic device operations, such as a voice communications module 730A and a data communications module 730B, may be installed on the wireless terminal <NUM> during manufacture. In addition, a personal information manager (PIM) application module 730C may also be installed on the wireless terminal <NUM> during manufacture. The PIM application is in some implementations capable of organizing and managing data items, such as e-mail, calendar events, voice mails, appointments, and task items. The PIM application is also in some implementations capable of sending and receiving data items via a wireless network <NUM>. In some implementations, the data items managed by the PIM application are seamlessly integrated, synchronized and updated via the wireless network <NUM> with the device user's corresponding data items stored or associated with a host computer system. As well, additional software modules, illustrated as other software module 730N, may be installed during manufacture.

Communication functions, including data and voice communications, are performed through the communication subsystem <NUM>, and possibly through the short-range communications subsystem <NUM>. The communication subsystem <NUM> includes a receiver <NUM>, a transmitter <NUM> and one or more antennas, illustrated as a receive antenna <NUM> and a transmit antenna <NUM>. In addition, the communication subsystem <NUM> also includes a processing module, such as a digital signal processor (DSP) <NUM>, and local oscillators (LOs) <NUM>. The specific design and implementation of the communication subsystem <NUM> is dependent upon the communication network in which the wireless terminal <NUM> is intended to operate. For example, the communication subsystem <NUM> of the wireless terminal <NUM> may be designed to operate with the Mobitex™, DataTAC™ or General Packet Radio Service (GPRS) mobile data communication networks and also designed to operate with any of a variety of voice communication networks, such as Advanced Mobile Phone Service (AMPS), Time Division Multiple Access (TDMA), Code Division Multiple Access CDMA, OFDM (orthogonal frequency division multiplexing), Personal Communications Service (PCS), Global System for Mobile Communications (GSM), etc. Other types of data and voice networks, both separate and integrated, may also be utilized with the wireless terminal <NUM>.

Network access may vary depending upon the type of communication system. For example, in the Mobitex™ and DataTAC™ networks, wireless terminals are registered on the network using a unique Personal Identification Number (PIN) associated with each device. In GPRS networks, however, network access is typically associated with a subscriber or user of a device. A GPRS device therefore typically has a subscriber identity module, commonly referred to as a Subscriber Identity Module (SIM) card, in order to operate on a GPRS network.

When network registration or activation procedures have been completed, the wireless terminal <NUM> may send and receive communication signals over the communication network <NUM>. Signals received from the communication network <NUM> by the receive antenna <NUM> are routed to the receiver <NUM>, which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog-to-digital conversion of the received signal allows the DSP <NUM> to perform more complex communication functions, such as demodulation and decoding. In a similar manner, signals to be transmitted to the network <NUM> are processed (e.g., modulated and encoded) by the DSP <NUM> and are then provided to the transmitter <NUM> for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network <NUM> (or networks) via the transmit antenna <NUM>.

In addition to processing communication signals, the DSP <NUM> provides for control of the receiver <NUM> and the transmitter <NUM>. For example, gains applied to communication signals in the receiver <NUM> and the transmitter <NUM> may be adaptively controlled through automatic gain control algorithms implemented in the DSP <NUM>.

In a data communication mode, a received signal, such as a text message or web page download, is processed by the communication subsystem <NUM> and is input to the microprocessor <NUM>. The received signal is then further processed by the microprocessor <NUM> for an output to the display <NUM>, or alternatively to some other auxiliary I/O devices <NUM>. A device user may also compose data items, such as e-mail messages, using the keyboard <NUM> and/or some other auxiliary I/O device <NUM>, such as a touchpad, a rocker switch, a thumb-wheel, or some other type of input device. The composed data items may then be transmitted over the communication network <NUM> via the communication subsystem <NUM>.

In a voice communication mode, overall operation of the device is substantially similar to the data communication mode, except that received signals are output to a speaker <NUM>, and signals for transmission are generated by a microphone <NUM>. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on the wireless terminal <NUM>. In addition, the display <NUM> may also be utilized in voice communication mode, for example, to display the identity of a calling party, the duration of a voice call, or other voice call related information.

The short-range communications subsystem <NUM> enables communication between the wireless terminal <NUM> and other proximate systems or devices, which need not necessarily be similar devices. For example, the short-range communications subsystem may include an infrared device and associated circuits and components, or a Bluetooth™ communication module to provide for communication with similarly-enabled systems and devices.

In <FIG>, the wireless terminal and the base stations can cooperate to implement one or more the methods described herein. More generally, the network side may be implemented by one or more network components that may include base stations, base station controllers, wireless routers, or mobile switching centres to name a few examples. The implementation particulars will depend on a given network configuration. In <FIG>, microprocessor <NUM>, RAM <NUM>, communication sub-system <NUM>, display <NUM>, flash memory <NUM>, voice module and data module can cooperate to implement one or more of the methods described herein. More generally, the implementation particulars will depend on a given wireless terminal configuration.

While the embodiments and examples described are particularly applicable to real-time low rate packet transmissions, such as VoIP, it is to be understood they can be applied to other packet transmissions that may not necessarily be real-time or low rate, although the efficiencies realized with real-time low-rate applications may not necessarily be realized.

For VoIP implementations described herein, the two states of a wireless terminal are talk-spurt state and silence state. More generally, in some embodiments layer <NUM> signalling is employed to signal the transition between two states referred to as active and inactive. These states can be defined on an implementation specific basis; for example, in some embodiments a wireless terminal will stay in the active state notwithstanding short periods during which the wireless terminal has nothing to send. For VoIP implementations the active state corresponds to the talk-spurt state, and the inactive state corresponds to the silence state.

While the embodiments and examples described herein are in the context of uplink transmission from a wireless terminal to a base station, more generally, some embodiments may be applied for the transmission from a transmitter to a receiver. The transmitter and receiver may be the base station and wireless terminal respectively in the event the embodiments are to be applied to downlink transmission, or they may be the wireless terminal and the base station respectively in the event the embodiments are to be applied to uplink transmission.

According to an embodiment of the application, a fast layer <NUM> talk-spurt state feedback channel may be provided and used to signal transitions from silence state to talk-spurt state. In some embodiments such a channel is also used to signal transitions from silence state to talk-spurt state.

A first example of the operation of the user of layer <NUM> indications to signal state transition will be described with reference to <FIG>. In <FIG>, generally indicated at <NUM> is a sequence of transmissions from a wireless terminal to a base station. Time is running from left to right in this Figure and the other figures described below. The figure represents a random sample of what might be transmitted as part of a VoIP session, but other session types are also contemplated. What is shown in the Figure is assumed to be part of a larger session that may include transmissions that precede and/or follow the specific transmissions shown. The transmissions include a SID frame <NUM>, talk-spurt state <NUM>, SID frames <NUM>,<NUM>, talk-spurt state <NUM> and SID frame <NUM>. During talk bursts <NUM>,<NUM>, the wireless terminal is in the talk-spurt state, and between the talk bursts, the mobile terminal is in the silence state. A talk-spurt state may contain one or more transmit frames that are either contiguous or close enough together to warrant staying in the talk-spurt state. Generally indicated at <NUM> is an example of fast layer <NUM> signalling that is used to report the status of the voice activity on the wireless terminal side to the network. In some embodiments, the uplink transmission resource for this fast indication is pre-allocated for the wireless terminal. Other examples are described below. In the illustrated example, one information bit is used to indicate the two different state transitions. In the particular example illustrated, "<NUM>" means a state transition from talk-spurt state to silence state, and "<NUM>" means a state transition from the silence state to talk-spurt state. Thus, the layer <NUM> signalling <NUM> includes signalling <NUM> to indicate the transition from talk-spurt state to silence state, this following talk-spurt state <NUM>. A next transition is signalled at <NUM> to signal a transition back to the talk-spurt state at the beginning of talk-spurt state <NUM>. Another transition is signalled at <NUM> to indicate another transition from talk-spurt state to silence state. As discussed above, in some implementations, there is a resource that is pre-allocated for this signalling. For this example, when there is nothing to signal, namely for periods between transition signallings, nothing is transmitted as indicated by periods of DTX (discontinuous transmission) <NUM>,<NUM>,<NUM>,<NUM>.

While the wireless terminal is in the talk-spurt state, it transmits using a first pre-allocated resource. This resource is semi-persistently allocated in the sense that the same resource is used each time the wireless terminal is in the talk-spurt state; this means that there is no signalling necessary to indicate a new resource allocation to the wireless terminal except at the beginning when the resource is initially allocated. This might be done, for example, at the beginning of a call. For VoIP transmissions, in the talk-spurt state period, a resource is allocated for the user on the uplink that is sufficient to deliver voice packets.

While the wireless terminal is in the silence state, the wireless terminal transmits SID frames using a second pre-allocated resource. This second resource is also semi-persistently allocated in the sense that the same resource is used each time the wireless terminal is in the silence state; this means that there is no signalling necessary to indicate a new resource allocation to the wireless terminal except at the beginning when the second resource is initially allocated. This might be done, for example, at the beginning of a call. The second resource has a smaller transmission capacity than the first resource. In some implementations, the second resource is completely distinct from the first resource; in other implementations, the second resource is a subset of the first resource. The pre-allocated resource for silent period may be a very small resource that is sufficient for SID frame transmission.

Both allocated resources are pre-configured during the call setup stage. The resource reservation state transition diagram for this example is illustrated in <FIG>. The talk-spurt state <NUM> is characterized by the use of a first pre-configured resource for transmission. The silence state <NUM> is characterized by the use of a second pre-configured resource for SID frame transmissions. The wireless terminal will DTX for the layer <NUM> indication when the wireless terminal is not changing (i.e. stays in one state be it silence state or talk-spurt state). When the state changes, the wireless terminal transmits a fast layer <NUM> indication to the network. The transmission of a "<NUM>" signals a transition from talk-spurt state <NUM> to silence state <NUM>; the transmission of a "<NUM>" signals a transition from the silence state <NUM> to the talk-spurt state <NUM>. Note that in order to improve the reliability, the fast indication may be repeated several times. Since the resource is pre-configured, no additional signalling is required. Transition from Talk-spurt state to Silence state period.

The wireless terminal can detect the coming silence state period by its buffer status. For example, in some embodiments, if the current voice frame is the last frame during the queue, then a conclusion is reached that a silence state period is coming. The wireless terminal will signal the transition from talk-spurt state to silence state so that the network can release the resource for other purposes. The wireless terminal will transmit the SID frame based on the pre-configured resource allocation in this state.

In some embodiments, the transition from talk-spurt state to silence state is not explicitly signalled. Rather, the network detects the silence state period by itself. This might for example be done by looking for periods with no data transmission or by looking for some indication from the application layer. In such cases, the base station can release the resource without any explicit request from wireless terminal.

When new voice packets come, the wireless terminal will signal the transition from silence state to talk-spurt state so that the network will re-allocate the pre-configured resource to the wireless terminal. The wireless terminal will transmit the voice frame based on the pre-configured resource allocation in this state.

It can be seen that for most of the time, the wireless terminal will simply DTX for the fast indication since most of the time there will not be a state transition to signal. This could be a waste of uplink resource. In another embodiment, rather than using the layer <NUM> indication to signal the transition from talk-spurt state to silence state, MAC layer signalling is employed to indicate the silence state period start from the wireless terminal. Assuming the wireless terminal can detect the coming silence state period by its buffer status, for example, the current voice frame is the last frame during the queue, the wireless terminal may use MAC layer signalling to indicate the coming silence state period. In a particular example, in band signalling within the last Voice packet data unit (PDU) transmission, could be performed within an optional field in MAC header. After receiving the signalling, the network can switch the resource reservation mode.

In such embodiments, the fast indication resource is not needed during the talk-spurt state period. This is because the state transition from the talk-spurt state to silence state period is driven by the in-band MAC layer signalling. In some embodiments, the resource that is allocated for the layer <NUM> signalling is available for re-allocation while the wireless terminal is in the talk-spurt state.

A specific embodiment of signalling implemented in this manner will now be described by way of example with reference to <FIG>. In <FIG>, generally indicated at <NUM> is a sequence of transmissions from a wireless terminal to a base station. The transmissions include a SID frame <NUM>, talk-spurt state <NUM>, SID frames <NUM>,<NUM>, talk-spurt state <NUM> and SID frame <NUM>. During talk bursts <NUM>,<NUM>, the wireless terminal is in the talk-spurt state, and between the talk bursts, the mobile terminal is in the silence state. Also shown at the end of talk-spurt state <NUM> is an in-band MAC layer indication <NUM> indicating the transition from talk-spurt state to silence state. Similarly, shown at the end of talk-spurt state <NUM> is an in-band MAC layer indication <NUM> indicating the transition from talk-spurt state to silence state.

Generally indicated at <NUM> is an example of fast layer <NUM> signalling that is used to report the status of the voice activity on the wireless terminal side to the network. In the illustrated example, one information bit is used to indicate the state transition from silence state to talk-spurt state. There is no need to signal the transition from talk-spurt state to silence state since that was taken care of with the in band MAC layer indications. Thus, the layer <NUM> signalling <NUM> includes signalling <NUM> to indicate the transition from silence state to talk-spurt state preceding talk-spurt state <NUM>. The resource for transmitting such a signalling is available for the time that the wireless terminal is in the silence state, but nothing is transmitted when there is no state transition to signal as indicated by DTX period <NUM>,<NUM>. For periods that the wireless terminal is in the talk-spurt state, there is no need for an allocation to the mobile terminal for the purpose of signalling state transitions since there will be no transitions from silence state to talk-spurt state during such periods. Thus, the resource is available for allocation for other purposes during such periods.

The resource reservation state transition diagram for this example is illustrated in <FIG>. The talk-spurt state <NUM> is characterized by the use of a first pre-configured resource for transmission. The silence state <NUM> is characterized by the use of a second pre-configured resource for SID frame transmissions. While in the silence state, the wireless terminal will DTX for the layer <NUM> indication. When the state changes from silence state <NUM> to talk-spurt state <NUM>, the wireless terminal transmits a fast layer <NUM> indication <NUM> to the network. To indicate a transition from talk-spurt state to silence state, the in-band MAC layer indication <NUM> is employed.

In some implementations, particularly true for voice communications, the overall communication is symmetric in the sense that there is downlink transmission as well as uplink transmission. The wireless terminal transmits the layer <NUM> signalling such as NACK/ACK transmission in respect of the downlink transmission. In some embodiments, there is a pre-allocated resource for uplink layer <NUM> transmission for NACK/ACK transmission that is further employed to transmit two additional state transition signals in addition to the NACK/ACK states to indicate the voice activity status. As a specific example, in some systems, <NUM> bit NACK/ACK indicator is repeated <NUM> times for the layer <NUM> transmission, such as "<NUM>" becomes "<NUM>" and "<NUM>" becomes "<NUM>". By using the last two channel bits to represent silence period "XXXXXXXX00" and talk-spurt period "XXXXXXXX11", the state transition can be completed together with NACK/ACK transmission. If talk-spurt to silence is handled by the MAC layer signalling or implicit signalling, then only one state is required.

An example of the operation of such a channel will now be described by way of example with reference to <FIG>. In <FIG>, generally indicated at <NUM> is a sequence of transmissions from a wireless terminal to a base station. This is exactly the same as the example of <FIG> and will not be re-described. Generally indicated at <NUM> is an example of fast layer <NUM> signalling that is used to report the status of the voice activity on the wireless terminal side to the network. This consists of ACK/NACK signalling <NUM> to indicate a transition from talk-spurt state to silence state, ACK/NACK signalling <NUM> to indicate a transition from silence state to talk-spurt state, and ACK/NACK signalling <NUM>. Also shown is ACK/NACK signalling <NUM>,<NUM>,<NUM>,<NUM> that does not need to include state transition information.

In yet another embodiment, the state transition information may be included with CQI (channel quality indication) reporting. For example, additional states in the CQI feedback can be defined that relate to one or the other transition. For example, the current <NUM> bit CQI can represent <NUM> states. However, one or multiple states are reserved for future use. By using <NUM> states to represent the talk-spurt-to-silence transition or silence-to-talk-spurt transition, the state transition can be easily completed together with the CQI transmission. Further, If talk-spurt to silence is handled by the MAC layer signalling or implicit signalling, then only one state is required. Certain coding techniques can be used to optimize the transmission. In this way, additional uplink resource may not be needed.

A pre-curser to the methods described herein is the allocation of an uplink wireless transmission resource to the wireless terminal for use while in the talk-spurt state. Similarly, in some implementations a second uplink wireless transmission resource is allocated to the wireless terminal for use while in the silence state. The particulars of the transmission resource will of course be implementation specific. They may be OFDM-based or CDMA-based or TDMA-based to name a few examples. The particulars of these initial resource allocations are beyond the scope of this application. The network may be able to re-assign the allocated resources to other purposes while they are not being used by the wireless terminal. This involves the network keeping track of the resources assigned to each wireless terminal, and keeping track of the state of each wireless terminal.

A pre-curser to some of the methods described herein is the allocation of an uplink layer <NUM> wireless transmission resource to the wireless terminal for use in signalling the state transition information. The particulars of the transmission resource will of course be implementation specific. They may be OFDM-based or CDMA-based to name a few examples. The particulars of these initial resource allocations are beyond the scope of this application. The network may be able to re-assign the allocated resources to other purposes while they are not being used by the wireless terminal. This involves the network keeping track of the resources assigned to each wireless terminal, and keeping track of the state of each wireless terminal.

All of the above embodiments and examples have assumed state feedback in respect of silence to talk-burst (more generally from inactive to active). In another embodiment, feedback in the form of a state transition indication in respect of talk-burst to silence is transmitted from the receiver to the transmitter, (more generally from active to inactive), optionally without any feedback in respect of silence to talk-burst. This may come in the form of MAC layer feedback, for example as described above, layer <NUM> feedback, for example as described above, ACK/NACK feedback being a specific example of layer <NUM> feedback, or application layer feedback. Again, associated with such a transition, in some embodiments, is a transition from using a first allocated resource that is semi-persistently allocated for use while in the active state, to using a second allocated resource that is semi-persistently allocated for use while in the inactive state.

Claim 1:
A method performed by a UE (<NUM>-<NUM>) in a Long Term Evolution, LTE, system, comprising:
sending a MAC layer signalling to indicate a silence state;
sending a layer <NUM> scheduling request (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) using a pre-allocated uplink transmission resource, wherein the pre-allocated uplink transmission resource is specific to the UE (<NUM>-<NUM>), the layer <NUM> scheduling request (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) indicating that the UE (<NUM>-<NUM>) is requesting to use an uplink resource;
resending the layer <NUM> scheduling request (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) at least one time, using the pre-allocated uplink transmission resource, wherein transmissions occur on the pre-allocated uplink transmission resource only when the UE (<NUM>-<NUM>) is sending a layer <NUM> scheduling request (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) on the pre-allocated uplink transmission resource;
sending a Voice over Internet Protocol, VOIP, packet using the uplink resource;
wherein the layer <NUM> scheduling request indicates an end to the silence state.