Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
AUDITING Availability for ksat72.ipv6.rus.uni-stuttgart.de:QoSManager:
2003-04 down=43155 => violation
It shows that during April 2003, the downtime of the QoS Manager entity is 43155 seconds, which leads
to the conclusion, that the commitment is violated.
Another example report of the examination on user registration for the user cco@rus.uni-stuttgart.de
shows the following:
AUDITING User Registration for cco@rus.uni-stuttgart.de:
2003-05-09 14:23:36 3 1 0 0 0 net-err= 0 usr-err= 0 => no violation
2003-05-09 14:33:50 1 0 0 0 0 net-err= 0 usr-err= 0 => no violation
2003-05-09 14:45:16 1 2 1 1 1 net-err=4002 usr-err= 0 => violation
The report shows that there is a violation of the guarantee on registration success. User cco@rus.unistuttgart.de
tried to register at 2003-05-09 14:45:16 and received a negative response with the code 4002
(DIAMETER_OUT_OF_SPACE). The user has performed registration retries as required (more than 5
times as can be seen in the series of number 1 2 1 1 1, that shows number of retries in each interval).
A similar report is also generated for the examination of service authorization event logs.
4.6 Paging Agent Software Specification
This section provides an overview on the Paging Agent software components, associated interfaces to
remote nodes and implementation specific information.
4.6.1 Overview of the different functional components
The following figure illustrates the logical functions of the Paging Agent node.
IP paging module
AR
Tracking
Agent
Component
MT
AAAC.f
Paging Agent
Functional
Component
Dormant
Monitoring
Agent Comp.
Enhanced IPv6 stack
Standard IPv6 stack
Network Device
Ethernet
Figure 93: Paging Agent Software Architecture.
The protocol interface to the AAAC.f , as illustrated in the figure above, can be used optionally according
to the paging concept in case, the proposed security mechanisms are supported. This interface has been
proposed in the concept, but has not been implemented and is not used in the integrated Moby Dick testbed.
4.6.2 Description of the different functional components
4.6.2.1 Dormant Monitoring Agent Functional Entity (DMA)
The Dormant Monitoring Agent function is responsible to capture/receive user-data traffic, destined for
dormant mobile terminals, which have been registered with the Paging Agent node before. In Moby Dick,
this function is co-located with the Paging Agent node, since with a Mobile IPv6 system, the concept
deploys the registration of the PA node address as alternate CoA with the HA for dormant mobile
terminals (MTs). 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
D0103v1.doc 140 / 168