The Secondary Cell
(SCell) Addition, Release, and Reconfiguration (Modification) are RRC’s responsibility. RRC
configures SCell for CA capable UEs only. RRC’s functionality pertaining to
Carrier Aggregation is discussed in this post.
In order for the UE to receive data (PDSCH/PDCCH) on SCell, it has to be activated which is different from configuring the SCell. This activation is done via MAC Control Element.
Activation/Deactivation of SCells will be discussed in detail in further posts.
The addition of
SCells is performed only when AS security has been activated.In order for the UE to receive data (PDSCH/PDCCH) on SCell, it has to be activated which is different from configuring the SCell. This activation is done via MAC Control Element.
After Configuring/Adding
the SCell, the SCell is initially in deactivated state. When SCell is Modified, the UE
does not change the activation status of the concerned SCell.
During Handover, if
the same SCell is in use in the target PCell (i.e., SCell is not released
during Handover), the SCell in the target Cell in initially in the deactivated
state.Activation/Deactivation of SCells will be discussed in detail in further posts.
SCell
Addition/Modification
SCells can not be added/configured
at the time of RRC Connection establishment i.e., there is no provision for
SCell addition in the RRC Connection Setup message.
Upon the completion
of AS security, the SCell may be added either blindly or after receiving
measurement report from the UE indicating that the cell on the carrier
frequency used for the SCell is above certain threshold.
SCell is added to the
PCell or to a set of serving cells through ‘RRC Connection Reconfiguration’
procedure.
E-UTRAN uses IE sCellToAddModList in RRCConnectionReconfiguration message to
add the SCell.
At the time of SCell
addition, the eNodeB sends the following information to the UE via RRCConnectionReconfiguration message, a
few of which are optional.
SCellIndex:
This is used to identify/address the SCell that is being
configured/reconfigured/released. If the received SCellIndex is part of the UE’s configuration already, then the UE
considers the procedure as SCell Modification. Else if the
received SCellIndex is not part of
the UE’s configuration, then the UE should consider the procedure as SCell
Addition. Based on the UE’s capability, at most four SCells can be
configured but the SCellIndex can
take values from 1 to 7.
cellIdentification: This
is mandatory at the time of SCell Addition and shouldn’t be present at the time
SCell Modification. cellIdentification consists
of Physical Cell Identity and Downlink Carrier Frequency (EARFCN).radioResourceConfigCommonSCell: This is a big structure of IEs which is mandatory at the time of SCell Addition and shouldn’t be present if the concerned SCell is being Modified.
When adding a new
SCell, radioResourceConfigCommonSCell
is used for sending all required system information of the SCell i.e. while in RRC_CONNECTED
mode, UEs need not acquire broadcasted system information directly from the
SCells.
radioResourceConfigCommonSCell
contains
downlink configurations such as Downlink Bandwidth, Number of Antenna Ports,
List of MBSFN subframe Configurations, PHICH Configuration, PDSCH common
configuration, TDD configuration (in case of TDD) etc..
In case of SCells
with configured uplink (UL CA), radioResourceConfigCommonSCell
contains uplink information such as Uplink Bandwidth, Uplink Carrier
Frequency, Uplink Power Control (Common) Information, common information of
physical channels, SRS common information etc…
radioResourceConfigDedicatedSCell:
This
is another big structure of IEs which is mandatory at the time of SCell
Addition and is optional otherwise. It contains UE specific (dedicated)
configurations for SCell.
radioResourceConfigDedicatedSCell
contains downlink dedicated configurations such as information related to
Transmission Mode for the SCell, Cross Carrier Scheduling configuration, SCell CSI
reference signal information, SCell PDSCH dedicated configuration etc…
E-UTRAN might
configure the UE with uplink dedicated configuration as well. This is mandatory
in case of UL CA where as it is optional for DL CA. It contains information
such as Uplink Transmission Mode for SCell, Uplink dedicated Power Control
information, CQI Reporting configuration for SCell, SCell’s dedicated SRS
configuration etc…
See an example RRCConnectionReconfiguration message for
SCell Addition below. As explained above, for an SCell, EUTRAN provides, via dedicated signalling, all system information relevant for operation in RRC_CONNECTED when adding the SCell (radioResourceConfigCommonSCell).
Upon a change of the
relevant system information of an already configured SCell, the E-UTRAN
releases and subsequently adds the concerned SCell, which may be done with a
single RRCConnectionReconfiguration
message (sCellToReleaseList and sCellToAddModList are used).
The SI parameter values
configured via dedicated signaling may be different than the ones broadcasted
in the SIs of the concerned SCell.
Upon receiving in RRCConnectionReconfiguration message the
UE first executes SCell Release
command (if included in the message) before executing any SCell Addition
Command.
At intra-LTE
handover, RRC can also add, remove, or reconfigure SCells for usage with the
target PCell. Some of the possible scenarios (considering only one SCell) are
given below.
― SCell is already
configured in the source PCell and the SCell is left modified/ unmodified i.e.,
same SCell is used even in the target PCell.
― SCell is already
configured in the source PCell and the SCell is left released during handover. i.e., release of the existing SCell during handover
― SCell1 is
configured in the source PCell and during the handover, SCell1 released and a
new SCell (SCell2) is configured for use in the target PCell i.e., change of
SCell during handover.
― SCell is not
already configured in the source PCell and an SCell is configured during
handover for use in the target PCell.
― SCell is not
already configured in the source PCell and an SCell is added during
handover for use in the target PCell.
― SCell is already
configured in the source PCell and UE receives handover command to handover to
configured SCell i.e., Handover to SCell. In this case, RRCConnectionReconfiguration message contains SCell Release and
also mobilityControlInfo containing carrierFreq and phyCellId which are same as that of
SCell.
― SCell is already
configured in the source PCell and UE receives handover command to handover to
configured SCell and a new SCell is added whose frequency is same as that of
source PCell i.e., Swapping PCell with SCell and vice versa. In this case, RRCConnectionReconfiguration message
contains SCell Release (SCell1) and also mobilityControlInfo
containing carrierFreq and phyCellId which are same
as that of SCell1, SCell Addition whose carrierFreq and phyCellId are same as that of source
PCell.
SCell can also be
added during Handover from another RAT (e.g. GERAN or UTRAN) to E-UTRAN.
SCell
Release
SCell is removed from
PCell or from a set of serving cells through ‘RRC Connection Reconfiguration’ procedure.
E-UTRAN uses IE sCellToReleaseList in RRCConnectionReconfiguration message to
remove/release an already configured SCell.
UE should release all
the configured SCells in case if, RRC Connection Re-establishment procedure is
initiated (obviously on PCell).Reference: 3GPP TS 36.331 and 36.300
Thanks for sharing information.I like this post very much.
ReplyDeletehttps://gelbattery.wordpress.com/
Hi Kumaraswamy,
ReplyDeleteThere are 4 scell (1,2,3,4) and If no.2 is released then will the scell-Index maintained at the UE will be re-arraged in proper order or will it remain same (1.3.4) .....?
After sCell (=2) is released, the result will be 1, 3 and 4
DeleteThanks Kumar,
DeleteIn Scell release - Do we need to make the data elements in the structure equal to 0 (or) will it free the memory for that scell-Index structure...?
If the procedures for sCell release (in 36.331 and 36.321 are followed correctly, I think no need to take care of freeing up memory.
DeleteHi Kumaraswamy,
ReplyDeleteAs you told there are two structures:
- radioResourceConfigCommonSCell
- radioResourceConfigDedicatedSCell
While I receive this structures from eNB, Do I need to check the data inside the structure (elements of the structure) to copy into our local structures? or will the elements will surely be present .....?
There are some optional and some mandatory elements in these structures. While storing, I think you should be checking the conditional requirements/presence of each IE/elements
DeleteHi Kumar Swamy - scell is "at first" added only blindly (i.e. manual configuration by operator) or after doing some measurments . What is the criteria that decides when a scell is to be added ? I think it is statically done at first without using any measurments and after addition scell's usage is subjected to DL data requirement , UE measurments of Channel quality in scell and coverage criteria etc.It is not like if a scell is above a certain threshold in quality then only it can be added . it is for it's activation I guess ?
ReplyDeleteThe sCell addition/release can be blind, but usually it is based on measurements. No point in adding an sCell and making UE moniter/report it even it doesn't exists. First thing for the eNodeB is to know that the UE can see the sCell with acceptable channel quality levels.
DeleteIf sCell is always added blindly, then no need to have two separate procedures for addition and activation.
The activation of sCell usually is based on data requirement.
I hope this clarifies.
hello
ReplyDeleteCan i ask you how to configure CA in Atoll, I need Secondary cell activation threshold but i don't find it in atoll neither in cell equipement nor in ue ! can you help me please?
Hello, anyone who can help?
DeleteHi,
ReplyDeleteIf PCELL and SCELL are both activated;
If data TX is happening on both;
Later if Handover is trigerred on PCELL to a new target cell, Will SCELL be released and activated automatically bu eNB?
Hello,
DeleteThe configured sCell will not be released if it is not included in sCellToReleaseList. However, all the configured sCells will be in deactivated state in the target cell. So, the eNodeB has to re-activate the sCell again in the target cell.
1. In Blind scell addition how many resource will utimized?
DeleteIf dont have any data then scell will be added only without activation
so we can say that some resource are waisting for scell addition only?
Hi
ReplyDeleteI like your post. I have a few questions.
How big is RRC Reconfig Message with ScellToAddMod and all the configuration details for the additional (1) carrier? Is it QPSK modulated always? Does it make a single transport block (transmitted in a single TTI)?
Thank you
Sorry for the delayed response. I can't give exact delta size as the coding is done in ASN.1.
DeleteThe RRC Reconfiguration message with single sCell with default configurations shouldn't be that bigger. However, a significant number of IEs would be added if the sCell configuration is different from default.
Usually, the eNodeB sends the entire message in single Transport block (i.e., in a TTI) even for the addition of two CCs
Hope it clarifies.
Thank you for the response on this. I have another question if you can help. Are configured Scells only valid (for example dedicated configuration) during a particular RRC connection, or can UE use Scells that were configured in some previous RRC connection? Thank you
ReplyDeleteThe Configured SCells are not valid for example if the UE re-establishes RRC connection.
DeleteThe UE should release configured SCells at:
1. RRC Connection Release
2. RRC Connection Re-establisment
What is the load on ue if scell is only configured but not activated? Ue sends cqi and monitors Pdcch only when scell is activated.so, is it good idea to configure scell always and activate when required for overlapped cell coverage case?
ReplyDeleteThe sCell is configured but not activated is not same situation at the UE as the sCell is not configured. Once the sCell is configured, the UE keeps tracking the sCell frequency, does sCell serving cell measurements etc...even though it is not active.
DeleteHi Kumar,
ReplyDeleteOnce eNB adds a Scell and Scell is in configured/deactivated state, does UE start reporting CQI for Scell?
My understanding is that UE starts reporting CQI only after Scell is activated by eNb. If yes, when does UE start reporting CQI for Scell so eNb can assign appropriate DL data on Scell? Assuming UE applies activation command after n+8 SF's, can you provide timeline of CQI reporting?
Thanks
CSI reporting for the SCell. The UE should start transmitting valid CSI report no later than subframe #n+24 or #n+34 (as defined in section 7.7.2 of 36.133) but it can report out of range (CQI index = 0) values from subframe #n+8, otherwise the eNodeB have to perform blind decoding of PUSCH (if scheduled) from subframe #n+8 till subframe #n+24 or #n+34
DeletePlease check my blog post on activation/deactivation: http://howltestuffworks.blogspot.com/2014/10/carrier-aggregation-activation-and.html
Hi Kumar,
DeleteCould you please elaborate " eNodeB have to perform blind decoding of PUSCH " ?
Hi kumar swamy,
ReplyDeletewhile sending data on any bearer dedicated/default , does EPC have any role in sending data on Scell ?.
Suppose i have only one Scell , i want to send the data on a bearer established from Pcell default/dedicated, do i need any config to be exchange between Scell (MAC) to EPC (SPGW) ?.
This comment has been removed by the author.
DeleteThere is no role of EPC, bkz Data is split at MAC layer of PCell and terminate at MAC layer of Scell
DeleteHi Kumar,
ReplyDeleteWhy ue release the Scells before handover?
is it possible to perform handover with Scells? if yes which 3GPP specs support it?
ReplyDeleteHi Kumar,
ReplyDeleteThans for sharing detailed info. Having one doubt would be requesting your input.
how UE reports CSI aperiodic of secondary scell if secondary scell is not configured for uplink transmission?
Hi Kumar, Why do we need PHICH configuration in RadioResourceConfigCommonScell section, as on SCELL for DL CA case there won't be any ack/nack
ReplyDeleteThis will be needed to figure out the number of REs, PHICH is gonna occupy to further perform PDCCH blind decoding.
DeleteEarlier in a comment you mentioned Scell addition is based on data requirement. could you please share related documentation?
ReplyDeleteI have one doubt in this statement
ReplyDelete"SCell may be added after receiving measurement report from the UE indicating that the cell on the carrier frequency used for the SCell is above certain threshold"
Does the UE indication is sufficient to add a SCELL? Imo, its the enb based on the DL buffers decides that a SCELL has to be added or not.
pls correct my understanding
Hi Kumar,
ReplyDeleteI have a question related to scheduling on Pcell/Scell. I think its possible to schedule only on Scell and not on Pcell at a particular instance . But in that case what HARQ feedback UE will provide considering the PUCCH 1bcs resources with A=4? Considering the Table 10.1.2.2.1-5 in 36.213 rel 11 spec (Both the cells have Tm3 mode configured). I could not see a case where HARQ feedback is not expected from Pcell but expected only for Scell.
Hi Kumar,
ReplyDeleteAt which stage Scell is added and during Pcell HO Throughput will drop?
At which state full bandwidth of CA is allocated to UE?
Hi Kumar, just wan to ask regarding Scell prioritization in adding and activating.
ReplyDeleteIs there any specifications about whcich Scell to prioritize during addition/activation if all priorities set are equal for all Scell? Thanks!
Hello,
ReplyDeleteSuppose the eNB request UE to add the Scell's which are configured in RRC connection reconfiguration message, then will the UE do the cell search on those Scell's and once cell is found then only UE adds those Scell's??
Thanks in advance.