Method and apparatus of transition to a battery efficient state or configuration by indicating end of data transmission in long term evolution

Abstract

A method is provided for sending a Fast Dormancy (FD) indication from a User Equipment (UE) to an access device through a Media Access Control (MAC) layer. The method includes receiving an indication from an upper layer that there is no more data for a prolonged period of time and generating and sending a MAC control element to the access device.

Description

BACKGROUND

Long Term Evolution (LTE) is a Third Generation Partnership Project (3GPP) standard for mobile network technology. The LTE describes a plurality of requirements for mobile communications systems in evolved or advanced cellular broadband technologies. Such requirements include Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), which is a high-speed radio access technique to meet the increased network demands, including improving user throughputs and network capacity, reducing latency, and increasing mobility. For instance, the LTE uses an Enhanced Packet Core (EPC) network architecture to support the E-UTRAN. The EPC network architecture uses protocols such as Transmission Control Protocol (TCP)/Internet Protocol (IP) for supporting IP based services, such as voice, video, other media, and messaging, with end-to-end Quality of Service (QoS). The EPC network architecture also enables improved connections and hand-over to other fixed-line and wireless access technologies with improved mobility.

The LTE Physical Layer (PHY) uses advanced technologies, including Orthogonal Frequency Division Multiple Access (OFDMA), multiple-input and multiple-output (MIMO) data transmissions, and smart antennas to meet the network demands above. The LTE PHY uses OFDMA for downlink transmissions, for instance from a Base Station (BS) to a User Equipment (UE), which can communicate by transmitting signals throughout a geographical region known as a cell. Additionally, The LTE PHY uses Single Carrier Frequency Division Multiple Access (SC-FDMA) for uplink transmissions, for instance from the UE to the BS. The OFDMA and SC-FDMA technologies reduce the LTE and UE system complexities and increase the communication spectrum or bandwidth.

The UE may be any mobile device used in the LTE system, such as mobile telephones, personal digital assistants, handheld or laptop computers, and similar devices that have telecommunications capabilities. The UE may consist of a wireless device and its associated Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application or might consist of the device itself without such a card. Alternatively, the UE may be a device that has similar wireless capabilities but that is not transportable, such as desktop computers, set-top boxes, or network nodes. The UE may also be a network node, which acts on behalf of another function, such as a wireless device, and simulates or emulates the device. For example, for some wireless devices, an IP Multimedia Subsystem (IMS) Session Initiation Protocol (SIP) client that would typically reside on the device actually resides in the network and relays SIP message information to the device using optimized protocols. In other words, some functions that were traditionally carried out by a wireless device can be distributed in the form of a remote UE, where the remote UE represents the wireless device in the network. In some instances, the UE may be any hardware or software component that can terminate an SIP session.

In addition to the BS and UE, LTE systems may include advanced equipment, which provide services that were not possible previously, such as an enhanced node B (ENB). These devices can provide at least some of the functionalities of the BS, wireless access points, and other systems and devices some of which may be more evolved than the equivalent equipment in a traditional wireless telecommunications system. The term ENB or access device may be used herein to refer to any device, existing or advanced, that may be used to gain access to a network. Such advanced or next generation equipment may be referred to herein as long-term evolution (LTE) equipment.

The LTE includes protocols such as a Radio Resource Control (RRC) protocol, which is responsible for the assignment, configuration and release of radio resources between the UE and the BS, ENB or other access or LTE equipment. The RRC protocol is described in detail in the 3GPP TS 36.331 specifications. According to the RRC protocol, the two basic RRC modes for the UE are defined as “idle mode” and “connected mode.” During the connected mode or state, the UE may exchange signals with the network and perform other related operations, while during the idle mode or state, the UE may shut down at least some of its connected mode operations. Idle and connected mode behaviors are described in details in the Third Generation Partnership Project (3GPP) specifications TS 36.304 and TS 36.331.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.

FIG. 1 is an illustration of a UE control interface for fast dormancy indication according to an embodiment of the disclosure.

FIG. 2 is an illustration of an RRC fast dormancy indication procedure according to an embodiment of the disclosure.

FIG. 3 is an illustration of another RRC fast dormancy indication procedure according to an embodiment of the disclosure.

FIG. 4 is an illustration of a medium access control level fast dormancy indication procedure according to an embodiment of the disclosure.

FIG. 5 is an illustration of another medium access control level fast dormancy indication procedure according to an embodiment of the disclosure.

FIG. 6 is an illustration of a plurality of fast dormancy configurations according to an embodiment of the disclosure.

FIG. 7 is a flow chart of a method for a UE fast dormancy behavior according to an embodiment of the disclosure.

FIG. 8 is a flow chart of a method for an ENB fast dormancy behavior according to an embodiment of the disclosure.

FIG. 9 is a diagram of a wireless communications system including a user agent operable for some of the various embodiments of the disclosure.

FIG. 10 is a block diagram of a user agent operable for some of the various embodiments of the disclosure.

FIG. 11 is a diagram of a software environment that may be implemented on a user equipment operable for some of the various embodiments of the disclosure.

FIG. 12 illustrates an exemplary general-purpose computer system suitable for implementing the several embodiments of the present disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

The UE's transition from the idle mode to the connected mode and vise-versa is typically controlled by the network or the LTE equipment in communication with the UE, such as an ENB. For instance, the network or ENB may decide when to release the RRC connection, and move the UE from one RRC state to another. The state transitions are triggered by data activity or inactivity between the UE and the network. The RRC connection is released by the network sending an RRC Connection Release message, which causes the releasing of the signal link connection and some or all of the radio resources between the UE and the network component. Since the network or ENB may not know the exact moment when the UE has completed data exchange or processing for a given application, it may keep the RRC connection for some time in anticipation of more data to/from the UE in order to reduce the latency of radio resource setup and subsequent connection set-up.

