throbber
(12) United States Patent
`Chun et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 9,078,236 B2
`Jul. 7, 2015
`
`US009078236B2
`
`(54) RANDOMACCESS SCHEME FOR
`PREVENTING UNNECESSARY
`RETRANSMISSION AND USEREQUIPMENT
`FOR THE SAME
`(75) Inventors: Sung Duck Chun, Anyang-Si (KR);
`Sung Jun Park, Anyang-Si (KR); Seung
`June Yi, Anyang-Si (KR)
`(73) Assignee: LG Electronics Inc., Seoul (KR)
`(*) Notice:
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 415 days.
`12/670,773
`Jan. 5, 2010
`PCT/KR2O1O/OOOO36
`
`(21) Appl. No.:
`(22) PCT Filed:
`(86). PCT No.:
`S371 (c)(1),
`Jul. 8, 2011
`(2), (4) Date:
`(87) PCT Pub. No.: WO2010/077122
`PCT Pub. Date: Jul. 8, 2010
`Prior Publication Data
`US 2011 FO261763 A1
`Oct. 27, 2011
`Related U.S. Application Data
`(60) Provisional application No. 61/142,613, filed on Jan.
`5, 2009.
`Foreign Application Priority Data
`
`(65)
`
`(30)
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`6,594,240 B1
`6,785,548 B2
`
`7/2003 Chuah et al.
`8/2004 Moulsley et al.
`(Continued)
`
`FOREIGN PATENT DOCUMENTS
`
`CN
`CN
`
`9, 2001
`1315099. A
`5, 2008
`101188852. A
`(Continued)
`
`OTHER PUBLICATIONS
`
`Nokia Siemens Networks, Nokia, “Triggers for Power Headroom
`Reports in EUTRANUplink.” Agenda Item 6.3.2. Discussion/Deci
`sion, 3GPP TSG RAN WG1 Meeting #52bis, Shenzhen, China,
`R1-081464, Mar. 31-Apr. 4, 2008. One page.
`(Continued)
`
`Primary Examiner — Alpus HHsu
`Assistant Examiner — Hooman Houshmand
`(74) Attorney, Agent, or Firm — Birch, Stewart, Kolasch &
`Birch, LLP
`
`(57)
`ABSTRACT
`A random access scheme for preventing unnecessary retrans
`mission and a user equipment for the same are disclosed. If a
`Contention Resolution (CR) timer expires in contention reso
`lution during a random access procedure or if a Physical
`Downlink Control Channel (PDCCH) signal or a Physical
`Downlink Shared Channel (PDSCH) signal associated with
`the PDCCH signal does not match an identifier of a terminal,
`a Hybrid Automatic Repeat Request (HARQ) buffer for stor
`ing a Medium Access Control Packet Data Unit (MAC PDU)
`transmitted in the random access procedure is flushed Such
`that unnecessary data retransmission can be prevented.
`
`13 Claims, 10 Drawing Sheets
`
`Dec. 24, 2009 (KR) ........................ 10-2009-0130622
`
`(51) Int. Cl.
`H04W 74/00
`HO4W 56/OO
`HO4W 74/08
`(52) U.S. Cl.
`CPC ........ H04W 74/008 (2013.01); H04 W56/0005
`(2013.01); H04W 56/0045 (2013.01); H04W
`74/0833 (2013.01)
`
`(2009.01)
`(2009.01)
`(2009.01)
`
`(58) Field of Classification Search
`None
`See application file for complete search history.
`
`NB
`
`UE
`
`a) starts TAT
`b) uses "HARQ process
`c) generates amACPDU aud
`store ill Msg3buffer
`d) fetches the MACPDU from
`Msg3buffer and stores itia the
`associated HARQbuffer
`
`:
`
`a)detects the contestion
`restlution failure
`t) stopsTAT
`c) flushesHARQbuffers
`d) performs re-attempts of the
`randoD accessprocedure
`
`a) uses"y"HARQprocess
`b)fetches the ACPDU from
`Misg3butter and storestin the
`associated ARQbuffer
`c) starts TAT
`
`Random Accesspreamble
`
`2. Randon Access Response
`
`MACPDUin"x"HARQbuffer
`
`Randlin AccessPreamble
`
`Randon Access Respolise
`
`MACPDUXx"HARQbuffer
`MACPDUiny"HARQbuffer
`
`LG Elecs. Ex. 1021
`LG Elecs. v. Pantech Corp.
`IPR2023-01273 Page 1
`
`

