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

attendant. The respective PBKs are to be extracted from the generic IP paging request message originated<br />

from the Paging Agent.<br />

The remote signalling peers (MT, RG and PA) are shown in the figure above and connected to the IP<br />

paging attendant through a dotted line for illustration purposes.<br />

IP Paging attendant<br />

MT<br />

Signaling<br />

relay<br />

PA<br />

RG<br />

Mapping<br />

function<br />

Enhanced IPv6 proto<br />

DiffServ<br />

IPv6<br />

IPSec<br />

Network device drivers<br />

WLAN<br />

Ethernet<br />

Figure 36: Paging Agent<br />

4.2.2.4.1 Paging Attendant Signalling Relay<br />

The signalling relay block represents the actual attendant function, receiving IP signalling<br />

messages from mobile terminals for Paging Agent (PA) discovery, implicit registration and<br />

paging area update. Furthermore, during a paging process this functional block receives the<br />

generic IP paging procedure related signalling messages from the respective PA. If L2 support<br />

from access technologies is available, the mapping function described in 4.2.2.4.2 performs<br />

appropriate conversion.<br />

Receiving an IP dormant registration message from a mobile terminal, the signalling relay<br />

checks its database for a responsible PA. Alternatively, PA address discovery can be initiated<br />

from the AR or a remote database can be contacted. The dormant registration is to be relayed<br />

to the responsible PA. The reply messages, originated from the PA, have to be relayed back to<br />

the mobile terminal.<br />

In case of receiving a paging request message from a PA, the signalling relay does not process the IP<br />

signalling message. The paging request message content is to be passed to the mapping function.<br />

4.2.2.4.2 Paging Agent Mapping Function<br />

During a paging process, the mapping function is responsible for generating the appropriate on-link<br />

paging request message. This can be either an IP paging message, addressing the Solicited Node<br />

Multicast Address, or a technology proprietary signalling sequence. On L2 support of respective access<br />

technologies, the mapping function represents an additional block for conversion between access<br />

technology specific location management signalling and respective IP signalling.<br />

For paging area update signalling, the mapping function block of the attendant can support a mobile<br />

terminal’s dormant mode if the respective access technology allows tracking and signalling of/from<br />

dormant mobile terminals on L2 mechanisms. The attendant on the first AR of the new paging area could<br />

then map the access technology specific indication to update the paging area to a generic IP paging area<br />

update message, which is to be forwarded to the appropriate PA then. This mechanisms is allowed to be<br />

implemented from paging attendants in ARs, but will not be specified and implemented within the<br />

framework of the <strong>Moby</strong> <strong>Dick</strong> project<br />

The mapping function is also responsible for extracting the PBKs from the generic IP paging message<br />

sent from the PA to the respective ARs. This key is to be processed and mapped to the proprietary<br />

D0103v1.doc 50 / 168

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

Saved successfully!

Ooh no, something went wrong!