KR100969573B1 - Method of network based vertical fast handover between heterogeneous networks - Google Patents

Abstract

The present invention relates to a network-based heterogeneous high-speed vertical handover method, wherein a home mobile access gateway having a mobile node connected and a Point of Service (PoS) function acquires information about a neighbor network from a media independent information server. Steps; A threshold setting step of setting, by the home mobile access gateway, two thresholds relating to link quality to the mobile node; The mobile node determines the PoS as a handover candidate by checking a resource of a PoS corresponding to a handoverable network when the current measured link quality is equal to or less than a first threshold value; Wow; A resource reservation step of the mobile node reserving a corresponding resource with the determined candidate PoS when the current measured link quality is less than or equal to a second threshold value; When the home mobile access gateway requests a handover to the mobile node, the home mobile access gateway sends a Fast Proxy Binding Update (PBU) message including the ID of the mobile node and a Fast Proxy Binding Acknowledgment (PBA) message in response. Exchanging with a home local mobility anchor and buffering all data destined for the mobile node by the home local mobility anchor; And a resource release step of requesting resource release to the home mobile access gateway by recognizing that the mobile node is connected to the candidate PoS and the candidate PoS is connected to the mobile node. According to the above configuration, the present invention enables handover through a PHY / MAC stack suitable for interface hardware already provided in the mobile terminal. Thus, if the mobile terminal has a stack that conforms to the IEEE 802.21 protocol, IP sessions can be correctly maintained during vertical high-speed handovers without requiring any network stack additions and changes, and also reduce handover latency and packet loss while reducing the load on network devices and improving handover performance. It has an effect.

Vertical, Fast Handover, Network-Based, Heterogeneous Network

Description

Method of network based vertical fast handover between heterogeneous networks}

The present invention relates to a network-based heterogeneous vertical fast handover method, and in particular, using the IEEE 802.21 protocol, which is a vertical handover method of heterogeneous network, and the IETF Proxy Mobile IPv6 (PMIPv6) protocol, which is a network-based handover method. A method for vertical fast handover between network-based heterogeneous networks that can reduce network load and improve vertical fast handover performance without creating new dynamic tunneling without requiring any stack addition and change for IP handover in mobile terminal. will be.

In general, vertical handover between heterogeneous networks has used IETF Mobile IPv4 or Mobile IPv6 protocol to maintain IP sessions.

The Mobile IPv4 / v6 protocol is a host-based handover scheme that requires a lot of modifications to the mobile terminal and can cause excessive load on the radio section by IP signaling.

In order to solve this problem, the IETF International Standardization Organization has recently standardized a network-based IP session maintenance and handover scheme called PMIPv6 protocol. The PMIPv6 protocol does not require any modification to the mobile terminal and is favored by many mobile operators because of the advantage of greatly reducing the load required for the wireless section.

The IEEE 802.21 protocol proposes a technology for providing an event service, a command service, and an information service required for vertical handover of heterogeneous mobile terminals.

When the IEEE 802.21 standard is completed, the IEEE 802.21 technology must be used for the vertical handover request procedure to prepare an efficient handover procedure based on the standard.

Meanwhile, efforts to process PMIPv6 at high speed using the Fast Handover for Mobile IPv6 (FMIPv6, RFC 4068) protocol established by the IETF have recently been made at the IETF. An example is the Fast Handover for PMIPv6 (FPMIPv6) protocol, described in draft-yokota-mipshop-pfmipv6-01.txt in the IETF document.

However, the conventional fast handover method, i.e., the conventional FMIPv6 protocol and the FPMIPv6 protocol, can be implemented through dynamic tunneling between a router and a router or between a mobile access gateway (MAG) and a mobile access gateway defined in the PMIPv6 protocol. Since high-speed handover processing is performed, there is a problem that it puts a lot of load on the network equipment and degrades the overall performance of the handover.

The present invention has been proposed to solve the above problems, using a new network based on the IEEE 802.21 protocol and PMIPv6 protocol, without the need to create a new dynamic tunneling while maximizing the existing tunnel for various mobile scenarios of the mobile node It is an object of the present invention to provide a vertical fast handover method between networks based on heterogeneous networks that can efficiently implement the vertical fast handover procedure.

According to an aspect of the present invention, there is provided an information acquisition step of acquiring a neighbor network information from a media independent information server by a home mobile access gateway to which a mobile node is connected and to which a point of service (PoS) function is added; A threshold setting step of setting, by the home mobile access gateway, two thresholds relating to link quality to the mobile node; The mobile node determines the PoS as a handover candidate by checking a resource of a PoS corresponding to a handoverable network when the current measured link quality is equal to or less than a first threshold value; Wow; A resource reservation step of the mobile node reserving a corresponding resource with the determined candidate PoS when the current measured link quality is less than or equal to a second threshold value; When the home mobile access gateway requests a handover to the mobile node, the home mobile access gateway sends a Fast Proxy Binding Update (PBU) message including the ID of the mobile node and a Fast Proxy Binding Acknowledgment (PBA) message in response. Exchanging with a home local mobility anchor and buffering all data destined for the mobile node by the home local mobility anchor; And a resource release step of requesting resource release to the home mobile access gateway by recognizing that the mobile node is connected to the candidate PoS and the candidate PoS is connected to the mobile node.

Advantageously, the candidate determining step includes: a first notifying step of the mobile node notifying the home mobile access gateway that the measured link quality is less than or equal to the first threshold value; When the home mobile access gateway notifies the mobile node of the handoverable network information, the mobile node selects a network that satisfies a current requirement and notifies the home mobile access gateway; And waiting for the mobile node to turn on an interface accessible to the selected network.

Preferably, the resource reservation step includes a second notification step of the mobile node notifying the home mobile access gateway that the measured link quality is less than or equal to the second threshold value; When a resource is reserved to a candidate PoS, the mobile node may be notified to move.