`

`US 9,078.236 B2
`Page 2
`
`2011/O103499 A1*
`2011 0116364 A1
`2011/0216705 A1
`2011/0216706 A1
`2014/0092851 A1*
`
`5, 2011
`5, 2011
`9, 2011
`9, 2011
`4, 2014
`
`Cheng et al. .................. 375,260
`Zhang et al.
`Lee et al.
`Lee et al.
`Wang et al. ................... 370,329
`
`FOREIGN PATENT DOCUMENTS
`
`EP
`EP
`EP
`EP
`EP
`JP
`JP
`JP
`JP
`JP
`JP
`JP
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`KR
`RU
`RU
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`WO
`
`2, 2007
`1755355 A1
`9, 2008
`1973.281 A2
`197617O A1 10, 2008
`2O2O821 A1
`2, 2009
`2094053 A1
`8, 2009
`2000-341204 A 12/2000
`2007-266733. A 10/2007
`2009-52.5655 A
`T 2009
`2009-303213 A 12/2009
`2010-518724. A
`5, 2010
`2011-508538 A
`3, 2011
`2011-509049 A
`3, 2011
`102005OO57926 A
`6, 2005
`10-0567 211 B1
`4/2006
`10-2006-01-15175 A 11, 2006
`10-2007-0107619 A 11, 2007
`10-2007-0108300 A 11, 2007
`10-2007-0109313 A 11, 2007
`10-2008-0016367
`2, 2008
`10-2008-0026583. A
`3, 2008
`10-0816598 A
`3, 2008
`10-2008-0039.177 A
`5, 2008
`10-2008-0039294. A
`5, 2008
`10-2008-0049596 A
`6, 2008
`10-2008-0065880 A
`T 2008
`10-2008-01 12649 A 12/2008
`10-2009-0014937 A
`2, 2009
`10-2009-0016402 A
`2, 2009
`10-2009-0084690 A
`8, 2009
`10-0938102 B1
`1, 2010
`2233546 C2
`T 2004
`23328O2 C2
`1, 2008
`WO-2004-056009 A1
`T 2004
`WO 2006/118427 A2 11/2006
`WO-2007/082407 A1
`7/2007
`WO-2007/083230 A2
`7/2007
`2007/088465 A2
`8, 2007
`WO 2007/091831 A2
`8, 2007
`WO-2007/1282O4 A1 11, 2007
`WO-2007,14391.6 A1 12/2007
`WO-2008/024628 A2
`2, 2008
`WO-2008.042967 A2
`4/2008
`WO-2008/054112 A2
`5, 2008
`WO-2008/097O23 A1
`8, 2008
`WO-2008/097O3O A1
`8, 2008
`WO 2008/100009 A1
`8, 2008
`WO-2008, 131401 A1 10, 2008
`WO-2008, 155469 A1 12/2008
`WO-2009/005429 A1
`1, 2009
`WO-2009/023470 A2
`2, 2009
`WO 2009/086188 A2
`T 2009
`WO-2009/088858 A1
`T 2009
`WO 2009,096.195 A1
`8, 2009
`OTHER PUBLICATIONS
`
`3GPP TS 36.523-1, V8.0.0 (Dec. 2008), 3rd Generation Partnership
`Project, Technical Specification Group Radio Access Network,
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
`Packet Core (EPC), User Equipment (UE) Conformance Specifica
`tion, Part 1: Protocol Conformance Specification, Release 8, 497
`pageS.
`LG Electronics Inc., "Correction to MAC PDU Format for Random
`Access Response.” 3GPP TSG-RAN2 Meeting #62bis, R2-083370,
`Change Request 36.321, Version 8.x.0, Jun. 30-Jul. 4, 2008, Warsaw,
`Poland, 4 pages.
`3GPP TS 36.321 V8.3.0 “3rd Generation Partnership Project; Tech
`nical Specification Group Radio Access Network: Evolved Universal
`Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC)
`Protocol Specification (Release 8)". Sep. 2008, 36 pages.
`
`370,354
`370,278
`
`370/350
`
`370,329
`
`370,329
`
`370,311
`
`370,329
`
`370,329
`714,749
`
`370,329
`
`370,345
`
`370,328
`
`
`
`12, 2004 Wu
`9, 2005
`Soliman
`T/2006
`Parsa et al.
`12, 2010
`Park et al.
`6, 2011
`Yi et al.
`T/2011
`Pettersson
`T/2012
`9, 2012
`12, 2014
`11, 2001
`1, 2002
`10, 2002
`11, 2002
`5/2003
`9, 2004
`1/2005
`4, 2005
`6, 2005
`6, 2005
`6, 2005
`11/2005
`1, 2006
`1, 2006
`12, 2006
`4, 2007
`6, 2007
`7/2007
`9, 2007
`1, 2008
`2, 2008
`4, 2008
`4, 2008
`8, 2008
`8, 2008
`8, 2008
`8, 2008
`9, 2008
`11, 2008
`12, 2008
`12, 2008
`12, 2008
`2, 2009
`2, 2009
`4, 2009
`4, 2009
`6, 2009
`6, 2009
`T/2009
`T/2009
`8, 2009
`8, 2009
`9, 2009
`9, 2009
`9, 2009
`9, 2009
`9, 2009
`10, 2009
`11/2009
`12, 2009
`12, 2009
`12, 2009
`12, 2009
`12, 2009
`2, 2010
`2, 2010
`4, 2010
`4, 2010
`5, 2010
`T/2010
`8, 2010
`9, 2010
`10, 2010
`11, 2010
`12, 2010
`1, 2011
`
`Sachs et al.
`Benveniste
`Miyazaki et al.
`Jiang
`Iacono et al.
`Moulsley et al.
`Kim
`Das et al.
`Walton et al.
`Dicket al.
`Finn
`Balasubramanian et al.
`Terry
`Revel et al.
`Lee
`Jung et al.
`Sammour et al.
`Pajukoski et al.
`Wang et al.
`Cho et al.
`Fischer et al.
`Driscoll et al.
`Damnjanovic
`Worrall
`Ranta-Aho et al.
`Malladi et al.
`Jen
`Lee et al.
`Park et al. ...................
`Alanara et al.
`Bertrand et al.
`Wang et al. .................
`Kim et al.
`Pelletier et al. .............
`Rosa et al.
`Meylan
`KitaZoe et al.
`Jersenius et al.
`Cave et al.
`Yu et al. ......................
`Tormalehto
`Sammour et al.
`Lee et al.
`Kuo ............................
`Damnjanovic et al.
`Lee et al.
`Lee et al.
`Yoo .............................
`Kuo ............................
`Guo
`Kennedy et al.
`Yi et al.
`Wang et al.
`Terry
`Ou et al.
`Yamada et al.
`Damnjanovic et al.
`Wu
`Fischer et al.
`Park et al.
`Chun et al.
`Fan et al.
`Lu et al.
`Aoyama et al.
`Wang et al. .................
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`6,836,469
`6,950,417
`7,075,971
`7,848,346
`7,957,298
`7,986,946
`8,223,708
`8,274,969
`8,908,570
`2001, 0043582
`2002fOOO9067
`2002fO1546.53
`2002.0167920
`2003/OO95534
`2004/O185892
`2005, OO14508
`2005/OO78641
`2005/O 117675
`2005/O12O097
`2005, 0141436
`2005/0249123
`2006, OO13182
`2006, OO13268
`2006/028O145
`2007/0076679
`2007/O1401.78
`2007/0171933
`2007/02O6531
`2008, OOO8212
`2008.0043771
`2008.OO96563
`2008/0098234
`20080186892
`2008. O188247
`2008/O192766
`2008/0207150
`2008/0232317
`2008/029.4958
`2008/0310396
`2008/0313300
`2008/0316961
`2009 OO46641
`2009/0052388
`2009, OO86671
`2009, OO88195
`2009. O1561.94
`2009,0163211
`2009/0175187
`2009,0186624
`2009,0196.208
`2009/0213968
`2009/0225711
`2009/0232058
`2009, O232O76
`2009, 0238141
`2009/023.9545
`2009,02599.10
`2009,0279495
`2009/0300457
`2009/03O3954
`2009/0305665
`2009/0316586
`2009/0316593
`2010.0027511
`2010.0034.162
`2010, 0080181
`2010/0093386
`2010/011 1067
`2010/01722.99
`2010/0202288
`2010/0226325
`2010.02601.36
`2010/0281486
`2010/033O995
`2011/0002262
`
`B1
`B2
`B2
`B2
`B2
`B2
`B2
`B2 *
`B2 *
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1
`A1*
`A1
`A1
`A1*
`A1
`A1*
`A1
`A1
`A1
`A1
`A1
`A1*
`A1
`A1
`A1
`A1*
`A1
`A1
`A1
`A1*
`A1*
`A1
`A1
`A1
`A1
`A1
`A1*
`A1
`A1
`A1*
`A1
`A1
`A1
`A1
`A1
`A1
`
`IPR2023-01273 Page 2
`
`

