27.03.2014 Views

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

D0103v1.doc Version 1 6.7.2003<br />

4.3.4.6.3 RRC internal states<br />

The RRC layer implements a state machine. From a macroscopic point of view, the UE can be either in<br />

idle or in connected mode. This mode is known at NAS level.<br />

• idle mode: The Mobile Terminal (UE) is first switched on. Then it enters the “Idle” mode where<br />

it listens to the synchronization channel and then to the BCH. After this first synchronization<br />

phase, the UE is “physically” attached to the RG. It is said to “camp on the cell”. It monitors the<br />

<strong>System</strong> Information messages broadcasted by the Radio Gateway (RG). When applicable, the<br />

UE RRC forwards the information received to the NAS entities.<br />

The UE enters connected mode on NAS request when data must be transferred between the UE and<br />

the RG. It then continues to monitor the <strong>System</strong> Information messages.<br />

• connected mode: The UE has established a connection with the Network. This mode is divided<br />

into several states:<br />

o Connected: CELL-DCH<br />

• One or more dedicated physical channel(s) is allocated to the UE<br />

• The UE may monitor FACH for <strong>System</strong> Info messages<br />

o Connected: CELL-FACH<br />

• No dedicated physical channel, FACH and RACH are used instead<br />

• The UE listens to BCH (Broadcast Channel) for <strong>System</strong> Information<br />

o Connected: CELL-PCH<br />

• No physical channel is allocated<br />

• The UE is accessible only via the PCH (Paging Channel)<br />

• It listens to <strong>System</strong> Information on BCH<br />

4.3.4.6.4 RRC procedures and messages<br />

The RRC protocol procedures are detailed in specification [25.331]. The following procedures are<br />

implemented in the <strong>Moby</strong> <strong>Dick</strong> framework.<br />

Broadcast of system information<br />

RG → UE - - SYSTEM INFORMATION <strong>System</strong> Information is broadcasted in <strong>System</strong><br />

Information Blocks. The following ones are used:<br />

• SIB type 1 : NAS system information as well as<br />

UE timers and counters to be used in idle mode<br />

and in connected mode<br />

• SIB type 5: parameters for the configuration of the<br />

common physical channels in the cell.<br />

• SIB type 11: measurement control information to<br />

be used in the cell.<br />

• SIB type 18: Identities of neighbouring cells to be<br />

considered in idle mode as well as in connected<br />

mode.<br />

RRC connection establishment<br />

UE → RG - RRC CONNECTION REQUEST<br />

RG → UE - RRC CONNECTION SETUP<br />

UE → RG - RRC CONNECTION SETUP<br />

COMPLETE<br />

RG → UE - RRC CONNECTION REJECT<br />

RRC connection release<br />

UE → RG – RRC UL CONNECTION RELEASE<br />

Initial Direct transfer<br />

UE → RG - INITIAL DIRECT TRANSFER<br />

Downlink Direct transfer<br />

RG → UE - DOWNLINK DIRECT TRANSFER<br />

The purpose of this procedure is to release the RRC<br />

connection including and all radio bearers between the<br />

UE and the Network. By doing so, all established<br />

signalling connections will be released.<br />

The initial direct transfer procedure is used in the<br />

uplink to establish a signalling connection. It is also<br />

used to carry an initial upper layer (NAS) message over<br />

the radio interface<br />

The downlink direct transfer procedure is used in the<br />

downlink direction to carry upper layer (NAS)<br />

messages over the radio interface.<br />

D0103v1.doc 94 / 168

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!