KR20080099991A - Method for managing mobility of ms using proxy mobile ip in mobile telecommunication system and therefor system - Google Patents

Abstract

A method for managing the mobility of a mobile terminal by using the proxy mobile Internet protocol and a system therefor are provided to safely and quickly process data communication by performing the authentication related to IP call processing in a PMP process. In a mobile communication network, a method for managing the mobility of a mobile station by using the proxy mobile internet protocol(PMIP) includes the following steps. The access authentication between the MS(Mobile Station) and an AAA(Authentication, Authorization and Accounting) server(101) is performed. An AG(Access Gate) sends a PBU(Proxy Binding Update) message of the MS to an HA(Home Agent) when an address assignment requesting message is received from the MS. A PBA(Proxy Binding Acknowledge) message is received from the HA in response to the PBU message.

Description

Method and system for managing mobility of mobile terminal using proxy mobile internet protocol in mobile communication system {METHOD FOR MANAGING MOBILITY OF MS USING PROXY MOBILE IP IN MOBILE TELECOMMUNICATION SYSTEM AND THEREFOR SYSTEM}

1 is a block diagram showing a mobile communication network environment according to a preferred embodiment of the present invention.

2 is a message flow diagram illustrating a connection and authentication procedure according to a preferred embodiment of the present invention.

3 is a message flow diagram illustrating an access and authentication procedure according to another embodiment of the present invention.

4 is a message flow diagram illustrating another example of an access and authentication procedure according to another embodiment of the present invention.

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

The present invention relates to a mobile communication system, and more particularly, to a method and system for managing mobility of a mobile terminal using proxy mobile IP for a mobile terminal using a simple internet protocol (IP).

In a mobile communication system, a base station (hereinafter referred to as a BS) manages a large number of radio related resources, and a packet data serving node (hereinafter referred to as a separate entity of a core network) In the PDSN), a procedure related to communication of packet data is performed.

Conventional mobile communication systems provide mobility for mobile terminals using simple IP or mobile IP in a mobile environment. However, the methods of mobile IP, namely Client Mobile IPv6 (hereinafter referred to as CMIPv6) and Client Mobile IP version 4 (hereinafter referred to as CMIPv4), are suitable for systems that want to send more data at higher speeds. Not As one of the solutions for this, Proxy Mobile IP (hereinafter referred to as PMIP) has been discussed.

The conventional CMIPv6 requires a lot of time in connection and call processing. In other words, although mobility is provided in comparison with simple IP, time delay occurs due to the time required for call processing and database management for mobility support in connection and call processing. In addition, in the conventional system, the authentication and security processing were supplemented to solve security weaknesses occurring in CMIPv6. As a result, an additional time delay occurred.

The present invention provides fast mobility support and more secure and efficient communication method and system using proxy mobile IP.

The present invention provides a method and system for efficiently performing proxy mobile IP authentication and call setup of a simple IP terminal in an initial call setup process of a mobile communication system.

The present invention provides a method and system for performing authentication and security of IP use using EAP (Extensible Authentication Protocol) in a mobile communication network.

According to a preferred embodiment of the present invention, in a method for managing mobility of a mobile terminal using a proxy mobile internet protocol in a mobile communication network,

Performing connection authentication between a mobile terminal (MS) and a billing and authentication (AAA) server;

When the address assignment request message is received from the mobile terminal, the access gateway AG acts on behalf of the mobile terminal to update the proxy binding including information related to the mobile agent authentication confirmation and mobility management. (PBU) sending messages and

And receiving a proxy binding response (PBA) message from the HA indicating that the related information is verified in response to the PBU message.

In a preferred embodiment of the present invention, in a system for managing mobility of a mobile terminal using a proxy mobile internet protocol in a mobile communication network,

Mobile terminal (MS),

A billing and authentication (AAA) server,

Home agent (HA),

When connection authentication is performed between the mobile terminal and the AAA server, and an address assignment request message is received from the mobile terminal, the mobile station provides relevant information for authentication confirmation and mobility management of the mobile terminal on behalf of the mobile terminal. An Access Gateway (AG) for sending a Proxy Binding Update (PBU) message, the Proxy Binding Response (PBA) message indicating that the relevant information has been verified in response to the PBU message. .

