KR101357511B1 - Mobility management method and apparatus using proxy mobile ip in mobile telecommunication system - Google Patents

Abstract

The present invention provides a method for managing mobility of a terminal using a proxy mobile internet protocol in a mobile communication system, wherein the target access gateway is to be handed off by a target access gateway and a proxy mobile internet as the terminal is handed off from a source network to a target network. Performing a proxy registration procedure for setting a protocol interface, transmitting a handoff request message from the target access gateway to a source access gateway, and relating to handoff including mobility information and a home address of a terminal used by the source access gateway Receiving a response message to the handoff request message carrying information, transmitting and receiving data through an interface established between the source access gateway and the target access gateway, and replacing the terminal. Sending a message to the proxy registration request to the home agent, and receives a response message to the proxy registration request from the home agent, and transmitting and receiving the target base station and a home agent in the data.

Proxy Mobile IP, 3GPP2 UMB, Mobility Management

Description

Mobility management method using proxy mobile IP in mobile communication system and apparatus therefor {MOBILITY MANAGEMENT METHOD AND APPARATUS USING PROXY MOBILE IP IN MOBILE TELECOMMUNICATION SYSTEM}

The present invention relates to a mobile communication system, and more particularly, to a method and apparatus for more efficiently managing mobility of a terminal in a handoff situation of a terminal in a mobile communication system supporting proxy mobile IP.

In a mobile communication system such as 3rd Generation Partnership Project 2 (3GPP2) Code Division Multiple Access (CDMA) 1x and Evolution Data Only (EV-DO), a base station (hereinafter referred to as AN) is responsible for managing a large number of radio resources. In addition, a packet data serving node (hereinafter referred to as PDSN), which is a separate entity of a core network (hereinafter referred to as CN), performs a procedure related to packet data communication.

Conventional mobile communication systems as described above have provided mobility to terminals using mobile IPv6, mobile IPv6. However, typical mobile IP is not suitable for use in Ultra Mobile Broadband (UMB), a 3GPP2 improvement that seeks to send more data at higher speeds. Therefore, the use of proxy mobile IP as one of the ways to support UMB more efficiently is being discussed. In addition, when the terminal moves between not only the UMB but also networks using different access network technologies, that is, when the terminal moves across a UMB network and a 3GPP or World Interoperability for Microwave Access (WiMAX) network, for example. There is a need for a scheme for more efficiently supporting mobility of terminals using proxy mobile IP.

Mobile IP used in the conventional CDMA 1x or EV-DO system requires a lot of time in connection and call processing. In other words, Mobile IP has the advantage of providing mobility compared to Simple IP, but the problem of time delay for security process, call processing process, and database management for mobility support in connection and call processing and security process. Since this has occurred, there is a need for a technique for solving such a problem.

The problem to be solved by the present invention is to provide a method and apparatus for supporting fast mobility and more secure and efficient communication to the terminal by using the proxy mobile IP and information delivery method in the evolved mobile communication system including 3GPP2 UMB It is.

In addition, the problem to be solved by the present invention is to provide a fast mobility to the terminal through the handoff technology through the proxy mobile IP and information transfer method, even if the terminal moves to another wireless access technology, that is, a handoff situation In the present invention, a method and apparatus for efficiently managing mobility of a terminal using a proxy mobile IP and a context transfer method are provided.

In addition, the problem to be solved by the present invention is RADIUS (using authentication and billing server (AAA) on the premise that a security framework for access authorization of EAP (Extensible Authentication Protocol) or other terminal in the mobile communication system) The present invention provides a method and apparatus for managing mobility by using a protocol such as Remote Authentication Dial In User Service, a diameter, proxy mobile IP, and a context transfer method.

