Patent Description:
Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (<NUM>) network, have been completed within the 3rd Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a Fifth Generation (<NUM>) network. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.

Long Term Evolution (LTE) includes a discontinuous reception (DRX) mode to conserve the battery of a terminal device. When DRX mode is configured in a terminal device, the terminal device is able to turn its receiver off and enter a low-power state, waking for defined (periodic) phases to listen for scheduling messages or other wireless communications. For example, when the terminal device is in a DRX sleep state, it does not need to listen on the physical downlink control channel (PDCCH). When the terminal device is in the DRX active state, it must normally listen on the PDCCH to wait for potential scheduling messages from the network (e.g. from the eNodeB).

According to the 3rd Generation Partnership Project (3GPP) media access control (MAC) standard for LTE (Technical Specification Group <NUM>, version <NUM>. <NUM>), the terminal device is in the DRX active state when any of the conditions specified in section <NUM> is true, that is to say:.

If none of these conditions is true, then the terminal device is in the DRX sleep state, (i.e. when its receiver is turned off).

A terminal device in RRC_CONNECTED state and which has been configured with the DRX function can be configured with both a long DRX cycle and a short DRX cycle. The intention with the long DRX cycle is that the terminal device should be able to sleep for a long time and wake up only periodically to listen for any new scheduling requests. The intention with the short DRX cycle is that the terminal device should be awake more frequently than in the long DRX cycle to listen for any scheduling requests. Those time periods when the terminal device is awake to listen for scheduling messages may be referred to as OnDuration periods, and are configured for a certain time duration. The scheduling messages sent from the UE to a network node may e.g. be a downlink assignment.

When the terminal device is scheduled, an inactivity timer called drx-InactivityTimer is started and while this timer is running the terminal device is awake to listen for any scheduling requests. When the drx-InactivityTimer expires, the terminal device will go to short DRX sleep, if configured, otherwise the terminal device will go to long DRX sleep.

If the terminal device has not been scheduled for a configured number of short DRX cycles the terminal device will go to long DRX sleep.

However, using a large value for the drx-lnactivityTimer (such as <NUM>) will in many cases cause the terminal device to be awake for much longer than necessary which will increase the power consumption in the network.

<CIT>, discloses using a wake-up message to indicate to an apparatus to exit a sleeping state and enter an awake state.

<CIT>, discloses receiving a wake-up signal and activating a transceiver in response to the reception.

It is an object of embodiments herein to enhance performance of a wireless communications network, in particular to reduce energy consumption of a UE in the wireless communications network.

Embodiments herein relate to a UE, a network node and methods therein. According to a first aspect of embodiments herein, the object is achieved by a method, performed by a User Equipment (UE), according to independent claim <NUM>.

According to a second aspect of embodiments herein, the object is achieved by a method, performed by a network node, according to independent claim <NUM>.

According to a third aspect of embodiments herein, the object is achieved by a User Equipment (UE), according to independent claim <NUM>.

According to a fourth aspect of embodiments herein, the object is achieved by a network node according to independent claim <NUM>.

Moreover, a computer program is provided according to independent claim <NUM> and a computer-readable storage medium is provided according to independent claim <NUM>. Preferred embodiments are provided by the dependent claims.

As part of developing embodiments, a problem will first be identified and discussed. Please note that the terms "UE" and "user equipment" are used interchangeably in this document.

3GPP contribution <NPL>) submitted to the 3GPP RAN WG2 meeting points at a problem in the UE to support connected mode DRX as it is currently defined in 3GPP.

<FIG> shows a typical Connected Mode DRX (C-DRX) operation in E-UTRAN. The UE wakes up, which may also be referred to as entering an onDuration, once every DRX cycle to monitor the downlink during its ON duration. If the UE successfully decodes a Physical Downlink Control Channel (PDCCH) for a first transmission, the UE stays awake to receive on the downlink. Following any new data/signaling reception, the UE (re-) starts an inactivity timer. The UE re-enters DRX operation if the inactivity timer expires or if a MAC Control Element (CE) indicating "DRX" is received. In both cases, the DRX cycle that the UE follows after re-entering DRX is given by the following rules:.

However, Connected Mode DRX is not as power efficient as IDLE Mode DRX (I-DRX). Below a few related aspects are discussed:.

Thus, the following has been observed:
Observation <NUM>: A C-DRX scheme which requires the UE to be able to receive data immediately following its C-DRX ON duration is not as power efficient for the UE as monitoring the paging occasion in I-DRX.

