KR101373354B1 - Mobility management method and system using proxy mobile ip and mobile ip context transfer in a mobile telecommunication system - Google Patents

Abstract

The present invention relates to a method and system for managing address and mobility of a terminal using proxy mobile IP and fast mobile IP in a mobile communication network. A handover method of a terminal to a target access gateway of a mobile communication system using a proxy mobile IP (PMIP) according to the present invention transmits a fast binding update message from a target access gateway to a source gateway for managing mobility of the terminal. Receiving at least one information, transmitting information including at least one of a previous home address or home network prefix information used at a previous source access gateway to a router advertisement message to the terminal, and at the target access gateway Receiving data through the interface established with the source access gateway and providing the terminal to the terminal, wherein the interface is aware that the terminal is absent for a predetermined period of time from its access gateway; When the source access gateway learns the movement of the terminal, it is set according to a request transmitted from a target access node.

Proxy Mobile IP, 3GPP2 UMB, Mobility Management

Description

MOBILITY MANAGEMENT METHOD AND SYSTEM USING PROXY MOBILE IP AND MOBILE IP CONTEXT TRANSFER IN A MOBILE TELECOMMUNICATION SYSTEM}

The present invention relates to a method and system for mobility management of a mobile communication system, and more particularly, to a method for managing mobility of a terminal in a mobile communication system supporting a mobile IP or a proxy mobile IP. It is about the system.

In the mobile communication systems such as 3rd Generation Partnership Project 2 (3GPP2) system, Code Division Multiple Access (CDMA) 1x system, and Evolution Data Only (EV-DO) system, typical mobile communication systems manage radio resources. Network: hereinafter referred to as "AN"). In each of the above systems, a packet data serving node (hereinafter referred to as "PDSN"), which is a separate entity of a core network (hereinafter referred to as "CN"), is used for packet data communication. Perform the relevant procedure.

The mobile communication system as described above has provided mobility using mobile IPv4 and mobile IPv6 in a mobile environment of a terminal. However, the above methods of mobile IP are inadequate for transmitting more data at higher speed. That is, many improvements have been made in the above mobile communication systems in order to transmit a larger amount of data at high speed. As one of the methods for transmitting a larger amount of data at higher speed in mobile communication systems, the method of Ultra Mobile Broadband (hereinafter referred to as “UMB”) has been proposed in 3GPP2. The mobile communication system using the UMB method is not suitable for using mobile IP as it is. Therefore, the use of Proxy Mobile IP (Proxy MIP) as one of the ways to support UMB more efficiently is discussed.

On the other hand, when a terminal moves not only within the UMB but also uses a different access network technology, for example, when the terminal moves across a UMB network, a 3GPP, or a WiMAX network, mobility is performed using the proxy mobile IP. There is a need for more efficient support. That is, the MIP method used in the conventional CDMA 1x or EV-DO system requires a lot of time in connection and call processing. Therefore, mobile IP provides mobility compared to simple IP, but due to the time required for security, call processing, and database management for mobility support in connection and call processing and security processes, There was a problem of time delay.

In the conventional Internet communication, fast mobile IP (hereinafter referred to as "FMIP") has been proposed as a solution to solve the problem of time delay of mobility support of mobile IP. However, in the wireless access process of the mobile communication system, there is no case applied to the mobile communication system because of the complexity of the procedure and the difference. Therefore, the current mobile communication system is not applicable to the FMIP method, and until now there is a problem that there is no way to manage mobility resources at high speed using mobile IP, and to quickly perform security, call processing and database management. .

Accordingly, the present invention provides a method and system for supporting fast mobility of a terminal in a mobile communication system that is evolving to provide high speed packet data.

The present invention provides a fast handover to a terminal when a handover is made from a mobile communication system to another mobile communication system.

