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

represents a temporary tunnel endpoint for the HA originated tunnel. User-data packets' address<br />

information will be processed and it is checked, whether or not the actual addressed node has registered<br />

as dormant with the PA before. If the address cannot be matched with one of the registered mobile<br />

terminals, the packet has to be dropped and an ICMPv6 Error message has to be sent, indicating that the<br />

destination is not reachable.<br />

If the user-data packet addresses a mobile terminal that has been registered as dormant with the PA, the<br />

DMA function has to buffer the packet and checks a previously set individual filter function, indicating<br />

whether or not this type of packet is allowed to trigger a paging procedure. As a default function setting,<br />

this filter allows all packet types and addressing types to initiate re-activation of the addressed dormant<br />

mobile terminal. During a paging process, the packet is to be buffered and after the current location has<br />

been found out through the paging mechanisms, the DMA has to re-address the packet and forward it to<br />

the current location of the addressed mobile terminal by means of IP tunnelling mechanism. The<br />

configuration of the packet filter function, as described briefly above, has not been implemented in the<br />

<strong>Moby</strong> <strong>Dick</strong> test-bed, but is for future optimisation. Hence, all kind of user-data packets, addressing a<br />

dormant mobile terminal and being forwarded from the HA to the PA, will initiate paging the mobile<br />

terminal.<br />

The size of buffers, which should be available for storing user-data packets temporarily for individual<br />

registered mobile terminals during a paging process, has been implemented to be configurable for an<br />

administrator.<br />

4.6.2.2 Tracking Agent Functional Entity (TA)<br />

The Tracking Agent function is responsible for tracking a dormant mobile terminal’s location. Paging<br />

area registrations and updates are to be processed by this functional block. The paging area update<br />

message can be either originated from the mobile terminal or from the paging attendant implemented in a<br />

paging area’s Access Router. In case the DMA receives an initial user-data packet (paging trigger packet)<br />

destined for a registered dormant mobile terminal, the DMA requests the TA to initiate the paging<br />

process. The TA checks for the paging area the dormant mobile terminal has registered with. The TA<br />

initiates paging the mobile terminal by means of providing the registered paging area information to the<br />

PA-function. After a successful page, the TA gets information from the PA-function about the current<br />

location of the paged mobile terminal. The location information is given to the DMA function to allow<br />

forwarding of buffered paging trigger packet for the addressed mobile terminal.<br />

4.6.2.3 Paging Agent Functional Entity (PA)<br />

The Paging Agent function is responsible for generation and distribution of generic IP paging messages as<br />

well as for the co-ordination of the paging process. The paging request signalling messages address all<br />

paging attendants implemented in a registered paging area’s set of Access Routers. The Paging Agent<br />

function receives a notification from the TA function to page an individual mobile terminal.<br />

Addressing a paging area:<br />

If the registered paging area comprises N Access Routers, N IP paging request messages are to be<br />

generated and to be distributed to the paging area’s ARs implementing the paging attendant function. If<br />

static paging areas are deployed, a multicast tree could be set up for each set of ARs building a paging<br />

area. In the latter case, the PA addresses one IP paging request message to the paging area’s multicast<br />

address. The deployment of multicast addressing of paging areas will not be deployed within the <strong>Moby</strong><br />

<strong>Dick</strong> project. Rather lists of ARs' access interface addresses are maintained in the Paging Agent node to<br />

keep addressing of paging attendant functions in ARs flexible, which allows operation of enhanced<br />

paging strategies in the future.<br />

4.6.3 Softwarimplementation / interfaces<br />

4.6.3.1 Interface between the Mobile Terminal and the Paging Agent<br />

4.6.3.1.1 Description<br />

In case of having a pre-established security association with the PA, the mobile terminal can<br />

communicate directly to the PA, if the current AR allows respective ICMPv6 message types passing<br />

through, either based on a previously established security association ??? or administrative setting of AR<br />

filter functions (also taking QoS and AAA filtering function on ARs into account). This can happen after<br />

the discovery phase (explicit dormant mode registration) as well as for paging area updating and dormant<br />

mode de-registration.<br />

The remote entities deploy the ICMPv6 protocol as specified for the IP paging concept in <strong>Moby</strong> <strong>Dick</strong>.<br />

4.6.3.1.2 Message types<br />

Source Dest Primitive Parameters<br />

D0103v1.doc 141 / 168

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

Saved successfully!

Ooh no, something went wrong!