`

`US 9,078.236 B2
`Page 3
`
`(56)
`
`References Cited
`
`OTHER PUBLICATIONS
`
`Huawei, "Corrections to Random Access Procedure, 3GPP TSG
`RAN WG 2 Meeting #64, R2-0087042, Change Request 36.321
`CR-189 Rev. Version 8.3.0, Nov. 10-14, 2008, Prague, Czech Repub
`lic, 4 pages.
`LG Electronics Inc., et al., “Reflection of RAN1 LS on Timing Adjust
`and Addition of MAC Padding in Random Access Response.” 3GPP
`TSG-RAN2 Meeting #64, R2-086374, Change Request 36.321 CR
`0 128rl Rev Version 8.3.0, Nov. 10-14, 2008, Prague, Czech Repub
`lic, 7 pages.
`Ericsson, “Correction to UEtransmission powerheadroom report for
`LTE, R2-083897, pp. 18-22, May 2008, Including 3GPP “Change
`Request”, TSG-RAN236.321 V8.2.0, R2-083897, Meeting #63, Jeju
`Island, Korea, May 18-22, 2008.
`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, Ver
`sion 8.4.0 Release 8, Apr. 2008.
`LG Electronics Inc. et al., “Counter Proposal to R2-090969 on
`Managment for HARQ Buffer with TAT.” 3GPP TSG-RAN2 Meet
`ing #65, R2-091232, Feb. 9-13, 2009, Athens, Greece, 3 pages.
`LG Electronics Inc., “Management for HARQ Buffer with TAT.”
`3GPP TSG-RAN2 Meeting #65, R2-090969, Feb. 9-13, 2009, Ath
`ens, Greece, 2 pages.
`Nokia Corporation et al., “Message 3 Definition.”3GPP TSG-RAN2
`Meeting #64, R2-086077, Oct. 10-14, 2008, Prague, Czech Republic,
`8 pages.
`Dahlman et al., “3G Evolution: HSPA and LTE for Mobile Broad
`band.” Elsevier, Edition 2, 2008, pp. 441, Cover page, and, p. 441.
`LG Electronics Inc., “Correction to RACH Procedure, 3GPP TSG
`RAN2, Meeting #64, R2-087070, Change Request, 36.321 CR 157,
`Rev. 1, Version 8.3.0, Prague, Czech Republic, Nov. 10-14, 2008, 6
`pageS.
`3GPP “Medium Access Control (MAC) Protocol Specification
`(Release 8), TS 36.321 V8.1.0 (Mar. 2008).
`3GPP, “Evolved Universal Terrestrial Radio Access (E-UTRA). TS
`36.321 V8.1.0 (Mar. 2008).
`3GPP Draft: R2-081035 LTE RACH M2 V1, 3rd Generation Part
`nership Project (3GPP), Mobile Competence Centre: 650, Route Des
`Lucioles; F=06921 Sophia-Antipolis Cedex; France, vol. RAN
`WG2, No. Sorrento, Italy; Feb. 5, 2008, XP050138825.
`3GPP Draft: R2-0810189 LTE RA BO RO, 3GPP, Mobile Com
`petence Centre, 650, Route Des Lucioles; F-06921 Sophia-Antipolis
`Cedex; France, vol. RAN WG2, No. Sevilla, Spain, Jan. 7, 2008,
`XP050138064, R2-080189.
`NTT Docomo et al: “RA response format”3GPP Draft: R2-080451,
`3GPP, Mobile Competence Centre; 650, Route Des Lucioles;
`F-06921 Sophia-Antipolis Cedex; France, vol. RAN WG2, No.
`Sevilla, Spain; Jan. 8, 2008, XP050138299.
`LG Electronics Inc.: “Missing condition for unsuccessful reception of
`Msg2' 3GPP Draft: R2-090323 Proposed CR to 36.321 on Missing
`Condition for Unsuccessful Reception of MSG2, 3GPP, Mobile
`Competence Centre; 650, Route Des Lucioles; F-06921 Sophia
`Antipolis Cedex, France, No. Ljubljana; Jan. 6, 2009, XP050322312.
`MAC Rapporteurs (Quamcomm Europe et al: "E-UTRAMAC pro
`tocol specification update' 3GPP Draft: R2-08 1389 CR0001 to
`36321-800, 3GPP, Mobile Competence Centre: 650, Route des
`Lucioses; F-06921 Sophia-Antipolis cedex; France, vol. RAN WG2.
`Sorento, Italy, Feb. 23, 2008, XP0501391 10.
`Panasonic: "Clarification on a Active Time a definition' 3GPP Draft;
`R2-082225, 3GPP, Mobile Competence Centre: 650, Route des
`Lucioles; F-06921 Sophia-antipolis cedex, France, vol. RAN WG2.
`No. Kansas City, USA; Apr. 29, 2008, XP050139994.
`3GPP Draft: R2-08025.09 Restriction to PDCCH for Contention
`Resolution RO, 3GPP, Mobile Competence Centre; 650, Route des
`Lucioses; F-06921 Sophia-Antipolis cedex; France, vol. RAN WG2.
`No. Kansas City, USA; Apr. 29, 2008, pp. 1-2, XP050140190.
`R2-082.509.
`
`3GPP Draft: R2-074787 DL Grant MSG2 RO, 3GPP, Mobile
`Competence Centre; 650, Route des Lucioses; F-06921 Sophia
`Antipolis cedex; France, vol. RANWG2, No. Jeju:Nov. 5, 2007, Oct.
`20, 2007, pp. 1-3, XP050137299.
`“Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved
`Universal Terrestrial Radio Access (E-UTRAN); Overall descrip
`tion: Stage 2 (3GPP TS 36.300 version 8.4.0 Release 8): ETSI TS 136
`300 ETSI Standards, LIS, Sophia antipolis cedex, France, vol.3-R2,
`No. V8.4.0, (Apr. 1, 2008), XPO 14041816.
`Sunplus Mmobile Inc: "Align the DRXActive Time with RA proce
`dure” 3GPP Draft: R2-083428, 3GPP, Mobile Competence Centre;
`650, Route des Lucioses; F-06921 Sophia-Antipolis cedex; France,
`vol. RAN WG2, No. Warsaw, Poland, Jun. 23, 2008, XP050140819.
`LG Electronics Inc.: “Correction to DRX 3GPP Draft: R2-083274
`Proposed CR to 36.321 REL-8 Correction to DRX, 3GPP, Mobile
`Competence Centre; 650, Route des Lucioses; F-06921 Sophia
`Antipolis cedex; France, vol. RAN WG2, No. Warsaw, Poland; Jun.
`23, 2008, XP050140694.
`MAC Rapporteurs (Qualcomm Europe et al: "E-UTRA MAN pro
`tocol specification update' 3GPP Draft: R2-081719 E-UTRAMAC
`Protocol Specification Update (CR), 3rd Generation Partnership
`Project (3GPP), Mobile Competence Centre: 650, Route des
`Lucioses; F-06921 Sophia-Antipolis cedex; France, vol. RAN WG2.
`No. Shenzhen, China; Mar. 25, 2008, XP050139431.
`LG Electronics: “Corrections to the Random Access Response recep
`tion” 3GPP Draft: R2-082447 LTE-RACH RESP RO, 3GPP
`Mobile Competence Centre; 650, Route Des Lucioles; F-06921
`Sophia-Antipolis Cedex; France, vol. RAN WG2, No. Kansas City,
`USA: Apr. 28, 2008, XP050140134.
`LG Electronics Inc.: “Correction to RACH Procedure' 3GPP Draft;
`R2-086137 IREL-8 Proposed CR to 36.321 Correction to RACH
`Procedure, 3rd Generation Partnership Project (3GPP) Mobile Com
`petence Centre, 650, Route des Lucioses; F-06921 Sophia-Antipolis
`cedex; France, No. Prague, Czech Republic; Nov. 10, 2008, pp. 1-6,
`XPOSO321188.
`Handover Failure Handling, 3GPP Draft: R2-081054, -3rd Genera
`tion Partnership Project (3GPP), Mobile Competence Centre; 65.
`route des Lucioles; F-06921 Sophia-Antipolis Cedex; France, Feb. 4.
`2008.
`Ghosh et al., “Random Access Design for UMTS Air-Interface Evo
`lution.” IEEE 65th Vehicular Technology Conference, Apr. 22, 2007.
`pp. 1041-1045.
`3GPP TS 36.321 V8.2.0(May 2008); Technical Specification Group
`Radio Access Network; Evolved Universal Terrestrial Radio Access
`(E-UTRA) Medium Access Control (MAC) protocol specification
`(Release 8), p. 1-33.
`Panasonic: “Priority handling of MAC Control Elements' Internet
`Citation, May 5, 2008, XP002537451.
`MAC Rapporteurs (Qualcomm Europe et al: “36.321 CR covering
`agreements of RAN2 #61bis and RAN2#62): R2-082902,
`XP050140449, May 2008.
`“BSR priority”3GPP Draft, R2-08 1589 BSR Priority, 3GPP, Mobile
`Competence centre; 650, Route des Lucioles; F-06921 Sophia
`Antipolis cedex; France. RAN WG2, No. Shenzhen, China; Mar. 24.
`2008, XP0501393.21.
`Infineon: “TP for the UL Logical channel prioritization” 3GPP
`Mobile Competence centre: 650, Route des Lucioles; F-06921
`Sophia-Antipolis cedex; France, vol. RAN WG2, No. Kansas City,
`WAS, Apr. 29, 2008, XP050140185, R2-082504.
`LG Electronics Inc.: "Correction to Multiplexing Procedure for BSR'
`3GPP Draft: R2-083275, 3GPP, vol. RAN WG2, No. Warsaw,
`Poland: May 23, 2008, XP050140695.
`3GPP Draft: R2-082049 See whole document esp. section 5.1 and
`Subsections thereof and Subsections 5.4.3.1 and 5.4.3.2, Mar. 2008,
`XP 05O139679.
`3GPP Draft: R2-09 1633.cr273r1-R2-090988, See whole document
`esp. subsections 5.4.3.1 and 5.4.3.2 Feb. 2009, XP 050323507.
`Alcatel-Lucent: “TP on Power Headroom reporting 3GPP Draft;
`R2-082224 PH Text Proposal, 3GPP Mobile Competence centre:
`650, Route des Lucioles; F-06921 Sophia-Antipolis cedex; France,
`vol. RAN WG2, No. Kansas City, USA; Apr. 28, 2008,
`XPO)5O139993.
`
`IPR2023-01273 Page 3
`
`