Regarding the validity of the problem described in R2-<NUM> it is herein disagreed with that it is commonly acknowledged that Connected mode DRX is not as power efficient as IDLE Mode DRX (I-DRX). It is however acknowledged that this may be so in some devices, depending on e.g. the implementation etc..

The problem, i.e. the increased power consumption in Connected-DRX, stems from the fact that a legacy UE is required to be able to receive data payload during and immediately following the ON duration, the UE is also expected to decode the data received during the OnDuration and provide HARQ feedback n milliseconds after reception, where n typically corresponds to <NUM>. This consumes more power compared to paging in IDLE state, since the UE immediately has to process the information it receives during the ON duration since there may be data scheduled for the UE. In Idle mode the UE has more time to process the paging channel since the Page response is not required to be sent immediately, it can e.g. be sent in the next or even in a later Random Access Channel (RACH) slot, which does not have to be in every TTI. In order to perform the delay sensitive processing in connected mode DRX, the UE needs to have more processing hardware (HW) activated which consumes more power. The advantage of the Connected mode DRX solution is a shorter delay compared to the IDLE mode procedure, since the UE may receive data immediately. In the IDLE mode procedure however, the UE needs to first send a page response message to the network which adds at least one RTT delay, plus the time it takes to wait for the next RACH slot.

Hence, embodiments herein describe improved methods for handling DRX operation, which may also be referred to as methods for DRX handling, which improves performance and energy consumption of the UE. It will sometimes say that the UE is in DRX state and is not monitoring certain channels. However, it should be appreciated that the DRX feature may only put requirements on when the UE shall be "awake", e.g. be in a non-power-saving-state, and not dictate when the UE shall not be "awake", e.g. be in a sleeping state or a power-saving-state. This means that the UE may be allowed to be in an "awake"/non-power-saving-state all the time, even if the DRX configuration does not require the UE to be in such a state.

It should further be appreciated that while the examples herein state that a UE is communicating with a network node, such as an eNB, it would also be possible to apply the embodiments herein to communication between any types of nodes. For example, in D2D-communication where two or more UEs are communicating with each other. In D2D communication the actions described herein as being performed by the network node, may also be performed by a second UE.

Embodiments herein relate to communication networks in general. <FIG> is a schematic overview depicting a communication network <NUM>. The communication network <NUM> may be a wireless communications network comprising one or more RANs and one or more CNs. The communication network <NUM> may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, <NUM>, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. Embodiments herein relate to recent technology trends that are of particular interest in a <NUM> context, however, embodiments are also applicable in further development of the existing wireless communication systems such as e.g. WCDMA and LTE.

In the wireless communication network <NUM>, wireless devices such as e.g. a UE <NUM>. It should be understood by the person skilled in the art that "wireless device" is a nonlimiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

The wireless communication network <NUM> comprises a network node such as a radio network node <NUM> providing radio coverage over a geographical area, a service area <NUM>, which may also be referred to as a beam or a beam group where the group of beams is covering the service area of a first radio access technology (RAT), such as <NUM>, LTE, Wi-Fi or similar. The radio network node <NUM> may be a transmission and reception point e.g. a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless device within the service area served by the radio network node <NUM> depending e.g. on the first radio access technology and terminology used. The radio network node <NUM> may be referred to as a serving radio network node and communicates with the wireless device <NUM> with Downlink (DL) transmissions to the wireless device <NUM> and Uplink (UL) transmissions from the wireless device <NUM>.

<FIG> discloses a flowchart depicting embodiments of a method performed by the UE <NUM>, for handling DRX operation. Handling DRX shall herein be interpreted as handling the operation of the DRX, such as e.g. handling the duration of the DRX cycles. Actions performed in some embodiments only are marked with dashed boxes.

Action <NUM>: In some embodiments the UE <NUM> may receive a message comprising information regarding actions to be delayed from a network node <NUM>. The message may comprise only an indication that actions may be delayed. The actions to apply the delay to may be specified in a specification. In some further embodiments the message may however also comprise information about e.g. which action or which actions to apply the delay to, the amount of time the action(s) should be delayed, which may also be referred to as delay duration, and/or conditions for when the delays should be applied. The conditions may e.g. be the type of DRX-cycle the UE applies, see also "Conditional applying of behaviors".

In some embodiments the action may be a decoding of a received signal, the information may e.g. comprise a decoding delay to be applied to signals received by the UE <NUM> during a predetermined first time period from the entering of an active state. The active state may be a semi-awake state in which the UE listens for a specific signal which may be received using only a part of a radio unit. The specific signal may e.g. be a signal which is easy to decode. The active state may in some embodiments e.g. be a DRX onDuration period.

