Wednesday, 8 January 2014

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)



Thursday, 2 January 2014

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.


  

Wednesday, 1 January 2014

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 transmissionthree 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.