U8010517133B2
`
`(12) Un1ted States Patent
`(10) Patent No.:
`US 10,517,133 B2
`
`Teyeb et al.
`(45) Date of Patent:
`Dec. 24, 2019
`
`(54) METHODS AND UE FOR RESUMING A
`CONNECTION WITH FULL
`CONFIGURATION
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`(71) Applicant‘ TELEFONAKTIEBOLAGET LM
`'
`ERICSSONQUBL): 30014101111613)
`
`(72)
`
`Inventors: Oumer Teyeb, Solna (SE); Gunnar
`Mildh, Sollentuna (SE)
`
`(73) 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.
`
`2/2013 Rayavarapu .......... H04W 76/19
`2013/0039339 A1*
`370/331
`2013/0260740 A1* 10/2013 Rayavarapu .......... H04W 76/27
`455/422.1
`2013/0260810 A1* 10/2013 Rayavarapu .......... H04W 76/19
`455/509
`2013/0260811 A1* 10/2013 Rayavarapu .......... H04W 76/19
`_
`455/509
`4/2015 Klm .................. H04W 52/0216
`370/311
`
`2015/0117286 A1*
`*
`
`2015/0131540 A1
`
`5/2015 K00 """"""""""" P10429329:
`(Continued)
`
`(21) Appl. No.: 16/380,844
`
`(22)
`
`Filed:
`
`Apr. 10, 2019
`
`(65)
`
`Pr10r Publlcatlon Data
`US 2019/0254102 A1
`Aug. 15, 2019
`
`Related US. Application Data
`(63) Continuation
`of
`application
`PCT/IB2019/050836 filed On Feb 1 2019
`’
`’
`
`No.
`
`(60) Provisional application No. 62/631,467, filed on Feb.
`15, 2018.
`
`(51)
`
`(201801)
`
`Int. Cl.
`H04W 76/19
`(52) US. Cl.
`CPC ................................... H04W 76/19 (2018.02)
`(58) Field of Classification Search
`None
`See application file for complete search history.
`
`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 7 Otis L Thompson, Jr.
`.
`(57).
`.
`ABSTRACT
`.
`A ereleSS deVlCe for resumlng a COHHeCUOn 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 “Odes the message 0011113115ng an
`indication to perform a filll configuration; and apply the full
`configuration.
`
`20 Claims, 17 Drawing Sheets
`
`2223:4343
`gamer
`
`3pm.:
`Emmi/r
`
`»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»
`
`3C3
`3mm!
`
`ma:
`
`' me
`
`me
`
`am
`
`6w:
`
`1w;
`
`7
`
`_
`
`1
`
`6w:
`
`3N
`
`;
`
`SAMSUNG 1001
`
`SAMSUNG 1001
`
`1
`
`

`

`US 10,517,133 B2
` Page 2
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`2015/0181461 A1*
`
`6/2015 Kim ...................... H04W 74/08
`370/236
`. H04W 8/22
`6/2017 Sunel
`2017/0188269 A1*
`H04W 24/08
`2017/0311206 A1* 10/2017 Ryoo .
`
`H04W 76/12
`2018/0049255 A1*
`2/2018 Chen ..
`2018/0091968 A1*
`3/2018 Ly ........... H04L 43/16
`
`2018/0213452 A1*
`7/2018 Kim .................. H04W 36/0033
`2018/0234941 A1*
`8/2018 Kim .................... H04W 68/005
`2018/0270741 A1*
`9/2018 Enomoto .
`H04W 36/12
`2018/0279204 A1*
`9/2018 Kim .........
`H04W48/02
`
`2018/0359149 A1* 12/2018 Shaheen
`H04L 5/0092
`2019/0037635 A1*
`1/2019 Guo
`H04W 76/27
`
`2019/0053102 A1*
`2/2019 Oohira ..
`..... H04W 8/06
`
`2019/0053199 A1*
`2/2019 Fujishiro
`H04W 72/04
`2019/0124572 A1*
`4/2019 Park .........
`.. H04W 76/27
`
`2019/0215800 A1*
`7/2019 Fujishiro ..
`. H04W 8/08
`
`2019/0215887 A1*
`7/2019 Burbidge .
`H04W48/14
`2019/0254074 A1*
`8/2019 Jeon .................. H04W 36/0069
`
`OTHER PUBLICATIONS
`
`Ericsson, Offline#22 LTE re-establishment and resume While using
`NR PDCP, 3GPP TSG-RAN WG2 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
`
`
`
`me$3“;mwfiwm
`
`
`
`
`
`\wmxmmmExwwm\fixwmm
`
`w35w:—
`
`3
`
`
`

`

`U.S Patent
`
`Dec. 24, 2019
`
`Sheet 2 of 17
`
`US 10,517,133 B2
`
`.xsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssxx
`
`\\
`
`
`
`.3»\\\\\\\\\\\\\\\\\\\\\\\x\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\x\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
`
`
`.‘.xx\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\x\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\>.\\.
`
`gmaa
`
`3m
`
`\\x\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\\\\\\\\\\\\\\\\\\\\\\\\\3‘:
`
`fi
`
`..1\\\\\\\““““““““““““
`
`\\\\\\\\\\\\\\\\\\\\\\\“\““““““““““~\
`
`\
`
`N9:.me—
`
`
`
`H1\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\k\\\\\\\\\\\\\\\\\\\\\\\\\‘5‘.
`
`{5}
`{,3
`w
`
`Ekmmm
`
`®Q§mama
`
`“3%kwkwwm
`
`4
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 3 of 17
`
`US 10,517,133 B2
`
`
`
`
`
`
`
`
`
`\\\\\\\\\\\\\ mm‘3xx..\.J\“Le,\nmM.k“...«kkkxMfik\\§§§§§\§xxxxxxkkkv............““»«««««««\
`
`\
`
`
`
`vxxxxxv.{xvxxxxxxlxxxlxxxvxxxxlxxxl.‘
`
`
`
`Ȣ.xx2x2x2x......xllvvvixvll..2222...
`
`\
`
`
`
` m.ESSKEEEEESEES:
`
`“....2am3\x.
`
`\\\\\\\\\
`
`\\\\\u\\
`
`
`
`.mm
`
`Km
`
`»
`
`3!!3t§¥$§..¥8§'8i88183Q§31§31§¥t§¥8i88
`
`...,
`
`m353m
`
`K
`
`.33.tS3
`{33032332.
`«3§.§$i.§83tw8§.¥3§¥8}¥¥!w
`
`3&3»)
`
`“
`
`.3...\
`
`ctEmuw.“
`
`3.3
`
`
`
`v.xxxxxxxxx§§§§§§§§§§§§\§§§\
`
`n n n , . . » .WM““\\““\““- \
`
`
`
`M....
`
`\§§§§§§§§§
`
`¢\\\“\“
`
`wwmw.“
`
`
`
`Vxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk
`
`
`
`
`
` .m“mm“.m..o..........................................“.
`
`
`
`\x\xxxx\\\\\\\\\\\\\\\¥x§x¥§\x\\\\\\\\\.
`
`
`
`v\\\\\\\§§§§§§§§§i§§i§§§§x
`
`N...“
`
`
`¢\\\\\\\\
`
`V
`
`Hmwms
`
`na$3.55....n.......EEEEbE:
`
`
`
`\\\\\\§§\§:4“§§§§§§§§§M§§x
`
`¥8§¥8§¥¥§¥3
`
`t«598
`
`039
`
`
`
`
`
` \.“22‘.“.i\...\i\o«.\.““S§§§§§\§§§§§§§§§§§§\\\ta
`
`
`
`....«\\\\\§§§\\xxxxvxxxxxxxxxxxxxxxxxxx¥§3
`
`ww
`
`3...“...
`
`\\\\\\\\\\\
`
`\\
`
`I‘\\\\\\\\\
`
`
`\Xx..im.\.¢.\u\m“an.”
`
`mitiiii...:ttmitimi.\----
`
`
`
`tit.{22
`
`.\\uu3.,v
`
`\\\\\\\\
`
`\\
`§«
`
`----~
`
`~
`\----
`
`
`
`.3{2‘3
`
`5
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 4 of 17
`
`US 10,517,133 B2
`
`XXXflaw.
`
`
`
`«XXXwamm«XXX»XQX
`
`\\\\\\\\\\\\\\\\\
`
`QXXmumm \\\\\\\\\\\\\\\\\
` waxy“XX--ammmwXX
`
`mquwwa
`
`\\\\\\\\\\\\\\\\\
`
`, \\\\\\\\\\\\\\\\\
`
`\\\\\\\\\\\\\\\\
`
`v359m
`
`mX
`
`XXXMgngwXfim,MXXXmXmXXXXxXXXXm,
`
`6
`
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 5 of 17
`
`US 10,517,133 B2
`
`EUTRAN
`
`RR CConnecIionReeslab111112172612{Re a uesl
`
`
`
`
`
`RRCConIvzectz‘onReestablishmem‘
`
`
`
`RR CConnectionReestablishmenlCom olete
`
`Figure 5
`
`EUTRAN
`
`
`
`
` RRCConnectionReestabliS/mzemRe '
`
`RRCCOImectionReestablishmentReuest
`
`Figure 6
`
`7
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 6 of 17
`
`US 10,517,133 B2
`
`
`
`RRCCmmeclionResumeRe uesl
`
`RRCConneclionResume
`
`
`
`RR CConnectionResum6Com 1 [etc
`
`Figure 7
`
`
`
`RRCCOi'zi'zecIiOI-zRammeRec uesi
`
`
`RRCConneciionSem )
`
`
`
`
`RRCConnectionSem (70m late
`
`Figure 8
`
`
`
`RRCCmmectionResum 6R6 ruesf
`
`8
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 7 of 17
`
`US 10,517,133 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`83r\
`
`
`
`30%m22«~76m3
`
`
`
`
`
`
`
`
`
`
`
`\............................................................................../
`
`32mg$.83mmmmwmmnomad/
`
`\W/waommsm38:80m5$2-5.32
`
`//WM\\
`
`
`\
`
`
`
`333m.688an“37$.32
`
`$9:qu
`
`48%AD
`
`
`
`
`
`vcoamsm8$383W766::
`.couooaaoumax2:
`
`omnommom
`
`.03”
`
`
`
`land...».3964“,
`
`
`
`5.6838nomsauummgob
`
`aH2&5
`
`
`
`
`
`
`Ba35%38:8m<m:.92:
`
`MS6929?;Ema255va
`
`
`
`$9.,“va$88
`
`9
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 8 of 17
`
`US 10,517,133 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Blmzm$22mZom3.
`
`
`
`
`
`
`
`cc:/\
`
`
`
`
`
`
`
`
`
`$250M2850Maxénoum3”Larfim
`
`.03H
`
`
`
`umuommoMoEaum“x250m3i<ém
`
`22:5
`
`
`
`.9:._BBQEcUQE:moxcosooccoonm
`
`.02H
`
`BaguxmsSummouummd:H
`
`3:399:Egugwfixgv
`
`oacsmomcozugccuvmxd:g
`
`“338%
`
`
`
`
`
`$2333Ba8532$359a5%.8:
`385m3muoamzsflmu-2
`
`ameouzzoodxx
`
`10
`
`
`
`
`
`wEEmoi0.384EogmxA:Hw
`
`
`
`ommommoxmmuuo<8253*..09H
`
`
`
`
`
`10
`
`
`
`
`
`

`

`U.S. Patent
`
`102
`
`S
`
`1f
`
`US 10,517,133 B2
`
`
`
`a9630.,M.aCNN”
`
`“3.53“woEmmoxcouoogoOUKM.2m.D3:233“
`
`
`mwuoo<Eocamx.03.;
`
`
`
`9umccmmum.mmfl
`
`
`
`ofismmmcocooccooumm.32
`
`GE.oUchcfiomogmucv
`
`
`
`03585mmoou<Eovmmm.83
`
`
`
`
`
`
`
`
`
`
`
`BadmEEmzo20m2“.262ab
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`03$K
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`353%:$55.Eammxm.mmfifi388m5mvuzflzmymoaa3.533Mm<was
`
`
`
`11
`
`
`
`
`
`7.cvm.,
`
`
`
`.m.m.0518000,anxqowoozmovuxm
`
`228%as?V£5Elm
`
`.m.N.
`
`¥U<«353%£0Em6mm”www-mm
`
`883%“com.
`
`22:5
`
`£3AD
`
`gigII
`
`019QQHUmZZOUDam
`
`
`
`
`
`11
`
`
`
`

`

`U.S Patent
`
`Dec. 24, 2019
`
`Sheet 10 of 17
`
`US 10,517,133 B2
`
`Q\\\\\\\\\\\\\\\\\\\\\\\\\\\z
`w<v
`1
`,“\
`f/I
`:1
`\
`\\ w
`A
`\
`\\\\\\\\\\\\\¥§\\\\\\\\\\\\5\\
`~~~~~~~~~~~~~~~§\~~~~~~~~~~~~~~\\
`
`\‘
`..
`§
`4
`\w mm
`:
`v ~, §
`§
`
`IIIIII
`
`\
`\
`\
`\Vo«xvon\vom\vou\von\von\vo\
`-
`§<
`
`III/II
`Ill]
`§<<<<<<<<<<<<<<<<§<dddddddddddddddé
`
`.,...0
`
`
`
` cox ¢oN ¢¢¢' two xeo wee
`
`”II”?
`IIIIIIIIIIIIIIIIIIIIIIIIII5I
`I9/
`
`\.
`
`-
`
`,
`
`v
`
`
`
`
`
`\x\\\\\\\
`
`xcc- ¢5N ¢bN ¢oN cow ceoIaaaaaaaaaaooaoaooaaaooaoaooaoaoov
`
`
`
`SSQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢Q§l99909999999999999977
`I$000004!
`
`
`‘§\‘x\§\\¥‘
`V\\\\\\\\\\\\\\\\\\\\§\\\\\\\\\\\\\\\\\\
`
`
`.
`..., \
`\§ s\k
`\\\}
` ,g?
`\kss wk V
`S»A»A»«VA»A»A»A»«VA»A»A»A»«VA»A»A»A»«VAVAVAVAV«VAVAVAVAVN«
`xxxxxxxxxxxxxxxxxxxxxxxxx\ xxxxxxxxxxxxxxxxxxxxxxx
`
`
`
` IaoooooagoovyIaaaaaaaaaaaaaaaaaaaaooaooooaooooaoooofiaooovr
`
`Ibaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaay
`
`
`‘////////////.O
`\\\\\y
`
`Vv\\\\\\\\\\\\\\\\\\~\\\\\\\\\\\\\\\\x
`
`\S
`
`:E
`
`
`
`
`
`
`\\\\\\\\\\\\\\\\\\§§\\\\\\\\\\\\\\\~~
`
`
`1444/f!IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
`IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
`I.
`
`
`\I
`\N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢N¢3%
`s,
`\
`V
`3
`§
`1-
`\
`\
`§
`:I
`\
`\
`v
`w\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\$
`33
`\
`\
`y ,
`
`\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\‘\§
`i
`§
`§
`§
`¥
`\xxxxxxxxxa\xxxxx:uxxxxxxxxxxxxxxxxx»
`§
`§
`"
`\
`x
`¢
`\
`\
`‘
`\
`\
`‘ ‘.
`\
`\
`~‘
`§
`§
`¥
`\
`
`§\
`
`§\
`\
`\
`\
`\
`\
`§
`%‘
`§
`§
`\
`.
`\
`§
`I
`\
`\
`-
`§
`\
`.'
`.
`.
`'
`\
`,
`.
`'
`\ .. .
`'
`'
`.
`.
`.
`\
`\
`,
`,
`.v.u.v
`.
`\
`.
`~ \
`§
`“any“.
`§
`§
`a§uNauNauNauNauNauNauNauNamNauNauNauNauNauNauNauNauaau«
`\
`\
`§
`
`S\
`
`§\
`\
`\
`\
`\
`\
`\
`\
`\
`\
`\
`\
`\
`\
`§
`\
`\
`
`§\
`
`i\
`§
`§
`
`Figure 13
`
`12
`
`12
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 11 of 17
`
`US 10,517,133 B2
`
`22:5
`
`13
`
`0 O
`
`N
`
`
`
` a{9552manomccoemg
`
`£03prSou
`
`%£52
`
`13
`
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 12 of 17
`
`US 10,517,133 B2
`
`[— 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
`
`3 10
`
`
`
`in response to determining that the retrieved configuration
`information is unidentifiable, generating new configuration
`
`parameters
`
`m
`
`sending a resume response message to the wireless device, the
`message comprising an indication to perform a full
`configuration using the new configuration parameters
`320
`
`Figure 15
`
`14
`
`14
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 13 of 17
`
`US 10,517,133 B2
`
`/. 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 wireiess device, the message comprising an, indication to
`perform a full configuration
`
`Figure 16
`
`Sending to a network node a request to resume a connection in
`the communication network
`355
`
`340
`3. 5
`
`Receiving a resume response message from the network node,
`the megsage comprising an indication to perform a foil
`configuration
`3.63;
`
`Applying or performing the full configuration
`
`Figure 17
`
`15
`
`15
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 14 of 17
`
`US 10,517,133 B2
`
`[— 370
`
`receiving, from a Wireless device, a request to resume a
`connection in a communication network
`375
`
`fl
`
`based on the request, retrieving configuration information for
`the Wireiess device; wherein the configuration information is
`adapted from a source network node to the network node so as
`to be usable by the network node
`
`3.3.519
`
`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 fl
`
`Network
`Interface
`Q
`
`Transceiver(
`5) Q
`
`Tx(s)
`
`Rx(s)
`Network node _2__.Z_Q_
`
`Figure 19
`
`Figure 20
`
`17
`
`17
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 16 of 17
`
`US 10,517,133 B2
`
`Rx(s) 660
`
`TranngiOvefls)
`“((5) 650
`
`l
`Processing Circuitry 610
`I
`Memory 630
`Processor(s)
`620
`|_ ____________ |
`
`|I
`
`I
`
`Figure 2}
`
`Wireiess device _2_1_0_
`
`Modulesm
`
`Figure 22
`
`18
`
`18
`
`

`

`U.S. Patent
`
`Dec. 24, 2019
`
`Sheet 17 of 17
`
`US 10,517,133 B2
`
`___
`
`rlllllIIIIL
`
`ommmdd
`
`EggmBEES
`
`
`
`
`
`1.111.111_mmmddw30522flammdd
`
`_IIIIIIId_sac.mamas_r!!!!!!Lmmegm
`
`
`
`formantcozWommdd
`
`
`
`2Egg:ommdc
`
`u.zommdd
`
`32%:
`
`com
`
`mmmmdc_
`
`
`_commas.11111111111...11111112
`
`_1111111112_mwmmdd___162.33”~“,_P3:0mmdd__.x1.v_rummmmmm--.“<n5:23m_1,2,3
`
`
`u.RN30.>m_r.11111111mAmvmccmu£<—§1:5,5”thEmmeOLQDmmdflu
`
`commuaatsommdc
`ES§§.s;325_s;380m..
`
`
`
`ll._1Ix.
`
`
`
`x<\8:835\32mm8was:2:55
`
`ommdd
`
`
`
`\wucflaamEELSxcozmuzgng
`
`Willing—IIIIIIJ
`
`.ondc__omm
`
`GO
`
`or?
`
`05¢
`
`Ommdd
`
`cozmgag<
`
`
`5%.“coumfi
`m:t_>ommdd
`
`§§§§§§§§§§§§§§§§§L~11111111
`.—_llllllla§>O¢MCU
`
`E>ovmdd
`
`llllllllllllllllll..
`
`a!iiiiiiiiiiiiiii
`
`2,:3.80.L
`
`0380
`
`EmemmcmE
`
`mam
`
`cosmzmmfié
`
`19
`
`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 US. 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_
`CONNECTED is 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 two different roles: an eNB may either act as an
`Master node (MN) or as an Secondary node (SN). In DC, a
`UE is connected to one MN and one SN.
`
`10
`
`15
`
`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.
`
`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 SRBlbis, was also introduced in 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, and it 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), SRBl 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
`SRBl, because logged measurement information and NAS
`messages can be lengthy and could cause the blocking of
`more urgent and smaller SRBl 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
`
`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 DC are:
`The introduction of split bearer from the SN (known as
`SCG split 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-NR tight interworking.
`The SN is sometimes referred to as SgNB (where gNB is
`an NR base station), and the MN as MeNB in case the LTE
`is the master node and NR is the secondary node. In the other
`case where NR is the master and LTE is 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 SCG legs or 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
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`In Radio Access Network 2 (RAN2), it has been agreed to
`harmonize what was former called MCG bearers, MCG split
`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-DC is not setup);
`20
`
`65
`
`20
`
`

`

`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 PDCP layers is 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) MCG bearer which uses the 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 and SN.
`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 RAN2 point of view it is fully supported to
`setup MCG bearers being terminated in the SN node using
`S-KeNB and SCG bearers being terminated in the MN node.
`Similarly, 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 terminated split bearers.
`
`LTE Re-Establishment Procedure
`
`The purpose of the LTE re-establishment procedure is 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 SRBl, 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 SI 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 the target
`eNB does not receive the UE context or it doesn’t under-
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`stand the context, it may reject the re-establishment and the
`UE has to go to RRC_IDLE to re-connect. If the target eNB
`doesn’t understand the RRC context but can understand the
`
`45
`
`SI 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 SI context.
`
`In case of a re-establishment success, SRBl 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 not initiate the
`procedure but instead moves to RRC_IDLE directly.
`E-UTRAN applies the re-establishment procedure as fol-
`lows:
`
`When AS security has been activated:
`reconfigure SRBl 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).
`
`50
`
`55
`
`60
`
`65
`
`21
`
`US 10,517,133 B2
`
`4
`
`SRBO is used for sending the RRCConnectionReestablish-
`mentRequest, RRCConnectionReestablishment and RRC-
`ConnectionReestablishementReject messages, while RRC-
`ConnectionReestablishmentComplete uses SRBl.
`
`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 be seen as if 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 mode is reduced signaling and
`faster transition to CONNECTED mode as compared to
`legacy IDLE-CONNECTED mode transitions, while main-
`taining the UE power saving advantages of IDLE mode.
`When a decision is made by the network to move the UE
`to suspended state, the eNB sends the UE an RRCConnec-
`tionRelease message with the release cause value of rrc-
`suspend. The RRCConnectionRelease message also con-
`tains a Resume ID. The UE stores 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.
`When the UE later 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 eNB other than the eNB that was serving the
`UE when the 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 eNB restore
`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. SRBO is used for sending the
`RRCConnectionResumeRequest,
`RRCConnectionSetup
`and RRCConnectionReestablishementReject, while RRC-
`ConnectionResume and RRCConnectionResume Complete
`messages use SRBl.
`The main difference between resume and re-establish-
`
`ment is (from a procedural perspective): SRBl 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/DRB configuration, 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.
`
`21
`
`

`

`US 10,517,133 B2
`
`5
`In step 1020, the eNB initiates the Sl-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, 81 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 Sl-U bearers for the UE. The Sl-U
`refers to the 81 user plane and the Sl-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 MME sends 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 resumeIdentity which is stored by the UE.
`In step 1060, the UE stores the AS context, suspends all
`SRBs and DRBs. The UE enters the RRC_IDLE light
`connected state.
`
`When the UE later 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 eNB other than the eNB
`that was serving the UE when the UE was suspended. In that
`case, the new eNB can perform a context fetch e.g. by using
`the Retrieve UE Context procedure from the old eNB (as the
`resumeIdentity includes information about the old eNB/
`cell).
`The RRC connection resume procedure in the same eNB
`and new eNB are illustrated 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 some later 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 eNB to 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 eNB initiates the Sl-AP Context Resume
`procedure to notify the MME about the UE state change.
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`In step 1180, the MME requests the S-GW to activate the
`Sl-U bearers for the UE.
`
`In step 1190, the MME acknowledges step 1170.
`FIG. 12 illustrates the RRC resume procedure 1200 in an
`eNB different from the source eNB where the UE got
`suspended.
`Steps 1205 to 1215 are the same as steps 1110 to 1130 in
`FIG. 11.
`
`In step 1220 C(2-AP: Retrieve UE Context Request), the
`new eNB locates 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 C(2-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 eNB initiates the S 1 -AP Path Switch
`procedure to establish a $1 UE associated signalling con-
`nection to the serving MME and to request the MME to
`resume the UE context.
`
`In step 1250, the MME requests the S-GW to activate the
`Sl-U bearers for the UE and updates the downlink path.
`In step 1255, the MME acknowledges step 1245.
`In step 1260 C(2-AP: UE Context Release), after the
`Sl-AP Path Switch procedure, the new eNB triggers release
`of the UE context 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
`UE signalling 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 or transitioning via IDLE (since the UE AS context
`is removed). FIG. 13 is known in the art, as such, it will not
`be described further.
`
`Full RRC Configurations in LTE
`
`In LTE, during a Handover (H0) or re-establishment, the
`UE context 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 UE shall:
`
`1> release/clear all current dedicated radio configurations
`except the MCG C-RNTI, the MCG security configuration
`and the PDCP, RLC, logical channel configurations for the
`RBs and the logged measurement configuration;
`NOTE 1: 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