as) United States
`a2) Patent Application Publication co) Pub. No.: US 2012/0202478 Al
` Van Lieshoutet al. (43) Pub. Date: Aug. 9, 2012
`
`
`
`US 20120202478A1
`
`(54) METHOD AND APPARATUS FOR
`CONFIGURING RADIO ACCESS
`FUNCTIONALITY OF A WIRELESS
`COMMUNICATION UNIT
`
`(30)
`
`Foreign Application Priority Data
`
`Oct. 5, 2009
`
`(GB) eeeee ceneeees 0917394.9
`
`(75)
`
`Inventors:
`
`Gert-Jan Van Lieshout, Apeldoorn
`(NL); Himke Van Der Velde
`Zwolle (NL)
`°
`
`Publication Classification
`
`(1)
`
`Int. CL.
`HO4AW 36/14
`HO04W 80/00
`
`(2009.01)
`(2009.01)
`
`(73) Assignee:
`
`SAMSUNG ELECTRONICS CO.
`LTD., Suwon-si, Gyeonggi-do (KR)
`
`(52) US. CD. eeececeeectesesenscneecessescneneeansenees 455/419
`
`(21) Appl. No.:
`
`13/500,528
`
`(57)
`
`ABSTRACT
`
`(22)
`
`PCTFiled:
`
`Oct. 1, 2010
`
`(86) PCT No.:
`
`PCT/KR2010/006718
`
`§ 371 (c)),
`(2), (4)Date:
`
`Apr. 5, 2012
`
`A method for configuring radio access functionality of a
`wireless communication unit within a wireless communica-
`tion network, the method comprising sending to the wireless
`communication unit an indication of a required radio access
`protocol version to which the wireless communication unit is
`to be reconfigured.
`
`400
`
`Core Network
`
`
`
`446
`
`4ag
`
`APPLE 1005
`
`1
`
`APPLE 1005
`
`

`

`Patent Application Publication
`
`Aug. 9,2012 Sheet 1 of 15
`
`US 2012/0202478 A1
`
`[Fig. 1]
`
`o_
`—
`
`o
`\onevedaig J3AOPUBH ~ \uonnoaxg JOAOPUBY
`A
`
` A ABMO1C9BUIALES
`
`UON8|dWOD JEAOPUeH
`A,
`
`ued10UdNIMSWL}---------"" S90JNOSOY
`peg3sviUOWBUUOJUYONUODITGOWTOU!JODYWUODHAL”|7,
`
`
`JanelayePansueldJ8SN‘El/~ysanbayYUMWed“ZI
`
`
`
`
`
`
`
`BUIIIEUBISZV11fOqUODUolss|wpyGyYW!SaNbayJenopueH9Itd
`BUINeUBIS£7~~UOISAPOH'E
`
`puabeySuadayWaUaINseay‘Z
`
`
`
`ANS8d1nDgWOL)Sjayoed10))ngUONESIUOIUSUAS*§
`
`
`JOJSUB]SMEISNS"8GHDyaBuEO}SJoYIeMSUE!)(—[99MOU0}OZUOIYOUAS
`
`
`~~BuIeMojeleg0tté—“‘™SOC*™S
`
`3010}Vi+UoNeDOTe1nDIoz
`
`UlpuepalayingJaNlagpue1199PlowoYyoe1ag
`
`
`
`
`
`SSUNKS8!BLPANSueldJ8S/1'C)
`——
`yoyIsanbayUWSWed'g}
`
`SSB9l9yKOIUO)3“LI
`
`
`
`PIPIAOldUOHINSOYCIlY‘D
`
`ANS19612]
`
`UONEOIE19
`
`uOHedo|le
`
`
`
`
`
`919/009JUOIBY‘UUODDHH“Lh
`
`
`
`Blepevoed
`
`
`
`8SE9|9y‘BL
`
`2
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 2 of 15
`
`US 2012/0202478 Al
`
`[Fig. 2]
`
`
`
`
`
`WH1NIO}-OHPuog“WNOLLdO
`
`
`
`OHpudd“WNOLLdO
`
`
`
`dOP9eN--TWNOILLdO
`
`
`
`OHBYUODAUNDSSOHBYUONAINDAS
`
`
`
`{}JONINOISuolsug?xq|e9NUguUOU
`
`SYNOJUIPS{e9IPaq
`
`
`
`OHPud)--“WNOlLd
`
`WNOLLe
`
`
`
`
`
`SII-QJ-UONEING|JUOIBYUONISUUODIYYBUODSseoBIJUOJSeow}JONINOIS=:
`
`
`
`{}JONINOISdININ{SuUO|sUdIXWedNW9
`
`‘{
`
`
`
`
`
`
`
`TINNLaJeds‘TINNZejeds‘TINNesJeds
`
`
`
`‘TINNvaJeds“TINNGeJeds‘TINNgeieds
`
`19811x4
`
`*SI-BI-U0NeINBGYUOISYUONISUUODOYYQ1-LONCINGYWUOCISHUONIBUUOIIN
`
`paleo|peqgsyuojeoinosayoipeypoleoipaqgsyuoj9dunOsayope!
`
`
`4O((@YOXew™|)3Z1S)JONINOISISITSYNOJU|P9}e51p9p
`OJU[O1UODAUIGOWOJU[POAUODAI|IGOW!Olz
`
`
`‘JayNUaP|UONIeSueI-Juy
`
`
`
`
`
`
`
`
`SUOMUNEPSHESSOW:7°2'9‘LEEVESLWOlJ
`
`}7010H9
`
`
`
` i)}FOIOHOSUOISUSIXCONNO
`
`
`
`JalNUIP|UONIeSUeI]—-I1}JONINDIS =::UONeINGYUOCXsYUONIeUUONDYY
`
`TINNLeeds
`
`
`
`
`
`
`
`3
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 3 of 15
`
`US 2012/0202478 A1
`
`[Fig. 3]
`
`
`
`2VYLNIOI-OHPuod—
`
`“WNOILdO
`
`BYUOD-Sd§
`
`“WNOLdO
`
`paresIpansjuogesIsAud
`
`DayBIIPSsA6YUODIeIISAUC
`
`Ole
`
`
`
`SWUWSWI/3UONBWOJUIOUH:£°9“LEGOESLWOd)
`
`JOeIIXI
`
`JSMPOWPPYOL-9us}JONANOAS=::PHyeapaqgsyuogesodinoseyolpey
`
`WHINIOI-OHBuoy—-
`
`“TWNOLLdO
`
`“TWNOLLdO
`
`uuo)-0Hpuo?—
`
`“WNOILdO
`
`‘BYUOQUIEW-OWN}JOIOHO
`
`ISN9Sb9l9HO1-u0
`
`IS/DOWPPYOL-8y0
`
`TINN
`
`aNjeAWIGXa
`
`“WNOILdO{SnjeAUNejap
`
`BuUOD-sds
`
`JSIDOWDPYOL-GUs
`
`JSHPOWPPYOL-qup
`
`}SN9Seb9lsHO1-GID
`
`BYUODUIEW-JewW
`
`4
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 4 of 15
`
`US 2012/0202478 Al
`
`[Fig. 4]
`400
`
`410
`
`
`
`422
`
`420
`
`cefe
`
`
`Laat a}
`
`Core Network
`
`
`
`432
`
`430
`
`
`440
`
`446
`
`AAR
`
`5
`
`