Hereinafter, with reference to the accompanying drawings will be described in detail the operating principle of the preferred embodiment of the present invention. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. In addition, terms to be described below are defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the contents throughout the specification.

The subject matter of the present invention described below is to provide the use and security of proxy mobile IP for mobile communication networks. In the following description, the UMB system based on 3GPP2 or Evolved Packet Core (EPC) which is an evolved mobile communication system of 3GPP or an evolved system of WiMAX will be used. However, the Internet communication method for a mobile communication network, which is a basic object of the present invention, is applicable to other mobile communication systems having a similar technical background and channel form with a slight modification without departing from the scope of the present invention. It will be possible in the judgment of a person skilled in the art of the invention.

 1 is a block diagram illustrating a mobile communication network environment according to a preferred embodiment of the present invention. Here, as an example, the network structure of the 3GPP2 UMB system is illustrated.

Referring to FIG. 1, a base station (BS) 107, 108, 109 establishes a wireless connection and communicates with a mobile station (hereinafter referred to as MS) 110 located in a cell serving each service area. Perform. Signaling Radio Network Controller (SRNC) 105, 106 controls communication of MS 110 via BS 107, 108, 109 when MS 110 is in idle mode. On the other hand, the MS 110 is a mobile node (hereinafter referred to as MN) that connects to a packet data network such as the Internet through an access gateway 103 (104). The main network entity of the packet data network is shown here as a Home Agent (hereinafter referred to as HA) 102 and an Authentication, Authorization and Accounting (hereinafter referred to as AAA) server 101. SRNC 105 If there is an authenticator for device authentication at 106, the SRNC 105 and 106 are used for device authentication through an interface with the AAA server 101.

An interface for managing mobility of the mobile terminal 110 in idle state exists between the BSs 107 to 109 and the SRNC 105 and 106 and between the AG 103 and 104 and the SRNC 105 and 106. There is a data path between 104 and BSs 107 ˜ 109. For authentication of the terminal 110, the SRNC (105, 106) has an authenticator (not shown) for device authentication, and the AG (103, 104) has an authenticator (not shown) for user authentication. It is located. In other cases, a structure in which the device authentication authentication unit and the user authentication unit belong to both the SRNCs 105 and 106 or both of the AG 103 and 104 may be possible.

The MS 110 supports only IPv6, not CMIPv6, and receives an IP address through the DHCPv6 server 111 or generates an IP address through an IPv6 address auto configuration process. If the DHCPv6 server 111 exists as a separate entity, the AG 103 or 104 performs the same role as the DHCPv6 repeater. However, if the DHCPv6 server 111 does not exist separately or if the MS 110 does not use automatic generation of IPv6 addresses, the IP address of the MS 110 may be assigned through the HA 102.

2 (consisting of FIGS. 2A and 2B) is a message flow diagram illustrating a connection and authentication procedure according to a preferred embodiment of the present invention.

Referring to FIG. 2, in step 201, the MS and the AAA server perform access authentication. Various procedures and various entities (eg, AG, BS, SRNC, etc.) are involved in the authentication of a connection, and thus the detailed description thereof will be omitted. After the access authentication is made, the MS and the AAA server generate the MN-HA key for mutual authentication of the MS and HA in steps 203a and 203b, and the MS and AG also MN-MAG (Mobile Access Gateway) in steps 205a and 205b. Will generate a key. Meanwhile, in steps 207a and 207b, the AG and the HA generate a MAG-LMA (Localized Mobility Anchor) key for mutual authentication of the AG and the HA. MAG means AG and LMA means HA. Since a specific key generation is not specifically related to the present invention, a detailed description thereof will be omitted. The keys are intended to be used in subsequent call processing to authenticate each other between the entities. That is, it is used to verify the MN-MAG Authentication Extension (hereinafter referred to as AE), MN-HA AE, or MAG-LMA AE. Also, the keys may be generated during the access authentication of step 201.