Preferably, the first buffering step may notify the determined candidate PoS when the home mobile access gateway requests a handover to the mobile node.

Preferably, the first buffering step may notify the home local mobility anchor that the mobile node moves to the candidate PoS when the Home Mobile Access Gateway transmits the Fast PBU message.

Preferably, the handoverable network is an access network managed by the same core network as the network to which the mobile node is connected, and the determined candidate PoS may be a visited mobile access gateway to which a PoS function is added.

Preferably, the Fast PBU message may further include information of the visited mobile access gateway.

Advantageously, the first buffering step comprises: sending a Reverse PBU message to the visited mobile access gateway requesting a binding process when the home local mobility anchor receives the Fast PBU message; And a tunneling step in which the visited mobile access gateway sends a Reverse PBA message as a response to the home local mobility anchor to perform tunneling between the visited mobile access gateway and the home local mobility anchor.

Preferably, the Reverse PBU message may include an ID of the mobile node and a home network prefix.

Preferably a second buffering step, if the home local mobility anchor sends the buffered data to the visited mobile access gateway, the visited mobile access gateway buffers the transmitted data; And transmitting, by the visited mobile access gateway, the buffered data and a router advertisement message (RA) message to the mobile node after the connection recognition of the mobile node in the second buffering step.

Preferably, when the visited mobile access gateway requests authentication to a policy server after access of the mobile node, the policy server responds to the visited mobile access gateway with a related profile including address information of a local mobility anchor; It may further include.

Preferably, the handoverable network is an access network managed by a core network different from the network to which the mobile node is connected, and the determined candidate PoS may be a visited mobile access gateway to which a PoS function is added.

Preferably, the Fast PBU message may further include information of the visited local mobility anchor and the visited mobile access gateway.

Preferably, in the first buffering step, if the home local mobility anchor receives the Fast PBU message, and then transmits a Reverse Remote PBU message requesting a binding process to the visit local mobility anchor, the visit local mobility anchor is configured to receive the Fast PBU message. Sending a Reverse PBU message requesting binding processing to the visiting mobile access gateway; A first tunneling step wherein the visited mobile access gateway sends a Reverse PBA message as a response to the visited local mobility anchor so that tunneling between the visited mobile access gateway and the visited local mobility anchor is performed; And a second tunneling step, wherein the visited local mobility anchor sends a Reverse remote PBA message to the home local mobility anchor to perform tunneling between the visited local mobility anchor and the home local mobility anchor.

Preferably, the Reverse Remote PBU message may include an ID of the mobile node, a home network prefix, and information of a visited mobile access gateway, and the Reverse PBU message may include an ID and a home network prefix of the mobile node.

Preferably a second buffering step, if the home local mobility anchor sends the buffered data to the visited mobile access gateway, the visited mobile access gateway buffers the transmitted data; And transmitting, by the visited mobile access gateway, data and an RA message buffered in the second buffering step to the mobile node after recognizing the connection of the mobile node.

Preferably, when the visited mobile access gateway requests authentication to a visited policy server after access of the mobile node, the visited policy server requests an authentication to a home policy server; A first response step for the home policy server to respond to the visited policy server an associated profile containing address information of a home local mobility anchor; And a second response step, wherein the visit policy server responds to the visited mobile access gateway an associated profile including the address information of the visited local mobility anchor with the address information of the home local mobility anchor.

Preferably, the handoverable network is an access network managed by a core network different from the network to which the mobile node is connected, and the determined candidate PoS is a serving gateway having a mobility management entity (MME) function with PoS capability. Can be.

Preferably, the Fast PBU message may further include information of the visited local mobility anchor.

Preferably, the first buffering step includes: a message transmitting step of transmitting, by the home local mobility anchor, a Reverse Remote PBU message requesting a binding process to the visited local mobility anchor after receiving the Fast PBU message; And a tunneling step in which the visited local mobility anchor transmits a reverse remote PBA message to the home local mobility anchor as a response to perform tunneling between the visited local mobility anchor and the home local mobility anchor.

Advantageously, the Reverse Remote PBU message may include an ID and a home network prefix of the mobile node.

Preferably a second buffering step wherein the visited local mobility anchor buffers the transmitted data if the home local mobility anchor sends the buffered data to the visited local mobility anchor; A mobile notification step of the serving gateway notifying the visited local mobility anchor that the mobile node has moved after recognizing the connection of the mobile node; Transmitting, by the visiting local mobility anchor, the buffered data and the RA message in the second buffering step to the serving gateway, and the serving gateway transmitting the transmitted data and the RA message to the mobile node; It may include.

Preferably, when the serving gateway requests authentication to the visited policy server after access of the mobile node, the visited policy server requests an authentication to a home policy server; A first response step for the home policy server to respond to the visited policy server an associated profile containing address information of a home local mobility anchor; And a second response step, wherein the visit policy server responds to the serving gateway a related profile including the address information of the visit local mobility anchor together with the address information of the home local mobility anchor.

The network-based heterogeneous vertical fast handover method according to the present invention utilizes the IEEE 802.21 protocol, which is a vertical handover method of a heterogeneous network, to provide a new network-based fast handover procedure for various mobile scenarios of a mobile node. Handover is possible through a PHY / MAC stack suitable for the interface hardware already in the terminal, so if the mobile terminal has a stack that conforms to the IEEE 802.21 protocol, there is no need to add or change any network stack for IP mobility. This can effectively maintain IP sessions during handover.

In addition, the present invention transmits a data packet through tunneling between a local mobility anchor and a mobile access gateway or two local mobility anchors already established by the PMIPv6 protocol, thereby reducing the load of network equipments and improving handover performance while simultaneously handover delay. There is an effect that can reduce latency and packet loss.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a schematic structural diagram of a system for vertical fast handover between heterogeneous networks based on a network according to the present invention.