The method according to an embodiment of the present invention provides a method for managing mobility of a terminal using a proxy mobile internet protocol in a mobile communication system, wherein the target access gateway is handed as the terminal is handed off from the source network to the target network. Performing a proxy registration procedure for setting a proxy mobile internet protocol interface with a target base station to be turned off, transmitting a handoff request message from the target access gateway to a source access gateway, and using mobility information and the source access gateway Receiving a response message for the handoff request message carrying the handoff related information including the home address of the terminal, and through an interface established between the source access gateway and the target access gateway Transmitting and receiving data, transmitting a message for requesting a proxy registration to a home agent on behalf of the terminal, receiving a response message for the proxy registration request from the home agent, the target base station and the And sending and receiving data with the home agent.

In addition, the apparatus according to an embodiment of the present invention is a target access gateway device for managing mobility of a terminal using a proxy mobile Internet protocol in a mobile communication system, as the terminal handoffs from a source network to a target network, An interface setting unit for performing a proxy registration procedure for setting a target mobile station and a proxy mobile internet protocol interface to be turned off, transmitting a handoff request message from the target access gateway to a source access gateway, and transmitting the source access gateway and the target access Transmits data through an interface set between gateways, transmits a message for proxy registration request to a home agent on behalf of the terminal, and transmits data to the target base station and the home agent. And a response message to the handoff request message including handoff related information including mobility information and a home address of a terminal used by the source access gateway, between the source access gateway and the target access gateway. And a receiving unit for receiving data through the set interface, receiving a response message for the proxy registration request from the home agent, and receiving data from the target base station and the home agent.

The effect obtained by the typical thing of the invention disclosed below is demonstrated briefly as follows.

The present invention is a problem of call setup delay for data communication in the case of performing the registration process to continue using the mobile IP currently used even in the cell to be moved when using the mobile IP and when the terminal moves to another access network. In this case, the problem of time delay caused by call resetting is solved. To this end, the present invention utilizes a proxy mobile IP (hereinafter referred to as Proxy MIP or PMIP) and a context transfer method to efficiently establish a call in a network using the same access technology or a mobile system using another access technology. By performing the registration process with the mobile station, the mobility of the terminal can be managed more quickly and efficiently.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an operation principle of an 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. In addition, terms to be described below are terms defined in consideration of functions in the present invention, which may vary according to a user's or operator's intention or custom. Therefore, the definition should be based on the contents throughout this specification.

SUMMARY OF THE INVENTION The present invention to be described later provides a method for managing mobility of a terminal using proxy mobile IP in a mobile communication system. In the following description, the UMB system based on 3GPP2 will be used. However, the present invention can be used in Evolved Packet Core (EPC) or WiMAX evolved system, which is an evolved mobile communication system of 3GPP. In addition, the present invention can be used when the terminal moves to a network using another wireless access technology. Therefore, the Internet communication method using proxy mobile IP and context transfer of the mobile communication system, which is the basic object of the present invention, does not significantly depart from the scope of the present invention in other mobile communication systems having similar technical background and channel form. Applicable in a slight modification in the scope, this will be possible in the judgment of a person skilled in the art.

 1 is a block diagram showing a mobile communication system environment and overall operation according to an embodiment of the present invention. Here, as an example, a structure in which a 3GPP2 UMB system, a WiMAX network, and a 3GPP Long Term Evolution (LTE) network coexist.

Referring to FIG. 1, the base station (AN) 121, 122 establishes a wireless connection and performs communication with a terminal (AT) 110 located in a cell serving each service area, and performs a signaling radio network controller (Signal Radio). Network Controller (hereinafter referred to as SRNC) 131, 132 to communicate with the AGW 105, 106 or the AAA server 101.

AT 110 refers to a user device that connects to a packet data network, such as the Internet, through access gateways (AGW) 105, 106 via respective ANs 108, 109. In the AGWs 105 and 106, when the AT 110 having another network as the home network has moved to the service area of the networks 141 and 143 managed by the AGWs 105 and 106, the AT 110 is moved. A foreign agent (FA) function (not shown), which is in charge of connecting to a packet data network, is provided.

In the present specification, as a main entity of a packet data network, home agents 102 and 103 which perform mobility management for the terminal and authentication and charging for performing an access authentication process with the terminal are performed. Authorization and Accounting (hereinafter referred to as AAA) server 101 is shown.