The action may also be an exiting of a DRX state and the information may comprise an indication that the UE <NUM> shall exit an inactive state. In this case the information may further comprise a time period within which the UE <NUM> is required to exit an inactive state.

Action <NUM>: The UE <NUM> may receive data and/or signaling when the UE has entered an active state.

Action <NUM>: The UE <NUM> applies a delay for at least one action performed as a response to data and/or signaling received by the UE <NUM> during a predefined first time period TA after the UE <NUM> has entered an active state, which in Example embodiment C, that will be described in the following, is referred to as that the UE woke up recently. In the following the wording predefined and predetermined may be used interchangeably. The UE <NUM> may apply the delay according to information comprised in the message received from the network node <NUM>.

In some embodiments the action may be a decoding of a received signal. The UE <NUM> may apply a first decoding delay D1 for signals received by the UE <NUM> during the predefined first time period from the entering of the active state. The predefined first time period TA may be one or more Transmission Time Intervals, TTl. The UE <NUM> may further apply a second decoding delay D2 for signals received by the UE <NUM> after the predefined first time period TA from entering the active state. The second coding delay D2 may be shorter than the first coding delay D1, hence the first decoding delay is an increased decoding delay. The UE <NUM> may further apply the delay by applying the first decoding delay D1 to data and/or signaling received during the active state. The UE <NUM> may reduce or remove the coding delay when the time from entering the active state has exceeded the predetermined first time period, i.e. when the UE <NUM> has been in the active state for a longer time than the predetermined first time period. The predetermined first time period may herein also be referred to as the first time limit. In the following, the UE <NUM> being in active state may also be referred to as the UE <NUM> being awake. This embodiment corresponds to the Example Embodiment A described below.

In some second embodiments the action may be a transmission of a HARQ feedback. The UE may apply the delay by delaying the transmission of HARQ feedback for DownLink (DL) and/or UpLink (UL) data during a predetermined second time period after the UE has entered the DRX onDuration. The predetermined second time period may be one or more Transmission Time Interval(s) (TTI).

In some embodiments herein the action may be a transmission of Hybrid Automatic Repeat Request (HARQ) feedback. The UE <NUM> may apply the delay by delaying the transmission of HARQ feedback for downlink (DL) and/or uplink (UL) data during a predefined second time period TB, which may herein also be referred to as a time limit, after the UE <NUM> has entered the active state, i.e. when the UE has not been awake for more than the predetermined second time period TB,, see also Example embodiment B. The predefined second time period TB may be one or more TTls. The UE <NUM> may in some embodiments also omit to send a HARQ feedback for DL and/or UL data during the predefined second time period TB after the UE <NUM> has entered the active state, such as e.g. the DRX onDuration. This embodiment corresponds to the Example Embodiment B described below.

In some embodiments the action may be a starting of a timer. The UE <NUM> may apply the delay by applying a delayed starting of the timer during a predefined third time period TC after the UE <NUM> has entered the active state, i.e. if the UE <NUM> has been in the active state for a shorter time than Tc. If the UE <NUM> has been awake for less than the third time period TC, the starting of the timer may be delayed until the third time period TC has passed. Hence, the UE <NUM> may start the timer at a first point in time from an event when the UE <NUM> after the third time period TC has passed and start the timer at a second point in time from an event within the third time period TC, see also Example embodiment C. The timer may e.g. be an inactivityTimer. The predetermined third time period TC may be one or more TTls. The UE <NUM> may in some embodiments apply an adjusted duration of the timer when a delayed starting of the timer has been applied. Thereby the the expiry of the timer may be the same regardless if the UE <NUM> did a delayed start or a non-delayed start of the timer. This embodiment corresponds to the Example Embodiment C described below.

In some embodiments herein, the action may be an entering of a DRX state. When the UE <NUM> has received an indication from a network node <NUM> indicating that the UE <NUM> shall enter an active state, which may also be referred to as the UE <NUM> entering an awake state, when it has been inactive, which may also be referred to as have been sleeping, the UE <NUM> may apply the delay by applying a delay to the entering of the active state. This embodiment corresponds to the Example Embodiment D described below.

The predefined first, second and third time periods TA, TB, TC are shorter than the active state period for receiving data and/or signaling. The predetermined time periods TA, TB, TC may be one or more Transmission Time Interval(s) (TTI).

