US010517133B2
`
`a2) United States Patent
`US 10,517,133 B2
`a0) Patent No.:
`
`(45) Date of Patent: Dec. 24, 2019
`Teyebet al.
`
`(54) METHODS AND UE FOR RESUMING A
`CONNECTION WITH FULL
`CONFIGURATION
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`2013/0039339 Al*
`
`2/2013 Rayavarapu.......... HO4W 76/19
`370/331
`2013/0260740 Al* 10/2013 Rayavarapu.......... HO4W 76/27
`455/422.1
`2013/0260810 Al* 10/2013 Rayavarapu.......... HO4W 76/19
`455/509
`2013/0260811 A1l* 10/2013 Rayavarapu.......... HO4W 76/19
`455/509
`4/2015 Kim wo. HO4W 52/0216
`370/311
`5/2015 Koo wee HO4W 76/14
`370/329
`
`2015/0117286 A1*
`
`2015/0131540 AL*
`
`(71)
`
`(72)
`
`(73)
`
`Applicant: TELEFONAKTIEBOLAGET LM
`ERICSSON (PUBL), Stockholm (SE)
`
`Inventors: Oumer Teyeb, Solna (SE); Gunnar
`Mildh, Sollentuna (SE)
`
`Assignee: Telefonaktiebolaget LM Ericsson
`(publ), Stockholm (SE)
`
`(*)
`
`Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21)
`
`Appl. No.: 16/380,844
`
`(22)
`
`Filed:
`
`Apr. 10, 2019
`
`(65)
`
`Prior Publication Data
`
`US 2019/0254102 Al
`
`Aug. 15, 2019
`
`Related U.S. Application Data
`
`(63)
`
`application
`of
`Continuation
`PCT/IB2019/050836, filed on Feb. 1, 2019.
`
`No.
`
`(60)
`
`(51)
`
`(52)
`
`(58)
`
`Provisional application No. 62/631,467, filed on Feb.
`15, 2018.
`
`Int. Cl.
`
`HOAW 76/19
`USS. Cl.
`
`(2018.01)
`
`CPC vieecccccccccsssceesecetteeessee HO4AW 76/19 (2018.02)
`Field of Classification Search
`None
`
`(Continued)
`
`OTHER PUBLICATIONS
`
`3GPP TS 36.331 V15.0.1 (Jan. 2018), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
`Resource Control (RRC); Protocol specification (Release 15), pp.
`1-776.
`
`(Continued)
`
`Primary Examiner — Otis L Thompson,Jr.
`
`ABSTRACT
`(57)
`A wireless device for resuming a connection in a commu-
`nication network. The wireless device comprises a commu-
`nication interface; and one or more processing circuits
`communicatively connected to the communication interface,
`the one or more processing circuits comprising at least one
`processor and memory, the memory containing instructions
`that, when executed, cause the at least one processor to: send
`to a network node a request to resume a connection in a
`communication network; receive a resume response mes-
`sage from the network node, the message comprising an
`indication to perform a full configuration; and apply the full
`configuration.
`
`See application file for complete search history.
`
`20 Claims, 17 Drawing Sheets
`
`PACS
`Bearer
`
`Spit
`Bearer
`
`WLOPPPORROOEDPORPLEDDIEDEPALEPDIPELIPOPDPPEELDALDPDIELADLEPDIRPOPLDPEEERELADEDEERELEDEDEDDIa,
`
`SCE
`Bearer
`
`RLC
`
`RLC
`
`ALG
`
`RLC
`
`MAC
`
`RAN
`
`]
`
`1
`
`MAS
`
`SM
`
`APPLE 1001
`
`1
`
`APPLE 1001
`
`

`