In step 209, the MS sends a DHCP Solicit message to the AG to request an appropriate address assignment server, and in step 211, the AG operates as a DHCPv6 repeater, and the DHCP relays a DHCP relay-forward message to the DHCPv6 server. The billing message will be sent. In step 213, the DHCPv6 server transmits a DHCP advertisement message to the AG by including a DHCP Relay-Reply message corresponding to the DHCP relay transfer message. Then, in step 215, the AG transmits the DHCP advertisement message to the MS so that the MS, which is a DHCP client, transmits a DHCP request message to a suitable DHCP server.

By the DHCP advertisement message, in step 217, the MS transmits a DHCP request message for requesting the assignment of the IP address to the AG. In this case, the MS sends MN-MAG AE and MN-HA AE for mutual authentication. A network access identifier (hereinafter referred to as NAI) is also transmitted for identification of the MS. The MN-HA AE and MN-MAG AE transmitted here are values generated by the MS using the MN-MAG key and the MN-HA key. In step 219, the AG transmits the DHCP request message to the DHCPv6 server by including the DHCP request message, and in step 221, the DHCPv6 server responds to the DHCP relay message by the MS. : Encapsulates a DHCP reply message (hereinafter referred to as HoA) and includes a DHCP relay response message together with the NAI. The AG verifies the MN-MAG AE received in step 217 with the MN-MAG key generated in step 205b.

After successfully verifying the MN-MAG AE, step 225 may be performed simultaneously with steps 227 to 237 or after steps 227 to 237. In step 225, the AG sends the DHCP response message to the MS. The DHCP response message includes the IP address of the MS allocated from the DHCPv6 server, that is, HoA. Meanwhile, the AG sends a proxy binding update (hereinafter referred to as PBU) message to the HA on behalf of the MS in step 227. The PBU message requests the AG to register the MS with the HA on behalf of the MS. Unlike the Binding Update (BU) message used in ordinary mobile IPv6, the MAG-LMA AE, MN-HA AE, NAI, HoA is used for the AG to manage the mobile management of the mobile terminal. , At least one of an AG address and an MS's Home Network Prefix (hereinafter referred to as HN prefix). The MAG-LMA AE among the AEs transmitted here is generated by the AG using, for example, a MAG-LMA key.

In step 229, the HA sends an access request message to the AAA server, indicating that there is an access request on behalf of the MS from the AG. The access request message means an AAA access request message such as an access request message according to a RADIUS protocol or an access request message according to a diameter AAA protocol. Meanwhile, the access request message includes at least one of an NAI, an HN prefix, and an HA address in order to be used as database information for a future MS.

In step 231, an access accept message according to the access request message is transmitted from the AAA server to the HA. The access acknowledgment message may mean an access acknowledgment message of a RADIUS protocol or an access answer message of a diameter AAA protocol. The access approval message includes the MN-HA key and the MAG-LMA key generated in step 201 or steps 203b and 207b. In step 233 and step 235, the HA uses the keys received in step 231. The MN-HA AE and MAG-LMA AE received in step 227 are verified. After the verification is successful, a Proxy Binding Acknowledgment (hereinafter referred to as PBA) message indicating that the registration request sent by the AG on behalf of the MS on behalf of the MS was successfully received in step 237 is transmitted from the HA to the AG.

3 (composed of FIGS. 3A and 3B) is a message flow diagram illustrating an access and authentication procedure according to another embodiment of the present invention. Here, the operation when HA assigns an IP address for the MS is illustrated.

Referring to FIG. 3, in step 301, the MS and the AAA server perform access authentication. Various procedures and various entities (eg, AG, BS, SRNC, etc.) are involved in the authentication of a connection, and thus the detailed description thereof will be omitted. After the access authentication is made, the MS and the AAA server generate the MN-HA key in steps 303a and 303b, and the MS and AG generate the MN-MAG key in steps 305a and 305b, and the AG and HA in steps 307a and 307b. Generates a MAG-LMA key. The keys are intended to be used in subsequent call processing to authenticate each other between the entities. In addition, the keys may be generated during the access authentication of step 201.

In step 309, the MS sends a DHCP request message to the AG requesting to find a suitable address assignment server. In step 311, the AG sends a DHCP advertisement message to the MS to inform the DHCP client MS of the appropriate DHCP server. In the case of FIG. 3, the AG performs the minimum function of the DHCP server, and the HA operates as the address assignment server of the MS.