Example Embodiment A: According to some first embodiments herein the UE may conditionally decode a signal received from the network, such as e.g. from a network node, with a longer delay depending on a configuration received from the network and/or on how long the UE has been in an awake state. For example, the UE may apply a longer decoding delay D1 if the UE has been awake less than a time TA, while applying a shorter decoding delay D2 if the UE has been awake for longer than time TA.

An example of this is illustrated in <FIG> (T = <NUM>). If the UE <NUM> is, according to the DRX-configuration, required to be awake in TTI N, N+<NUM>, N+<NUM> and N+<NUM>, the UE <NUM> would according to this embodiment be allowed to apply a longer decoding delay in TTI N and N+<NUM> than it would be allowed to apply in TTI N+<NUM> and N+<NUM>. This is because the UE <NUM> in TTI N and N+<NUM> would not have been awake for <NUM> TTls yet, but in TTI N+<NUM> and N+<NUM> the UE has been awake for T = <NUM> TTls and hence the UE <NUM> may apply a shorter decoding delay.

The UE <NUM> may of course be allowed to decode the message quickly, however the intention of the embodiments herein is to allow the UE <NUM> to decode slower which may save power. The UE <NUM> may only be allowed to apply this slow decoding for a certain period of time after it has entered active state, which may herein also be referred to as active time. For example, if the UE <NUM> wakes up from an inactive state, such as e.g. non-active time according to a DRX configuration, the UE <NUM> may be allowed to apply the slow decoding only for a short period of time, such as e.g. a few TTls, after it has entered active time which may also be referred to the UE <NUM> being awake.

The UE <NUM> may be allowed to apply slow decoding only during an OnDuration, i.e. data needs to be received during subframes corresponding to an OnDuration timer. The OnDuration may herein also be referred to as a DRX OnDuration. Furthermore, the UE <NUM> may be instructed to apply slow decoding during the OnDuration timer associated with the long DRX cycle. The onDurationTimer specifies the number of consecutive PDCCH-subframe(s) at the beginning of each DRX Cycle (DRX ON), i.e. the number of subframes over which the UE shall read PDCCH during every DRX cycle before entering a power saving mode.

The appended claims are based on Embodiment D, other embodiments are provided as examples useful for understanding the invention.

Example Embodiment B: According to some second embodiments herein, the UE <NUM> may omit or delay HARQ feedback when the UE <NUM> has not been awake for more than a time TB. Alternatively, the UE <NUM> may omit or delay HARQ feedback if it has not been awake during the past time TB. The UE <NUM> behavior for which conditions to omit or delay feedback could be hardcoded in the standard or configured by the network, e.g. by means of the network node <NUM>, using signaling.

In one embodiment the UE <NUM> may omit or delay HARQ feedback for DL and UL data received during the OnDuration timer of the long DRX cycle.

This would for example allow the transmitter in the UE <NUM> to be turned off longer periods of time since the UE <NUM> may not need to start the UL transmitter in the UE <NUM> prior to determining that anything has been received which requires feedback. For example, in LTE today the UE <NUM> should respond with HARQ feedback <NUM> TTls after the UE <NUM> has received something in downlink to ACK/NACK the reception. So if the UE <NUM> is in onDuration, i.e. when the onDuration timer is running, in TTI N, the UE <NUM> would need to ensure that the transmitter needs to be awake at time N+<NUM> to be prepared to send feedback. This may require the UE <NUM> to start the uplink transmitted before N+<NUM> , and maybe even before the UE <NUM> has decoded downlink and knows whether the UE <NUM> needs to respond with HARQ feedback at all. This would therefore result in that the UE <NUM> would activate the uplink transmitter unnecessarily since the UE would activate the uplink transmitter even if the UE <NUM> does not detect any downlink transmission (and hence no feedback should be sent). Hence this embodiment could allow the UE <NUM> to activate the uplink transmitter only when the UE <NUM> has detected a transmission from the network and hence only when feedback needs to be transmitted and hence power could be saved in the UE <NUM>.

Example Embodiment C: According to the DRX-feature in LTE the UE <NUM> is applying an "inactivityTimer" which is started in response to communication with the network. if the network schedules the UE <NUM> for an uplink transmission the UE <NUM> should start the inactivityTimer and stay awake while that timer is running.

According to some third embodiments herein the UE <NUM> may start one or more certain timer, such as e.g. the inactivity timer or a DRX retransmission timer, at a first point in time (relative to an event) if the UE <NUM> has been awake for more than a time TC, while starting the timer(s) at a second point in time (relative to an event) if the UE <NUM> has been awake for less than a time TC. This would allow the UE <NUM> to apply a delayed starting of a timer if the UE <NUM> woke up recently, i.e. less than a time TC ago.