`US 10,517,133 B2
`
`Page 2
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`2015/0181461 Al*
`
`6/2015 Kim we HO4W 74/08
`370/236
`. HO4W 8/22
`6/2017 Sunel....
`2017/0188269 Al*
`
`... HO4W 24/08
`2017/0311206 A1l* 10/2017 Ryoo .
`... HO4W 76/12
`2018/0049255 AL*
`2/2018 Chen..
`
`2018/0091968 AL*
`3/2018 Ly ween HO4L 43/16
`7/2018 Kim oe. HO04W 36/0033
`2018/0213452 AL*
`8/2018 Kim oe, HO4W 68/005
`2018/0234941 AL*
`... HO4W 36/12
`2018/0270741 Al*
`9/2018 Enomoto .
`
`... HO4W 48/02
`2018/0279204 Al*
`9/2018 Kim .........
`
`... HO4L 5/0092
`2018/0359149 Al* 12/2018 Shaheen
`. HO4W 76/27
`2019/0037635 AL*
`1/2019 Guo...
`2019/0053102 Al*
`2/2019 Oohira ..
`HO4W 8/06
`2019/0053199 Al*
`2/2019 Fujishiro
`... HO4W 72/04
`4/2019 Park .........
`.. HO4W 76/27
`2019/0124572 Al*
`
`7/2019 Fujishiro ..
`2019/0215800 Al*
`. HO4W 8/08
`7/2019 Burbidge .
`... HO4W 48/14
`2019/0215887 Al*
`
`8/2019 Jeon we HO04W 36/0069
`2019/0254074 AL*
`
`
`
`OTHER PUBLICATIONS
`
`Ericsson, Offline#22 LTE re-establishment and resume while using
`NR PDCP, 3GPP TSG-RAN WG? Meeting #100, Reno, US, Nov.
`27-Dec. 1, 2017, pp. 1-12.
`
`* cited by examiner
`
`2
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 1 of 17
`
`US 10,517,133 B2
`
`O25wasOE
`
`SRLEBYAOLsaneagg
`
`Jwns
`
`3
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 2 of 17
`
`US 10,517,133 B2
`
`dodd
`
`fa
`
`S
`
`ASSRSSSR
`
`“NemcreoceccrococccecreoripeeccoecceoceececceeceeocecceececccempeoceoceccoocoeoceceecocoeoriabiTbeTitTereertebetittirennet
`
`
`
`
`ReenareePerereePePOPOEPELOLOEPELELOEPELOLOEPELELOLLELELEEPELELOLPELELOLPETRIOLPELELELPELELELPELELOLLELELULPELRAILLELELELLELEDDIDE
`
`AME
`
`OOWSOW
`
`
`
`HasLBLEOG
`
`AAALACKALKIRRRKEKEERLELRURKEKEURKELRRRRKERRRRRKERRRRRKERN
`
`
`
`
`
`SSSR,
`
`LTNCACAOAAOEAALEAUNEAUDTAODTADLAALLAUDLAUDEAUDEAUDEAUDTOULTALLTULLTULLTUDLTUDEAUDEOUDEOUDTULLTULLTUDLAUDLAUEAHOEAbapa,NS
`
`POPOOOPLOLEDDPLOLEDEPLOLEDLOLEDEDLOLODEDLOLODEDLELODEDLOLEDEDLOLEDEDLELEDEDLOLELEDLOLEDEDLELEDEDLELEDEDLOLEDEDLOLEDEDLOLEDEDDTLaa
`‘, oie
`
`ZaS
`
`4
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 3 of 17
`
`US 10,517,133 B2
`
`rane
`
`“onMn
`%neanwvnne>ODAOS¥
`
`yes
`
`AAR
`
`gececececcececessacetebeststbesssMrisitth, iiTEAS:HiLcccccecercecersecercecercecerseemgrecesseede
`
`PaaaaeaaeaaaaaaafjtMattyeBE3gBCEALY3i3iZ%OAMAhhdbdbhhhdhhhdedhdhdhatthe
`
`[(LPPPPPPPPPPPPPPPPPPPPPPPPLLEPEPPAEEAPEEEDA
`
`NellhellehhellelhiidhhhhdilhdddeSs
`
`jporcecsBivestterrererererererMarererercerey“
`
`aigB24hee
`
`Rwanananns
`
`%
`
`$...%.
`
`3Arent
`
`;
`
`aR:
`"ee,
`
`
`
`SPOCOOPLIPELLLLOILIDEELLLDILIDELLODOIIEDIEEE:;aFEBBH
`
`Mee,
`
`
`
`naan
`sont
`
`avy Pav vBSNESESBENSNARES
`
`AY
`
`A
`
`¢INSIY
`
`GOORSHEEAMEAEEE
`
`$#
`
`“*
`
`geernecceetBerrerrenerrrireeeeeentrrrrdeneniy
`
`
`
`
`
`:rr4:;é3iZ3;$3;$3;$:3gZ:3gZ%Abewe
`
`Snes
`
`sececccdgescccacaersiaededt
`
`yprrecencwrateBenleletPePOLELPOPOLELPEPEPELtlh,
`
`TeEOEeeKWH,
`
`sbo
`
`eecvccecsceggecccagececccecscecseccteigiioed.
`
`SSNs
`
`z3apeererorerorerereororereororeerorerereerey
`
`SBABH
`
`SEASASAAS
`
`
`
`pesccssecsrebicsttbbesceesceeseeeseeesBeste,
`
`4%
`
`FBSS
`
`pevecccdcdevecdediapededicecdigececdedsagededs
`
`OFaeywmSo
`
`SAAS!
`
`
`
`PeatCALOLILNilCIOLELIAANASALAINLAehbbb
`
`
`
` e ¥3222g$fgMagsZ;tetan"5$pgahsZ“or:ZFEES3gFCSBY¢Zz;$Zt2Aa
`
`woenthghessesssnsssysatin
`ewes
`
`
`
`5
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 4 of 17
`
`US 10,517,133 B2
`
`SRNANANANANADAANS
`
`MEBOS SRNAAANAAAAAANNNS
` JO0dapifSdUN
`
`OVADOW
`
`SRNANAASANANADNANS
`
`SORNANAASANAEAANANS
`
`SSNNANASSANANADIAD
`
`AEEEXIS
`
`
`
`ABTSSHOROVE
`
`pons]
`
`
`
`RiRo6160aioenEo>+(eso10Ne)hoyAino?,
`
`6
`
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 5 of 17
`
`US 10,517,133 B2
`
`EUTRAN
`
`RRCConnectionReestablishmentRequest
`
`
`
`
`
`RRCConnectionReestablishment
`
`
`
`RRCConnectionReestablishmentComplete
`
`Figure 5
`
`EUTRAN
`
`
`
`
` RRCConnectionReestablishmentRejec
`
`RRCConnectionReestablishmentRequest
`
`Figure 6
`
`7
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 6 of 17
`
`US 10,517,133 B2
`
`RRCConnectionResumeRequest
`
`
`
`RRCConnectionResume
`
`
`
`RRCConnectionResumeComplete
`
`Figure 7
`
`
`
`RRCConnectionResumeRequest
`
`
`
`RRCConnectionSetup
`
`
`
`RRCConnectionSetupComplete
`
`Figure 8
`
`
`
`RRCConnectionResumeRequest
`
`
`
`Figure 9
`
`RRCConnectionRejec
`
`8
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 7 of 17
`
`US 10,517,133 B2
`
`
`
`
`
`
`
`
`
`MOSdWA
`
`
`
`
`
`
`
`
`
`
`
`
`
`0001A
`
`
`
`SADIBVGSSBIYBSI|SY:O€OT‘
`
`
`
`
`
`f\J/¥
`
`
`ysanbay
`
`
`
`
`
`puadsng1xay009FN‘dW-LS‘OZO]
`
`
`
`BYEP“TN
`
`Byep“1d
`
`
` {NO‘OLOT
`puodsns0}sopisap
`VORWUUODDWy2G}
`
`
`
`
`
` asuodsoy\.puadsne¢1x800DANcdV-1S‘Or0l
`
`SESSYUOTSUTY
`
`
`
`(CJounsal‘asne7yaseajol)
`
`‘0S01
`
`OFansiy
`
`
`
`
`|
`purPsrO}sX99SYAN‘0901
`
`AN‘papusdsnssepapursqus
`
`
`
`
`
`WIGOwessoiua
`
`NeAn
`
`
`
`
`
`
`
`
`
`9
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 8 of 17
`
`US 10,517,133 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`gsuodsoyounsay3X9}007)OQidV-1S
`
`‘06H
`
`Tpamar
`
`
`
`
`
`ysanboyotunsayIxaqu0aAAidW-1S
`
`‘OLIT
`
`
`
`qopduro7youinseyuoIUUOMY.
`
`“O91
`
`asuodsayssasoy
`
`
`Wwopuey“OCTT
`
`quinsoyuoNa
`TUONOOCT
`
`jsonbay,
`
`
`
`DWMNSTYBOONIAULOITY‘OFLT
`
`Gunoj8uruinyjdopixeu)
`
`
`
`
`
`
`SVpurpoutnsalsepapueSEAS“OSTI
`
`
`
`SIoTUSTry“poysiyqeisa-asAymnoes
`
`
`COELOINNODOWY
`
`10
`
`
`
`
`
`
`
`eine
`
`OOLTA
`
`
`
`
`
`
`
`qn.
`
`
`
`
`
`
`
`afquiRaigssaoaywopury‘OT!
`
`10
`
`
`
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 9 of 17
`
`US 10,517,133 B2
`
`
`
`MOS
`
`
`
`
`
`aA
`
`
`
`
`
`
`
`
`
`
`
`
`HN?PIO
`
`
`
`
`
`INS“ON
`
`
`
`00TIA
`
`
`
`
`
`
`
`aa
`
`
`
`
`
`
`
`MOVIonboyyopMSWe"<AV-1S
`
`BIeP“TL
`
`vrep“TC
`
`
`
`OSBOPOY-O9T1
`
`ZIounsry
`
`
`
`isanbayYOHMAMSWed‘AV-1S
`
`"$Gel
`
`2
`1c|
`
`syodtuojournsayuonIedUODYY
`
`‘OFCI
`
`
`
`SAOUIOA“OCT
`
`
`
`aUINSAYVOHIUAGIBY“SIZI
`
`ysanboxy
`
`
`asuodsayS77]
`AUINSIYUOTIIVUODPY“OLT1
`
`(Funosurureyjdopyxou)
`
`
`
`
`
`
`SVpurpauinsarSgyC]purSUAS“S¢TI
`
`
`
`
`SIdWU9YP)[poysyjqwisa~arAyumoas
`
`
`
`C3ILOANNODOWA
`
`11
`
`
`
`
`
`ajGUILAIYSsaodyWopuey‘SOZ]
`
`
`
`
`
`
`
`qsuodsayssaoayWOpUeY“O1Z|
`
`11
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 10 of 17
`
`US 10,517,133 B2
`
`~
`°
`3
`SSSESSERESSRERSS:
`:
`XK
`worth
`
`bite
`Teer
`
`ee
`=
`4
`RY wn
`s
`SHY
`=
`fonnenn:
`
`
`gennnennenannsnnennnnnnnsnag
`oe
`z
`tees
`we
`s
`s
`Se
`3
`Ronmennnnngannnnnnnt
`C
`
`+N
`
`4444444444444444444444444444
`Mes
`
`enrol
`
`S
`
`
`
`>
`
`:
`
`‘
`
`sx=
`
`=<
`
`xx
`
`
`
`%$3333333333
`
`*RRSSLES
`
`SASSSSSASSSSSSSSSSSSSSN
`
`
`anit,¥zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
`zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzZz
`g%
`
`
` AX RE RE A ARON EAee
`seeneveg:
`
`
`
`aSOOOVPELOVVLELELUTED
` Yorn
`
`%<Sx=====
`
`SSSOQVSN
`
`SinOCCURS
`
`ee
`sthent
`SASS
`
` te,
`AT {EAN 2
`OOMNAHHNHNAHHNANNANNANAHNNNTNNNANNNANTNANTNN
`FSSAEAASSSR CSCSSA
`eteeeeededetin,
`z22223
`
`
`
`
`
`
`
`
`
`
`xxxxxxx
`
`<
`x
`
`Sx
`g
`
`S
`a
`
`x>
`=
`
`Figure 13
`
`12
`
` AOMOAAAAOLAEAIALEAIPOLDEAEAOEOELIAOEOELIAOEOELIAILOELIPOLOELIAITOELIAOEDELEPOEOELEPOEOELIAOLOELIPISOELEPESOELIASELEPESOEDEPSDEDEDE
`
`
`
`
`
`
`
`
`
`
`
` vanetaggrodTisveetedddriest:
`
`SSNSASASAASSSSSSSSNSSAASSRASASASSASSSNSSASSRASSANSSSSSASSRSRASSSSASSSSSSR
`2:
`z
`=
`¥
`x
`x
`x
`g
`=
`SheenaeeeeeeENR
`=
`z
`g
`x.
`
`3SLTY
`3
`¥
`s
`S
`Seereneeenegeeteneenessesener
`g
`=
`mt
`g
`3
`>
`=
`x
`3
`:
`g
`z
`AS
`g
`3
`3%
`s
`S
`¢
`3
`x
`
`sxxx
`x
`g
`S
`N
`x
`g
`z
`g
`S
`x
`is
`3
`cree:
`SERED
`oS
`k
`OS aan
`Ssh
`3
`g
`3
`:
`SA
`SEES
`S38
`S
`y 8
`z
`SARS
`3
`<
`S
`Siisesennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
`x
`g
`S
`S
`x
`
`12
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 11 of 17
`
`US 10,517,133 B2
`
`0:
`0¢
`
`
`
`YIOMJBNSUIPSUUOIIa}y|
`
`OEZ
`
`YIOMIBNB09
`
`O”ZBPON
`
`13
`
`plonshy
`
`13
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 12 of 17
`
`US 10,517,133 B2
`
`a 300
`
`receiving, from a wireless device, a request to resume a
`connection in a communication network
`305
`
`based on the request, retrieving configuration information for
`the wireless device
`
`310
`
`320
`
`in response to determining that the retrieved configuration
`information is unidentifiable, generating new configuration
`parameters
`315
`
`sending a resume response message to the wireless device, the
`message comprising an indication to perform a full
`configuration using the new configuration parameters
`
`Figure 15
`
`14
`
`14
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 13 of 17
`
`US 10,517,133 B2
`
`a 330
`
`Receiving, from a wireless device, a request to resume a
`connection in a communication network
`335
`
`In response to the request, sending a resume response message
`to the wireless device, the message comprising an indication to
`perform a full configuration
`
`340
`360
`
`Figure 16
`
`Sending to a network node a request fo resume a connection in
`the communication network
`355
`
`Receiving a resume response message from the network node,
`the message comprising an indication to perform a full
`configuration
`
`Figure 17
`
`15
`
`15
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 14 of 17
`
`US 10,517,133 B2
`
`a 370
`
`receiving, from a wireless device, a request to resume a
`connection in a communication network
`375
`
`385
`
`based on the request, retrieving configuration information for
`the wireless device; wherein the configuration information is
`adapted from a source network node to the network node so as
`te be usable by the network node
`380
`
`sending a resume response message to the wireless device to
`resume the connection based on the adapted configuration
`information
`
`Figure 18
`
`16
`
`16
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 15 of 17
`
`US 10,517,133 B2
`
`220
`
`Processing
`Circuitry 410
`
`Processor(s)
`
`Network
`interface
`
`430
`Network node 2206
`
`Transceiver(
`s) 420
`
`Figure 19
`
`Figure 20
`
`17
`
`17
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 16 of 17
`
`US 10,517,133 B2
`
` |
`
`|
`||
`|
`|
`|
`eee Rx({s} 660
`
`Processing Circuitry 610
`Memory 630
`Processor(s)
`
`620
`
`Transceiver(s)
`Tx(s} 650
`
`Figure 21
`
`Wireless device 210
`
`Modules 700
`
`Figure 22
`
`18
`
`18
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 17 of 17
`
`US 10,517,133 B2
`
`00ZE0DiApiarypoceedpay
`
`
`Jnateeee,|sezeoo!1|gaaasayiLMHGEEOO||rhsp|_OFEEDDnySUyunopeyiJade]
` |I|!;o¢zeoo|4A3Pennefj(sJeunauyfcINDBuissav0idO9EDO
`
`(sjeuuaiuy|WAoreDD||WAOYEDD|G@ZEDD|wTL7NU7BOUR
`
`uOHeZ|ENUlAOSEDD
`ISU]/JAASJOBPOU[ENA/sueldde
`
`jena/uonenjddy
`OSEODidecweonenoeJpueeeeLyTTT1“}WAOPEOD1;WAOPEDD|
`paregrresaesosiHliwiddyqoddy4iiaze00
`Jade}uonezenulA
`
`OZEDD
`
`a>=aQo
`
`O
`ny
`og
`oO
`me one srwo
`
`a-—-——-l
`
`OFZEDD
`
`
`
`WaySAS[OuWUOD
`
`S6EDD|aeeeeJade1ojys
`en7j“Asuy
`
`
`
`AjoysueuON7-C6E00
`
`€7IANS
`
`
`
`oo|S6E0D|MOWayyT-O6EDO
`
`
`
`IN[221sA4dOBEDD
`
`JINOLEDOD
`
`non mee ome teen
`
`Zz
`
`%2w
`
`008
`
`OZEOD
`
`OZEDD
`
`uoneoyddy
`
`iMHOEEDD|Boon
`wwsateSorettttutratsrStudWhatSnWr,
`
`}{}{}{}{jj{}{}
`
`pue{juauadeuryy|
`
`ooreOD
`
`uonelsaysso
`
`19
`
`I{j{}{}{}{jj|}{}
`
`19
`
`
`
`
`

`

`US 10,517,133 B2
`
`1
`METHODS AND UE FOR RESUMING A
`CONNECTION WITH FULL
`CONFIGURATION
`
`RELATED APPLICATIONS
`
`The present application is a continuation of International
`Application Ser. No. PCT/IB2019/050836,
`filed Feb. 1,
`2019, entitled “Methods and UE for resuming a connection
`with full configuration” which claims priority to and the
`benefit of the filing of U.S. Provisional Patent Application
`No. 62/631,467, entitled “RRC Resume with Full Configu-
`ration’, and filed at the United States Patent and Trademark
`Office on Feb. 15, 2018, all of which are incorporated herein
`by reference in their entireties.
`
`TECHNICAL FIELD
`
`2
`whereby a multiple Receive/Transmit (Rx/Tx) UE in RRC_
`CONNECTEDis configured to utilize radio resources pro-
`vided by two distinct schedulers,
`located in two eNBs
`connected via a non-ideal backhaul over the X2 interface
`
`(see 3GPP 36.300). eNBs involved in DC for a certain UE
`may assume twodifferent roles: an eNB mayeither act as an
`Master node (MN)or as an Secondary node (SN). In DC, a
`UE is connected to one MN and one SN.
`
`In LTE DC,the radio protocol architecture that a particu-
`lar bearer uses depends on how the bearer is setup. Three
`bearer types exist: Master Cell Group (MCG) bearer, Sec-
`ondary Cell Group (SCG) bearer and split bearers. RRC is
`located in MN and SRBs are always configured as a MCG
`bearer type and therefore only use the radio resources of the
`MN.FIG.1 illustrates the LTE DC User Plane (UP), with the
`3 types of bearers in a UE.
`
`15
`
`The present description generally relates to wireless com-
`munications and, more particularly, to resume a connection
`for a wireless device.
`
`20
`
`BACKGROUND
`
`Radio Resource Control (RRC) Protocol
`
`As in Long Term Evolution (LTE), the Radio Resource
`Control
`(RRC) protocol
`is used to configure/setup and
`maintain the radio connection between the User Equipment
`(UE) and the network node (e.g. eNB). When the UE
`receives an RRC message from the eNB, it will apply the
`configuration (the term “compile” can be also used to refer
`to the application of the configuration). And if this succeeds,
`the UE generates an RRC complete message that indicates
`the transaction identity (ID) of the message that triggered
`this response.
`Since LTE-release (rel.) 8, three Signaling Radio Bearers
`(SRBs), namely SRBO, SRBland SRB2have been available
`for the transport of RRC and Non Access Stratum (NAS)
`messages between the User Equipment (UE) and eNB. A
`new SRB, known as SRB1bis, was also introducedin rel-13
`for supporting DoNAS (Data Over NAS) in Narrowband
`Internet of Things (NB-IoT).
`SRBO is used for RRC messages using the Common
`Control Channel (CCCH)logical channel, andit is used for
`handling RRC connection setup, RRC connection resume
`and RRC connection re-establishment. Once the UE is
`
`connected to the eNB (i.e. RRC connection setup or RRC
`connection reestablishment/resume has succeeded), SRB1 is
`used for handling RRC messages (which may include a
`piggybacked NAS message) as well as for NAS messages
`prior to the establishment of SRB2, all using Dedicated
`Control Channel (DCCH)logical channel.
`SRB2 is used for RRC messages which include logged
`measurement information and for NAS messages, all using
`DCCH logical channel. SRB2 has a lower priority than
`SRB1, because logged measurement information and NAS
`messages can be lengthy and could cause the blocking of
`more urgent and smaller SRB1 messages. SRB2 is always
`configured by Evolved-Universal Mobile Telecommunica-
`tions Service (UMTS) Terrestrial Radio Access Network
`(E-UTRAN)after security activation.
`
`Dual Connectivity (DC) in LTE
`
`Evolved-UMTS Terrestrial Radio Access Network
`
`(E-UTRAN) supports Dual Connectivity (DC) operation
`
`25
`
`40
`
`45
`
`LTE-NR Dual Connectivity
`
`LTE-NR (LTE-New Radio) DC (also referred to as LTE-
`NR tight
`interworking) is currently being discussed for
`rel-15. In this context, the major changes from LTE DCare:
`The introduction of split bearer from the SN (knownas
`SCGsplit bearer);
`The introduction of split bearer for RRC;
`The introduction of a direct RRC from the SN (also
`referred to as SCG SRB).
`FIGS. 2 and 3 show the UP and Control Plane (CP)
`architectures respectively for LTE-NRtight interworking.
`The SN is sometimesreferred to as SgNB (where gNBis
`an NRbasestation), and the MN as MeNBin case the LTE
`is the master node and NRis the secondary node. In the other
`case where NRis the master and LTEis the secondary node,
`the corresponding terms are SeNB and MgNB.
`Split RRC messages are mainly used for creating diver-
`sity, and the sender can decide to either choose one of the
`links for scheduling the RRC messages, or it can duplicate
`the message over both links. In the downlink,
`the path
`switching between the MCG or SCGlegsor duplication on
`both is left to network implementation. On the other hand,
`for the UL, the network configures the UE to use the MCG,
`SCG or both legs. The terms “leg” and “path” are used
`interchangeably throughout this document.
`The following terminologies are used throughout this
`disclosure to differentiate different dual connectivity sce-
`narios:
`DC: LTE DC (i.e. both MN and SN employ LTE);
`EN-DC: LTE-NR dual connectivity where LTE is the
`master and NR is the secondary;
`NE-DC: LTE-NR dual connectivity where NR is the
`master and LTE is the secondary;
`NR-DC (or NR-NR DC): both MN and SN employ NR;
`MR-DC (multi-RAT DC): a generic term to describe
`where the MN and SN employ different Radio Access
`Technologies (RATs), EN-DC and NE-DC are two different
`example cases of MR-DC.
`
`Bearer Harmonization in EN-DC
`
`In Radio Access Network 2 (RAN2), it has been agreed to
`harmonize what was former called MCG bearers, MCGsplit
`bearers, SCG bearers and SCG split bearers in the following
`way:
`a) It is possible to configure the UE to use NR Packet Data
`Convergence Protocol (PDCP) for all
`the bearers (even
`when the UE is operating in standalone LTE mode and
`EN-DCis not setup);
`20
`
`65
`
`20
`
`

`

`US 10,517,133 B2
`
`3
`b) For all bearers configured with NR PDCP,it is possible
`to configure the UE to either use KeNB or S-KeNB as
`security key;
`c) The configuration of the PDCPlayersis separated from
`the configuration of the lower layers of the MCG and SCG
`leg.
`From a UE point of view, this means that there are only
`3 different bearers (as can be seen in FIG. 4) namely the:
`d) MCGbearer which usesthe radio link towards the MN
`node only;
`e) SCG bearer which uses the radio of the SN node only;
`f) And the split bearer which uses the radio of both the
`MN andSN.
`Where these bearers are terminated in the network is not
`
`important from the UE’s perspective anymore, i.e. the UE
`will just use the key that is being configured from each
`bearer. From a RAN2point of view it is fully supported to
`setup MCGbearers being terminated in the SN node using
`S-KeNB and SCGbearers being terminated in the MN node.
`Sunilarly, it is possible to support both SN and MN termi-
`nated bearers at the same time i.e. both SN terminated split
`bearers and MN terminatedsplit bearers.
`
`LTE Re-Establishment Procedure
`
`The purpose of the LTE re-establishment procedureis to
`re-establish the RRC connection upon detecting radio link
`failure, handover failure, mobility from E-UTRA failure,
`integrity check failure on SRBs or RRC connection recon-
`figuration failure. Re-establishment involves the resumption
`of SRB1, the re-activation of security and the configuration
`of only the Primary cell (PCell), i.e. Carrier Aggregation
`(CA) or DC operations are not re-established.
`When the target eNB gets a re-establishment request, it
`identifies the source eNB/cell from the ReestabUE-Identity
`included in the request and can send a Radio Link Failure
`(RLF) Indication X2 message to the source eNB. The source
`eNB may respond with a Handover Request message that
`includes the UE context (RRC context and $1 context). If
`the target eNB is able to understand the UE context, re-
`establishment succeeds and the target eNB sends an RRC-
`ConnectionReestablishment message to the UE. If thetarget
`eNB does not receive the UE context or it doesn’t under-
`
`stand the context, it may reject the re-establishment and the
`UEhasto go to RRC_IDLEto re-connect.If the target eNB
`doesn’t understand the RRC context but can understand the
`S1 context, it doesn’t necessarily reject the re-establishment
`and can still respond with RRCConnectionReestablishment
`and later use full reconfiguration to reconfigure the bearers
`based on the $1 context.
`
`In case of a re-establishment success, SRB1 operation
`resumes while the operation of other radio bearers (SRB2
`and DRBs) remains suspended. If Access Stratum (AS)
`security has not been activated, the UE does notinitiate the
`procedure but instead moves to RRC_IDLEdirectly.
`E-UTRANapplies the re-establishment procedureas fol-
`lows:
`
`When ASsecurity has been activated:
`reconfigure SRB1 and resume data transfer only for this
`Radio Bearer;
`re-activate AS security without changing algorithms.
`After this, the UE sends the RRCConnectionReestablish-
`mentComplete message, and the target eNB responds by
`sending an RRCConnectionReconfiguration message to
`reconfigure SRB2 and the DRBs.
`The RRC connection re-establishment procedure flow is
`shown in FIG. 5 (success case) and FIG.6 (failure case).
`
`4
`SRBOis used for sending the RRCConnectionReestablish-
`mentRequest, RRCConnectionReestablishment and RRC-
`ConnectionReestablishementReject messages, while RRC-
`ConnectionReestablishmentComplete uses SRB1.
`
`LTE Suspend/Resume Procedure
`
`The RRC suspend/resume functionality has been intro-
`duced in LTE rel-13. A suspended UE can be considered to
`be in an intermediate state between IDLE and CON-
`
`10
`
`NECTED, where the UE AS context is kept both at the UE
`and RAN, and the UE can beseen asif it is in connected
`mode but suspended from the Core Network (CN) point of
`view and in IDLE mode from the RAN point of view. The
`advantage of operating in this modeis reduced signaling and
`faster transition to CONNECTED mode as compared to
`legacy IDLE-CONNECTED modetransitions, while main-
`taining the UE power saving advantages of IDLE mode.
`When a decision is made by the network to move the UE
`to suspendedstate, the eNB sends the UE an RRCConnec-
`tionRelease message with the release cause value of rre-
`suspend. The RRCConnectionRelease message also con-
`tains a Resume ID. The UEstores the Resume ID and UE AS
`
`context (including the current RRC configuration, the cur-
`rent security context,
`the PDCP state including Robust
`Header Compression (ROHC) state, Cell-Radio Network
`Temporary Identifier (C-RNTI) used in the source PCell, the
`cell Identity (cellID) and the physical cell identity of the
`source PCell); re-establishes all Radio Link Control (RLC)
`entities (both for SRBs and DRBs); and suspends all DRBs
`and SRBs except SRBO.
`Whenthe UElater on wants to resume the connection (in
`response to UL data to be sent or a paging request for DL
`data), it sends an RRCConnectionResumeRequest message
`with the saved Resume ID. If the resume operation is
`performed in an eNBother than the eNBthat wasserving the
`UE whenthe UE was suspended, the new eNB can perform
`a context fetch by using the Retrieve UE Context X2
`procedure from the old eNB (as the Resume ID includes
`information about the old eNB/cell). Upon getting the con-
`text (if resuming on a new eNB)or if the resumption was in
`the same eNB, the target eNB responds with an RRCCon-
`nectionResume message, and both the UE and eNBrestore
`the saved UE context, and data transmission/reception from/
`to the UE can be resumed.
`
`The RRC connection resume procedure flow is shown in
`FIG.7 (success case) and FIG.8 (fallback to RRC connec-
`tion establishment). FIG. 9 (network reject or release) shows
`the resume procedure in LTE. SRBOis used for sending the
`RRCConnectionResumeRequest,
`RRCConnectionSetup
`and RRCConnectionReestablishementReject, while RRC-
`ConnectionResume and RRCConnectionResume Complete
`messages use SRB1.
`The main difference between resume and re-establish-
`
`ment is (from a procedural perspective): SRB1 is used for
`the RRCConnectionResume message, while SRBO is used
`for the RRCConnectionReestablishment message.
`The RRCConnectionResume message, unlike the RRC-
`ConnectionReestablishement message, can contain the
`SRB2/DRBconfiguration, and thus RRCConnectionRecon-
`figuration is not needed after resume (while it is necessary
`in the re-establishment case to reconfigure SRB2/DRBs).
`The detailed RRC connection suspend procedure 1000 is
`illustrated in FIG. 10.
`
`More specifically, in step 1010 of FIG. 10, due to some
`triggers, e.g. the expiry of a UE inactivity timer, the eNB
`decides to suspend the RRC connection.
`
`25
`
`30
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`21
`
`21
`
`

`

