TREA

Method and apparatus for accessing a random access channel by selectively using dedicated or contention-based preambles

Follow

Information

  • Patent Grant
  • 11751104
  • Patent Number
    11,751,104
  • Date Filed
    Friday, September 17, 2021
    3 years ago
  • Date Issued
    Tuesday, September 5, 2023
    a year ago
  • Inventors
  • Original Assignees
    • InterDigital Patent Holdngs, Inc. (Wilmington, DE, US)
  • Examiners
    • Wong; Warner
    Agents
    • CONDO ROCCIA KOPTIW LLP
Information
Abstract
A method and apparatus for accessing a random access channel (RACH) during handover are disclosed. A handover procedure is initiated and a maximum handover interruption timer is activated. A dedicated preamble is transmitted in an attempt to access the RACH on a condition that the dedicated preamble is reserved in a current random access opportunity and the maximum handover interruption timer has not expired. A contention-based preamble is transmitted in an attempt to access the RACH on a condition that a dedicated preamble is not reserved in a current random access opportunity. If the maximum handover interruption timer has expired, a contention-based preamble is transmitted in an attempt to access the RACH.
Description
FIELD OF INVENTION

This application is related to wireless communications.


BACKGROUND

In a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) wireless communication system, when a wireless transmit/receive unit (WTRU) performs handover to a target cell, the WTRU uses a dedicated preamble to access a network. A preamble is a signal sent from the WTRU to an evolved Node-B (eNB) to detect timing misalignment in the uplink (UL) during a handover procedure. Accordingly, the target cell needs to reserve a dedicated preamble for the WTRU. However, a non-contention based random access channel (RACH), used by the eNB to provide configuration information of the dedicated preamble, will become overloaded when a large number of WTRUs handover to the same target cell in a short amount of time. Because of this overloading of the RACH, there is a need for a more efficient mechanism by which the dedicated preamble is used during handover.


SUMMARY

The method and apparatus disclosed herein allows for an efficient usage of a dedicated preamble to access a RACH in evolved universal terrestrial radio access (E-UTRA) during handover. The WTRU may use a dedicated preamble in pre-reserved (or preconfigured) frames, but not in every frame. Alternatively, the WTRU may use contention-based preambles in other random access opportunities when a dedicated preamble is not reserved, or a RACH access attempt does not succeed using the dedicated preamble.





BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:



FIG. 1 shows an example of a plurality of WTRUs sharing one dedicated preamble during different reserved dedicated preamble periods;



FIG. 2 is a block diagram of a wireless communication system including a WTRU and an eNB; and



FIG. 3 is a flowchart of a procedure for using a dedicated or contention-based preamble during handover using the system of FIG. 2.





DETAILED DESCRIPTION

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 an evolved Node-B (eNB), a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.


The method and apparatus disclosed herein allows for an efficient usage of a dedicated preamble for handover performed by WTRUs in E-UTRA. The WTRU may use a dedicated preamble in pre-reserved (or preconfigured) frames, but not in every frame. Alternatively, the WTRU may use contention-based preambles in other random access opportunities when a dedicated preamble is not reserved.


Rather than reserving a dedicated preamble for a handover WTRU in every random access opportunity, (e.g., every 10 ms), the eNB will reserve a dedicated preamble N out of M random access opportunities, where the parameter M is defined as the period of a reserved dedicated preamble. A random access opportunity is a time period when a RACH may be accessed. In such an instance, the preferred value of N is one.


As is shown in FIG. 1, such a value facilitates the eNB to interleave several WTRUs sharing one dedicated preamble over the time domain. WTRU 1 only uses the dedicated preamble in a first random access opportunity out of every 4 random access opportunities. WTRU 2 only uses the dedicated preamble in a second random access opportunity out of every 4 random access opportunities. WTRU 3 only uses the dedicated preamble in a third random access opportunity out of every 8 random access opportunities. Thus, a dedicated preamble is efficiently shared by 3 WTRUs in the time domain.


The network will monitor and decide the value of parameters N and M based on the load on a non-contention RACH. Although different M values may be configured, a larger period must be an integer multiple of a smaller preamble period. In this way, WTRUs with different dedicated preamble configurations may share the same preamble without collision in the time domain. An example of a preferred set of a different reserved dedicated preamble periods is M=1, 2, 4 and 8.



