The present invention relates to wireless communication systems. More particularly, a method and apparatus is disclosed for enhancing discontinuous reception (DRX) in wireless systems.
A goal of the Long Term Evolution (LTE) program of the Third Generation Partnership Project (3GPP) is to bring new technology, network architecture, configurations and applications and services to wireless networks in order to provide improved spectral efficiency, reduced latency, faster user experiences and richer applications and services with less cost. LTE's aim is to create an Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
In an LTE compliant network, discontinuous reception (DRX) operation is used by a wireless transmit/receive unit (WTRU) to save power. DRX allows the WTRU to sleep during regular intervals and wake up at specific time instances to verify if the network has data for it.
The RRC protocol 112 may operate in two states: RRC_IDLE and RRC_CONNECTED. While in RRC_IDLE state the WTRU DRX cycle is configured by signaling over the NAS protocol 108. This state includes system information broadcasts, paging, and cell resection mobility. A WTRU in RRC_IDLE state preferably is allocated an ID number that identifies the WTRU in a tracking area. No RRC protocol context is stored in an eNB.
In the RRC_CONNECTED state, the WTRU may make a connection with an E-UTRAN. The E-UTRAN knows the cell to which the WTRU belongs to so that the network can transmit and receive data to/from the WTRU. In the RRC_CONNECTED state, the network controls mobility (handover) and the WTRU conducts neighbor cell measurements. Furthermore, at the RLC/MAC level, a WTRU can transmit data to, and receive data from, the network and monitors a control signaling channel for a shared data channel to see if any transmission over the shared data channel has been allocated to the WTRU. The WTRU also reports channel quality information and feedback information to the eNB. A DRX/discontinuous transmission (DTX) period can be configured according to WTRU activity level for power saving and efficient resource utilization. This is typically under control of the eNB.
The NAS protocol 108 may operate in an LTE_DETACHED state, in which there is no RRC entity. The NAS protocol 108 may also operate in an LTE_IDLE state. Also, the NAS protocol 108 may operate in an RRC_IDLE state, while in LTE_DETACHED state, during which some information may be stored in the WTRU and in the network, such as IP addresses, security associations, WTRU capability information and radio bearers. Decisions regarding state transitions are typically decided in the eNB or the aGW.
The NAS protocol 108 may also operate in an LTE_ACTIVE state, which includes an RRC_CONNECTED state. In this state, state transitions are typically decided in the eNB or the aGW.
DRX may be activated in LTE_ACTIVE state, which corresponds to the RRC_CONNECTED state. Some of the services that would run in the LTE_ACTIVE state are those services generating small packets on a regular basis, such as VoIP. Also, those services generating delay insensitive bulk packets on an infrequent basis, such as FTP, may run in the LTE_ACTIVE, as well as those services generating small packets on a rare basis, such as presence service.
Based on the characteristics of the aforementioned services, data transmission/reception may be performed during DRX operation without RRC signaling. Also, a DRX cycle length should be long enough for battery power savings. Furthermore, the amount of data transmitted within a DRX cycle should be variable from cycle by cycle. For example, DRX for FTP service may allow an increase in the amount of data for each DRX cycle.
The DRX cycle length 206 may be determined by the network, considering the quality of service (QoS) requirements of a service activated in the WTRU. Active period start positions should be unambiguously identified by both the WTRU and the eNB.
At an active period start position, the WTRU may monitor an L1/L2 control channel during a predefined time interval to see whether there is incoming data. A length of the active period 202 may be variable, depending on the amount of data to be transmitted during the DRX cycle 206. An end position of active period 202 may be explicitly signaled by the eNB or implicitly assumed after inactivity of the predefined time interval. Uplink data transmission can be initiated anytime during the sleep period 204. Active period uplink data transmission may end when the uplink transmission is completed.
A low level DRX signal 304 is signaled by the MAC layer. A low level DRX interval 308 is flexible and may support fast changes in the DRX interval. A MAC header may carry information regarding low level settings.
Dependence between the high level DRX 302 and low level DRX 304 should be at a minimum because the high level DRX interval 306 can be used as fallback DRX interval in case of any errors occur applying the lower level DRX interval 308. The network and the WTRU preferably are synchronized with the high layer DRX interval 306.
The relatively long high level DRX interval 306 is beneficial for WTRU power savings, but limits downlink (DL) scheduling flexibility and throughput. If there is a significant amount of data buffered in an eNB or WTRU transmission buffer, it may be beneficial to change the short low level DRX interval 308 for a period of time suitable for the transmission of the buffered data. After the data transmission, the WTRU and the eNB could resume the high level DRX interval 302.
As shown in Table 1, DRX may be split between regular signals and interim signals.
Signaling DRX in the RRC is based on the regularity of the basic connection requirements and may result in a regular DRX signal ensuring the requirements of the connection. Regular DRX is determined in the eNB. A WTRU should know, through RRC signaling, to apply regular DRX. In other words, when a WTRU enters active mode, one of the RRC parameters delivered to the WTRU will be the regular DRX parameters to be applied. While in active mode the eNB can change, at any point in time and through RRC signaling, the regular DRX parameters used by the WTRU.
MAC layer DRX may be able to handle fast and irregular changes such as, for example, an instantaneous increase of data throughput. The MAC layer interim DRX may be temporary. Interim DRX settings preferably are determined in the eNB. A WTRU acquires information regarding which interim DRX parameters to apply through MAC signaling. MAC signaling from the eNB to the WTRU may include interim DRX information. The WTRU may apply the interim DRX according to network instructions. Applying interim DRX does not affect the regular DRX interval. When a WTRU no longer applies interim DRX it will resume regular DRX.
A method and apparatus for discontinuous reception (DRX) in a wireless transmit receive unit (WTRU) is disclosed. The method preferably includes a WTRU receiving DRX setting information over a radio resource control (RRC) signal, and the WTRU receiving DRX activation information over medium access control (MAC) signal. The method may also include the WTRU grouping DRX setting information into a DRX profile and determining a DRX profile index associated with the DRX profile. The method may also include the WTRU, in a DRX minimum active period, receiving a data indication signal from an eNB and remaining in an active period based on the data indication signal.
A more detailed understanding may be had from the following description, given by way of example and to be understood in conjunction with the accompanying drawings wherein:
When referred to hereafter, the terminology “wireless transmit/receive unit (WTRU)” includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a wireless environment. When referred to hereafter, the terminology “base station” includes but is not limited to a Node-B, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.
Two layer DRX operation may include a regular DRX operation controlled by RRC signaling and an interim DRX operation controlled by MAC signaling. The use of RRC signaling takes advantage of the reliability and robustness of RRC signaling in general. Reliability is achieved via response or acknowledgement messages that are generated at the RRC layer or via the use of the acknowledged mode (AM) service of the RLC layer. Also, ciphering and integrity protection are required for RRC signaling, thus making an RRC signal a reliable signal.
A MAC signal is used for speed. MAC signaling is generally faster to generate and to process than RRC signaling. Interim DRX operations that use MAC signaling may be flexible, but do not include the reliability and security aspects that are provided in RRC signaling and not MAC signaling.
DRX signaling information can be classified into two categories: 1) DRX settings, parameters or configurations, such as DRX cycle periodicity, for example, and 2) DRX activation commands, such as to turn DRX on or off, for example.
The DRX settings, parameters or configuration information is preferably signaled reliably, robustly and securely. Interim DRX RRC signaling parameters and configuration information may be communicated via RRC signaling. However, DRX activation commands that, for example, instruct the WTRU to enter DRX mode, are preferably signaled quickly via MAC signaling. For example, the commands to enter or exit interim DRX are signaled via MAC signaling.
In an alternative, some DRX settings, parameters, or configuration information may be signaled with the DRX activation commands.
Sets of DRX setting information can be grouped to form a DRX profile. A DRX Profile ID may be used to indicate the DRX profile. RRC signaling may be used to define a DRX profile and attach it to a DRX Profile ID. The DRX profile may be used with interim DRX, regular DRX, or any other DRX mode. Once the profiles are setup or preconfigured, an eNB and a WTRU may exchange DRX activation commands that may reference an appropriate DRX Profile ID for the WTRU. The activation commands may be RRC signals, but are preferably MAC signals.
The WTRU may dynamically apply the DRX parameter information in a particular DRX profile using MAC signaling that makes reference to the DRX profile ID, rather than having to specify and detail all DRX parameters. An interim DRX activation signal may reference a DRX Profile ID, or may contain some DRX settings that were not included in the RRC signaling. This signaling method may be applied to any level DRX or any type of DRX operation in general.
A DRX cycle may contain an active period and a sleep period. The active period start positions may be unambiguously identified by both a WTRU and an eNB, while the active period length may be variable and depend on an amount of data to be transmitted during the DRX cycle.
A DRX signaling message may specify an activation time or a start time that is used to indicate a time to activate the DRX cycle or enter into DRX mode. An activation time can be indicated in absolute terms, or relative to the present time, to ensure that the both the WTRU and the eNB unambiguously identify the start of the DRX cycle. MAC or RRC signaling messages used for DRX may include a DRX activation or start time.
A WTRU may remain in an awake DRX mode for a minimum active period. The minimum active period preferably is communicated in a DRX signaling message, either RRC or MAC, or it can be predefined. The minimum active period may be used for a number of activities. For example, it may be used to increase DRX flexibility, increase DRX robustness, or ensure that if a WTRU has missed some transmissions it will stay awake to receive them in an expedited manner.
DRX structure may be defined periodically, for example, one DRX cycle every 50 msec. In order to increase the flexibility of DRX, another mode of DRX operation may be utilized whereby a DRX cycle start time is defined during a previous DRX cycle. This mode can be used independent of, or in addition to, the periodic mode of DRX operation. As an example, during the active period of a DRX cycle, once the WTRU has received its intended data and there are no further packets to transmit to that WTRU at the eNB, the eNB may instruct the WTRU via a signaling message, either MAC or RRC, to go to sleep for a predetermined time and/or wake up at a predetermined time.
Additionally, it may be advantageous under certain circumstances to keep the WTRU awake during a DRX cycle instead of allowing it to go to sleep until the next DRX cycle. In order to achieve that, a DRX signaling message, either MAC or RRC, may be used to instruct the WTRU to stay awake until a specified time, such as, the next DRX cycle, for example.
A WTRU may, by default, enter DRX once it is in the active/connected state. As an alternative, signaling messages may be used to exchange capability information regarding whether the WTRU supports DRX operation in the active/connected state. An eNB may obtain the WTRU's active mode DRX capability and any other parameters associated with such capability. Accordingly, the eNB may instruct the WTRU to go into active mode DRX as it deems necessary.
A WTRU may remain awake for a minimum active period. During this period, the eNB may use Layer 1, Layer 2 or Layer 3 signaling messages to indicate whether data will be transmitted to the WTRU during a particular DRX cycle. The WTRU may stay in the active period until the beginning of the next DRX cycle. The WTRU will not sleep following the reception of its data until the beginning of the next DRX cycle.
The WTRU may wait for an explicit signal from the eNB to indicate the presence of data for a particular WTRU. IF the WTRU does not receive an indication from the eNB, the WTRU may determine that no signal was transmitted or the signal went missing but shall stay awake because there might be something on the downlink for the WTRU
In an alternative embodiment, if the eNB has not or will not transmit data for the WTRU during this DRX cycle, it does not send the command 708. The WTRU may interpret the lack of command as an indication that it can go back to sleep until the next DRX cycle, as it has no data to receive.
A WTRU that is not in DRX mode may send a signaling message to an eNB indicating that the WTRU wants to enter DRX mode. The signaling can be RRC, MAC, or PHY signaling. The WTRU may use a trigger to generate the signaling, such as, the detection of an idle time or inactivity time following the reception of data by the WTRU, for example. There may be other triggers as well. Upon receiving the signaling message, the eNB generates a response signal to instruct the WTRU to go into DRX operation and the DRX settings.
A DRX cycle is typically associated with a single WTRU. However, for multimedia broadcast/multicast service (MBMS), it is difficult to broadcast to multiple WTRUs that have different DRX cycles. Therefore, an eNB or a radio access network (RAN) may define an “MBMS DRX” cycle that is common for a group of WTRUs. One-to-one signaling messages can be exchanged between the eNB and a WTRU to set up and confirm the MBMS DRX cycle. In an alternative embodiment, the MBMS DRX cycle can be set up via multicast or broadcast messages, for example, on a broadcast channel. In another alternative embodiment, the MBMS DRX cycle can be implicit or derived from a predetermined MBMS scheduling pattern. A WTRU may power down its MBMS transceiver during an MBMS DRX cycle.
It is preferable to coordinate between the MBMS traffic or the MBMS DRX cycle and the WTRU's normal DRX cycle. For example, MBMS traffic can be scheduled with the DRX cycle of the WTRU. This scheme may be less flexible if there are many WTRUs involved in MBMS that have different DRX cycles, but may lead to increased efficiency since the WTRU will have aligned DRX and MBMS intervals.
During DTX, a WTRU transmits during pre-determined intervals, and sleeps during the rest. Coordination between DTX and DRX may be utilized, and the DRX and DTX intervals/cycles may coincide as much as possible, in order to allow maximum efficiency in power consumption. For example, uplink resource assignment can be performed periodically. Aligning the uplink resource assignment with the DRX period may result in greater efficiency. In particular, periodic thin channel assignments can coincide with the DRX cycle.
System messages related to handover are critical. If a DRX cycle is too long, a WTRU may react too late to handover commands, which can cause complete failure of transmission and reception. Accordingly, the handover timing should be a consideration when the DRX cycle is determined, adjusted and signaled by an eNB.
For example, when a WTRU is close to a cell edge a measurement cycle may be required to be shorter than the normal DRX cycle in LTE active mode. Therefore, a signaling message may be sent to the WTRU to reconfigure the DRX cycle to reflect the WTRU being close to a cell edge.
Additionally, when a neighbor cell's measurements are strong, meaning it is a high probability that handover may occur, the DRX cycle should be turned off by the eNB by sending a signaling message or command to the WTRU. The WTRU may continuously monitor its own and its neighbor cell's reference signal, to, for example, prepare autonomous timing adjustment, or to prepare for any handover related activity. In general, when the serving cell's signal strength or transmission quality indicator is below a certain threshold, the WTRU preferably is not be put into DRX mode in order to give the WTRU a better chance to make measurements and try and sustain the call.
WTRU mobility aspects may also be a factor in determining the DRX cycle in LTE active mode. Separate DRX settings may be implemented for different services, such as VoIP, web browsing traffic and the like. A WTRU may have multiple separate or independent DRX cycles for each of the services, or a WTRU may have a single DRX cycle whose DRX settings/parameters satisfy the most frequent traffic pattern. If multiple DRX cycles are used, the cycles may be aligned or coincide as much as possible, in order to maximize the potential for power savings.
Although the features and elements are described in the embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the embodiments or in various combinations with or without other features and elements. The methods or flow charts provided may be implemented in a computer program, software, or firmware tangibly embodied in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) module.
This application is a continuation of U.S. patent application Ser. No. 14/717,145, filed May 20, 2015, which is a continuation of U.S. patent application Ser. No. 13/526,104, filed Jun. 18, 2012; which issued as U.S. Pat. No. 9,066,350, on Jun. 23, 2015, which is a continuation of U.S. patent application Ser. No. 11/924,484, filed Oct. 25, 2007, which issued as U.S. Pat. No. 8,228,829, on Jul. 24, 2012; which claims the benefit of U.S. Provisional Patent Application No. 60/863,185, filed Oct. 27, 2006, the contents of which are hereby incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
4248922 | Shortway et al. | Feb 1981 | A |
4291097 | Kamada et al. | Sep 1981 | A |
5532113 | Frechet et al. | Jul 1996 | A |
6028153 | Jung | Feb 2000 | A |
6284321 | Brindoepke et al. | Sep 2001 | B1 |
6344307 | Kojima et al. | Feb 2002 | B1 |
6485895 | Choi et al. | Nov 2002 | B1 |
6803176 | Choi et al. | Oct 2004 | B2 |
7574226 | Takano et al. | Aug 2009 | B2 |
7916675 | Dalsgaard et al. | Mar 2011 | B2 |
8228829 | Sammour et al. | Jul 2012 | B2 |
8412211 | Petrovic | Apr 2013 | B2 |
8521139 | Vayanos | Aug 2013 | B2 |
8572250 | Rinne et al. | Oct 2013 | B2 |
8682376 | Franceschini | Mar 2014 | B2 |
8818321 | Dalsgaard | Aug 2014 | B2 |
9066350 | Sammour et al. | Jun 2015 | B2 |
20020045458 | Parantainen et al. | Apr 2002 | A1 |
20030185162 | Fraser | Oct 2003 | A1 |
20040029596 | Kim et al. | Feb 2004 | A1 |
20040043798 | Amerga | Mar 2004 | A1 |
20040116110 | Amerga et al. | Jun 2004 | A1 |
20050009527 | Sharma | Jan 2005 | A1 |
20050063304 | Sillasto et al. | Mar 2005 | A1 |
20050111599 | Walton et al. | May 2005 | A1 |
20050153751 | Bultan | Jul 2005 | A1 |
20050195852 | Vayanos et al. | Sep 2005 | A1 |
20060029011 | Etemad et al. | Feb 2006 | A1 |
20060094441 | Beckmann et al. | May 2006 | A1 |
20060195576 | Rinne et al. | Aug 2006 | A1 |
20070170485 | Shimada et al. | Jul 2007 | A1 |
20070183355 | Kuchibhotla et al. | Aug 2007 | A1 |
20070291728 | Dalsgaard | Dec 2007 | A1 |
20070291729 | Dalsgaard | Dec 2007 | A1 |
20080101268 | Sammour | May 2008 | A1 |
20090260667 | Chen et al. | Oct 2009 | A1 |
20110003600 | Beckmann et al. | Jan 2011 | A2 |
20120170485 | Maeda et al. | Jul 2012 | A1 |
Number | Date | Country |
---|---|---|
1222271 | Jul 1999 | CN |
0536099 | Apr 1993 | EP |
1841249 | Oct 2007 | EP |
0937344 | Feb 1997 | JP |
2006-501705 | Jan 2006 | JP |
10-2003-0097373 | Dec 2003 | KR |
2120181 | Oct 1998 | RU |
200503571 | Jan 2005 | TW |
WO 1997049201 | Dec 1997 | WO |
WO 2004012359 | Feb 2004 | WO |
WO 2004095860 | Nov 2004 | WO |
WO 2005117297 | Dec 2005 | WO |
WO 2007145006 | Dec 2007 | WO |
WO 2008063474 | May 2008 | WO |
Entry |
---|
3rd Generation Partnership Project (3GPP), R2-040415, “MTCH Discontinuous Transmission and Reception”, LG Electronics, TSG-RAN Working Group 2 #41, Malaga, Spain, Feb. 16-20, 2004, pp. 1-7. |
3rd Generation Partnership Project (3GPP), R2-060888, “DRX and DTX Operation in LTE_Active”, Panasonic, 3GPP TSG-RAN WG2 Meeting #52, Athena, Greece, Mar. 27-31, 2006, 3 pages. |
3rd Generation Partnership Project (3GPP), R2-061200, “Paging for LTE”, Qualcomm Europe, 3GPP TSG-RAN WG 2 Meeting #53, Shanghai, China, May 8-12, 2006, pp. 1-3. |
3rd Generation Partnership Project (3GPP), R2-061981, “Paging in RRC_CONNECTED State”, ETRI, 3GPP TSG RAN WG2 ad-hoc on LTE, Cannes, France, Jun. 27-30, 2006, 3 pages. |
3rd Generation Partnership Project (3GPP), R2-062027, “Text Proposal on Clarification on Difference of RRC and MAC Control”, NTT DoCoMo, Inc., 3GPP TSG RAN WG2 Ad Hoc on LTE, Cannes, France, Jun. 27-30, 2006, 2 pages. |
3rd Generation Partnership Project (3GPP), R2-062752, “Active Mode DRX”, Nokia, 3GPP TSG-RAN WG2 Meeting #55, Seoul, Korea, Oct. 9-13, 2006, 3 pages. |
3rd Generation Partnership Project (3GPP), R2-062753, “Active Mode DRX Details”, Nokia, 3GPP TSG-RAN WGx Meeting #55, Seoul, Korea, Oct. 9-13, 2006, 10 pages. |
3rd Generation Partnership Project (3GPP), Tdoc R2-062778, “DRX Operations for Connected Mode UEs in LTE”, Samsung, 3GPP TSG-RAN2 Meeting #55, Seoul, Korea, Oct. 9-13, 2006, 3 pages. |
3rd Generation Partnership Project (3GPP), TS 25.321 V6.10.0, “Technical Specification Group Radio Access Network, Medium Access Control (MAC) Protocol Specification (Release 6)”, Sep. 2006, pp. 1-91. |
3rd Generation Partnership Project (3GPP), TS 36.300 V.8.2.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Overall Description, Stage 2 (Release 8)”, Sep. 2007, pp. 1-109. |
3rd Generation Partnership Project (3GPP), TS 36.300 V0.1.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Overall Description, Stage 2 (Release x)”, 2006, pp. 1-57. |
3rd Generation Partnership Project (3GPP), Tdoc R2-060967, “DRX and DTX in LTE_Active”, Ericsson, TSG-RAN WG2, Meeting #52, Athens, Greece, Mar. 27-31, 2006, 1-5 pages. |
Number | Date | Country | |
---|---|---|---|
20170048921 A1 | Feb 2017 | US |
Number | Date | Country | |
---|---|---|---|
60863185 | Oct 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14717145 | May 2015 | US |
Child | 15336258 | US | |
Parent | 13526104 | Jun 2012 | US |
Child | 14717145 | US | |
Parent | 11924484 | Oct 2007 | US |
Child | 13526104 | US |