LTE RRC Extension: Difference between revisions
Pankaj303er (talk | contribs) (NSoC Project update initial version) |
Pankaj303er (talk | contribs) m (editorial) |
||
Line 25: | Line 25: | ||
'''''Items''''' '''''Time''''' | '''''Items''''' '''''Time''''' | ||
API Design One week | |||
System Information One week | System Information One week | ||
Paging One week | Paging One week |
Revision as of 17:27, 22 May 2011
Objective Current RRC entity in the present LTE module of ns-3 has the handling of user plane. This proposal is to enhance and develop the RRC entity is ns-3 LTE for control plane handling in UE and eNodeB. We aim to incorporate following functionality viz. Paging, System Information (MIB, SIBType1 and SIBType2) and connection control (RRC establishment, RRC reconfiguration, RRC release and RRC resource configuration)
Introduction The Radio Resource Control (RRC), i.e., layer 3, for control plane is responsible for, establishing the radio bearers, control of radio resource usage and configuring all the lower layers. It handles system information, carries out mobility function and QoS management function. Key features include 1. System information handling 2. Paging 3. Connection control. 4. RB control. 5. UE measurement reporting and control.
List of Functions to be implemented in this project
• System Information: Reception and transmission at UE and eNodeB
• Paging: Reception and Transmission at UE and eNodeB
• Connection control Procedures: Following procedures have been identified for the implementation in during NSoC 2011.
RRC connection establishment , RRC Connection Reconfiguration , RRC Connection Release , UE action upon leaving
Deliverables At the end of the project we will be able establish between UE and eNodeB the SRB0/SRB1/DRBs. And UE and EnodeB can able to perform following procedures Paging, System Information , Connection control procedures ( RRC establishment , RRC reconfiguration , RRC release , RRC radio resource configuration).
Time schedule
Items Time API Design One week System Information One week Paging One week Connection Control Three week Integration and testing Three week Final wrap-up Two week