FIG. 2 shows a wireless communication system 200 including a WTRU 205 and an eNB 210. The eNB 210 reserves a dedicated preamble for a WTRU N out of M random access opportunities for a duration up to a maximum allowed handover interruption time. The eNB 210 may transmit reserved dedicated preamble configuration information 215 to the WTRU 205 via a handover command, when a handover decision is made, or via a special medium access control (MAC) protocol data unit (PDU). The WTRU 205 includes a transmitter 225, a receiver 230 which receives preambles from the WTRU 205, a processor 235 and a maximum handover interruption timer 240. The eNB 110 includes a transmitter 245, which is configured to transmit the reserved dedicated preamble configuration information 215, a receiver 250 which receives the preambles from the WTRU 205 and a processor 255. The processor 255 includes a preamble resource manager 260, which is used to allocate preambles to the WTRU 205.


The WTRU 205 transmits either a dedicated or contention-based preamble 220 to the eNB 210 such that the WTRU 205 can access a RACH to complete a handover procedure. If a RACH access attempt implemented by the WTRU 205 fails when using a dedicated preamble, the WTRU 205 will then use a contention-based preamble in subsequent random access opportunities until either its RACH access attempt succeeds or a random access opportunity occurs in which there is a reserved dedicated preamble.


Still referring to FIG. 2, the WTRU 200 is configured to access a RACH during handover. The processor 235 is configured to initiate handover and activate the maximum handover interruption timer 240. The transmitter is configured to transmit a dedicated preamble in an attempt to access the RACH on a condition that the dedicated preamble is reserved in a current random access opportunity and the maximum handover interruption timer has not expired, and transmit a contention-based preamble in an attempt to access the RACH on a condition that a dedicated preamble is not reserved in a current random access opportunity.


The transmitter 225 in the WTRU 200 is also configured to transmit a contention-based preamble in an attempt to access the RACH on a condition that the maximum handover interruption timer has expired. The transmitter 225 is also configured to transmit, on a condition that a failure to access a RACH has failed, a contention-based preamble in subsequent random access opportunities until a successful RACH access attempt occurs, or a random access opportunity occurs in which there is a reserved dedicated preamble.


A non-contention based procedure is used on a condition that the dedicated preamble is reserved in a current random access opportunity and the maximum handover interruption timer has not expired.


A contention-based random access procedure is used on a condition that the dedicated preamble is not reserved in a current random access opportunity and the maximum handover interruption timer has expired.



FIG. 3 is a flow diagram of a procedure 300 that uses a reserved dedicated preamble or a contention-based random access preamble during handover. Referring to FIGS. 2 and 3, the processor 235 in the WTRU 205 initiates a handover to a target cell and activates the maximum handover interruption timer 240 in the WTRU 205 (305). When a random access opportunity occurs (310), a determination is made by the processor 235 as to whether the maximum handover interruption timer 240 has expired (315). If the maximum handover interruption timer 240 has not yet expired before a random access opportunity occurs, the processor 235 determines whether there is a dedicated preamble reserved in the current random access opportunity (step 320).


If there is a reserved dedicated preamble in the current random access opportunity, the WTRU uses a dedicated preamble in random access, and a non-contention based random access procedure is used between the WTRU 205 and the eNB 210 to make a RACH access attempt (step 325). A non-contention based random access procedure is two-step random access procedure that does not involve transmission of RACH message 3 in the uplink and contention resolution in the downlink, (as compared to a contention-based one).


If a reserved dedicated preamble does not exist in the current random access opportunity, the WTRU uses a contention-based preamble in random access, and a contention based random access procedure is used between the WTRU 205 and the eNB 210 to make a RACH access attempt (step 330). A contention based random access procedure is a four-step random access procedure that involves transmission of RACH message 3 in the uplink and contention resolution in the downlink. The contention-based preamble may be randomly selected from a set of contention-based preambles.


In step 335, a determination is made as to whether the RACH access attempt succeeded. If a WTRU fails its RACH access attempt using a reserved dedicated preamble, it will use a contention-based preamble in subsequent random access opportunities until either its RACH access attempt succeeds, or a random access opportunity occurs in which there is a reserved dedicated preamble.


Due to the high success probability of RACH access using a dedicated preamble, the approach to try a RACH access attempt with alternating non-contention based and contention based RACH access attempts is preamble resource efficient.


Although the features and elements of the present method and apparatus are described in particular combinations, each feature or element may be used alone, without other features and elements of the preferred embodiments, or in various combinations with or without other features and elements of the present method and apparatus.


While the present method and apparatus has been described in terms of the preferred embodiment, other variations which are within the scope of the invention will be apparent to those skilled in the art.