`

`
`
`1S3N03YYINOONYH
`
`
`
`
`UOISJSAJOI0OId<<TLS
`UONPWJOJU|WONeJEdSd)qJ9AONUeHreege<
`
`
`
`WOW1S3N0IdYIADONWH
`
`[Fig. 5]
`
`vevtevOvi
`
`Patent Application Publication
`
`Aug. 9, 2012 Sheet 5 of 15
`
`US 2012/0202478 A1
`
`
`
`9)9/0WOQUONEINGWOIBYVONIBUUONIYYLEE'SE:
`
`oS
`
`E17'9E:1 O1S
`
`
`HN9JOBE]§N990IN0S
`ELW9E:Z SfGIG
`12S\UOISJ9A\109010140UDIIMS<<UO|S19\1090}01d0USUMS<
`
`
`
`UoHeMByUCsYUONOBUUOQaYY<<—_
`
`
`
`DUWIWODIaAROpUEH1Se"9R<UONEINGJWOISYUONISLUOQOYYLEE-£
`
`6
`
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 6 of 15
`
`US 2012/0202478 Al
`
`[Fig. 6]
`
`600
`ay
`
`
`
`RECEIVE HANDOVER
`REQUEST FROM
`SOURCE eNB
`
`610
`
`PERFORM ADMISSION CONTROL AND
`RESERVE RESOURCES IN TARGET CELL
`
`PREPARE CONNECTION
`RECONFIGURATION MESSAGE
`
`
`
`
`ADD
`‘SWITCH TO VERSION’
`FIELD TO
`RECONFIGURATION MESSAGE, AND SET TO V1
`
`RETURN HANDOVER REQUEST
`ACKNOWLEDGMENT TO SOURCE eNB
`COMPRISING RECONFIGURATION MESSAGE
`
`670
`
`ESTABLISH CONNECTION
`WITH UE
`
`620
`
`630
`
`650
`
`660
`
`7
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 7 of 15
`
`US 2012/0202478 Al
`
`
`
`FORWARD RECONFIGURATION MESSAGE TO UE
`
`
`
`
`
`
`PERFORM CONNECTION RECONFIGURATION
`
`
`
`ESTABLISH CONNECTION
`WITH TARGET eNB
`
`8
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 8 of 15
`
`US 2012/0202478 A1
`
`
`
`
`
`
`
`183034HIAOONVH
`
`
`
`
`UOISJBAIOINIOd<<vVL6
`UONPWJOJUIUONEJeCaJqJaAOpueHleege</
`
`SLE16
`
`
`
`
`
`
`
`[Fig. 9]
`
`vevvarYXOrv
`
`ELP'9E:1 GN919618]ON9899JNOS
`9)3/OWOQUONEINGBYUOISYUONIAUUOIOUYLEE'OE:9216
`
`
`WOW1SINOIYHIAOONVHE179E°2
`
`726
`
`oc6
`
`
`
` WOIS19A]090101d01U0IM§<<UONEINGYWVOISYUONIBULONOYH<<
`
`PUBWLWODJ8AOPUBHLEE9E<
`
`
`
`JSONDIYIUSWYSIGEISOYUONIIULODIYYLEE'OE:P
`
`
`
`nigUoReanBGuuoseuUORDSUUONONYLEE9E
`
`
`
`
`
`~\yo1s1991090101401UDIIMS<
`
`9
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 9 of 15
`
`US 2012/0202478 Al
`
`[Fig. 10]
`1000
`
`PROTOCOL VERSION FOR UE
`
`RECEIVE INDICATION OF REQUIRED
`CHANGE TO RADIO ACCESS
`
`ADD
`
`‘SWITCH TO PROTOCOL’
`
`FIELD TO
`
`RECONFIGURATION MESSAGE
`
`
`
`
`
`10
`
`