Disclosed herein is a system and method for initiating a fast dormancy (FD) procedure type at the UE to move the UE from the connected mode to the idle mode or to release some connections, or uplink transmission resources between the UE and the network. FD, FD procedure or FD indication may be used herein to refer generally to fast dormancy techniques such as, but not limited to, those proposed to UTRAN. The FD procedures herein may refer to any procedure or process that promotes improved power management and/or extended battery life by, for example, reducing the time the device spends in a particular configuration with assigned connection(s) or configured resources and moving into more energy efficient states or modes, such as idle mode. Accordingly, the UE may decide that it no longer needs at least some of the radio resources currently assigned to it based on available upper layer knowledge, such as end of applications or application contents, and may hence send an indication to the network or an ENB. In response, the network or ENB may act upon the indication by moving the UE from the connected mode to a more energy efficient states or modes, such as idle mode without waiting for further network action or an inactivity timer, which may be preset by the network, to expire by releasing at least some of the connections. Alternatively, the network or ENB may act upon the indication by releasing uplink transmission resources. For instance, the connections may be released in an explicit manner when the ENB sends a release message back to the UE. The uplink transmission resource may be released in explicit manner when the ENB transmits a reconfiguration message to release the resource or in an implicit manner when the ENB stops sending time alignment data to the UE, which may be required by the UE for maintaining uplink transmission timing. The indication may be sent at the RRC protocol layer, for instance using an RRC message, or at a medium access control (MAC) layer. MAC layer signaling may have the benefit of reducing the indication and response time between the UE and the ENB. The FD procedure may be used to improve the total power efficiency at the UE by shortening the RRC connected mode time and moving the UE to a more energy efficient states or modes, such as RRC idle mode, before a network preset time expires causing the network to change the UE resource configuration or release the UE connection. Additionally, the ED procedure may improve the total power efficiency at the UE if the network determines to keep the UE in the RRC connected mode, while reducing the number of unnecessary uplink transmissions. For example, this can be carried out by the network reconfiguring the RRC connection to remove the need for sending the sounding reference signal or, alternatively, by allowing the UE time alignment timer to expire without providing any update to the UE time alignment. Maintaining the RRC connected mode whilst reducing the required number of uplink transmissions also enables a reduction in the time required for call/session setup latency, as compared to idle mode. In addition, the FD procedure may improve further the total power efficiency at the UE since the absence of FD indication could then be used as a sign that more data transfer is likely to be required (with greater probability than in a system not using the FD procedure). This would allow, for example, some inactivity timers on the network side to be influenced, such as extended or reduced.

Specifically, the RRC protocol for LTE may support discontinuous reception (DRX) in connected mode, where the UE may switch in an alternating manner or periodically between the DRX Active Time to monitor Physical Downlink Control Channel (PDCCH) and exchange signals with the network and the non-DRX Active Time to preserve battery power. The time duration of the connected mode of the DRX cycle may be shorter than that of the idle mode. The connected mode may comprise more uplink transmissions and uplink control channel resources. For instance, the UE may be configured to periodically report downlink channel status, e.g., channel quality indicator (CQI), rank indicator (RI), and preceding matrix indicator (PMI), and sounding reference signal (SRS) for uplink channel estimation during DRX active time or connected mode but not during idle time or idle mode. Hereafter CQI, PMI, RI and SRS are referred to as channel status report. The UE may maintain the uplink transmissions during the connected mode regardless of the presence or amount of user traffic or payload. As such, the uplink transmissions may be maintained until the uplink control channel resources are released by the UE, for instance when the uplink time alignment timer in the UE is expired, when the UE receives a reconfiguration message from the network to disable the uplink transmissions, such as an RRC connection reconfiguration message, or when the UE receives a connection release message upon the expiry of the inactivity timer at the network. When the UE exchanges communications with the network at higher rates, the inactivity timer expiration time may increase, and hence the UE may remain in the connected mode for longer time durations unnecessarily.

Additionally, in connected mode, the UE may search for physical downlink control channel (PDCCH) information not only in common search areas but also in UE specific search area, which may increase processing by the UE compared to idle mode where the UE needs to search only in common areas, and hence power consumption is greater in connected mode in comparison to the idle mode. The UE may also examine, during the connected mode, more types of radio network terminal identities (RNTIs), such as cell RNTIs (C-RNTI) or Transmit Power Control-Physical Uplink Shared Channel-RNTI (TPC-PUSCH-RNTI) or Transmit Power Control-Physical Uplink Control Channel-RNTI (TPC-PUCCH-RNTI) or Semi-persistent Scheduling RNTI (SPS-RNTI). Moreover, when the UE is located closer to a cell edge, it may perform additional measurements, which may be related to neighboring cells, and report measurements to the network during the connected mode to ensure robust mobility management. Further, when the UE is transported between the cells, hand-over signaling is used during the connected mode. In contrast, the UE may change cells during the idle mode within its registered tracking areas without signaling to the network. As described above, since the UE performs more operations and hence uses more power during the connected mode in comparison to the idle mode, the FD procedure may preserve the UE's battery power by reducing the duration of the connected mode or by reducing the amount of operations or transmissions during the connected mode. Additionally, by releasing unnecessary control channel resources or connections the FD procedure may improve radio resource utilization and management in Radio Access Networks (RANs) and thus provide more resources for other active users, e.g., for UEs in connected mode with data to transmit.

FIG. 1 illustrates an embodiment of a UE control interface 100, which may be used to send the FD indication to the network. The control interface 100 may comprise a UE connection manager 110, at least one application 120, which may be running or processed at the UE. Additionally, the control interface 100 may comprise a plurality of network protocol layers, including the RRC protocol layer 130, the MAC layer 140, and other protocol or control layers which may be accessed or supported, such as a Packet Data Convergence Protocol (PDCP) layer 150, a Radio Link Control (RLC) layer 160 and a Physical layer (PHY) 170.