As shown in FIG. 1, in a system for vertical fast handover between heterogeneous networks based on an IEEE 802.21 protocol, a MIH Media Independent Point of Service (MIS PoS) which is a node that performs a service defined in the IEEE 802.21 protocol. Is added to the Mobile Access Gateway (MAG) defined in the PMIPv6 protocol and the Mobility Management Entity (MME) defined in the 3GPP LTE / SAE protocol.

Here, the mobile access gateway (MAG) and the mobility management entity (MME) are nodes that are mainly responsible for mobility management in each access network, and the mobile access gateway (MAG) is an access router located in the PMIPv6 domain. The function is added to the Access Router, and the mobility management entity (MME) performs mobility management of the mobile node.

Meanwhile, the MIH PoS also exchanges information with a Point of Attachment (PoA), which is a lower layer 1/2 connection point of a mobile terminal (MN), and includes a media independent information server (MIIS) and a local mobility anchor (LMA); It is also configured to exchange information with high-level nodes such as Local Mobility Anchor.

Here, the Media Independent Information Server (MIIS) is a server that manages various network information about heterogeneous networks serviced to users, and the Local Mobility Anchor (LMA) is a function defined in the IETF PMIPv6 protocol and all mobiles that reside in the PMIPv6 domain. Supports routing and mobility services for the terminal.

The above configuration depends on how operators configure heterogeneous networks, that is, when one or more access networks are managed in one same core network and when different core networks manage one or more access networks. It may be configured in consideration of. Here, the access network considers LTE / SAE of 3GPP and WiBro network, which has recently become a lot of issues.

FIG. 2 is a schematic diagram of a case where the system of FIG. 1 is managed on one core network.

As shown in Fig. 2, when the operator configures one core network, it manages all mobile node subscribers in one core network, and the old system and the new LTE of different access networks, for example, the WiBro network or 3GPP. / SAE keeps the system together.

In this configuration, the local mobility anchor (LMA) for operating PMIPv6 is basically configured as one. Of course, multiple local mobility anchors (LMAs) can be managed for load balancing and fault tolerance. In addition, the local mobility anchor (LMA) is tunneled to the mobile access gateway (MAG) connected to the mobile terminal unconditionally any packet transmitted by any node outside the domain to the mobile terminal that resides in the domain.

The Mobile Access Gateway (MAG) is added to an Access Control Router (ACR) or the like of a WiBro network that performs the function of an Access Router that is directly related to layer 3 general routing and IP address assignment. In addition, when a mobile node enters a domain and connects to an access router, the mobile access gateway (MAG) supports mobility by exchanging mobility-related signaling with a local mobility anchor (LMA) on behalf of the mobile node.

A Policy Server (PS) is a function defined in the IETF PMIPv6 protocol and stores a variety of information related to a mobile node. In particular, a Policy Server (PS) stores a local mobility anchor (LMA) address for providing mobility services to a mobile node. It is managed and added to AAA (Authentication, Authorization, Accounting) server.

The AAA server is a server that provides authentication, authorization, and fee calculation functions for network resource access processing and service provision of mobile nodes, and is generally located in a core network managed by an operator.

Meanwhile, in the 3GPP LTE / SAE network, since the Packet Data Network Gateway (P-GW) functions as an access router of the entire network, the Mobile Access Gateway (MAG) function serves as a serving gateway (S-GW; Serving). Local mobility anchor (LMA) added to the packet data network gateway (P-GW) itself, or local mobility anchor (LMA) in the operator network outside the packet data network gateway (P-GW) It is configured to.

A packet data network gateway (P-GW) is a gateway located between the operator's core network and the external Internet network and acts as a gateway between them, and typically performs a layer 3 access router function and delivers RA messages to mobile nodes. .

The serving gateway (S-GW) is located between the core network and the access network to perform various management of mobile nodes.

The mobility management entity (MME) cooperates with the serving gateway (S-GW) and the evolved nodeB (eNodeB) to perform mobility management of the mobile node.

NodeB is a node that performs the same function as the base station in the 3GPP network, eNodeB is a node that performs a function similar to the previous base station as a function defined in the 3GPP LTE / SAE protocol and performs an improved function.

Radio Network Controller (RNC) is a node that mainly manages the overall resources of a wireless network, and a Serving GPRS Support Node (SGSN) delivers data packets with mobile nodes in a service area. This node is responsible for packet routing and transmission, mobility management, logical link management, authentication, and charging.

In the WiBro network, a radio access system (RAS) plays a role as a base station in a WiBro service area, and an access control router (ACR) manages a radio access system (RAS) and a mobile terminal. Typically responsible for the function of an access router.

FIG. 3 is a schematic diagram of a case where the system of FIG. 1 is managed on different core networks.

As shown in FIG. 3, when two operators configure different core networks, one or more access networks are maintained in each core network.

In this configuration, each core network operates independently with PMIPv6, and local mobility anchors (LMAs) are configured independently.

Hereinafter, a method for vertical fast handover between heterogeneous networks based on the present invention will be described with reference to FIGS. 4 to 7.

4 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on a network according to the present invention.

The method is a basic procedure to efficiently support the PMIPv6 protocol from the list of various event services, command services, and information services defined in the IEEE 802.21 protocol.