In step 313, the MS transmits a DHCP request message for requesting the assignment of the IP address to the AG, wherein the MN-MAG generated using the MN-MAG key and the MN-HA key for mutual authentication of the MS and the AG. Send AE and MN-HA AE and send NAI together for identification of MS. In step 315, the AG verifies the MN-MAG AE received in step 313 using the MN-MAG key generated in step 305b.

After successfully verifying the MN-MAG AE, in step 317, the AG transmits a PBU message to the HA for requesting registration of the MS's movement status to the HA on behalf of the MS, and the PBU message transfers the mobility management of the MS to the HA. To include at least one of the address of the MAG-LMA AE, MN-HA AE, NAI, AG, HN prefix of the MS. Here, MAG-LMA AEs transmitted from the AEs are generated by the AG using the MAG-LMA key. Unlike in step 227, the HoA of the MS is not included in the PBU message.

In step 319, after receiving the PBU message, the HA sends an access request message to the AAA server, indicating that there is an access request on behalf of the MS from the AG. The access request message means an AAA access request message, such as an access request message according to a RADIUS protocol or an access request message according to a diameter AAA protocol. Meanwhile, the access request message includes an NAI, an HN prefix, and an HA address in order to be used as database information for a future MS.

In step 321, an access acknowledgment message according to the access request message is transmitted from the AAA server to the HA. The access grant message means an access grant message of the RADIUS protocol or an access response message of the Diameter AAA protocol. Meanwhile, the access approval message includes the MN-HA key and the MAG-LMA key generated in steps 303b and 307b. In steps 323 and 325, the HA verifies the MN-HA AE and the MAG-LMA AE received in step 317 using the keys received in step 321.

After the successful verification, in step 327, a PBA message indicating that the MS was successfully registered with the HA is transmitted from the HA to the AG, and the HoA, which is the initial address of the MS assigned to the MS by the HA, is included in the PBA message. In step 329, the AG sends a DHCP response message corresponding to the DHCP request message to the MS. The DHCP response message includes the HoA, which is the address of the MS allocated from the HA.

4 (composed of FIGS. 4A and 4B) is a message flow diagram illustrating an access and authentication procedure according to another embodiment of the present invention. Here, the operation in the case where automatic address generation is performed by the MS is shown.

Referring to FIG. 4, in step 401, the MS and the AAA server perform connection authentication. Various procedures and various entities (eg, AG, BS, SRNC, etc.) are involved in the authentication of a connection, and thus the detailed description thereof will be omitted. After the access authentication is made, the MS and the AAA server generate the MN-HA key in steps 403a and 403b, the MS and AG generate the MN-MAG key in steps 405a and 405b, and the AG and HA in steps 407a and 407b. Generates a MAG-LMA key. The keys are intended to be used in subsequent call processing to authenticate each other between the entities. In addition, the keys may be generated during the access authentication of step 201.

Steps 409 to 415 show that the MS performs IPv6 address auto configuration without receiving an IP address from the DHCPv6 server or the HA. In step 409, the MS sends a Router Solicitation message to the AG, wherein the MN-MAG AE and MN-HA AE generated using the MN-MAG key and MN-HA key for mutual authentication are recalled. Send it in a Router Solicitation message. In addition, the NAI for identification of the MS may be transmitted together. In step 411, the AG verifies the MN-MAG AE received in step 409 using the MN-MAG key generated in step 405b. Upon successful verification of the MN-MAG AE, in step 413, the AG sends a Router Advertisement message corresponding to the Router Solicitation message to the MS. The HN prefix is also transmitted to the MS after the Router Advertisement message is sent to the MS. Enable automatic address generation. In step 415, the MS generates an IP address by automatic address generation using the HN prefix included in the router advertisement message.

Thereafter, in step 417, the AG transmits a PBU message to the HA for requesting registration of the MS's mobility status to the HA on behalf of the MS, and the PBU message includes: MAG-LMA AE, At least one of the address of the MN-HA AE, the NAI, the AG, and the HN prefix of the MS. The MAG-LMA AE is generated by the AG using the MAG-LMA key. In step 419, the HA transmits a connection request message to the AAA server after receiving the PBU message. Informs that there is a proxy connection request. The access request message means an AAA access request message, such as an access request message according to a RADIUS protocol or an access request message according to a diameter AAA protocol. Meanwhile, the access request message includes an NAI, an HN prefix, and an HA address in order to be used as database information for a future MS.