The UE connection manager 110 may be aware of the status of any application 120 running or scheduled for running at the UE, for instance at an application or upper layers. For example, the UE connection manager 110 may be aware of the start time, end time, process time, remaining time, or combinations thereof for at least some of the applications 120 at the UE. The applications 120 may comprise network or link management applications, network services applications, other network applications, or user applications. In one embodiment, the UE connection manager 110 may also be aware of the type of power source or status level of available power being used by the UE, whereby if the UE is powered by an external power source or the battery is being charged the UE may determine that the need for FD procedure is reduced or even not needed as sufficient power is available. Alternatively, the UE connection manager 110 may use a battery power level indication as one additional input to trigger the need to activate, or inhibit, the FD procedure, for example enabling the UE connection manager's 110 knowledge of application status to only trigger or allow to trigger a FD procedure if the UE is only being powered by a battery or possibly when the power is below a certain level. The UE connection manager 110 may use such knowledge to determine whether the UE needs any of the radio resources currently assigned to the UE or scheduled for the UE based on such upper layer knowledge. In an embodiment, if no current applications are running or scheduled in a relatively short amount of time, the UE connection manager 110 may send an FD indication 131 to the RRC layer 130, or the FD indication 141 might be sent to the MAC layer 140. Alternatively, the UE connection manager 110 may send the FD indication 131 to the RRC layer 130 which may in turn forward the FD indication 132 to the MAC layer 140. In an embodiment, the RRC layer 130 may send the FD indication to the network or ENB using an RRC message, for example a Signaling Connection Release Indication (SCRI), RRC Connection Release Indication (RCRI) or RRC Connection Release Request (RCRR) message. In an embodiment, the RRC layer 130 may send the FD indication to the network or ENB within an RRC message within an information element comprising a cause value associated with FD indication. For instance, an extension cause indicating “end of data transmission” may be included within an RRC message and sent. In an alternative embodiment, the MAC layer 140 may send the FD indication to the network or ENB using a MAC control element, the control element may have fixed size of 0 octets and be identified by a MAC sub-header comprising a unique logical channel identity (LCID) designated for use for FD indication. For instance, the MAC sub-header may have a length equal to about one octet. Alternatively, the MAC layer FD indication may be a short BSR MAC control element identified by the sub-header comprising a unique LCID designated for use for FD indication by BSR. Other MAC indications, e.g., not requiring that an explicit RRC message be sent as a response to the FD indication, may also be used. In this case, the MAC control element for FD indication has the size of about one octet.

Further, the UE connection manager 110 may be aware of the status of the UE data or application buffer, and may use such knowledge with the upper layer knowledge to determine whether the UE can release the assigned or scheduled radio resources. In an embodiment, if no current applications are running or scheduled, for a period (e.g., short) of time and the buffer is empty, the UE connection manager 110 may determine to send the FD indication to the RRC layer 130 or the MAC layer 140. Additionally, the RRC layer 130 or the MAC layer 140 may be aware of the status of the inactivity timer at the network and may use this along with such upper layer knowledge as indicated by the UE connection manager 110 and/or buffer information to determine whether to send the FD indication. The FD indication may be sent via an RRC message or via a MAC control element. In an embodiment, if no current applications are running or scheduled for a relatively short amount of time, the buffer is empty, and the uplink time alignment is maintained the FD indication may be transmitted. In another embodiment, if no current applications are running or scheduled for a relatively short amount of time, the buffer is empty, the uplink time alignment is not maintained and the inactivity timer may not expire before a relatively long amount of time, the FD indication may be transmitted.

FIG. 2 illustrates an embodiment of an FD indication procedure 200, where the RRC layer 130 at the UE may be used to send the FD indication to the network. When the UE connection manager 110 decides to forward the FD indication, the UE may use the RRC layer 130 to send an RRC FD indication message 205, such as an SCRI, RCRI or RCRR, to the network if there is no data to transmit. Specifically, the RRC FD indication may be sent when the UE maintains uplink (UL) time alignment (TA), i.e., time alignment for uplink transmissions. Accordingly, the UE may send a scheduling request (SR) message 201 to the network, which may be configured by the network (ENB) for contention free uplink access. The network may receive the SR message 201 and grant the UE uplink access, for instance by sending back an uplink grant message 202. The UE may then send a buffer status reporting (BSR) message 203 to obtain uplink resources for transmitting the RRC FD indication. The network may receive the BSR message 203 and grant the UE uplink resources, for instance by sending back an uplink grant message 204. The UE transmits the RRC FD indication to the network (ENB) 205. In some embodiments, if the uplink grant message 202 is sufficient for transmission of the RRC FD indication, the UE may transmit the indication to the network 205 without executing steps 203 and 204.

Finally, the network may reply with a response message 206, such as an RRC connection release message, to release the connection with the UE or to move the UE from the connected mode to the idle mode. In another embodiment, if the UE still maintains UL TA after sending the RRC FD indication message 205, the network may reply with an RRC connection reconfiguration message to release the uplink resources to stop the uplink transmission of channel status reports. In some embodiments the network may not send the response message 206 and instead may stop sending time alignment data to the UE, which may cause the UL TA timer to expire and hence stop the uplink transmissions from the UE.

FIG. 3 illustrates another embodiment of an FD indication procedure 300, where the RRC layer 130 at the UE may be used to send the FD indication to the network. When the UE connection manager 110 decides to forward the FD indication, the UE may use the RRC layer 130 to send an RRC indication message 205, such as an SCRI, RCRI or RCRR, to the network if there is no data to transmit. Specifically, the FD indication may be sent when the UL TA at the UE is not maintained or when the network does not configure scheduling requests for the UE. Accordingly, the UE may send a random access preamble 301 to the network, for contention based access and compete with other random access requests from other UEs, for example. Assuming there is no contention among the UEs, the network may receive the random access preamble 301 and grant the UE uplink access, for instance by sending back a random access response message 302 during a period defined by the network. Due to the possible contentions among the UEs the requesting UE may repeat sending the random access preamble 301 and receiving the random access response message 302, in comparison to sending the SR message 201 and receiving the uplink grant message 202 in the FD indication procedure 200 described above.

In an embodiment, when a preamble group B is available and radio conditions are acceptable, the UE may then select a preamble from the group and transmits the preamble 301 in order to obtain an uplink resource sufficiently large for transmitting the RRC FD indication. In response the network may return a random access response 302 which contains an uplink grant large enough to transmit the RRC FD indication. The UE then transmits the RRC FD indication 303. Alternatively, when a preamble group B is not available or radio conditions are not acceptable, the UE uses a preamble from the preamble group A and the network may send the random access response message 302 to the UE. The preamble group A and B are described in 3GPP TS36.321 specification. When the UE transmits a preamble from the group A 301, additional steps or messaging may then be required to execute the FD procedure 300 if the random access response 302 includes uplink grant not sufficient for the RRC ED indication. The UE may then send a BSR message 303 to the network or execute a BSR procedure with the network in order to obtain enough uplink grant to transmit the RRC FD indication 305. Regardless of the preamble group being used, the network may grant the UE uplink resources, for instance by sending back a contention resolution message 304. The network may then reply explicitly with a response message 306, which may be similar to the response message 206, or implicitly by stopping transmission of time alignment data to the UE.