`

`US 9,078.236 B2
`Page 4
`
`(56)
`
`References Cited
`
`OTHER PUBLICATIONS
`
`Nokia Siemens Networks: “Power Headroom Reporting” Internet
`Citation, May 5, 2008, pp. 1-4, XP002537452, R2-082197.
`Ericsson: “UE transmission power headroom report for LTE' 3GPP
`TSG RAN WG2 #62, R2-082147, May 5, 2008, pp. 1-4,
`XP002539839 (Aug. 4, 2009).
`Nokia Siemens Networks et al: “Triggers for Power Headroom
`Reports in EUTRAN Uplink” 3GPP Draft; R1-080947, 3GPP
`Mobile Competence centre: 650, Route des Lucioles; F-06921
`
`Sophia-Antipolis cedex; France, vol. RANWG 1. No. Sorrento, Italy;
`Feb. 5, 2008, XP050109419.
`Nokia: “Scheduling Information for E-UTRAN Uplink” Oct. 8,
`2007-Oct. 12, 2007, vol. TSG-RAN WG2 Meeting #59BIS, No.
`R2-073909, pp. 1-3, Oct. 2007, XP002522064.
`Ericsson et al., “Prioritization of MAC control elements', 3GPP
`TSG-RAN WG2 Meeting #64, Nov. 10-14, 2008, R2-087413, 3
`pageS.
`Huawei, “Discussion of Message 3, 3GPP TSG RAN2 #60bis, Jan.
`14-18, 2008, R2-080239, pp. 1-3.
`* cited by examiner
`
`IPR2023-01273 Page 4
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 1 of 10
`
`US 9,078,236 B2
`
`FIG. 1
`
`
`
`102
`
`Core Network
`
`IPR2023-01273 Page 5
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 2 of 10
`
`US 9,078,236 B2
`
`FIG. 2
`
`FIG. 3
`
`
`
`UE
`
`E-UTRAN
`
`IPR2023-01273 Page 6
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jul. 7, 2015
`Jul. 7, 2015
`
`Sheet 3 of 10
`Sheet 3 of 10
`
`US 9,078,236 B2
`US 9,078,236 B2
`
`FIG. 4
`FIG.
`4
`
`
`
`
`
`S405$406
`
`8401
`
`S.
`8407
`
`S.s
`$402$404
`
`IPR2023-01273 Page 7
`
`8403
`
`5.
`
`IPR2023-01273 Page 7
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 4 of 10
`
`US 9,078,236 B2
`
`FIG. 5
`
`
`
`Random Access Preamble
`
`
`
`
`
`
`
`Radom Access Respoise
`
`- S502
`
`Scheduled Transmission
`
`:
`
`.
`
`.
`
`.
`
`ys
`
`Contention Resolution
`
`is
`
`is:
`
`S504
`
`IPR2023-01273 Page 8
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 5 of 10
`
`US 9,078,236 B2
`
`EIG. 6
`
`a) starts TAT
`b)uses"x"HARQ process
`c) generates a MACPDU and
`store it in Msg3 buffer
`d) fetches the MACPDU from
`Msg3 buffer and stores it in the
`associated HARQ buffer
`
`
`
`
`
`a) detects the contention
`resolution failure
`b) stop TAT
`c) performs re-attempts of the
`random access procedure
`
`a) uses"y"HARQ process
`b) fetches the MACPDU from
`Msg3 buffer and stores it in the
`asSociated HARQ buffer
`c) starts TAT
`if "x"HARQbuffer still keeps
`the MACPDU, retransmits the
`MACPDU in "x"HARQbuffer
`
`
`
`
`
`
`
`
`
`l, Random Access Preamble
`
`2. Random Access Response
`
`MACPDU in "x"HARQbuffer
`
`Random Access Preamble
`
`Random Access Response
`
`
`
`
`
`MAC PDU in "x"HARQbuffer
`MAC PDU in "y"HARQ buffer
`
`IPR2023-01273 Page 9
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 6 of 10
`
`US 9,078,236 B2
`
`FIG. 7
`
`UE
`
`Random Access Preamble
`
`Random Access Response
`
`CR Timer starts
`
`MAC PDU with C-RNT
`W1
`-
`
`S704 O
`
`k
`
`eNB
`
`
`
`S701
`
`S702
`
`S703
`
`PDCCH not addressed to C-RNTI
`
`S705
`
`Flush HARQ buffer
`used at S703
`
`S706
`
`IPR2023-01273 Page 10
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 7 of 10
`
`US 9,078,236 B2
`
`ETG. 8
`
`
`
`CRTimer starts
`
`
`
`
`
`
`
`UE
`
`
`
`
`
`
`
`PDCCH addressed to Temporary C-RNTI /
`
`PDSCH(MACPDU)
`
`Flush HARQ buffer
`used at S803
`
`S807
`
`Random Access Preamble
`
`Random AcceSS Response
`
`MAC PDU with S-TMSI
`UUW S
`
`eNB
`
`S8O
`
`S802
`
`S803
`
`S805
`
`S806
`
`IPR2023-01273 Page 11
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 8 of 10
`
`US 9,078,236 B2
`
`FIG. 9
`
`UE
`
`
`
`
`
`
`
`eNB
`
`S901
`
`S902
`
`Random Access Preamble
`
`Random ACCCSS Response
`
`MAC PDU with C-RNT
`of MAC PDU With S-TMSI
`
`S903
`
`?
`
`CRTimer starts
`
`IPR2023-01273 Page 12
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 9 of 10
`
`US 9,078,236 B2
`
`FIG, 10
`
`a) starts TAT
`b)uses"x"HARQ process
`c) generates a MAC PDU and
`store it inMsg3 buffer
`d) fetches the MACPDU from
`Msg3 buffer and stores it in the
`associated HARQ buffer
`
`
`
`
`
`
`
`
`
`a) detects the contention
`resolution failure
`b) stops TAT
`c) flushes HARQ buffers
`d) performs re-attempts of the
`random access procedure
`
`a) uses"y"HARQ process
`b) fetches the MACPDU from
`Msg3 buffer and stores it in the
`associated HARQ buffer
`c) starts TAT
`
`eNB
`
`1. Random Access Preamble
`
`2. Random Acccss Response
`
`MAC PDU in "x"HARQ buffer
`
`Random Access Preamble
`
`Random Access Response
`
`MACPDU ("x"HARQ buffer
`MACPDU in "y"HARQ buffer
`
`-le
`
`IPR2023-01273 Page 13
`
`

`

`U.S. Patent
`
`Jul. 7, 2015
`
`Sheet 10 of 10
`
`US 9,078,236 B2
`
`FIG.
`
`11
`
`IZII
`
`(OZII)OVW
`
`
`
`
`
`
`
`que19 TQ
`
`9?QUEÐJA WY?
`
`IPR2023-01273 Page 14
`
`

`

`US 9,078,236 B2
`
`1.
`RANDOMACCESS SCHEME FOR
`PREVENTING UNNECESSARY
`RETRANSMISSION AND USEREQUIPMENT
`FOR THE SAME
`
`This application is the National Phase of PCT/KR2010/
`000036 filed on Jan. 5, 2010, which claims priority under 35
`U.S.C. 119(e) to U.S. Provisional Application No. 61/142,
`613 filed on Jan.5, 2009 and under 35 U.S.C. 119(a) to Patent
`Application No. 10-2009-0130622 filed in Korea on Dec. 24,
`2009, all of which are hereby expressly incorporated by ref
`erence into the present application.
`
`BACKGROUND OF THE INVENTION
`
`10
`
`15
`
`2
`FIGS. 2 and 3 show an architecture of a radio interface
`protocol between a terminal and a UTRAN according to the
`3GPP radio access network standard.
`The radio interface protocol shown in FIGS. 2 and 3 is
`horizontally composed of a physical layer, a data link layer,
`and a network layer, and is vertically composed of a user
`plane for transmitting user data and a control plane for trans
`ferring control signaling. In detail, FIG. 2 shows the layers of
`the radio protocol control plane and FIG.3 shows the layers of
`the radio protocol user plane. The protocol layers of FIGS. 2
`and 3 may be divided into L1 (Layer 1), L2 (Layer 2), and L3
`(Layer 3) based upon the lower three layers of the Open
`System Interconnection (OSI) standard model that is widely
`known in the field of communication systems.
`Hereinafter, particular layers of the radio protocol control
`plane of FIG.2 and the radio protocol userplane of FIG.3 will
`be described.
`The physical layer (PHY) (Layer 1) provides an informa
`tion transfer service to an upper layer using a physical chan
`nel. The PHY layer is connected to a Medium Access Control
`(MAC) layer located thereabove via a transport channel, and
`data is transferred between the PHY layer and the MAC layer
`via the transport channel. At this time, the transfer channel is
`roughly divided into a dedicated transfer channel and a com
`mon transfer channel depending on whether or not a channel
`is shared. In addition, data is transferred respectively between
`different physical layers, namely, between the respective
`physical layers of the transmitting side and the receiving side
`via a physical channel using radio resources.
`Various layers are located in Layer 2. First, the Medium
`Access Control (MAC) layer maps various logical channels
`to various transfer channels and performs a logical channel
`multiplexing function for mapping various logical channels
`to one transfer channel. The MAC layer is connected to a
`Radio Link Control (RLC) layer which is an upper layer via a
`logical channel, and the logical channel may be roughly
`divided into a control channel for transmitting information
`about the control plane and a traffic channel for transmitting
`information about the user plane, according to the type of
`transmitted information.
`The RLC layer of the second layer segments and concat
`enates data received from an upper layer, thereby controlling
`a data size so as to be suitable for a lower layer to transmit data
`to a radio interval. The RLC provides three modes, namely, a
`transparent mode (TM), an unacknowledged mode (UM) and
`an acknowledged Mode (AM) to support various QoSs
`requested by each radio bearer (RB). Especially, for reliable
`data transmission, the AM RLC performs a function to
`retransmit data through an automatic repeat request (ARQ).
`A packet data convergence protocol (PDCP) layer located
`at the second layer is used to efficiently transmit IP packets,
`such as IPv4 or IPv6, on a radio interval with a relatively
`narrow bandwidth. For this purpose, the PDCP layer reduces
`the size of an IP packet header which is relatively great in size
`and includes unnecessary control information, namely, per
`forms a function called header compression. Accordingly,
`only necessary information can be included in the headerpart
`of data for transmission, so as to increase a transmission
`efficiency of a radio interval. In the LTE system, the PDCP
`layer also performs a security function. The security function
`includes a ciphering function for preventing data monitoring
`from a third party, and an integrity protection function for
`preventing data manipulation from a third party.
`A radio resource control (RRC) layer located at a highest
`portion of the third layer is defined in the control plane. The
`RRC layer handles logical channels, transport channels and
`physical channels for the configuration, re-configuration and
`
`1. Field of the Invention
`The present invention relates to a random access Scheme of
`a user equipment in a mobile communication system, and
`more particularly, to a random access Scheme for preventing
`unnecessary retransmission and a user equipment for the
`SaC.
`2. Discussion of the Related Art
`As an example of a mobile communication system to
`which the present invention is applicable, a 3" Generation
`Partnership Project Long Term Evolution (3GPP LTE) com
`25
`munication system will be schematically described.
`FIG. 1 is a schematic diagram of an Evolved Universal
`Mobile Telecommunications System (E-UMTS) network
`architecture as an example of a mobile communication sys
`tem.
`30
`The E-UMTS is an evolved version of the existing UMTS
`and basic standardization thereof is in progress under the
`3GPP. The E-UMTS is also referred to as a Long Term Evo
`lution (LTE) system.
`The E-UMTS network may be roughly divided into an
`Evolved UMTS Terrestrial Radio Access Network (E-UT
`RAN) 101 and a Core Network (CN) 102. The E-UTRAN 101
`generally comprises a terminal (i.e., User Equipment (UE))
`103, a base station (i.e., eNode B or eNB) 104, an Access
`Gateway (AG) 105 that is located at an end of the E-UMTS
`network and connects with one or more external networks.
`The AG 105 may be divided into a part for processing user
`traffic and a part for handling control traffic. Here, an AG for
`processing new user traffic and an AG for processing control
`traffic can communicate with each other using a new inter
`face.
`One eNode B may have one or more cells. An interface for
`transmitting the user traffic or the control traffic may be used
`among the eNode Bs. The CN 102 may comprise an AG 105,
`nodes for user registration of other UEs 103, and the like. An
`50
`interface may be used to distinguish the E-UTRAN 101 and
`the CN 102 from each other.
`The various layers of the radio interface protocol between
`the terminal and the network may be divided into Layer (L1),
`Layer 2 (L2) and Layer 3 (L3), based upon the lower three
`layers of the Open System Interconnection (OSI) standard
`model that is well-known in the field of communications
`systems. Among these layers, Layer 1 (L1), namely, the
`physical layer, provides an information transfer service by
`using a physical channel, while a Radio Resource Control
`(RRC) layer located in Layer 3 (L3) performs the function of
`controlling radio resources between the terminal and the net
`work. The RRC layer exchanges RRC messages between the
`terminal and the network. The RRC layer may be located by
`being distributed in network nodes such as the eNode B 104,
`the AG 105, and the like, or may be located only in the eNode
`B 104 or the AG 105.
`
`35
`
`40
`
`45
`
`55
`
`60
`
`65
`
`IPR2023-01273 Page 15
`
`

`

`US 9,078,236 B2
`
`3
`release of radio bearers. Here, a radio bearer (RB) denotes a
`logical path provided by the first and second layers of radio
`protocols for data transfer between the terminal and the
`UTRAN. Generally, configuration of the RB indicates a pro
`cess of regulating radio protocol layers and channel charac
`teristics necessary for providing a specific service, and con
`figuring specific parameters and operation methods. The RB
`is divided into a signaling RB (SRB) and data RB (DRB). The
`SRB is used as a path through which an RRC message is
`transmitted on a C-plane, while the DRB is used as a path
`through which user data is transmitted on a U-plane.
`Downlink transport channels for transmitting data from a
`network to a terminal may include a Broadcast Channel
`(BCH) for transmitting system information and a downlink
`Shared Channel (SCH) for transmitting other user traffic or
`control messages. Traffic or control messages of a downlink
`multicast or broadcast service may be transmitted either via a
`downlink SCH, or via a separate downlink Multicast Channel
`(MCH). In addition, uplink transport channels for transmit
`ting data from a terminal to a network may include a Random
`Access Channel (RACH) for transmitting an initial control
`message and an uplink Shared Channel (SCH) for transmit
`ting user traffic or control messages.
`Downlink physical channels for transmitting information
`transferred to a downlink transport channel via a radio inter
`val between a network and a terminal may include a Physical
`Broadcast Channel (PBCH) for transmitting BCH informa
`tion, a Physical Multicast Channel (PMCH) for transmitting
`MCH information, a Physical Downlink Shared Channel
`(PDSCH) for transmitting PCH information and downlink
`SCH information, and a Physical Downlink Control Channel
`(PDCCH) (also called a DLL1/L2 control channel) fortrans
`mitting control information sent from the first and second
`layers, such as downlink or uplink radio resource allocation
`information (DL/UL Scheduling Grant) or the like. Uplink
`physical channels for transmitting information transferred to
`an uplink transport channel via a radio interval between a
`network and a terminal may include a Physical UplinkShared
`Channel (PUSCH) for transmitting uplink SCH information,
`a Physical Random Access Channel (PRACH) for transmit
`ting RACH information, and a Physical Uplink Control
`Channel (PUCCH) for transmitting control information sent
`from the first and second layers, such as HARQ ACK or
`NACK, Scheduling Request (SR), Channel Quality Indicator
`(CQI) report and the like.
`The HARQ operation performed in the LTE system based
`on the above description will now be described.
`FIG. 4 is a diagram showing a HARQ operation performed
`in the LTE system.
`In FIG. 4, description will be given in an uplink state in
`which a UE is a transmission side, a base station (eNode B or
`eNB) is a reception side, and HARQ feedback information is
`received from the base station, but may be equally applied to
`downlink transmission.
`First, the eNB may transmit uplink scheduling informa
`tion, that is, uplink grant (UL grant), via a Physical Downlink
`Control channel (PDCCH), in order to enable the UE to
`transmit data using the HARQ scheme (S401). The UL grant
`may include a UE identifier (e.g., C-RNTI, semi-persistent
`scheduling C-RNTI), a location of an assigned radio resource
`(resource block assignment), a transmission parameter Such
`as a modulation/coding rate, a redundancy version and the
`like, a new data indicator (NDI), etc.
`The UE may check UL grant information sent to itself by
`monitoring a PDCCH in each Transmission Time Interval
`(TTI). In case of discovering the UL grant information sent to
`itself, the UE may transmit data (data 1 in FIG. 4) via a
`
`40
`
`45
`
`4
`physical uplink shared channel (PUSCH) according to the
`received UL grant in

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket