All About Automatic Neighbor Relation (ANR)

Automatic Neighbor Relation (ANR):
- Automatic Neighbor Relation (ANR) function is to relieve the operator from the burden of
manually managing Neighbor Relations (NRs).
- The ANR function resides in the eNB and manages the conceptual Neighbor Relation Table (NRT).
- The Neighbor Detection Function finds new neighbors and adds them to the NRT.
- ANR also contains the Neighbor Removal Function which removes outdated NRs.
- An existing Neighbour Relation from a source cell to a target cell means that eNB controlling the source cell:

• Knows the ECGI/CGI and PCI of the target cell.
• Has an entry in the Neighbour Relation Table for the source cell identifying the target cell.
• Has the attributes in this Neighbour Relation Table entry defined, either by O&M or set to default values.

- NRT contains : 

• Target Cell Identifier (TCI)
• Identifies the target cell. 
• For E-UTRAN, the TCI corresponds to the E-UTAN Cell Global Identifier (ECGI) and Physical Cell Identifier (PCI) of the target cell. 

Each NR has three attributes: 

• NoRemove : eNB shall not remove the Neighbor cell Relation from the NRT.
• NoHO : Neighbor cell Relation shall not be used by the eNB for handover reasons.
• NoX2 attribute : Neighbor Relation shall not use an X2 interface in order to initiate procedures towards the eNB parenting the target cell.

NR Table

- Part of Self-Configuring Networks in SON.
- Manual Addition of cells in the neighbor list is a tough task. It is becomes very difficult when there are exiting networks like 2G,3G.
- For LTE there can be Intra LTE, Inter LTE and Inter RAT neighbors.
- There can be:

• Intra-Freq Automatic Neighbor Relations. 
• Inter-Freq/Inter System Automatic Neighbor Relations. 

Intra-Freq Automatic Neighbor Relations:

- Intra-Frequency neighbors can be added automatically as part of Intra-Freq handover procedure.

-  As a process for Intra Frequency HO procedure the serving eNodeB instructs each UE  to perform Intra-Frequency Measurement on neighboring cell by sending RRC Connection Reconfiguration message with measurement control information.

Automatic Neighbour Relation Function

- Consider as in the above picture, Serving Cell is CellA(UE is in RRC Connected State) and Cell B is the Target Cell: 
1.

• The UE sends a measurement report regarding cell B. 
• This report contains Cell B’s PCI, but not its ECGI. 
• eNodeB checks if the reported PCI is already included in the Neighbor Database, then the HO proceeds in the normal way.
• If reported PCI is not included in the Neighbor Database then eNB proceeds to add the PCI to its NRT.

2.

• Once eNB receives a UE measurement report containing the PCI, the eNB instructs the UE with another RRC Connection Reconfiguration Message, using the newly discovered PCI as parameter.
• Instruct UE to read the ECGI, the TAC and all available PLMN ID(s) of the related neighbor cell. 
• To do so, the eNB may need to schedule appropriate idle periods to allow the UE to read the ECGI from the SIB1 of the detected neighbor cell. 
• The UE reads the requested information from SIB1 on PDSCH. UE needs to read MIB on PBCH, then DCI with SI-RNTI on PDCCH to read SIB1 on PDSCH.

3. 

• When the UE has found out the new cell’s ECGI, the UE reports the detected ECGI to the serving cell eNB. 
• In addition the UE reports the tracking area code and all PLMN IDs that have been detected. 
• If the detected cell is a CSG or hybrid cell, the UE also reports the CSG ID to the serving cell eNB.

4. 
The eNB decides to add this neighbor relation, and can use PCI and ECGI to:

• Look up a transport layer address to the new eNB.
• Update the Neighbor Relation List.
• If needed, setup a new X2 interface towards this eNB. 

Inter-Freq/System Automatic Neighbor Relations:
- Can be done as a part of the normal inter-frequency and inter-system handover procedure.
- Inter-frequency and Inter-RAT measurement requires compressed mode to be configured.
- The eNodeB instructs UE to start inter-frequency and inter-RAT measurement using RRC Connection Reconfiguration message.
- The UE searches for the neighbor cells, identifies and reports them to eNodeB.
- The format of PCI depends upon the RAT of the Cell being measured.

Measurement Info Reported By UE

- Neighbor cell addition procedure:

Automatic Neighbour Relation Function in case of Inter Frequency/System Neighbor

- Once UE receives the Measurement Report for the Inter Frequency/RAT cell, 

• eNodeB checks if the reported PCI is already included in the Neighbor Database, then the HO proceeds in the normal way.
• If reported PCI is not included in the Neighbor Database then eNB proceeds to add the PCI to its NRT

- eNodeB instruct UE using another RRC Connection Reconfiguration message to decode the Global Cell Identity (CGI) from the system information.
- The UE may be required to report additional information depending on the system being measured.
- The eNB updates its inter-RAT/inter-frequency Neighbour Relation Table.
- In the inter-frequency case and if needed, the eNB can use the PCI and ECGI for a new X2 interface setup towards the new eNB.

All About Self Organizing Network (SON)

Self Organizing Network : 
- Aims to reduce the network operational cost and improve user experience.
- Addition of new network element should be in Plug and Play mode.
- SON introduced in Rel 8 version of the 3GPP specification.
- Fully implemented in Rel 9 and Rel 10.
- 3 main concepts :

• Self - Configuring Network
• Self - Optimizing Network
• Self - Healing Network

Self Configuring Network :

- Aimed at automating the deployment of new eNodeB.
- eNodeB should be added to the Network as Plug and Play.
- Introducing a new eNodeB to the system should be automatic and eNodeB will be able to allocate appropriate Physical Layer Cell Identity.
- ANR is part of Self Configuring Network.
- Should be easy to deploy and should be less sensitive to error.
- Most used during initial network deployment.

Self - Optimizing Network :

- Aimed at automating network performance improvement.

- Includes 

• Coverage and capacity optimization
• Handover optimization
• RACH optimization
• Reduce inter-cell interference between eNodeB.

- Aimed at reducing the requirement of drive test.

- Useful throughout the life of the network

Self - Healing Network :

- Aimed at automating the fault handling.

- Faults should be automatically detected and corrected.

- Reduces outage time.

- Improves network performance

- Improves end-user experience.

- If one the eNodeB goes bad then self - healing allows neighboring eNodeBs to compensate by using their unused power headroom.

- It also uses redundancy within the network. 

- Useful throughout the life of the network

All about Buffer Status Reporting (BSR)

Buffer Status Reporting (BSR) :

- The Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data available for transmission in the UL buffers of the UE.

Type Of BSR:

- UL data, for a logical channel which belongs to a LCG, becomes available for transmission in the RLC entity or in the PDCP entity and either the data belongs to a logical channel with higher priority than the priorities of the logical channels which belong to any LCG and for which data is already available for transmission, or there is no data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR".

- UL resources are allocated and number of padding bits is equal to or larger than the size of the Buffer Status Report MAC control element plus its subheader, in which case the BSR is referred below to as "Padding BSR".

- retxBSR-Timer expires and the UE has data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR"

- periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".

When UE will Report Which Type:

- periodicBSR-Timer expires, "Periodic BSR".

For Regular and Periodic BSR:

 If (More than one LCG has data available for transmission in the TTI where the BSR is transmitted)

      Report Long BSR.

 else,

      Report Short BSR.

For Padding BSR:

If (Number of padding bits => size of the Short BSR plus its subheader) && If (Number of padding bits < size of the Long BSR plus its subheader)

Then Short BSR or Truncated BSR Can be transmitted instead of Padding.

If (More than one LCG has data available for transmission in the TTI where the BSR is transmitted): 
Then : 

     Report Truncated BSR of the LCG with the highest priority logical channel with data available for transmission;
Else

     Report Short BSR.

Elseif (Number of padding bits => Size of the Long BSR plus its subheader)         

     Report Long BSR.

All About HARQ

HARQ :

- It is a re-transmission technique used by LTE for re-transmitting of UL & DL Data.
- HARQ (Hybrid ARQ) = ARQ (Automatic Repeat Request) +  FEC (Forward Error Correction).

- The HARQ makes use of ARQ along with an Error Correction technique called 'Soft Combining', which no longer discards the received corrupted data.

- Using 'Soft Combining' data packets that are not decoded are not discarded anymore. The received signal is stored in a 'buffer', and combined with next re transmission.

