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

1. It detects Router Advertisements (and so, the respective ARs). The IPv6 addresses of these ARs,<br />

the corresponding subnet prefixes, and the signal levels associated with the frames that contain<br />

the respective Router Advertisements, are sent to the MTNM in a WLAN_INFO message. If no<br />

Router Advertisements are received from the AR the MT is using, the IPv6 address of this AR<br />

must nevertheless be included in the WLAN_INFO message with signal level “0” (this indicates<br />

to the MTNM that the WLAN connection is lost).<br />

2. The Router Advertisements received from the AR the MT is using, are sent to the IPv6 stack.<br />

Any other Router Advertisements are not sent to the IPv6 stack. The filtering function knows the<br />

AR the MT is using because, each time a handover is executed, the MTNM sends a message<br />

USE_WLAN_AR to the WLAN driver. This message includes the IPv6 address of the AR to<br />

use, and the respective network prefix.<br />

3. All broadcast traffic that does not belong to the IPv6 subnet of the AR the MT is using, is<br />

discarded. The subnet is identified by the source address of the packet, using the subnet prefix of<br />

the subnet of the current AR.<br />

4.2 Access Router Software Specification<br />

Figure 29 depicts a functional overview of the Access Router (protocol communications with MT are not<br />

shown in this figure).<br />

The basic functional blocks are:<br />

• The Fast Handover Module which is responsible for an appropriate context transfer for intra-mobility<br />

scenarios.<br />

• A Paging Attendant which is responsible for paging in the connected access cell.<br />

• The AAAC Framework which is represented by a Metering module and the AAAC Attendant.<br />

• A QoS Attendant which is responsible for executing QoS related actions on the Access Router.<br />

• The Enhanced IPv6 stack and the Network Device Drivers.<br />

• The Logger which is responsible for logging availability, registration, and authorization events.<br />

All these modules will be described in greater detail in the following sections.<br />

4.2.1 Overview of the different components<br />

This section splits the components identified before in sub-blocks, giving an overview of their role. The<br />

detailed behaviour of these sub-blocks and their interactions will be detailed in the next chapter.<br />

4.2.1.1 Fast Handover Module / MIPL<br />

It provides the implementation of fast handover procedures. Also, this module will take care of the<br />

context transfer of some AAAC, and security parameters that will be done between the old AR and the<br />

new AR to speed up handover. QoS context is transferred by the QoS infrastructure.<br />

4.2.1.2 Paging Attendant<br />

The IP paging attendant implements procedures for IP paging support:<br />

1. Procedures for PA discovery.<br />

2. Procedures for paging request. PA will send paging requests from which the AR will create an<br />

on-link paging request to awake the dormant MT (if it is in the corresponding cell).<br />

4.2.1.3 Network Device Driver /WLAN<br />

This is a standard WLAN driver. In <strong>Moby</strong> <strong>Dick</strong> the hostap driver (http://hostap.epitest.fi/), version 19-05,<br />

by Jouni Malinen is used.<br />

4.2.1.4 Enhanced IPV6/IPSec/DiffServ packet Filter<br />

The enhanced IPv6 stack is based on the IPv6 stack of the linux kernel 2.4.16. Functionality that must be<br />

present:<br />

• Standard IPv6 functionality.<br />

• IPSec: for authentication of packets.<br />

• Mobile-Ipv6, needed for Fast-Handoff implementation<br />

• Diffserv and packet filter, that includes:<br />

o Filtering: all packets received must belong to a flow in the DSCP table or they must be<br />

signalling packets for network access procedures (a particular DSCP code) that must be<br />

given to upper layers. If not, they must be dropped.<br />

o Shaping: when sending packets, to control that flows adjust to agreed bandwidth.<br />

D0103v1.doc 44 / 168

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

Saved successfully!

Ooh no, something went wrong!