An interface and data path exist between AN 121 and 122 and AGW 105 and 106 and SRNC 131 and 132 and AGW 105 and 106 respectively for managing mobility of AT 110. do. The AT 110 has an IP protocol stack and mobility management may be performed by proxy mobile IP.

Network 3 (NW3, 145) represents a WiMAX, UMB, or 3GPP network, which is an access service network gateway (hereinafter referred to as ASN-GW) or a gateway (GW or Serving Gate way (S-GW) (107), the network entity AN 3 (Access network 3) or base station (BS) or e (Evolved) -Node B (123), and AT (110) AT 110 that was under NW1 123 may move to a NMB1 141 or NW2 143, which is a UMB network, through handoff, as described above. AGW 105, 106, and AN 121, 122, respectively, and AGW1 105 of NW1 141 may share NW2 143 and HA1 102. PDW or ASN of NW3 145, respectively. -GW1 107 can share AGW1 105 and HA2 103 of NW1 141, but specific description will be omitted in the present invention, and HA2 103 is 3G. In the case of the PP network, the packet data network gateway (hereinafter referred to as P-GW or PDN-GW) may play a role.

If either IPv4 or IPv6 is used between HA1 102 and AGW1 105 or HA1 102 and AGW2 106, and especially mobility support by the network, ie PMIP, the interface between HA1 and AGW or the interface between HA1 and AGW It can support PMIPv4 or PMIPv6.

In the present invention, an interface for context transfer between AGW1 105 and AGW2 106 is supported. Even though AT 110 moves from NW1 141 to NW 2 143, it shares HA 1 102, and through the interface of AGW1 105 and AGW2 106, AGW2 106 becomes its home agent. Knowing that the HA to be used is HA1 102, the AT (110) has moved its AGW2 106 to its home network prefix, the Proxy Care of Address (formerly Proxy-CoA) at the former AGW1 105. Receiving such information in a context transfer method has the advantage of performing the registration procedure of the terminal faster while maintaining the session in the mobility registration procedure of the terminal.

Hereinafter, an information delivery method according to an embodiment of the present invention will be described in detail with reference to FIGS. 2 and 3. AT 110 may handoff from NW 1 141 to NW2 143 or vice versa, or may handoff from NW1 141 to NW3 145 or vice versa.

2 is a message flow diagram illustrating a mobility management procedure of a terminal in a PMIPv4 environment according to an embodiment of the present invention. In FIG. 2, the AT 110 handoffs from NW1 141 to NW2 143 in FIG. 1, but an environment using a similar mechanism, that is, an interface between a proxy mobile IP and an access gateway for information delivery is supported. If it is an environment, the basic idea of the present invention can be applied.

2, in step 201, the AT 110, the source AN (Source-AN, 121), the source AGW (Source-AGW) 105, and the HA 102 are involved to perform communication. In the case of UMB, data communication is performed through a Gernic Routing Encapsulation (GRE) tunnel between the Source-AGW 105 and the Source-AN 121.

In step 203, the AT 110 requests the target SRNC 132 to include the target AN 120 in the active set, and the target-SRNC 132 requests the source SRNC. Fetch session information from (Source-SRNC, 131).

In step 205, the AT 110 executes Layer 2 fast switching to the Target-AN 122, and a Layer 2 tunnel protocol (Layer 2) between the Target-AN 122 and the Source-AN 121. tunnel protocol (hereinafter referred to as L2TP) data transmission continues through the tunnel. Thereafter, the Target-SRNC 132 transmits session information to the Target-AN 122.

In step 207, the proxy registration request (hereinafter referred to as Proxy RRQ or PRRQ) from the Target-AN 122 to the Target-AGW 106 for the signaling interface between the Target-AN 122 and the Target-AGW 106. The target AN 122 receives a proxy registration response message (hereinafter referred to as Proxy RRP or PRRP) from the target AGW 106, such as GRE. Key and so on.

In step 209, the Target-ANNC 122 notifies the Target-SRNC 132 or the Source-AN 121 of the Target-AGW 106 and the GRE key. The -AN 121 sends an acknowledgment message to the Target-AN 122.

In step 211, the target-AGW 106 transmits a handoff (HO) request message to the source-AGW 105. In this case, it is possible to include in the handoff request (HO_Request) message which context information to request or a GRE key to be used for data communication mapping with AN. The format and option of the message used in the handoff request will be described later.

In step 213, the Source-AGW 105 sends a handoff response (HO_Response) message including context transfer to the Target AGW 106 in response to the handoff request. The format of the handoff response message and the options used for the information transfer will be described later. The target-AGW 106 may send a handoff acknowledgment (HO_Ack) message in step 215 depending on whether the information is well delivered to the source-AGW 105 or whether there is additional information requested. This step may be omitted. . In step 217, the packet is transmitted through the interface established between the source-AGW 105 and the target-AGW 106 in steps 213 to 215.

In step 219, the AT-110 transmits a Dynamic Host Configuration Protocol (DHCP Discover with rapid Commit) message with an option to request a response when the AT 110 uses IPv4 to transmit the target-AN 122 and the target-AGW (106). In this case, an interface has been set, and an interface between the target-AGW 106 and the HA 102 needs to be set.

In step 221, the Target-AGW 106 transmits a proxy binding update (PBU) or proxy routing request (PRRQ) message to the HA 102, which is an example of a proxy registration request message for registering the UE's mobile state on behalf of the UE. send. Whether to send PBU or PRRQ depends on which of IPv4 and IPv6 is used in the network as the interface between the Target-AGW 106 and the HA 102. That is, PRRQ is transmitted when using IPv4 to support PMIPv4 on the network, and PBU is transmitted when using IPv6 to support PMIPv6 on the network.

In step 223, the target-AGW 106 receives a proxy registration response message from the HA 102 in response to the proxy registration request message. At this time, in case of IPv6, a PBinding (Proxy binding acknowledgement) message is received, and in case of IPv4, a PRRP (Proxy routing response) message is received.

In step 225, if the AT 110 is an IPv4 terminal, the Target-AGW 106 having the fast processing option may use the Home of Address, which was used in the Source-AGW 105 in the DHCP Acknowledgement with rapid commit. By including the HoA) to send to the AT (110) to support a seamless service even when the handoff of the terminal. After the handoff procedure is completed, in step 227, data communication through the target-AN 122, the target-AGW 106, and the HA 102 is enabled using the interface set through the steps 203 to 225.