- Hybrid ARQ (HARQ) leads to higher efficiency in transmission and error correction.
- There is one HARQ entity per UE with 8/16 stop-and-wait processes for each HARQ entity.
- It means Sender will not send new data or re-transmitted data until he will not get ACK or NACK from receiver respectively.
- As Sender is waiting for ACK/NACK from receiver, hence it decreases the through put. To overcome this issue, LTE uses multiple parallel HARQ Process with different process ID.
- FDD-LTE uses 8 HARQ Parallel Process having unique process ID 0, 1, 2...7 (3 bits reserve for HARQ Process ID in DCI Messages).
- In TD-LTE, it uses 16 HARQ Parallel Process ID having unique process ID 0, 1…15(4 bits reserve for HARQ Process ID in DCI Messages).
- Both Incremental redundancy(IR) and Chase combining(CC) are supported.
- The number of HARQ re transmissions targeted by the HARQ protocol depends on the network provided configuration.

FEC (Forward Error Correction) :

FEC or Channel Coding is a technique used for controlling and correcting error in LTE Data transmission.

Channel coding supported for LTE Data Transmission

HARQ with Soft Combining :

In practice, incorrectly received coded data blocks are often stored at the receiver rather than discarded, and when the re-transmitted block is received, the two blocks are combined. This is called Hybrid ARQ with soft combining

Soft Combining Techniques

- IR requires larger receiver buffer than CC but can achieve better performance than CC.
- CC is simple HARQ and requires small receiver buffer.

Chase Combining :

- Every re-transmission = The same information (data and parity bits).
- Receiver uses maximum-ratio combining to combine the received bits with the same bits 
from previous transmissions.
- All transmissions are identical So Chase combining seen as additional repetition coding.
- This scheme achieves gain with small buffer size in a receiver. 
- The buffer size becomes the number of coded symbols of one coded packet

Incremental Redundancy :

- To transmit additional redundant information in each re-transmission and receiver decode on each re-transmission. 
- Every retransmission contains different information than the previous one.
- IR requires larger size of buffer in a receiver than Chase Combining. The buffer size becomes the number of coded bits of total transmitted coded packets.

Redundancy Versions (RV) :

- Different combinations of systematic data bits + FEC bits.
- LTE HARQ has 4 RVs typically of a packet (0,1,2,3).

Difference between LTE HARQ used in UL and DL:

• UL: A synchronous HARQ mode is used.
• DL: An adaptive, asynchronous HARQ.

All About Connected Mode Discontinuous Reception (DRX)

Connected Mode DRX:

- DRX in connected mode is a power-saving method.

- DRX is a method by which the UE can switch off its receiver for a period of time.

- Applicable when UE is in RRC_CONNECTED state.

- When UE is in RRC Connected state UE may be configured with a UE specific DRX.

- if DRX is configured, the UE is allowed to monitor the PDCCH discontinuously in RRC Connected state.

- Controls the UE’s PDCCH monitoring activity for the UE’s C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and Semi-Persistent Scheduling C-RNTI (if configured).

- In the RRC_CONNECTED state DRX mode is enabled during the idle periods during the

packet arrival process,when there are no outstanding/new packets to be transmitted/received, eNB/UE may initiate the DRX mode.

- If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered and periodical triggered measurements until the Active Time.

- cqi-Mask - Limits CQI/PMI/PTI/RI reports to the on-duration period of the DRX cycle.

DRX Cycle : 

-On Duration followed by a possible period of inactivity.

DRX Configuration: 

onDurationTimer : 

- The duration of 'ON time' within one DRX cycle.

- The number of consecutive PDCCH-subframe(s) UE monitors at the beginning of a DRX Cycle.

- If both Long DRX and Short DRX is configured for a particular UE, onDurationTimer i.e. on duration time during Short DRX cycle or Long DRX cycle should be same.

- When to onDurationTimer should be started depends on : 

-     If (Short DRX Cycle) && If ([(SFN * 10) + subframe number] modulo (shortDRX-Cycle) == (drxStartOffset) modulo (shortDRX-Cycle)) 

or

-     If (Long DRX Cycle) && If ([(SFN * 10) + subframe number] modulo (longDRX-Cycle) == drxStartOffset)

-     start onDurationTimer.

drx-InactivityTimer : 

- During Active time if UE receives PDCCH indicates a new transmission (DL or UL) drx-InactivityTimer started or restarted.

- Determines the number of consecutive PDCCH-subframe(s) UE monitors before going to sleep, after successfully decoding a PDCCH during active time. 

- Value in number of PDCCH sub-frames.

drx-RetransmissionTimer :

- PDCCH subframe(s) the UE should remain active as soon as a DL re-transmission is expected by the UE.

- Value in number of PDCCH sub-frames.