First, the home mobile access gateway (MAGh) to which the mobile node (MN) is connected obtains peripheral network information from the media independent information server (MIIS) (steps S1 and S1 ').

That is, when the mobile node MN is connected to any network, the home mobile access gateway MAGh existing in the network requests the neighbor network information to the media independent information server MIIS (step S1), and the media independent information. The server MIIS sends the corresponding information to the home mobile access gateway MAGh as a response (step S1 ').

Here, the home mobile access gateway (MAGh) has a PoS function added, and the candidate PoS may be a visited mobile access gateway (MAGv) or a serving gateway (S-GW) as described below according to the configuration of the system. In FIG. 4, the mobile access gateway (MAG) to which the mobile node (MN) is connected is shown as a home mobile access gateway (MAGh) separately from the visited mobile access gateway (MAGv).

Next, the home mobile access gateway (MAGh) sets a threshold value on the link quality (Link Quality) to the mobile node (MN) (step S2).

Here, the threshold setting proceeds immediately after the mobile node MN is connected to an arbitrary network, and the threshold is set to two different thresholds Th1 and Th2. Thereafter, the mobile node MN moves and measures the current link quality.

If the mobile node MN has a current measured link quality less than or equal to the first threshold Th1, the mobile node MN indicates that the measured link quality is less than or equal to the first threshold Th. Home Mobile Access Gateway MAGh (Link_Going_Down Report I) is informed (step S3).

At this time, when the home mobile access gateway (MAGh) (Resource Check) of the network information that can be handed over to the mobile node (MN) (step S4), the mobile node (MN) selects a network that satisfies the current requirements Notify the home mobile access gateway (MAGh) (step S4 ').

Next, the mobile node MN waits for the mobile connection by turning on an interface that can be connected to the selected network (Power On) (step S5).

At this time, the home mobile access gateway (MAGh) checks the resource of the PoS corresponding to the handable network (Resource Availability Check) (steps S6 and S6 '). That is, the home mobile access gateway (MAGh) checks the resources for the handoverable candidate networks.

The home mobile access gateway (MAGh) determines that the PoS is a handover candidate when resource checking is completed on the candidate networks (step S7). Here, the home mobile access gateway (MAGh) determines the handover candidate PoS in consideration of the network selected by the mobile node (MN) in step S4 '.

Next, when the mobile node MN continuously moves and measures the current link quality, and the current measured link quality is less than or equal to the second threshold Th2, the mobile node MN determines that the measured link quality is the second threshold. The home Mobile Access Gateway (MAGh) is notified (Link_Going_Down Report II) that it is equal to or smaller than the value Th2 (step S8).

Subsequently, the Home Mobile Access Gateway (MAGh) reserves the resource with the determined candidate PoS (Resource Reservation) (step S9). At this time, the home mobile access gateway (MAGh) informs the mobile node (MN) to move to the candidate PoS.

Next, the home mobile access gateway MAGh requests a handover to the mobile node MN (Step S10). At this time, the home mobile access gateway (MAGh) informs the mobile node (MN) of the candidate PoS determined in step S7.

The home mobile access gateway (MAGh) then sends a Fast PBU message containing the ID of the mobile node (MN) to the home local mobility anchor (LMAh) (step S11).

Herein, the Fast PBU message is a newly defined message utilizing the message defined in the IEEE 802.21 protocol and the message defined in the PMIPv6 protocol, and the home mobile access gateway (MAGh) homes that the mobile node (MN) moves to the candidate PoS. This message is notified to the local mobility anchor (LMAh).

At this time, the Home Local Mobility Anchor (LMAh) receiving the Fast PBU message initiates buffering of all data destined for the Mobile Node (MN) and is currently processing the binding cache data structure defined in the PMIPv6 protocol. The home network prefix is bound to the ID of the mobile node MN.

The home local mobility anchor (LMAh) sends a Fast PBA message to the home mobile access gateway (MAGh) in response (step S12).

Here, the Fast PBA message is a newly defined message, which is a message transmitted by the Home Local Mobility Anchor (LMAh) to the Home Mobile Access Gateway (MAGh) after the Fast PBU message is received and the binding processing is completed.

At this time, the home local mobility anchor LMAh ends buffering for data destined for the mobile node MN and transmits the buffered data to the candidate PoS as described below.

Next, the mobile node MN performs a handover according to a request of the home mobile access gateway MAGh (Link-specific Handover) and is connected to the candidate PoS (step S13).

Subsequently, when the mobile node MN is handed over to a new network and connected, the candidate PoS recognizes the connection of the mobile node MN (step S14).

Next, the candidate PoS requests resource release to the home mobile access gateway (MAGh) (step S15). That is, the candidate PoS requests the home mobile access gateway (MAGh) to release resources associated with the handed over mobile node (MN).

In this manner, network-based vertical fast handover using the IEEE 802.21 protocol can be performed without modification of the mobile node (MN).

On the other hand, such a network-based vertical fast handover method can be applied in consideration of the following three mobile scenarios related to the configuration of the network.

The first is when a mobile node (MN) moves to an access network that supports a mobile access gateway (MAG) within the same core network, and the second is a mobile access gateway (MAG) between core networks with different mobile nodes (MN). Is a case of moving to a supported access network, and a third case is that a mobile node (MN) moves to an access network in which a mobile access gateway (MAG) is not supported between different core networks.

Hereinafter, a network-based vertical fast handover method for each mobile scenario will be described.

5 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on a network according to a first embodiment of the present invention.

A first embodiment of the present invention is a vertical fast handover method when a mobile node (MN) moves to an access network supported by a mobile access gateway (MAG) within a same core network. The network is an access network managed by the same core network as the network to which the mobile node MN is connected, and the determined candidate PoS is a visiting mobile access gateway (MAGv) to which the PoS function is added.

In a first embodiment of the present invention, an information acquisition step of acquiring a neighbor network information from a media independent information server (MIIS) by a home mobile access gateway (MAGh) to which a mobile node (MN) is connected and a PoS function is added (step S101, S101 '); A threshold setting step (step S102) in which the home mobile access gateway MAGh sets two thresholds relating to link quality to the mobile node MN; If the mobile node MN has a current measured link quality of less than or equal to the first threshold, the home mobile access gateway MAGh checks the resources of the visited mobile access gateway MAGv corresponding to the network to which the handover is possible and then visits the corresponding mobile site. A candidate determination step (steps S103 to 107) of determining the access gateway MAGv as a handover candidate; Resource reservation step (steps S108 to S109) in which the mobile node (MN) reserves the corresponding resource to the visited mobile access gateway (MAGv) where the home mobile access gateway (MAGh) is determined if the current measured link quality is less than or equal to the second threshold. )Wow; The home mobile access gateway (MAGh) requesting a handover to the mobile node (MN) (step S110); this is the same method as step S1 to step S10 in FIG.

As described above, when the home mobile access gateway (MAGh) requests a handover to the mobile node (MN), as shown in step S11 of FIG. 4, the home mobile access gateway (MAGh) is a mobile node visited by the mobile node (MN). A Fast PBU message is sent to the home local mobility anchor LMAh, which notifies that it moves to MAGv (step S111).

Here, the Fast PBU message includes the ID of the mobile node (MN) and the information of the visited mobile access gateway (MAGv).

When the Home Local Mobility Anchor (LMAh) receives a Fast PBU message, it initiates the buffering of all data destined for the mobile node (MN) and simultaneously sends a Reverse PBU message requesting binding processing to the visited mobile access gateway included in the Fast PBU message ( MAGv) (step S112).

Here, the Reverse PBU message is a newly defined message and is a message for requesting binding processing to the Visited Mobile Access Gateway (MAGv) included in the Fast PBU message, and includes an ID of the mobile node (MN) and a home network prefix.

On the other hand, the PBU message defined in the PMIPv6 protocol requests binding processing from the Landing Mobile Access Gateway (MAGv) to the Home Local Mobility Anchor (LMAh), whereas the Reverse PBU message is in contrast to the Landing Mobile Access Gateway at the Home Local Mobility Anchor (LMAh). Because we ask with (MAGv), we use "Reverse" to separate the messages.

At this time, the Home Local Mobility Anchor (LMAh) sends a Reverse PBU message and at the same time the MNv of the visiting mobile access gateway (MAGv) for the ID of the mobile node (MN) to be processed in its binding cache data structure defined in the PMIPv6 protocol. Bind the address.

Next, the visiting mobile access gateway (MAGv) sends a Reverse PBA message to the home local mobility anchor (LMAh) in response to the Reverse PBU message (step S113).

Here, the Reverse PBA message is a newly defined message, which is transmitted by the Visited Mobile Access Gateway (MAGv) to the Home Local Mobility Anchor (LMAh) after the Reverse PBU message is received and the binding processing is completed.

At this time, the visiting mobile access gateway (MAGv) has a Home Local Mobility Anchor (LMAh) for the ID of the mobile node (MN) to be processed in its binding cache data structure defined in the PMIPv6 protocol before sending the Reverse PBA message. Bind the address of.

As such, when the Home Local Mobility Anchor (LMAh) receives a Reverse PBA message, bidirectional tunneling is formed between the Home Local Mobility Anchor (LMAh) and the Landing Mobile Access Gateway (MAGv). Set.

As in step S12 of FIG. 4, the home local mobility anchor (LMAh) sends a Fast PBA message to the home mobile access gateway (MAGh) as a response to the Fast PBU message (step S114).

At this time, when the home local mobility anchor LMAh ends buffering of data destined for the mobile node MN and transmits it to the visited mobile access gateway MAGv through the established tunnel, the visited mobile access gateway MAGv is transmitted. Start buffering data.

Next, the mobile node MN is handed over at the request of the home mobile access gateway MAGh and connected to the visited mobile access gateway MAGv (step S115).

Subsequently, when the visiting mobile access gateway (MAGv) requests authentication to the policy server (AAA Query) (step S116), the policy server PS generates a related profile including address information of the local mobility anchor (LMA). Reply with a visited mobile access gateway (MAGv) (step S116 '). Here, the authentication request and response includes the ID of the mobile node (MN), and the profile is a profile required by the PMIPv6 protocol.

When the AAA authentication is completed, the visiting mobile access gateway (MAGv) recognizes that the mobile node (MN) is handed over to the access network managed by the visited mobile access gateway (step S117).

At this time, the visiting mobile access gateway MAGv ends buffering of data destined for the mobile node MN, and transmits the buffered data and the RA message to the mobile node MN (step S118).

As such, when the handover of the mobile node MN is normally completed, the visited mobile access gateway MAGv requests the resource release from the home mobile access gateway MAGh to release resources for the moved mobile node MN ( Step S119).

In this way, even if the mobile node (MN) moves from the same core network to the access network supported by the mobile access gateway (MAG), the new dynamic tunneling can be utilized while maximizing the existing tunnel without modification of the mobile node (MN). Network-based vertical fast handover can be performed without generation.

6 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on a network according to a second embodiment of the present invention.

A second embodiment of the present invention is a vertical fast handover method when a mobile node (MN) moves between different core networks to an access network supported by a mobile access gateway (MAG). A possible network is an access network managed by a core network different from the network to which the mobile node (MN) is connected, and the determined candidate PoS is a visiting mobile access gateway (MAGv) with PoS function.

According to the second embodiment of the present invention, the process until the home mobile access gateway (MAGh) requests a handover to the visiting mobile access gateway (MAGv) existing in the access network newly moved to the mobile node (MN) is carried out in the first embodiment. Since it is the same as the example, the description is omitted here.

If the home mobile access gateway (MAGh) requests a handover to the mobile node (MN) as described above, as in step S111 of the first embodiment, the home mobile access gateway (MAGh) is a mobile node (MN) visited mobile access A Fast PBU message notifying the movement to the gateway MAGv is transmitted to the home local mobility anchor LMAh (step S211).

Here, the Fast PBU message includes the ID of the mobile node (MN) and information of the visited mobile access gateway (MAGv) and the visited local mobility anchor (LMAv).

When the Home Local Mobility Anchor (LMAh) receives a Fast PBU message, it initiates the buffering of all data destined for the Mobile Node (MN) and at the same time the Local Remote Mobility Anchor included in the Fast PBU message with a Reverse Remote PBU message requesting binding processing. Transmit to LMAv (step S212).

Here, the Reverse Remote PBU message is a newly defined message. When the mobile node (MN) moves to a different core network, the home local mobility anchor (LMAh) existing in the old core network is present in the newly moved core network. The message is transmitted to the local mobility anchor (LMAv), and includes the ID of the mobile node (MN), the home network prefix, and the information of the visited mobile access gateway (MAGv).

At this time, the Home Local Mobility Anchor (LMAh) transmits a Reverse Remote PBU message and simultaneously moves the Home Network Prefix and the New Move to the ID of the Mobile Node (MN) to be processed in its binding cache data structure defined in the PMIPv6 protocol. Bind the address of a visited local mobility anchor (LMAv) that exists in the core network.

Next, when the visited local mobility anchor LMAv receives the Reverse Remote PBU message, as in step S112 of the first embodiment, a Reverse PBU message requesting binding processing is sent to the visited mobile access gateway (MAGv) (step S112). S213).

Here, the Reverse PBU message includes a mobile node (MN) and a home network prefix.

The visited mobile access gateway (MAGv) sends a Reverse PBA message to the visited local mobility anchor (LMAv) as a response to the Reverse PBU message, as in step S113 of the first embodiment (step S214), and the visited mobile access gateway (MAGv). And bidirectional tunneling is formed between the LMAv and the visited local mobility anchor (LMAv).

When the visited local mobility anchor LMAv receives the Reverse PBA message, it sends a Reverse remote PBA message to the home local mobility anchor LMAh (step S215).

Here, the reverse remote PBA message is a newly defined message, when a visited local mobility anchor (LMAv) existing in the newly migrated core network receives a reverse remote PBU message from a home local mobility anchor (LMAh) existing in the old core network. A message sent as a response message.

In this case, the visited local mobility anchor (LMAv) is assigned the home network prefix and home local for the ID of the mobile node (MN) that it currently wants to process in its binding cache data structure defined in the PMIPv6 protocol before sending the Reverse Remote PBA message. Bind the address of the mobility anchor (LMAh).

As such, when the Home Local Mobility Anchor (LMAh) receives a Reverse Remote PBA message, tunneling is formed between the Visit Local Mobility Anchor (LMAv) and the Home Local Mobility Anchor (LMAh). Set it.

As in step S114 of the first embodiment, the home local mobility anchor (LMAh) sends a Fast PBA message to the home mobile access gateway (MAGh) in response to the Fast PBU message (step S216).

At this time, when the home local mobility anchor LMAh ends buffering of data destined for the mobile node MN and transmits it to the visited mobile access gateway MAGv through the established tunnel, the visited mobile access gateway MAGv is transmitted. Start buffering data.

Next, the mobile node MN is handed over at the request of the home mobile access gateway MAGh and connected to the visited mobile access gateway MAGv (step S217).

Subsequently, after the mobile node MN is handed over and connected to the visited mobile access gateway MAGv, the visited mobile access gateway MAGv requests authentication from the visited policy server PSv (step S218).

In this case, the mobile node (MN) needs to obtain the result of AAA authentication to the previous network in order to perform AAA authentication to the currently connected network. For this, the visiting policy server PSv authenticates with the home policy server PSh. Is requested (step S219).

The home policy server PSh responds to the visited policy server PSv with the relevant profile containing the address information of the home local mobility anchor LMAh (step S220), and then the visited policy server PSv receives the home local mobility anchor ( The associated profile including the address information of the visited local mobility anchor (LMAv) together with the address information of LMAh) is responded to the visited mobile access gateway (MAGv) (step S221).

Here, the authentication request and response includes an ID of a mobile node (MN), and the profile is a profile required by the PMIPv6 protocol, and is transferred to a visited local mobility anchor (LMAv) of a network to which the mobile node (MN) is currently connected. Home local mobility anchor (LMAh) of the network.

When the AAA authentication is completed, the visited mobile access gateway (MAGv) recognizes that the mobile node (MN) is handed over to the access network managed by the visited mobile access gateway (MAGv).

At this time, the visited mobile access gateway MAGv ends buffering of data destined for the mobile node MN, and transmits the buffered data and the RA message to the mobile node MN (step S223).

As such, when the handover of the mobile node MN is normally completed, the visited mobile access gateway MAGv requests the resource release from the home mobile access gateway MAGh to release resources for the moved mobile node MN ( Step S224).

In this way, even if the mobile node (MN) moves between different core networks to the mobile access gateway (MAG) supported access network, the new dynamic while utilizing the existing tunnel without modification of the mobile node (MN) Network-based vertical fast handover that does not require the creation of tunneling can be performed.

7 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on a network according to a third embodiment of the present invention.

The third embodiment of the present invention is a vertical fast handover method when a mobile node (MN) moves between different core networks to an access network not supported by a mobile access gateway (MAG). The over-available network is an access network managed by a core network different from the network to which the mobile node (MN) is connected, and the serving gateway (S-GW) in which the determined candidate PoS has a mobility management entity (MME) function with PoS capability added thereto. If

The third embodiment of the present invention is an access network in which a home mobile access gateway (MAGh) is newly moved to a mobile node (MN), except that the visited mobile access gateway (MAGv) is configured as a serving gateway (S-GW). Since the process of requesting handover to the serving gateway (S-GW) and authentication process performed after the mobile node (MN) is connected to the serving gateway (S-GW) are the same as in the second embodiment, The description is omitted.

When the home mobile access gateway (MAGh) requests a handover to the mobile node (MN) as described above, as in step S211 of the second embodiment, the home mobile access gateway (MAGh) is served by the mobile node (MN). A Fast PBU message notifying the movement of the gateway S-GW is transmitted to the home local mobility anchor LMAh (step S311).

Here, the Fast PBU message includes the ID of the mobile node MN and the information of the visited local mobility anchor LMAv.

After the Home Local Mobility Anchor LMAh receives the Fast PBU message, as shown in step S212 of the second embodiment, a Reverse Remote PBU message which starts the buffering of all data destined for the mobile node MN and requests binding processing. Is transmitted to the visited local mobility anchor (LMAv) included in the Fast PBU message (step S312).

Here, the Reverse Remote PBU message includes the ID of the mobile node MN and the home network prefix.

Next, the visited local mobility anchor LMAv sends a Reverse remote PBA message to the home local mobility anchor LMAh (step S313) as a response to the Reverse Remote PBU message, as in step S215 of the second embodiment. Bidirectional tunneling is formed between the mobility anchor LMAv and the home local mobility anchor LMAh, and bidirectional tunneling is established if no tunnel is established.

As in step S216 of the second embodiment, the home local mobility anchor (LMAh) sends a Fast PBA message to the home mobile access gateway (MAGh) as a response to the Fast PBU message (step S314).

In this case, when the home local mobility anchor LMAh ends buffering of data destined for the mobile node MN and transmits to the visited local mobility anchor LMAv through the set tunnel, the visited local mobility anchor LMAv is transmitted. Start buffering data.

Next, the mobile node MN is handed over at the request of the home mobile access gateway MAGh and connected to the serving gateway S-GW (step S315).

Subsequently, after the mobile node MN is handed over and connected to the serving gateway S-GW, the serving gateway S-GW is connected to the visiting policy server PSv and the home as in steps S218 to S221 of the second embodiment. Authentication of the mobile node MN is performed through the policy server PSh (steps S316 to 319).

When the AAA authentication is completed, the serving gateway S-GW recognizes the fact that the mobile node MN is handed over to the access network managed by the serving gateway S-GW (Link-Up Indication I) (step S320).

Next, the serving gateway S-GW notifies the visited local mobility anchor LMAv that the mobile node MN has moved (Link-Up Indication II) (step S321).

Here, the serving gateway (S-GW) informs the visited local mobility anchor (LMAv) of the mobile node (MN) of the mobile node by using the visited local mobility anchor (LMAv) address obtained through the AAA authentication.

At this time, the visited local mobility anchor LMAv ends buffering of data destined for the mobile node MN to transmit the buffered data and the RA message to the serving gateway S-GW (step S322), and the serving gateway S- GW) transmits the data and the RA message transmitted from the visited local mobility anchor (LMAv) back to the mobile node (MN) (step S323).

As such, when the handover of the mobile node MN is normally completed, the serving gateway S-GW requests the resource release from the home mobile access gateway MAGh to release resources for the mobile node MN. (Step S224).

In this way, even if the mobile node (MN) moves between different core networks to the mobile access gateway (MAG) supported access network, the new dynamic while utilizing the existing tunnel without modification of the mobile node (MN) Network-based vertical fast handover that does not require the creation of tunneling can be performed.

1 is a schematic configuration diagram of a system for vertical fast handover between heterogeneous networks based on the present invention;

FIG. 2 is a schematic structural diagram of a case where the system of FIG. 1 is managed on one core network. FIG.

3 is a schematic structural diagram of a case where the system of FIG. 1 is managed on different core networks;

4 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on the present invention.

5 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on a network according to a first embodiment of the present invention.

6 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on a network according to a second embodiment of the present invention.

7 is a flowchart illustrating a method for vertical fast handover between heterogeneous networks based on a network according to a third embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

MN: Mobile Node MAG: Home Mobile Access Gateway

LMA: Local Mobility Anchor MIIS: Media Independent Information Server

PS: Policy Server S-GW: Serving Gateway

Claims (23)

An information acquisition step of acquiring a neighboring network information from a media independent information server by a home mobile access gateway to which a mobile node is connected and to which a point of service (PoS) function is added; A threshold setting step of setting, by the home mobile access gateway, two thresholds relating to link quality to the mobile node; The mobile node determines the PoS as a handover candidate by checking a resource of a PoS corresponding to a handoverable network when the current measured link quality is equal to or less than a first threshold value; Wow; A resource reservation step of the mobile node reserving a corresponding resource with the determined candidate PoS when the current measured link quality is less than or equal to a second threshold value; When the home mobile access gateway requests a handover to the mobile node, the home mobile access gateway sends a Fast Proxy Binding Update (PBU) message including the ID of the mobile node and a Fast Proxy Binding Acknowledgment (PBA) message in response. Exchanging with a home local mobility anchor and buffering all data destined for the mobile node by the home local mobility anchor; And a resource release step of requesting resource release from the mobile node by accessing the mobile node to the candidate PoS and recognizing that the candidate PoS is connected to the mobile node. Heterogeneous vertical fast handover method. The method of claim 1, The candidate determination step, A first notifying step of the mobile node notifying the home mobile access gateway that the measured link quality is less than or equal to the first threshold value; When the home mobile access gateway notifies the mobile node of the handoverable network information, the mobile node selects a network that satisfies a current requirement and notifies the home mobile access gateway; And waiting for the mobile node to wait for a mobile connection by turning on an interface accessible to the selected network. The method of claim 1, The resource reservation step includes a second notification step of the mobile node notifying the home mobile access gateway that the measured link quality is less than or equal to the second threshold value. And the home mobile access gateway notifies the mobile node to move when reserving a resource to the determined candidate PoS. The method of claim 1, In the first buffering step, the home mobile access gateway notifies the determined candidate PoS when a handover request is made to the mobile node. The method of claim 1, In the first buffering step, the home mobile access gateway notifies the home local mobility anchor that the mobile node moves to the candidate PoS when the Fast PBU message is transmitted. 6. The method according to any one of claims 1 to 5, The handable network is an access network managed by the same core network as the network to which the mobile node is connected, and the determined candidate PoS is a visited mobile access gateway to which a PoS function is added. Fast handover method. The method of claim 6, The Fast PBU message further includes information of the visited mobile access gateway. The method of claim 6, The first buffering step, When the home local mobility anchor receives the Fast PBU message, sending a Reverse PBU message requesting binding processing to the visited mobile access gateway; A tunneling step in which the visited mobile access gateway sends a Reverse PBA message as a response to the home local mobility anchor so that tunneling between the visited mobile access gateway and the home local mobility anchor is performed. Vertical fast handover method between heterogeneous networks. The method of claim 8, The Reverse PBU message includes the ID of the mobile node and a Home Network Prefix (Home Network Prefix). The method of claim 6, A second buffering step, when the home local mobility anchor sends the buffered data to the visited mobile access gateway, the visited mobile access gateway buffers the transmitted data; And transmitting, by the visiting mobile access gateway, the buffered data and a router advertisement message (RA) message to the mobile node after the connection recognition of the mobile node to the mobile node. Vertical Fast Handover Method between Heterogeneous Networks. The method of claim 6, If the visited mobile access gateway requests authentication to a policy server after access of the mobile node, the policy server authenticates the related profile including address information of a local mobility anchor to the visited mobile access gateway; Network-based heterogeneous vertical vertical fast handover method comprising a. 6. The method according to any one of claims 1 to 5, The handable network is an access network managed by a core network different from the network to which the mobile node is connected, and the determined candidate PoS is a visited mobile access gateway to which a PoS function is added. Fast handover method. 13. The method of claim 12, The Fast PBU message further includes information of a visited local mobility anchor and the visited mobile access gateway. The method of claim 12, The first buffering step, After the home local mobility anchor receives the Fast PBU message and sends a Reverse Remote PBU message requesting binding processing to the visited local mobility anchor, the visited local mobility anchor requests binding processing to the visited mobile access gateway. A message transmitting step of transmitting a Reverse PBU message; A first tunneling step wherein the visited mobile access gateway sends a Reverse PBA message as a response to the visited local mobility anchor so that tunneling between the visited mobile access gateway and the visited local mobility anchor is performed; And a second tunneling step, wherein the visited local mobility anchor transmits a reverse remote PBA message to the home local mobility anchor to perform tunneling between the visited local mobility anchor and the home local mobility anchor. Vertical Fast Handover Method between Heterogeneous Networks. The method of claim 14, The Reverse Remote PBU message includes an ID of the mobile node, a home network prefix, and information of a visited mobile access gateway, and the Reverse PBU message includes an ID of the mobile node and a home network prefix. Vertical fast handover method between heterogeneous networks. 13. The method of claim 12, A second buffering step, when the home local mobility anchor sends the buffered data to the visited mobile access gateway, the visited mobile access gateway buffers the transmitted data; And transmitting, by the visiting mobile access gateway, data and an RA message buffered in the second buffering step to the mobile node after recognizing the connection of the mobile node. Vertical fast handover method. 13. The method of claim 12, An authentication request step of, when the visiting mobile access gateway requests authentication to a visiting policy server after access of the mobile node, the visiting policy server requests authentication to a home policy server; A first response step for the home policy server to respond to the visited policy server an associated profile including address information of a home local mobility anchor; And a second response step, wherein the visit policy server responds to the visited mobile access gateway a related profile that includes the address information of the visited local mobility anchor together with the address information of the home local mobility anchor. Network-Based Heterogeneous Vertical Fast Handover Method. 6. The method according to any one of claims 1 to 5, The handoverable network is an access network managed by a core network different from the network to which the mobile node is connected, and the determined candidate PoS is a serving gateway having a mobility management entity (MME) function to which a PoS function is added. A vertical fast handover method between network based heterogeneous networks. The method of claim 18, The Fast PBU message is a network-based heterogeneous network vertical fast handover method, characterized in that further comprises the information of the visited local mobility anchor. The method of claim 18, The first buffering step, After the home local mobility anchor receives the Fast PBU message, sending a Reverse Remote PBU message requesting a binding process to a visited local mobility anchor; And a tunneling step of tunneling between the visited local mobility anchor and the home local mobility anchor by transmitting a reverse remote PBA message to the home local mobility anchor as a response by the visited local mobility anchor. Vertical Fast Handover Method between Heterogeneous Networks. The method of claim 20, The Reverse Remote PBU message includes an ID of the mobile node and a home network prefix. The method of claim 18, A second buffering step, if the home local mobility anchor sends the buffered data to a visited local mobility anchor, the visited local mobility anchor buffers the transmitted data; A mobile notification step of the serving gateway notifying the visited local mobility anchor that the mobile node has moved after recognizing the connection of the mobile node; Transmitting, by the visiting local mobility anchor, the buffered data and the RA message in the second buffering step to the serving gateway, and the serving gateway transmitting the transmitted data and the RA message to the mobile node; A vertical fast handover method between heterogeneous networks based on a network comprising a. The method of claim 18, An authentication request step of, when the serving gateway requests authentication to a visit policy server after access of the mobile node, the visit policy server requests authentication to a home policy server; A first response step for the home policy server to respond to the visited policy server an associated profile containing address information of a home local mobility anchor; And a second response step, wherein the visit policy server responds to the serving gateway a related profile including the address information of the visit local mobility anchor with the address information of the home local mobility anchor. Vertical Fast Handover Method of Heterogeneous Networks.

Images