Next, an information delivery method for supporting a mobility management procedure of a terminal of the present invention will be described.

The overall format of the information transfer message is shown in Table 1. Message headers are used to transfer information on the User Datagram Protocol (UDP) header, and the information required for handoff is delivered through message options.

In the following description, each message occupies a length in bytes and specifies a bit if necessary.

UDP Header (8 bytes) Message Header Message Option (variable)

The header format of the information delivery message is a message type field for indicating the message type such as HO_Request, HO_Response, HO_Ack, length field for indicating the length of the message, and necessary information as a flag value as shown in [Table 2]. Contains a flag field to give. In particular, the flag field includes an R bit for resetting the next transaction ID, and an F bit for indicating that it is the last fragment. The apparatus further includes an AT's ID field including an ID of the terminal, a Transaction ID for identifying a transaction, and a fragment ID field for distinguishing a fragment. The reserved field is reserved for future use.

The message option to be added takes the form of TLV (type, length, value). In the embodiment of the present invention, only the GRE key, NAI (Network Access Identifier), PMIPv4 mobility state, PMIPv6 Mobility state, etc. are mentioned as message options, but LCP state, IPv4CP state, IPv6CP state, Information such as a CCP state, a header compression state, a QoS state, a TFTv4 state, a TFTv6 state, and a vendor specific state may also need to be transmitted. Such information will not be specifically described in the present invention.

The GRE Key option includes GRE key and life time information of the key as shown in [Table 3] below.

Type (2bytes) Length (2bytes) GRE key (4 bytes) lifetime (2bytes) reserved (2bytes)

The NAI option includes NAI information as shown in [Table 4] below, which can be used together as key information regarding mobility management and authentication for PMIP.

Type (2bytes) Length (2bytes) NAI (max: 70 bytes) reserved (2bytes)

To manage PMIP mobility, PMIPv4 mobility options as shown in [Table 5] and PMIPv6 mobility options as shown in [Table 6] can be used.

In the PMIPv4 mobility option, there is a HoA field indicating a home address of a terminal and an AGW Addr-serving field indicating an address of a proxy CoA in the Source-AGW 105, that is, an address of the Source-AGW 105. There is a field indicating a Proxy CoA in the AGW 106, a field for transmitting a PMIP related key, and a lifetime field for a tunnel lifetime. Proxy CoA (care of address) in the Source AGW or Target AGW means that the gateway requests registration on behalf of the UE in PMIP. Thus, the gateway address is registered in the database of the binding cache for the UE. Name the target gateway as Proxy CoA. On the other hand, there is a PMIP relate key field that indicates a PMIP-related key. For example, this field carries a root key used to generate a PMN-AN-HA key, which is a key between an AGW and eBS such as PMN-AN-RK. Can be.

Type (2bytes) Length (2bytes) HoA (4 bytes) Home Agent (4 bytes) Source AGW Addr or Proxy CoA in serving AGW (4 bytes) Target AGW Addr or Proxy CoA in Target AGW (4 bytes) PMIP related Key (16bytes: TBD) lifetime (2bytes) reserved (2bytes)

A special field to manage PMIPv6 mobility is a home network prefix field, which is a field for delivering a home network prefix for generating an address of a terminal.

Type (2bytes) Length (2bytes) HoA (16 bytes) Home Network Prefix (max: less than 16bytes) Home Agent (16bytes) Proxy CoA-serving (16bytes) Proxy CoA-Target (16bytes) PMIP related Key (16bytes: TBD) lifetime (2bytes) reserved (2bytes)

In addition, as shown in [Table 7], there is an AAA attributes field for indicating the authentication status of the terminal.

Type (2bytes) Length (2bytes) AAA attributes and VSAs (variables)

In addition, information may be requested while making a handoff request (HO_Request) using a 'state request option' as shown in [Table 8], and information may be requested through a HO_ACK message. The Requested state field is used to specify the state required for information delivery.

Type (2bytes) Length (2bytes) Request States (2 bytes) Reserved (2 bytes)

In addition, as shown in [Table 9], options such as status code can be managed for error status management, and a status code field for checking error status is included.

Type (2bytes) Length (2bytes) Status Code (4 bytes)

In addition, as shown in Table 10, the authenticator option can be used to ensure the integrity of the delivered message. The authenticator option may include a security parameter index (SPI) including a security parameter index value and an added authenticator field for data integrity.

Type (2bytes) Length (2bytes) SPI (4 bytes: TBD) Authenticator (Variable: TBD)

3 is a message flow diagram illustrating a mobility management procedure of a terminal in a PMIPv6 environment according to an embodiment of the present invention. In FIG. 3, the AT 110 handoffs from the NW1 141 to the NW2 143 in FIG. 1, but in an environment using a similar mechanism, that is, an environment in which an interface for proxy MIP and context transfer is supported. The basic idea of the present invention can be applied.

Referring to FIG. 3, in step 301, the AT 110, the Source-AN 121, the Source-AGW 1 105, and the HA 102 are involved to perform communication. In the case of UMB, data communication is performed between the Source-AGW 105 and the Source-AN 121 through a GRE tunnel.

In step 303, the AT 110 requests the Target-SRNC 132 to include the Target-AN 122 in the active set, and the Target-SRNC 132 obtains session information from the Source-SRNC 131 ( fetch).

In step 305, the AT 110 performs L2 fast switching to the target AN 122, and data transmission continues through the L2TP tunnel between the target-AN 122 and the source-AN 121. Thereafter, the Target-SRNC 132 transmits session information to the Target-AN 122.

In step 307, the PRRQ is sent from the Target-AN 122 to the Target-AGW 106 for the signaling interface between the Target-AN 122 and the Target-AGW 106, and the Target-AN 122 sends the Target-AGW. By receiving PRRP from 106, information necessary for data communication thereafter, for example, a GRE key and the like, are set.

In step 309, the Target-ANNC 122 notifies the Target-SRNC 132 or the Source-AN 121 of the address and the GRE key of the Target-AGW 106, and not the Target-SRNC 132 or the Source. The -AN 121 sends an acknowledgment message to the Target-AN 122.

In step 311, the Target-AGW 106 transmits a HO_Request message to the Source-AGW 105. In this case, the context information may be requested or the GRE key to be used for data communication with the AN may be included in the handoff request message. The format of the message used in the handoff request message and the form of the options follow Tables 1 to 10 above.

In step 313, the Source-AGW 105 may send a Handoff Response (HO_Response) message including context transfer to the Target-AGW 106 in response to the handoff request message. The format of the message used in the handoff response message and the form of the option follow Tables 1 to 10 above. The target-AGW 106 may send a handoff acknowledgment (HO_Ack) message according to whether the information is well delivered to the source-AGW 105 or whether there is additional information requested in step 315, and this step may be omitted. . In step 317, the packet is transmitted through the interface established between the source-AGW 105 and the target-AGW 106 in steps 311 to 313 or 315.

In step 319, when the AT 110 uses IPv6, a route solicitation message is sent to the AGW 106 to establish an interface between the Target-AN 122 and the Target-AGW 106, and the Target-AGW. At 106 it is informed that an interface between HA 102 needs to be established.

In step 321, the Target-AGW 106 transmits a PBU or PRRQ message, which is an example of a proxy registration request message, to the HA 102 in order to manage mobility of the UE. Which of the PBU and PRRQ is sent depends on whether the operator's network uses IPv4 or IPv6 as the interface between the Target-AGW 106 and the HA 102. In other words, if PMIPv4 is supported as a network mobility support mechanism on a network using IPv4, PRRQ is transmitted, and PBU is transmitted when PMIPv6 is supported as a network mobility support mechanism on a network using IPv6.

In step 323, the Target-AGW 106 receives a proxy registration response message from the HA 102 in response to the proxy registration request message. At this time, in case of IPv6, PBAck is received and in case of IPv4, PRRP is received.

 In step 325, if the AT 110 is an IPv6 terminal, the AT 110 includes the home network prefix information in the Router Advertisement message from the Target-AGW 106 to the AT 110, thereby transmitting the AT 110. By generating an address, such as the home address (HoA) used in the Source-AGW 105 to support a seamless service even when the terminal handoff.

When the handoff procedure is completed, in step 327, data communication through the target-AN 122, the target-AGW 106, and the HA 102 may be performed using the interface set through steps 303 to 325.

4 is a flowchart illustrating the operation of a target access gateway according to an exemplary embodiment of the present invention. In FIG. 4, a target access gateway means an access gateway of a network to which a terminal is to move.

Referring to FIG. 4, the Target-AGW 106 receives a PRRQ message for establishing a PMIP interface between the Target-AN 122 and the Target-AGW 106 from the Target-AN 122 in step 401. The PRRP message is sent to the target-AN 122 in response to the PRRQ message.

In step 403, the target-AGW 106 sends a handoff request (HO_request) message to the source-AGW 105, and in step 405, the handoff response (HO_response) message from the source-AGW 105 is associated with the handoff. Context transfer. In step 407, the Target-AGW 106 requests additional information or sends a handoff acknowledgment (HO_Ack) message in response to the information transfer. In step 409, the Target-AGW 106 sends a message between the Source-AGW 105 and the Target-AGW 106. Packets are delivered through the configured interface.

