Académique Documents
Professionnel Documents
Culture Documents
Interworking
1 Introduction
The current technologies vary widely in terms of bandwidths, media access tech-
nologies, security mechanisms, etc. One of promising evolutions is to combine
different existing wireless technologies to offer access to services while on the
move, at any place and any time. A mobile device with multiple wireless network
interfaces can switch the connection among available access points implementing
different technologies.
The Universal Mobile Telecommunication System (UMTS) provides high mo-
bility with wide area coverage and supports low to medium data rates. However,
UMTS data rates are not sufficient to satisfy data-intensive applications and
the service charge is high. A research trend which aims to integrate UMTS and
Wireless Local Area Network (WLAN) to benefit the high data rate and low cost
of WLAN has much attracted research community and standardization bodies
for the last few years. Recently, the Worldwide Interoperability for Microwave
Access (WIMAX), a common name associated to the IEEE 802.16a/REVd/e
wirelessMAN standard [1, 2], which provides specifications for an air interface
for fixed, portable and mobile broadband wireless access networks, has not only
addressed the last mile problem but also supported the nomadic and mobile
clients on the go over the extended coverage area of cellular network. In our
study here, we focus only on the mobile WIMAX operating in the frequency
band of 2.5-3.5 GHz which supports a maximum mobility at about 100km/h.
This research has been partially funded by Eureka Celtic project SeIMoNet.
2 Related work
In WIMAX network, each time the mobile changes its ASN gateway, it will obtain
a new local IP address through the DHCP server. The ASN GW can learn this
new local IP address and also ask to the DHCP server the WIMAX HA’s address
since it plays the role of the DHCP relay agent in the DHCP discovery process.
The ASN GW then informs the serving BS the MS’s new local IP address and
sends the Mobile IP (MIP) registration to the WIMAX HA. A generic IP-in-IP
tunnel such as Generic Routing Encapsulation (GRE)[16, 17] may be used to
transport the IP packets between the WIMAX HA and the FA.
Each time the mobile switches the connection to the UMTS network, it will
initiate the PDP context activation procedure. No IP address is allocated to
the MS at the PDP context activation. The remote address provided by HA
or an external entity in PDN will be kept unchanged and will be informed to
the GGSN via PDP context activation. The remote IP address is a global home
address that is used to address to the external network and the correspondent
node. It may be a static address or a dynamic address acquired from the HA
or another external entity when the mobile first time connects to the network,
4 Handover procedure
To reduce the interruption time during the handover, we have specified a forward
handover procedure. That is to say, before leaving the serving network, the
mobile prepares a new attachment in the target network. In order to reduce the
packet loss during handover, the old FA notifies the HA the MS’s movement so
that the HA can buffer the packets and forward them to the MS as soon as the
HA receives the MIP update from the MS.
1. The UTRAN is responsible for detecting the handover need and initiating
the inter-system measurement process by sending the measurement control
message to the MS. This message contains the neighboring WIMAX cell
information, the compressed mode pattern, etc.
2. While the MS has an on-going communication in FDD mode, in order to
perform the measurement on the neighboring WIMAX cells, it must enter
in the compressed mode. Note that the measurement on WIMAX cell is
performed on the preamble of each WIMAX frame.
3. After the measurement period, the MS sends the measurement report to
the network. The report must contain the parameters indicating the signal
quality level of the neighboring WIMAX BSs.
4. The RNC initiates the handover procedure by notifying the potential target
WIMAX BSs where the mobile may handover. The HO request message
including the MS’s APN, the candidate BS identifiers, the required QoS
of MS’s current applications, etc. will be sent to the GGSN. The GGSN
performs the DNS request to learn the addresses of the PDGs which serve
the MS’s current APN. The GGSN selects one PDG in the result list and
sends it the HO request message. If the GGSN does not receive any response
from the PDG after a certain time, it will send the HO request to another
PDG in the list. The HO request message will then be transmitted to the
potential WIMAX BSs based on the routing information at the PDG. This
step aims to check if the target WIMAX BS can accept the MS handover
with the required QoS.
5. The WIMAX BSs which support the MS handover will return a HO support
to the RNC.
6. The RNC will select the best target WIMAX BS among the supporting BSs
and then sends the HO command to the MS. This message includes all the
required information for setting up the connection to the selected target
WIMAX BS.
7. Right after that the RNC sends the HO confirmation. The mobile is then
disconnected from the UMTS network and starts the connection setup to
the target WIMAX BS.
8. Upon receiving the handover confirmation, GGSN/FA sends a MIP update
message to the HA to notify the MS’s movement. The HA then stops sending
the packets to the MS via this GGSN/FA and buffers the inbound packets
until it receives the MIP update from the target WIMAX network.
9. Based on the information included in the HO request message, the WIMAX
BS can provide a non-contention based initial-ranging opportunity to the
MS by placing a Fast Ranging Information Element in the UL MAP [1, 2].
This information will facilitate the RAN connection setup of the MS. If not,
the MS must perform the normal ranging procedure which takes more time.
References
1. IEEE Std 802.16, ”Part 16: Air Interface for fixed and mobile broadband wireless
access system”, October 2004.
2. IEEE P802.16e/D11, ”Part 16: Air Interface for fixed and mobile broadband wire-
less access system”, Sept. 2005.
3. Salkintzis,A.K.; Fors, C.; Pazhyannur, R.; ”WLAN-GPRS integration for next-
generation mobile data networks”, IEEE Wireless Communication, Vol.9, pp.
112-124, Oct. 2002.
4. Shiao-Li Tsao; Chia-Ching Lin; ”Design and evaluation of UMTS-WLAN inter-
working strategies”, Proceedings. VTC 2002-Fall, IEEE 56th Volume 2, pp.777 -
781, Sept. 2002
5. Hyun-Ho Choi; Song, O.; Dong-Ho Cho; ”A seamless handoff scheme for UMTS-
WLAN interworking”, Globecom, 2004, pp.1559 - 1564, Vol.3. Dec. 2004
6. V. Varma, S. Ramesh, K.D. Wong, M. Barton, G. Hayward and J. Friedhoffer.
”Mobility Management in Integrated UMTS/WLAN Networks”, IEEE ICC, An-
chorage, Alaska, USA, May 2003.
7. Muhammad Jaseemuddin. ”An Architecture for Integrating UMTS and 802.11
WLAN Networks”, 8th IEEE ISCC, p.716, 2003.
8. N. Vulic, S.H. Groot, I. Niemegeers, ”A comparison of Interworking Architectures
for WLAN Integration at UMTS Radio Access Level”, ConWIN05, July 2005.
9. G. Cunningham, P. Perry and L. Murphy, ”Soft, Vertical Handover of Streamed
Multimedia in a 4G network”,5th International Conference on 3G mobile commu-
nications Technologies, London, UK, Oct. 2004.
10. R. Inayat, R. Aibara, and K. Nishimura, ”Handoff Management for Mobile Devices
in Hybrid Wireless Data Networks”, JCN, vol. 7, No. 1, March 2005.
11. 3GPP,”Feasibility Study on 3GPP System to WLAN Interworking”, Tech. rep.
3GPP TR22.934 v6.2.0,September 2003.
12. 3GPP,”3GPP system to Wireless Local Area Network (WLAN) interworking; Sys-
tem description”, TS 23.234 v6.4.0 March 2005.
13. UMA, ”UMA Architecture (stage 2)”, Release 1.0.4, May 2005.
14. UMA, ”UMA Protocols (stage 3)”, Release 1.0.4, May 2005.
15. C. Perkins, Ed. ”IP Mobility Support for IPv4”, IETF RFC 3344, Aug. 2002.
16. D. Farinacci, T. Li, S. Hanks, D. Meyer and P. Traina, Generic Routing Encapsu-
lation (GRE), IETF RFC 2784, March 2000.
17. G. Mommety, ”Key and Sequence Number Extensions to GRE”, IETF RFC 2890,
September 2000.
18. 3GPP, ”Radio Resource Control (RRC)” , TS 25.331 v6.6.0, June 2005.
19. C. Kaufman, ”Internet Key Exchange (IKEv2) Protocol”, RFC 2407, Sept. 2004.
20. P. Eronen, ”IKEv2 Mobility and Multihoming Protocol (MOBIKE)” IETF MO-
BIKE WG, October 2005.
21. D. Johnson, C. Perkins, J. Arkko,”Mobility Support in IPv6”, RFC3775, 2004.