longDRX-Cycle :

- Once drxShortCycleTimer  expires Long DRX cycle starts.

- longDRX-Cycle and drxStartOffset . The value of longDRX-Cycle is in number of sub-frames.

- If shortDRX-Cycle is configured,the value of longDRX-Cycle shall be a multiple of the shortDRX-Cycle value.

- The value of drxStartOffset value is in number of sub-frames.

shortDRX-Cycle : 

- It is a optional one.

- If Short DRX is configured, if drx-InactivityTimer expires or a DRX Command MAC control element is received, drxShortCycleTimer  is started and short DRX cycle is used.

drxShortCycleTimer : 

- Specifies the number of time(s) the UE shall follow the Short DRX cycle.

- Value in multiples of shortDRX-Cycle. A value of 1 corresponds to shortDRX-Cycle, a

value of 2 corresponds to 2 * shortDRX-Cycle and so on.

Active Time:

• Time when UE continuously monitors PDCCH.
• Includes when onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or mac-ContentionResolutionTimer is running.
• SR is sent on PUCCH and is pending.
• Uplink grant for a pending HARQ re-transmission can occur, and there is data in the corresponding HARQ buffer.
• A PDCCH indicating a new transmission addressed to the C-RNTI of the UE has not been received after successful reception of a RAR for the preamble not selected by the UE i.e. Dedicated RACH.

DRX Command MAC Control Element : 

- DRX Command MAC control element is identified by a MAC PDU subheader with LCID (11110).

- It has a fixed size of zero bits.

All About Idle Mode Discontinuous Reception (DRX)

DRX: 

- In LTE, DRX mode can be enabled in both RRC_IDLE and RRC_CONNECTED states.

- DRX is used to reduce power consumption.

Idle Mode DRX: 

- Applicable when UE is in RRC_IDLE state.

- The UE is registered with the evolved packet system mobility management (EMM_REGISTERED) but does not have an active session (ECM_IDLE).

- In this state the UE can be paged.

- UE monitors paging messages using idle mode DRX configuration.

- Idle mode DRX configuration is broadcast within System Information Block 2(SIB2).

- Idle mode DRX configuration is used to calculate Paging Frame(PF) and Paging Occation(PO).

- One Paging Occasion (PO) is a subframe where there may be P-RNTI transmitted on PDCCH addressing the paging message.

- One Paging Frame (PF) is one Radio Frame, which may contain one or multiple Paging Occasion(s).

-When DRX is used the UE needs only to monitor one PO per DRX cycle.

PF is given by following equation: 

     SFN mod T= (T div N)*(UE_ID mod N) 

T : DRX cycle of the UE. T = min(The UE specific DRX , Default DRX value).
The UE specific DRX value allocated by upper layers, and default DRX value broadcast in system information. 
If UE specific DRX is not configured by upper layers, the default value is applied. 

N: min(T,nB)

nB: Broadcast within System Information Block 2(SIB2) and can take values 4T, 2T, T, T/2, T/4, T/8, T/16, T/32.

N can have values of T, T/2, T/4, T/8, T/16, T/32.

UE_ID: IMSI mod 1024.

IMSI is given as sequence of digits of type Integer

Index i_s pointing to PO from subframe pattern defined below will be derived from following calculation: 

     i_s = floor(UE_ID/N) mod Ns 

Ns: max (1,nB/T)

All About RACH Contention Resolution Procedure

All About RACH Contention Resolution Procedure:

- RACH procedure can be Contention Based and Non-Contention Based.

Contention Based RACH Procedure:

-  In Contention based procedure UE selects a Random Access Resource i.e. UE selecting a PRACH resource, a Preamble Sequence and the next available Subframe for PRACH transmission.

- There are two types of contention based RACH procedure depending on MSG3 i.e. initial layer 3 message.

- For RRC Connection Establishment and RRC Connection Reestablishment the MSG3 is transferred on CCCH logical channel i.e. initial layer 3 message is a CCCH SDU. 
- Contention Resolution is based upon the reception of Contention Resolution Identity MAC CE. In this case a new CRNTI is allocated to the UE.
-  If ( CCCH SDU was included in Msg3 ) && If ( PDCCH transmission is addressed to its Temporary C-RNTI ) && If ( The MAC PDU is successfully decoded ) && If ( MAC PDU contains a UE Contention Resolution Identity MAC control element ) 
{
      If ( UE Contention Resolution Identity included in the MAC control element == CCCH SDU transmitted in Msg3) 
                    Then Consider Contention Resolution successful.
}