If the interface is active between the target-AN 122 and the target-AGW 106 and the tunnel is established, the process of step 411 is performed according to whether the AT 110 uses IPv4 or IPv6 in step 411. Decide In case of AT 110 using IPv4, the process branches to step 421, and the Target-AGW 106 receives a DHCP Discover with Rapid commit message with the option of requesting a quick reply sent by the AT 110. It is noted that an interface has been established between the AN 122 and the Target-AGW 106 and that an interface between the HA 102 at the Target-AGW 106 needs to be established.

In step 423, the AGW 106 transmits a PBU or PRRQ message, which is a proxy registration request message, to the HA 102. Whether to send a PBU or PRRQ is determined depending on whether the interface between the Target-AGW 106 and the HA 102 is IPv4 or IPv6. In case of supporting PMIPv4 on the network using IPv4, PRRQ is transmitted. In case of supporting PMIPv6 on the network using IPv6, PBU is transmitted. In step 425, a proxy registration response message, PBAck (for IPv6) or PRRP (for IPv4), is received from the HA 102 in response to the proxy registration request message.

In step 427, if the AT 110 is an IPv4 terminal, the home address used in the Source-AGW 105 in a DHCP Acknowledgment with Rapid Commitment with a fast processing option from the Target-AGW 106 to the AT 110. Sending to (HoA) to support a seamless service even when the terminal handoff. After the handoff procedure is completed, data communication through the Target-AN 122, Target-AGW 106, and HA 102 is enabled in step 429.

On the other hand, in case of the UE using IPv6, the process branches from step 411 to step 441. When the target-AGW 106 receives a route solicitation message sent from the AT 110, the target-AN 122 and the target-AGW are received. It will be appreciated that a tunnel has been established between the 106 and the interface between the AGW 106 and the HA 102 should be established.

In step 443, the Target-AGW 106 transmits a PBU or PRRQ message, which is a proxy registration request message, to the HA 102 on behalf of the UE for mobility management of the UE. Whether to send a PBU or PRRQ is determined by whether the Target-AGW 106 uses IPv4 or IPv6 as the interface between the HA 102. In case of supporting PMIPv4 on the network using IPv4, PRRQ is transmitted. In case of supporting PMIPv6 on the network using IPv6, PBU is transmitted.

In step 445, the HA 102 receives a PBAck (IPv6) or a PRRP (IPv4), which is a proxy registration response message, in response to the proxy registration request message.

If the AT 110 is an IPv6 terminal in step 447, the Target-AGW 106 transmits the AT-110 by including a home network prefix (HN-Prefix) in a route advertisement message to the AT 110. By generating an address such as a home address (HoA) used in the Source-AGW 105, the service is seamless even when the terminal is handed off. When the handoff procedure is completed, data communication through the target-AN 122, the target-AGW 106, and the HA 102 is enabled in step 449.
In addition, although not shown, it is assumed that the target-AGW includes an interface setting unit, a control unit, a transmitter, and a receiver. In this case, step 401 is performed by the interface setting unit. Step 411 is performed by the controller.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

1 is a block diagram showing a mobile communication system environment and overall operation according to an embodiment of the present invention.

2 is a message flow diagram illustrating a mobility management procedure of a terminal in a PMIPv4 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 PMIPv6 environment according to an embodiment of the present invention.

4 is a flowchart illustrating an operation of a target access gateway according to an embodiment of the present invention.

Claims (12)

