Difference between revisions of "LTE RRC Extension"

From Nsnam
Jump to: navigation, search
m (editorial)
m (editorial)
Line 22: Line 22:
 
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).
 
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).
  
'''Functional discription'''
+
'''Functional Description'''
  
 
1. '''System information''': System configuration messages send to your from e-utran are system information messages. System information classified in following four broad categories.  Master information block: Contains information parameter for initial access.  SIB1 contains information parameter for cell selection. SIB2 contains information parameter for common and shared channel.  
 
1. '''System information''': System configuration messages send to your from e-utran are system information messages. System information classified in following four broad categories.  Master information block: Contains information parameter for initial access.  SIB1 contains information parameter for cell selection. SIB2 contains information parameter for common and shared channel.  

Revision as of 17:49, 25 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).

Functional Description

1. System information: System configuration messages send to your from e-utran are system information messages. System information classified in following four broad categories. Master information block: Contains information parameter for initial access. SIB1 contains information parameter for cell selection. SIB2 contains information parameter for common and shared channel.

2. Paging: To inform for the incoming calls to UE paging messages are used. Transmission of paging is done by base station (section 5.3.2 of 36.331). Reception and processing of paging in UE (section 5.3.2.3).

3. Connection Control: To establish connection to exchange information. Following sub procedure under this category which will provide functionality related to establishment/maintenance/release of radio bearers RRC connection establishment (section 5.3.2), RRC reconfiguration (section 5.3.5), RRC radio resource configuration (section 5.3.10) and RRC connection release (section 5.3.8).

Time schedule

      Items 	                   Time 
      API Design	         Two week
      System Information	 One week
      Paging	                 One week
      Connection Control  	 Three week
      Integration and testing	 Two week
      Final wrap-up	         Two week