Although features and elements are described above in particular combinations, each feature or element may 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 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.

Claims
  • 1. A wireless transmit/receive unit (WTRU) comprising:
  • 2. The WTRU of claim 1, wherein the processor is configured to transmit one or more dedicated non-contention-based RACH preambles in accordance with the received configuration information.
  • 3. The WTRU of claim 2, wherein the processor is configured to transmit the one or more dedicated non-contention-based RACH preambles in a subset of available RACH opportunities.
  • 4. The WTRU of claim 2, wherein the configuration information comprises an indication of the one or more dedicated non-contention-based RACH preambles, andwherein the indication of the non-contention-based RACH resource comprises an indication of one of the one or more dedicated non-contention-based RACH preambles.
  • 5. The WTRU of claim 4, wherein the configuration information comprises an indication of a subset of available RACH opportunities for attempting RACH access using the one or more dedicated non-contention-based RACH preambles.
  • 6. The WTRU of claim 1, wherein the processor is configured to transmit a contention-based RACH preamble.
  • 7. The WTRU of claim 1, wherein the processor is configured to receive the configuration information from a base station.
  • 8. The WTRU of claim 1, wherein the processor is configured to transmit a dedicated non-contention-based RACH preamble in a subset N out of M available random access opportunities, wherein N and M are integers and N is not equal to M.
  • 9. The WTRU of claim 1, wherein the processor is configured to attempt the first RACH access and the second RACH access during a handover procedure for handover to a target cell.
  • 10. The WTRU of claim 1, wherein the non-contention-based RACH resource comprises a first RACH preamble; andwherein the contention-based RACH resource comprises a second RACH preamble.
  • 11. A method comprising: receiving configuration information comprising an indication of a non-contention-based random access channel (RACH) resource;attempting a first RACH access using the non-contention-based RACH resource during a time period associated with the non-contention-based RACH resource indicated in the configuration information;determining that the time period has ended; andattempting a second RACH access using a contention-based RACH resource after the time period has ended.
  • 12. The method of claim 11, wherein attempting the first RACH access comprises: transmitting one or more dedicated non-contention-based RACH preambles in accordance with the received configuration information.
  • 13. The method of claim 12, wherein transmitting one or more dedicated non-contention-based RACH preambles in accordance with the received configuration information further comprises: transmitting the one or more dedicated non-contention-based RACH preambles in a subset of available RACH opportunities.
  • 14. The method of claim 12, wherein the configuration information comprises an indication of the one or more dedicated non-contention-based RACH preambles, andwherein the indication of the non-contention-based RACH resource comprises an indication of one of the one or more dedicated non-contention-based RACH preambles.
  • 15. The method of claim 14, wherein the configuration information comprises an indication of a subset of available RACH opportunities for attempting RACH access using the one or more dedicated non-contention-based RACH preambles.
  • 16. The method of claim 11, wherein attempting the second RACH access comprises:
  • 17. The method of claim 11, wherein the configuration information is received from a base station.
  • 18. The method of claim 11, wherein attempting the first RACH access comprises: transmitting a dedicated non-contention-based RACH preamble in a subset N out of M available random access opportunities, wherein N and M are integers and N is not equal to M.
  • 19. The method of claim 11, wherein the first RACH access and the second RACH access are attempted during a handover procedure for handover to a target cell.
  • 20. The method of claim 11, wherein the non-contention-based RACH resource comprises a first RACH preamble; andwherein the contention-based RACH resource comprises a second RACH preamble.
  • 21. The WTRU of claim 1, further comprising: a receiver;wherein the processor configured to receive the configuration information is configured to receive the configuration information via the receiver; andwherein the processor is further configured to determine the time period, wherein the WTRU is allowed to attempt RACH access using the non-contention-based RACH resource indicated in the configuration information during the time period.
  • 22. The method of claim 11, further comprising: determining the time period, wherein a wireless transmit/receive unit (WTRU) is allowed to attempt RACH access using the non-contention-based RACH resource indicated in the configuration information during the time period.
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/444,736, filed Jun. 18, 2019, which is a continuation of U.S. patent application Ser. No. 15/977,706, filed May 11, 2018, which issued as U.S. Pat. No. 10,368,270 on Jul. 30, 2019, which is a continuation of U.S. patent application Ser. No. 15/067,607, filed Mar. 11, 2016, which issued as U.S. Pat. No. 10,021,601 on Jul. 10, 2018, which is a continuation of U.S. patent application Ser. No. 14/169,951, filed Jan. 31, 2014, which issued as U.S. Pat. No. 9,344,919 on May 17, 2016, which is a continuation of U.S. patent application Ser. No. 12/392,235, filed Feb. 25, 2009, which issued as U.S. Pat. No. 8,649,353 on Feb. 11, 2014, which claims the benefit of U.S. Provisional Application No. 61/033,676, filed Mar. 4, 2008, the contents of all of which are hereby incorporated by reference as if fully set forth herein.