In the method for managing the mobility of a terminal using a proxy mobile Internet protocol in a mobile communication system, Performing a proxy registration procedure for setting a proxy mobile internet protocol interface with a target base station to be handed off by the target access gateway as the terminal hands off from the source network to the target network; A handoff request message is transmitted from the target access gateway to a source access gateway, and a response message to the handoff request message including handoff related information including mobility information and a home address of a terminal used by the source access gateway is sent. Receiving process, Transmitting and receiving data through an interface established between the source access gateway and the target access gateway; Transmitting a message for requesting a proxy registration to a home agent on behalf of the terminal; Receiving a response message for the proxy registration request from the home agent; Mobility management method comprising the step of transmitting and receiving data with the target base station and the home agent. The method of claim 1, The handoff related information may further include at least one of a gernic routing encapsulation (GRE), a network access ID, mobility information of the proxy mobile internet protocol, authentication status information of the terminal, a security parameter index, and an authentication value. How to manage mobility. The method of claim 1, Dynamic Host Configuration Protocol Discover (DHCP) Discovery message with a Rapid Commit option from the terminal when the interface between the target access gateway and the home agent uses internet protocol version 4 Mobility management method characterized in that for receiving. The method of claim 1, And receiving a route solicitation message from the terminal when the interface between the target access gateway and the home agent uses internet protocol version 6. The method of claim 1, The message for the proxy registration request, When the interface between the target access gateway and the home agent uses Internet Protocol Version 4, it is a Proxy Registration Request (PRRQ) message, And a proxy binding update (PBU) message when the interface between the target access gateway and the home agent uses internet protocol version 6. The method of claim 1, The response message to the proxy registration request, When the interface between the target access gateway and the home agent uses Internet Protocol version 6, it is a Proxy Binding Acknowledge (PBAck) message, And a proxy registration response (PRRP) message when the interface between the target access gateway and the home agent uses internet protocol version 4. A target access gateway device for managing mobility of a terminal using a proxy mobile internet protocol in a mobile communication system, As the terminal handoffs from the source network to the target network, an interface setting unit for performing a proxy registration procedure for setting the target mobile station and the proxy mobile Internet protocol interface to be handed off, Send a handoff request message from the target access gateway to a source access gateway, transmit data through an interface established between the source access gateway and the target access gateway, and request a proxy registration request to a home agent on behalf of the terminal A transmitter for transmitting a message and transmitting data to the target base station and the home agent; Receiving a response message for the handoff request message including handoff related information including mobility information and a home address of a terminal used in the source access gateway, and establishing an interface between the source access gateway and the target access gateway. And a receiving unit for receiving data from the home agent, receiving a response message for the proxy registration request from the home agent, and receiving data from the target base station and the home agent. The method of claim 7, wherein The handoff related information may further include at least one of a gernic routing encapsulation (GRE), a network access ID, mobility information of the proxy mobile internet protocol, authentication status information of the terminal, a security parameter index, and an authentication value. A target access gateway device. The method of claim 7, wherein And a controller configured to determine whether an interface between the target access gateway and the home agent uses an internet protocol version 4 or an internet protocol version 6, When the controller determines that the Internet Protocol version 4 is used, the receiver receives a Dynamic Host Configuration Protocol Discover (DHCP) discovery message with a Rapid Commit option from the terminal. Target access gateway device characterized in that. The method of claim 7, wherein And a controller configured to determine whether an interface between the target access gateway and the home agent uses an internet protocol version 4 or an internet protocol version 6, And the receiver receives a route solicitation message from the terminal when the controller determines that the Internet Protocol version 6 is used. The method of claim 7, wherein And a controller configured to determine whether an interface between the target access gateway and the home agent uses an internet protocol version 4 or an internet protocol version 6, When the controller determines that the Internet Protocol version 4 is used, the message for the proxy registration request is a Proxy Registration Request (PRRQ) message, And when the controller determines that the Internet Protocol version 6 is used, the message for requesting a proxy registration is a Proxy Binging Update (PBU) message. The method of claim 7, wherein And a controller configured to determine whether an interface between the target access gateway and the home agent uses an internet protocol version 4 or an internet protocol version 6, When the controller determines that the Internet Protocol version 6 is used, the response message to the proxy registration request is a Proxy Binding Acknowledge (PBAck) message, And when the controller determines that the Internet Protocol version 4 is used, the response message to the proxy registration request is a Proxy Registration Response (PRRP) message.

Images