`

`JIeIIX
`OHPudd—“THNOLLdO6U0D-S¥BIJU09-Se
`
`
`
`OHpuod—“TWNOILdO1X9}U0D-SY1X¥9]U09-Se
`
`
`
`
`‘$3I-9.1-UONPWJOJLWUONeJedeJqJaAopueyQJ-UONWJOJUUONeJedeJqJeAopuey
`S3I-OX6A-UONEWJOJU|UONeJedasqianopueyUOISUGIXJ/CINQUONOXBA
`
`
`
`“TWNOLLdO6IJUOD-INHYBIJU0DW
`
`‘SMMSuUleUOD-LWYAMIIGeded-3NnOJUIAIIGedegsssdoyoipey-an
`
`1010}JONINOIS=::SII-OXGA-UVUONCWWOJUJUOHeIedaIgJaAOpPueH
`TLE"1)Y39NI
`
`TINNL8Jeds“TINNZeieds‘TINNEaJeds
`
`
`
`
`
`
`
`TINNweleds‘TINNGeleds‘TINNgaJeds
`
`
`
`SUONIUNSPBHessowl:2oO)Wold)
`
`
`
`}3OIOHOi)}JOIOHDSUOISUSIXI/EDNW9
`
`}JONINOIS=::UONBUWWOJUJUONeIedSIdJaAOPueH
`
`TINNL8Jeds
`
`Patent Application Publication
`
`Aug. 9, 2012 Sheet 10 of 15
`
`US 2012/0202478 A1
`
`[Fig. 11]
`
`TWNOILdO{}JONIN0IS
`
`TWNOILdO
`
`{
`
`
`
`{}JONINOISajNIN{JSUOISUdIXABINWD
`
`‘{
`
`
`
`}JONANDIS=::SII-GJ-UONEWOJUIUOHeIED9JdJSAOPUBH
`
`{
`
`11
`
`
`
`
`
`
`
`
`
`11
`
`

`

`Patent Application Publication
`
`Aug. 9,2012 Sheet 11 of 15
`
`US 2012/0202478 A1
`
`1981IXA [Fig. 12]
`
`
`TWNOILdOSJI-OXGA-UONeINGYUOIAYUONISUUODOYYUOISU9}XF/BINNOUONOXBA
`
`
`
`VH1NI0}-OHPudD—“WNOlLdO§=—PAYeI|PSQGJUoDsdinassyoipeypaesIpaq6yUOJadINosayolpe!
`
`
`
`OHpuod—“TWNOLLdOOHBYUODAINIISOHBWUODAWINIES
`
`
`
`OHpulod—-“TWNOLLdOOJU[O.NUOOAIIGONDJU[O.QUODAUIGOW
`
`
`
`SJI-BJ-LONeINGYUOISYUORNISUUODOYYNOP8eN—-“WNOILdOHIJUDgSeaWbyUogseaw}JONINOIS=":
`
`
`
`QHUOUpuog—“WNOILdOSYNOJUIPS1e9|paq
`
`‘$9|-Q/-UONeINGYUOISYUONIEUUODDYY8J-UONBJNEGYUOISqUONIBUUO|DII
`
`TWNOLLdO{}JONINOIS=Zzz1~UOISUa}XIeIAUQUOU
`
`
`40[(@HOXeW"1)3Z1S)JONINOISISNSYNOJUIPS}e9IPap
`
`
`UONeINGyUOXSyUOHIIUUODdYYJOUNUSP|UONIeSUBIL-9HHJayNuUsp|uOHoesueIL-9.}JONINOIS=::
`{}JONaINOISBNIN{SUOISUD}XABINWI{
`
`TLE”L)HIDSINI4A(DO01OIgOLUSIIMS.
`
`}JONANOIS=::SI-OXBA-UONeuNsYUOIIYyUONIIUUONOYY
`
`
`}OIOHO19}JOIOHOSUOISU9}XWEINND
`
`
`
`
`
`SUONIUNEPBHeSSAW:72°9WOl)
`
`00g!
`
`‘TINNZeJeds
`
`
`
`
`
`
`
`
`
`‘TINNvoleds‘TINNGaJeds‘TINNgaJeds
`
`
`
`
`
`
`
`
`
`TINNL9JedS‘TINNZaJeds‘TINNEaJeds
`
`dOD98N--
`
`{
`
`12
`
`12
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 12 of 15
`
`US 2012/0202478 A1
`
`[Fig. 13]
`
`TWNOLLdO
`
`
`
`‘S4I-8.-USWYSI|Ge}S3SYUOnIIUUONDHYSJ-JUSWYSIGe}SI9YUOHIBUUODI
`SJI-0XBA-JUAWYSIge)}sasyuondsuuoggYHH
`
`TWNOILdO{}JONINOISGeek___Yo|suaXedWQUOU
`‘pa}eolpaqbyuojadsnosayoipey
`
`
`JEWYSIIGeIssayUuONIeUUODIYY“JyURUapP|UONIeSUe!L-OHHJalnuap|uonoesues-I}JONINDIS=::
`‘WUNOQBuUIUIEYICOHIXON
`{}JONINOISSININISUOISUS}XICIUI{
`
`
`
`
`TLE”L)4999INI-UQIS!WOOIdOLUITEMS}JONINDIS=::
`
`ps}ed|PSQHYUOJaIdInoOsayolpe!}FONINOIS=::SII-BJ-JUSWYSI|GeSasqUOHIBUUODIYHY
`SJI-OXGA-uONeI
`
`
`
`TINN§=veleds“TINNGaJeds‘TINNgaJeds
`
`
`
`
`TINN=:FEABUS“TINNeJeds“TINNEaieds
`
`H9I0HD19}JOIOHSUDISUSIXIBINW
`
`
`
`SUOMULIPSHESSIW:2°2°9WOILBI1X9
`UDISUBYXI/BONLQUONOXGA
`
`junogbululeygdoHIxeu
`
` k
`
`~,\
`
`OOEl
`
`
`
`‘TINNaJeds
`
`d0p9eaN—
`
`{
`
`[Fig. 14]
`
`1400
`
`1410
`
`General control
`
`2=S~ceo=oa=SaSD=
`
`Security unit
`
`—=SnonoC3°os2=oSa
`
`1420
`
`1430
`
`1440
`
`13
`
`13
`
`
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 13 of 15
`
`US 2012/0202478 A1
`
`[Fig. 15]
`
`
`
`
`
`[0.}U098dJNOSalOlpey
`
`ANNIGOW 00S!
`
`
`
`[O.U09BIBJJOIUIYOM
`
`JOU09
`
`
`
`|0.1}U09AYINIVS
`
`
`
`JO.U09JUSWEJINSEsW
`
`14
`
`14
`
`

`

`Patent Application Publication
`
`Aug. 9, 2012 Sheet 14 of 15
`
`US 2012/0202478 Al
`
`[Fig. 16]
`
`1600
`
`1602
`
`
`
` Processor Memory Storage Devices
`
`1612
`
`Media Drive
`
`Storage Unit
`interface
`
`Communications
`interface
`
`1624
`
`15
`
`

`

`9BNX4
`
`(8°1)YI9ILNI
`
`éplaly
`
`LDIey
`
`6IjU09-X
`
`Patent Application Publication
`
`Aug. 9, 2012 Sheet 15 of 15
`
`US 2012/0202478 A1
`
`[Fig. 17]
`
`NOp9en—
`
`NOPION—-
`
`NOP8ON—-
`
`NOpaaN—
`
`NOp3en—
`
`NOP9eN—-
`
`NOPSeNn-—-
`
`NOP3aN—
`
`NOPaaN—
`
`NOP8eN--
`
`“TWNOLLdO
`
`“TWNOLLdO
`
`“THNOLLdO
`
`“TWNOWWdO
`
`‘TWNOILdO
`
`“TWNOLLdO
`
`“TWNOILdO
`
`pajeapaqio.nuogJaMOdMulGN
`PaeIpPIagiosuogJaModyuGN
`
`p9}29!P9Qb1U09-HIINd
`p97eIIpsqbyuog-yoond
`
`P9}B9IPSq6UOD-HOSNd
`psjeoipsqsyuog-yosnd
`
`p9}e9!IPsqbijU0I-HISOd}JONINOIS
`
`=I:PIPIpPIgsUOD|edlsAyd
`payeIIpsqbyuog-yospd
`
`BYUOD-HIIOd-IdL
`HOINdSYUO9-H9I0d-I90)
`
`BYUOI-HO0Od-ddL
`HOSNdSYUOD-HIIOd-90}
`
`51JU0DW0d9H-109
`
`BJUOJWOdSy-ID9
`
`“TWNOLLdO
`
`payesIpsqbju0d-IN-Subulpunag
`peyesIpaqgbyuog-IN-Sybulpunos
`
`SIUSW9]9VONBWIOJUIOHH:
`
`69‘LESSESLWor
`
`‘payeoipaqojujeuuaiuy
`
`TINN
`
`}JOIOHO
`
`aNjeAWayaxa
`
`“WNOLdO{SnleAUNeLEp
`
`OjJUJEUUAUE
`
`“THNOLLAO
`
`HUODISINDSYysuljnpsyos
`BHYUODISINDSYyBulnpaysIs
`
`16
`
`OXBA-N9ILIIPINHJUOD|BIISAud
`
`
`OXGA-PaieIPIJUoD|eoIsAyd
`
`{
`
`61uog-AUONoUNY
`OXOLA-6U0D-AUOHIUNY
`
`BuOD-KUONIUN{}JONINOIS
`
`=i:0X6A-PdedIPaqbyuoD|eoisAud
`OxBA-BlJUOD-Xuonsuny
`
`{}JONINOIS
`
`UDISUSIXIJBIHNQUOU
`
`{
`
`
`
`
`
` ‘{Zl@A“LI@A}CALWHAINNNA}JONINOIS}JONINOIS
`=!:Byuog-yuonoun4
`
`
`16
`
`

`

`US 2012/0202478 Al
`
`Aug. 9, 2012
`
`METHOD AND APPARATUS FOR
`CONFIGURING RADIO ACCESS
`FUNCTIONALITY OF A WIRELESS
`COMMUNICATION UNIT
`
`TECHNICAL FIELD
`
`[0001] The field of this invention relates to a method and
`apparatus for configuring radio access functionality of a wire-
`less communication unit. The invention is applicable to, but
`not limited to, a method for configuring radio access func-
`tionality of a wireless communication within a 3rd Genera-
`tion Partnership Project (GPP) evolved universalterrestrial
`radio access network, a network entity, a wireless communi-
`cation unit and a wireless communication network therefor.
`
`BACKGROUND ART
`
`In the field of cellular communication systems, for
`[0002]
`example cellular communication systems conforming to 3rd
`Generation Partnership Project (GPP) specifications, typi-
`cally the network controls the mobility of a mobile commu-
`nication unit (or user equipment (UE) in 3GPPparlance) that
`is in a connected mode(or to be precise in 3GPP terms in an
`RRC_CONNECTED state). For example,
`the network
`decides with which cell the UE maintains a radio connection
`
`(also referred to as the serving cell). The network applies the
`handoverprocedure to move the UE from onecell, namely the
`serving cell, to another cell, referred to as the target cell. The
`network decides the cell, as well as the Radio Access Tech-
`nology (RAT) in some circumstance, that the UE should
`connect to typically based on radio quality. However, the
`network may also take into accountotherfactors, such as cell
`load, UE capabilities, the type of bearers that are (being)
`established, etc. To assist the handover decision process, the
`network normally configures the UE to perform measure-
`ments on a serving frequency for its current serving cell
`(referred to as intra-frequency measurements), on other fre-
`quencies used by the Radio Access Technology for that net-
`work(referred to as inter-frequency measurements) and/or on
`frequencies used by other Radio Access Technologies (re-
`ferred to as inter-RAT measurements).
`[0003]
`FIG. 1 illustrates an example of a typical overall
`handoverprocedure 100 for a UE 105. Morespecifically FIG.
`1 illustrates an Intra-MME (Mobility Management Entity)/
`Serving Gateway handoveras defined in the 3GPP Technical
`Specification (TS) 36.300.
`[0004] Once a decision has been made to perform a han-
`dover, the handover procedure 100 starts with a preparation
`stage 110 comprising a source eNB 102 (enhanced NodeB)
`forwarding a HANDOVER REQUEST message 112, as
`defined in 3GPP TS 36.413, to a target eNB 104, the HAN-
`DOVER REQUEST message 112 comprising handover
`preparation information needed to prepare for the handover.
`The HANDOVER REQUESTmessage 112 carries the han-
`dover preparation information within a HandoverPrepara-
`tionInformation message, defined in 3GPP TS 36.331, and
`includes:
`
`radio access capabilities for the UE;
`[0005]
`a current radio access (e.g. access stratum, AS)
`[0006]
`configuration;
`[0007] RRM (Radio Resource Management) configura-
`tion, such as information kept only by the eNB thatis
`used primarily for Radio Resource Management(where
`
`usage of such RRM configuration information is eNB
`implementation-dependent); and
`[0008]
`radio access (AS) context, i.e. information kept
`only by the eNB (..e. information that is not exchanged
`across the radio interface), such as information needed
`to perform RRC (Radio Resource Control) connection
`re-establishment.
`
`it
`If the target eNB 104 accepts the handover,
`[0009]
`reserves the radio resources and decides on the details of the
`
`radio access configuration to be used by the UE 105 in the
`target cell. This radio access configuration is returned to the
`source eNB 102 within a HANDOVER REQUEST ACK
`message 114, as defined in 3GPP TS 36.413. This HAN-
`DOVER REQUEST ACK message 114 carries the radio
`access configuration within a HandoverCommand message,
`that is defined in 3GPP TS 36.331. The HandoverCommand
`
`message again carries an RRCConnectionReconfiguration
`message, as defined in 3GPP TS 36.331. When used to per-
`form a handover within, say, E-UTRA,this message includes
`the radio access configuration to be used in the target cell,
`such as:
`
`the measurement configuration, expressed by
`[0010]
`wayof a ‘delta’ compared to the configuration used in
`the source cell
`(the delta indicating configuration
`changes, as opposed to complete configuration informa-
`tion, in order to reduce the size of the message);
`[0011]
`the mobility control information, which specifies
`the target cell identity (by meansofa cell identity) and
`some characteristics (such as a frequency, a bandwidth
`and additional spectrum emission information; only if
`different from what is used in the sourcecell, i.e. delta
`signaling information is provided), the new radio access
`identity to be used in the target cell, the cell-specific
`radio resource configuration (common for all UEs),
`dedicated resources used for initial access in the target
`cell and a timer to limit the duration that the UEtries
`
`connecting to the target cell;
`[0012]
`the UE-specitfic radio resource configuration(i.e.
`the dedicated radio configuration), also expressed as a
`delta, compared to the configuration used in the source
`cell; and
`[0013]
`the security configuration,i.e. the algorithms, if
`different from the ones used in the source cell (delta), as
`well as parameters affecting the derivation of radio
`access security keys (i.e. an indication whether a new
`base key is to be used and a counterthat is incremented
`upon every handover).
`[0014] After the preparation stage 110, handover execution
`is performed as illustrated generally at 120, whereby the
`source eNB 102 proceeds with the handover, which includes
`the source eNB 102 transparently forwarding a RRCConnec-
`tionReconfiguration message 122 to the UE 105 (i.e. it does
`not change the message contents; the source eNB does how-
`ever perform integrity protection and ciphering of the mes-
`sage), and the UE 105 attempting to connectto thetargetcell
`(steps 124, 126), and returning a RRCConnectionReconfigu-
`rationComplete message 128, as defined in 3GPP TS 36.331.
`[0015] The signaling used upon handover, as defined in
`3GPP TS 36.331 to a large extent applies delta signaling for
`the various parameters, or fields in 3GPP parlance, whereby
`the radio access network (Evolved Universal Terrestrial
`Radio Access Network? EUTRANin the case of 3GPP TS
`36.331) only signals values that change from those used in the
`source cell. 3GPP TS 36.331 specifies the signaling (the
`
`17
`
`17
`
`

`

`US 2012/0202478 Al
`
`Aug. 9, 2012
`
`Protocol Data Unit content) by means of ASN.1. Fields for
`which delta signaling applies are defined as optional, so they
`may be absent, in combination with a need code of ‘ON’
`whereby in case of absencethe receiver takes no action with
`respect to such fields, and where applicable continues to use
`the existing value (and/or associated functionality). FIG. 2
`illustrates an example 200 of a message definition for RRC-
`ConnectionReconfiguration messages in accordance with
`3GPP TS 36.331. For the example illustrated in FIG. 2, the
`field measConfig 210 is defined as being OPTIONAL(at
`220), with aneed code of ‘ON’(at 230). It should be noted that
`whilst the example illustrated in FIG. 2 only showsthe fields
`present at the message level, similar considerations with
`regard to fields being defined as ‘optional’ with need codes of
`‘ON’apply at otherlevels. For example, FIG.3 illustrates an
`example 300 ofa definition for a RadioResourceConfigDedi-
`cated information element (IF) (in accordance with 3GPP TS
`36.331) comprising several optional fields with need codes
`set to ‘ON’.
`
`[0016] Whilst the use of delta signaling in this manner
`enables a significant reduction in the signaling overhead
`required when a handoveris performed, it also creates issues
`with respect to backward compatibility when a target eNBis
`arranged to support an earlier release of the radio access
`protocols than a version supported by both the serving eNB
`and UE.
`
`For optional fields with a need code of ‘ON’,
`[0017]
`explicit signaling is required to deactivate functionality asso-
`ciated with that field, such as for backward compatibility
`purposes, as applies when the target eNB does support the
`concerned functionality. For example, in the case where, say,
`the sps-Config field 310 illustrated in FIG. 3 is absent in a
`RadioResourceConfigDedicated identity element (IE), the
`UE will continue to use previously configured values.
`Accordingly, in order to deactivate previously active func-
`tionality, it is necessary to include the appropriate fields in a
`mannerthat is suitable to ‘clear’ the previously configured
`values.
`
`[0018] The RRC protocol defined in 3GPP TS 36.331
`includes different kinds of protocol extensions that may be
`addedforlater versions of the specifications, of which there
`are two prime categories: non-critical extensions (NCE) and
`critical extensions (CE). It has been agreed that the non-
`critical extension mechanism is
`the primary extension
`mechanism, since it just adds on to the existing signaling.
`This, for example, means that when a messageis received that
`includes non-critical extensions that are not comprehended
`by the receiver, the message maybe processedas if the exten-
`sions were not present. In contrast, a message that includes
`critical extensions that are not comprehended is completely
`ignored bythe receiver. Such critical and non-critical exten-
`sions are provided in various different manners:
`[0019]
`defining new message types;
`[0020]
`defining a new messageversion;
`[0021]
`adding an optional open SEQUENCEatthe end
`of a message or within a size-delimited containere.g. a
`bit string;
`[0022]
`extending the values of a field of ENUMER-
`ATEDtypeby using a value previously defined as spare
`or by adding a new value after an extension marker;
`[0023]
`extending the values of a field of CHOICE type
`by using a value previously definedas spare or by adding
`a new value after an extension marker;
`
`extending a field of SEQUENCEtype by adding
`[0024]
`new fields after an extension marker;
`[0025]
`etc.
`
`DISCLOSURE OF INVENTION
`
`Technical Problem
`
`[0026] Currently there is no defined wayfor a target eNB to
`deactivate radio access configuration functionsthatare intro-
`duced in a protocol version not supported by the target eNB.
`If the UE continues using the concerned functions, severe
`interoperability problemsare likely to occur.
`[0027] Thus, a need exists for an improved mechanism for
`configuring radio access functionality of a wireless commu-
`nication unit.
`
`Solution to Problem
`
`[0028] Accordingly, the invention seeks to mitigate, allevi-
`ate or eliminate one or more of the above mentioned disad-
`vantages singly or in any combination. Aspects of the inven-
`tion provide a network entity, a wireless communication unit,
`a wireless communication network, and a method therefor as
`described in the appended claims.
`[0029] According toa first aspect of the invention, there is
`provided a methodfor configuring radio access functionality
`of a wireless communication unit within a wireless commu-
`nication network, the method comprising, at a radio access
`network entity, sending to the wireless communication unit
`an indication of a required radio access protocol version to
`which the wireless communication unitis to be reconfigured.
`[0030] Thus, in one example embodimentofthe invention,
`the network entity is able to (re)configure radio access func-
`tionality that is active within the wireless communication unit
`in accordance with a required radio access protocol version.
`For example, the network entity is able to configure the wire-
`less communication unit to deactivate radio access function-
`
`ality introducedin later versionsofthe radio access protocol,
`relative to that version supported by the network entity (the
`required version), even though the network entity does not
`recognise such functionality.
`[0031] According to an optional feature of the invention,
`the method comprises receiving from a source network entity
`a handover request for a wireless communication unit; and
`sending to the wireless communication unit an indication of a
`target radio access protocol version to which the wireless
`communication unit is to be configured. In this manner, the
`network entity is able to configure the wireless communica-
`tion unit to deactivate radio access functionality introduced in
`later versionsofthe radio access protocolrelative to the target
`version supported by that network entity (the required ver-
`sion), even thoughthe networkentity does not recognise such
`functionality.
`[0032] According to an optional feature of the invention,
`the method further comprises determining, upon receipt of a
`handoverrequest, at least one of a source networkentity radio
`access protocol version and a wireless communication unit
`radio access protocol version, and if the at least one deter-
`mined source network entity and wireless communication
`unit radio access protocol version comprises a version later
`than a supported radio access protocol version, sending to the
`wireless communication unit an indication of a target radio
`access protocolversion to which the wireless communication
`unit is to be configured. For example, the method may com-
`prise, upon receipt of a handover request, determining a
`
`18
`
`18
`
`

`