- For  Intra-System Hand Over and Uplink/Downlink data arrives while UE is in Non-synchronized RRC Connected State the MSG3 is transferred using the DCCH logical channel and contention resolution is based upon the reception of PDCCH on already allocated C-RNTI.

RACH Sequence

Non Contention Based RACH Procedure:
- ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) explicitly signalled and and ra-PreambleIndex not equal to 000000.
- During Intra System HO(RRC Connection Reconfiguration with Mobility Control Info) or PDCCH order will provide the information about  ra-PreambleIndex and ra-PRACH-MaskIndex.


  

All About Random Access Procedure In LTE

When UE Initiate Random Access Procedure In LTE:
- Transition from RRC Idle to RRC Connected mode.
- Completing an Intra-System Hand Over.
- Uplink data arrives while UE is in Non-synchronized RRC Connected State(Time alignment Timer Expiry).
- Downlink data arrives while UE is in Non-synchronized RRC Connected State(Time alignment Timer Expiry).
- RRC Connection Re-establishment.

PRACH : Physical Random Access Channel:
- Used to transfer RANDOM ACCESS PREAMBLES to initiate RANDOM ACCESS PROCEDURE.
- Do not transfer RRC Signaling Messages or Application Data.

RACH - Config Common Information: 

RACH-ConfigCommon IE

RACH-ConfigDedicated IE

RACH Procedure:
- RACH Procedure can be
             - Contention Based.
             - Non Contention Based.
- Contention Based procedure involves the UE selecting a Random Access Resource i.e. UE selecting a PRACH resource, a Preamble Sequence and the next available Subframe for PRACH transmission.
- Non-Contention Based procedure involves the eNodeB allocating the Random Access Resource i.e. eNodeB allocating ra-PreambleIndex and ra-PRACH-MaskIndex.
- Contention Based RACH Procedure can be applicable for all RACH reasons but Non Contention Based RACH Procedure can be applicable for :
             - Completing an Intra-System Hand Over.
             - Downlink data arrives while UE is in Non-synchronized RRC Connected State.

Random Access Resource Selection:

Random Access Group Selection:
If (ra-PreambleIndex == Allocated By eNB && ra-PRACH-MaskIndex == Allocated By eNB)
      {
      If (ra-PreambleIndex != 000000)
           {
            Random Access Preamble && PRACH Mask Index = Allocated By eNB.
            }
       }
Elseif
      {
      If (MSG3 == Not Transmitted Yet)
           {
            If (Random Access Preambles group B == present)
                 {
                 If ( sizeof(MSG3) > messageSizeGroupA && pathloss < (P-CMAX,c– preambleInitialReceivedTargetPower – deltaPreambleMsg3 – messagePowerOffsetGroupB))
                      {
                       select the Random Access Preamble from  Random Access Preambles group B
                       }
                  Else
                      {
                       select the Random Access Preamble from  Random Access Preambles group A
                       }
                  }
              Else
                  {
                   select the Random Access Preamble from  Random Access Preambles group A
                   }
             }
       Elseif (MSG3 == Re-transmitted)
              {
               select the Same Group of Random Access Preambles = used for the preamble transmission attempt corresponding to the first transmission of Msg3
               }
       }

Random Access Preamble Selection Within the Group:
- Randomly select a Random Access Preamble within the selected group.
- The random function shall be such that each of the allowed preamble will have equal probability.
- set PRACH Mask Index to 0.

PRACH Resource Selection:
- Subframe for PRACH transmission selected using restrictions given by the prach-ConfigIndex and the PRACH Mask Index.
- physical layer timing requirements i.e. UE may take into account the possible occurrence of measurement gaps when determining the next available PRACH subframe.

