Escolar Documentos
Profissional Documentos
Cultura Documentos
Implementation
Pedro Neves1, Ricardo Matos2, Bruno Sousa3, Giada Landi4, Susana Sargento2, Kostas
Pentikousis5, Marilia Curado3, Esa Piri5
1
Portugal Telecom Inovação, pedro-m-neves@ptinovacao.pt, Aveiro, Portugal
2
University of Aveiro, {ricardo.matos, susana}@ua.pt, Aveiro, Portugal
3
University of Coimbra, {bmsousa, marilia}@dei.uc.pt, Coimbra, Portugal
4
Nextworks, g.landi@nextworks.it, Piza, Italy
5
VTT Technical Research Centre of Finland, first.lastname@vtt.fi, Oulu, Finland
R1 WiMAX
WiMAX
ASN
Serving R6
CSN
WiMAX BS R3 DNS
R8
MS CSN-GW
AAA
R6 ASN-GW
(Foreign Agent) Figure 2: WEIRD mobility and QoS integrated
Target architecture
WiMAX BS MIP
(Home Agent)
DHCP
During the session setup phase, the Connectivity
Figure 1: WiMAX Network Reference Model Service Controllers (CSCs) interact with the service
layer in order to retrieve information from the
The MS is responsible for establishing radio applications, regarding the traffic type and the required
connectivity with the serving BS. The ASN is QoS parameters. In particular, two different
composed by a set of BSs connected to one or several approaches can be adopted in order to support both
ASN-Gateways (ASN-GW). The ASN-GW is the legacy and IP Multimedia Subsystem (IMS)
gateway for the ASN, establishing connectivity with applications, based on the Session Initiation Protocol
the CSN. The ASN includes the required (SIP) [23] and Session Description Protocol (SDP)
functionalities to provide radio connectivity with signaling. For legacy applications, the QoS signaling is
WiMAX subscribers, such as the establishment of initiated by the MS. The Connectivity Service
signaling and data service flows (with the required Controller located at the MS (CSC_MS) communicates
WiMAX QoS parameters) in the WiMAX air link, as with a module, called WEIRD Agent (WA), in charge
well as micro and macro mobility support. of obtaining the application QoS parameters, such as
Additionally, it also performs relay functions to the required bandwidth, maximum latency and jitter.
CSN in order to establish IP connectivity and CSC_MS coordinates end-to-end QoS signaling, using
Authentication, Authorization and Accounting (AAA) the NSIS framework, translating the application QoS
mechanisms. The CSN provides connectivity with the parameters to a QSPEC (Qos SPECification) adopted
IP backbone and holds DHCP, DNS and AAA servers, in the WiMAX NSIS model [24] and initiating the end-
as well as Application Functions (AF) acting as the to-end signaling towards the ASN, the CSN and the
application-level controller. core network. In the case of IMS-like applications, the
The proposed mobility and QoS architecture, QoS signaling follows the network-initiated approach
illustrated in Figure 2, is compliant with the WiMAX and it is strictly connected to the application layer
Network Reference Model (NRM), and thus composed SIP/SDP signaling. The SIP Proxy located at the CSN
by the CSN, ASN and MS. Quality of Service and intercepts the SIP signaling between the SIP User
mobility functionalities are managed in a coordinated Agents and extracts the session description from the
way at the control plane level through the inter- SDP messages. The QoS parameters are forwarded to
communication and the combined processing of the the CSC located at the ASN (CSC_ASN), through a set
Connectivity Service Controller (CSC) modules, of Diameter [25] messages describing the media flows
located in each segment of the Network Reference included in the sessions, where they are translated into
Model (NRM). WiMAX parameters. In this case the QoS NSIS
signaling follows the edge-to-edge model since it is
initiated and controlled by the CSC_ASN.
For both legacy and IMS-like applications,
WiMAX resource reservations are handled by the
ASN-GW through the interaction of the CSC_ASN
with the link layer level. In particular, the WiMAX
Resource Control (RC) module hides all the WiMAX
technology related functionalities from the higher layer
entities of the architecture. It manages the WiMAX
Service Flows (SFs) creation, modification and
deletion, admission control mechanisms, and QoS
policies enforcement on the WiMAX system through a
set of technology dependent adapters. Detailed
information about standalone WEIRD QoS
management procedures has been published in [20]
[21]. Figure 3: IEEE 802.21 MIH framework
With respect to mobility procedures, the proposed
architecture is based on the IEEE 802.21 [5] In the WEIRD architecture (see Figure 2), the
framework and on the standardized Mobile IP (MIP) mobility management framework includes several
[26] protocol. IEEE 802.21 introduces a new entity instances of the MIHF, located at each segment of the
called MIH Function (MIHF), which hides the WiMAX Network Reference Model. The MIH events
specificities of different link layer technologies from are originated by the LLC (Link Layer Client) and
the higher layer mobility entities. Several higher layer include information about the link layer, such as the
entities, known as MIH Users (MIHUs), can take respective link status. The MIH commands are
advantage of the MIH framework, including mobility triggered by the MIHUs and are used to convey the
management protocols, such as Mobile IPv4 (MIPv4) handover decisions. The transport of the MIH protocol
[26], Fast Mobile IPv6 (FMIPv6), Proxy Mobile IPv6 messages between remote MIHF peers is supported by
(PMIPv6) and SIP [23], as well as other mobility the NSIS framework through the Media Independent
decision algorithms. In order to detect, prepare and Handover NSLP (MIH NSLP) [22]. The MIH NSLP
execute handovers, the MIH platform provides three was developed as an extension to the NSIS framework
services: Media Independent Event Service (MIES), in order to transport the MIH protocol messages. There
Media Independent Command Service (MICS) and are two main reasons to sustain this approach. First, the
Media Independent Information Service (MIIS). MIES IEEE 802.21 proposed standard does not specify any
provides event reporting such as dynamic changes in protocol for message exchange, providing only the
link conditions, link status and link quality. Since requirements for such protocol, namely, security and
multiple higher layer entities may be interested in these reliability. Second, QoS signaling, which is tightly
events simultaneously, they may need to be sent to coupled with mobility, is performed through the QoS-
multiple destinations. MICS enables MIHUs to control NSLP. In this context, the use of the NSIS framework
the physical, data link and logical link layer. The to support both QoS and mobility processes, illustrated
higher layers may utilize MICS to determine the status in Figure 4, becomes the natural choice, since it fulfills
of links and/or control a multimode terminal. the requirements for MIH message exchange between
Furthermore, MICS may also enable MIHUs to remote entities.
facilitate optional handover policies. Events and/or The mobility management architecture includes a
commands can be sent to MIHUs within the same Mobility Manager (MM) instance, acting as a MIH
protocol stack (local) or to MIHUs located in a peer User and strictly connected with the related
entity (remote). Finally, MIIS provides a framework by Connectivity Service Controller (CSC), located on
which a MIHF located at the MS or at the network side each segment of the Network Reference Model
may discover and obtain network information within a (NRM), and a Link Layer Client (LLC) located on the
geographical area to facilitate handovers. The objective MS. The LLC is in charge of monitoring the link
is to acquire a global view of all the heterogeneous condition (signal level for Wi-Fi and WiMAX links,
networks in the area in order to optimize seamless connected/disconnected cable for Ethernet). In case of
handovers when roaming across these networks. Figure link status variation, the related MIH event is triggered
3 illustrates the 802.21 MIH framework. and sent to the local MIHF through the
MIH_LINK_SAP. Here, it is delivered to the registered
MIHUs, both local and remote MMs, through the WiMAX fixed SS (target SS), located in the same ASN
MIH_SAP. of the serving SS. This type of scenario includes inter-
and intra-technology mobility procedures: the MS is
MIHF
(Mobility Info)
CSC
(QoS Info)
connected via Ethernet and makes an inter-technology
handover to a Wi-Fi network; at the same time, there is
an intra-technology handover from the serving
MIH QoS
NSLP NSLP WiMAX SS to the target WiMAX SS in the backhaul,
following the intra-ASN WiMAX mobility model.
GIST
NSIS
Link_Up
messages between MIH peers. Both QoS NSLP and
1
Initialization and session setup MIH_Link_Up
(Eth)
(Eth)
GIST are conformant with the specifications of the
MS
Serving SS 1 MIH_Link_Up
Link_Up
(Wi-Fi) IETF NSIS working group [6] [7] [8], whilst the MIH
ETH
SF
BS
(Wi-Fi)
NSLP was included in the WEIRD architecture to
WA_Resv_Req
NSIS_Resv_Req 2 transport MIH messages between peer remote entities
RC_Resv_Req
[22]. The MIH NSLP module has a northbound
Target SS
Create
WiFi AP
3 SFs at
RC_Resv_Resp
Eth side
NSIS_Resv_Resp
WA_Resv_Resp
interface with MIHF, compliant with the
MIH_NET_SAP specified in the IEEE 802.21
Link_Going_Down
Handover Preparation phase MIH_Link_Going_Down
(Eth)
(Eth)
4 standard, and a southbound interface with GIST acting
MS
Serving SS NSIS_Resv_Req according to the specification of GIST (see Figure 4).
RC_Resv_Req 5
ETH
SF
BS
6
Create
SFs at
For MIH events/commands propagation, MIHF
Target SS
RC_Resv_Resp WiFi side
NSIS_Resv_Resp delivers the messages to the MIH NSLP. The MIH
WiFi AP
SF MIH_Link_Action NSLP parses the received message and creates the
7 Link_Action
necessary information to instruct GIST on the delivery
Serving SS SF BS
Handover Execution phase process. Such information includes the MIH message
MS
Target SS
and Message Routing Information (MRI) which
Mobile IPv4
WiFi AP
SF contains information such as the type of transport
8 Link_Down
required (e.g. TCP for reliable delivery). The NSIS
ETH
Serving SS Handover Completion phase
BS
MIH_Link_Down
(Eth)
(Eth)
framework related modules have been implemented in
MS
NSIS_Del_Req
9
the Java programming language.
Target SS RC_Del_Req Delete
WiFi AP SFs at
SF
10 RC_Del_Resp
Eth side
NSIS_Del_Resp 4.2. LLC
Figure 6: Signaling diagram for QoS-aware The aim of the Link Layer Client (LLC) was to
handover implement a link information collector independent of
the specific hardware, vendor, or GNU/Linux kernel.
The resources previously allocated between the
For this, Linux natively provides convenient ways for
serving SS and BS are released during the Handover
application layer software to gather link specific
Completion phase. When the Ethernet cable is
information from the kernel and directly from the
unplugged, the LLC sends a Link_Down event (step 8),
network device drivers without modifications to both
forwarded by the MIHF to the MM_MS. The
of them. LLC constantly monitors the network link
CSC_MS, as responsible for the dynamic control of
states and, based on this information, provides events
sessions and resources, is in charge of handling the
through an Event Trigger module to the registered
deletion of the old WiMAX Service Flows for the
MIHF. For simplicity, in the examined scenario, LLC
existing sessions and initiates the related NSIS QoS
provides only Link_Up, Link_Down and synthetically
signaling towards the CSC_ASN (step 9). Finally, the
generated Link_Going_Down events. The monitored
link types are Ethernet and Wi-Fi.
Link states are identified in the Generic Link State while resources on the old path are released at the end
Monitor (GLSM) by observing the operation status of of the handover execution phase. These procedures are
access network interfaces. After each link is completely transparent for the application layer and are
operationally up and its link type has been identified, managed by the entity that acts as the main coordinator
GLSM initiates the Link-specific Information Monitor for the sessions involved in the handover: the MM_MS
(LSIM) which acquires link-specific information. For for host-initiated sessions and the MM_ASN for IMS-
instance, LSIM can obtain Access Point (AP) like applications.
information for Wi-Fi accesses. This information is Link layer information about the wireless link
gathered using ioctl system calls. status is monitored by LLC and sent to the MM
module through a set of MIH events carried by the
4.3. MIHF MIH NSLP signalling (for remote events). The strong
interaction between the CSC, which manages the
The MIHF is the core entity of the IEEE 802.21 sessions at the control plane, and the related MM,
framework. It provides communication with lower which manages the link layer MS status, allows the
layers through MIH_LINK_SAP, with upper layers system to allocate new resources in the target link for
through MIH_SAP and with remote MIHFs via the existing traffic flows whenever a new handover is
MIH_NET_SAP, using the MIH protocol [5]. During detected through the Link_Going_Down event.
initialization, each MIHF must be configured and Following the same approach, previously used
thereafter it automatically creates the communication resources are removed when the Link_Down message
sockets for each one of the standardized interfaces. is received, as presented in Figure 6.
Maps of events, commands and information services
are associated with each one of the MIHFs. The MIH 5. Testbed Evaluation
Users will also be associated to these sets of maps,
after having subscribed to one (or more) of the MIH This section describes the empirical evaluation of
services (MIES, MICS and MIIS). The MIHF receives the proposed mobility management architecture
messages from the MIHU, LLC or remote MIHF and prototype. The experimental scenario is illustrated in
reacts accordingly. For example, after receiving a link Figure 5. The testbed includes modules that implement
event from the LLC though the MIH_LINK_SAP, the the CSN, ASN and MS functionalities. Under the
MIHF must look for the subscribed MIHUs to this ASN, a real, commercial-of-the-shelf (COTS) WiMAX
event on the events list. For local MIHUs, the MIHF BS is directly connected to the ASN-GW. Two
must generate the correspondent MIH event and send it WiMAX SSs are connected to the BS creating a Point-
through the MIH_SAP, whereas for remote MIHUs to-Multipoint topology. The MS is connected to SS#1
subscriptions, the MIHF must deliver the MIH event to by Ethernet and to SS#2 by Wi-Fi. A streaming server
the MIH NSLP through the MIH_NET_SAP. is located in the CSN broadcasting a video towards the
MS.
4.4. CSC & MM The goal of this scenario is to demonstrate a
handover process between Ethernet and Wi-Fi,
As mentioned above, each segment of the WiMAX backhauled by a fixed WiMAX link, while the MS is
network is managed by a Connectivity Service receiving a video stream. Initially the MS is connected
Controller (CSC), with its own Mobility Manager to SS#1 using an Ethernet cable. For the video stream
(MM). CSC has, as its main role, to manage sessions at to traverse the WiMAX link towards the MS it is
the control plane, coordinating all relevant related required to establish two Service Flows between the
signalling at different layers and the resource BS and SS#1, one for the downlink and one for the
reservation in the WiMAX link, which is dynamically uplink, with 512 Kbps each. While the user is receiving
updated during the session setup and the handover the video stream through the concatenated WiMAX
phases. In particular, the CSC_MS is the main and Ethernet link, he decides to unplug the Ethernet
coordinator for sessions of applications based on host- cable and connect to the Wi-Fi link. This behavior
initiated QoS signalling, while the CSC_ASN has the automatically triggers a vertical handover procedure
same role for IMS-like applications that adopt the from Ethernet to Wi-Fi, leading to the handover
network-initiated approach. Resource allocation on the preparation phase. During this phase, the required
WiMAX link follows the network-initiated model and resources on the concatenated WiMAX (BS and SS#2)
is handled by the CSC_ASN at the ASN-GW. and Wi-Fi link are reserved for the MS. After the
The resource update for mobility follows the make- preparation phase is complete, the user executes the
before-break approach: when an imminent handover is physical handover to Wi-Fi and resumes the video
detected, new SFs are allocated on the target segment, stream.
The performance of the proposed mobility 800
ASN Processing Time + Cross Layer
MS Processing Time
architecture is addressed in this section. The internal MS<->ASN Communication
Time (ms)
802.21 entities is also evaluated. 400
300