The present application is related to wireless communications.
The Third Generation Partnership Project (3GPP) has initiated the Long Term Evolution (LTE) program to bring new technology, new network architecture, new configurations and new applications and services to wireless cellular networks in order to provide improved spectral efficiency and faster user experiences.
In order for a wireless transmit receive unit (WTRU 101) to perform various procedures related to sleep, monitoring the paging cycles, cell reselection or using a random access channel (RACH), a network would typically signal a number of parameters to the WTRU in system information messages. Some of these parameters can also be used when the WTRU is in an active state, including, but not limited to, reduced neighbor cell lists, measurement reporting and handover parameters. There is a need to put all necessary parameters together and group them into system information messages for use by the WTRU in procedures and methods for sleep, reselection or RACH procedures.
Within a core network (CN) domain system information, information for a discontinuous reception (DRX) would typically be signaled to a WTRU 101 in idle mode in an information element (IE) (e.g., CN_DRX_cycle_length_coefficient). However, DRX exists in active mode as well as idle mode. Therefore, it would be beneficial to signal a DRX cycle length for the active mode.
When a WTRU 101 is camped on a cell, it regularly searches for a better cell according to a set of criteria. If a better cell is found, that cell is selected. In an LTE system with only two states LTE_Idle and LTE_active, the WTRU 101 can perform cell reselection only in the LTE_Idle state. The WTRU 101 uses parameters broadcasted from the system, including, but not limited to the following parameters that are transmitted in a system information block (SIB), such as SIB 3, SIB 4 and/or SIB 11:
A wireless transmit/receive unit (WTRU 101) is configured to receive system level information, such as discontinuous reception (DRX) information, cell reselection information and random access channel (RACH) information, in the form of system information blocks (SIBs) or dedicated radio resource control (RRC) message signaling. The WTRU 101 autonomously processes the received parameters and alters its behavior with respect to sleep mode, cell reselection and using RACH signatures.
One or more techniques are contemplated for a wireless transmit/receive unit (WTRU), that may include receiving, via a receiver, information as a plurality of parameters defined as information elements (IEs) for a physical random access channel (PRACH) operation of the WTRU. Techniques may include processing, via a processor, the received parameters to perform PRACH operations by the WTRU. The IEs may include PRACH system information. The PRACH system information may include a random access channel (RACH) response window size. The RACH response window size may be provided as a number of subframes. Techniques may include receiving, via the receiver, one or more RACH responses sent to the WTRU over the RACH response window.
One or more techniques are contemplated for an evolved NodeB (eNB), where the eNB may include a processor. The processor may be configured to determine a plurality of parameters for physical random access channel (PRACH) operations. The plurality of parameters may include PRACH system information. The PRACH system information may include a random access channel (RACH) response window size. The RACH response window size may be provided as a number of subframes. The eNB may include a transmitter. The transmitter may be configured to transmit the plurality of parameters defined as information elements (IEs) for a PRACH operation of a wireless transmit/receive unit (WTRU). The transmitter may be configured to transmit one or more RACH responses to the WTRU over the RACH response window.
A more detailed understanding may be had from the following description, given by way of example 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.
In a first example of defining SIBs with system level information, a system information block 1 (SIB1) may be defined by information elements and related information as shown in Table 1. Each of the IEs shown in Table 1, as well as all tables shown herein, may be defined and provided to the WTRU 101 on a need basis that includes, but is not limited to, the following: mandatory, mandatory with a default value available, conditional on a value, or optional.
As shown in Table 1, the core network (CN) IEs include common GSM-mobile application part (MAP) non-access stratum (NAS) system information and domain system information for the packet switched (PS) domain. These IEs inform the WTRU 101 about the serving CN and domain system. The LTE network operates only in a packet switched (PS) domain. Therefore, there is no need to maintain any other domain information. Only PS domain information is required to be signaled.
In the LTE specification, DRX operates in both explicit and implicit modes. DRX parameters may be signaled by two IEs that can carry specific DRX parameters for each mode of operation. The IE can carry both DRX explicit mode parameters and DRX implicit mode parameters. These IEs can be signaled with the domain system information or may be transmitted with another message, such as a RRC_Connection_Command message for example.
Table 2 shows an example of LTE idle mode and LTE active mode DRX configuration IEs and associated parameters for this embodiment, for which the WTRU 101 is configured to receive and process. An IE for CN DRX cycle period length in LTE idle mode indicates the length of the entire DRX cycle for the WTRU 101 to use while receiving paging in idle mode. An IE for LTE active mode parameters indicates to the WTRU 101 whether LTE active mode parameters are to be the same as the idle mode parameters, or different than the idle mode parameters. If different, the network may then specify a different set of active mode parameters. In order to allow the WTRU 101 to synchronize to the DRX cycle, an IE for DRX cycle start time is defined. In this example, the cell system frame number (SFN) is used as a reference for the DRX cycle start time. A choice IE, Choice Signaling Method, is defined by the network and received by the WTRU 101 to indicate the type of DRX signaling method being employed, which is either explicit type or implicit type, explained later in further detail with respect to Tables 3 and 4.
Table 3 shows a summary of an exemplary configuration for information elements used in explicit DRX signaling. As a choice IE, the DRX configuration mode may indicate either a Full Configuration or a Predefined Configuration mode. For the Full Configuration mode, the network provides all of the DRX parameters to the WTRU 101. In the Predefined Configuration mode, the WTRU 101 uses default DRX parameters that are predefined by the network. The DRX profile ID information element can be used for defining different DRX profiles which can be used for changing the DRX lengths and other parameters during various procedures, including 3GPP to non-3GPP handovers.
Table 4 shows a summary of an exemplary configuration for information elements used in implicit DRX signaling. As shown, the IE for Implicit DRX State and Transition List may have multiple instances in the signaling to the WTRU 101, one per maximum number of DRX states. Similar to the Explicit DRX explained above, there is a choice IE for DRX configuration mode, for either a Predefined configuration or a Full Configuration. Under a Full configuration mode, trigger mechanism IEs Trigger-UP-1, Trigger-Down-1 and Trigger-Down-2 are defined. The Trigger-UP-1 IE indicates the WTRU 101 is to move to the next upper level DRX state (i.e., a longer DRX cycle). The Trigger-Down-1 IE is a trigger mechanism for the WTRU 101 to move the next lower level DRX state (i.e., a shorter DRX cycle). For the Trigger-Down-2 IE, the WTRU 101 receives a trigger mechanism to move to the shortest DRX cycle, Level-1. For each of these trigger IEs, a choice IE for Triggering Mechanism includes either a timer or a measurement event, as summarized in Table 5. If a timer trigger mechanism is applied, a timer value IE, Implicit-DRX-triggering-timer, may be included. For a measurement event trigger, an Implicit DRX triggering event IE may be included, based on traffic volume and/or inter-frequency, intra-frequency, inter-RAT, intra-RAT measurement events, and an IE for threshold value to be used for the measurement event may also be included.
Additional IEs provided to the WTRU 101 for defining the DRX cycle may include DRX Cycle length, the active period length, the active period position and the active period start subframe. For the DRX cycle length IE, the parameter indicates the DRX cycle length for LTE active mode in units of system frames and indicating if this DRX parameter is different than the LTE idle mode parameter. The active period length IE indicates the active duty cycle length in sub-frames for LTE active mode, and whether the parameter is different than the LTE idle mode parameter. The active period position IE indicates whether the active duty period is at the beginning or at the end of the DRX cycle whether the parameter is different than the LTE idle mode parameter. If the active period does not start at a frame boundary, then the active period start sub-frame IE provides the sub-frame number at which the active period starts.
In another embodiment, parameters for cell selection and reselection are defined and transmitted in a SIB 3, for example, or one of the other SIBs defined in the 3GPP specifications. Tables 6 and 7 show a summary of an example configuration of IEs containing cell selection and reselection parameters.
As seen in Table 6, for a choice IE for barring representation, either an IE “Access restriction parameter list” IE or an “Access restriction parameter for all” IE is selected. If the “Access restriction parameter list” IE is applied, then multiple IEs are available for specifying access restriction parameters for WTRUs assigned to a respective public land mobile network (PLMN), which is identified in an IE “multiplePLMNs” in the IE “Multiple PLMN List” in the master information block (MIB). When the “Alternative access restriction parameters for all” IE is chosen, then a set of common access restriction parameters is indicated to the WTRU 101, which is applied to all PLMNs in the IE “multiple PLMNs”. As there is one PS domain, the parameters for the CS domain are not specified.
As shown in Table 7, the WTRU 101 may receive an IE for Cell selection and reselection quality measure based on RSRP and/or RSRQ, an IE for radio access technology (RAT) of the candidate cell for selection, and a Treslection IE that indicates the reselection time parameter. With respect to the Qhyst IE, the WTRU 101 may receive the following scaling factors: an IE that indicates a Speed dependent scaling factor, an Inter-frequency Speed dependent scaling factor, and an Inter RAT Speed dependent scaling factor. A Neighbor cell blacklist IE may be received by the WTRU 101 to indicate a list of neighbor cells forbidden by the network for reselection.
Before the WTRU 101 makes received signal measurements for cell selection/reselection, the WTRU 101 may receive and process an UTRAN_min IE or GERAN_Min which indicate the minimum signal power for a UTRAN or GERAN cell, respectively. The IEs Qoffset1 and Qoffset2 may be received by the WTRU 101 to indicate biasing cell measurements
In another embodiment, system level information for a PHY random access channel (PRACH) is defined by parameters in IEs and included into an SIB 5, or another 3GPP specified SIB, to be received and processed by the WTRU 101. Tables 8-10 show a summary of example configurations of such IEs and related information.
As shown in Table 8, a PRACH system information IE may be included with multiple instances from 1 to maxPRACH. A PRACH-info IE for RACH comprises several IEs that are summarized in Table 9. A RACH non-dedicated signature IE indicates dedicated and non-dedicated signatures allocated to the WTRU 101, and comprises several IEs that are summarized in Table 10. A RACH Response Window IE informs the WTRU 101 as to a number of sub-frames over which multiple RACH responses sent to the WTRU 101 are to be received. A PHY downlink control channel (PDCCH) information IE, “PDCCH-Info”, provides PDCCH parameters for the PRCAH to the WTRU 101, comprising IEs summarized in Table 12. A routing area-radio network temporary identification (RA-RNTI) List IE, comprising IEs summarized in Table 11, provides RNTI information to the WTRU 101 for the routing area
As shown in Table 9, WTRU 101 receives PRACH information parameters for frequency division duplex (FDD) and time division duplex (TDD) operation. For FDD, the WTRU 101 may receive a PRACH frequency position IE indicating an integer value within a range starting from the lowest frequency edge of the carrier bandwidth. Alternatively, the integer value may range between negative and positive values centered in the middle of the carrier frequency. Additional parameters received by the WTRU 101 include a PRACH burst type IE (e.g., normal, extended or repeated burst type) and a Channel Coding parameter IE for identifying the turbo code in use. For TDD, the WTRU 101 may receive a PRACH Frame structure type IE and a PRACH Burst Type IE to indicate, for example, a normal or extended burst type.
As shown in Table 10, the WTRU 101 may receive a set of RACH parameters defined according to a group G1 for dedicated RACH signatures, a group G2 for consecutive or bit-mapped non-dedicated RACH signatures, or a group G3 for small message consecutive or bit-mapped non-dedicated RACH signatures. Each RACH channel typically has 64 random access signatures of cyclical Z-C codes whose generation/derivation is specified in 3GPP Standards. For system information, the signatures can be identified by their indexes (0 . . . 63).
When a random access signature group whose signatures are all consecutive in terms of the signature index, it can be defined by [start-index-a, range]. The WTRU 101 then knows and selects the signatures within the defined group since they are consecutive. For example, WTRU 101 receives the Available Dedicated Signatures G1 IE, the Number of Signatures IE with a value 8, and a Begin Signature Index IE with value 8, then WTRU 101 can derive that its RACH signature group is [8-15].
But if the random access signatures in a group is not consecutive, then the above described signature index mapping IE is replaced by the alternative bit-mapped signature index, shown in Table 10 as the Signature Map IE. For the bit-mapped signature mapping, the WTRU 101 receives a bit string which indicates a set of available signatures in the random access signature group according to a predefined signature map. The Signature map IE use a bitmap with 64 bits, or with a first start-index-a, and a subsequent bitmap in a range.
Other than the SIBs mentioned above, the LTE network could also transmit a SIB 16 message which could carry some configuration parameters that the WTRU 101 could read and use when entering the LTE system during a handover from another RAT (3GPP or non-3GPP) to LTE. Alternatively, the LTE system could transmit a SIB 16 message or some other analogous dedicated RRC message which would carry parameters applicable for the non 3GPP RAT during a handover from LTE to other RAT (3GPP or non-3GPP). Such a message could have been possibly conveyed to the LTE system just before the handover procedure. This SIB 16 could contain a combination of parameters like some of the DRX parameters mentioned, some RACH and reselection parameters and any other physical layer parameters which might give the WTRU 101 some knowledge of the system.
Although features and elements are described above in particular combinations, each feature or element can be used alone without the other features and elements or in various combinations with or without other features and elements. The methods or flow charts provided herein may be implemented in a computer program, software, or firmware incorporated 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) or Ultra Wide Band (UWB) module.
This application is a continuation of U.S. patent application Ser. No. 14/918,960, filed on Oct. 21, 2015, which is a continuation U.S. patent application Ser. No. 12/185,546 filed on Aug. 4, 2008, which issued as U.S. Pat. No. 9,173,167 on Oct. 27, 2015, which claims the benefit of U.S. provisional application No. 60/953,816, filed on Aug. 3, 2007, the entire contents of all of which being incorporated by reference as if fully set forth herein, for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
6205333 | Abe | Mar 2001 | B1 |
6621803 | Halton et al. | Sep 2003 | B2 |
6697346 | Halton et al. | Feb 2004 | B1 |
7187934 | Turina et al. | Mar 2007 | B2 |
7197323 | Terry | Mar 2007 | B2 |
8315214 | Womack et al. | Nov 2012 | B2 |
8451741 | Enstrom et al. | May 2013 | B2 |
8559342 | Kim et al. | Oct 2013 | B2 |
20020041578 | Kim et al. | Apr 2002 | A1 |
20030095528 | Halton et al. | May 2003 | A1 |
20040116126 | Cave | Jun 2004 | A1 |
20040198221 | Bin | Oct 2004 | A1 |
20040224684 | Dorsey et al. | Nov 2004 | A1 |
20040224689 | Raghuram et al. | Nov 2004 | A1 |
20050032542 | Wilborn et al. | Feb 2005 | A1 |
20050271025 | Guethaus | Dec 2005 | A1 |
20060146858 | Kim | Jul 2006 | A1 |
20070004445 | Dorsey et al. | Jan 2007 | A1 |
20070178875 | Rao et al. | Aug 2007 | A1 |
20070291729 | Dalsgaard et al. | Dec 2007 | A1 |
20080101268 | Sammour et al. | May 2008 | A1 |
20080181127 | Terry et al. | Jul 2008 | A1 |
20080227453 | Somasundaram et al. | Sep 2008 | A1 |
20080253323 | Fischer | Oct 2008 | A1 |
20090042576 | Mukherjee et al. | Feb 2009 | A1 |
20090088160 | Pani et al. | Apr 2009 | A1 |
20090207802 | Lee | Aug 2009 | A1 |
20100330998 | Park et al. | Dec 2010 | A1 |
Number | Date | Country |
---|---|---|
1499144 | Jan 2005 | EP |
1509056 | Feb 2005 | EP |
1739990 | Jan 2007 | EP |
11-220433 | Aug 1999 | JP |
2002-539730 | Nov 2002 | JP |
2003-153325 | May 2003 | JP |
2005-260906 | Sep 2005 | JP |
2006-121172 | May 2006 | JP |
2008-523711 | Jul 2008 | JP |
M240063 | Aug 2004 | TW |
2006-35411 | Oct 2006 | TW |
2007-18230 | May 2007 | TW |
2007-23809 | Jun 2007 | TW |
I302806 | Nov 2008 | TW |
I324003 | Apr 2010 | TW |
WO 2000056095 | Sep 2000 | WO |
WO 2006065198 | Jun 2006 | WO |
WO 2006118426 | Nov 2006 | WO |
WO 2006104335 | Jul 2007 | WO |
WO 2007111480 | Oct 2007 | WO |
Entry |
---|
3rd Generation Partnership Project (3GPP), R2-063120, “DRX Operations for Connected Mode UEs in LTE”, Samsung, 3GPP TSG-RAN2 Meeting #56, Riga, Latvia, Nov. 6-10, 2006, 3 pages. |
3rd Generation Partnership Project (3GPP), R2-071261, “Explicit DRX Control”, Research in Motion Limited, 3GPP TSG RAN WG2 Meeting #57bis, Mar. 26-30, 2007, pp. 1-2. |
3rd Generation Partnership Project (3GPP), R2-071285, “DRX Parameters in LTE”, Nokia, 3GPP TSG-RAN WG2, Meeting #57bis, St. Julian's, Malta, Mar. 26-30, 2007, 7 pages. |
3rd Generation Partnership Project (3GPP), R2-071783, “DRX Handling Issues in LTE”, Panasonic, 3GPP TSG RAN WG2 #58, Kobe, Japan, May 7-11, 2007, 4 pages. |
3rd Generation Partnership Project (3GPP), R2-072409, “Stage 3 Topics of Random Access Procedure”, Nokia, Nokia Siemens Networks, 3GPP TSG-RAN WG2, Meeting# 58 bis, Orlando, U.S.A, Jun. 25-29, 2007, 4 pages. |
3rd Generation Partnership Project (3GPP), R2-072620, “RLC Status Report Trigger”, LG Electronics Inc., 3GPP TSG-RAN WG2 #58bis, Jun. 25-29, 2007, pp. 1-3. |
3rd Generation Partnership Project (3GPP), R2-072742, “Multiple RA Response”, Mobile Competence Centre, 650, Route Des Lucioles, F06921, Sophia-Antipolis Cedex, France, vol. RAN WG2 #58 bis, Jun. 25-29, 2007, pp. 1-2. |
3rd Generation Partnership Project (3GPP), TS 23.122 V3.1.1, “Technical Specification Group Core Network, NAS Functions Related to Mobile Station (MS) in Idle Mode”, Feb. 2000, pp. 1-31. |
3rd Generation Partnership Project (3GPP), TS 25.304 V3.14.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 1999)”, Mar. 2004, pp. 1-41. |
3rd Generation Partnership Project (3GPP), TS 25.304 V4.8.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 4)”, Mar. 2004, pp. 1-41. |
3rd Generation Partnership Project (3GPP), TS 25.304 V5.9.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 5)”, Sep. 2005, pp. 1-44. |
3rd Generation Partnership Project (3GPP), TS 25.304 V6.10.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 6)”, Mar. 2008, pp. 1-38. |
3rd Generation Partnership Project (3GPP), TS 25.304 V6.9.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 6)”, Mar. 2006, pp. 1-38. |
3rd Generation Partnership Project (3GPP), TS 25.304 V7.1.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reslection in Connected Mode (Release 7)”, Dec. 2006, pp. 1-38. |
3rd Generation Partnership Project (3GPP), TS 25.304 V7.2.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 7)”, Jun. 2007, pp. 1-41. |
3rd Generation Partnership Project (3GPP), TS 25.304 V7.6.0, “Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 7)”, May 2008, pp. 1-41. |
3rd Generation Partnership Project (3GPP), TS 25.304 V8.2.0, “ Technical Specification Group Radio Access Network, User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (Release 8)”, May 2008, pp. 1-41. |
3rd Generation Partnership Project (3GPP), TS 25.331 V3.21.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 1999)”, Dec. 2004, pp. 1-879. |
3rd Generation Partnership Project (3GPP), TS 25.331 V4.17.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 4)”, Mar. 2005, pp. 1-953. |
3rd Generation Partnership Project (3GPP), TS 25.331 V4.19.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 4)”, May 2008, pp. 1-953. |
3rd Generation Partnership Project (3GPP), TS 25.331 V5.19.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 5)”, Dec. 2006, pp. 1-1045. |
3rd Generation Partnership Project (3GPP), TS 25.331 V5.22.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 5)”, May 2008, pp. 1-1045. |
3rd Generation Partnership Project (3GPP), TS 25.331 V6.14.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 6)”, Jun. 2007, pp. 1-1247. |
3rd Generation Partnership Project (3GPP), TS 25.331 V6.18.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 6)”, May 2008, pp. 1-1252. |
3rd Generation Partnership Project (3GPP), TS 25.331 V7.5.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 7)”, Jun. 2007, pp. 1-1429. |
3rd Generation Partnership Project (3GPP), TS 25.331 V7.9.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 7)”, May 2008, pp. 1-1475. |
3rd Generation Partnership Project (3GPP), TS 25.331 V8.3.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 8)”, May 2008, pp. 1-1494. |
3rd Generation Partnership Project (3GPP), TS 36.213 V1.2.0, “Technical Specification Group Radio Access Network, Technical Specification Group Radio Access Network, Physical Layer Procedures (Release 8)”, May 2007, pp. 1-10. |
3rd Generation Partnership Project (3GPP), TS 36.213 V8.3.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Layer Procedures (Release 8)”, May 2008, pp. 1-45. |
3rd Generation Partnership Project (3GPP), TS 36.300 V8.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 8)”, Jun. 2007, pp. 1-106. |
3rd Generation Partnership Project (3GPP), TS 36.304 V8.2.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), User Equipment (UE) Procedures in Idle Mode (Release 8)”, May 2008, pp. 1-27. |
3rd Generation Partnership Project (3GPP), TS 36.331 V8.2.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RCC), Protocol Specification (Release 8)”, May 2008, pp. 1-151. |
European Telecommunications Standard Institute (ETSI), TS 136 300 V8.1.0, “Universal Mobile Telecommunications System (UMTS), Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN), Overall Description, Stage 2 (3GPP TS 36.300 version 8.1.0 Release 8)”, Jun. 2007, pp. 1-108. |
European Telecommunications Standards Institute (ETSI), TS 125 304 V6.9.0, “Universal Mobile Telecommunications System (UMTS), User Equipment (UE) Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (3GPP TS 25.304 version 6.9.0 Release 6)”, Mar. 2006, pp. 1-40. |
European Telecommunications Standards Institute (ETSI), TS 125 331 V7.5.0, “Universal Mobile Telecommunications Systems (UMTS), Radio Resource Control (RRC), Protocol Specification (3GPP TS 25.331 version 7.5.0 Release 7)”, Jun. 2007, pp. 1-1431. |
Khan, “Impact of DRX on VoIP Performance and Battery Life in LTE”, Blekinge Institute of Technology, Sweden School of Engineering and University of Kalmar, Sweden Department of Technology, Chapter 4, Nov. 2008, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20170055295 A1 | Feb 2017 | US |
Number | Date | Country | |
---|---|---|---|
60953816 | Aug 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14918960 | Oct 2015 | US |
Child | 15346294 | US | |
Parent | 12185546 | Aug 2008 | US |
Child | 14918960 | US |