In step 421, an access approval message according to the access request message is transmitted from the AAA server to the HA. The access grant message means an access grant message of the RADIUS protocol or an access response message of the Diameter AAA protocol. Meanwhile, the access approval message includes the MN-HA key and the MAG-LMA key generated in steps 403b and 407b. In steps 423 and 425, the HA verifies the MN-HA AE and the MAG-LMA AE received in step 417 using the keys received in step 421. After the verification is completed, a PBA message indicating that the MS successfully registered with the HA in step 427 is transmitted from the HA to the AG.

5 (consisting of FIGS. 5A and 5B) is a flowchart illustrating the operation of an access gateway according to a preferred embodiment of the present invention.

Referring to FIG. 5, in step 501, access authentication is performed. The access authentication includes device authentication and user authentication. The AG generates a MN-MAG key necessary for verification of the MN-MAG AE in step 503, and generates a MAG-LMA key for generation of the MAG-LMA AE in step 505. In step 507, the process proceeds to step 509 or 541 depending on whether the network of the mobile communication system to which the MS belongs uses a DHCPv6 server. If a DHCPv6 server is used, the process proceeds to step 511 or 531 depending on whether the AG operates as a DHCPv6 repeater in step 509.

If a separate DHCPv6 server is used in the network and the AG has a function as a DHCPv6 repeater, the AG receives a DHCP billing message from the MS in step 511 and forwards the DHCP billing message to the DHCPv6 server including the DHCP billing message in the DHCP relaying message in step 513. do. When receiving the DHCP relay response message including the DHCP advertisement message in response to the DHCP relay transfer message from the DHCPv6 server in step 515, the AG sends the DHCP advertisement message to the MS in step 517, the appropriate DHCP server in the DHCPv6 process Delivers an advertisement message to a DHCP client.

If a DHCP request message including MN-MAG AE, MN-HA AE, and NAI is received from the MS in step 519, in step 521, the AG transmits the DHCP request message to the DHCPv6 server through a DHCP relay delivery message. Receives a DHCP response message and a DHCP relay response message including NAI from a DHCPv6 server. Here, the DHCP response message includes the HoA, which is the IP address of the MS assigned by the DHCPv6 server.

After step 523, the AG performs verification on whether the MN-MAG AE is suitable in step 551. This verification uses the MN-MAG key of the AG to check the MN-MAG AE transmitted from the MS in step 519. By verification. After the verification of the MN-MAG AE is completed, in step 553a, the AG sends a DHCP response message including the HoA to the MS. The HoA is assigned to the MS by a DHCPv6 server. After transmitting the DHCP response message to the MS, in step 561, the AG sends a PBU message to the HA to request registration on behalf of the MS about the MS's movement situation, and in step 563, receives the PBA message from the HA to the HA. Complete the registration.

On the other hand, if a DHCPv6 server is used on the network, but the AG does not act as a DHCPv6 repeater, then the AG will function as a minimal DHCPv6 server. Therefore, in step 531, the AG receives a DHCP request message from the MS, and in step 533, the AG sends a DHCP advertisement message to the MS. In step 535, a DHCP request message including MN-MAG AE, MN-HA AE, and NAI is received from the MS.

After the process 535, in step 551, the AG verifies whether the MN-MAG AE is suitable, this verification using the MN-MAG key of the AG, the MN-MAG AE transmitted from the MS in step 535 By verification. After the verification of the MN-MAG AE is completed, in step 561, the AG sends a PBU message to the HA to request registration on behalf of the MS for the MS's movement situation, and in step 563 receives a PBA message from the HA, Complete registration with HA. The PBA message includes the HoA of the MS assigned in the HA, and in step 553b, the HoA assigned in the HA is delivered to the MS in a DHCP response message.

On the other hand, if there is no DHCPv6 server in the network, the UE uses IPv6 automatic address generation. Therefore, in step 541, the AG receives MN-MAG AE, MN-HA AE, NAI, etc. through a router request message from the MS. The MN-MAG AE is verified using the MN-MAG key that it already has. After the verification of the MN-MAG AE is completed, in step 545, the AG sends a Router Advertisement message corresponding to the Router Solicitation message to the MS so that the MS automatically generates an IP address.

