LTE RRC Connection Setup Messaging - EventHelix.com
LTE RRC Connection Setup Messaging - EventHelix.com
LTE RRC Connection Setup Messaging - EventHelix.com
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systems<strong>LTE</strong> <strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong><strong>Messaging</strong>© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc.All Rights Reserved
<strong>LTE</strong> attach messagesequence chart<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systemsUEeNodeBRACH: Random Access Preamble(RA-RNTI)UE initiates a session to the eNodeBusing a random RA-RNTIDL-SCH: Random Access Response(RA-RNTI, C-RNTI, Timing)eNodeB assigns a C-RNTI and adjuststimingUL-SCH: <strong>RRC</strong> <strong>Connection</strong> Request(C-RNTI, M-TMSI, Establishment Cause)DL-SCH: <strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong>(SRBs, DRBs, UE Specific Configuration)UL-SCH: <strong>RRC</strong> <strong>Connection</strong> Complete(PLMN id, Dedicated NAS Info)UE requests an <strong>RRC</strong> connection via theUL-SCH.Network establishes the SRBs and DRBsbased on the establishment cause.UE acknowledges the setup of SRBs andDRBs.© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc.2
Establishment Cause<strong>RRC</strong> <strong>Connection</strong> RequestUL-SCH: UE eNodeB<strong>RRC</strong> <strong>Connection</strong> Request<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systems• The UE has received the Random AccessResponse based on the RA-RNTI.• The Random Access Response assigns aC-RNTI and resources for transmission ofthe <strong>RRC</strong> <strong>Connection</strong> Request• The message identifies the UE with the C-RNTIUE ID/RNTI TypeUE ID/RNTI ValueUE-IdentityC-RNTIS-TMSIMMEC• The message contains the UE-Identity• IMSI is sent in the message if this is thefirst attach to the network• If the terminal had attached previously,the S-TMSI is included in the message• The message also contains theestablishment cause.• In this example, the <strong>RRC</strong> <strong>Connection</strong>Request is sent with “Mobile OriginatedSignaling” cause.• Note that the eNodeB may optionallysend a contention resolution message onreceipt of this messageEstablishmentCausemo-SignallingemergencyhighPriorityAccessmt-Accessmo-SignallingM-TMSImo-Data© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc. 5
<strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong>DL-SCH: UE eNodeB<strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong>UE ID/RNTI TypeC-RNTI<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systems• The message identifies the signaling radiobearer (SRB)UE ID/RNTI ValueSRB IdentityT Poll Retransmit• The configuration parameters carried inthe message are described in the nexttwo slidesRadio ResourceConfig DedicatedSRBs toAdd/ModifyMAX HARQ TXUL AM RLCPoll PDUMaximum Retrans.ThresholdDL AM RLCT ReorderingUL-SCH ConfigPeriodic BSR TimerRetransmissionBSR TimerPeriodic PHR TimerPHR ConfigProhibit PHR TimerDL Path LossChangeP0 UE PUSCHDelta MCS EnabledUplink PowerControl DedicatedP0 UE PUCCHPSRS OffsetFilter Coefficient© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc. 6
<strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong>Configuration - 1<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systemsRLC UplinkConfiguration• Timer for statusreport polling• Number ofretransmissionsof buffer statusreport• Control planeretransmissionlimitRLC DownlinkConfiguration• The maximumtime to wait forpacketreorderingUL-SCHconfiguration• Maximumnumber ofHybrid ARQtransmissions• Periodic andregular bufferstatus report(BSR) timer© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc. 7
<strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong>Configuration - 2<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systemsPower Headroom Report (PHR)Configuration• Periodicity of the PHR• Downlink Path Loss more than thespecified value also triggers PHR(provided the Prohibit PHR timer hasexpired)Uplink Power Control Parameters• P0-UE-PUSCH and P0-UE-PCCHvalues are used to determine thenominal power of the uplinktransmissions• “pSRS Offset” determines the uplinkSounding Reference Signal power• Delta MCS (choose between Ks = 0and Ks = 1.25)• Filter Coefficient value for RSRP(Reference Signal Received Power)measurement used to calculate pathloss• Reference: 36.213 clause 5.1.1.1© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc. 8
<strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong>CompleteUL-SCH: UE eNodeB<strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong>Complete<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systems• UE sends this message on receipt of the<strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong> message• “Dedicated Info NAS” is used to transferUE specific NAS layer informationbetween the network and the UE. The<strong>RRC</strong> layer is transparent for thisinformation.• The message may optionally containregistered MME• The <strong>RRC</strong> <strong>Connection</strong> <strong>Setup</strong> Complete mayalso carry octets for a NAS messageexchanged between the UE and the MMESelected PLMNIdentityRegistered MME(Optional)PLMN IdMMEGIMMECDedicated Info NASOctets carryingNAS message© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc. 9
Explore more<strong>EventHelix</strong>.<strong>com</strong>• tele<strong>com</strong>munication design• systems engineering• real-time and embedded systemsLinks3GPP 36.331 <strong>RRC</strong> SpecificationsEventStudio System DesignerVisualEther Protocol AnalyzerTele<strong>com</strong> Call FlowsTCP/IP Sequence DiagramsTele<strong>com</strong> • Networking • SoftwareTele<strong>com</strong> • Networking • Design blogDescriptionRadio Resource Control (<strong>RRC</strong>); ProtocolspecificationSequence diagram based systems engineeringtool.Wireshark based visual protocol analysis andsystem design reverse engineering tool.GSM, SIP, H.323, ISUP, <strong>LTE</strong> and IMS call flows.TCP/IP explained with sequence diagrams.Real-time and embedded systems, call flowsand object oriented design articles.<strong>EventHelix</strong>.<strong>com</strong> blog© 2012 <strong>EventHelix</strong>.<strong>com</strong> Inc. 10
Change language