281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote LTE Advanced - Carrier Aggregation Home : www sharstechnote com Carrier Aggregation is a special form of LTE technology that enables UE and Network to use more than one carrier frequencies. Actually this is not 2 new concept in LTE. You might have used/heard Dual Carrier in WCDMA HSDPA (HSDPA DC) or similar mode in WiFi (I forgot the terminology in WiFi). Followings are the list of topics to be described in this page. ‘+ Initial Motivation for Carrier Aggregation * Initial Deployment * Overview of Carrier Allocation and Network Architecture + Layer 2 Structure of Carrier Agareaation ‘© E-UTRA CA configurations and bandwidth combination sets defined for intra-band contiguous CA two sub-blocks! © E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA © Test Frequency Table ‘* How a Network know if a UE support Carrier Agareaation 2 * Overall nce of Addin nd Carrier © Evolution path of Carrier Aggregation / Possible Test Plan Initial Motivation for Carrier Aggregation You may be hearing more and more about LTE Advanced these days (approaching the end of 2012) and you may think "Do we really need such a huge bandwidth ? Is the current LTE BW not enough ? Do we have all the technologies mature enough for LTE Advanced Implementation ?” To see the mature implementation of LTE advanced netwark or mobile phone, you should get firm "YES" to following quesitons first, ‘= Is there any major LTE Network Operators who has strong willingness to deploy LTE Advanced Network(Feature) ? ‘+ Are all those components (especially baseband chipsets and RF devices) for LTE advanced device available and mature in the market ? ‘+ Are there any test equipment which are providing the test capability for the device ? ‘As of the end of 2012, T don't think I have firm "YES" to any of these questions. But I am hearing that a couple of LTE network operators will deploy LTE Advanced feature in very near future and some operators has already Supported the feature. I think this is true, but the LTE advanced they talk about at this point is not the full fledged technology and it is mainly about Carrier Aggregation, Does this mean that they already feel the current 20 Mhz LTE bandwidth is not enough ? As far as I know, it is not because of this. Even though the current LTE supports 20 Mhz BW in max, there are only a few network operators who is certified for such a wide bandwidth. The most common bandwidth that network operators has for LTE is 10, Mhz, which means they are not fully utilizing the LTE capability in terms of bandwidth, This is not because of technical restriction, it is purely because of licensing issues for the allocated bandwidth, Even though there is not many Network Operators who has 20 Mhz BW, there are some network operators who has license multiple band (e.g, two separated 10 Mhz BW and two or more 5 Mhz BW). These network operators wants to combine those multiple bands to achieve wide BW (in most case 20 Mhz BW) LTE, It is the initial motivation for LTE ‘Advanced for now and I don't think we will see the fully grown LTE advanced technology in any time soon. We still have a lot of things to be done even for the initial LTE (Release 8 LTE) and this maturing process would take a couple of more years. LTE Advanced will be introduced gradually in parallele to Release 8 LTE, but initial introduction of LTE advanced would be more about "Marketing motivation rather than "Technical motivation’ tipdhwwrwsharetecnnata.comhimlLe_Advanced_ Carrier Aagregation him! 9281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote 1 jal Deployment You may heard from other sources or will see in this page a lot of fancy stories about LTE advanced (like the aggregation of 5 carriers with 20 Mhz BW each, 8 x 8 DL MIMO, 4 x 4 UL MIMO, 1G Data Rate etc). But as I mentioned above, the reality would not be as fancy as you may expect. As of Jan, 2013. The only type of deployment Tam hearing that some network operators would deploy is as follows 1) 2 DL Carriers (mostly 10 Mhz BW each, Inter band) ii) NO UL Subcarriers Following illustration shows some of possible carrier allocations for initial deployment. Be, Secendary Component Cartier: Carries only UserDeta i ‘Uplink Channel: Caries User sta ana PUGH ter aom POG anascG Even this simple configuration there are many things to consider and following is some of the list. What kind of data you would carry on the primary and secondary DL carrier ? Definately both channel can carry PDSCH, How about PDCCH ? Would both DL carry each of its own PDCCH seprately ? or Primary DL Carrier would carry PDCCH for both carrier and the secondary carrier carry only PDSCH ?. Both options are possible and it is upto network implementation, How kind of data you would carry on UL carrier ? ‘You may think there would be no differences in UL carrier if UL does not support multi carrier as in the initial deployment, but it would not be true, There would be no differences in terms of PUSCH, but how about PUCCH? Since UE is getting PDSCHs from two separate carriers, there should be questions of how to send HAR ACK/NACK for each of the PDSCH. Should UE send separate PUCCHs(HARQ ACK/NACK for each DL carriers) or single PUCCH carrying the HARQ ACK/NACK for both channels. Both options are possible in terms of Rel 9/Rel 10 specification, but it is higher possibility to use a single PUCCH for carrying HARQ ACK/NACK for both DL carriers. It means that we will have new PUCCH format for this situation. How to handle PRACH ? Since UE can have possibility of send Uplink to two different carrier and can receive the data from two separate carrier. Possible channels for PRACH procedure can be diverse as shown below. ‘+ PRACH via Primary Carrier and RAR via Primary Carrier eipdhwwrsharetecmnata. commie Advanced_ Carrier Aagregation him! 29281320°7 LTE Advanced Carlee Aggregaton| SrareTechoote ‘+ PRACH via Primary Carrier and RAR via Secondary Carrier ‘+ PRACH via Secondary and RAR via Secondary Carrier = and couple of others. But I guess the first option would be the best candidate since it is easy and is the same as Rel 8 method we are currently using. How to handle handover with dual carrier ? For this, we may also have easy option or tricky option. Tricky option would be to handover the two carrier without any modification from one cell (source cell) to another (destination cell). but this will cause a lot of issues if it is not very carefully implemented, Easy option would be to remove the secondary DL channel before handover and then perform handover and configure the secondary channel in the destination cell. Ff course, it is highly probable to take an easy option for initial deployment. Overview of Carrier Allocation and Network Architecture One of the most important/critical feature in LTE Advanced is that we use multiple carriers in downlink and possible in uplink as well. It may sound simple to use multiple carriers, but in reality, with the introduction of multiple carrier all the possible carrier/resource allocation in uplink and downlink has such a huge combinations as shown below. This is not just a graphicaly complication -:). Just by looking at this illustration, a lot of questions would be boggling in your mind. How to allocated resources (number of RBs) in control channel ? Do we have to have separate HARQ process for each carrier ? or single-aggregated HARQ for the multiple carrier ? What about Uplink side ? How can 1 Schedule the resource for Multiple SC-FDMA (Clustered SC-FDMA) ? etc... These are the topics I have to add later.. For now, just enjoy the illustration and use your imagination for all of these questions. Trying to get the solution based on your imagination would greatly help you to understand 3GPP specification. This is a kind of motivation step for the new study, co - = i ses 3 ° an ZB, Bana Bande case Another aspect of LTE Advanced is network architecture side. One of the key modification of LTE advanced is "Relay Node’ to improve data communication especially on cell boundary and increase cell coverage. Again, I just put the [Link] Advanced_ Carrier Aagregation him! ane2e2017 LTE Advanced - Carrie Aggregation] ShaeTechnote illustrations and I would like you to use your imagination to find the answers to the questions popping up in your mind. Do we need any RRC message or Information element to handle this Relay Node ? How a UE handle the situation as shown for UE C in the following illustration. This UE is getting the similar strength of signals both from eNodeB and Relay Node. Would it be possible to handover between two Relay Nodes ? Would the Relay Node have the same RF capability as eNB ? Would this Relay Node get involved in L1/PHY scheduling as well ? etc. Saye ) a (t is sccessin (CQ) = LY “ e 2 rm " 5 oa m $ ply = (pita pals ee Layer 2 Structure of Carrier Aggregation Many people asked me "Is there any way to direct a specific IP packet to PCC (Mirmary Component Carrier) and another specific IP packet to SCC (Secondary Component Carrier) 2" The Answer is 'No! You may understand why the answer is 'NO' from 2 structure of 3GPP 36.300 as shown below (This figure may look a little too complicated. You will find clearer figure after this). As you may notice here, Carrier Layer Aggregation is, MAC-PHY layer concept and it is not applied to higher layer. ‘< 36,200 Figure 6.4-1 : Layer 2 Structure for DL with CA Configured > eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! ang281320°7 LTE Advanced Carrie Aggregation] ShaeTechnote — Rado Beon “c Seg HC | ARGete |*"| ARQ ete ARQ ate |*"] ARQ ete > - Unicast Scheduling /Priovty Handling sued Mutilexing UE, z Multiplexing UE, | [Faro HAR ARG HaRO| bb rat a op DISCH ——DIASCH DLSCH —DIASCH BCH PCH one, ‘on Cy one, on CC For clarity, let's suppose a case of a Carrier Aggregation with 2 CC(Component Carrier) and each carrier support SISO, Following is overal data path from IP to Physical layer. As you see, from IP through RLC, there is no separate path between PCC and SCC. eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! 59281320°7 LTE Advanced Carlee Aggregaton| SrareTechoote No diferentetion (separation) between PCC and SCC at these layer Unicast Scheduling /Priorty Handling aac Mutilexing UE, cnn cm b 6 sce For clarity, let's suppose a case of a Carrier Aggregation with 2 CC(Component Carrier) and each carrier support MIMO, Following is overall data path from IP to Physical layer. AS you see, from IP through RLC, there is no separate path between PCC and SCC. eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! any281320°7 LTE Advanced Carlee Aggregaton| SrareTechoote DCP ~ No diferentition (separation) between PCC and SCC at these layer Unicast Scheduling /Prionty Handing Mutilexing UE, aac ow eon UG é - Pec sec What kind of Aggregated Carrier (Carrier Combination) is possible ? Now the question you may ask is how can I know which band combination of bands a UE support in terms of Carrier Aggregation ? It is also supposed to be reported to network by the UE via UE Capability Information message. Followings are some of the possible IEs a UE may use depending on its release status. RF-Parameters-v1020 ::= SEQUENCE { supportedBandCombination-r10 SupportedBandCombination-r10 > RF-Parameters-v1090 ::= SEQUENCE { supportedBandCombination-vi090 SupportedBandCombination-v1090 OPTIONAL > RF-Parameters-v1130 ::= SEQUENCE { supportedBandCombination-vi130 SupportedBandCombination-v1130 OPTIONAL > ‘The definition of these IE is described as below in 36.331, Generally it sounds OK. but itis not very clear to me if I 1 into one step deeper. For example, this definition does not clearly explain on which item in the fist ean be a PCC {Primary Component Carrier) and which should be SCC (Secondary Component Carrier). As far as I know, there 1s no priority ofthese items in terme of determining PCC/SCC, meaning eltner one should be allowed to be PCC depending bn situation. But you may see some UE that allows oniy’specific BCC/SCC mapping. bandCombinationListEUTRA : One entry corresponding to each supported band combination listed in the same order as in supportedBandCombination. eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! m9281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote BandCombinationParameters-v1090 : If included, the UE shall include the same number of entries, and listed in the same order, as in BandCombinationParameters-r10. BandCombinationParameters-v1130 :The field is applicable to each supported CA bandwidth class combination (i.e. CA configuration in TS 36.101 Section 5,6A.1 indicated in the corresponding band combination ‘One example of Carrier Combination information in UE Capability Information is as follows. This example shows the UE allows Carrier Aggregation between band 4 and band 17. nonCriticalExtension rf-Parameters-v1020 ‘upportedBandCombination-r10: 1 item Ttem 0 BandCombinationParameters-r10: 2 items Ttem 0 BandParameters-ri0 bandEUTRA-r10: 4 bandParametersUL-r10: 1 item Item 0 CA-MIMO-ParametersUL-r10 ca-BandwidthClassUL-r10: bandParametersDL-r10: 1 item Item 0 CA-MIMO-ParametersDL-r10 ca-BandwidthClassDL-r10: a supportedMIMO-CapabilityDL-r10: twoLayers Item 1 BandParameters-r10 bandEUTRA-r10: 17 bandParametersDL-r10: 1 item Item 0 CA-MIMO-ParametersDL-r10 ca-BandwidthClassDL-r10: a supportedMJMO-CapabilityDL-r10: twoLayers Following Table from 36.101 V11.7.0 (2014-03) shows all the possible (allowed) band combination of inter-band CA case. This list is likely to get extended as time goes on. So try to refer to latest spec. I just put inter-band case since I see only inter-band CA which Is really deployed as of now (Apr 2014). If you are interested in intra-band CA, refer to Table 5.6A.1-1, Table 5.6A.1-3 in 36.101 << 36.101 Table 5.6A.1-1: E-UTRA CA configurations and bandwidth combination sets defined for intra-band contiguous CA > eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! are281320°7 LTE Advanced Carrie Aggregation] ShaeTechnote TRA CA coniguraion [ana ComBTON Se pS ae ae or rsa caer equ) Eutraca | alowed channel | Alowsdchamet | ZS"2 | aggregated | Banowith configuration | bandwidths for carrier | bandwidths for carrier & siwidehs for | Pandwidth r [MH] wiz] mederdits Bt| cute nee ene Nae = a cate “0 0 20 20 a8 CABC se aa 40 0 a EEE = a Fa 20 care ‘2 20 @ 5 “0 : 20 160 16 cage 20 0 5 5 Ta. 5 cazra 1a rn ts 0 CA_38C 18 18 40 0 2 20 20 51078 20 ca 390 3 0 ‘0 2 7 a “0 0 cna 20 a sf 0 2 = a “ : 620 2 2 CA 40D 20 10, 15 2 0 0 ra 2 0 ‘0 20 6 7 re 2 cast 1 2 70.18 ¢o 0 = 6 2 3 1520 3 30 ee Bz aie 501820 20 7 : Fa i108 OTE Tie A cnfauaion 6s an opts band anda CA Dani ass oScoT TS ESAT Uh qeltis ie Musee cir Ghimmemeat cies tr upeemg tet opers sept eeel comes Nov[Link] Fate soto! GO bani comnatona th OS dav an i ands a equal < 36,101 Table 5.6A.1-3: E-UTRA CA configurations and bandwidth combination sets defined for non-contiguous intra- band CA (with two sub-blocks) > eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! a9281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote frequency ae Bandwidth eorae ees bandwidins for cartier | panawiatns tor carrier | [MHZ] et ne me z =a 36.101 Table 5.6A.1- : E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA F-LUTRA CA configuration 1 Bandwidth combination set waxy eurraca | y&. | 14 | 3 | 5 | 1 | 45 | 20 | aggregated | Bancwicth Configuration | UTA | atte | mre | wiz | MHz | MHz | MHz | bandwidth | combination : = = [MHz] re CAAA 5. zee ° ° i Yes_| Yes _|_Yea_| Ves e q 5 Yes_[ Yes 7 Yes_| Yes | Yas | Ves B Yes Yes a t CAAA 4 “es_|_Gs es_| Yes D 7 Yes_[ Yas 1 Yes _| Yes _| Yes | Yes CAIAAIA 7 Yes | ves » 0 1 Yes _| Yes | Yes_| Yes 35 0 ERAS, 76 Yes_|_Yes_| Yes 7 Yea_[_Yea 3 m 76 Yes_| Yes 1 Yes_| Yes | Yas | Ves SALIANIA: 48 Yes ‘Yes Yes % ® 7 Yes_|_Yes_| Yes CA_18.204 a wes [ates % ° 1 Yes_|_Yes_|_Yes_| Yes Cee 21 Yes Yes Yes 2 f 1 Yes_| Yes | Yes_| Yes A 3% ° ca 18264 76 Yes_| Yes_| Yes . 7 Yea_|[Yes a a 26 Yes_| Yes 2__[_Yes_|_Yes_|_Yes_|_Yes_|_Yes_| Ves 0 ° z Yes_| Yes | Yes _| Yes Gee 2 ‘Yes ‘Yes 20 1 ny Yes_| Yas eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! 1019281320°7 LTE Advanced Carrie Aggregation] ShaeTechnote : 2 Yes] Yer | vas [Yer aa 3 ‘Yes ‘Yes a 2 Yer[-Yes| Yar_| Yer cazava [2 ven| Yes 2 Yes-[-Yar|-Yar|-er - » CA_2R-138 i ae : 7 Yee| Yes m = Yes 3 ves {Yes caanta var ss A 2 Yer Ez] Yes ‘Yes a 2 Yee carmen [2 Nes 2 2 Yes Wee] Yar 2 ‘Yes 8 3 Ya [Yes a Yes 2 3 Ves CASES = ‘Yes Yes eo 3 Yes[ Yes|-Yar_|- Ye 3 ‘Yes ‘Yes i 5 3 Yer Yer} ¥a Yes ane 7 ‘Yes ‘Yes ‘Yes £ : 3 Yer [Yas | Yat Bas a ‘Yes ‘Yes es 3 Yas 8 ‘Yes ‘Yes et 3 Yer_| Yes [Yes [Yea pee 3 ‘Yes Yes Yes ES 3 YeYa--ve}-ves1—, 2 Yer [Yas CARAIA 3 Yes Yes Yes ves 40 2 Yas [-Yes {ver} Yer 3 Yep yep ve-{ vet —, % Yee yes | Yar ASKIN 3 ‘Yes Yes 26 ‘Yes Yes 2% 3 Yer[ er | var [Yas cazaaia | fe ae 2» casana [2 ee : vee Z AMARA 4 ‘Yes ‘Yes ‘Yes ‘Yes 30 3 Yer [ Yas t Ya Yes Aga 7 Yes Yes Yes Yes * ere ee eB ® Ye [Vs AARON 4 Yes Yes Yes Yes ‘Yes Yes 30 % Ya Yes i Yer | Ye | ve {ver | ay canta = 7 oa[ Yes m 2 ver 7 Wess canta | velar EB eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! 9281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote a Yes_[ Yes ey Yes_[_Yes_|_ves pa 4 Yes_[ Yes eee 2 Yes_[ Yes gi a Yes | ves | Yes_| Yes 2 Yes | Yes 38 3_| ves_|_ves_[ Yes [Yes CASATA 7 Yes | ves_| Yo a 5 Yes_| Yes CASA 128 2 tees 20 z 3 Yes [Yes CA SAATA + Tee 20 CA. 5A25A 2 Yee | Nes 30 ili ay Yes_[ Yes | ves Yes z Yes_[ Yes | Yes 38 20 Yea | ves ea 7 Yes | Yes | Yes a 20 Yes_|_ves_|_Yes_[ Yes 7 Yes Yes | Yes Yes CALTNPEA, 76 Yes_[Yes_|_Yes 8 3 Yes | ves 20 2 ‘Yes_[ Yes ei aad 3 Yes_[Yes_[_Yes = I Yes_[ Yes 3 Yes | Yes SA BAAOA. a) Yes | ves_| ves [Yes 0 a i Yes_[ Yes CASTE 18 Yes_[ Yes_| Yes ae CALTRBE 2 Yes_[ Ves w < Test Frequency Tables > For the specific test fequencies for each of the band combination, we need to refer to following tables in 36.508 (A lot of tables :) “4 A: A: 7 1: Ls Ls 1 1 1 1“ 1 1 re 1 1 1 1 1 1 1 1 1 1 1 re rf 1 1 1 1 1 re 1 2- 3- 4- 7- 8 9- 0- 1 2- 3- 4 6° 7- Test Frequencies for E-UTRA channel Bandwidth for operating band 1 Test Frequencies for Test Frequencies for Test Frequencies for E-UTRA channel Bandwidth for operating band 5 Test Frequencies for E-UTRA channel Bandwidth for operating band 6 Test Frequencies for E-UTRA channel Bandwidth for operating band 7 Test Frequencies for Test Frequencies for E-UTRA channel Bandwidth for operating band 8 Test Frequencies for E-UTRA channel Bandwidth for operating band 9 : Test Frequencies for E-UTRA channel Bandwidth for operating band Test Frequencies for E-UTRA channel Bandwidth for operating band cAIC CA_3C CALIC Test Frequencies for E-UTRA channel Bandwidth for operating band 2 Test Frequencies for E-UTRA channel Bandwidth for operating band 3 : Test Frequencies for E-UTRA channel Bandwidth for operating band 4 : Test Frequencies for E-UTRA channel Bandwidth for operating band Test Frequencies for E-UTRA channel Bandwidth for operating band : Test Frequencies for E-UTRA channel Bandwidth for operating band Test Frequencies for E-UTRA channel Bandwidth for operating band : Test Frequencies for E-UTRA channel Bandwidth for operating band E-UTRA channel Bandwidth for operating band E-UTRA channel Bandwidth for operating band 20 E-UTRA channel Bandwidth for operating band 21 E-UTRA channel Bandwidth for operating band 22 E-UTRA channel Bandwidth for operating band 23 E-UTRA channel Bandwidth for operating band 24 E-UTRA channel Bandwidth for operating band 25 E-UTRA channel Bandwidth for operating band 26 E-UTRA channel Bandwidth for operating band 27 + Test Frequencies for Test Frequencies for : Test Frequencies for + Test Frequencies for + Test Frequencies for Test Frequencies for + Test Frequencies for Test Frequencies for 1 1 1 1 1 1 1 1 1 Test Frequencies for 1 1 1 1 1 et 1 1 eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! 10 it 12 13 14 7 18 19 rao281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote © Table [Link].27A+1 : Test Frequencies for CA_27B '* Table [Link].28-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 28 * Table [Link].29-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 29 + Table [Link].31-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 31 © Table 4.3.1,2.1-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 33 © Table [Link].2-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 34 Table [Link].3-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 35 * Table [Link].4-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 36 + Table [Link].5-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 37 * Table [Link].6-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 38 + Table [Link].6A-1 : Test Frequencies for CA_38C + Table [Link].7-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 39 + Table [Link].7A-1 : Test Frequencies for CA_39C © Table [Link].8-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 40 + Table [Link].84-1 : Test Frequencies for CA_40C + Table [Link].9-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 41 ‘© Table 4.3.1,2.9A-1 : Test Frequencies for CA_41C '* Table [Link].10-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 42 + Table [Link].11-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 43 Table [Link].12-1 : Test Frequencies for E-UTRA channel Bandwidth for operating band 44 One of the UE capability information that may confuses you would be following IE. This IE shows you which band are supported by the UE in terms of single cartier. It is not about Carrier Aggregation, rf-Parameters supportedBandListEUTRA: 4 items Ttem 0 ‘SupportedBandEUTRA bandEUTRA: 2 10... halfDuplex Item 1 ‘SupportedBandEUTRA bandEUTRA: 4 (0,. vs. halfDuplex Item 2 ‘SupportedBandEUTRA bandEUTRA: 5 Ov. ans halfDuplex: Item 3 ‘SupportedBandEUTRA bandEUTRA: 17 +0 halfDuplex: False False False False How a Network know if a UE support Carrier Aggregation ? ‘The most important thing you have to pay attention in UE Capability Information is CA Band combination as specified in RRC message as shown below. eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! sai9281320°7 LTE Advanced Carrie Aggregation] ShaeTechnote Table 5.64.12: EUTRA CA contiguratione and bendwidth combination sets defined for intor band cA Eameace | £0TEA | sanne | swe | sane | somne | rsaez | 20mm | areas | combina in) NOTE TCA Gariguaion SET 5 SnGnnien Tan Spring Bd sds CADSR SSE HOORET TOE NOTES, forthe suppored GO bendwadhncorionatane, oe OO dowrirkand vp bandwidts are equal S-rfParameters-v1020 (6 supperedsenacomonaton0 2 ute ent catandwian cesses cerccenratintaaneten 19 (5. SandParameters-10 e |= — a7? ee @-baneParametersuLri0 7 x sears 7 Chao Parmeter 10 2 4 ae Sapper eeNOCepaat UCT eee eta fps} re G. banoParametersDL-10 1 CAMINO-ParametersDL-+10 1 ca-HananianciassDLr10 a = BandParemeters-110 FourLapers egniLavers ‘bandPerameteroUL-r10 anaParametersDL-r0 1 5 CAMINO-PerametersDL+10 1 ce-danqmamnciassDL-r10 a supporiecilIMO-CapabiliyDL-+10 ‘woLayers ‘Another important part is featureGroupIndicator (FGI) for r10. It has following items. eaturecroupindte110-r30; 00000000 [bit Tength 32, 0000 6000 9000 9000 0000 0000 0000 0000 decimal value 0) 0. ‘= tndicator 101: oaRS with ac (orthogonal cover code) and SCH (Sequence group hopping) disabling - Not supported 8 = Indicator 102: Trigger type 1 SRS (aperiodic 55) transmission (Up to X ports) ~ Not supporved indicator 103: POSCH 79 when up to 4 CSI reference signal ports are configures - Not supported Indicator 104: POScH IMB for 100 when 8 CSI reference signal ports are configured ~ Rot supported Indicator 105: PUCCH RN2-O when POSCH THB Is configured and R21 when POSCH TM and up to 4 CSI reference signal ports are configured ~ Not supported indicator 106: PUCCH RYD-1 when POSCH TN and & CSE reference signal pores are configured - Not supported Indicator 107: PUSCH 2-0 when POSCH TH is configured and RAZ-2 when POSCH THB and Up to 4 CSI reference signal ports are configured - Not supported indicator 108: PUSCH ®Y2-2 when POSCH TMD and & CSE reference signal ports are configured - Not supported indicator 109: PUCcH RY-2 ndicator 10: PUCCH RI-1 sutnede 2 — Not indicator 121: Measurement reporting trigger Event AS - Not supporced (0... = Indicator 112: sceTl addition within the Handover to CUTRA procedure ~ Not supported 0... = indicator 113: Trigger type 0 SRS (periodic SRS) transmission on X Serving Cells - Not supported 0.. = Indicator 114: Reporting of both UIRA CPIGI RSCP and Ec/NO in a Measurement Report - Not supported 0. = Indicator 15: Time domain CIC RLA/ARM / TCIC RAW / TEIC CSI measuresent SF restriction for the serving ceTl / neighbour ceTIs - Not supporved 0 = indicator 116: Relative transmit phase continuity for spatial multiplexing in UL - Not supported Overall Sequence of Adding a Second Carri eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! wo281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote QB ee ANB op ONBce CNB sco UE xc UEscc E FRC Connection Reconfiguration u @) - HARQ ACK (2) T . ww = e =< 08 Sk (Scheduling Request) Bee ae nm (a) Cogid (s) RRC Connection Reconfiguration Complete (6) —_ + MAC CE (Activation) (ca) psc (8) Following is an example for RRC Connection Reconfiguration for LTE advanced (Step 1). I just enabled all IE on ASN to give you full details of parameters, but it reality the implementation would start with very limited set of parameters enabled and leaving large portions of parameter to some 3GPP default or hardcoded configuration based ‘on aggrement between UE maker and Network Operator. First part you have to pay attention to this sample RRC message is sCellToAddModList-r10 which is for adding the SCC and next important thing is pucch-ConfigDedicated-v1020 which Is for defining uplink control channel for reporting Ack/Nac for aggregated Carrier. —reeconnectionReconFiguration-r& ::= SEQUENCE [000101] -measconfig ::= SEQUENCE OPTIONAL :omit -mobiTityControlinfo ::= SEQUENCE OPTIONAL: Omit -dedicatedinfonasList.::= SEQUENCE OF OPTIONAL:Omit radioResourceconfignedicated ::= SEQUENCE [000101] OPTZONAL:EXist | +-srb-ToaddModL ist ::= SEQUENCE OF OPTIONAL :ort | -drb-ToaddModL ist ::= SEQUENCE OF OPTIONAL ont srdrb-ToReleaseList ::= SEQUENCE OF OPTIONAL omit ‘s-mac-mainconfig ::= CHOICE [explicitvalue] OPTIONAL:Exist xplicitvalue ::= SEQUENCE [000] NI-ScH-Config ::= SEQUENCE OPTIONAL:Omit irx-ConFig ::= CHOICE OPTIONAL: omit imealignmentTimerbedicated ::= ENUMERATED [infinity] phr-Config ::= CHOICE OPTIONAL:omit -S-EXTENSION = SEQUENCE [01] S-VERSTON-BRACKETSL ::= SEQUENCE OPTTONAL:Omit S-VERSTON-BRACKETS? ::= SEQUENCE [1] OPTIONAL: Exist t-mac-Mainconfig-v1020 :!= SEQUENCE [111] OPTIONAL:Exist ‘4-scelIbeactivationTimer-ri0 ::= ENUMERATED [rf16] OPTIONAL:Exist eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! 18192e2017 LTE Advanced - Carrie Aggregation] ShaeTechnote im s-extendedase-sizes-rl0 ::= ENUMERATED [Setup] OPTIONAL:Exist 4-extendedPHa-rl0 ::= ENUMERATED [setup] OPTIONAL :Exist Sps-Config ::= SEQUENCE OPTIONAL:omit physicalconfigoedicated ::= SEQUENCE [0000000000] OPTIONAL: Exist. pdsch-Configdedicated ::= SEQUENCE OPTIONAL:onit -pucch-Configdedicated ::= SEQUENCE OPTIONAL:omit -pusch-Configdedicated ::= SEQUENCE OPTIONAL:Omit uplinkPonerControlDedicated ::= SEQUENCE OPTIONAL :omit tpc-POCCH-ConFigPUCCH ::= CHOICE OPTIONAL: Omit tpc-POCCH-ConfigPUSCH ::= CHOICE OPTTONAL:omit ~cqi-Reportconfig ::= SEQUENCE OPTTONAL Omit soundingRS-UL-Configbedicated ::= CHOICE OPTIONAL :omit || #-antennarnfo ::= CHOICE OPTIONAL :omit | | 4-Schedulingkequestconfig ::= CHOTCE OPTIONAL :omit | | #-ExreNszon ::= SeQueNce [010] || 4-VERSION-ERACKETSI. ::= SEQUENCE OPTIONAL Omit [| s-VERSION-BRACKETS2 ::= SEQUENCE [00000111111] OFTTONAL Exist 11 | ssantennaznfo-r10 ::= CHOICE OPTIONAL:omit i i 1 im im s-antennainfolL-r10 ::= SEQUENCE OPTIONAL :omit S-cif-Presence-r10 ::= BOOLEAN OPTIONAL :onit $-€81-RS-ConFig-r10 ::= SEQUENCE OPTIONAL :ont +-pucch-ConFigdedicated-v1070 ::= SEQUENCE [1111] OPTIONAL :exist | +-pucch-Format-ri0 ::= CHOICE [channeTselection-r10] OPTIONAL: Exist | 4-channelselection-r10 ::= SEQUENCE [1] | 4-nLPUCCH-AN-CS-r10 ::= CHOICE [Setup] OPTIONAL:EXist | tesetup ::= sequence i $-RIPUCCH-AN-CS-List-r10 ::= SEQUENCE OF SIZE(1..2) [2] i 4-NIPUCCH-AN=CS-r10.::= SEQUENCE OF SIZEC1..4) [4] i | 4-25 INTEGER (0, .2047) [10] i | 4 22 INTEGER (0.2047) [11] i | + c= INTEGER (0.2047) [12] i i i i i i i | s-cqi-Reportconfig-rl0 ::= SEQUENCE OPTIONAL :omit i i | 4-2 INTEGER (0. .2047) [13] 4-NIPUCCH-AN-CS-r10 := SEQUENCE OF SIZE(L..4) [4] 4+ :2= INTEGER (0.2047) [10] 4. i= INTEGER (0.2047) [11] 4+ t= INTEGER (0.2047) [12] i t= He INTEGER (0.2047) [13] -4-twoantennaportactivatedPUCcH-Formatlalb-r10 ::= ENUMERATED [true] OPTIONAL: Exist 4-simuTtaneousPUCCH-PUSCH-rl0 ::= ENUMERATED [true] OPTIONAL:Exist 4-nIPUCCH-AN-RepPl-ri0 ::= INTEGER (0..2047) [0] OPTIONAL:Exist pusch-configoedicated-v1020 ::= SEQUENCE [000] OPTIONAL :Exist ‘t-betaoffsetMC-r10 ::= SEQUENCE OPTIONAL:Omit 4+-grouplioppingoi sabled-ri0 ::= ENUMERATED OPTIONAL:onit 4-dars-i thocc-Activated-r20 ::= ENUMERATED OPTIONAL: Oni t -schedulingRequestconfig-v1020 ::= SEQUENCE [0] OPTIONAL:Exist “4-Sr-PUCCH-ResourcerIndexP]-r10.::= INTEGER OPTIONAL :onit soundingRS-UL-Configoedicated-v1020 ::= SEQUENCE OPTIONAL :Exist ‘4-srs-AntennaPort-rl0 ::= ENUMERATED [and] soundngRS-UL-Configdedi catedaperiodic-ri0 | 4-setup :2= SEQUENCE [11] | #-srs-Configtndexap-ri0 ::= INTEGER (0..31) [0] | 4-srs-configapocr-Format4—ri0 ::= SEQUENCE OF SIZE(1..3) [1] OPTIONAL: exist || 4-SRs-Configap-ri0. ::= SEQUENCE || 4esrs-antennaportap-r ENUMERATED [an}] || t+srs-Bandwidthap-r20.::= ENUMERATED [bw0] | | +-freqponainpositionap-ri0 ::= INTEGER (0..23) [0] od ro i i ‘CHOICE [setup] OPTIONAL :Exist 4-transmissionconbap-ri0.::= INTEGER (0..1) [0] S-cyclicshiftap-rl0.::= ENUMERATED [cs0] 4-srs-Activateap-rl0 ::= CHOICE [release] OPTIONAL:EXist terelease 11= NULL UuplinkPowercontrolbedicated-vi020 ::= SEQUENCE [11] OPTIONAL:Exist s-deltaTx0-of fsetListPUCCH-r10 = SEQUENCE OPTTONAL:Exist | +-deltarxo-of fsetPUCCH-Formatl-r10.::= ENUMERATED [a0] del taTxD-of fsetPUCcH-Formatialb-ri0 ::= ENUMERATED [80] de] tatxD-of fsetPuCcH-Format22a2b-r10 ::= ENUMERATED [480] eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! 19281320°7 LTE Advanced - Carrie Aggregation] ShaeTechnote || s-dettarxo-of fsetPuccH-Format3-r10 ::= ENUMERATED [80] 1 | [| +8xteNston ::= sequence || 4-psRs-offsetap-r10 ::= INTEGER (0..15) [0] OPTIONAL :Exist || +-VERSION-BRACKETS3 ::= SEQUENCE OPTIONAL :Omit -A-EXTENSION : = SEQUENCE [00] -VERSION-BRACKETSL ::= SEQUENCE OPTIONAL omit -VERSTON-BRACKETS2 ::= SEQUENCE OPTIONAL :Onit 4+-securityConFigho ::= SEQUENCE OPTIONAL:omit noncriticalextension ::= SEQUENCE [Oi] OPTIONAL:Exist Tatenoncriticalextension ::= OCTET STRING OPTIONAL: Omit noncriticalextension ::= SEQUENCE [001] OPTTONAL Exist otherconfiger9 ::= SEQUENCE OPTIONAL: omit -Fullconfig-r9.::= ENUMERATED OPTIONAL: omit noncriticalextension ::= SEQUENCE [010] OPTIONAL Exist, Cel TToReleaseList-rl0.::= SEQUENCE OF OPTIONAL:0nit +-sCelTToadéModL ist-r10 ::= SEQUENCE OF SIZECL..maxSceT1-r10[4]) [1] OPTIONAL :exist | 4-ScelTToaddMod-r10 ::= SEQUENCE [111] | qescelltndex-r10.::+ INTEGER (1.47) [1] 4-cellidentification-r10 ::= SEQUENCE OPTIONAL :Exist | +-physceT11d-ri0 ::= INTEGER (0.503) [2] | 4-dl-carriersreq-r10 :1= INTEGER (0. .maxEARFCN[65535])_ [5790] 4-radionesourceconfigconmonscell-r10 ::= SEQUENCE [0] OPTTONAL:Exist | +-nonut-configuration-ri0 ::= SEQUENCE [00] | 4-d1-Bandwideh=r10 ::= ENUMERATED [nS0] | 4-antennaznfocommon-ri0.::= SEQUENCE | | 4-antennaportscount ::= ENUMERATED [an2] | +-mbsfr-subframeconfiglist-r10 ::= SEQUENCE OF OPTIONAL: omit | +phich-config-r10 ::= SEQUENCE || 4-phich-puration ::= ENUMERATED [normal] | 4-phich-Resource ::= ENUMERATED [onesixth] | +-pdsch-configconmon-ri0.::= SEQUENCE i i i | +-referencesignalpower ::= INTEGER (-60..50) [21] | 4-peb t= INTEGER (0.3) [1] t-tdd-Config-r10.::= SEQUENCE OPTIONAL :omit -ul-ConFiguration-r0. ::= SEQUENCE OPTTONAL :omit EXTENSION ::= SEQUENCE ‘radionesourceconfigbedicatedsceT1-r10 ::= SEQUENCE [1] OPTIONAL:Exist physical Configoedicatedscell-r10 ::= SEQUENCE [11] OPTIONAL:Exist nonU.-Configuration-r10.::= SEQUENCE [1111] OPTIONAL:Exist | +-antennatnfo-ri0 ::= SEQUENCE [1] OPTIONAL:Exist | 4-transmissionode-ri0 ::= ENUMERATED [tm3] | #-codebooksubsetkestriction-ri0 ::= BIT STRING SIZE(ALIGNED) [00] OPTIONAL :Exist | +-ue-Transmitantennaselection ::= CHOTCE [release] s-release :!= NULL crosscarrierSchedul ingconfig-ri0 ::= SEQUENCE OPTIONAL:Exist s-schedulingcellinfo-rl0.::= CHOICE [own-r10] $-oun-r10 ::= SEQUENCE 4-cif-presence-rl0 i= BOOLEAN [FALSE] esi-RS-Config-r10 ::= SEQUENCE [11] OPTIONAL:Exist #-€S1-RS-r10 i= CHOICE [setup] OPTIONAL :Exist | ¢-setup :2= SEQUENCE | +antennarortscount-r10 ::= ENUMERATED [ant] i i 1 S-resourceconfig-rl0 ::= INTEGER (0..31) [0] s-subframeconfig-r10 ::= INTEGER (0..154) [0] 4-p-C-r]0 :1= INTEGER (-8..15) [-8] -zeroTxPonercsT-RS-r10 ::= CHOICE [setup] OPTIONAL :Exist s-setup i= SEQUENCE 4-zeroTxPowerResourceconFighist-r10 ::= BIT STRING SIZ&(16) [0000000000000000] $-zeroTxPowerSubfraneconfig-rl0 ::= INTEGER (0. 154) [0] pdsch-Configoedicated-rl0 ::= SEQUENCE OPTIONAL :Exist t-pea ::= ENUMERATED [48-3] -ul-configuration-ri0 ::= SEQUENCE [1111111] OPTZONAL:Exist t-antennatnfoUL-r10 ::= SEQUENCE [11] OPTIONAL:Exist | +-transmissionModeUt -r10 ::= ENUMERATED [tml] OPTIONAL :Exist i 4-fourantennaPortActivated-r10 ::= ENUMERATED [setup] OPTIONAL :Exist i i i i i i i i i i i i i i i i i i i i i i I i i i i i SEQUENCE [11] OPTIONAL :Exist ~pusch-Configdedicatedsce11-r10 eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! amg281320°7 +-grouphoppingoisabled-r10 +-dnrs-withocc-activated-ri0 4-p0-UE-PUSCH-r10 ::= INTEGER 4-deltancs-enabled-r10 | +-accumilationenabled-ri0 =: | +-pses-offset-r10 ::= INTEGER | +-psks-oF fsetap-ri0 | 4-Filtercoefficient- 10 +-cgi-Reportconfigscel1-r10 | +-cqi-Reportodeaneriadic-ri0 | ¢-nomppscH-RS-EPRE-offset-ri0 +-cqi-Reportreriodicscell-ri0 setup ::= Sequence [0000] +-cqi-pmi -configiadex #1 | 4-esi-ReportMode-ri0 4-ri-configrndex egi-Mask-r3 4-csi-configindex-ri0_ =: +-pwi-RT-Report-ri0 sound ngkS-Ut-ConFigde s-setup t= SEQUENCE ‘+-Sr's-Bandwidth 4-srs-Hoppinggandwidth +-FreqoonainPosition s-duration ::= 4-sr's-confiigindex 4-transmi ssfonconb seyelicshife 2 i i i i i || +-widebandear-~ i i i i i | 4-srs-antennarort-ri0 S-setup ::= SEQUENCE [11] 4-srs-Configindexap-r10 ::= | 4-sas-configap-r20 4-sr's-gandwidthap-r10 s-cyclicshifeap-ria s-srs-activateap-r10 s-release :1= NULL EXTENSION i= SEQUENCE EXTENSION ::= SEQUENCE EXTENSION 1:= SEQUENCE 1 i 4-uplinkrowercontrolpedicatedscel1-r10 i i | ¢-pathlossreferencelinking-r10 +-cqi-PUCCH-Resourcemndex- 4-cqi-Formatindicatorperiodic-r10 0 t= SEQUENCE [0] 4-simultaneousackNackandcar +-soundingts-UL -configbedicated- = ENUMERATED [and] +-soundingas-UL-configoedicatedaperiodic-ri0 : 4-Srs-confighpocr-Format4-r10 : SEQUENCE 4-srs-antennaPortap-rl0 + i i | 4-Freqoonainposi tfonap-r10 | 4-transmissionconbap-ri0 i LTE Advanced - Carrie Aggregation] ShaeTechnote ‘= ENUMERATED [true] OPTIONAL :Exist ENUMERATED [true] OPTIONAL :Exist EQUENCE [11] OPTIONAL Exist (8.7 C8] ENUMERATED [en0] BOOLEAN [FALSE] (0.15) [0] INTEGER (0.-15) [0] OPTIONAL:Exist ENUMERATED [FcO] OPTIONAL: Exist ENUMERATED [pce] SEQUENCE [111] OPTIONAL: exist ENUMERATED [rm2] OPTIONAL :€xist TEGER (-1..6) [1] ‘CHOICE [Setup] OPTIONAL :Exist r10 4-cqi-PUCCH-ResourcezndexPl-r10 INTEGER (0.1184) /= INTEGER OPTIONAL Omit INTEGER (0.1023) [0] (worce [widebandcar-r "= ENUMERATED OPTIONAL: Oni t ‘= INTEGER OPTIONAL Omit BOOLEAN [FALSE] ‘CHOLCE OPTIONAL: nit ENUMERATED [setup] OPTTONAL:Exist ated- 10 i= CHOICE [setup] OPTIONAL :Exist = ENUMERATED [bwO] P= ENUMERATED [hbwO0] INTEGER (0..23) [0] BOOLEAN [FALSE] = INTEGER (0.-1023) [0] = INTEGER (0.-1) [0] ENUMERATED [cs0] ‘vi020 ::= SEQUENCE OPTIONAL Exist CHOTCE [setup] OPTIONAL: Exist INTEGER (0..31) [0] = SEQUENCE OF SIZE(1,.3) [1] OPTIONAL: Exist ENUMERATED [ant] NUMERATED [bw0] INTEGER (0..23) [0] INTEGER (0..1) [0] ENUMERATED [c50] CHOICE [release] OPTIONAL :Exist n path of Carrier Aggregation / Possible Test Plan It's already been over an year since the first LTE-A was deployed since July 2013 in Korea and now it is getting spreaded wider. I tried to list up possible evolution path of LTE-A development in terms of chipset development ‘aspect and UE development. This can be a big picture of test plan. I would be good practice if you think on your own about why we need these test and what kind of challenge UE (or chipset) should overcome to pass each of these test, You don't have to get the answers to your question.. about a lot of details. Just think about it as much as possible and it would let you think + [Link] Aggregation - SISO, Cat 3, PUSCH enabled : HARQ Ack/Nack is carried by PUSCH + [Link] Aggregation - SISO, Cat 3, PUSCH diabled : HARQ Ack/Nack is carried by PUCCH Format 1b eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! swi9281320°7 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 2 CC Aggregation 3 CC Aggregation 3 CC Aggregation Format 3 3 CC Aggregation PuscH 3 CC Aggregation PUCCH Format 3 = [Link] Aggregation = 3CC Aggregation LTE Advanced - Carrie Aggregation] ShaeTechnote ~ SISO with CST Report - Periodic - SISO with CSI Report - Aperiodic ~ SISO, Handover for SCC Change = SISO, Handover for PCC Change ~ SISO, Handover for both SCC and PCC Change - 2x2 MIMO, Cat 3, PUSCH enabled ; HARQ Ack/Nack is carried by PUSCH - 2x2 MIMO, Cat 3, PUSCH diabled : HARQ Ack/Nack is carried by PUCCH Format 1b - 2x2 MIMO, Cat 3, 40 Mhz Aggregated BandWidth, 200 Mbps Throughput at IP layer - SISO, Cat'4, PUSCH enabled : HARQ Ack/Nack is carried by PUSCH ~ SISO, Cat 4, PUSCH diabled : HARQ Ack/Nack is carried by PUCCH Format 1b - 2x2 MIMO, Cat 6, MIMO, 20 Mhz Aggregated Bandwidth, 150 Mbps Throughput at IP layer - 2x2 MIMO, Cat 6, MIMO, 40 Mhz Aggregated Bandwidth, 300 Mbps Throughput at IP layer -™8 -™9 - SISO, Cat 6, 30 Mhz Aggregated BW, PUSCH enabled : HARQ Ack/Nack is carried by PUSCH - SISO, Cat 6, 30 Mhz Aggregated BW,PUSCH diabled : HARQ Ack/Nack is carried by PUCCH = 2x2 MIMO, Cat 6, 30 Mhz Aggregated BW, PUSCH enabled : HARQ Ack/Nack is carried by - 2x2 MIMO, Cat 6, 30 Mhz Aggregated BW, PUSCH diabled : HARQ Ack/Nack is carried by = 2x2 MIMO, Cat 6, 40 Mhz Aggregated BW = 2x2 MIMO, Cat 6, 60 Mhz Aggregated BW o LTE Advanced - Overview [Link] eipdhwwrsharetecmnata. commie Advanced_ Carrer Aagregation him! s99