Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
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 />
Uplink Direct transfer<br />
UE → RG - UPLINK DIRECT TRANSFER<br />
UE dedicated paging<br />
RG → UE - PAGING TYPE 2<br />
The uplink direct transfer procedure is used in the<br />
uplink direction to carry all subsequent upper layer<br />
(NAS) messages over the radio interface belonging to a<br />
signalling connection.<br />
This procedure is used to transmit dedicated paging<br />
information to one UE in connected mode in<br />
CELL_DCH or CELL_FACH state. Upper layers in<br />
the network may request initiation of paging.<br />
Radio bearer establishment<br />
RG → UE - RADIO BEARER SETUP<br />
UE → RG - RADIO BEARER SETUP COMPLETE<br />
UE → RG - RADIO BEARER SETUP FAILURE<br />
Radio bearer release<br />
RG → UE - RADIO BEARER RELEASE<br />
UE → RG - RADIO BEARER RELEASE<br />
COMPLETE<br />
UE → RG - RADIO BEARER RELEASE FAILURE<br />
Cell update procedures<br />
UE → RG - CELL UPDATE<br />
RG → UE - CELL UPDATE CONFIRM<br />
The cell update procedures serve several main<br />
purposes:<br />
• to notify the Network of an RLC unrecoverable<br />
error [25.322] on an AM RLC entity;<br />
• to be used as a supervision mechanism in the<br />
CELL_FACH state by means of periodical update.<br />
• to act on a radio link failure in the CELL_DCH<br />
state;<br />
The cell update procedures may:<br />
• cause a state transition from the CELL_FACH<br />
state to the CELL_DCH state or idle mode.<br />
The cell update procedure may also include:<br />
• a re-establish of AM RLC entities;<br />
• a radio bearer release.<br />
4.4 QoS Broker Software Specification<br />
Table 16 : RRC procedures and messages<br />
This section describes the software specification of the Bandwidth Broker (QoS Broker). It will describe<br />
the <strong>Moby</strong> <strong>Dick</strong> components that interact with the QoS Broker, the broker’s interfaces and all its internal<br />
functions.<br />
On each QoS Broker interface we will discuss the messages exchanged between the QoS Broker and the<br />
other <strong>Moby</strong><strong>Dick</strong> components, its format and when they will occur. At the end of the section we will<br />
resent the QoS Broker databases format, and discuss its purpose.<br />
A bandwidth broker is an entity that takes admission control decisions and configures all access network<br />
components, according to a set of conditions given by administration entities.<br />
4.4.1 General QoS Broker Positioning<br />
Figure 70 shows a view of all the entities of the <strong>Moby</strong> <strong>Dick</strong> project that interact with QoSBroker.<br />
D0103v1.doc 95 / 168