`US 2012/0202478 Al
`
`Aug. 9, 2012
`
`source network entity radio access protocol version and a
`wireless communication unit radio access protocol version,
`and ifthe source network entity radio access protocol version
`and the wireless communication unit radio access protocol
`version comprise versions later than the supported radio
`access protocol version, sending to the wireless communica-
`tion unit an indication of a targetradio access protocol version
`to whichthe wireless communication unitis to be configured.
`In this manner, the wireless communication unit may only be
`sent an indication of a required radio access protocol version
`to whichit is to be reconfigured whenit is determined that a
`source network entity radio access protocol version and/or a
`wireless communication unit radio access protocol version is
`a later version than that supported by the target network
`entity, potentially avoiding unnecessary reconfiguration of
`the radio access functionality of the wireless communication
`unit.
`
`[0033] According to an optional feature of the invention,
`the step of determiningat least one ofa source network entity
`radio access protocol version and a wireless communication
`unit radio access protocol may comprise reading a field
`within a recetved HANDOVER REQUEST message. The
`field is arranged to comprise an indication ofat least one of a
`supported radio access protocol version for a source network
`entity from which the handover request was received; a sup-
`ported radio access protocol version for the wireless commu-
`nication unit; and a latest radio access protocol version in
`which active functionality of the wireless communication
`unit is introduced.
`
`[0034] According to an optional feature of the invention,
`the field within the received HANDOVER REQUESTmes-
`sage may form a part of a HandoverPreparationInformation
`message contained within the HANDOVER REQUESTmes-
`sage.
`
`wireless communication unit in response to receiving a con-
`nection reestablishment request message from the wireless
`communication unit.
`
`[0040] According to an optional feature of the invention,
`the method may comprise receiving an indication of a
`required changeto a radio access protocol version for which
`the wireless communication unit is configured to comply with
`and sending to the wireless communication unit an indication
`ofa required radio access protocol version to whichthe wire-
`less communication unitis to switch to.
`
`[0041] According to an optional feature of the invention,
`the wireless communication network may comprise an
`evolved universal terrestrial radio access network (E-UT-
`RAN).
`[0042] According to a second aspectofthe invention, there
`is provided a computer program product comprising execut-
`able program code for configuring radio access functionality
`of a wireless communication unit within a wireless commu-
`nication network, the executable program code operable for
`sending to the wireless communication unit an indication of a
`required radio access protocol version to which the wireless
`communication unit is to be reconfigured.
`[0043] According to a third aspect of the invention,thereis
`provided a network entity for supporting radio access to a
`wireless communication network, the network entity com-
`prising a signal processing module arranged to send to the
`wireless communication unit an indication ofa required radio
`access protocolversion to which the wireless communication
`unit is to be reconfigured.
`[0044] According to a fourth aspectofthe invention thereis
`provided a methodfor configuring radio access functionality
`of a wireless communication unit within a wireless commu-
`nication network, the method comprising sendingto a target
`network entity a handover request for a wireless communi-
`cation unit, the handover request comprising an indication of
`at least one of a source networkentity radio access protocol
`version and a wireless communication unit radio access pro-
`tocol version.
`
`[0035] According to an optional feature of the invention,
`determining a source network entity radio access protocol
`version may comprise looking up, within Operation and
`Maintenance (O&M)configuration information, a supported
`[0045] According toafifth aspect of the invention there is
`radio access protocolversion for a source network entity from
`provided a computer program product comprising executable
`which the handover request was received.
`program code for configuring radio access functionality of a
`[0036] According to an optional feature of the invention,
`wireless communication unit within a wireless communica-
`the target radio access protocol version ofwhichan indication
`tion network, executable program code operable for sending
`is sent to the wireless communication unit may comprise a
`to a target network entity a handover request for a wireless
`latest supported radio access protocol version.
`communication unit, the handover request comprising an
`[0037] According to an optional feature of the invention,
`indication of at least one of a source network entity radio
`the target radio access protocol version ofwhichan indication
`access protocol version and a wireless communication unit
`is sent to the wireless communication unit may comprise a
`radio access protocol version.
`latest supported radio access protocol version from a subset of
`[0046] According to a sixth aspect of the invention there is
`radio access protocol versions.
`provided a network entity for supporting radio access to a
`[0038] According to an optional feature of the invention,
`wireless communication network, the network entity com-
`sending to the wireless communication unit an indication ofa
`prising a signal processing module arranged to sendto a target
`target radio access protocol version to which the wireless
`network entity a handover request for a wireless communi-
`communication unitis to be configured may comprise adding
`cation unit, the handover request comprising an indication of
`the indication ofthe target radio access protocol within a field
`at least one of a source networkentity radio access protocol
`of a connection reconfiguration message to be contained
`version and a wireless communication unit radio access pro-
`tocol version.
`within a HANDOVER REQUESTACKmessage returned to
`the source network entity.
`[0039] According to an optional feature of the invention,
`sending to the wireless communication unit an indication ofa
`target radio access protocol version to which the wireless
`communication unitis to be configured may comprise adding
`the indication ofthe target radio access protocol within a field
`of a connection re-establishment message to be sent to the
`
`[0047] According to a seventh aspect ofthe invention there
`is provided a method for configuring radio access function-
`ality ofa wireless communication unit within a wireless com-
`munication network, the method comprising, at the wireless
`communication unit, receiving an indication of a required
`radio access protocol version to which the wireless commu-
`nication unit is to be reconfigured, and deactivating radio
`
`19
`
`19
`
`

`

`US 2012/0202478 Al
`
`Aug. 9, 2012
`
`access functionality introduced in radio access protocol ver-
`sions later than the indicated required radio access protocol
`version.
`
`[0048] According to an eighth aspect of the invention there
`is provided a computer program product comprising execut-
`able program code for configuring radio access functionality
`of a wireless communication unit within a wireless commu-
`
`been drawn to scale. Like reference numerals have been
`includedin the respective drawings to ease understanding.
`[0058]
`FIG. 1 illustrates an example of a typical overall
`handoverprocedure.
`[0059]
`FIG. 2 illustrates an example ofa messagedefinition
`for RRCConnectionReconfiguration messages.
`[0060]
`FIG. 3 illustrates an example of a definition for a
`RadioResourceConfigDedicated information element.
`nication network, the executable program code operable for
`[0061]
`FIG. 4 illustrates an example of a wireless commu-
`receiving an indication of a required radio access protocol
`nication network.
`version to which the wireless communication unit is to be
`[0062]
`FIG. 5 illustrates a simplified example of a message
`reconfigured, and deactivating radio access functionality
`sequence for a handover request in accordance with some
`introduced in radio access protocol versions later than the
`example embodiments of the invention.
`indicated required radio access protocol version.
`
`[0063] FIG.6illustrates an example of a simplified flow-
`[0049] According to a ninth aspect of the inventionthereis
`chart of amethodfor configuring radio access functionality of
`provided a wireless communication unit for connecting to a
`a wireless communication unit according to some example
`wireless communication network, the wireless communica-
`embodiments of the invention.
`tion unit comprising a signal processing module arranged to
`[0064] FIG.7illustrates an example of a simplified flow-
`
`receive an indication of a required radio access protocolver-
`sion to which the wireless communication unitis to be recon-
`chart of amethodfor configuring radio access functionality of
`a wireless communication unit according to some example
`figured, and deactivate radio access functionality introduced
`embodiments of a further aspect of the invention.
`in radio access protocol versions later than the indicated
`
`[0065] FIG.8illustrates an example of a simplified flow-
`required radio access protocol version.
`chart of amethodfor configuring radio access functionality of
`[0050] According to a tenth aspect of