3) RRC Connection Request:

Direction: UE => E-UTRAN Signaling Radio Bearer: SRB0 RLC Mode: TM Logical Channel: CCCH Transport Channel: UL-SCH RRC CONNECTION REQUEST message is used to request the E-UTRAN for the establishment of an RRC connection. It is sent as part of the Random Access procedure. It is transferred using SRB0 on the Common Control Channel (CCCH) because neither SRB1 nor a Dedicated Control Channel (DCCH) has been setup at this point.

IEs in RRC CONNECTION REQUEST message are given below: Ue-Identity (Initial UE-Identity): This IE is included to facilitate contention resolution by lower layers. It can be either S-TMSI (40-bits) or a bit string of random Value (40-bits). If the upper layers provide STMSI, then S-TMSI is used as the ue-Identity; else a random value in the range of 0 240-1 is drawn and used as the ue-Identity. Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell EstablishmentCause: The main cause values and the corresponding NAS procedure which triggers the RRC connection establishment are presented below: Emergency: This corresponds to NAS Procedure MO-CS fallback Emergency call Mt-Access: Corresponding NAS procedures are Service Request (paging response for PS domain) or Extended Service Request (MT-CS fallback) Mo-Signaling: Corresponding NAS procedures are Attach, Detach, and TAU Mo-Data: Corresponding NAS Procedures are Service Request and Extended Service Request

Example1: RRC CONNECTION REQUEST message with ue-Identity as a random Value

Example2: RRC CONNECTION REQUEST message with ue-Identity as s-TMSI

4) RRC Connection Setup

Direction: E-UTRAN => UE Signaling Radio Bearer: SRB0 RLC Mode: TM Logical Channel: CCCH Transport Channel: DL-SCH The RRC CONNECTION SETUP message is used to establish SRB1. It contains configuration information forSRB1. This allows subsequent signaling to use the DCCH logical channel. The configuration for SRB1 can be a specific configuration or the default configuration. The RRC CONNECTION SETUP message may also contain configuration for PUSCH, PUCCH, PDSCH channels and information regarding uplink power control, CQI reporting, the SRS, antenna configuration and scheduling requests Example: RRC CONNECTION SETUP

5) RRC Connection Setup Complete

Direction: UE => E-UTRAN Signaling Radio Bearer: SRB1 RLC Mode: AM Logical Channel: DCCH Transport Channel: UL-SCH The RRC CONNECTION SETUP COMPLETE message is used to confirm the successful completion of an RRC connection establishment. Some of the IEs in this message are explained below: SelectedPLMN-Identity: This IE points to a PLMN-Id in the plmn-IdentityList of SIB1. The IE plmnIdentityList is transmitted in SIB1 when the cell belong to more than one PLMN.The value of this IE equals to 1 if the 1stPLMN is selected from the plmn-IdentityList included in SIB1, 2 if the 2nd PLMN is selected from the plmn-IdentityList included in SIB1 and so on Registered ME: This IE is optional, and is included when available. This is the identity of the MME with which the UE is (previously) registered with. If upper layers provide the 'Registered MME', then the IEregisteredMME is set as follows: If the PLMN identity of the 'Registered MME' is different from the PLMN selected by the upper layers (selectedPLMN-Identity) then include the plmnIdentity in the registered ME and set the mmegi and the mmecto the value received from upper layers DedicatedInfoNAS: This IE includes the initial NAS message from the UE Example1: RRC CONNECTION SETUP COMPLETE message without registered ME IE

Example2: RRC CONNECTION SETUP COMPLETE message with registered ME IE included

6) Attach Request
The UE includes ATTACH REQUEST (initial-NAS) message within RRC CONNECTION SETUP COMPLETE message. The IE dedicatedInfoNAS in RRC CONNECTION SETUP COMPLETE includes this initial-NAS message The IEs (some of them are explained below) in ATTACH REQUEST message include EPS attach type, EPS mobile identity, UE network capability, ESM message container, Old P-TMSI signature, Additional GUTI, Last visited registered TAI, DRX parameter, Old location area identification, Additional update type, Voice domain preference and UE's usage setting etc The IE EPS Attach Type indicates the purpose of the attach procedure. The value can beEPS attach (to attach for EPS services only) or combined EPS/IMSI attach (to attach for both EPS and non-EPS services) or EPS emergency attach (to attach for emergency bearer services) The IE EPS Mobile Identity can be GUTI, IMSI or IMEI. The UE shall include GUTI if it holds a valid GUTI (either native GUTI or mapped GUTI). If there is no valid GUTI available, the UE shall include the IMSI as EPS Mobile Identity IE. If the UE is attaching for emergency bearer services and does not hold a valid GUTI, P-TMSI or IMSI as described above, the IMEI shall be included in the EPS mobile identity IE The purpose of the ESM message container IE is to enable piggybacked transfer of an ESM message within an EMM message (This may contain IEs for example, EPS bearer identity, procedure transaction identity, PDN connectivity request, PDN type, Request type, ESM information transfer flag, EIT (ESM information transfer), Protocol Configuration Options (Configuration Protocol, DNS Server Address Request etc..) The IE Additional Update Type provides additional information about the type of request for a combined attach procedure. Bit1 value 0 means that there is no additional information and 1 means that SMS only Voice domain preference and UE's usage setting IE shall be included if the UE supports CS fallback and SMS over SGs, or if the UE is configured to support IMS voice, but does not support 1xCS fallback. This IE provides the network with the UE's usage setting and the voice domain preference for E-UTRAN. Refer to 3GPP TS 24.008, section 10.5.5.28 for detailed information The IE Last Visited Registered TAI shall be included if the UE holds a valid last visited registered Tracking Area Identity (TAI)