Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
• All routers: Since they have to forward the packets of QoS flows.
• HA: In case, the CN does not know the location of the MT, the packets will be sent to the HA
which has then to forward the traffic to the “new” location of the MT.
• PA: If the MT is in idle state, the HA will forward the first few packets to the PA by using
tunnelling. This tunnels have to be DS aware and will be probably implemented by mapping the
respective DS code point from the tunnelled IP packet into the code point of the tunnelling IP
packet.
Connectivity to the QoS aware IP backbone: The different domains are connected via at least one DS
egress/ingress router to the backbone. The same is valid for the inter-connection of the access networks to
the domain’s “backbone”. These “sub-network” access routers can be fully mashed. However, they
should have full IPsec, DS, and mobility support. These are the first and important policy points for
incoming traffic (from the MT towards the backbone).
4 Moby Dick Physical Components
As a preparation for the implementation, the following types of physical elements were identified based
on the logical and conceptual Moby Dick architecture:
i) Mobile Terminal (MT)
ii) Access Router (AR)
iii) Radio Gateway (RG)
iv) QoS broker (QoSB)
v) AAAC Server
vi) Paging Agent (PA)
vii)Home Agent (HA)
At least one set of functions has been identified for each of the physical element types, and these will be
one or more software modules of the implemented system. The following sub-sections contain the
complete list of functions that are associated with each physical element type. They represent the
maximum list of functions, and some physical element instances may not need all of them. Each function
includes handling the associated message flows.
Mobile Terminal and Access Router are the two components which host logical modules of all three
implementation workpackages. Paging Agent and Home Agent are modules which mostly fulfil functions
for mobility management and thus are mainly derived from WP3 work. The QoS Bare mainly based ,
Access Router is of course a component which is exclusively provided by Moby Dick WP2 and the
AAAC Server is a WP4-exclusive component. Further, the Radio Gateway is a component for SC-TDMA
specific radio access with high interaction and involvement of WP2.
4.1 Mobile Terminal Software Specification
This section gives the software specification of the different components of the Mobile Terminal. These
include
• Networking Control Panel (NCP, section 1.1.1): graphical user interface to specify user
preferences and initiate manual handover execution.
• Mobile Terminal Network Manager (MTNM, section 1.1.2): module to decide about handover
execution.
• Fast Handover module:…
• Registration Module
• Paging Module
• Enhanced IPv6 Stack
• Network Device Drivers
Below is a high level integrated view of the different components.
D0103v1.doc 14 / 168