I 1111111111111111 1111111111 11111 lllll lllll 111111111111111 111111111111111111
`US010044613B2
`
`c12) United States Patent
`Kazmi et al.
`
`(IO) Patent No.: US 10,044,613 B2
`(45) Date of Patent:
`Aug. 7, 2018
`
`(54) MULTIPLE RADIO LINK CONTROL (RLC)
`GROUPS
`
`(71) Applicant: INTEL IP CORPORATION, Santa
`Clara, CA (US)
`
`(72)
`
`Inventors: Zaigham Kazmi, San Marcos, CA
`(US); Ana Lucia Pinheiro, Portland,
`OR (US)
`
`(73) Assignee: Intel IP Corporation, Santa Clara, CA
`(US)
`
`( *) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 195 days.
`
`(21) Appl. No.:
`
`14/785,116
`
`(22) PCT Filed:
`
`Dec. 13, 2013
`
`(86) PCT No.:
`
`PCT /US2013/07 4861
`
`§ 371 (c)(l),
`(2) Date:
`
`Oct. 16, 2015
`
`(87) PCT Pub. No.: WO2014/185953
`
`PCT Pub. Date: Nov. 20, 2014
`
`(65)
`
`Prior Publication Data
`
`US 2016/0094446 Al Mar. 31, 2016
`
`Related U.S. Application Data
`
`(60) Provisional application No. 61/824,338, filed on May
`16, 2013.
`
`(51)
`
`Int. Cl.
`H04L 121741
`H04W 72104
`
`(2013.01)
`(2009.01)
`(Continued)
`
`(52) U.S. Cl.
`CPC ............ H04L 45174 (2013.01); G0lC 211005
`(2013.01); G0lS 19112 (2013.01);
`(Continued)
`
`(58) Field of Classification Search
`CPC ............... H04L 45/74; H04L 12/6418; H04W
`28/0252; H04W 72/0433; H04W 4/02;
`(Continued)
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`2005/0073974 Al* 4/2005 Kim ...................... H04L 12/189
`370/329
`
`2012/0281666 Al
`
`11/2012 Diachina et al.
`(Continued)
`
`FOREIGN PATENT DOCUMENTS
`
`CN
`EP
`
`9/2012
`102655682 A
`2916572 Al * 9/2015
`
`........ H04W 72/0406
`
`OTHER PUBLICATIONS
`
`3GPP TSG-RAN WG2 #81-R2-130420: Protocol architecture
`alternatives for dual connectivity; Agenda Item 7.2; Jan. 28 to Feb.
`1, 2013; Malta.
`
`(Continued)
`
`Jackie Zuniga Abad
`Primary Examiner -
`(74) Attorney, Agent, or Firm - Thorpe North & Western
`
`ABSTRACT
`(57)
`Technology to process radio link control (RLC) groups is
`disclosed. In an example, a carrier aggregation (CA) capable
`user equipment (UE) operable process radio link control
`(RLC) groups can include a UE radio frequency (RF)
`transceiver and a processor. The UE RF transceiver can be
`configured to receive packets from more than one cell via a
`sending node RF transceiver. The processor can be config(cid:173)
`ured to process service data units (SDU) of the packets in a
`radio link control (RLC) entity of a protocol stack (PS).
`Each SDU can be associated with an RLC flow identifier
`(RFI). The RFI can comprise an RLC group identifier (RGI)
`indicating the sending node RF transceiver, and a radio
`bearer identifier (RBID).
`
`28 Claims, 15 Drawing Sheets
`
`500 ---.
`
`Receiving packets via at least one
`LIE redio frequency (RF) transceiver
`from more than one node RF
`transceivers.
`
`Feeding data from each node
`physical leyer/med1a access control
`(PHY/MAC) entity to a peer UE PHY/
`MAC entity on the LIE, wherein each
`LIE PHY/MAC entity is associated
`with a RLC group ident1f1er (RGI).
`
`Processing service data units (SDUs)
`of Iha packets in a radio link control
`(RLC) entity of a protocol stack (PS)
`based on a RLC flow identifier (RFI)
`including the RGI and a radio bearer
`identifier (RBID).
`
`510
`
`520
`
`530
`
`IPR2019-00047
`Qualcomm 2018, p. 1
`
`

`