In an alternative embodiment, when UL TA is not maintained, the UE may decide not to start the FD indication procedure 300. Instead, the UE may remain in the connected mode until the inactivity timer at the network is expired. On the expiry of the inactivity timer, the network will release the RRC connection and transition the UE in idle mode. The above behavior may be encouraged when the inactivity timer in the network will expire shortly. This inactivity timer may be measured by the UE, or could be signaled by the network to the UE (e.g., broadcast in a cell through system information RRC messages, or sent in a dedicated RRC message). Uplink transmission is one of the most expensive operations in terms of battery power consumption. Therefore if the UE knows that the network inactivity timer will expire in a short period of time, it may not be useful to send the indication. The UE may measure the value of network inactivity timer by the use of an internal timer which counts the time between the last data transmission and the RRC connection release or the network may indicate the value of inactivity timer to the UE. Alternatively, the UE may decide to delay sending an RRC indication message 305 to the network until another RRC procedure for mobility, for example measurement reporting, is initiated to increase the duration of the connected mode and hence reduce unnecessary mobility tracking and to improve UE battery efficiency.

FIG. 4 illustrates an embodiment of an FD indication procedure 400, where the MAC layer 140 at the UE may be used to send the FD indication to the network. When the UE connection manager 110 and/or the RRC layer 130 decide to forward the FD indication, the UE connection manager 110 and/or the RRC layer 130 may signal the MAC layer 140 to send a MAC FD indication 403 to the network if there is no data to transmit, or if there has not been any data to transmit within a given time duration. The MAC level indication 403 may comprise a MAC control element for FD indication, such as “End of Data Transmission” or “Fast Dormancy Indication.” The control element may have fixed size of 0 octets and be identified by a MAC sub-header comprising a unique logical channel identity (LCID) designated for use for Fast Dormancy Indication. For instance, the MAC sub-header may have a length equal to about one octet. Alternatively, the MAC FD indication 403 may be a short BSR designated for use for FD indication and comprising a unique LCID. Specifically, the FD indication may be sent when the UE maintains UL TA. Accordingly, the UE may send an SR message 401 to the network, which may be configured for contention free uplink access. The network may receive the SR message 401 and grant the UE uplink access, for instance by sending back an uplink grant message 402. Due to the short length of the MAC FD indication, the uplink grant message 402 may comprise the uplink resource needed by the UE to transmit a MAC FD indication, therefore the UE may not need to send an additional message such as a BSR message. For instance, the MAC FD indication may be a MAC control element for FD indication. For instance, the MAC control element may have a length equal to about one octet including the MAC sub-header. The network may receive the SR message 401 and grant the UE uplink resources, for instance by sending back an uplink resource grant message 402. The UE then transmits the MAC FD indication 403.

The network may then reply explicitly with a response message 404, similar to the FD procedure 200, or implicitly by not sending time alignment data to the UE. For instance, the response message 404 may be RRC Connection Release message or a MAC control element for releasing uplink resources, such as “release Uplink Control Information Resource” and the time alignment data may comprise a time advance MAC control element for aligning the UL time at the UE.

FIG. 5 illustrates another embodiment of an FD indication procedure 500, where the MAC layer 140 at the UE may be used to send the FD indication to the network if there is no data to transmit when the UE connection manager 110 and/or the RRC layer 130 decide to forward the FD indication. Specifically, the FD indication may be sent when the UL TA at the UE is not maintained or when the network does not configure scheduling requests for the UE. Accordingly, the UE may send a random access preamble 501 to the network for contention access. Where there are no contentions among the UEs the network may receive the random access preamble 501 and grant the UE uplink access when possible or applicable, for instance by sending back a random access response message 502. Due to the short length of the MAC FD indication, the random access response message 502 may comprise the uplink resource needed by the UE to transmit a MAC FD indication 503. Therefore, the UE may not need to send an additional message such as a BSR message. For instance, the MAC FD indication 503 may be a MAC control element for FD indication, in addition to a C-RNTI control element. For instance, the MAC control element and its sub-header may have a length equal to about one octet and the C-RNTI control element and its sub-header may have a length equal to about three octets. Further, the network may send back a contention resolution message 504 to the UE, to solve any possible contentions among the UEs. The network may then reply explicitly with a response message 505, similar to the FD procedure 400, or implicitly by stopping time alignment data to the UE. In an alternative embodiment, when UL TA is not maintained, the UE may decide not to start the FD indication procedure 500. Instead, the UE may remain in the connected mode until the timer expires, similar to the FD procedure 300.

Comparing the FD procedures 500 and 400 to the FD procedures 300 and 200, it is apparent that the MAC FD indication may be more efficient than the RRC FD indication as fewer and shorter messages are sent. On the other hand, during the MAC FD indication no message authentication is executed. However, an ENB may check if there is any on-going data transfer activity for the UE that may have triggered the FD indication procedure, for instance based on the BSR messages received from the UE or the downlink buffer status. If there is on-going activity, the ENB may consider that the FD indication is invalid and may ignore it. Alternatively, the ENB may provide a small uplink grant to trigger a BSR from the UE. If the buffer is not empty, the ENB may consider that the FD indication is not valid. If higher security is required, the MAC FD indication may be extended to carry a short message authentication code derived from C-RNTI and an integrity protection key associated with the connection, for example.

FIG. 6 discloses three options that are actually different ways in which FD can be configured by the network—and it is likely that only a single one of these options would be adopted by the system at one time. FIG. 6 illustrates some embodiments for the configuration of FD 600, which may be supported in the network. An FD configuration may comprise a plurality of configuration parameters, including for example, an indication that FD indications are permitted to be sent by the UE and an inhibition timer. For instance, in a first FD configuration 600 (Option 1), a system information RRC message is used to send the configuration to the UE. The scope of configuration is the cell so the set of configuration parameters are applied to all UEs in the cell. In this case, the UE is granted the right to select the target bearer to which the FD indication will apply. In a second FD configuration 600 (Option 2), the RRC Connection Setup message is used to send the configuration to the UE, the scope of configuration is the UE so the set of configuration parameters is applied to only that UE receiving the message. The UE is granted the right to select the target bearer to which the FD indication will apply. Further, in a third FD configuration 600 (Option 3), the RRC Connection Reconfiguration message is used to send the configuration to the UE, the scope of configuration is the UE or radio bearer so the set of configuration parameters is applied to only that UE receiving the message or to that radio bearer defined in the message.

