Step 1: The server is started. The NAS module in
the server talks to the NAS module on the Local
LAN to get access to its wireless infrastructure.
Step 2: The QBS security module on the server
informs the QBS module in the core network about
its Service Level Agreement which contains the QoS
associated with a connection to this service.
Step 3: The mobile node is started. The NAS
module in the mobile node contacts the NAS module
in the peripheral networks to gain access to the
wireless infrastructure.
Step 4: When the mobile node wants to use the
service, the QBS Module in the mobile node
contacts the QBS module in the core network and
asks for a connection with a given quality of service
to be made to the Server. The QBS module returns
two core endpoints which must be used to set up the
connection.
Step 5: The NTS module on the mobile node
contacts the NTS module in the core network and
says that it would like a connection to the server,
using the core endpoints, the QoS and security
parameters.
Step 6: The NTS module in the core network
contacts the NTS module on the server to signal an
incoming call. At this point, the server can also
check the security of the client as well as the
security of the connection.
Step 7: If the server accepts the request, then the
NTS module in the core network joins the two core
endpoints.
Step 8: It then signals to both the client and
server that a connection has been established.
2.1.2 Ring-based Security Model
Ring-based security is an extension of “Off-by-
Default”, an idea introduced by (Ballani, et al.,
2005) See Figure 4. The Ring-Based concept does
not allow servers to be directly accessible over a
WAN such as the Internet without initially
interacting with the network infrastructure. This is
done by using the concept of scope where a server
acts only within a given scope. There are 3 scopes:
Local: Only processes on the same machine are
allowed to use a local server. This is enforced by the
SAS layer on the local machine.
LAN: Only processes on the same network are
allowed to access these servers. This is enforced by
the NAS layer of the Peripheral Network. These
servers must register with a Local DNS and are
made available to mobile devices when users are
cleared to use the peripheral network.
Global: Global Servers are accessible from any
point via the Core Network using Global Services.
This therefore involves the Core NTS and QBS
layers. In addition, servers must register with the
Global DNS.
2.1.3 Vertical Handover Security Model
As shown in Figure 5, in addition to the
Authentication, Authorization, Auditing and Cost
(AAAC) servers, new entities are involved in the
Vertical Handover Security Model (VHSM); the
QoS Brokers (QoSB) which monitor the network
performance and QoS-related issues; it accomplishes
this using admission control and auditing
mechanisms. This model is given by the steps
below:
Step 1: The QBS layer of the MN asks the QBS of
the QoSB about potential target network for
handover with required QoS and security level.
Step 2: The request is passed to the QBS layer of
the Core endpoint.
Step 3: If this information has not been already in
the Core-End point, the QoS Brokers of all the
available networks are probed by the core endpoint.
At the end of this first stage, the MN has a clear idea
of the QoS and security suits available at all
potential networks in the vicinity and could decide
on the target network for future handover.
Step 4: The NAS layer of the MN initiates a Re-
authentication process to lunch the security
mechanisms in the target network.
Step 5: Through its NAS layer, the currently
serving AAA server (CAAA) forwards the re-
authentication request along with core information
that are used to derive a fresh set of the security
parameters for the new network to the NAS layer of
a Central Authority (CA) in the Core endpoint.
Figure 4: Ring based Security Model.
Step 6: If the target network is located in the core-
endpoint, CA’s NAS layer passes the core
information to the target network to derive the
security materials and achieves the triple A tasks.
SECRYPT 2010 - International Conference on Security and Cryptography
320