DriverInitialize

BCCH Controller

PCCH Controller

MTCH Controller

MCCH Controller

DL-ULCCCH Controller

DL-ULDCCH Controller

DL-ULDTCH Controller

BCCH

PCCH

MTCH MAC-DeMux

MCCH

CCCH MAC-DeMux

DCCH

DTCH

MAC-Mux
MACPDUAssembler

BCCHHARQ

HeaderQualifier

MACSDUAssemble r

MACRAR

DLController I_BCH
Ring Buffer

ULController I_HARQ
Ring Buffer

SUTInitializer

I_PCH
Ring Buffer

I_MCH
Ring Buffer Ring Buffer

I_DL-SCH
Ring Buffer

I_UL-SCH
Ring Buffer

I_RACH
Ring Buffer

StubInitializer

PBCHController

PMCHController

PDSCHController

PDCCHController

PUCCHController

PUSCHController

PRACHController

PBCH PBCH 2000

PMCH 6000

PDSCH 4000

PDCCH 8000

PUCCH 7000

PUSCH 5000

PRACH 3000

eNB

PDCCH Controller

PDSCH Controller

DL-SCH Controller

HARQ Process

HARQ Controller

PUSCH Controller

PUCCH Controller

Sock_read( DCI=HI+RI)

HI RI Data
CRC Check

Data

NDI+RV

getbuff_data()

ACK/ NACK If have

Data to transmit

ACK/ NACK
If no data To transmit

eNB-PHY

eNB_MAC

Scheduler

eNB-RRC

Notify Rx_RACH_Preamble (PRACH-ID) Allocate T-C-RNTI T-C-RNTI

SCHED_DL_RACH_info_REQ(RNTI list)

Subframe Indication SCHED_DL_Trigger_REQ SCHED_DL_CONFIG_IND (RAR list with UL grant per RNTI)

Send RAR with RA-RNTI identifying preambleID

Determine RA-RNTI from PRACH-ID

Rx over UL_SCH

RxoverCCCH (RRCConnectionReq, T_C_RNTI) Configure UE

3rd Test Case flow eNB RRCConnectionReconfiguration msg

UE

Transmit PRACH Preamble RAR MAC PDU (RRCConnectionRecinfigurationComplete)

UE-RRC

UE_MAC

UE-PHY

eNB-PHY

Send over CCCH(RRC_Connection_req

)
Send Rach_Preamble(PRACH-ID

RACH_Preamble(PRACH-ID) =[{RA-RNTI(1+t_id+f_id)} +{indication of message3 size}] t_id=subframe number (accd. To PRACH Configuration index comes in SIB2) f_id=0(for FDD) Rx RAR over DL-SCH SendoverUL-SCH (RRC_Connection_req)

RACH_Preamble over RACH

RAR over PDSCH

Rx over PUSCH with T_C_RNTI Notify Random Access Procedure end ok (C-RNTI) RX over DL_SCH Rx CR over PDSCH

Msg2: If multiple UEs had collided by selecting the same signature in the same preamble time-frequency resource, they would each receive the RAR. The RAR conveys the identity of the detected preamble, a timing alignment instruction to synchronize subsequent uplink transmissions from the UE, an initial uplink resource grant for transmission of the Step 3 message, and an assignment of a Temporary Cell Radio Network Temporary Identifier (C-RNTI) (which may or may not be made permanent as a result of the next step contention resolution). The RAR message can also include a backoff indicator which the eNodeB can set to instruct the UE to back off for a period of time before retrying a random access attempt. The UE expects to receive the RAR within a time window, of which the start and end are configured by the eNodeB and broadcast as part of the cell-specific system information. Msg3: This message is the first scheduled uplink transmission on the PUSCH and makes use of Hybrid Automatic Repeat reQuest (HARQ). It conveys the actual random access procedure message, such as an RRC connection request, tracking area update, or scheduling request. It includes the Temporary C-RNTI allocated in the RAR at Step 2 and either the C-RNTI if the UE already has one (RRC_CONNECTED UEs) or the (unique) 48bit UE identity. In case of a preamble collision having occurred at Step 1, the colliding UEs will receive the same Temporary C-RNTI through the RAR and will also collide in the same uplink time-frequency resources when transmitting their L2/L3 message. This may result in such interference that no colliding UE can be decoded, and the UEs restart the random access procedure after reaching the maximum number of HARQ retransmissions. However, if one UE is successfully decoded, the contention remains unresolved for the other UEs. The following downlink message (in Step 4) allows a quick resolution of this contention. If the UE successfully receives the RAR, the UE minimum processing delay before message 3 transmission is 5 ms minus the round-trip propagation time.