Additionally, the FD configuration may be limited to a specific radio bearer or bearers or resource or resources assigned to the UE, for instance corresponding to an interactive or background type, or may be applied to all radio bearers currently used by the UE. A target radio bearer or bearers may be selected by the UE based on its knowledge of on-going connections and their traffic nature and according to its FD procedure. In an embodiment, the FD configuration may comprise additional parameters, including a value for an inhibition timer, which may be preset and used by the network to control the frequency for transmitting FD indications from the UE, as will be described in more detail below.

In an embodiment, the FD configuration parameters or information elements, which may determine the FD behavior, may be defined using a system information block, an RRC connection setup message, an RRC Connection Reestablishment message, or an RRC connection reconfiguration message. In an embodiment, the FD configuration may comprise an optional parameter which may be configured and hence included or excluded with the remaining parameters in the system information block or RRC message. As an example, the FD configuration parameters or information elements in the system information block or RRC message may be defined as:

FastDormacy-Config ::=  SEQUENCE {
fastDormancyInhibitTimer ENUMERATED
{f0, f1, f10, f100, f1000, } OPTIONAL
-- default f0
}

In an embodiment, other types of networks, which may not be LTE based networks, may support FD behavior or at least some FD functionalities, such as a UTRAN. Hence, when the UE may be transported or relocated between such networks, the FD information element may be transmitted during intra-E-UTRAN handover or inter-radio access technology (RAT) handover between E-UTRAN and UTRAN. For instance, the RRC connection reconfiguration message may be used during handover between UTRAN to E-UTRAN handover, while an Evolved UMTS Terrestrial Radio Access (E-UTRA) mobility command may be used for handover between E-UTRAN to UTRAN.

FIG. 7 illustrates a method 700 for implementing the FD procedures or functions associated with the UE side. At block 710, the UE waits until it receives a trigger such as a no more data indication (NMD) from the UE connection manager 110. For instance, the UE connection manager may determine whether no more uplink data is transmitted or scheduled from upper layer applications and may inform the RRC or MAC layers at the UE. At block 720, the UE or the network may verify whether the inhibit timer is expired. The inhibit timer may be previously set, by the network, for instance for a short time duration to prevent the UE from sending a second or subsequent FD indication in quick repetition. The inhibit timer value represents the time duration during which the device is not allowed to send a subsequent FD indication (even if the other conditions for invoking FD become true again). The time duration may be pre-set in the standards or indicated from the network to the device as a RRC dedicated or system information. As such, the inhibit timer may reduce the frequency of transmitting the FD indications and hence allow more latency in the connected mode. The method 700 may proceed to block 722 if the inhibit timer is still running or may proceed to block 730 if the inhibit timer is expired or not running. At block 722, the UE may wait for the expiration of the inhibit timer. The method 700 may then proceed to block 724, where the UE may verify whether implementing the FD procedure is still valid, for instance when no more data is yet received or scheduled. If transmitted or received data is detected or scheduled the FD procedure may not be valid anymore, hence the method 700 may end, otherwise the method 700 or may proceed to block 730.

At block 730, the UE may verify whether data buffer for uplink transmission is empty. The data buffer is a buffer which stores PDCP Service Data Units (SDUs), PDCP Protocol Data Units (PDUs) and RLC PDUs for initial transmission or retransmission and is referred to as the buffer hereafter. For instance, the buffer may be monitored by the UE connection manager, or in an alternative embodiment by the RRC layer or MAC layer. The method 700 may proceed to block 740 if the buffer is empty, or may proceed to block 732 if the buffer is not empty. At block 732, the UE may wait for a preset time or until the buffer is empty and proceed to block 734, where the UE may verify whether implementing the FD procedure is still valid, as described above. If the FD procedure is determined to be still valid, the method 700 may proceed to block 740, otherwise the method 700 may end. At block 740, the UE may verify whether the UL TA is maintained. The method 700 may proceed to block 750 if the UL TA is still maintained, or may proceed to block 742 otherwise. At block 742, the UE may decide whether to send the FD indication, for instance by deciding whether to implement the FD procedure in an explicit manner. The UE decision may also be based on FD configuration, user preference, or network setup. The FD configuration may include a setting such that the UE can determine whether to initiate the FD procedure when TA is not maintained based on whether the UE would benefit in power efficiency from transmitting to the network in order to move to idle mode or whether it would be sufficient to remain in a timing unaligned status in RRC connected mode. The method 700 may end when implicit FD is decided, allowing the uplink time alignment timer to expire. The other embodiments of explicit or implicit decision are discussed above.

At block 760, the UE transmits FD indication to the network. The indication may be an RRC message or MAC control element which are also described above, the method to be implemented in the UE may be based on system design decision or a network protocol standard for instance 3GPP TS36.331. At block 770, the UE may start the inhibit timer since the FD indication has been sent to allow the delay between FD indications and hence reduce their frequency during connected mode. The method 700 may then return back to block 710 to restart the FD procedure.

FIG. 8 illustrates a method 800 for implementing the FD procedures or functions associated with the network or ENB. At block 810, the ENB may wait until it receives a no more data (NMD) indication from the UE. When it receives the indication from the UE, the method 800 moves on to block 815. At block 815, the ENB may check the validity of the FD indication. First of all the ENB may check if there is any downlink data available for the UE. If any downlink data is available, then the FD procedure may proceed to the block 820 and end. Otherwise, the ENB may verify the message authentication code (MAC) for integrity protection if RRC FD indication is received. If the MAC is correct the FD procedure may proceed to the block 820 and thereafter to the block 830. If MAC FD is received, the ENB may check to determine whether previously received BSR indicated an empty buffer or whether the ENB may provide a small uplink grant to the UE to trigger a new BSR in order to verify that the buffer is empty. If the buffer is confirmed empty the FD procedure may proceed to the block 820 and then to block 830, otherwise the FD procedure may end. For improvement of security of MAC FD indication, the MAC FD control element may be extended to contain a short MAC for integrity protection. The short MAC may be calculated using C-RNTI, Physical cell Id, current system frame number, for example. If the short MAC is correct, the FD procedure proceeds to 830, otherwise proceeds to 820 and ends. At block 830, the ENB may decide whether to transition the UE from the connected mode to the idle mode. The method 800 may proceed to block 850 if the condition of block 830 is met, otherwise the UE may proceed to block 831. At block 831, the ENB may verify whether the UE maintains UL TA. The method 800 may proceed to block 833 if the condition of block 831 is met, otherwise the FD procedure may end. At block 833, the ENB may decide to release the UEs uplink resources implicitly or explicitly. The method 800 may proceed to block 834 if implicit implementation is decided, otherwise the method 800 may proceed to block 835. At block 834, the ENB may stop sending TA commands to the UE, which may be MAC control elements (CE), so the UE will loose uplink time synchronization and hence release the uplink resources after expiration of a certain time. Alternatively, at block 835, the ENB may explicitly release the UEs uplink resources by transmitting an RRC connection reconfiguration message or a MAC CE, for instance to release uplink resources.

FIG. 9 illustrates a wireless communications system including an embodiment of the UE 901. The UE 901 is operable for implementing aspects of the disclosure, but the disclosure should not be limited to these implementations. Though illustrated as a mobile phone, the UE 901 may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a portable computer, a tablet computer, or a laptop computer. Many suitable devices combine some or all of these functions. In some embodiments of the disclosure, the UE 901 is not a general purpose computing device like a portable, laptop or tablet computer, but rather is a special-purpose communications device such as a mobile phone, a wireless handset, a pager, a PDA, or a telecommunications device installed in a vehicle. In another embodiment, the UE 901 may be a portable, laptop or other computing device. The UE 901 may support specialized activities such as gaming, inventory control, job control, and/or task management functions, and so on.

The UE 901 includes a display 902. The UE 901 also includes a touch-sensitive surface, a keyboard or other input keys generally referred as 904 for input by a user. The keyboard may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. The UE 901 may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct.

The UE 901 may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the UE 901. The UE 901 may further execute one or more software or firmware applications in response to user commands. These applications may configure the UE 901 to perform various customized functions in response to user interaction. Additionally, the UE 901 may be programmed and/or configured over-the-air, for example from a wireless base station, a wireless access point, or a peer UE 901.

Among the various applications executable by the UE 901 are a web browser, which enables the display 902 to show a web page. The web page may be obtained via wireless communications with a wireless network access node, a cell tower, a peer UE 901, or any other wireless communication network or system 900. The network 900 is coupled to a wired network 908, such as the Internet. Via the wireless link and the wired network, the UE 901 has access to information on various servers, such as a server 910. The server 910 may provide content that may be shown on the display 902. Alternately, the UE 901 may access the network 900 through a peer UE 901 acting as an intermediary, in a relay type or hop type of connection.

FIG. 10 shows a block diagram of the UE 901. While a variety of known components of UEs 901 are depicted, in an embodiment a subset of the listed components and/or additional components not listed may be included in the UE 901. The UE 901 includes a digital signal processor (DSP) 1002 and a memory 1004. As shown, the UE 901 may further include an antenna and front end unit 1006, a radio frequency (RE) transceiver 1008, an analog baseband processing unit 1010, a microphone 1012, an earpiece speaker 1014, a headset port 1016, an input/output interface 1018, a removable memory card 1020, a universal serial bus (USB) port 1022, a short range wireless communication sub-system 1024, an alert 1026, a keypad 1028, a liquid crystal display (LCD), which may include a touch sensitive surface 1030, an LCD controller 1032, a charge-coupled device (CCD) camera 1034, a camera controller 1036, and a global positioning system (GPS) sensor 1038. In an embodiment, the UE 901 may include another kind of display that does not provide a touch sensitive screen. In an embodiment, the DSP 1002 may communicate directly with the memory 1004 without passing through the input/output interface 1018.

The DSP 1002 or some other form of controller or central processing unit operates to control the various components of the UE 901 in accordance with embedded software or firmware stored in memory 1004 or stored in memory contained within the DSP 1002 itself. In addition to the embedded software or firmware, the DSP 1002 may execute other applications stored in the memory 1004 or made available via information carrier media such as portable data storage media like the removable memory card 1020 or via wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP 1002 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 1002.

The antenna and front end unit 1006 may be provided to convert between wireless signals and electrical signals, enabling the UE 901 to send and receive information from a cellular network or some other available wireless communications network or from a peer UE 901. In an embodiment, the antenna and front end unit 1006 may include multiple antennas to support beam forming and/or multiple input multiple output (MIMO) operations. As is known to those skilled in the art, MIMO operations may provide spatial diversity which can be used to overcome difficult channel conditions and/or increase channel throughput. The antenna and front end unit 1006 may include antenna tuning and/or impedance matching components, RF power amplifiers, and/or low noise amplifiers.

The RF transceiver 1008 provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF. In some descriptions a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions. For the purposes of clarity, the description here separates the description of this signal processing from the RF and/or radio stage and conceptually allocates that signal processing to the analog baseband processing unit 1010 and/or the DSP 1002 or other central processing unit. In some embodiments, the RF Transceiver 1008, portions of the antenna and front end 1006, and the analog baseband processing unit 1010 may be combined in one or more processing units and/or application specific integrated circuits (ASICs).

The analog baseband processing unit 1010 may provide various analog processing of inputs and outputs, for example analog processing of inputs from the microphone 1012 and the headset 1016 and outputs to the earpiece 1014 and the headset 1016. To that end, the analog baseband processing unit 1010 may have ports for connecting to the built-in microphone 1012 and the earpiece speaker 1014 that enable the UE 901 to be used as a cell phone. The analog baseband processing unit 1010 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration. The analog baseband processing unit 1010 may provide digital-to-analog conversion in one signal direction and analog-to-digital conversion in the opposing signal direction. In some embodiments, at least some of the functionality of the analog baseband processing unit 1010 may be provided by digital processing components, for example by the DSP 1002 or by other central processing units.

The DSP 1002 may perform modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions associated with wireless communications. In an embodiment, for example in a code division multiple access (CDMA) technology application, for a transmitter function the DSP 1002 may perform modulation, coding, interleaving, and spreading, and for a receiver function the DSP 1002 may perform despreading, deinterleaving, decoding, and demodulation. In another embodiment, for example in an orthogonal frequency division multiplex access (OFDMA) technology application, for the transmitter function the DSP 1002 may perform modulation, coding, interleaving, inverse fast Fourier transforming, and cyclic prefix appending, and for a receiver function the DSP 1002 may perform cyclic prefix removal, fast Fourier transforming, deinterleaving, decoding, and demodulation. In other wireless technology applications, yet other signal processing functions and combinations of signal processing functions may be performed by the DSP 1002.

The DSP 1002 may communicate with a wireless network via the analog baseband processing unit 1010. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive email or text messages. The input/output interface 1018 interconnects the DSP 1002 and various memories and interfaces. The memory 1004 and the removable memory card 1020 may provide software and data to configure the operation of the DSP 1002. Among the interfaces may be the USB interface 1022 and the short range wireless communication sub-system 1024. The USB interface 1022 may be used to charge the UE 901 and may also enable the UE 901 to function as a peripheral device to exchange information with a personal computer or other computer system. The short range wireless communication sub-system 1024 may include an infrared port, a Bluetooth interface, an IEEE 802.11 compliant wireless interface, or any other short range wireless communication sub-system, which may enable the UE 901 to communicate wirelessly with other nearby mobile devices and/or wireless base stations.

The input/output interface 1018 may further connect the DSP 1002 to the alert 1026 that, when triggered, causes the UE 901 to provide a notice to the user, for example, by ringing, playing a melody, or vibrating. The alert 1026 may serve as a mechanism for alerting the user to any of various events such as an incoming call, a new text message, and an appointment reminder by silently vibrating, or by playing a specific pre-assigned melody for a particular caller.

The keypad 1028 couples to the DSP 1002 via the interface 1018 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the UE 901. The keyboard 1028 may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. Another input mechanism may be the LCD 1030, which may include touch screen capability and also display text and/or graphics to the user. The LCD controller 1032 couples the DSP 1002 to the LCD 1030.

The CCD camera 1034, if equipped, enables the UE 901 to take digital pictures. The DSP 1002 communicates with the CCD camera 1034 via the camera controller 1036. In another embodiment, a camera operating according to a technology other than Charge Coupled Device cameras may be employed. The GPS sensor 1038 is coupled to the DSP 1002 to decode global positioning system signals, thereby enabling the UE 901 to determine its position. Various other peripherals may also be included to provide additional functions, e.g., radio and television reception.

FIG. 11 illustrates a software environment 1102 that may be implemented by the DSP 1002. The DSP 1002 executes operating system drivers 1104 that provide a platform from which the rest of the software operates. The operating system drivers 1104 provide drivers for the UE hardware with standardized interfaces that are accessible to application software. The operating system drivers 1104 include application management services (“AMS”) 1106 that transfer control between applications running on the UE 901. Also shown in FIG. 11 are a web browser application 1108, a media player application 1110, and Java applets 1112. The web browser application 1108 configures the UE 901 to operate as a web browser, allowing a user to enter information into forms and select links to retrieve and view web pages. The media player application 1110 configures the UE 901 to retrieve and play audio or audiovisual media. The Java applets 1112 configure the UE 901 to provide games, utilities, and other functionality. A component 1114 might provide functionality described herein. Although shown at an application layer, the component 1114 might be provided at various layers within the environment 1102 or elsewhere on the UE 901.

The UE 901 and other components described above might include a processing component that is capable of executing instructions related to the actions described above. FIG. 12 illustrates an example of a system 1200 that includes a processing component 1210 suitable for implementing one or more embodiments disclosed herein. In addition to the processor 1210 (which may be referred to as a central processor unit or CPU), the system 1200 might include network connectivity devices 1220, random access memory (RAM) 1230, read only memory (ROM) 1240, secondary storage 1250, and input/output (I/O) devices 1260. In some cases, some of these components may not be present or may be combined in various combinations with one another or with other components not shown. These components might be located in a single physical entity or in more than one physical entity. Any actions described herein as being taken by the processor 1210 might be taken by the processor 1210 alone or by the processor 1210 in conjunction with one or more components shown or not shown in the drawing.

The processor 1210 executes instructions, codes, computer programs, or scripts that it might access from the network connectivity devices 1220, RAM 1230, ROM 1240, or secondary storage 1250 (which might include various disk-based systems such as hard disk, floppy disk, or optical disk). While only one processor 1210 is shown, multiple processors may be present. Thus, while instructions may be discussed as being executed by a processor, the instructions may be executed simultaneously, serially, or otherwise by one or multiple processors. The processor 1210 may be implemented as one or more CPU chips.

The network connectivity devices 1220 may take the form of modems, modem banks, Ethernet devices, universal serial bus (USB) interface devices, serial interfaces, token ring devices, fiber distributed data interface (FDDI) devices, wireless local area network (WLAN) devices, radio transceiver devices such as code division multiple access (CDMA) devices, global system for mobile communications (GSM) radio transceiver devices, worldwide interoperability for microwave access (WiMAX) devices, and/or other well-known devices for connecting to networks. These network connectivity devices 1220 may enable the processor 1210 to communicate with the Internet or one or more telecommunications networks or other networks from which the processor 1210 might receive information or to which the processor 1210 might output information.

The network connectivity devices 1220 might also include one or more transceiver components 1225 capable of transmitting and/or receiving data wirelessly in the form of electromagnetic waves, such as radio frequency signals or microwave frequency signals. Alternatively, the data may propagate in or on the surface of electrical conductors, in coaxial cables, in waveguides, in optical media such as optical fiber, or in other media. The transceiver component 1225 might include separate receiving and transmitting units or a single transceiver. Information transmitted or received by the transceiver component 1225 may include data that has been processed by the processor 1210 or instructions that are to be executed by processor 1210. Such information may be received from and outputted to a network in the form, for example, of a computer data baseband signal or signal embodied in a carrier wave. The data may be ordered according to different sequences as may be desirable for either processing or generating the data or transmitting or receiving the data. The baseband signal, the signal embedded in the carrier wave, or other types of signals currently used or hereafter developed may be referred to as the transmission medium and may be generated according to several methods well known to one skilled in the art.

The RAM 1230 might be used to store volatile data and perhaps to store instructions that are executed by the processor 1210. The ROM 1240 is a non-volatile memory device that typically has a smaller memory capacity than the memory capacity of the secondary storage 1250. ROM 1240 might be used to store instructions and perhaps data that are read during execution of the instructions. Access to both RAM 1230 and ROM 1240 is typically faster than to secondary storage 1250. The secondary storage 1250 is typically comprised of one or more disk drives or tape drives and might be used for non-volatile storage of data or as an over-flow data storage device if RAM 1230 is not large enough to hold all working data. Secondary storage 1250 may be used to store programs that are loaded into RAM 1230 when such programs are selected for execution.

The I/O devices 1260 may include liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, printers, video monitors, or other well-known input devices. Also, the transceiver 1225 might be considered to be a component of the I/O devices 1260 instead of or in addition to being a component of the network connectivity devices 1220. Some or all of the I/O devices 1260 may be substantially similar to various components depicted in the previously described drawing of the UE 901, such as the display 902 and the input 904.

The following Third Generation Partnership Project (3GPP) Technical Specifications (TS) are incorporated herein by reference for all purposes: TS23.401, TS23.203, TS36.331, TS36.304, TS36.321 and TS36.300. The following U.S. patent applications are also incorporated herein by reference for all purposes: Ser. No. 11/302,263 filed Dec. 14, 2005; 60/747,466 filed May 17, 2006; Ser. No. 11/464,380 filed Aug. 14, 2006; 60/956,785 filed Aug. 20, 2007; Ser. No. 12/195,018 filed Aug. 20, 2008; 61/061,359 filed Jun. 13, 2008; 61/074,856 filed Jun. 23, 2008; 61/086,955 filed Aug. 7, 2008; 61/089,731 filed Aug. 18, 2008 and Ser. No. 12/270,522 filed Nov. 13, 2008.

In an embodiment, a method is provided for sending a Fast Dormancy (FD) indication from a User Equipment (UE) to an access device through a Media Access Control (MAC) layer. The method includes receiving an indication from an upper layer that there is no more data for a prolonged period of time and generating and sending a MAC control element to the access device.

In another embodiment, a method is provided for responding to a FD indication from a UE. The method include responding to the FD indication by at least one of releasing a connection with the UE, moving the UE from a connected mode to an idle mode, replying with a reconfiguration message to release an uplink resource to stop an uplink transmission of a channel status report, and stopping sending a time alignment command to the UE.

In another embodiment, a method is provided for responding to a FD indication from a UE through a Media Access Control (MAC) layer. The method includes determining whether there is any on-going data transfer activity for the UE that may have triggered the FD indication and ignoring the FD indication if there is on-going data transfer activity.

In another embodiment, a method is provided for sending a FD indication from a UE to an access device through a Radio Resource Control (RRC) protocol layer. The method includes, when an uplink (UL) time alignment (TA) is maintained between the UE and the access device, sending a scheduling request (SR), receiving an uplink grant, and sending the RRC FD indication.

In another embodiment, a method is provided for handling a FD indication during an inter-radio access technology (RAT) handover. The method includes transmitting FD configuration parameters using a RRC connection reconfiguration message during a handover to a long term evolution (LTE) network.

In another embodiment, a UE is provided. The UE includes a processor configured such that the UE sends a FD indication to an access device through a MAC layer by receiving an indication from an upper layer that there is no more data for a prolonged period of time, and generating and sending a MAC control element to the access device.

In another embodiment, an access device is provided. The access device includes a processor configured such that the access device responds to a FD indication from a UE by at least one of releasing a connection with the UE, moving the UE from a connected mode to an idle mode, replying with a reconfiguration message to release an uplink resource to stop an uplink transmission of a channel status report, and stopping sending a time alignment command to the UE.

In another embodiment, an access device is provided. The access device includes a processor configured such that the access device responds to a FD indication from a UE through a MAC layer by determining whether there is any on-going data transfer activity for the UE that may have triggered the FD indication and ignoring the FD indication if there is on-going data transfer activity.

In another embodiment, a UE is provided. The UE includes a processor configured such that the UE sends a FD indication to an access device through a RRC protocol layer, wherein, when a UL TA is maintained between the UE and the access device, the UE sends a scheduling request, receives an uplink grant, and sends the RRC FD indication.

In another embodiment, a UE is provided. The UE includes a processor configured such that the UE handles a FD indication during an inter-RAT handover by transmitting FD configuration parameters using a RRC connection reconfiguration message during a handover to a LTE network.

While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.

Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.

Claims

1. A method performed by a user equipment (UE), the method comprising: determining whether a type of one or more bearers assigned to the UE is a background type or an interactive type;determining a status of an inhibit timer reflecting whether the inhibit timer has expired or is not running;determining whether to send a request for a more energy efficient state or mode based on the determined type of the one or more bearers and the status of the inhibit timer, wherein an inhibit timer value represents a time duration during which the UE is prevented from sending a subsequent request for the more energy efficient state or mode; andtransmitting the request based on the determining of whether to send the request for the more energy efficient state or mode.

2. A method performed by a network element, the method comprising: determining whether a type of one or more bearers assigned to a user equipment (UE) is a background type or an interactive type;determining whether to permit the UE to send a request for a more energy efficient state or mode based on the determined type of the one or more bearers assigned to the UE;generating an indication based on the determining;setting an inhibit timer value, wherein the inhibit timer value represents a time duration during which the UE is prevented from sending a subsequent request for the more energy efficient state or mode; andtransmitting the indication and the inhibit timer value to the UE.

3. The method of claim 2, wherein transmitting the indication comprises transmitting a Radio Resource Control (RRC) Connection Reconfiguration message.

4. A user equipment (UE) comprising transmitter, receiver, memory and a processor, the processor configured to: determine whether a type of one or more bearers assigned to the UE is a background type or an interactive type;determine a status of an inhibit timer reflecting whether the inhibit timer has expired or is not running;determine whether to send a request for a more energy efficient state or mode based on the determined type of the one or more bearers and the status of the inhibit timer, wherein an inhibit timer value represents a time duration during which the UE is prevented from sending a subsequent request for the more energy efficient state or mode; andtransmit the request based on the determination of whether to send the request for the more energy efficient state or mode.

5. A network element comprising transmitter, receiver, memory and a processor, the processor configured to: determining whether a type of one or more bearers assigned to a user equipment (UE) is a background type or an interactive type;determine whether to permit the UE to send a request for a more energy efficient state or mode based on the determined type of the one or more bearers assigned to the UE;generate an indication based on the determining;set an inhibit timer value, wherein the inhibit timer value represents a time duration during which the UE is prevented from sending a subsequent request for the more energy efficient state or mode; andtransmit the indication and the inhibit timer value to the UE.

6. The network element of claim 5, wherein the transmitting the indication comprises transmitting a Radio Resource Control (RRC) Connection Reconfiguration message.

7. The method of claim 1, further comprising receiving the inhibit timer value via radio resource control signaling.

8. The UE of claim 4, wherein the processor is further configured to receive the inhibit timer value via dedicated radio resource control signaling.