The method according to the preferred embodiment of the present invention is a handover method of a terminal to a target access gateway of a mobile communication system using a proxy mobile IP (PMIP), by transmitting a fast binding update message from a target access gateway to a source gateway Receiving at least one information for mobility management of the terminal, and transmitting information including at least one of a previous home address or home network prefix information used in a previous source access gateway to a router advertisement message to the terminal; And receiving, by the target access gateway, data through an interface established with the source access gateway and providing the data to the terminal, wherein the interface is connected to the terminal from the access gateway for a predetermined time. Found that the or or characterized in that said source access gateway when the learned movement of the terminal, a set according to the request transmitted from the target access node.

A system according to a preferred embodiment of the present invention uses a proxy mobile IP and is a mobile communication system for supporting handover of a terminal, and transmits a fast binding update message from a target access gateway to a source access gateway to provide mobility of the terminal. Receives a message for management, receives data through the interface set between the source access gateway and the target access gateway to provide to the terminal, and triggers when receiving the fast binding update response message to the home agent A target access gateway configured to set an interface with a home agent by transmitting a message for managing the movement status of the terminal to the mobile station; and when the movement of the terminal is detected, buffer the data, provide the target access gateway, And a source access gateway providing a quick response message including at least one information for managing mobility information of the terminal upon receiving an update update message, wherein the interface has no terminal on the link for a predetermined time from the access gateway. If it is known that the source access gateway or the movement of the terminal, characterized in that configured according to the request sent from the target access node.

According to the present invention, there is an advantage that the call setup delay for data communication can be reduced during the registration process for the use of mobile IP when the terminal moves when using mobile IP. In addition, when the terminal moves to another access network, there is an advantage that can eliminate the time delay caused by call reconfiguration. Therefore, by efficiently performing call setup and registration in a network using the same access technology or in a mobile system using another access technology, there is an advantage that the mobility of the terminal can be managed more quickly and efficiently and the data communication can be processed.

The operation principle of the preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions of the present invention and may be changed according to the intention or custom of the user and the operator. Therefore, the definition should be based on the contents throughout this specification.

In the following description of the present invention will be described for providing a mobility management method of a terminal using a proxy mobile IP for a mobile communication system. In the following description, the UMB system based on 3GPP2 will be used, and the present invention can be used in an Evolved Packet Core (EPC) or WiMAX evolved system, which is an evolved mobile communication system of 3GPP. In addition, the present invention may be used when the terminal moves to a network using a UMB system based on 3GPP2 and other wireless access technologies such as WiMAX and 3GPP. Accordingly, the present invention is a method of internet communication using proxy mobile IP and context transfer in mobile communication, and in other mobile communication systems having a similar technical background and channel form, the present invention does not significantly depart from the scope of the present invention. Modifications are applicable, which will be possible in the judgment of a person skilled in the art.

1 is a conceptual diagram illustrating an overall operation in a mobile communication system environment according to a preferred embodiment of the present invention. 1 illustrates a 3GPP2 UMB system, WiMAX, and 3GPP LTE network structure as an example.

The access networks 121 and 122 are connected through a wireless channel with a terminal 110 located in a cell serving each service area (Access Terminal: AT). Set up and perform communication. AT 110 refers to a terminal that accesses a packet data network, such as the Internet, through Access Gateways (hereinafter referred to as "AGW") 105, 106. In the AGW 105, 106, an external agent in charge of a function of accessing a packet data network of a terminal that has moved when a terminal having another network as its home network has moved to a network area managed by the AGW 105, 106 is provided. (Foreign Agent) function (not shown in Figure 1) is provided.