`US 10,517,133 B2
`
`5
`In step 1020, the eNB initiates the S1-Application Pro-
`tocol (AP) UE Context Suspend procedure to inform the
`Mobility Management Entity (MME) that the RRC connec-
`tion is being suspended. To do so, the eNB sends a UE
`context Suspend Request. As a note, S1 refers to the inter-
`face between the eNB and the core network.
`
`In step 1030, the MME requests the Serving-Gateway
`(S-GW)to release all S1-U bearers for the UE. The $1-U
`refers to the S1 user plane and the S1-U bearers are the
`bearers that carry user data between the eNB and the core
`network.
`
`In step 1040, the MME Acknowledges step 1020. For
`example, the MMEsends a response to the request of step
`1020.
`
`In step 1050, the eNB suspends the RRC connection by
`sending an RRCConnectionRelease message with the
`releaseCause set to rrc-Suspend, to the UE. The message
`includes the resumeldentity which is stored by the UE.
`In step 1060, the UE stores the AS context, suspendsall
`SRBs and DRBs. The UE enters the RRC_IDLE light
`connectedstate.
`Whenthe UElater on wants to resume the connection (in
`response to UL data to be sent or a paging request for DL
`data), it sends an RRCConnectionResumeRequest message
`with the saved resumeldentity. The eNB responds with an
`RRCConnectionResume message, and both the UE and eNB
`restore the saved UE context, and data transmission/recep-
`tion from/to the UE can be resumed. Note that the resume
`operation can be performed in an eNBother than the eNB
`that was serving the UE when the UE wassuspended. In that
`case, the new eNB can perform a contextfetch e.g. by using
`the Retrieve UE Context procedure from the old eNB (as the
`resumeldentity includes information about the old eNB/
`cell).
`The RRC connection resume procedure in the same eNB
`and new eNBareillustrated in FIGS. 11 and 12, respec-
`tively.
`FIG. 11 illustrates a RRC connection resume procedure
`1100 in the same eNB.
`
`In step 1110, the UE sends a Random Access Preamble to
`the eNB, in order to access the network.
`In step 1120,
`the eNB replies by sending a Random
`Access Response,to confirm that the UE is connected to the
`network node (eNB).
`In step 1130 of FIG. 11, at somelater point in time (e.g.
`when the UE is being paged or when new data arrive in the
`uplink buffer) the UE resumes the connection by sending an
`RRCConnectionResumeRequest to the eNB. The UE may
`include its Resume ID, the establishment cause, and authen-
`tication token. The authentication token is calculated in the
`same way as the short Message Authentication Code-Integ-
`rity (MAC-I) used in RRC connection re-establishment and
`allows the eNBto verify the UE identity.
`In step 1140, provided that the Resume ID exists and the
`authentication token is successfully validated,
`the eNB
`responds with an RRCConnectionResume. The message
`includes the Next Hop Chaining Count (NCC) value which
`is required in order to re-establish the AS security.
`In step 1150, the UE resumes all SRBs and DRBs and
`re-establishes the AS security. The UE is now in RRC_CO-
`NNECTED.
`
`In step 1160, the UE responds with an RRCConnection-
`ResumeComplete confirming that the RRC connection was
`resumed successfully.
`In step 1170, the eNBinitiates the $1-AP Context Resume
`procedure to notify the MME about the UEstate change.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`In step 1180, the MMErequests the S-GWto activate the
`S1-U bearers for the UE.
`
`In step 1190, the MME acknowledges step 1170.
`FIG.12 illustrates the RRC resumeprocedure 1200 in an
`eNB different from the source eNB where the UE got
`suspended.
`Steps 1205 to 1215 are the sameas steps 1110 to 1130 in
`FIG. 11.
`
`In step 1220 (X2-AP: Retrieve UE Context Request), the
`new eNBlocates the old eNB using the Resume ID and
`retrieves the UE context by means of the X2-AP Retrieve
`UE Context procedure.
`In step 1225 (X2-AP: Retrieve UE Context Response),
`the old eNB responds to the new eNB with the UE context
`associated with the Resume ID.
`
`In step 1230, it is the same step as step 1140 of FIG. 11
`(in the intra eNB connection resumption).
`In step 1235, it is the same step as step 1150 of FIG. 11
`(in the intra eNB connection resumption).
`In step 1240, it is the same as step 1160 of FIG. 11 (in the
`intra eNB connection resumption).
`In step 1245, the new eNBinitiates the S1-AP Path Switch
`procedure to establish a S1 UE associated signalling con-
`nection to the serving MMEand to request the MMEto
`resume the UE context.
`In step 1250, the MMErequests the S-GW to activate the
`S1-U bearers for the UE and updates the downlink path.
`In step 1255, the MME acknowledges step 1245.
`In step 1260 (X2-AP: UE Context Release), after the
`S1-AP Path Switch procedure, the new eNBtriggers release
`of the VEcontext at the old eNB by means of the X2-AP UE
`Context Release procedure.
`The resume procedure is an opportunistic procedure in
`that there may be cases where the RAN node does not have
`the stored UE context. In this case, it has been specified a
`solution enabling the RAN to recover the UE context by
`using the RRC connection setup procedure which involves
`UEsignalling to the CN and then the CN rebuilding the UE
`context in the RAN. The RRC procedure for this is shown
`in FIG.8. In FIG. 13, a more detailed procedure is shown for
`this case. This case could also be referred to as using NAS
`recovery ortransitioning via IDLE (since the UE AScontext
`is removed). FIG. 13 is known intheart, as such, it will not
`be described further.
`
`Full RRC Configurations in LTE
`
`In LTE, during a Handover (HO)orre-establishment, the
`UEcontext is passed from the source to the target eNB. If
`the target eNB does not understand any part of the UE
`configuration, then it triggers full configuration. The full
`configuration procedure is specified in Third Generation
`Partnership Project Technical Specification (3GPP TS)
`36.331 section 5.3.5.8 as below.
`The UEshall:
`1> release/clear all current dedicated radio configurations
`except the MCG C-RNTI, the MCGsecurity configuration
`and the PDCP, RLC, logical channel configurations for the
`RBs and the logged measurement configuration;
`NOTE1: Radio configuration is not just the resource con-
`figuration but includes other configurations like MeasConfig
`and OtherConfig.
`1> if the RRCConnectionReconfiguration message includes
`the mobilityControlInfo:
`2> release/clear all current common radio configurations;
`2> use the default values specified in 9.2.5 for timer T310,
`T311 and constant N310, N311;
`
`22
`
`22
`
`

`

`US 10,517,133 B2
`
`7
`
`1> else:
`2>use values for timers T301, T310, T311 and constants
`N310, N311,
`as
`included in ue-TimersAndConstants
`received in SystemInformationBlockType2 (or SystemInfor-
`mationBlockType2-NB in NB-IoT);
`1>apply the default physical channel configuration as speci-
`fied in 9.2.4;
`1>apply the default semi-persistent scheduling configuration
`as specified in 9.2.3;
`1>apply the default MAC main configuration as specified in
`9.2.2;
`1>if the UE is a NB-IoT UE; or
`1>for each srb-Identity value included in the srb-ToAdd-
`ModList (SRB reconfiguration):
`2>apply the specified configuration defined in 9.1.2 for
`the corresponding SRB;
`2>apply the corresponding default RLC configuration for
`the SRB specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for
`SRB2;
`2>apply the corresponding default logical channel con-
`figuration for the SRB as specified in 9.2.1.1 for SRB1 or in
`9.2.1.2 for SRB2;
`NOTE 2: This is to get the