An example of this is shown in <FIG>, w here T=<NUM> and the inactivity timer duration is <NUM> TTls. If the UE <NUM> gets an UL grant in TTI N, the UE <NUM> will apply a delayed starting of inactivityTimer since the UE <NUM> has not been awake for <NUM> TTls. In this example the timer will be started in TTI N+<NUM>. However for the second time the UE <NUM> receives a grant (in TTI N+<NUM>) the UE <NUM> has been awake for <NUM> TTls and hence applies another starting-time for the inactivityTimer and in this example the UE <NUM> (re)starts the inactivity timer directly without any delay.

In some embodiments, when the UE <NUM> applies a delayed starting of the timer, such as e.g. the inactivity timer or a DRX retransmission timer, the UE <NUM> may adjust the timer duration. The benefit of this is that the expiry of the timer may be the same regardless if the UE <NUM> did a delayed start or a non-delayed start. For example, if the UE <NUM> has delayed the starting of a timer T1 seconds and the duration of the timer is T2, the UE <NUM> may adjust the duration of the timer to be T2-T1 which ensures that the timer would end at T2 regardless if the UE <NUM> did a delayed or non-delayed starting of the timer.

In the example scenario as described in <FIG> and with the behavior as described, as described above, if the UE <NUM> receives a grant in TTI N+<NUM> the UE <NUM> would not have been awake for more than <NUM> TTls since the UE <NUM> may just have started the inactivityTimer and hence just entered the "awake"-state. Therefore, according to the embodiment described above, the UE <NUM> may apply a delayed start of the inactivityTimer. However, since the UE <NUM> received a grant in TTI N it may be so that the UE <NUM> could apply a non-delayed starting of the timer(s). Hence, in one embodiment the UE <NUM> may apply a delayed start of the timer if the UE <NUM> has not been active more than a certain time T3 ago. If T3 is set to e.g. <NUM> TTls this would ensure that if the UE <NUM> has been awake recently (less than <NUM> TTls ago) then the UE <NUM> may apply a non-delayed starting of the timer.

A network node <NUM>, such as e.g. an eNB, indicates to the UE <NUM> that the eNB wants the UE <NUM> to exit from a DRX state, which is to enter an awake state from a sleeping state. This will for simplicity be referred to as a "wake up"-message. This "wake up"-message may be a message which does not require heavy processing and hence may be decoded by the UE <NUM> with a limited power consumption. If it e.g. is possible to decode the message very quickly, it may be possible to decode the message without too tight time requirements.

In response to receiving the wake up-message the UE <NUM> is required to exit from a DRX state.

The UE <NUM> is required to exit the DRX state within a certain period of time TWU after receiving/decoding the "wake up"-message.

With a short value TWU the UE <NUM> would be required to quickly wake up which may not allow the UE <NUM> to save a lot of power since the UE <NUM> may not be able to turn off some components within the UE <NUM> since some components may not be possible to turn on/off quickly. However, with a short value TWU it would be a smaller delay for exiting the DRX state and hence latency for starting communication could be lower which may improve performance in terms of user experience, system capacity, etc..

On the other hand, with a long value TWU the UE <NUM> may be able to save more power since it may be able to turn off more components in the UE <NUM> and hence save more power. This may however result in longer delay for waking up and hence longer delay is induced for starting communication which may impair user experience, system capacity, etc..

The value TWU may be specified in a specification and may for example be a certain number of TTls, or a certain number of milliseconds, etc. Another possibility is that the value TWU is configured by the network. The network could determine a suitable value TWU depending on the situation. If for example it is important to quickly start communication a short TWU could be configured, while if power savings in the UE <NUM> is more important a longer TWU could be configured.

In one embodiment herein, the wake up message may be indicated in a Downlink Control Indicator (DCI) of a physical control channel. In this case, the UE <NUM> may not be required to receive data channel if it has been sleeping recently. The physical data channel may be used to indicate pure wakeup signal or wakeup signal together with scheduling grant or assignment to be valid in near future.

In one embodiment, the UE <NUM> only required to monitor physical control signals indicating UL scheduling. This means that the UE <NUM> does not need to monitor and decode downlink data channels at all when it has been sleeping. This behavior can be applicable for the scenario when the UE <NUM> has been inactive over time period TD. Alternatively the UE <NUM> may monitor control signaling related to only UL during an OnDuration of the long DRX cycle. The OnDuration timer and the cycle for the UL related reception may be separately configured by the network.

In the above it has been assumed that the UE <NUM> monitors the "wake up" message when it is in Active Time. In one embodiment herein the eNB may provide a configuration indicating when the UE <NUM> shall monitor the "wake up" message. This may be a periodically occurring time duration and may be configured by a periodicity, and monitoring-duration which indicates for how long (each period) that the UE <NUM> shall monitor for the message. In addition an offset may be provided to the configuration indicating when, in relation to a reference, such as e.g. System Frame Number (SFN) <NUM>, the UE <NUM> monitoring-durations should occur/start.

It should be appreciated that even with the above described explicit configuration for when the UE <NUM> shall monitor for the "wake up" message, the UE <NUM> may also monitor for the "wake up" message in other times, such as e.g. according to the DRX configuration.

<FIG> discloses a flowchart depicting embodiments of a method performed by the network node <NUM>, for handling DRX operation.

Action <NUM>: The network node <NUM> may send a configuration message to the UE <NUM>. The configuration message may comprise information regarding actions to be delayed by the UE <NUM>. The message may comprise information about which action or which actions to apply the delay to, the amount of time the action(s) should be delayed and/or conditions for when the delays should be applied. In some embodiments the action may be a decoding of a received signal, the information may e.g. comprise a decoding delay to be applied to signals received by the UE <NUM> during a predetermined first time period from the entering of an active state. The active state may be a semi-awake state in which the UE listens for a specific signal which may be received using only a part of a radio unit. The specific signal may e.g. be a signal which is easy to decode.

Whether the UE <NUM> applies the behaviors according to the embodiments A to D described herein, such as e.g. slow decoding, delayed timer start, etc., or not may be configured by the network, e.g. by means of the network node <NUM>. This may e.g. be configured using RRC signaling. The network may determine whether to configure the behaviors described herein for the UE <NUM> based on which traffic the UE <NUM> has active, which types of bearers the UE <NUM> has active, the need for power savings for the UE <NUM>, etc..

For example, if the network determines that the UE <NUM> has a voice-bearer configured/active, then there is a chance that voice-traffic may arrive to the UE <NUM>. Hence it may be critical that the UE <NUM> wakes up quickly and quickly decodes traffic, since voice traffic may have tight delay-requirements. Hence, in this scenario the network may configure that the UE <NUM> should not apply slow decoding. This configuration may be performed by sending the configuration message as described in Action <NUM>.

According to another embodiment, the UE <NUM> may apply different behaviors depending on which type of DRX-cycle the UE <NUM> is applying. For example, if the UE <NUM> is applying a long DRX-cycle, the UE <NUM> may apply behaviors which the UE <NUM> does not apply when applying a short DRX-cycle. This is beneficial since long DRX is in general a state where more power should be saved since this is the state when the UE <NUM> does not get frequent data transmissions and hence delay may be acceptable. Hence, the UE <NUM> may apply features described above to reduce the power consumption. It may further be specified in a specification that one or more of the behaviors described above is applied when the UE <NUM> applies a certain type of DRX-cycle. According to another embodiment, the network may configure, depending on the type of DRX-cycle, which behavior(s) the UE <NUM> shall apply.

By applying one or more of the embodiments herein, the delay for communicating a packet may be increased which may negatively impact user experience and system efficiency.

In some embodiments, to avoid this, a DRX configuration may therefore be adjusted to reduce the delay. This may e.g. be done to compensate for the potential longer delay.

This may be performed by a network node <NUM>, such as e.g. an eNB, configuring a DRX configuration for the UE <NUM> which makes the UE <NUM> wake up earlier if it applies the embodiments described herein. For example, the eNB may configure the UE <NUM> to apply a shorter DRX periodicity. This would then make the UE <NUM> wake up more frequently. Consider for example if the "wake up" message is applied where the UE requires an explicit indication to really wake up and the UE <NUM> is given a certain time TWU to actually wake up from the point in time in which the "wake up" message was received. In this case, there would be a delay of time TWU from the point in time where the UE <NUM> receives the "wake up" message until the UE <NUM> actually wakes up. When comparing a legacy UE A (not applying the "wake up" message) with a UE B which requires a "wake up" message to wake up, it would take an additional time TWU to wake up the UE B compared to UE A, since UE A is awake directly while UE B needs a time TWU to wake up. Hence, the network node <NUM>, such as the eNB, may configure the UE B to wake up earlier and/or more frequently, in order to compensate for this additional delay. This configuration may also be performed by sending the configuration message as described in Action <NUM>.

Since it may be implementation dependent whether the UE <NUM> is able to perform, or benefit from, the behaviors described above, the UE <NUM> may indicate to the network if it supports one or more of the behaviors described herein. The network node <NUM>, such as an eNB, may then consider this when determining whether to configure these behaviors for the UE <NUM>.

Applying the delays as disclosed in the embodiments described above, has the advantage that the UE <NUM> may avoid starting up all components every time it enters the onDuration which leads to a reduction of the power consumption of the UE <NUM>.

It should be noted that the embodiments described herein are not mutually exclusive, rather they can be combined in any suitable manner.

<FIG> is a block diagram depicting the UE <NUM> for performing the method for handling DRX operation. The UE <NUM> may comprise a processor <NUM>, such as e.g. a processing circuitry, configured to perform the method as described herein, as performed by the UE <NUM>. Dashed lines of a box in <FIG> indicate that this box is not mandatory and relate to some embodiments only.

The UE <NUM> is configured to apply a delay for at least one action performed as a response to data and/or signaling received by the UE <NUM> during a predefined first time period after the UE <NUM> has entered an active state.

The UE <NUM> may further be configured to apply a first decoding (D1) delay for signals received by the UE <NUM> during a predetermined first time period from the entering of the active state when the action is a decoding of a received signal. The first decoding delay (D1) is a longer decoding delay and the second decoding delay (D2) is a shorter decoding delay. Hence, the first decoding delay (D1) is an increased decoding delay in comparison to a second decoding delay (D2).

In some embodiments the UE <NUM> may further be configured to reduce or to remove the coding delay when the time from entering the active state has exceeded the predetermined first time limit.

The UE <NUM> may further be configured to apply the increased decoding delay only for data received during the active state.

The UE <NUM> may further be configured to delay the transmission of HARQ feedback for Downlink (DL) and/or UpLink (UL) data during a predetermined second time period after the UE <NUM> has entered the active state.

The UE <NUM> may further be configured to omit to send a HARQ feedback for DownLink, DL, and/or UpLink, UL data during the predetermined second time period after the UE <NUM> has entered the active state.

The UE <NUM> may further be configured to apply a delayed starting of the timer, such as the inactivity timer, during a predetermined third time period after the UE <NUM> has entered the active state.

The UE <NUM> may further be configured to apply an adjusted duration of the timer, such as the inactivity timer, when a delayed starting of the timer has been applied.

The UE <NUM> may further be configured to receive an indication from the network node <NUM>, indicating that the UE <NUM> shall enter an awake state when it has been sleeping, and wherein the UE <NUM> may further be configured to apply a delay to the entering of the awake DRX state when the UE <NUM> has received an indication from the network node <NUM> that the UE <NUM> shall enter the awake state.

The UE <NUM> may further be configured to receive a message from a network node <NUM>, which message comprises information regarding the actions to be delayed, and wherein the UE <NUM> may further be configured to apply the delay according to the information comprised in the message.

The UE <NUM> may further comprise a memory <NUM>. The memory <NUM> may comprise one or more units to be used to store data on, such as system information, applications to perform the methods disclosed herein when being executed, and similar.

The methods according to the embodiments described herein for the UE <NUM> may respectively be implemented by means of e.g. a computer program <NUM> or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the determining module. The computer program <NUM> may be stored on a computer-readable storage medium <NUM>, e.g. a disc or similar. The computer-readable storage medium <NUM>, having stored thereon the computer program, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE <NUM>. In some embodiments, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

The embodiments herein may be implemented through one or more processors, such as the processor in the UE <NUM> depicted in <FIG>, and/or a processor in a network node together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the UE and/or the network node. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the UE and/or the network node.

According to a possible implementation, shown in <FIG>, the UE <NUM> may comprise a delay module <NUM>, a receiving module <NUM>, a processing module <NUM> and/or a transmitting module <NUM> configured for performing the method described herein, as performed by the UE <NUM>.

In some embodiments, the UE <NUM> may comprise the delay module <NUM> being configured to apply a delay for at least one action performed as a response to data and/or signaling received by the UE <NUM> during a predefined first time period after the UE <NUM> has entered an active state.

In some embodiments, the UE <NUM> may comprise the delay module <NUM> further being configured to apply a first decoding (D1) delay for signals received by the UE <NUM> during a predetermined first time period from the entering of the active state when the action is a decoding of a received signal. The delay module <NUM> may further being configured to, reduce or to remove the coding delay when the time from entering the active state has exceeded the predetermined first time limit.

In some embodiments the delay module <NUM> may further being configured to apply the increased decoding delay only for data received during the active state.

