Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
authentication scheme deployed by the access link paging procedure. Also the paging process related
proprietary encryption of access link paging messages is to be handled within this function block.
On reception of an IP paging request message from the signalling relay block, in particular the common
IP paging ID is processed and the Solicited Node Multicast address for the respective access technology
interface is derived from it. In case of having TD-CDMA as access technology, the mapping function is
responsible for building of paging signalling messages and interaction with the Radio Gateway through
the signalling socket.
4.2.2.4.3 Dormant Monitoring Agent Functional Entity (DMA)
The Dormant Monitoring Agent function is responsible to capture/receive user-data traffic, destined for
dormant mobile terminals. In Moby Dick, this function is co-located with the Paging Agent node, since
with a Mobile IPv6 system, the concept implies the registration of the PA node address as alternate CoA
with the HA for dormant mobile terminals. Therefore, initial packets, destined for dormant mobile
terminals, are forwarded from the HA to the PA by means of IP-IP encapsulation. The DMA function
receives the tunnelled packets and represents a temporary tunnel endpoint for the HA originated tunnel.
User-data packets will be processed and it’s checked, whether or not the actual addressed node has
registered with the PA. If the address cannot be matched with one of the registered mobile terminals, the
packet has to be dropped and an ICMPv6 Error message has to be sent, indicating that the destination is
not reachable.
If the user-data packet addresses a mobile terminal registered as dormant with the PA, the DMA function
has to buffer the packet and check a previously set individual filter function, indicating whether or not
this type of packet is allowed to trigger a paging procedure. During a paging process, the packet is to be
buffered and after the current location has been found out through the paging mechanisms, the DMA has
to re-address the packet and forward it to the current location of the addressed mobile terminal by means
of IP tunnelling.
The size of buffers, which should be available for storing user-data packets temporarily for individual
registered mobile terminals during a paging process, should be configurable for an administrator.
4.2.2.4.4 Tracking Agent Functional Entity (TA)
The Tracking Agent is responsible for tracking a dormant mobile terminal’s location. Paging area
registrations and updates are to be processed by this functional block. The paging area update message
can be either originated from the MT or from the paging attendant implemented in a paging area’s Access
Router in case of getting related L2 support from access technologies while being dormant. In case the
DMA receives a validated user-data packet (paging trigger packet) destined for a registered dormant
mobile terminal, the DMA requests the TA to initiate the paging process. The TA checks for the paging
area the dormant mobile terminal has registered with. The TA initiates paging the mobile terminal by
telling the registered paging area to the PA-function. After a successful page, the TA gets information
from the PA-function about the current location of the paged mobile terminal. The location information is
given to the DMA function to allow forwarding of buffered paging trigger packet for the addressed
mobile terminal.
4.2.2.4.5 Paging Agent Functional Entity (PA)
The Paging Agent function is responsible for generation and distribution of generic IP paging
messages. The paging request signalling messages address all paging attendants implemented
in a registered paging area’s set of Access Routers. The Paging Agent function receives a
notification from the TA function to page an individual mobile terminal.
Addressing a paging area:
If the registered paging area comprises N Access Routers, N IP paging request messages have to be
generated and to be distributed to the ARs individually. If static paging areas are deployed, a multicast
tree could be set up for each set of ARs building a paging area. In the latter case, the PA addresses one IP
paging request message to the paging area’s multicast address. The deployment of multicast addressing of
paging areas won’t be deployed within the Moby Dick project. Rather lists of ARs access interface
addresses are maintained in the Paging Agent node. Later, this list could be maintained by an external
paging server.
4.2.2.5 QoS Manager
The QoS manager is responsible for QoS activities in the AR. Figure 37 shows the QoS Manager and its
relationship with other components.
D0103v1.doc 51 / 168