After transmitting the Router Advertisement message to the MS, in step 561, the AG sends a PBU message to the HA to request registration on behalf of the MS about the MS's movement situation, and in step 563, receives the PBA message from the HA and sends the message to the HA. Complete the registration and end the operation.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

In the present invention operating as described in detail above, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

The present invention not only solves the problems of the delay in the call setup process when using mobile IP and the time delay caused by the call resetting during terminal movement, but also performs the authentication related to IP call processing in the PMIP process more safely and quickly. Handle data communication.

Claims (10)

A method for managing mobility of a mobile terminal using a proxy mobile internet protocol (PMIP) in a mobile communication network, Performing connection authentication between a mobile terminal (MS) and a billing and authentication (AAA) server; When the address assignment request message is received from the mobile terminal, the access gateway AG transmits a proxy binding update (PBU) message of the mobile terminal to a home agent (HA); And receiving a proxy binding response (PBA) message from the HA in response to the PBU message. The method of claim 1, further comprising: generating, by the mobile terminal and the AAA server, a first key for mutual authentication of the mobile terminal and the HA through the access authentication; The AAA server transferring the first key to the HA; Acquiring, by the AG, first authentication information for authentication confirmation of the mobile terminal from the address assignment request message, and transmitting the first authentication information to the HA through the PBU message; The HA further comprises the step of verifying the first authentication information through the first key. The method of claim 1, further comprising: generating, by the mobile terminal and the AG, a second key for mutual authentication of the mobile terminal and the AG through the access authentication; Obtaining second authentication information for verifying authentication of the mobile terminal from the address assignment request message; The AG further comprises the step of verifying the second authentication information through the second key. The method of claim 1, further comprising: generating, by the AG and the AAA server, a third key for mutual authentication of the AG and the HA through the access authentication; Transmitting, by the AAA server, the third key to the HA; Obtaining, by the HA, third authentication information for authentication verification of the AG from the PBU message, and verifying the third authentication information through the third key. The method of claim 1, wherein the related information is Authentication information generated by a first key for mutual authentication of the mobile terminal and the HA, a third key for mutual authentication of the AG and the HA, a network access identifier (NAI), and an initial IP of the mobile terminal. And at least one of a home address (HoA) which is an address, an address of the AG, and a home network prefix (HN prefix) of the mobile terminal. A system for managing mobility of a mobile terminal using a proxy mobile internet protocol (PMIP) in a mobile communication network, Mobile terminal (MS), A billing and authentication (AAA) server, Home agent (HA), When the mobile terminal and the AAA server perform connection authentication, and when an address allocation request message is received from the mobile terminal, a proxy binding update (PBU) message of the mobile terminal is sent to the HA, and in response to the PBU message, And an Access Gateway (AG) for receiving a Proxy Binding Response (PBA) message from the HA. The method of claim 6, wherein the AAA server generates a first key for mutual authentication of the mobile terminal and the HA through the access authentication, and transfers the first key to the HA. The AG obtains first authentication information for authentication confirmation of the mobile terminal from the address assignment request message, and relays the first authentication information to the HA through the PBU message, The HA, the mobility management system, characterized in that for verifying the first authentication information through the first key. The method of claim 6, wherein the AG, Generate a second key for mutual authentication of the mobile terminal and the AG through the access authentication, obtain second authentication information for authentication verification of the mobile terminal from the address assignment request message, and the second authentication information Verifying through the second key. The apparatus of claim 6, wherein the AAA server generates a third key for mutual authentication of the AG and the HA through the access authentication, and transfers the third key to the HA. The HA acquires third authentication information for authenticating the AG from the PBU message, and verifies the third authentication information with the third key. The method of claim 6, wherein the related information, Authentication information generated by a first key for mutual authentication of the mobile terminal and the HA, a third key for mutual authentication of the AG and the HA, a network access identifier (NAI), and an initial IP of the mobile terminal. And at least one of a home address (HoA) that is an address, an address of the AG, and a home network prefix (HN prefix) of the mobile terminal.

Images