In FIG. 1, home agents (hereinafter referred to as "HA") 102 and 103 and authentication and billing (hereinafter referred to as "AAA") servers as main network entities of a packet data network ( 101 is shown. In addition, an interface and a data path for managing mobility of the terminal between the ANs 121 and 122 and the AGWs 105 and 106, the SRNCs 131 and 132, and the AGWs 105 and 106. Is present. In the present invention, the AT 110 is a terminal having an IP protocol stack and mobility management may be performed by proxy mobile IP.

Meanwhile, in the present invention, network 3 (hereinafter referred to as "NW3") 145 is a WiMAX, UMB, or 3GPP network, and NW3 is an access service network gateway (network entity) denoted by reference numeral 107. Gateway: (hereinafter referred to as "ASN-GW"), gateway (GW), serving gateway (Serving Gate way: referred to as "S-GW") or access gateway (AGW), or packet data service node (PDSN) do. For convenience of description, it will be referred to as an access gateway. A base station (BS or AN3 or e-Node B), which is a network entity indicated by reference numeral 123, is connected to the access gateway of NW3, and communicates with a terminal (AT) 110 through a wireless channel through the base station. can do.

At this time, the terminal (AT) 110 under Network 1 (hereinafter referred to as "NW 1") 123 is NW 2 143, which is a UMB network, or NW3, which is a UMB network or a WiMAX, 3GPP network, through handoff. 145 and NW1 and NW2 include AGW and AN as described above. In addition, home agent 2 indicated by reference numeral 103 (Home Agent: HA2) may play a role of a packet data network gateway (denoted as a P-GW or PDN-GW) in the case of a 3GPP network.

The home agent (HA1) denoted by reference numeral 102 and AGW 1 (105) or AGW 2 (106) communicate in the IPv6 manner, and can support some call processing using the PMIPv6 and FMIP schemes. Network.

In the present invention, some call processing procedures of FMIP are supported for context transfer between AGW1 105 and AGW2 106. At this time, even though the terminal (AT) 110 moves from NW1 141 to NW 2 (143), the home agent HA 1 (102) is shared, and part of the FMIP call processing process between AGW1 (105) and AGW2 (106) Through the AGW2 106 can be seen that the HA to use as a home agent for communication of the terminal 110 is HA1 (102). In addition, the AGW2 106 to which the terminal 110 moves may receive a home network prefix, a Proxy-CoA in the previous AGW1 105, and the like through a context transfer method. Through this, the present invention has the advantage of performing the registration procedure of the terminal faster while maintaining the session in the mobility registration procedure of the terminal. This detailed process will be described in more detail later with reference to FIGS. 2 and 3. In addition, the terminal 110 may handoff from the NW 1 141 to the NW 2 143 or the opposite direction or handoff from the NW 1 141 to the NW 3 145 or the opposite direction.

2 is a message flow diagram illustrating a mobility management procedure of a terminal in a reactive environment according to an exemplary embodiment of the present invention.

FIG. 2 will be described with reference to a case in which the terminal 110 handoffs from NW 1 141 to NW 2 143 in FIG. 1. However, if a similar environment, that is, an environment where some messages of Proxy mobile IP and FMIP are supported, the basic idea of the present invention can be applied.

In step 201, a data communication channel between the AT 110, the source AN 121, the source AGW 1 105, and the HA 102 is established to perform communication. At this time, if the network is a UMB, data communication is performed through a Generic Routing Encapsulation (GRE) tunnel between the source AGW 105 and the source AN 121. In operation 203, the AT 110 requests the target AN 122 to be included in the active set. At this time, the target SRNC 132 fetches session information of the AT 110 from the source SRNC 131. Then, in step 205, the AT 110 performs L2 fast switching to the target AN 122, and between the target AN 122 and the source AN 121 is referred to as a Layer 2 tunnel protocol (hereinafter referred to as "L2TP"). After the tunnel is created, data transmission continues through the tunnel. Thereafter, the target SRNC 132 transmits session information to the target AN 122.

In step 207, the source AGW 105 knows that there is no AT 110 on its link for a certain time or buffers the packet for the AT 110 when the source AGW 105 knows that the AT 110 is moving. do. In step 209, a proxy registration message (hereinafter referred to as "proxy RRQ") from the target AN 122 to the target AGW 106 for setting up a signaling interface between the target AN 122 and the target AGW 106. Send the message "PRRQ". As a response to the PRRQ, the target AN 122 receives a proxy registration response message (hereinafter referred to as "Proxy RRP" or "PRRP") from the target AGW 106. Through this, information necessary for data communication, for example, GRE key is set.

In step 211, the target AN 122 notifies the target SRNC 132 or the source AN 121 of the address and the GRE key of the target AGW 106. The target SRNC 132 or the source AN 121 sends an acknowledgment thereto.

In operation 213, the target AGW 106 may send a fast binding update (“FBU”) message to the source AGW 105 to request information related to the AT 110. Then, in step 215, the source AGW 105 performs a context transfer related to handoff with a fast binding acknowledgment (“FBack”) message in response to the FBU. The format and option of the message used in steps 213 and 215 will be described later with reference to FIGS. 2 and 3.

In step 217, the target AGW 106 transmits a proxy binding update message (“PBU”), which is a proxy registration request message, to the HA 102, and thus, between the target AGW 106 and the HA 102. Set up the interface. Step 215 and step 217 are processes that can be performed in parallel. In step 215, the target AGW 106 obtains information of the HA 102 for the AT 110. . Thereafter, in step 219, the packet is transmitted through the interface established between the source AGW 105 and the target AGW 106.

In addition, in step 221, the AGW 106 receives a proxy binding acknowledgment (hereinafter referred to as "PBAck") from the HA 102 in response to the proxy registration request message. The target AGW 106 then transmits the home network prefix (HN-Prefix) in the router advertisement message from the AGW 106 to the AT 110 when the AT 110 is an IPv6 terminal (223). This allows the AT 110 to generate an address, such as the home address (HoA), used in the previous gateway source AGW 105. As such, by using the same address as the home address (HoA) used in the previous gateway source AGW 105, the AT 110 may receive a seamless service even during handover. On the other hand, if the AT 110 is an IPv4 terminal in step 223, the home AGW 105 used by the source AGW 105, which is the previous gateway, may be a response message (DHCP Acknowledgement with rapid commit) that is a response message from the AGW 106 to the AT 110. By sending the address (HoA) to support the seamless service even in the handover of the terminal.

When the handover procedure is completed through the above-described process, a data communication channel between the target AN 122, the target AGW 106, and the HA 102 is established in step 225, and thus data communication is possible.

3 is a message flow diagram illustrating a mobility management procedure of a terminal in a predictive environment according to an embodiment of the present invention.

FIG. 3 will be described with reference to FIG. 1 described above, and the case where the AT 110 handoffs from NW 1 141 to NW 2 143 will be described as an example. However, if a similar environment, that is, an environment in which some messages of Proxy mobile IP and FMIP are supported, the basic idea of the present invention can be applied.

In step 301, as shown in FIG. 2, a communication channel between the AT 110, the source AN 121, the source AGW 1 105, and the HA 102 is established to perform communication. At this time, if the network is UMB, data communication is performed between the source AGW 105 and the source AN 121 through the GRE tunnel.

In operation 303, the AT 110 illustrates a process of requesting to include the target AN 122 in an active set. At this time, the target SRNC 132 fetches session information from the source SRNC 131. In step 305, the AT 110 performs L2 fast switching to the target AN 122. Accordingly, data is transmitted between the target AN 122 and the source AN 121 through an L2TP tunnel, and then the target SRNC 132 transmits session information to the target AN 122. Then, in step 307, the Source-AGW 105 is notified of the handoff of the AT 110 through the Source AN 121 or the Source SRNC 131. Source AGW 105 thus buffers the packet for AT 110.

Thereafter, in step 309, the proxy RRQ is transmitted from the target AN 122 to the target AGW 106 to set up a signaling interface between the target AN 122 and the target AGW 106. In response, the target AN 122 receives the Proxy RRP from the target AGW 106. Through this, information necessary for data communication, for example, GRE key is set. In operation 311, the target AN 122 notifies the target SRNC 132 or the source AN 121 of the address and the GRE key of the target AGW 106. The target SRNC 132 or the source AN 121 then transmits an acknowledgment to the target AN 122.

In step 313, the source AGW 105 generates and transmits a handover initiation message (hereinafter, referred to as “HI”) to the target AGW 106. At this time, the source AGW 105 performs a context transfer to the target AGW 106 for handover. Then, in step 315, the target AGW 106 transmits a handover acknowledgment (“HAck”) message in response to receiving the information for mobility management from the source AGW 105. Then, in step 317, the packet is delivered through the interface established between the source AGW 105 and the target AGW 106, and in step 319, the data delivered to the target AGW 106 is buffered to the target AGW 106. .

Thereafter, if the AT 110 is an IPv6 terminal in step 321, the AT 110 is a previous gateway by transmitting a home network prefix (HN-Prefix) together with a router advertisement message from the AGW 106 to the AT 110. It generates the same address as the home address (HoA) used in the source AGW (105). Through this, even when handover of the terminal to support a seamless service. On the other hand, if the AT 110 is an IPv4 terminal at step 321, the source AGW 105, which is the previous gateway, is assigned to a DHCP Acknowledgment with Rapid Commitment with a fast processing option that is a response message from the AGW 106 to the AT 110. By sending the same address as the home address (HoA) that is being used, it is possible to support a seamless service even during handover of the terminal.

In operation 323, the target AGW 106 sets an interface between the target AGW 106 and the HA 102 by transmitting a PBU message, which is a proxy registration request message, to the HA 102. In response to the PBU in step 325, the target AGW 106 receives the following PBAck from the HA 102.

The above step 321 may be performed after the setting of the interface between the target AGW 106 and the HA 102 or after the step 325, or may be performed in parallel, but for more accurate process, the steps 321 to 323 to 325 may be performed. It is more stable to carry out after the step. When the handover procedure is completed, a data communication channel between the target AN 122, the target AGW 106, and the HA 102 is established in step 327, and thus data communication is possible.

Next, an information delivery method for supporting a mobility management procedure of a terminal of the present invention will be described. As described above with reference to FIGS. 2 and 3, an FBAck message is used in a reactive method and a HI message is used in a predictive method for information transmission. By default, the default format of these two messages follows the message format of FMIP, and additionally includes an option containing the following information. That is, network access identifier (NAI) information, home address information of AT 110, and proxy in source AGW 105 as an identifier of AT 110. Proxied address (Proxy CoA), that is, address information of the serving AGW (105), proxy proxy address (Proxy CoA) information in the target AGW (106), that is used to generate the address information of the target AGW (106), the address of the terminal Includes options that indicate Home Network prefix information.

In the above, the NAI option includes NAI information, which may be used together with the PMIP mobility management information as main information regarding mobility management and authentication for PMIP. In addition, the Proxy CoA (care of address) in the Serving AGW or Target AGW means that the gateway requests registration on behalf of the UE, so the gateway address is registered in the database of the binding cache for the UE. The source (Serving) or Target gateway is named Proxy CoA.

In addition, additional information may be optionally defined. Some of the options will be described in Tables 1 to 4 below.

On the other hand, the FBU message requesting information transfer in a reactive method is optionally added with proxy coarse address (Source CoW) at the source AGW 105 and proxy coarse address (Proxy CoA) information at the target AGW 106 as an option. The two ends of the bi-directional tunnel for information delivery. In addition, HAck, which is a response message for receiving information in a predictive method, optionally adds proxy CoA information in the target AGW 106, so that the source AGW 105 adds the target AGW 106 to the target AGW 106. Use Proxy CoA at the end of the tunnel.

In the present invention, only a few options, etc. are mentioned in addition to the conventionally existing options as message options in the present invention, but the LCP state, IPCP state, IPv6CP state, CCP state, etc., header compression state, and QoS state for PPP state management. Information such as a TFTv4 state, a TFTv6 state, and a vendor specific state may also need to be transmitted, and detailed description thereof will be omitted.

It will be described with respect to the <Table 1> to <Table 4> options that are additionally defined in the following description. The length occupied by each message described below is indicated by the length of the byte, and a bit is specified if necessary. In addition, the added message option takes the form of TLV (type, length, value).

Message option format 1 according to an embodiment of the present invention is a message option for informing the address of a home agent, and this may be illustrated as Table 1 below.

Type (1 byte) Length (1 byte) Reserved (2 bytes) Home Agent (16 bytes)

Referring to Table 1, it includes a message type field for indicating an option type of a message, a length field for indicating a length of a message, a reserved field for future use, and a Home Agent field indicating a home agent address.

Next, the message option format 2 according to the present invention may be a message related to a security key as shown in Table 2 below.

Type (1 byte) Length (1 byte) Reserved (2 bytes) PMIP related Key (16 bytes: TBD)

In Table 2, there is a PMIP related key field indicating a PMIP related key. For example, a root key used to generate a PMN-AN-HA key, which is a key between an AGW such as PMN-AN-RK and eBS, may be transmitted to the PMIP-related key field.

Next, the message option format 3 according to the present invention is a message related to the set life time of a tunnel, and may be shown in a table as shown in Table 3 below.

Type (1 byte) Length (1 byte) Reserved (2 bytes) Lifetime (2 bytes) Reserved (2 bytes)

Finally, the message option format 4 according to the present invention is a message related to a GRE key and can be shown as shown in Table 4 below.

Type (1 byte) Length (1 byte) Reserved (2 bytes) GRE key (4 bytes) lifetime (2 bytes) Reserved (2 bytes)

The message option format 4 of Table 4 includes a GRE key and life time information of the key.

4 is a flowchart illustrating operations during handover in a target access gateway according to an exemplary embodiment of the present invention. In general, the target access gateway means an access gateway of a network to which the terminal will move at the time of handover. In the following description, the configuration of the network is to use the configuration of FIG. 1 described above.

The target AGW 106 receives the PRRQ message for establishing the PMIP interface between the AN 122 and the AGW 106 from the target AN 122 in step 401 and the PRRP in response to the PRRQ message to the target AN 122. Send a message.

Then, in step 403, the operation of the target AGW 106 branches depending on whether the network supports the reactive method or the predictive method.

In case of supporting the reactive method, the target AGW 106 sends an FBU message to the source AGW 105 to request information transfer for mobility management in step 411. Then, in step 413, the target AGW 106 receives the context transfer information from the source AGW 105 through the FBAck message for information on mobility management. In step 415, the target AGW 106 receives the home agent 102. The PBU message, which is a proxy registration request message, is transmitted. Steps 413 and 415 are processes that can occur in parallel as soon as the HA information is obtained in step 413. Thereafter, the packet is delivered to the target AGW 106 through the interface established with the source AGW 105 in step 417. Thereafter, in step 419, a PBAck message is received from the HA 102 in response to the PBU message in step 415.

In step 421, when the AT 110 is an IPv6 terminal, the target AGW 106 transmits a home network prefix (HN-Prefix) to the router advertisement message from the AGW 106 to the AT 110. The 110 generates the same address as the home address (HoA) used by the source gateway, the source AGW 105. Through this, even when handover of the terminal to support a seamless service. As described above, when the handover procedure is completed, data communication is possible through the communication channel established between the target AN 122, the target AGW 106, and the HA 102 in step 423.

On the other hand, if the network supports the predictive method in step 403, the process branches to step 441, and in step 441, the target AGW 106 transfers information for mobility management from the source AGW 105 through the HI message. Receive. In step 443, the target AGW 106 sends a HAck message in response to receiving the information for mobility management from the source AGW 105, and in step 445, the target AGW 106 between the source AGW 105 and the target AGW 106; Packets are delivered through the configured interface. Thereafter, the data transferred to the target AGW 106 in step 447 is buffered to the target AGW 106.

Thereafter, in step 449, the target AGW 106 receives the home network prefix received from the previous source AGW 105 in a router advertisement message from the AGW 106 to the AT 110 when the AT 110 is an IPv6 terminal. By transmitting the (HN-Prefix) together, the AT 110 generates the same address as the home address (HoA) used by the serving AGW 105, which is the previous gateway. Through this, even when handover of the terminal to support a seamless service. Step 449 may be performed at step 449 when the information transmission is completed, or after step 453, that is, after setting up an interface between the target AGW 106 and the HA 102, that is, step 454.

In step 451, the target AGW 106 transmits a PBU message, which is a proxy registration request message, to the home agent 102. In step 453, the HA 102 receives a PBack message, which is a proxy registration response message, in response to the proxy registration request message. After the handover procedure is completed, data communication through a communication channel established between the target AN 122, the target AGW 106, and the HA 102 is enabled in step 455.

1 is a conceptual diagram illustrating the overall operation in a mobile communication system environment according to an embodiment of the present invention;

2 is a message flow diagram illustrating a mobility management procedure of a terminal in a reactive environment according to an embodiment of the present invention;

3 is a message flow diagram illustrating a mobility management procedure of a terminal in a predictive environment according to an embodiment of the present invention;

4 is a flowchart illustrating operations during handover in a target access gateway according to an exemplary embodiment of the present invention.

Claims (4)

In a handover method of a terminal to a target access gateway of a mobile communication system using a proxy mobile IP (PMIP), Receiving at least one information for mobility management of the terminal by transmitting a fast binding update message from a target access gateway to a source gateway; Transmitting information including at least one of a previous home address or home network prefix information used in a previous source access gateway to the terminal in a router advertisement message; Receiving data from the target access gateway through an interface established with the source access gateway and providing the data to the terminal; The interface is configured according to a request transmitted from a target access node when the access gateway knows that the terminal is not in the link for a predetermined time or when the source access gateway learns the movement of the terminal. How to manage. In a handover method of a terminal to a target access gateway of a mobile communication system using a proxy mobile IP (PMIP), Receiving at least one information for mobility management of the terminal through a handover initiation message from a source access gateway to the target access gateway, and transmitting a response message thereto; Buffering the received data by using an interface connected to the source access gateway; Transmitting, to the terminal, information including at least one of a previous home address or home network prefix information used in a previous source access gateway in a router advertisement message; Receiving data from the target access gateway through an interface established with the source access gateway and providing the data to the terminal; The interface is configured according to a request transmitted from a target access node when the access gateway knows that the terminal is not in the link for a predetermined time or when the source access gateway learns the movement of the terminal. How to manage. The method according to claim 1 or 2, Information for mobility management of the terminal includes network access identifier (Network Access Identifier) information, the home address (home address) information of the terminal, the proxy access address (Proxy CoA) information in the source access gateway, the proxy in the target access gateway Referral address information, home network prefix information used to generate the address of the terminal, home agent address information, PMIP related key information in relation to security, life time information of the tunnel, GRE and at least one of key and life time information of the key. In the mobile communication system using a proxy mobile IP, to support the handover of the terminal, Sending a fast binding update message from a target access gateway to a source access gateway to receive a message for mobility management of the terminal, and receives the data through the interface set between the source access gateway and the target access gateway to provide to the terminal And a target access gateway configured to set an interface with the home agent by transmitting a message for managing the movement of the terminal to the home agent by triggering the quick binding update response message upon receiving the fast binding update response message. Source access for buffering data, providing data to the target access gateway, and providing a quick response message including information for managing mobility information of the terminal when the quick binding update message is received when the movement of the terminal is detected. A gateway; The interface may be configured according to a request transmitted from a target access node when the access gateway learns that the terminal does not exist in the link for a predetermined time or when the source access gateway learns the movement of the terminal. System for mobile mobility management.

Images