US Referenced Citations (120)
Number Name Date Kind
5692184 Ardoin et al. Nov 1997 A
5872774 Wheatley, III et al. Feb 1999 A
6330459 Crichton et al. Dec 2001 B1
6594240 Chuah et al. Jul 2003 B1
7003303 Khawand et al. Feb 2006 B2
7167709 Schwarz et al. Jan 2007 B2
7525941 Islam et al. Apr 2009 B2
7778151 Bertrand et al. Aug 2010 B2
7804799 Venkatachalam et al. Sep 2010 B2
7852805 Kahtava et al. Dec 2010 B2
7903818 Park et al. Mar 2011 B2
7979769 Chun et al. Jul 2011 B2
8000305 Tan et al. Aug 2011 B2
8102804 Noh et al. Jan 2012 B2
8107950 Amirijoo et al. Jan 2012 B2
8111763 Ma et al. Feb 2012 B2
8131295 Wang et al. Mar 2012 B2
8169986 Jeong et al. May 2012 B2
8331326 Wang et al. Dec 2012 B2
8345654 Parkvall et al. Jan 2013 B2
8369854 Peisa et al. Feb 2013 B2
8712415 Zhang et al. Apr 2014 B2
8797989 Lee Aug 2014 B2
8837435 Singh et al. Sep 2014 B2
8971349 Park et al. Mar 2015 B2
9807688 Yi et al. Oct 2017 B2
20020089734 Meehan et al. Jul 2002 A1
20030016698 Chang et al. Jan 2003 A1
20030153275 Oh et al. Aug 2003 A1
20030156553 Benveniste Aug 2003 A1
20030223452 Toskala et al. Dec 2003 A1
20040052229 Terry et al. Mar 2004 A1
20040082356 Walton et al. Apr 2004 A1
20040095911 Benveniste et al. May 2004 A1
20040170179 Johansson et al. Sep 2004 A1
20040174845 Koo et al. Sep 2004 A1
20040185853 Kim et al. Sep 2004 A1
20040192320 Khawand et al. Sep 2004 A1
20040208160 Petrovic et al. Oct 2004 A1
20050047366 Ghosh et al. Mar 2005 A1
20050053029 Lee et al. Mar 2005 A1
20050094600 Zhang et al. May 2005 A1
20050096050 Hidaka May 2005 A1
20050101299 Farnsworth May 2005 A1
20050282549 Kim et al. Dec 2005 A1
20060045139 Black et al. Mar 2006 A1
20060126570 Kim et al. Jun 2006 A1
20060183429 Anderson Aug 2006 A1
20060209798 Oikarinen et al. Sep 2006 A1
20060223532 Liu et al. Oct 2006 A1
20070047493 Park et al. Mar 2007 A1
20070165567 Tan et al. Jul 2007 A1
20070206531 Pajukoski et al. Sep 2007 A1
20070213059 Shaheen Sep 2007 A1
20080026759 Sawamoto Jan 2008 A1
20080043771 Cho et al. Feb 2008 A1
20080072269 Malladi et al. Mar 2008 A1
20080076405 Jen Mar 2008 A1
20080102896 Wang et al. May 2008 A1
20080159334 Venkatachalam et al. Jul 2008 A1
20080161000 Li et al. Jul 2008 A1
20080187027 Malladi Aug 2008 A1
20080227453 Somasundaram et al. Sep 2008 A1
20080232304 Mooney et al. Sep 2008 A1
20080232317 Jen Sep 2008 A1
20080233941 Jen Sep 2008 A1
20080242292 Koskela et al. Oct 2008 A1
20080254800 Chun et al. Oct 2008 A1
20080261600 Somasundaram et al. Oct 2008 A1
20080267127 Narasimha et al. Oct 2008 A1
20080267131 Kangude et al. Oct 2008 A1
20080280594 Voyer et al. Nov 2008 A1
20080285539 Tiedemann, Jr. et al. Nov 2008 A1
20080310395 Kashima Dec 2008 A1
20080310396 Park Dec 2008 A1
20090016301 Sammour et al. Jan 2009 A1
20090086676 Meylan et al. Apr 2009 A1
20090101299 Wanke et al. Apr 2009 A1
20090103501 Farrag et al. Apr 2009 A1
20090104909 Vesely et al. Apr 2009 A1
20090109838 Kuo Apr 2009 A1
20090109926 Meylan Apr 2009 A1
20090116399 Ho et al. May 2009 A1
20090129335 Lee et al. May 2009 A1
20090147768 Ji et al. Jun 2009 A1
20090168728 Pani et al. Jul 2009 A1
20090213771 Celentano et al. Aug 2009 A1
20090213818 Park et al. Aug 2009 A1
20090215459 Kuo Aug 2009 A1
20090225739 Yeo et al. Sep 2009 A1
20090238141 Damnjanovic et al. Sep 2009 A1
20090239539 Zhang et al. Sep 2009 A1
20090247161 Pani et al. Oct 2009 A1
20090274086 Petrovic et al. Nov 2009 A1
20090309921 Ohyama et al. Dec 2009 A1
20090316678 Yamada Dec 2009 A1
20100027466 Mustapha Feb 2010 A1
20100074218 Cai et al. Mar 2010 A1
20100103889 Kim et al. Apr 2010 A1
20100113033 Qiu et al. May 2010 A1
20100118788 Ohta et al. May 2010 A1
20100182974 Barraclough et al. Jul 2010 A1
20100197308 Racz et al. Aug 2010 A1
20100202402 Dalsgaard et al. Aug 2010 A1
20100210255 Amirijoo et al. Aug 2010 A1
20100216483 Tynderfeldt et al. Aug 2010 A1
20100220713 Tynderfeldt et al. Sep 2010 A1
20100238799 Sebire Sep 2010 A1
20100260140 Zhu Oct 2010 A1
20100265854 Baldemair et al. Oct 2010 A1
20100279695 Amirijoo et al. Nov 2010 A1
20100284376 Park et al. Nov 2010 A1
20110081912 Fischer et al. Apr 2011 A1
20110096748 Meyer et al. Apr 2011 A1
20110134862 Huang et al. Jun 2011 A1
20110149942 Ko et al. Jun 2011 A1
20110292816 Lee et al. Dec 2011 A1
20120064897 Amirijoo et al. Mar 2012 A1
20120213157 Jeong et al. Aug 2012 A1
20130064224 Wang et al. Mar 2013 A1
Foreign Referenced Citations (66)
Number Date Country
2010200888 Mar 2014 AU
1612635 May 2005 CN
1984452 Jun 2007 CN
101069448 Nov 2007 CN
0568212 Sep 1997 EP
1058417 Dec 2000 EP
1058471 Dec 2000 EP
1117269 Jul 2001 EP
1199904 Apr 2002 EP
1408658 Apr 2004 EP
1511246 Mar 2005 EP
1799003 Jun 2007 EP
1909520 Apr 2008 EP
1909523 Apr 2008 EP
2353671 Feb 2001 GB
194081 Jun 2009 IL
10-23501 Jan 1998 JP
10-247806 Sep 1998 JP
2003-069469 Mar 2003 JP
2003-523138 Jul 2003 JP
2003-532138 Oct 2003 JP
2005-539468 Dec 2005 JP
2006-504335 Feb 2006 JP
2006-515484 May 2006 JP
2007-503740 Feb 2007 JP
2009-500894 Jan 2009 JP
2009-509431 Mar 2009 JP
2009-519636 May 2009 JP
2010-023501 Feb 2010 JP
2010-506445 Feb 2010 JP
5023150 Sep 2012 JP
10-2005-0116497 Dec 2005 KR
2003122285 Feb 2005 RU
2292669 Jan 2007 RU
2305900 Sep 2007 RU
2007-38026 Oct 2007 TW
M340666 Sep 2008 TW
WO 2001060017 Aug 2001 WO
WO 2001072081 Sep 2001 WO
WO 2001076304 Oct 2001 WO
WO 2003043237 May 2003 WO
WO 2004025778 Mar 2004 WO
WO 2004079948 Sep 2004 WO
WO 2004080102 Sep 2004 WO
WO 2005006596 Jan 2005 WO
WO 2005020617 Mar 2005 WO
WO 2005022814 Mar 2005 WO
WO 2005029642 Mar 2005 WO
WO 2005032199 Apr 2005 WO
WO 2005120183 Dec 2005 WO
WO 2005122704 Dec 2005 WO
WO 2006061671 Jun 2006 WO
WO 2006073225 Jul 2006 WO
WO 2007000722 Jan 2007 WO
WO 2007038994 Apr 2007 WO
WO 2007066882 Jun 2007 WO
WO 2007068304 Jun 2007 WO
WO 2007108959 Sep 2007 WO
WO 2007144760 Dec 2007 WO
WO 2007149509 Dec 2007 WO
WO 2008023927 Feb 2008 WO
WO 2008040447 Apr 2008 WO
WO 2008087524 Jul 2008 WO
WO 2008131401 Oct 2008 WO
WO 2009117575 Sep 2009 WO
WO 2010002692 Jan 2010 WO
Non-Patent Literature Citations (57)
Entry
3rd Generation Partnership Project (3GPP), R2-082903, “Miscellaneous Clarifications/Corrections”, Rapporteur (Samsung), 3GPP TSG-RAN2#62 Meeting, Kansas City, U.S.A, May 5-9, 2008, 177 pages.
3rd Generation Partnership Project (3GPP), R1-060773, “Text Proposal of Prioritizing Non-Synchronized Random Access in E-UTRA Uplink”, ITRI, 3GPP TSG-RAN WG1 Meeting #44bis, Athens, Greece, Mar. 27-31, 2006, 6 pages.
3rd Generation Partnership Project (3GPP), R1-072648, “LS on LTE Latency Analysis”, RAN WG2, 3GPP TSG Ran WG1 Meeting #49bis, Orlando, Florida, Jun. 25-29, 2007, 10 pages.
3rd Generation Partnership Project (3GPP), R2-052787, “Channels for Random Access”, CATT, 3GPP TSG RAN WG2 Meeting #49, Seoul, Korea, Nov. 7-11, 2005, pp. 1-2.
3rd Generation Partnership Project (3GPP), R2-060078, “Handover Procedure for LTE_ACTIVE UEs”, Samsung, 3GPP TSG-RAN WG2 #50 Meeting, Sophia-Antipolis, France, Jan. 9-13, 2006, pp. 6-14.
3rd Generation Partnership Project (3GPP), R2-060095, “Real-Time Services Handover Support within E-UTRAN”, Huawei, 3GPP TSG RAN2 #50, Sophia-Antipolis, France, Jan. 9-13, 2006, pp. 1-4.
3rd Generation Partnership Project (3GPP), R2-060821, “RACH Message Structure”, Nokia, Joint 3GPP TSG-RAN WG1 & WG2 Meeting on LTE, Athens, Greece, Mar. 27-31, 2006, 2 pages.
3rd Generation Partnership Project (3GPP), R2-061135, “Intra-LTE Handover Operation”, Nokia, NTT DoCoMo, 3GPP TSG-RAN WG2 Meeting #53, Shanghai, PRC, May 8-13, 2006, 3 pages.
3rd Generation Partnership Project (3GPP), R2-061169, “Inter-ENS handover: Data Unit Forwarding for DL ?”, Samsung, 3GPP TSG-RAN2 Meeting #53, Shanghai, China, May 8-12, 2006, 4 pages.
3rd Generation Partnership Project (3GPP), R2-061196, “Cell Switching in LTE Active State”, Qualcomm Europe, 3GPP TSG-RAN WG2 Meeting #53, Shanghai, China, May 8-12, 2006, 5 pages.
3rd Generation Partnership Project (3GPP), R2-061199, “Discussion on eNode B Change Procedure”, Qualcomm Europe, 3GPP TSG-RAN WG 2 Meeting #53, Shanghai, China, May 8-12, 2006, pp. 1-7.
3rd Generation Partnership Project (3GPP), R2-061552, “Discussion on Initial Access to LTE Cell”, LG Electronics, TSG-RAN Working Group 2 #53, Shanghai, China, May 8-12, 2006, 6 pages.
3rd Generation Partnership Project (3GPP), R2-061928, “RRC Re-Establishment Procedure”, NTT DoCoMo, 3GPP TSG-RAN WG2 Ad-Hoc on LTE, Cannes, France, Jun. 27-30, 2006, 6 pages.
3rd Generation Partnership Project (3GPP), R2-062809, “Non-Contention based Handover Procedure on RACH Channel”, ZTE, TSG-RAN Working Group 2 Meeting #55, Seoul, Korea, Oct. 9-13, 2006, 4 pages.
3rd Generation Partnership Project (3GPP), R2-070167, “Neighboring Cell Information”, Samsung, 3GPP TSG-RAN WG2 Meeting #56bis, Sorrento, Italy, Jan. 15-19, 2007, 3 pages.
3rd Generation Partnership Project (3GPP), R2-070646, “Contention-Free Intra-LTE Handover”, IP Wireless, 3GPP TSG RAN WG2 #57, St. Louis, Missouri, USA, Feb. 12-16, 2007, pp. 1-4.
3rd Generation Partnership Project (3GPP), R2-071229, “Radio Link Failure and Context Recovery”, Nokia, 3GPP TSG-RAN WG2 Meeting #57bis, St. Julian's, Malta, Mar. 26-30, 2007, 3 pages.
3rd Generation Partnership Project (3GPP), R2-071359, “Radio Link Failure”, Ericsson, 3GPP TSG-RAN WG2 #57bis, St Julian, Malta, Mar. 26-30, 2007, pp. 1-4.
3rd Generation Partnership Project (3GPP), R2-072193, “LS on LTE Latency Analysis”, RAN WG2, 3GPP TSG-RAN WG2 Meeting #58, Kobe, Japan, May 7-11, 2007, 12 pages.
3rd Generation Partnership Project (3GPP), R2-072549, “On the details of the Dedicated Preamble at Intra-LTE Handover”, Ericsson, 3GPP TSG-RAN WG2 #58-bis, Orlando, Jun. 25-29, 2007, 3 pages.
3rd Generation Partnership Project (3GPP), R2-073992, “Delivery of HO Command”, Qualcomm Europe, 3GPP TSG-RAN WG 2 Meeting #59-bis, Shanghai, China, Oct. 8-12, 2007, pp. 1-3.
3rd Generation Partnership Project (3GPP), R2-074312, “Need to Obtain the Target SFN Prior to HO”, LG Electronics, 3GPP TSG-RAN#59bis WG 2 LTE, Shanghai, China, Oct. 8-12, 2007, 2 pages.
3rd Generation Partnership Project (3GPP), R2-080751, “Overload Handling for Non-Contention Based RACH”, China Mobile, 3GPP TSG-RAN WG2#61, Feb. 11-15, 2008, 2 pages.
3rd Generation Partnership Project (3GPP), R2-082948, “SIB Reading after Handover”, Panasonic, 3GPP TSG RAN WG2 RRC Ad Hoc, Sophia-Antipolis, France, Jun. 5-6, 2008, 4 pages.
3rd Generation Partnership Project (3GPP), R2-082982, “Measurement Related Actions during Handover”, Huawei, 3GPP TSG RAN WG2-RRC Ad-Hoc, Sophia-Antipolis, France, Jun. 5-6, 2008, 4 pages.
3rd Generation Partnership Project (3GPP), R3-060009, “The Handover Procedure for the LTE_ACTIVE Mobility”, Panasonic, TSG-RAN Working Group 3 Meeting #50, Sophia-Antipolis, France, Jan. 10-12, 2006, 4 pages.
3rd Generation Partnership Project (3GPP), TR 25.912 V0.1.4, “Technical Specification Group Radio Access Network, Feasibility Study for Evolved UTRA and UTRAN (Release 7)”, May 2006, pp. 1-38.
3rd Generation Partnership Project (3GPP), TR 25.912 V0.1.7, “Technical Specification Group Radio Access Network, Feasibility Study for Evolved UTRA and UTRAN (Release 7)”, Jun. 2006, pp. 1-64.
3rd Generation Partnership Project (3GPP), TR 25.912 V0.2.0, “Technical Specification Group Radio Access Network, Feasibility Study for Evolved UTRA and UTRAN (Release 7)”, Jun. 2006, pp. 1-57.
3rd Generation Partnership Project (3GPP), TR 25.912 V7.1.0, “Technical Specification Group Radio Access Network, Feasibility Study for Evolved Universal Terrestrial Radio Access (UTRA) and Universal Terrestrial Radio Access Network (UTRAN) (Release 7)”, Sep. 2009, pp. 1-57.
3rd Generation Partnership Project (3GPP), TR R3.018 V0.4.0, “Technical Specification Group Radio Access Network, Evolved UTRA and UTRAN, Radio Access Architecture and Interfaces (Release 7)”, May 2006, pp. 1-51.
3rd Generation Partnership Project (3GPP), TS 36.300 V8.7.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)”, Dec. 2008, pp. 1-144.
3rd Generation Partnership Project (3GPP), TS 36.321 V8.0.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Medium Access Control (MAC) Protocol Specification (Release 8)”, Dec. 2007, pp. 1-23.
3rd Generation Partnership Project (3GPP), TS 36.321 V8.4.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) Protocol Specification (Release 8)”, Dec. 2008, pp. 1-43.
3rd Generation Partnership Project (3GPP), TS 36.331 V8.0.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC), Protocol Specification (Release 8)”, Dec. 2007, pp. 1-56.
3rd Generation Partnership Project (3GPP), TS 36.331 V8.4.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC), Protocol Specification (Release 8)”, Dec. 2008, pp. 1-198.
3rd Generation Partnership Project (3GPP), TS 25.331 V6.7.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 6)”, Sep. 2005, pp. 1-1166.
3rd Generation Partnership Project (3GPP), TS 25.331 V6.9.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 6)”, Mar. 2006, pp. 1-1209.
3rd Generation Partnership Project (3GPP), TS 25.331 V8.0.0, “Technical Specification Group Radio Access Network, Radio Resource Control (RRC), Protocol Specification (Release 8)”, Sep. 2007, pp. 1-1460.
3rd Generation Partnership Project (3GPP), TS 36.211 V8.1.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Channels and Modulation (Release 8)”, Nov. 2007, pp. 1-54.
3rd Generation Partnership Project (3GPP), TS 36.211 V8.5.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Channels and Modulation (Release 8)”, Dec. 2008, pp. 1-82.
3rd Generation Partnership Project (3GPP), TS 36.300 V8.0.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)”, Mar. 2007, pp. 1-82.
3rd Generation Partnership Project (3GPP), TS 36.300 V8.3.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)”, Dec. 2007, pp. 1-121.
3rd Generation Partnership Project (3GPP), TS 36.300 V8.4.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)”, Mar. 2008, pp. 1-126.
3rd Generation Partnership Project (3GPP), TS 36.300 V8.5.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)”, May 2008, pp. 1-134.
3rd Generation Partnership Project (3GPP), TS 36.300 V8.8.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)”, Mar. 2009, pp. 1-157.
3rd Generation Partnership Project (3GPP), TS 36.300 V8.9.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. 2009, pp. 1-159.
3rd Generation Partnership Project (3GPP), TS 36.300 V9.0.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. 2009, pp. 1-157.
3rd Generation Partnership Project (3GPP), TS 36.331 V8.1.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC), Protocol Specification (Release 8)”, Mar. 2008, pp. 1-122.
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 (RRC), Protocol Specification (Release 8)”, May 2008, pp. 1-151.
3rd Generation Partnership Project (3GPP), TS 36.331 V8.5.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC), Protocol Specification (Release 8)”, Mar. 2009, pp. 1-204.
3rd Generation Partnership Project (3GPP), TS 36.331 V8.6.0, “Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC), Protocol Specification (Release 8)”, Jun. 2009, pp. 1-207.
European Telecommunications Standards Institute (ETSI), TS 136 300 V8.0.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.0.0 Release 8)”, Mar. 2007, pp. 1-84.
European Telecommunications Standards Institute (ETSI), TS 136 300 V8.4.0, “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.4.0 Release 8)”, Apr. 2008, 5 pages.
Festag, A., “Optimization of Handover Performance by Link LayerTriggers in IP-Based Networks: Parameters, Protocol Extensions and AP is for Implementation”, Telecommunication Networks Group, TKN Technical Report TKN-02-014, Version: 1, Aug. 2002, 32 pages.
Ghosh et al., “Random Access Design for UMTS Air-Interface Evolution”, IEEE 65th Vehicular Technology Conference, 2007, VTC2007-Spring, Apr. 22-25, 2007, pp. 1041-1045.
Koodli et al., “A Context Transfer Protocol for Seamless Mobility”, Communication Systems Laboratory, Nokia Research Center, Seamoby Working Group, Aug. 30, 2002, pp. 1-35.
Related Publications (1)
Number Date Country
20220007238 A1 Jan 2022 US
Provisional Applications (1)
Number Date Country
61033676 Mar 2008 US
Continuations (5)
Number Date Country
Parent 16444736 Jun 2019 US
Child 17478381 US
Parent 15977706 May 2018 US
Child 16444736 US
Parent 15067607 Mar 2016 US
Child 15977706 US
Parent 14169951 Jan 2014 US
Child 15067607 US
Parent 12392235 Feb 2009 US
Child 14169951 US