In some embodiments the UE <NUM> may comprise the delay module <NUM> or the transmitting module <NUM> being configured to delay the transmission of HARQ feedback for DownLink (DL) and/or UpLink (UL) data during a predetermined second time period after the UE <NUM> has entered the active state.

In some embodiments the delay module <NUM> may further be configured to omit to send a HARQ feedback for DownLink, DL, and/or UpLink, UL data during the predetermined second time period after the UE <NUM> has entered the active state.

In some embodiments the delay module <NUM> may further be configured to apply a delayed starting of the timer, such as the inactivity timer, during a predetermined third time period after the UE <NUM> has entered the active state.

In some embodiments the delay module <NUM> may further be configured to apply an adjusted duration of the timer, such as the inactivity timer, when a delayed starting of the timer has been applied.

In some embodiments the UE <NUM> may comprise the receiving module <NUM> being configured to receive an indication from the network node <NUM> indicating that the UE <NUM> shall enter an awake state when it has been sleeping. The UE <NUM> may further comprise a processing module <NUM> or the delay module <NUM> further being configured to apply a delay to the entering of the awake DRX state when the receiving module has received an indication from the network node <NUM> that the UE <NUM> shall enter the awake state.

In some embodiments the receiving module <NUM> may further be configured to, receive a message from a network node <NUM>, which message comprises information regarding the actions to be delayed. The delay module <NUM> may further be configured to, apply the delay according to the information comprised in the message.

As will be readily understood by those familiar with communications design, that functions means or modules described herein may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a network node, for example.

Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term "processor" or "controller" as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and/or program or application data, and nonvolatile memory. Designers of network nodes will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

Fig. <NUM> is a block diagram depicting the network node <NUM> for performing the method for handling DRX operation. The network node <NUM> may comprise a processor801, such as e.g. a processing circuitry,, configured to perform the method as described herein, as performed by the network node <NUM>. Dashed lines of a box in Figure <NUM> indicate that this box is not mandatory and relate to some embodiments only.

The network node <NUM> is configured to send a configuration message to the UE <NUM>, which message comprises information regarding actions to be delayed by the UE <NUM>.

In some embodiments, the network node <NUM> may be configured to send a configuration message to the UE <NUM>, which message comprises information regarding actions to be delayed by the UE <NUM>.

The network node <NUM> may further comprise a memory <NUM>. The memory <NUM> may comprise one or more units to be used to store data on, such as system information, applications to perform the methods disclosed herein when being executed, and similar.

The methods according to the embodiments described herein for the network node <NUM> may respectively be implemented by means of e.g. a computer program <NUM> or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node. The computer program <NUM> may be stored on a computer-readable storage medium <NUM> e.g. a disc or similar. The computer-readable storage medium <NUM> having stored thereon the computer program, may comprise instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the network node. In some embodiments, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

The embodiments herein may be implemented through one or more processors, such as the processor network node <NUM> depicted in Figure <NUM> together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the UE and/or the network node. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the UE and/or the network node.

According to a possible implementation, shown in <FIG>, the network node <NUM> may comprise a sending module <NUM> being configured to send a configuration message to the UE <NUM>, which message comprises information regarding actions to be delayed by the UE <NUM>.

Thus, the methods according to the embodiments described herein performed by the UE <NUM> and/or the network node <NUM> may be implemented by means of a computer program product, comprising instructions, i.e. software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE <NUM> and/or the network node <NUM>. The computer program product may be stored on a computer-readable storage medium. The computer-readable storage medium, having stored there on the computer program, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE <NUM> and/or the network node <NUM>. In some embodiments, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

The UE <NUM> and/or the network node <NUM> may further each comprise a memory comprising one or more memory units. The memory is arranged to be used to store obtained information such as indications of a mobility set, identifiers of APs and WLANs, identifiers of UEs, ciphering keys, measurements of signals from radio access nodes, measurement reports or parts thereof and applications etc. to perform the methods herein when being executed in the UE and/or the network node.

In some embodiments, a computer program comprises instructions, which when executed by the at least one processor such as the processor <NUM> and/or <NUM>, cause the at least one processor <NUM> and/or <NUM> to perform actions according to any of the above Actions.

Claim 1:
A method, performed by a User Equipment, UE, for handling discontinuous reception, DRX, operation, wherein the method comprises:
receiving a wake up message from a network node while the UE is in a sleeping state, wherein the wake up message indicates that the UE is required to exit the sleeping state and entering an awake state within a certain period of time after receiving or decoding the wake up message introducing a delay of time, TWU, from the point in time where the UE receives the wake up message until the UE actually wakes up.