For updating the local mobility anchor about the current location of the mobile node, the mobile access gateway sends a Proxy Binding Update message to the mobile node’s local mobility a
Trang 1Network based Global Mobility Management Scheme in NGN
Han Gyol Kim, Myong Ju Yu, Jong Min Lee, Yong Hun Yu, Song Gon Choi,
School of Electrical & Computer Engineering, ChungBuk National University
410, Sungbong-ro, Heungdeok-gu, Cheongju-si, ChungBuk, Korea, 361-763*
hgkim@cbnu.ac.kr, mjyu@cbnu.ac.kr, ljm80 @cbnu.ac.kr, yhyoo@cbnu.ac.kr,
sgchoi@cbnu.ac.kr
Abstract
We propose a network-based global mobility
mechanism between the IP based Access Networks
And this mechanism improves the global mobility
problem of the existing MIPv6 Moreover, the
handover latency time can be reduced through the
using Label Switched Path (LSP) of Multi Protocol
Label Switching (MPLS) setup
1 Introduction
In the next generation network environment, the
research for providing the seamless service actively
progresses [1,2] For the seamless service providing,
the inappropriate mobility management technique is
needed Generally, a signal is controlled in Layer 3 in
order to provide mobility In Layer 3, there is
MIP(Mobile Internet Protocol) in the representative
technology providing a mobility [3] A mobility is
provided to the various merit because of in the Layer 3
hierarchical layer However, in order to provide the
mobility in the various point of views, presently it
makes every effort
The fast location registration techniques using the
L2 trigger need to be looked into As to the technology,
the electrical transmission at the Layer 2 layered-based
is made the signaling for the location registration
doesn't rise up to the Layer 3 hierarchical layer [4]
Moreover the location registration delay time is
reduced by separating the control signal transmission
area and data transferring area [4] The fast signal
processing technique at the L2 layered-based is
determined as the good method instead of the signal
processing delay time at the L3 hierarchical layer
Presently in IETF, there is actively the PMIPv6
technology among the normalizing progressing [5]
PMIPv6 minimizes the burden in which the mobile
node is offered mobility And the technology for
providing the mobility is supported in a network Moreover the systems used in the existing MIPv6 or the advantage that it can carry out many message parameter values with reuse are presented [5] However PMIPv6 still has the problem of MIP Because of using MIPv6 in the global handover, the continued network-based providing users with mobile node mobility service does with disable [6]
In the paper, the problem that this kind of the mobility providing technologies has was improved Advantages were operated with and the new procedure was shown In the core network domain, the control message and data transmission were separated The fast location registration was considered In the local area, by applying the PMIPv6 technology, the network-based mobility was possible Moreover by applying the managing system the location information
of the mobile node in the core network, the network-based global mobility of the mobile node was suggested
In chapter 2, we illustrated about a configuration and procedure of the technologies which the configuration of the paper operates with In chapter 3, concretely the network configurations to be proposed and location registration procedure were made with technology In the final conclusion, we described about the objective of research in the future
2 Related Work
2.1 PMIPv6
It is the technology for providing the network-based mobility to the mobile node in the local area done based on increased IP Presently in the IETF NETLMM WG, a normalizing progresses [5]
Figure 2.1.1 shows the network configuration of PMIPv6
If the mobile node has the IPv6 function although it Fourth International Conference on Networked Computing and Advanced Information Management
Trang 2moves to an anywhere within the PMIPv6 Domain, it
can be offered a mobility Moreover the mobile node
determines that it continuously maintains its own home
link which it comprises for the first time although it
moves Because, continuously the
LMA1
LMA2
MN
PMIP domain#1
PMIP domain#2
Core Network
MAG1
MAG2
MAG3
MAG4 MIPv6-Home Agent = LMA#2
CN LMA0
MIPv6-Home Agent = LMA#1
PMIP domain#0
MAG0
Figure 2.1.1 PMIPv6 Network Architecture – Local
Handoff and Global Handoff Scheme
same Home Network Prefix information is due to be
received [5]
MAG provides with the mobility of mobile node
instead of mobile node MAG goes through the
authentication procedure through mobile node and L2
event If mobile node of the PMIPv6 service
certification is completed, the role of place-registering
to LMA is carried out Moreover, a packet can be
transmitted by forming LMA and bi-directional
tunneling [5]
LMA is the topology anchor point for mobile
node’s Home Network Prefix And LMA manages the
binding entry for the location information of mobile
node And LMA assigns Home Network Prefix of
mobile node A LMA searches for its own binding
table and system determines whether the mobile node
is the initial registration process situation or the
handover situation And MAG and both direction type
tunneling are set and it packets with electrical
transmission At this time used LMA Address (LMAA)
And he address used in MAG is a Proxy Care of
Address (pCoA) [5]
Figure 2.1.2 shows the signaling call flow when the
mobile node enters the Proxy Mobile IPv6 Domain
Once a mobile node enters a Proxy Mobile IPv6
domain and attaches to an access link, the mobile
access gateway on that access link, after identifying the
mobile node and acquiring its identity, will determine
if the mobile node is authorized for the network-based
mobility management service [5]
For updating the local mobility anchor about the
current location of the mobile node, the mobile access gateway sends a Proxy Binding Update message to the mobile node’s local mobility anchor Upon accepting
MN Attached
MN Attached Event (Acquire MN-Id and Profile)
Accept PBU (Allocate MN-HNP, Setup BCE and Tunnel) PBU
PBA Accept PBA (Setup Tunnel and Routing)
Rtr Adv
IP Address Configuration
Bi-Dir Tunnel
Figure 2.1.2 mobile node Attachment – signaling
Call Flow this Proxy Binding Update message, the local mobility anchor sends a Proxy Binding Acknowledgement message including the mobile node’s home network prefix It also creates the Binding Cache entry and sets
up its endpoint of the bi-directional tunnel to the mobile access gateway Acknowledgement message sets up its endpoint of the bi-directional tunnel to the local mobility anchor and also sets up the forwarding for the mobile node’s traffic At this point the mobile access gateway will have all the required information for emulating the mobile node’s home link It sends Router Advertisement messages to the mobile node on the access link advertising the mobile node’s home network prefix as the hosted on-link-prefix The mobile node on receiving these Router Advertisement messages of the access link will attempt to configure its interface either using stateful or stateless address configuration modes, based on the modes that are permitted on that access link as indicated in Router Advertisement messages At the end of a successful address configuration procedure, the mobile node will end up with one or more addresses from its home network prefix [5]
Figure 2.1.3 shows the signaling call flow for the mobile node’s handoff from previously attached mobile access gateway (p-MAG) to the newly attached mobile access gateway (n-MAG) This call flow reflects only a specific message ordering, it is possible the registration message from the n-MAG may arrive before the de-registration message from the p-MAG arrives [5]
After obtaining the initial address configuration in the Proxy Mobile IPv6 domain, if the mobile node changes its point of attachment, the mobile access gateway on the previous link will detect the mobile
Trang 3node’s detachment from the link and will signal the
local mobility anchor and will remove the binding and
routing state for that mobile node The local mobility
anchor upon receiving this request will identify the
corresponding mobility session for which the request
was received and once it accepts the request will wait
for certain amount of time for allowing the mobile
access gateway on the new link to update the binding
However, if it does not receive any Proxy Binding
Update message within that given amount of time, it
will delete the binding cache entry [5]
MN Detached
Bi-Dir Tunnel
MN Detached Event
DeReg PBU Accept PBU Start MindelaybeforeBCEDelete Timer PBA
MN Attached MN Attached Event received from MN or from network
Acquire MN-Id and Profile
……….
Registration steps as in Mobile Node Attachment
……….
Rtr Adv
MN retains HoA/HNP
Bi-Dir Tunnel Rtr Sol
Figure 2.1.3 mobile node Handoff –Signaling Call
Flow The mobile access gateway on the new access link
upon detecting the mobile node on its access link will
signal the local mobility anchor for updating the
binding state Once that signaling is complete, the
serving mobile access gateway will send the Router
Advertisements containing the mobile node’s home
network prefix(es) and this will ensure the mobile node
will not detect any change with respect to its layer-3
attachment of its interface [5]
It can be offered the mobility if the IPv6 function is
equipped with within the PMIPv6 Domain In the
position of the mobile node, it determines that it there
is continuously in the home link Its own link is not
reestablished However, PMIPv6 has the still many
problems The problem of going with the existing
MIPv6 is shared And it is considered that it has to be
defined in many part which is not still standardized
2.2 PMIPv6 –MIPv6
In this model, PMIPv6 and MIPv6 are used in a
hierarchical manner where PMIPv6 is used for local
mobility and MIPv6 is used for global mobility [6]
The mobile node-HoA address assigned to the mobile
node in the Proxy Mobile IPv6 domain is used as the
care-of address for Mobile IPv6 registration If the
mobile node moves and attaches to an access network
that is not part of the proxy mobile IPv6 domain, it acquires a care of address from the access network and performs a regular Mobile IPv6 registration with its home agent When the mobile node is outside the Proxy Mobile IPv6 domain, only Mobile IPv6 is used Using the figure 2.1.1 to illustrate the hierarchical use of Mobile IPv6 and Proxy Mobile IPv6, when the mobile node is attached to MAG1, it uses mobile node-HoA as CoA for Mobile IPv6 registration with the home agent If the mobile node moves and attaches to MAG2, it is still attached to the same PMIPv6 domain and its PMIPv6 mobile node-HoA remains the same Since there is no change in care-of address, the mobile node does not need to update its binding at the home agent If the mobile node moves and attached to MAG3, it is no longer in the same PMIPv6 domain The mobile node acquires a new PMIPv6 mobile node-HoA2 from LMA2 Since there is now a change in the care-of address, the mobile node updates its binding with the home agent with mobile node-HoA2 as the care-of address [6]
When the mobile node moves and attaches to a different MAG in the PMIPv6 domain, the mobile node and the Mobile IPv6 home agent are not aware of the movement PMIPv6 takes care of managing the mobility between different MAGs The mobile node's movement is restricted only to the LMA If the mobile node movement results in attaching to a different PMIPv6 domain then the mobile node sees a change in its care-of address and sends a binding update to its home agent [6]
There are other hierarchical scenarios possible using Proxy Mobile IPv6 and Mobile IPv6
2.3 MPLS LSP based in NGN Figure 2.3.1 shows the architecture of the this Scheme
The Mobility Information Control Server (MICS), central address manager, manages MAC address, permanent IP address (IP_PA), and local IP address (IP_LA) of an mobile node as well as Handover Control Agent (HCA)’s IP address, and manages binding information related to communication between the mobile node and the Correspondent Nodes (CNs) The HCA, local address manager, manages MAC address, IP_PA, and IP_LA of an mobile node, and encapsulates packets for data transmission The Access Point(AP) forwards an mobile node’s MAC address to HCA when an mobile node enters into its area The LSPs between HCAs and MICS are used to transmit only MM signaling message [4]
When an mobile node enters into the AP#1 area, the AP#1 catches the mobile node’s MAC address and then sends a Location Report message to the HCA#1
Trang 4The HCA#1 creates a record for the mobile node in its
Local Address management Table, and sends a
Location Registration message to the MICS, sending
an Address Inform message to the mobile node in its
Central Address Management Table The MICS has
MAC address and IP_LA of the mobile node, as well
as the HCA#1’s IP address During the processing of
the MICS, the mobile node sends an Address Inform
ACK message to the HCA#1 in response to the address
Inform message from the HCA#1 When the HCA#1
receives the Address Inform ACK message, it sends an
Address Update message to the MICS [4]
Figure 2.3.1 Architecture for the MPLS LSP based
in NGN
In case of data transmission, when the HCA#3
receives a packet toward the mobile node from the CN,
the refers to the mobile node’s IP-LA in its L-AMT If
it has no mobile node’s IP_LA, it sends a Location
Request message to the MICS The MICS searches the
mobile node’s IP-LA, creates a record of IP_PA
mapping about connection between the mobile node
and the CN, sends a Location Response messages to
the HCA#1 as well as the HCA#3 The HCA#3
encapsulates the packet with the destination address
and the source address, and the packet is tunneled from
the HCA#3 to the mobile node, which removes the
encapsulated packet header [4]
In figure 2.3.2, when an mobile node moves from
the AN#1 to the AN#2, the AP#2 catches the mobile
node’s MCA address and sends a Location Report to
the HCA#2 The HCA#2 creates a record for the
mobile node in its L-AMT, writes the mobile node’s
MCA address and IP_LA, and sends a Location
Registration message to the MICS updates the record
of the mobile node in its C-AMT, and sends a Location
Response message to the HCA#2, while sending other
Location Response message to HCA#3 that keeps the
connection with the mobile node In consequence, the fast handover of the mobile node can be supported by the HCA and the MICS [4]
Figure 2.3.2 fast handover using L2
information
3 Proposal
In the paper, the technology making the fast location information registration of the PMIPv6 technology described in the above and L2 base is operated with and the network-based global mobility management scheme is proposed In the local area, by applying the existing PMIPv6 technology, the network-based local mobility offer is possible And by using the center server Mobility Information Control Server(MICS) in the global handover, the fast location registration through the Multi Protocol Label Switching Label Switching Path(MPLS LSP) is possible
Figure 3.1 is figure showing the architecture of the network to be proposed
MICS HCA1
HCA2
MN
AN#1
AN#2
MPLS Core Network
MAG1
MAG2
MAG3
MAG4
AN#0
HCA0 MAG0
MN
CN
MICS : Mobility Information Control Server HCA : Handover Control Agent MAG : Mobile Access Gateway
CN : Correspondent Node
MN : Mobile Node
MPLS LSP IPv6
MN
Figure 3.1 Proposal Network Architecture Mobile Access Gateway(MAG) carry out the role at the existing PMIPv6 identically
Trang 5Handover Control Server(HCA) perform the fast
location registration through the MPLS LSP and has
the LMA system function at the existing PMIPv6
Moreover, the packet through the bi-directional
tunneling between HCA is transmitted
In MICS, all location information of the mobile
node are managed By notifying changed location
information to HCA the packet transmission is
supported And the network-based providing users
with mobile node mobility service of the mobile node
are possible in the global handover by informing of the
mobile node HNP information
Figure 3.2 shows the Attached registration process
of the mobile node
L2 event
Location report (MN_ID, MAG#1)
Loca tion registra tion Req.
(MN_ID, HCA#1) Loca tion registration Ack.
(New MN_ID)
Loca tion report Ack.
(MN_HNP)
HNP registration (MN_HNP) HNP registra tion Ack
Tunnel setup
Router Advertisement
(MN_HNP)
Allocation MN_HNP
Address
Configuration
HoA#1 MAG#1 HCA#1
Figure 3.2 Proposal Attached Location
Registration
1 As to mobile node entered for the first time
with MAG1 and L2 event come into existence
2 MAG1 gives the location registration request
to HCA1 including the mobile node
information and its own address if the
authentication is completed
3 There is no information of mobile node’s
binding entry in the HCA1’s binding table,
then gives the location registration request to
MICS
4 The information of mobile node confirms
nothing for its own binding table The MICS
informs through the response message to
HCA1 that the process is the initial registration
process
5 The HCA1 allocation the mobile node HNP
And the HCA1 informs this information to
MICS and MAG1
6 The MAG1 includes in its own router
advertisement message and transmits this
information to mobile node
7 mobile node perform its own address
configuration process the MN_HNP The next figure 3.3 shows the location registration procedure of the mobile node in the local handover of mobile node
L2 event
Location report Ack.
(MN_HNP)
Tunnel setup
Router Advertisement (MN_HNP)
Location report (MN_ID, MAG#2)
Figure 3.3 Proposal Local Mobility Procedure
1 As to mobile node penetrated into the MAG2
area, L2 event are generated
2 MAG2 makes the location registration request
to HCA1 including the mobile node information and its own address if the authentication is completed
3 In its own binding table, HCA1 confirm the
entry of mobile node The HCA1 transmits the stored mobile node HNP information to MAG2
4 The MAG2 includes the mobile node HNP
information in its own router advertisement message and transmits to mobile node
5 The mobile node determines that the mobile
node there is continuously in the home link by receiving the same HNP information
Figure 3.4, the mobile node shows the Location registration procedure by the other domain area in the handover
1 As to mobile node approached to the domain
which is new with MAG3 and L2 event are generated
2 MAG3 gives the location registration request
to HCA2 including the mobile node information and its own address if the authentication is completed
3 The information about mobile node confirms
nothing for its own binding table and the
Trang 6HCA2 makes the location registration request
to MICS
4 The information of mobile node confirms to
there be in its own binding table The MICS
transmits the information (MN_HNP) of
mobile node to HCA2 HCA2 stores the new
entry this information in its own binding table
and HCA2 transmits the mobile node HNP
information to MAG3
5 The MAG3 includes the mobile node HNP
information in its own router advertisement
message and transmits to mobile node
6 The mobile node determines that there is
continuously in the home link by receiving the
same HNP information
L2 event
Loca tion registration Req.
(MN_ID, HCA#2) Location registra tion Ack.
(MN_HNP) Loca tion report Ack.
(MN_HNP)
Tunnel setup
Router Advertisement
(MN_HNP)
HoA#1 MAG#3 HCA#2
Loca tion report (MN_ID, MAG#3)
Figure 3.4 Proposal Global Mobility
Procedure Through this process, the network-based global
mobility offer of the mobile node becomes possible
The mobile node determines that the mobile node there
is continuously in its own home link since it is offered
the same HNP information although it handovers
Figure 2.3.5 shows the initial packet transmission
procedure of the technology to be proposed
1 A packet as to the transmission packet, is
transmitted to HCA0 from the CN as the initial
transmission path
2 HCA0 confirm the destination of packet
address and requests the location information
of mobile node to MICS A packet is buffered
in HCA0 while being requested
3 The HCA0 receiving the location information
from the MICS sets a tunneling as HCA1 and
it encapsulates a packet and it transmits
4 The HCA1 sets HCA0 and tunneling through
the information which the HCA1 receives from
MICS And It decapsules the packet which it gets a transmission of and it encapsulates a packet with MAG1 and transmits
5 MAG1 decapsules a packet Finally the MAG
transmits a packet the destination address after
a confirmation to mobile node
MN MAG1 HCA1 MICS
HCA0 MAG0 CN
HCA#0 MAG#0 HoA#0
Location Infor Req.
Location Infor Ack.
Location Infor.
packet
Incapsulation Decapsulation
Incapsulation Decapsulation
Incapsulation Decapsulation
Tunneling
Tunneling Tunneling
Location Infor Res.
Figure 3.5 Proposal Initial Data Transmission Figure 3.6 mobile node shows the packet transmission procedure in the global handover
1 MICS renewing the location information of the
mobile node transmits the location information message to all HCAs communicated with the mobile node
2 The HCA0 setup its own tunneling to HCA2
3 The HCA0 getting a transmission of a packet
encapsulates a packet to the HCA2 established
in advance and transmits
4 HCA2 decapsulates a packet and HCA2
encapsulates a packet to MAG3 and transmits
5 The MAG3 getting a transmission of a packet
decapsulates a packet and transmitted to the mobile node
The technology to be proposed is considered to contribute more than the mechanism which carries out the mobility with offer by using the existing MIPv6 to the signaling delay time reduction and routing optimization Moreover, it is determined in contributing to the unification and miniaturization of the mobile node by providing the network-based global mobility offer
Trang 7MN MAG3 HCA2 MICS HCA0 MAG0 CN
Location Notif.
Location Notif Ack.
Data packet
Incapsulation Decapsulation
Incapsulation Decapsulation
Incapsulation
Decapsulation
Tunneling Tunneling
Tunneling
Global Handover
Figure 3.6 Proposal Packet Transmission
4 Conclusion
This paper proposed the method for providing the
seamless mobility scheme between the PMIPv6
domain The existing MPLS LSP based mobility
technique was used in order to propose this mechanism
The method proposed in this paper is expected to show
the good performance to the Global mobility than
using the existing MIPv6 Moreover, the part which it
was unable to support from MIPv6 is supported we
will analyze the transmission time and processing time
in order to verify the performance of this paper The
analyzed value will submit in the full paper
Acknowledgment
"This research was supported by the MKE(Ministry of
Knowledge Economy), Korea, under the
ITRC(Information Technology Research Center)
support program supervised by the IITA(Institute of
Information Technology Advancement"
(IITA-2008-(C1090-0801-0036))
* Corresponding Author: Seong Gon Choi (sgchoi@cbnu.ac.kr)
5 References
[1] Output Document of Draft Recommendation
Y.MPLS-MOB: “MPLS-based Mobility and QoS capabilities for NGN
Services”, Geneva, 12-22 May 2008
[2] “Draft Recommendation Q.MMF” (version 1.7),
Seoul, Korea, 17-24 January 2008
[3] D.Johnson, C.Perkins, and J.Arkko, RFC 3775, “Mobility
support in IPv6”, June 2004
[4] Myoungju Yu, jongmin LEE, Tai-Won UM, Won RYU,
Byong Sun LEE, “A New Mechanism for Seamless Mobility
Based on MPLS LSP”, IEICE TRANS, Information and
Communication Engineers, Japan, February 2008,
pp.593-596
[5] S Gundavelli, “Proxy Mobilie IPv6
draft-ietf-netlmm-proxymipv6-11.txt”, IETF draft, IETF NETLMM WG,
August 28-2008, pp 1-80 [6]V Devarapalli, “Proxy Mobilie IPv6 and Mobile IPv6 interworking
drafi-devarapalli-netlmm-pmopv6-mipv6-01.txt”, IETF draft, IETF NETLMM WG, 27-Apr-2007.pp
1-10