Random Access Preamble Power : 
- PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower (RACH-ConfigCommon) + deltaPreambleMsg3 (UplinkPowerControlCommon) + (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep (RACH-ConfigCommon)
- Physical layer transmit a preamble using the selected PRACH, corresponding RA-RNTI, preamble index and PREAMBLE_RECEIVED_TARGET_POWER

Random Access Response (RAR) Reception:
- Once RACH is transmitted UE shall monitor PDCCH regardless of the possible occurrence of a measurement gap.
- RAR is identified by RA-RNTI.
- RA Response window starts at subframe that contains the end of the preamble transmission + three subframes.
- RA Response window has a length ra-ResponseWindowSize(SIB2) subframes
- The RA-RNTI is calculates as :
          RA-RNTI= 1 + t_id+10*f_id
          where t_id = Subframe within which start of preamble was transmitted(0<= t_id<=9).
                    f_id = Frequency domain index of the PRACH within the subframe.(0<= f_id<=5).
- For FDD there can be maximum one set of RBs allocated to PRACH within a subframe so f_id is always 0.
- So for FDD RA-RNTI= 1 + t_id.

All About Carrier Aggregation (CA)

Carrier Aggregation (CA):

- LTE Release 10 Feature.

- Known as LTE Advance.

- DL Speeds upto 1 Gbps and UL Speeds upto 500Mbps.

- Backward Compatibility with Rel 8 and Rel 9.

- Can be used for both FDD and TDD.

- The component carrier can have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz.

- A maximum of 5 Component Carriers(CC) can be aggregated.

- The maximum aggregated bandwidth is 100 MHz.

- Each component carrier is treated as an R8 carrier.

- The spacing between center frequencies of contiguously aggregated component carriers will be a multiple of 300 kHz to be compatible with the 100 kHz frequency raster of Release 8/9 and at the same time preserve orthogonality of the subcarriers, which have 15 kHz spacing.

- For non-contiguous cases the CCs are separated by one, or more, frequency gap(s).

LTE-Advanced Support Three Component Carrier Aggregation Scenarios:

- Intra-Band Contiguous

- Intra-Band Non-contiguous

- Inter-Band Non-contiguous

PCell and SCell :
- The Cell UE selects during initial establishment (RRC Connection Request/RRC Connection Re-establishement Request) will become the PCell.
- eNodeB can add / delete Scell(s) using RRC Connection Reconfiguration message.

PCell Vs SCell:
- PCell always have both Uplink(UL) and Downlink(DL). Scell always have DL (While activated) but may or may not have UL.
- PCell is always activated whereas SCell has to be activated or deactivated using MAC-CE.
- UE does not required to acquire System Information and decode Paging from SCell.
- For Scell SI is passed to UE while adding the Scell. 
- When an Scell is added using RRC Connection Reconfiguration Message it remains in the deactivated state till it is activated using MAC-CE.
- If Scell activation/deactivation MAC-CE is received on Subframe n the Scell is activated/deactivated on Subframe n+24 or n+34.(TS 36.133 Section 7.7.2)
- When sCellDeactivationTimer expires then Scell is deactivated.
- Once Scell is deactivated 
         - PDCCH on Scell and PDCCH for Scell is not monitored. 
         - PUSCH is not transmitted and PDSCH is not received. 
         - The SRS is not transmitted.
         - The CQI/PMI/RI for Scell is not reported.


Activation/Deactivation MAC-CE:
- The MAC-CE can activate and deactivate Scell(s) which is already configured using RRC Connection Reconfiguration Meassage.
- Control Element is identified by a MAC PDU subheader with LCID.
.

Values of LCID for DL-SCH

Index	LCID values
11011	Activation/Deactivation

- fixed size and consists of a single octet containing seven C-fields and one R-field.

Activation/Deactivation MAC control element

- The Ci field is set to "1" to indicate that the SCell with SCellIndex i shall be activated.

- The Ci field is set to "0" to indicate thatthe SCell with SCellIndex i shall be deactivated.

- R: Reserved bit, set to “0”.
- 

Pcell and Scell Concepts:
- Pcell can be changed using RRC Connection Reconfiguration With MobilityControlInfo i.e. Handover.
- Scell can be changed using RRC Connection Reconfiguration message.
- During Radio Link Failure, the Scell is release first before initiating RRC Connection Re-establishment procedure.
- On receiving Handover Command i.e. RRC Connection Reconfiguration With MobilityControlInfo, UE deactivates the Scell, if configured.
- TTI Bundling is not supported when configured with one or more Scell with Configured Uplink.
- The RSRP and RSRQ measurement for Pcell shall follow time domain measurement resource restriction in accordance with measSubframePatternPCell, if configured.

Procedure	Pcell	Scell
Radio Link Monitoring	Y	N
System Information Acquisition	Y	N
Random Access Procedure	Y	N
Time Alignment	Y	N
SPS	Y	N
Connected Mode DRX	Y	Y
Paging	Y	N
NAS Mobility Information	Y	N
Data Transmission	Y	Y
S-measure Criteria	Y	N
Power Control	Y	Y
Link Adaptation	Y	Y
Pathloss Meaurement	Y	Y= when pathloss reference=Scell N= when pathloss reference=Pcell

Channel	Pcell	Scell
PDCCH	Y	Y - No Cross Carrier Scheduling N - Cross Carrier Scheduling (UE does not look at PDCCH when CCS but eNodeB might be transmitting PDCCH.)
PDSCH	Y	Y
PUCCH	Y	N
PUSCH	Y	Y
PRACH	Y	N
SRS	Y	Y
PBCH	Y	N - UE does not look at PBCH But eNodeB might be transmitting it.
PSS/SSS	Y	N - UE does not look at PSS/SSS but to get timing information eNodeB might be transmitting PSS/SSS.
PCFICH	Y	Y - No Cross Carrier Scheduling N - Cross Carrier Scheduling (UE does not look at PCFICH when CCS but eNodeB might be transmitting PCFICH.)
PHICH	Y	Y - No Cross Carrier Scheduling N - Cross Carrier Scheduling (UE does not look at PHICH when CCS but eNodeB might be transmitting PHICH.)

Cross Carrier Scheduling(CCS):
- Downlink Scheduling or Uplink Grant information of One Component Carrier(CC) can be carried by the PDCCH of another Component Carrier(CC).
- 3 bit CIF field indicates target CC.
- Pcell shall always be scheduled by Pcell only.
- Scell can be cross scheduled by Pcell or by other Scell.
- UE indicates whether it supports CCS or not.
- Cross Carrier Scheduling is not applicable for PDCCH order. It is transmitted on Pcell.
- CCS is applicable for aperiodic SRS transmission.

- The cif-Presence-r10 in physicalConfigDedicated indicates whether CIF will be present in PDCCH of Pcell.

- The RadioResourceConfigDedicatedSCell-r10.PhysicalConfigDedicatedSCell-r10.CrossCarrierSchedulingConfig-r10 indicates CCS status of Scell.

- cif-Presence indicates whether carrier indicator field is present (value TRUE) or not (value FALSE) in PDCCH DCI formats.

- pdsch-Start indicates the starting OFDM symbol of PDSCH for the concerned SCell. Values 1, 2, 3 are applicable when dl-Bandwidth for the concerned SCell is greater than 10 resource blocks, values 2, 3, 4 are applicable when dl-Bandwidth for the concerned SCell is less than or equal to 10 resource blocks.

- schedulingCellId Indicates which cell signals the downlink allocations and uplink grants, if applicable, for the concerned SCell.(When Scell cross scheduled  other Scell.)

- The other-r10.schedulingCellId-r10 and cif-Presence-r10 of that cell should be consistent.

Carrier Aggregation and Measurement Events:

- Definition of Serving Cell Measurement is Modified.

- For Event A1 and Event A2 The Carrier Frequency in Measurement Object indicates whether this event is for Pcell or any Scell. 

- The eNodeB shall configure separate A1/A2 events for each serving cell.

- Event A3 - Neighbor becomes offset better than Pcell.

- Event A5 - Pcell becomes worse than theshold1 and neighbour becomes better than threshold2.

        - For Event A3 and Event A5 the frequency mentioned in the associated measObjectEUTRA indicates neighbours.

        - For Event A3 and Event A5 the Scell become neighbouring cell.

- Event B2 - Pcell becomes worse than theshold1 and inter RAT neighbour becomes better than threshold2.

- Event A6 - Intra Frequency Neighbour becomes offset better than Scell.

- No change in the definition of Event A4 and Event B1.

Carrier Aggregation and Periodic Measurement:

- If (Purpose == reportStrongestCells && reportAmount > 1)

      UE initiates a first MR immediately after the quantity to be reported becomes available for the Pcell.

- If (Purpose == reportStrongestCells && reportAmount == 1)

      UE initiates a first MR immediately after the quantity to be reported becomes available for the Pcell and for the strongest cell among the applicable cells.

- If (Purpose == reportStrongestCellsForSON)

      UE initiates a first MR when it has determined the strongest cells on the associated frequency.

Carrier Aggregation and Measurement Gap:

- UE shall be able to carry out Measurement on any serving frequency without measurement gap i.e. intra-frequency measurement for any serving frequency.

- UE may required measurement gap to perform inter-frequency or inter-RAT measurement.

Typical CA Call Flow: