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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

D0103v1.doc Version 1 6.7.2003<br />

associated radio bearer Id, to warn it that the radio bearer is now closed and no data packet for the<br />

associated radio QoS class can be sent.<br />

Send / Receive Data sub-block<br />

The Send / Receive Data sub-block manages the sending and reception of data packets to and from the<br />

AS.<br />

When an IP data packet is received from the RCM, with the associated radio bearer id and SAP Id, the<br />

radio bearer is already opened (this has been taken care of in the RCM, before transmitting this packet).<br />

Therefore, the RCF directly makes a PDCP_DATA_REQ to the AS on the appropriate SAP, to transfer<br />

the data packet to the Radio Gateway, with parameters radio bearer id, data packet length and data packet.<br />

When an IP data packet sent by the Radio Gateway is received from the AS via the message<br />

PDCP_DATA_IND, with parameters: radio bearer id, data packet length and data packet; this IP data<br />

packet is directly transmitted to the Packet Reception block of the RCM.<br />

4.1.2.5 Fast Handover module<br />

MTNM<br />

Set<br />

Network<br />

Preferences<br />

Set<br />

Handover<br />

Preference<br />

Automatic / Manual<br />

Handover<br />

Network<br />

Environment<br />

Infos<br />

Fast RCF Handover Module<br />

Context<br />

Transfer<br />

WCDMA<br />

Connection Manager<br />

Wcdma<br />

Infos<br />

Fast Handover<br />

Execution<br />

Open /<br />

Close<br />

Enhanced IP stack and<br />

Mobile IP stack<br />

Network device drivers<br />

TDCDMA WLAN Ethernet<br />

Figure 16: FHO module and its interfaces<br />

The Fast Handover module must be installed on every Access Router and Mobile Node wanting to<br />

exchange FHO messages in the <strong>Moby</strong> <strong>Dick</strong> scenario. It provides the complete Fast Handover IP<br />

mechanism and signalling for fast intra-domain handover. The module must not be triggered for interdomain<br />

handover, since administrative domain distinction within the <strong>Moby</strong> <strong>Dick</strong> trial is provided in the<br />

MTNM by comparison of the last two bits of the IPv6 network-prefix. The inter-domain handover will be<br />

handled like a new registration, since this kind of handoff may not be fast, because the home domain must<br />

be contacted.<br />

The following figure sketches the relations of the Fast Handover Linux Kernel Module with the related<br />

<strong>Moby</strong> <strong>Dick</strong> components on the Mobile Terminal, i.e., the MTNM, IP/MIPL stack and the network device<br />

drivers.<br />

The Fast Handover module has been implemented as a Linux kernel module, because this provides most<br />

possible independence from the IPv6 and Mobile IPv6 stack and at the same time provides fast message<br />

processing. The fast handover signalling messages are sent via the enhanced IPv6 stack, i.e., deploy the<br />

sending functionality of this stack, and therefore this module does not require awareness of the current<br />

access technology.<br />

D0103v1.doc 33 / 168

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

Saved successfully!

Ooh no, something went wrong!