`US 10,044,613 B2
`Page 2
`
`(51)
`
`(52)
`
`(58)
`
`(56)
`
`(2018.01)
`(2006.01)
`(2006.01)
`(2010.01)
`(2009.01)
`(2009.01)
`(2009.01)
`(2009.01)
`
`Int. Cl.
`H04W 4102
`H04L 12164
`G0lC 21100
`G0lS 19112
`H04W28/02
`H04W 84/12
`H04W 88/06
`H04W 16/18
`U.S. Cl.
`CPC ........... H04L 1216418 (2013.01); H04W 4102
`(2013.01); H04W 2810252 (2013.01); H04W
`7210433 (2013.01); H04W 7210453 (2013.01);
`H04W 16/18 (2013.01); H04W 84/12
`(2013.01); H04W 88/06 (2013.01)
`Field of Classification Search
`CPC ... H04W 72/0453; G01C 21/005; G0lS 19/12
`See application file for complete search history.
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`2013/0301547 Al * 11/2013 Gupta
`
`2014/0010192 Al
`
`1/2014 Chang et al.
`
`H04W 76/048
`370/329
`
`OTHER PUBLICATIONS
`
`3GPP TSG RAN WG2 Meeting #8lbis-R2-131529: Impacts of
`Splitting a Single EPS Bearer between Two (or more) eNBs;
`Agenda Item 7.2; Apr. 15 to Apr. 19, 2013; Chicago, USA.
`3GPPTSG RAN 2G2 Meeting #8lbis-R2-131350: Discussion on
`protocol architecture comparison for dual connectivity; Agenda
`Item 7.2; Apr. 15 to Apr. 19, 2013; Chicago USA.
`3GPP TSG-RAN WG2 Meeting #8lbis-R2-131174: Protocol
`architecture for dual connectivity; Agenda Item 7.2; Apr. 15 to Apr.
`19, 2013; Chicago, USA.
`3GPP TWG-RAN WG2 Meeting #8lbis-R2-131164: Study of
`Solutions and Radio Protocol Architecture for Dual-Connectivity;
`Agenda Item 7.2; Apr. 15 to Apr. 19, 2013; Chicago USA.
`Office Action dated Sep. 18, 2017, in European Patent Application
`No. 13884528.4, filed Dec. 13, 2013; 10 pages.
`
`2013/0083783 Al
`
`4/2013 Gupta et al.
`
`* cited by examiner
`
`IPR2019-00047
`Qualcomm 2018, p. 2
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 1 of 15
`
`US 10,044,613 B2
`
`I
`
`I
`
`I
`I
`
`I
`
`I
`
`I
`
`I
`I
`
`I
`
`I
`
`I
`I
`
`n n n D
`- - -
`
`5 MHz
`1.4 MHz 3 MHz
`25 RBs
`6 RBs 15 RBs
`72 SCs 180 SCs 300 SCs
`210
`212
`214
`
`10 MHz
`50 RBs
`600 SCs
`216
`
`I
`
`I
`I
`
`I
`
`il
`
`I
`
`I
`
`~i
`
`I
`
`I
`
`il
`
`I
`
`I
`
`~i
`
`I
`
`15 MHz
`75 RBs
`900 SCs
`218
`
`20 MHz
`100 RBs
`1200 subcarriers (SCs)
`220
`
`FIG. 1
`
`IPR2019-00047
`Qualcomm 2018, p. 3
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 2 of 15
`
`US 10,044,613 B2
`
`Component Carriers
`
`Band A
`
`Carrier 1
`
`Carrier 2
`
`Carrier 3
`
`Frequency
`
`FIG.2A
`
`Component Carriers
`
`Band A
`
`Carrier 1
`
`Frequency
`
`FIG. 28
`
`Component Carriers
`
`Band A Carrier 1
`
`FIG. 2C
`
`Frequency
`
`IPR2019-00047
`Qualcomm 2018, p. 4
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 3 of 15
`
`US 10,044,613 B2
`
`eNB DL
`
`•••••••~1••••:•:•••s••••••• ••••••••~•••:•:••••1~••••••••••••••• n•••:•:••••[•••••••
`
`[[]K>•K>-KJID
`UE UL rrnm··•··~~
`wm·••-•••00
`
`. . . . . . . .
`. ...... .
`.. ·.·.hf·.·.··.·.·.·.· . . ·.·.·.hf·.·.·.·.·.·.·.·.
`
`Frequency
`
`UE (and network) configuration
`
`Network only configuration
`
`FIG. 3A
`
`UE UL
`
`Frequency
`
`FIG. 3B
`
`IPR2019-00047
`Qualcomm 2018, p. 5
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 4 of 15
`
`US 10,044,613 B2
`
`,--------------------------
`
`.....
`I
`LL
`0::: ---
`
`()
`<(
`~
`
`N
`I
`LL
`
`-
`
`0..
`()
`0
`0..
`
`w
`::J
`
`N
`()
`...J
`0:::
`
`-
`
`0::: ---()
`I
`<(
`~ I
`I
`I
`I
`L ____ ________________ _____ J
`
`(cid:127)
`
`(9
`LL
`
`-----------------------1
`I
`I
`I
`I
`I
`
`I
`0:::
`0:::
`
`----
`
`s
`
`(9
`0..
`~
`(9
`(J)
`
`,._
`,._
`(J)
`Cll
`(J)
`co
`(J)
`0..
`W
`
`I
`
`0..
`()
`0
`0..
`
`-----
`
`()
`...J
`0:::
`
`N
`LL
`0:::
`---
`()
`<(
`~
`
`I
`
`I
`
`I
`I
`I
`I
`I
`----- __________________ J
`----- ------------------
`I
`I
`I
`I
`- -
`I
`I
`I
`I
`I
`.....
`I
`I ©
`I
`LL
`I ()
`I
`,....
`0:::
`---
`,._
`()
`I
`I (..)
`<(
`Cll
`~ I
`I ~
`I
`I
`I
`I
`-
`I
`I
`I
`I
`L---------------------~
`
`IPR2019-00047
`Qualcomm 2018, p. 6
`
`

`

`SGW/PGW
`
`UE
`
`PDCP
`
`RLClflow 2
`I
`I
`I
`I
`I
`I
`I
`I
`
`I
`RLClflow 1
`I
`I
`I
`I
`I
`I
`
`RLC
`
`LCID=4
`
`LCID=3
`
`MAC/
`RF-2
`
`MAC/
`RF-1
`
`PS
`
`I
`
`I
`
`I
`
`I
`
`MAC/
`RF-1
`
`MAC/
`RF-2
`
`Bearer-6 on LCID-4
`Bearer-5 on LCID-3
`
`Bearer-6 on LCID-4
`
`Bearer-5 on LCID-3
`
`FIG. 5
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`> = ~
`0 ....
`
`'"-....J
`N
`
`QO
`
`I
`
`I
`I
`I
`
`('D
`('D
`
`rJJ =(cid:173)
`.....
`Ul
`0 ....
`....
`
`Ul
`
`d r.,;_
`"'""'
`'"= = ~
`"'""' w = N
`
`~
`O'I
`
`IPR2019-00047
`Qualcomm 2018, p. 7
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 6 of 15
`
`US 10,044,613 B2
`
`--
`
`0..
`()
`0
`0..
`
`~
`
`w
`::J
`
`.....
`___ (.l ___
`...J
`0:::
`
`___ u ___
`N
`...J
`0:::
`
`I
`I
`I
`I
`I
`I
`
`.....
`I
`LL
`0:::
`---
`()
`<(
`~
`
`N
`I
`LL
`
`0::: ---
`
`()
`<(
`~
`
`L ______________________
`
`co .
`(9
`LL
`
`-----------------------1
`I
`I
`I
`I
`I
`
`©
`()
`cii
`E
`(J)
`
`----
`
`N
`LL
`0:::
`---
`()
`<(
`~
`
`I
`I
`()
`...J
`I
`0:::
`I
`I
`----- __________________ J
`----- ------------------
`I
`I
`I
`--
`I
`I
`I
`I
`I
`I
`.....
`I
`I ©
`I
`LL
`I ()
`I
`0:::
`,....
`---
`,._
`()
`I
`I (..)
`<(
`Cll
`~ I
`I ~
`I
`I
`I
`-
`I
`I
`I
`I
`I
`L---------------------~
`
`s
`
`(9
`0..
`~
`(9
`(J)
`
`,._
`,._
`(J)
`Cll
`(J)
`co
`(J)
`0..
`W
`
`I
`
`0..
`()
`0
`0..
`
`-----
`
`()
`...J
`0:::
`
`IPR2019-00047
`Qualcomm 2018, p. 8
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 7 of 15
`
`US 10,044,613 B2
`
`0..
`
`w
`::::>
`
`~----------------------
`
`(cid:127)
`
`(9
`u..
`
`~----------------------,
`I
`Ill
`I
`Z
`I
`I
`I
`I
`Cll
`ai
`I
`I
`I
`U
`I
`I
`I
`iii
`I
`I
`E
`I
`I
`L-~----- ______________ I
`
`Cl)
`CJ
`~
`
`Cl) -- - C:
`N ><
`,----------------------,
`I
`Ill
`I
`Z
`I
`I
`Cll ~
`I
`I
`I
`I
`- _I
`
`0..
`
`I
`I
`L -
`
`e ~
`~ ~
`:i::
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`IPR2019-00047
`Qualcomm 2018, p. 9
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 8 of 15
`
`US 10,044,613 B2
`
`(")
`II
`0
`0
`
`_J
`
`CL
`(.)
`0
`CL
`
`LU
`::J
`
`CD
`
`u
`- - -~ - - -
`
`N
`I
`LL
`0:::
`~
`~
`
`8 ~-----~
`I
`I
`~
`I
`~
`ffi
`I
`en
`I
`__________________________ I
`_J
`
`00 .
`(9
`u..
`
`(")
`II
`0
`(.)
`_J
`
`~
`II
`0
`(")
`0
`_J 8
`
`(.)
`_J
`
`--------------------------,~
`I II
`1Q
`10
`I _J
`I
`
`u
`...J c:::
`
`0
`u
`C:
`
`CD 1----
`8 I
`
`I
`I
`I
`I
`
`CL
`(.)
`0
`CL
`
`u
`...J c:::
`
`LO
`II
`0
`~
`~
`ca
`(J)
`(l)
`
`I
`I
`I
`I
`I
`~ - - -~
`I
`I
`I
`__________________________ I
`
`IPR2019-00047
`Qualcomm 2018, p. 10
`
`

`

`,---------- ---------,
`UE
`EPS Bearer 5
`
`PDCP
`
`Reordering
`
`RLC
`
`I
`I
`1 LCID 3
`I RGI 0
`I
`I
`
`I
`I
`LCID 31
`RGI 1 I
`I
`I
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`~
`~
`'"-....J
`N
`
`0 ....
`
`QO
`
`('D
`('D
`
`1,0
`
`rJJ =(cid:173)
`.....
`0 ....
`....
`
`Ul
`
`d r.,;_
`"'""'
`'"= = ~
`"'""' w = N
`
`~
`O'I
`
`MAC/RF
`1
`
`MAC/RF 2
`
`------!-------
`
`LCID 3
`
`LCID 3
`LCID 3
`RGI 0
`RGI 1
`I MAC RF 1
`1 I MAC/RFl2
`L ______ j _______ -----
`
`LCID 3
`
`FIG. 9
`
`I
`
`SGW/PGW
`
`EPS Bearer 5
`
`II
`
`,------ -------1 r - - - - - - - - - - - -
`Macro Cell I
`Small Cell
`1
`I
`(Group 0) I
`(Group 1)
`I
`
`I
`I
`1
`1
`PDCP
`:
`t----i-
`---t-
`- - -~
`I ~---+--___J
`I
`I
`I
`I
`1
`I
`
`, - - - - - - I - - - - -
`RLC
`1
`I
`I
`I
`I
`
`I
`I
`I
`I
`1 I
`I
`I
`I
`I
`I
`I
`I
`I
`
`RLC
`
`I
`I
`I
`I
`
`IPR2019-00047
`Qualcomm 2018, p. 11
`
`

`

`SOU Reordering can be performed at SAPs
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`I
`I
`I
`I
`I
`
`i - - - - - -
`1
`I
`1 BearerID=6
`I
`I.
`I
`I
`I RLC flow 2.0
`I
`I
`I
`1 RLC flow 2.1
`I
`I
`I
`I
`I
`I
`I
`I
`1
`
`MAC/RF-2
`RGI 1
`1 ..................... - - - -
`
`BearerID=5
`
`RLC flow 1.1
`
`RLC flow 1.0
`
`LCID=3
`
`MAC/RF-1
`RGI 0
`
`~
`~
`'"-....J
`N
`
`0 ....
`
`QO
`
`('D
`('D
`
`rJJ =(cid:173)
`.....
`....
`0
`0 ....
`....
`
`Ul
`
`d
`rJl.
`"'""'
`'"= = ~
`"'""' w = N
`
`~
`O'I
`
`BearerID=5
`
`17"·=·~·=·- -
`1 IVla~roC~II
`I
`I
`I
`I
`I
`I
`I
`I
`I
`
`PDCP
`
`RLC
`
`MAC/RF-1
`
`LCID=4
`LCID=3
`
`-----1 r------
`I
`~mall (;ell
`I
`I
`I
`I
`I
`
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`
`RLC
`
`.
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`~.~.~.~.~.~.--:-
`
`MAC/RF-2
`
`------:-'.·
`LCID=4
`
`LCID=3
`
`FIG. 10
`
`IPR2019-00047
`Qualcomm 2018, p. 12
`
`

`

`BearerID=6
`
`Both RLC DRBs setup with RLC group=0
`
`r---------------~;---------------
`
`PDCP
`
`Source Cell
`
`PS
`
`RLC flow 2.0
`
`RLC flow 1.0
`
`RLC
`
`LCID=4
`
`LCID=3
`
`MAC/RF-2
`RGI 0
`
`MAC/RF-1
`
`RGI 0
`
`Bearer-6 on LCID-4
`
`Bearer-5 on LCID-3
`
`FIG. 11
`
`MAC/RF-1
`
`MAC/RF-2
`
`Bearer-6 on LCID-4
`
`Bearer-5 on LCID-3
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`~
`~
`'"-....J
`N
`
`0 ....
`
`QO
`
`('D
`('D
`
`rJJ =(cid:173)
`.....
`....
`....
`0 ....
`....
`
`Ul
`
`d r.,;_
`"""'
`'"= = ~
`"""' w = N
`
`~
`O'I
`
`IPR2019-00047
`Qualcomm 2018, p. 13
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 12 of 15
`
`US 10,044,613 B2
`
`500 ~
`
`Receiving packets via at least one
`UE radio frequency (RF) transceiver
`from more than one node RF
`transceivers.
`
`510
`~
`
`1'
`
`Feeding data from each node
`physical layer/media access control
`(PHY/MAC) entity to a peer UE PHY/
`MAC entity on the UE, wherein each
`UE PHY/MAC entity is associated
`with a RLC group identifier (RGI).
`
`~
`520
`
`1'
`
`Processing service data units (SDUs)
`of the packets in a radio link control
`(RLC) entity of a protocol stack (PS)
`based on a RLC flow identifier (RFI)
`including the RGI and a radio bearer
`identifier (RBID).
`
`~
`530
`
`FIG. 12
`
`IPR2019-00047
`Qualcomm 2018, p. 14
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 13 of 15
`
`US 10,044,613 B2
`
`600 ~
`
`Process service data units (SOUs) for
`packets in a radio link control (RLC) ~ 610
`entity of a protocol stack (PS).
`
`,,
`Assign a RLC group identifier (RGI)
`to each SOU indicating a sending ~ 620
`node RF transceiver.
`
`,,
`Transmit the SOUs in packets that
`include the RGI to a user equipment
`(UE) RF transceiver via the sending
`node RF transceiver.
`
`~
`630
`
`FIG. 13
`
`IPR2019-00047
`Qualcomm 2018, p. 15
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 14 of 15
`
`US 10,044,613 B2
`
`Wireless
`Device
`720
`r----------1
`1 Transceiver 1
`,._ __________
`I
`I
`724
`I
`I
`r - - - - - - - - - -,
`I Processor
`I
`I
`I
`._ __________
`722
`I
`I
`I
`I
`
`Serving Node
`710
`------------,
`Node
`Device
`712
`
`Transceiver
`716
`
`Processor
`714
`
`Cooperation
`Node
`750
`------------,
`Node
`Device
`752
`
`Transceiver
`756
`
`Processor
`754
`
`748
`
`FIG. 14
`
`IPR2019-00047
`Qualcomm 2018, p. 16
`
`

`

`U.S. Patent
`
`Aug. 7, 2018
`
`Sheet 15 of 15
`
`US 10,044,613 B2
`
`Mobile
`Device ~
`
`Multiple
`Antennas
`
`:-No;:;--Volatil;
`1 Memory Port
`
`Speaker
`
`'
`[
`
`/
`
`/
`
`J Speaker
`'
`
`Liquid Crystal Display
`(LCD) Screen and/or
`Touch Screen Display
`1-------,
`1 Application 1
`1 Processor
`I
`_ __ __ __ .J
`1-------,
`Graphics
`1
`1
`1 Processor
`I
`___ ____ .J
`
`:- - ,;:;-t;r~al -1
`
`1 Memory
`I
`_ __ __ __ .J
`
`!_j _J _J _J _J _J _J _J _J _J _Ji
`!_j _J _J _J _J _J _J _J _J _J _Ji
`i_J _J _J _J _J _J _J _J _J _J _Ji
`l _J _J _ _J ________________________ _J _ _J _Ji
`©--('I ......
`
`Keyboard
`
`Microphone
`
`FIG. 15
`
`IPR2019-00047
`Qualcomm 2018, p. 17
`
`

`

`US 10,044,613 B2
`
`1
`MULTIPLE RADIO LINK CONTROL (RLC)
`GROUPS
`
`RELATED APPLICATIONS
`
`This application claims the benefit of and hereby incor(cid:173)
`porates by reference U.S. Provisional Patent Application
`Ser. No. 61/824,338, filed May 16, 2013.
`
`BACKGROUND
`
`Wireless mobile communication technology uses various
`standards and protocols to transmit data between a node
`(e.g., a transmission station) and a wireless device (e.g., a
`mobile device). Some wireless devices communicate using
`orthogonal frequency-division multiple access (OFDMA) in
`a downlink (DL) transmission and single carrier frequency
`division multiple access (SC-FDMA) in an uplink (UL)
`transmission. Standards and protocols that use orthogonal
`frequency-division multiplexing (OFDM) for signal trans(cid:173)
`mission include the third generation partnership project 20
`(3GPP) long term evolution (LTE), the Institute of Electrical
`and Electronics Engineers (IEEE) 802.16 standard (e.g.,
`802.16e, 802.16m), which is commonly known to industry
`groups as WiMAX (Worldwide interoperability for Micro(cid:173)
`wave Access), and the IEEE 802.11 standard, which is
`commonly known to industry groups as WiFi.
`In 3GPP radio access network (RAN) LTE systems, the
`node can be a combination of Evolved Universal Terrestrial
`Radio Access Network (E-UTRAN) Node Bs (also com(cid:173)
`monly denoted as evolved Node Bs, enhanced Node Bs,
`eNodeBs, or eNBs) and Radio Network Controllers (RNCs),
`which communicates with the wireless device, known as a
`user equipment (UE). The downlink (DL) transmission can
`be a communication from the node (e.g., eNodeB) to the
`wireless device (e.g., UE), and the uplink (UL) transmission
`can be a communication from the wireless device to the
`node.
`In computer networking and/or wireless communication,
`different functions can be provided by different layers in a
`protocol stack. The protocol stack (PS) can be an imple(cid:173)
`mentation of a computer networking protocol suite. The 40
`protocol stack ( or protocol suite) can include the definition
`and implementation of the protocols. Each layer or protocol
`in the protocol stack can provide a specified function. The
`modularization of the layers and protocols can make design
`and evaluation of the computer networking and/or wireless
`communication easier. In an example, each protocol module
`or layer module in a stack of protocols may communicate
`with at least two other modules ( e.g., a higher layer and a
`lower layer). The lowest protocol or layer can provide
`low-level, physical interaction with the hardware. Each
`higher layer may add more features. The upper or topmost 50
`layers can include user applications and services.
`In the LTE system, communication layers can include a
`physical (PHY) (i.e., layer 1 (Ll)), a data link (i.e., layer 2
`(L2)), a network (i.e., layer 3 (L3)), and an application layer.
`In an example, layer 2 (L2) can include media access control
`(MAC), radio link control (RLC), or packet data conver(cid:173)
`gence protocol (PDCP) layers, and layer 3 (L3) can include
`a radio resource control (RRC) layer, non-access stratum
`(NAS), and internet protocol (IP). In an example, the RRC
`protocol can manage control plane signaling between a
`wireless device (e.g., a user equipment (UE)) and a radio
`access network (RAN) via the node (e.g., an eNB).
`
`2
`junction with the accompanying drawings, which together
`illustrate, by way of example, features of the disclosure; and,
`wherein:
`FIG. 1 illustrates a block diagram of various component
`5 carrier (CC) bandwidths in accordance with an example;
`FIG. 2A illustrates a block diagram of multiple contigu(cid:173)
`ous component carriers in accordance with an example;
`FIG. 2B illustrates a block diagram of intra-band non(cid:173)
`contiguous component carriers in accordance with an
`10 example;
`FIG. 2C illustrates a block diagram of inter-band non(cid:173)
`contiguous component carriers in accordance with an
`example;
`FIG. 3A illustrates a block diagram of a symmetric-
`15 asymmetric carrier aggregation configuration in accordance
`with an example;
`FIG. 3B illustrates a block diagram of an asymmetric(cid:173)
`symmetric carrier aggregation configuration in accordance
`with an example;
`FIG. 4 illustrates a diagram of a carrier aggregation (CA)
`architecture for a protocol stack (PS) in accordance with an
`example;
`FIG. 5 illustrates a diagram of carrier aggregation (CA)
`architecture with multiple split evolved packet system (EPS)
`25 bearers in accordance with an example;
`FIG. 6 illustrates a diagram of a user equipment (UE)
`architecture for dual connectivity with a single bearer in
`accordance with an example;
`FIG. 7 illustrates a diagram of a user equipment (UE)
`30 architecture for dual connectivity in accordance with an
`example;
`FIG. 8 illustrates a diagram of a user equipment (UE)
`architecture to support dual connectivity with multiple radio
`link control (RLC) entities and multiple evolved packet
`35 system (EPS) bearers into different cells in accordance with
`an example;
`FIG. 9 illustrates a diagram of an architecture to support
`dual connectivity with radio link control (RLC) groups in
`accordance with an example;
`FIG. 10 illustrates a diagram of radio link control (RLC)
`groups for multiple evolved packet system (EPS) bearers in
`accordance with an example;
`FIG. 11 illustrates a diagram of a backward compatible
`carrier aggregation (CA) architecture with radio link control
`45 (RLC) groups for multiple split evolved packet system
`(EPS) bearers in accordance with an example;
`FIG. 12 depicts a flow chart of a method for processing
`radio link control (RLC) flows at a user equipment (UE) in
`accordance with an example;
`FIG. 13 depicts functionality of computer circuitry of a
`node operable to support radio link control (RLC) groups in
`accordance with an example;
`FIG. 14 illustrates a block diagram of a serving node, a
`coordination node, and wireless device (e.g., UE) in accor-
`55 dance with an example; and
`FIG. 15 illustrates a diagram of a wireless device (e.g.,
`UE) in accordance with an example.
`Reference will now be made to the exemplary embodi(cid:173)
`ments illustrated, and specific language will be used herein
`60 to describe the same. It will nevertheless be understood that
`no limitation of the scope of the invention is thereby
`intended.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`DETAILED DESCRIPTION
`
`65
`
`Features and advantages of the disclosure will be apparent
`from the detailed description which follows, taken in con-
`
`Before the present invention is disclosed and described, it
`is to be understood that this invention is not limited to the
`
`IPR2019-00047
`Qualcomm 2018, p. 18
`
`

`

`US 10,044,613 B2
`
`3
`particular structures, process steps, or materials disclosed
`herein, but is extended to equivalents thereof as would be
`recognized by those ordinarily skilled in the relevant arts. It
`should also be understood that terminology employed herein
`is used for the purpose of describing particular examples
`only and is not intended to be limiting. The same reference
`numerals in different drawings represent the same element.
`Numbers provided in flow charts and processes are provided
`for clarity in illustrating steps and operations and do not
`necessarily indicate a particular order or sequence.
`
`Example Embodiments
`
`An initial overview of technology embodiments is pro(cid:173)
`vided below and then specific technology embodiments are
`described in further detail later. This initial summary is
`intended to aid readers in understanding the technology
`more quickly but is not intended to identify key features or
`essential features of the technology nor is it intended to limit
`the scope of the claimed subject matter.
`An increase in the amount of wireless data transmission
`has created congestion in wireless networks using licensed
`spectrum to provide wireless communication services for
`wireless devices, such as smart phones and tablet devices.
`The congestion is especially apparent in high density and
`high use locations such as urban locations and universities.
`One technique for providing additional bandwidth capac(cid:173)
`ity to wireless devices is through the use carrier aggregation
`of multiple smaller bandwidths to form a virtual wideband
`channel at a wireless device (e.g., UE). In carrier aggrega(cid:173)
`tion (CA) multiple component carriers (CC) can be aggre(cid:173)
`gated and jointly used for transmission to/from a single
`terminal Carriers can be signals in permitted frequency
`domains onto which information is placed. The amount of
`information that can be placed on a carrier can be deter(cid:173)
`mined by the aggregated carrier's bandwidth in the fre(cid:173)
`quency domain. The permitted frequency domains are often
`limited in bandwidth. The bandwidth limitations can
`become more severe when a large number of users are
`simultaneously using the bandwidth in the permitted fre(cid:173)
`quency domains.
`FIG. 1 illustrates a carrier bandwidth, signal bandwidth,
`or a component carrier (CC) that can be used by the wireless
`device. For example, the LTE CC bandwidths can include:
`1.4 MHz 210, 3 MHz 212, 5 MHz 214, 10 MHz 216, 15 45
`MHz 218, and 20 MHz 220. The 1.4 MHz CC can include
`6 resource blocks (RBs) comprising 72 subcarriers. The 3
`MHz CC can include 15 RBs comprising 180 subcarriers.
`The 5 MHz CC can include 25 RBs comprising 300 sub(cid:173)
`carriers. The 10 MHz CC can include 50 RBs comprising 50
`600 subcarriers. The 15 MHz CC can include 75 RBs
`comprising 900 subcarriers. The 20 MHz CC can include
`100 RBs comprising 1200 subcarriers.
`Carrier aggregation (CA) enables multiple carrier signals
`to be simultaneously communicated between a user's wire- 55
`less device and a node. Multiple different carriers can be
`used. In some instances, the carriers may be from different
`permitted frequency domains. Carrier aggregation provides
`a broader choice to the wireless devices, enabling more
`bandwidth to be obtained. The greater bandwidth can be 60
`used to communicate bandwidth intensive operations, such
`as streaming video or communicating large data files.
`FIG. 2A illustrates an example of carrier aggregation of
`continuous carriers. In the example, three carriers are con(cid:173)
`tiguously located along a frequency band. Each carrier can 65
`be referred to as a component carrier. In a continuous type
`of system, the component carriers are located adjacent one
`
`5
`
`4
`another and can be typically located within a single fre(cid:173)
`quency band (e.g., band A). A frequency band can be a
`selected frequency range in the electromagnetic spectrum.
`Selected frequency bands are designated for use with wire-
`less communications such as wireless telephony. Certain
`frequency bands are owned or leased by a wireless service
`provider. Each adjacent component carrier may have the
`same bandwidth, or different bandwidths. A bandwidth is a
`selected portion of the frequency band. Wireless telephony
`10 has traditionally been conducted within a single frequency
`band. In contiguous carrier aggregation, only one fast Fou(cid:173)
`rier transform (FFT) module and/or one radio frontend may
`be used. The contiguous component carriers can have simi(cid:173)
`lar propagation characteristics which can utilize similar
`15 reports and/or processing modules.
`FIGS. 2B-2C illustrates an example of carrier aggregation
`of non-continuous component carriers. The non-continuous
`component carriers may be separated along the frequency
`range. Each component carrier may even be located in
`20 different frequency bands. Non-contiguous carrier aggrega(cid:173)
`tion can provide aggregation of a fragmented spectrum.
`Intra-band (or single-band) non-contiguous carrier aggrega(cid:173)
`tion provides non-contiguous carrier aggregation within a
`same frequency band (e.g., band A), as illustrated in FIG.
`25 2B. Inter-band (or multi-band) non-contiguous carrier
`aggregation provides non-contiguous carrier aggregation
`within different frequency bands ( e.g., bands A, B, or C), as
`illustrated in FIG. 2C. The ability to use component carriers
`in different frequency bands can enable more efficient use of
`30 available bandwidth and increases the aggregated data
`throughput.
`Network symmetric (or asymmetric) carrier aggregation
`can be defined by a number of downlink (DL) and uplink
`(UL) component carriers offered by a network in a sector.
`35 UE symmetric ( or asymmetric) carrier aggregation can be
`defined by a number of downlink (DL) and uplink (UL)
`component carriers configured for a UE. The number ofDL
`CCs may be at least the number of UL CCs. A system
`information block type 2 (SIB2) can provide specific linking
`40 between the DL and the UL. FIG. 3A illustrates a block
`diagram of a symmetric-asymmetric carrier aggregation
`configuration, where the carrier aggregation is symmetric
`between the DL and UL for the network and asymmetric
`between the DL and UL for the UE. FIG. 3B illustrates a
`block diagram of an asymmetric-symmetric carrier aggre(cid:173)
`gation configuration, where the carrier aggregation is asym(cid:173)
`metric between the DL and UL for the network and sym(cid:173)
`metric between the DL and UL for the UE.
`For each UE, a CC can be defined as a primary cell
`(PCell). Different UEs may not necessarily use a same CC
`as their PCell. The PCell can be regarded as an anchor
`carrier for the UE and the PCell can thus be used for control
`signaling functionalities, such as radio link failure monitor(cid:173)
`ing, hybrid automatic repeat request-acknowledgement
`(HARQ-ACK), and PUCCH resource allocations (RA). If
`more than one CC is configured for a UE, the additional CCs
`can be denoted as secondary cells (SCells) for the UE.
`Carrier aggregation can be used in homogeneous or
`heterogeneous networks. In homogeneous networks, the
`node, also called a macro node, can provide basic wireless
`coverage to wireless devices in a cell. The cell can be the
`area in which the wireless devices are operable to commu(cid:173)
`nicate with the macro node. Heterogeneous networks (Het(cid:173)
`Nets) are used to handle the increased traffic loads on the
`macro nodes due to increased usage and functionality of
`wireless devices. HetNets can include a layer of planned
`high power macro nodes (or macro-eNBs) overlaid with
`
`IPR2019-00047
`Qualcomm 2018, p. 19
`
`

`

`US 10,044,613 B2
`
`5
`layers of small cell nodes or lower power nodes (micro(cid:173)
`eNBs, pico-eNBs, femto-eNBs, or home eNBs [HeNBs])
`that can be deployed in a less well planned or even entirely
`uncoordinated manner within the coverage area ( cell) of a
`macro node. The lower power nodes can generally be 5
`referred to as "low power nodes". The macro node can be
`used for basic coverage, and the low power nodes can be
`used to fill coverage holes, to improve capacity in hot-zones
`or at the boundaries between the macro nodes' coverage
`areas, and improve indoor coverage where building struc- 10
`tures impede signal transmission. HetNets can be used to
`optimize performance particularly for unequal user or traffic
`distribution and improve spectral efficiency (SE) per unit
`area of a cell. HetNets can also achieve significantly 15
`improved overall capacity and cell-edge performance. The
`nodes, such as the macro nodes and/or lower power nodes
`(LPN), can also be grouped together with other transmission
`stations in a Coordinated MultiPoint (CoMP) system where
`transmission stations from multiple cells can transmit sig- 20
`nals to the wireless device and receive signals from the
`wireless device.
`Data (e.g., packets) from a wired network (e.g., Internet)
`can be processed via a protocol stack (PS) at a node ( e.g.,
`LTE eNodeB). The node in a RAN can be coupled to the 25
`Internet via a core network (CN) or an LTE evolved packet
`core (EPC). The EPC can include various core network
`devices, such as a serving gateway (SGW) and a packet data
`network (PDN) gateway (PGW). Core network devices or
`nodes can be in direct communication with each other via 30
`cabling, wire, optical fiber, and/or transmission hardware,
`such a router or repeater. The SGW can provide network
`access for the UEs associated with the RAN. The SGW can
`route and forward user data packets, while acting as a
`mobility anchor for a user plane during inter-eNodeB han(cid:173)
`dovers and as an anchor for mobility between LTE and other
`3GPP technologies. For idle state UEs, the SGW can ter(cid:173)
`minate the downlink data path and triggers paging when
`downlink data arrives for the UE. The SGW can manage and
`store UE contexts, parameters of the IP bearer service, and
`network internal routing information. The SGW can perform
`replication of the user traffic in case of lawful interception.
`The PDN gateway (PGW) can provide connectivity from
`the wireless device to external packet data networks by
`being the point of exit and entry of traffic for the wireless
`device. A wireless device can have simultaneous connectiv(cid:173)
`ity with more than one PGW for accessing multiple PDNs.
`The PGW can perform policy enforcement, packet filtering
`for each user, charging support, lawful interception and
`packet screening. The PGW can act as the anchor for
`mobility between 3GPP and non-3GPP technologies such as
`WiMAX and 3GPP2.
`AUE ( e.g., CA capable UE) can be configured for carrier
`aggregation and support dual connectivity ( e.g., to multiple
`nodes (e.g., eNB)) for a faster and/or more reliable data
`connection. In legacy configurations ( e.g., 3GPP LTE
`releases 10 or 11 ), the protocol stack ( e.g., PDCP, RLC, and
`upper MAC) can be common ( e.g., for a macro cell and
`small cell, such as a remote radio head (RRH)) and the lower
`MAC and PHY can be duplicated for each serving cell, as
`shown in FIG. 4. With the legacy configuration, one RLC
`entity can be used for data transfer, which can simplify data
`processing especially in terms of time sensitive segmenta(cid:173)
`tion (SGMT) and/or automatic repeat request (ARQ), ser(cid:173)
`vice data unit (SDU) reordering, and so forth. For example,
`each data radio bearer (DRB) can be split between two radio
`frequency (RF) transceivers (e.g., MAC/RF 1 and MAC/RF
`
`6
`2) and can be assembled at MAC-RLC service access point
`(SAP) ( e.g., RLC 2) of the UE.
`The data radio bearer (DRB) can be a bearer for the
`internet protocol (IP) packets from the IP layer. A bearer is
`a virtual concept that can define how UE data ( e.g., packets)
`is treated when the data travels across the network. For
`instance, the network might treat some data in a special way
`and treat others normally. Some flow of data might be
`provided guaranteed bit rate while other may have a low
`transfer. A bearer can be a set of network parameters that
`defines specific treatment of data. A signaling radio bearer
`(SRB) can b