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 />

RCF to establish it, with the local connection reference, the DSCP code, the source and destination<br />

address of the IP packet, as parameters.<br />

An answer is expected from the RCF, to give the status of this operation, upon which the radio bearer is<br />

declared established or not. The answer will contain the original DSCP code, the radio bearer Id and a<br />

SAP Id as parameters.<br />

If the bearer is established, the IP data packets can be transmitted to the Data Channel Management block<br />

of the RCF (with the radio bearer Id and SAP id), to be sent on the radio bearer by the AS.<br />

Two requests to open a radio bearer can be handled in parallel.<br />

While the request to open a radio bearer is handled, the corresponding IP packets will be stored to be sent<br />

when the bearer is effectively established.<br />

Important point: before the user has been authenticated and authorized, no IP data packet should be<br />

transferred (they should be buffered in the TD-CDMA driver); only signalling packets should be<br />

transferred. This means we should not attempt to open radio bearers until we are authenticated and<br />

authorized.<br />

In the current implementation, we will not buffer IP data packets, we will open radio bearers, and it will<br />

be up to the AAAC Attendant in the Access Router to control the IP packets received, and let them go<br />

further or not.<br />

In a more advanced implementation design, the MTNM could warn the RCM that we are authenticated<br />

and authorized via a specific control message. Before its reception, we buffer IP data packets and after its<br />

reception, we open radio bearers and send IP data packets. This will not be part of the <strong>Moby</strong> <strong>Dick</strong><br />

implementation.<br />

4.1.2.3.6 Packet Reception block<br />

Enhanced IPv6 stack<br />

RCM<br />

Radio Connection<br />

Manager<br />

Radio<br />

Infos<br />

Open /<br />

Close<br />

Packet Transmission<br />

Control Data<br />

Packet Packet<br />

Packet Reception<br />

Control Data<br />

Packet Packet<br />

Conn<br />

RCF<br />

TD-cdma<br />

Infos<br />

TD-CDMA<br />

Connection Manager<br />

Open /<br />

Close<br />

Conn<br />

Paging<br />

Control Channel Mngt<br />

Send /<br />

Receive<br />

Data<br />

Data Channel Mngt<br />

Open / Send /<br />

Close Receive<br />

Data Data<br />

Chanels<br />

AS<br />

Figure 14: Packet Reception block<br />

The IP signalling packets and the IP data packets received from the RCF are directly transmitted to the<br />

IPv6 stack. Some of the IP signalling packets are “pure” IP signalling and will be used by the IPv6 stack.<br />

The other IP signalling packets will be automatically directed to the appropriate module (fast handover,<br />

registration or paging) by the IPv6 stack.<br />

D0103v1.doc 30 / 168

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

Saved successfully!

Ooh no, something went wrong!