WO2010051697A1

WO2010051697A1 - REGISTRATION METHOD, SYSTEM AND LOCAL MOBILE ANCHOR FOR INTERFACE PREFIX IN PMIPv6

Info

Publication number: WO2010051697A1
Application number: PCT/CN2009/071899
Authority: WO
Inventors: 严为; 荀永生; 夏晋伟; 糜正琨; 王灵矫; 雷振宇
Original assignee: 华为技术有限公司
Priority date: 2008-11-06
Filing date: 2009-05-21
Publication date: 2010-05-14
Also published as: CN101741811A

Abstract

A registration method, system and local mobile anchor for interface prefix in PMIPv6. The method comprises the following steps: an agent binding update message sent by a mobile access gateway is received and an identifier of the interface to be registered is carried in the agent binding update message; a home network prefix which is the same as the registered interface is allocated to the interface to be registered and a binding cache directory is set up for the interface to be registered and the home network prefix is comprised in the binding cache directory; an agent binding acknowledgement message is sent to the mobile access gateway and the home network prefix which is allocated to the interface to be registered is carried in the agent binding acknowledgement message.

Description

Registration method, system and local mobile anchor point of interface prefix in ΡΜΙΡνό This application is submitted to the Chinese Patent Office on November 6, 2008, and the application number is 200810175240. X. The registration method and system of the interface prefix in the invention name is “ΡΜΙΡν6” The priority of the Chinese Patent Application, the entire disclosure of which is incorporated herein by reference. Technical field

The present invention relates to the field of mobile communications, and in particular, to a method, a system for registering interface prefixes in PMIPv6, and a local mobility anchor point.

Background technique

In PMIP6 (Proxy Mobile Internet Protocol version 6, Proxy Mobile Internet Protocol version 6), a MN (Mobile Node) can connect to a PMIPv6 domain through multiple interfaces.

In the prior art, when the MN enters the ΡΜΙΡνό domain, the process of prefix registration with an interface connected to the MN is as follows:

1. The MAG (Mobile Access Gateway) accessing the interface obtains the NAI (Network Access Identifier) of the MN, and performs access authentication on the display.

2. After the access authentication, the MAG sends a PBU (Proxy Binding Update) message to the LMA (Local Mobility Anchor), where the PBU carries the NAI of the MN and the ID of the interface. (Identifiers, identifiers).

3. After receiving the PBU, the LMA establishes a BCE (Binding Cache Entry) for the interface, and the BCE includes a unique HNP (Home Network Prefix) for the interface. The NAI of the MN, the ID of the interface, the address of the MAG, and the like.

The LMA sends a PBA (Proxy Binding Acknowledgement) message to the MAG, and the PBA message carries the HNP assigned to the interface.

5. After receiving the PBA message, the MAG sends an RA to the MN through the interface. Adver ti sement, the router announces that the RA carries the HNP assigned to the interface.

After the receiving the RA, the HNP carried by the RA is obtained, and the MN configures an IP address for the interface according to the HNP.

If the MN switches from one interface to another in the same PMI Pv6 domain, the MAG accessing the new interface sends a PBU message to the LMA, the PBU message carrying a handover indication indicating that the connection is an old connection; the LMA receiving the PBU After the switch is the old one, the LMA allocates the HNP of the old interface to the new interface; updates the BCE created when the old interface is registered, or creates a new BCE, and deletes the BCE of the old interface.

After receiving the HNP of the interface with the destination IP address prefix, the LMA matches the destination IP address prefix of the packet with the HNP of each BCE to find the BCE that contains the HNP of the interface. Then, the corresponding MAG address included in the BCE is obtained, and the text is forwarded to the MAG through the bidirectional tunnel. After receiving the packet, the MAG removes the outer packet header and forwards the packet to the display through the interface.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: The MN configures an IP address for the interface according to the unique HNP assigned to each interface. Therefore, only one IP address prefixed with HNP is used. Other IP addresses prefixed with HNP cannot be used, which is a waste of IP address resources. Summary of the invention

In one aspect, an embodiment of the present invention provides a method for registering an interface prefix in PMIPv6, which saves an IP address resource prefixed by HNP.

In order to achieve the above object, the embodiment of the present invention adopts the following technical solutions:

A method for registering an interface prefix in PMIPv6, including:

Receiving a proxy binding update message sent by the mobile access gateway, where the proxy binding update message carries an identifier of the interface to be registered;

And assigning, to the to-be-registered interface, a home network prefix that is the same as the registered interface, and storing the home network prefix in a binding cache directory created for the to-be-registered interface;

Sending a proxy binding acknowledgement message to the mobile access gateway, where the proxy binding acknowledgement message is carried The home network prefix assigned to the interface to be registered.

In one aspect, an embodiment of the present invention provides a local mobility anchor, which saves an IP address resource prefixed by HNP.

A local mobility anchor, including:

a message receiving unit, configured to receive a proxy binding update message sent by the mobile access gateway, where the proxy binding update message carries an identifier of the interface to be registered;

a directory setting unit, configured to allocate, to the to-be-registered interface, a home network prefix that is the same as the registered interface, and store the home network prefix in a binding cache directory created for the to-be-registered interface;

And a message sending unit, configured to send a proxy binding acknowledgement message to the mobile access gateway, where the proxy binding acknowledgement message carries a home network prefix allocated for the to-be-registered interface.

In one aspect, an embodiment of the present invention provides a registration system for an interface prefix in PMIPv6, which saves an IP address resource prefixed by HNP.

A registration system for interface prefix in PMIPv6, comprising a local mobility anchor and at least one mobile access gateway, wherein the local mobility anchor is connected to at least one mobile access gateway;

The local mobility anchor is configured to receive a proxy binding update message sent by the mobile access gateway, where the proxy binding update message carries an identifier of the interface to be registered, and allocates and registers the interface for the to-be-registered interface. The same home network prefix is stored in the binding cache directory created for the to-be-registered interface, and a proxy binding acknowledgement message is sent to the mobile access gateway; the mobile access gateway is configured to receive A proxy binding acknowledgement message sent by the local mobility anchor. The method for registering the interface prefix in the PMIPv6 and the local mobility anchor provided by the embodiment of the present invention, by assigning the same HNP to different interfaces, the MN connecting the interface configures an IP address for the interface according to the HNP; The problem of wasted resources, in addition, when a heterogeneous network is switched, one session is switched from one interface to another, if the same interface is assigned the same HNP is conducive to business continuity. At the same time, the embodiment of the present invention configures different IP addresses of the same home network prefix for each interface, so that the local mobility anchor can correctly forward the received packet to the corresponding mobile access gateway according to the IP address of each interface, thereby avoiding At the same time, the packet is forwarded to multiple mobile access gateways, which causes waste of resources and network security.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following drawings will be briefly described, and the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in view of the drawings.

1 is a flowchart of a method for registering an interface prefix in PMIPv6 according to an embodiment of the present invention; FIG. 2 is a flowchart of another method for registering an interface prefix in PMIPv6 according to an embodiment of the present invention; FIG. 3 is another PMIPv6 according to an embodiment of the present invention; FIG. 4 is a flowchart of another method for registering an interface prefix in PMIPv6 according to an embodiment of the present invention; FIG. 5 is a schematic structural diagram of a local mobility anchor point according to an embodiment of the present invention;

6 is a schematic structural diagram of another local mobility anchor point according to an embodiment of the present invention;

7 is a schematic structural diagram of another local mobility anchor point according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of another local mobility anchor point according to an embodiment of the present invention; FIG.

FIG. 9 is a schematic structural diagram of a system for registering an interface prefix in PMIPv6 according to an embodiment of the present invention. detailed description

The method and system for registering interface prefixes in the PMIPv6 in the embodiment of the present invention and the local mobility anchor point are described in detail below with reference to the accompanying drawings.

Embodiment 1

The embodiment of the invention provides a method for registering an interface prefix in PMIPv6. As shown in FIG. 1, the method for registering an interface prefix in PMIPv6 according to the embodiment of the present invention includes:

101. The local mobility anchor receives a proxy binding update message sent by the mobile access gateway, where the proxy binding update message carries an identifier of the interface to be registered. Assume that MN1 accesses MAGI through interface 1, and MN2 accesses MAG2 through interface 2, MAG1 and MAG2 access the same LMA, and interface 1 has completed registration on the LMA. During the registration of interface 1, the LMA establishes BCE1 for interface 1. The BCE1 contains the home network prefix P1, the ID of the NAI interface 1, and the MAGI address assigned to interface 1. After the MN2 completes the authentication process on the MAG2 through the interface 2, the MAG 2 sends a PBU message to the LMA; the PBU message carries the ID of the interface 2 and the plastic NAI (NAI 2 ).

102. The local mobility anchor allocates a home network prefix that is the same as the registered interface to the to-be-registered interface, and stores the home network prefix in a binding cache directory created for the to-be-registered interface.

The LMA is determined to be a new connection according to the PBU message sent by the MAG2, and the same home network prefix PI is assigned to the interface 2; the LMA creates the BCE2 for the interface 2, and the BCE2 includes the P1, NAI 2, the ID of the interface 2, and the MAG2 address. Etc. At this time, there are two BCEs corresponding to the same home network prefix P1 in the LMA.

103. The local mobility anchor sends a proxy binding acknowledgement message to the mobile access gateway, where the proxy binding acknowledgement message carries the home network prefix allocated for the to-be-registered interface.

The LMA sends a PBA message to the MAG 2; the PBA message carries the home network prefix P1 assigned to the interface 2.

After receiving the PBA message, the MAG2 sends the RA to the display 2 through the interface 2; the RA carries the home network prefix PI assigned to the interface 2; after receiving the RA, the MN2 obtains the home network prefix PI, and the MN2 configures the IP for the interface 2 according to P1. address.

It should be noted that, although the above example is given, interface 1 and interface 2 can access different MAGs, and can also access one MAG at the same time; interface 1 and interface 2 can be connected to different MNs, or one can be connected at the same time. It should be noted that the present invention does not limit this. In addition, the NAI is used as the user identifier, and the NAI corresponding to the same distinct interface may be the same.

The method for registering an interface prefix in the PMIPv6 provided by the embodiment of the present invention, by assigning the same HNP to different interfaces, the MN connecting the interface configures an IP address for the interface according to the HNP, and the solution is solved. The problem of IP address resources being wasted. At the same time, the embodiment of the present invention configures different IP addresses of the same home network prefix for each interface, so that the local mobility anchor can correctly forward the received packet to the corresponding mobile access gateway according to the IP address of each interface, thereby avoiding At the same time, the packet is forwarded to multiple mobile access gateways, which causes waste of resources and network security.

Embodiment 2

The present invention provides a method for registering an interface prefix in PMIPv6. As shown in FIG. 2, the method for registering an interface prefix in PMIPv6 according to the embodiment of the present invention includes:

201. The interface to be registered accesses the MAG through the access authentication, and the MAG sends a PBU message to the LMA, where the PBU message carries the ID of the interface to be registered.

202. The LMA receives the PBU and accepts the registration, allocates an HNP to the interface, establishes a BCE corresponding to the interface to be registered, and stores the HNP in the BCE.

After receiving the PBU message, the LMA determines that it is a new connection, and allocates an HNP to the to-be-registered interface; the HNP may be a different HNP than other registered interfaces, or may be the same HNP as some registered interfaces. The BCE corresponding to the interface to be registered is set up, and the BCE includes an HNP allocated by the LMA to the interface to be registered, an explicit NAI connected to the interface to be registered, an ID of the interface to be registered, and an MAG address to be accessed by the interface to be registered.

A status identifier may be added to the BCE to identify whether the BCE contains an IP address configured for the interface to be registered. The newly created BCE does not contain the IP address configured for the interface to be registered. The BCE cannot be forwarded according to the BCE. Therefore, the status of the BCE is set to the inactive state.

203. The LMA sends a PBA message to the MAG, where the PBA message carries the HNP allocated to the interface to be registered. The PBA message may also carry the home address identifier, so that the MAG learns that the MAG needs to obtain the interface to be registered according to the home address identifier. IP address. The home address flag can be implemented in various ways. For example, the LMA adds a flag "U" to the PBA message to indicate to the MAG that it wishes to obtain the home address information of the interface to be registered.

204. After receiving the PBA message, the MAG sends the RA through the interface to be registered; and connects to the interface to be registered. After receiving the received RA, the HNP carried by the RA is configured with an IP address for the interface to be registered.

205. The MAG obtains an IP address configured for the interface to be registered.

The MAG can obtain the IP address configured for the interface to be registered through an appropriate mechanism, such as ND (Neighbor Di scovery), DHCP (Dynamic Hosting Protocol), ping mechanism, or other methods. . In the embodiment of the present invention, the MAG obtains the IP address configured for the interface to be registered through the reverse query mechanism, that is, queries the corresponding IP address according to the l ink layer address of the MN.

The MAG sends the PBU message to the LMA again, where the PBU message is the second proxy binding update message, where the PBU message carries the IP address obtained by the MAG for the interface to be registered;

You can use the home network prefix option in the existing PBU message to carry the IP address configured for the interface to be registered. In this case, set the Length of the home network prefix option to 128. You can also define new options in the PBU message. The new option 7 describes the IP address configured for the interface to be registered.

207. After receiving the PBU message, the LMA sets the IP address configured for the interface to be registered into the BCE corresponding to the interface to be registered; and sets the status identifier of the BCE to an active state.

The LMA is configured to insert the IP address configured for the interface to be registered into the BCE corresponding to the interface to be registered according to the PBU message: The HNP of the interface to be registered in the home network prefix entry in the BCE may be changed to the interface to be registered. Configure the IP address. In this case, set the Length of the home network prefix entry to 128. You can also add a home address entry to the BCE to place the IP address configured for the interface to be registered into the home address entry.

The BCE at this time contains the IP address configured for the interface to be registered, and the packet can be forwarded accordingly. Therefore, the status of the BCE is set to the active state (act ive).

After the LMA receives the packet, the LMA determines the BCE that matches the destination address of the packet, and obtains the MAG address recorded in the BCE; forwards the packet to the MAG: If the IP address configured on the interface is placed in the BCE In the home network prefix entry, the LMA determines the unique BCE that matches the destination address of the packet according to the prefix matching principle, and forwards the packet to the MAG recorded in the BCE; In the home address entry in BCE, LMA is based on the longest matching principle. Determining a unique BCE that matches the destination address of the message, and forwarding the message to the MAG recorded in the BCE.

The method for registering an interface prefix in the PMIPv6 provided by the embodiment of the present invention saves the IP address resource prefixed by the HNP, and also inserts the IP address configured for the interface to be registered with the LMA when registering through the LMA. Registering the BCE corresponding to the interface, so that when the LMA forwards the packet, the LMA can obtain a unique BCE according to the IP address matching, and forward the packet to the MAG of the BCE record, so as to avoid forwarding the packet to multiple mobile interfaces at the same time. Resource waste and network security problems caused by gateways further save network resources and ensure data security.

Embodiment 3

The embodiment of the present invention further provides a method for registering an interface prefix in the PMIPv6. As shown in FIG. 3, the method for registering an interface prefix in the PMIPv6 according to the embodiment of the present invention includes:

301. The LMA receives the PBU message sent by the MAG, where the PBU message carries the interface to be registered.

ID;

Each interface is connected to a different MAG, and the MAG initiates the interface registration process.

302. The LMA allocates an HNP to the to-be-registered interface, and stores the HNP in the BCE created for the to-be-registered interface.

The LMA allocates HNPs for each interface and creates corresponding BCEs for each interface. A status identifier can be added to the BCE to identify whether the BCE contains an IP address configured for the registered interface. If the BCE does not contain an IP address configured for the registered interface, set the status of the BCE to the inactive state (pend ing). If the BCE contains an IP address configured for the registered interface, set the status of the BCE to the active state (ac t ve ).

303. The LMA sends a PBA message to the MAG.

The PNP carries the HNP allocated by the LMA to the interface to be registered. After receiving the PBA message sent by the LMA, the MAG sends an RA to the MN. After receiving the RA, the MN connected to each interface configures its own IP address for each interface according to the HNP carried in the RA.

304. The LMA receives the packet, determines a BCE that matches the destination address of the packet, and obtains the The MAG address recorded in the BCE is forwarded to the MAG.

After receiving the packet, the LMA parses the packet header to obtain the destination address of the packet. If the BMA finds a BCE that matches the destination address of the document, it forwards the message to the MAG of the BCE record.

305. When a BCE that does not match the destination address of the text is obtained, determine a BCE that matches the destination address prefix of the ^艮 and the status identifier is inactive.

Assume that interface 1 and interface 2 share the same HNP. BCE1 corresponding to interface 1 does not contain the IP address configured for interface 1, and BCE2 corresponding to interface 2 does not contain the IP address configured for interface 2. Assume that the destination address of the packet received by the LMA is the IP address of interface 1. Therefore, the LMA finds BCE1 and BCE2 that match the destination address prefix of the message and identifies the status as "pending". The LMA caches the message.

306. The LMA acquires the ID of the registered interface recorded in the BCE and the MAG address corresponding to the registered interface, and the LMA sends a network address request message to the MAG, where the network address request message carries the registered The ID of the interface;

The LMA obtains the ID of interface 1 and the MAG1 address recorded in BCE1. The LMA obtains the ID of interface 2 and the MAG2 address recorded in BCE2.

The LMA constructs a network address request message, and sends network address request information to the MAG 1 and the MAG 2 respectively. The network address request information sent to the MAG1 carries the destination address of the packet, the ID of the interface 1, and the NAI of the MN connected to the interface 1. The HNP assigned to the interface 1; the network address request information sent to the MAG 2 carries the destination address of the message, the ID of the interface 2, the NAI of the MN connected to the interface 2, and the HNP assigned to the interface 2. The network address request information is used to request the correspondence between the ID of the interface and the IP address configured for the interface.

307. After receiving the network address request message, the MAG obtains an IP address configured for the registered interface.

After receiving the network address request message, the MAG1 obtains the IP address configured for the interface 1 by using an appropriate mechanism, that is, obtains the correspondence between the ID of the interface 1 and its IP address, for example, the Ping mechanism process, the ND process, the DHCP, and the like. Come to get. MAG2 receives the network address request cancellation After the information is obtained, the corresponding relationship between the ID of the interface 2 and its IP address is obtained in the same manner.

308. The MAG sends a network address response message to the LMA, where the network address response message carries an IP address configured by the MAG for the registered interface.

The MAGI and MAG 2 respectively send a network address response message to the LMA; the network address response message sent by the MAG1 carries the ID of the interface 1, the IP address configured for the interface 1, the NAI of the MN connected to the interface 1, and the HNP allocated to the interface 1; The network address response message sent by the MAG2 carries the ID of the interface 2, the IP address configured for the interface 2, the NAI of the MN connected to the interface 2, and the HNP assigned to the interface 2.

309. The LMA updates, according to the received network address response message, a BCE that matches the destination address prefix of the packet and the status identifier is inactive, and places the IP address configured for the registered interface into the registered The BCE corresponding to the interface sets the status of the BCE to the active state.

The LMA updates the BCE1 according to the received network address response message from MAG1, and sets the IP address configured for interface 1 to BCE1. The HNP of interface 1 in the home network prefix entry in BCE1 can be changed to the IP configured on interface 1. Address, at this time, set the Length of the home network prefix entry to 128; you can also add a home address entry to BCE1 to store the IP address configured for interface 1 in the home address entry. BCE1 at this time contains the IP address configured for interface 1. Therefore, the status ID of BCE1 is changed to "act ive".

In the same way, the LMA puts the IP address configured for interface 2 into BCE2 according to the received network address response message from MAG2. The status identifier of BCE2 is changed to "active".

After the update is complete, the LMA looks for a BCE that matches the destination address of the message. If the IP address configured on the interface is placed in the home network prefix entry in the BCE, the LMA determines the unique BCE that matches the destination address of the source according to the prefix matching principle, and forwards the file to the record in the BCE. If the IP address configured on the interface is placed in the home address entry in the BCE, the LMA determines the unique BCE that matches the destination address of the packet according to the longest match criterion, and forwards the packet to the BCE. Recorded MAG. The LMA uses the foregoing method to find the BCE1 that matches the destination address of the packet, and the LMA forwards the buffered packet to the MAG1 recorded in the BCE1.

The method for registering an interface prefix in PMIPv6 provided by the embodiment of the present invention saves HNP as The IP address resource of the prefix is also determined by the LMA when the LMA receives the packet, and if the BCE matching the destination address of the packet is not obtained, the destination address prefix matches the state and the state is determined. The BCE, which is inactive, indicates that the MAG obtains and returns the IP address configured by the interface recorded in the BCE, and places the BCE corresponding to the interface with the IP address configured for the interface, and the LMA is updated. Then, the BCE that matches the destination address of the packet is re-discovered, and the packet is correctly forwarded to the corresponding MAG, so that when the LMA forwards the packet, the LMA can obtain a unique BCE according to the IP address matching, and the The packet is forwarded to the MAG of the BCE record, which avoids resource waste and network security caused by forwarding the packet to multiple mobile access gateways at the same time, further saving network resources and ensuring data security.

Embodiment 4

The embodiment of the present invention can also provide another method for registering an interface prefix in the PMIPv6 based on the prefix registration method described in the second embodiment. As shown in FIG. 4, the method for registering an interface prefix in the PMIPv6 according to the embodiment of the present invention is Includes:

401 - 407 are the same as steps 201 ~ 207 in the second embodiment.

408. The LMA receives the packet, determines the BCE that matches the destination address of the packet, and obtains the MAG address recorded in the BCE, and forwards the message to the MAG.

409. When a BCE that does not match the destination address of the ciphertext is obtained, determine a BCE that matches the destination address prefix of the 艮且 and the status identifier is inactive.

When the BMA does not obtain the BCE that matches the destination address of the packet, the LMA searches for at least one BCE that matches the destination address prefix of the packet and does not include the IP address configured for the registered interface.

The LMA acquires the ID of the registered interface recorded in the BCE and the MAG address corresponding to the registered interface, and the LMA sends a network address request message to the MAG, where the network address request message carries the registered The ID of the interface;

The network address request message of the LMA is used to request the correspondence between the ID of the registered interface and the IP address configured for the registered interface, where the network address request message carries the destination address of the message. The ID of the registered interface, the explicit NAI connected to the registered interface, and the HNP assigned to the registered interface.

411. After receiving the network address request message, the MAG obtains an IP address configured for the registered interface.

After receiving the network address request message, the MAG obtains an IP address configured for the registered interface by using an appropriate mechanism, that is, obtaining an ID of the registered interface and an IP address configured for the registered interface. The correspondence relationship can be obtained, for example, by using a Ping mechanism process, an ND process, and DHCP.

412. The MAG sends a network address response message to the LMA, where the network address response message carries an IP address configured by the MAG for the registered interface.

The network address response message carries the ID of the registered interface, the IP address configured for the registered interface, the NAI of the MN connected to the registered interface, and the HNP assigned to the registered interface.

413. The LMA updates the BCE that matches the destination address prefix of the packet and the status identifier is inactive according to the received network address response message, and places the IP address configured for the registered interface into the registered interface. The corresponding BCE sets the status identifier to an active state.

If the LMA is placed in the home network prefix entry of the corresponding BCE in step 407, the LMA will also place the corresponding BCE for the IP address of the registered interface. In the home network prefix entry, set the Length of the home network prefix entry to 128. If the LMA adds the IP address update configured for the registered interface to the home address entry of the corresponding BCE in step 407, the LMA also adds a home address entry to the BCE corresponding to the registered interface. The IP address update configured for the registered interface is placed in the home address entry of the BCE. Also, change the status flag of the BCE to "act ive".

The method for registering the interface prefix in the PMIPv6 provided by the embodiment of the present invention saves the IP address resource prefixed by the HNP, and also does not obtain the destination address of the packet when the LMA receives the packet. In the case of the BCE, the BCE that matches the destination address prefix of the message and the status identifier is inactive is determined, instructing the MAG to obtain and return the IP address configured by the interface recorded in the BCE, and The IP address configured on the interface is placed in the BCE corresponding to the interface. Therefore, if the MAG does not obtain the IP address configured for the interface to be registered when the LMA is registered, the BCE corresponding to the interface in the LMA does not get the updated IP address, and the LMA can update the corresponding BCE again when receiving the packet. Therefore, the LMA re-discovers the BCE that matches the destination address of the packet, and forwards the packet to the corresponding MAG correctly. It avoids resource waste and network security problems caused by forwarding packets to multiple mobile access gateways at the same time, thereby further saving network resources and ensuring data security.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Acces s Memory (RAM).

Embodiment 5

Embodiments of the present invention provide a local mobility anchor point. As shown in FIG. 5, the local mobility anchor point in the embodiment of the present invention includes:

The message receiving unit 501 is configured to receive a PBU message sent by the MAG, where the PBU message carries an ID of the interface to be registered;

a directory setting unit 502, configured to be connected to the message receiving unit 501, configured to allocate the same HNP as the registered interface to the to-be-registered interface, and store the HNP in the BCE created for the to-be-registered interface;

The message sending unit 503 is connected to the directory setting unit 502, and is configured to send a PBA message to the MAG, where the PBA message carries the HNP allocated for the interface to be registered.

The local mobility anchor provided by the embodiment of the present invention allocates the same HNP to different interfaces, and the MN that connects the interface configures an IP address for the interface according to the HNP. The problem that the IP address resource is wasted is solved. At the same time, the embodiment of the present invention configures different IP addresses of the same home network prefix for each interface, so that the local mobility anchor can correctly forward the received packet to the corresponding mobile access gateway according to the IP address of each interface, thereby avoiding Forwarding packets to multiple mobile access gateways at the same time Resource waste and network security issues.

Embodiment 6

The state identification setting unit, the home address flag adding unit, the interface address placing unit, and the address matching unit may be added to the local mobility anchor described in the fifth embodiment, so that the LMA can use the IP address of the interface to match the destination address of the packet. Forward the packet, as shown in Figure 6.

The status identifier setting unit 604 is connected to the directory setting unit 602, and is configured to set the status of the BCE to an inactive state when the BCE is created; and connect with the interface address placing unit 605 for being to be registered or When the IP address of the registered interface is placed in the BCE, the status of the BCE is set to the active state.

The home address identifier adding unit 607 is connected to the message sending unit 603, and is configured to add a home address flag to the proxy binding confirmation message, so that the mobile access gateway learns that the interface needs to be acquired as an interface according to the home address identifier. IP address;

Correspondingly, a home address flag acquisition unit, an interface address acquisition unit, and an interface address addition unit are added to the MAG. The home address identifier obtaining unit is configured to acquire a home address identifier in the received proxy binding confirmation message. The interface address obtaining unit is connected to the home address identifier obtaining unit, and configured to acquire an IP address configured for the registered interface. The interface address adding unit is connected to the interface address obtaining unit, and is configured to add the obtained IP address to the PBU message.

The interface address setting unit 605 is connected to the message receiving unit 601, and configured to put the network address configured for the registered interface in the received second proxy binding update message into the binding cache corresponding to the registered interface. The directory, the IP address configured for the registered interface in the proxy binding update message to be received again, is placed in the BCE corresponding to the registered interface;

The address matching unit 606 is connected to the interface address placing unit 605, and is configured to determine a BCE that matches the destination address of the message when the packet is forwarded.

When the LMA registers, the BCE corresponding to the interface to be registered is placed in the IP address configured for the interface to be registered, so that when the LMA forwards the packet, the LMA obtains a unique BCE according to the address matching. The packet is forwarded to the MAG of the BCE record, which avoids resource waste and network security caused by forwarding the packet to multiple mobile access gateways at the same time, further saving network resources and ensuring data security.

Example 7

The state identification setting unit, the address matching unit, the prefix matching unit, the network address request sending unit, the network address response receiving unit, and the interface address placing unit may be added to the local mobility anchor described in Embodiment 5, so that the LMA can utilize the interface. The IP address matches the destination address of the packet and is forwarded as shown in Figure 7.

The status identifier setting unit 704 is connected to the directory setting unit 702, and is configured to set the status identifier of the BCE to an inactive state when the BCE is created; and connect with the interface address placing unit 705, for being to be registered or already When the IP address of the registered interface is placed in the BCE, the status of the BCE is set to the active state.

The address matching unit 706 is connected to the interface address placing unit 705, and configured to determine a BCE that matches the destination address of the packet.

The prefix matching unit 708 is connected to the directory setting unit 702 and the state identifier setting unit 704, and configured to determine, when the address matching unit does not obtain the BCE that matches the destination address of the message, determine the file with the ^3⁄4 The BCE whose destination address prefix matches and whose status is identified as inactive;

The network address request sending unit 709 is connected to the prefix matching unit 708, and configured to send a network address request message to the mobile access gateway in the binding cache directory determined by the prefix matching unit, where the network address request message carries the prefix according to the The identifier of the corresponding registered interface of the binding cache directory determined by the matching unit;

Correspondingly, a network address request receiving unit, an interface address obtaining unit, and a network address response sending unit are added to the MAG. The network address request receiving unit is configured to receive a network address request message sent by the LMA. The interface address obtaining unit is connected to the network address request receiving unit, and configured to acquire an IP address configured for the registered interface. The network address response sending unit is connected to the interface address obtaining unit, and configured to send a network address response message to the LMA, where the network address response message carries an IP address configured for the registered interface. The network address response receiving unit 710 is configured to receive a network address response message sent by the mobile access gateway, where the network address response message carries an IP address configured by the mobile access gateway for the registered interface.

The interface address placement unit 705 is coupled to the network address response receiving unit 710 for placing an IP address configured for the registered interface into a BCE corresponding to the registered interface.

When receiving the BME, the LMA determines that the BCE that matches the destination address prefix of the "3⁄4 text" and the status identifier is inactive is in the case that the BCE matching the destination address of the packet is not obtained, indicating the MAG. Acquiring and returning the IP address configured by the interface recorded in the BCE, and placing the IP address configured for the interface into the BCE corresponding to the interface, and after the LMA is updated, re-finding the destination of the packet. The BCE that matches the address forwards the packet to the corresponding MAG. Therefore, the LMA can use the IP address of the interface to match the destination address of the text to forward the packet to the corresponding MAG. Resource waste and network security problems caused by forwarding to multiple mobile access gateways further save network resources and ensure data security.

Example eight

The prefix matching unit, the network address request sending unit, and the network address response receiving unit may be added to the local mobility anchor described in the sixth embodiment, so that the LMA correctly forwards the packet to the corresponding MAG when forwarding the packet. , as shown in Figure 8.

The prefix matching unit 808 is connected to the directory setting unit 802 and the state identifier setting unit 804, and is configured to determine, when the BCE matching the destination address of the packet is not obtained, the state and the destination address prefix of the packet match. BCE identified as inactive;

The network address request sending unit 809 is connected to the prefix matching unit 808, and configured to send a network address request message to the mobile access gateway, where the network address request message carries an identifier of the registered interface;

Correspondingly, a network address request receiving unit, an interface address obtaining unit, and a network address response sending unit are added to the MAG. The network address request receiving unit is configured to receive a network address request message sent by the LMA. The interface address obtaining unit is connected to the network address request receiving unit, Used to obtain the IP address configured for the registered interface. The network address response sending unit is connected to the interface address obtaining unit, and configured to send a network address response message to the LMA, where the network address response message carries an IP address configured for the registered interface.

The network address response receiving unit 810 is connected to the interface address placing unit 805, and configured to receive a network address response message sent by the mobile access gateway, where the network address response message carries the mobile access gateway to obtain the The IP address of the configured interface.

When receiving the BME, the LMA determines that the BCE that matches the destination address prefix of the "3⁄4 text" and the status identifier is inactive is in the case that the BCE matching the destination address of the packet is not obtained, indicating the MAG. Obtaining and returning the IP address configured on the interface recorded in the BCE, and placing the IP address configured for the interface into the BCE corresponding to the interface. Therefore, if the MAG is not acquired, the MAG is not acquired. Registering the IP address configured on the interface. Therefore, the BCE corresponding to the interface in the LMA does not get the updated IP address. The LMA can update the corresponding BCE again when receiving the packet, so that the LMA can find the destination address of the document again. The BCE forwards the >3⁄4 text correctly to the corresponding MAG, which avoids resource waste and network security problems caused by forwarding the message to multiple mobile access gateways at the same time, further saving network resources and ensuring data security.

Example nine

The embodiment of the invention provides a registration system for interface prefix in PMIPv6. As shown in FIG. 9, the system for registering an interface prefix in PMIPv6 includes an LMA and at least one MAG, and the LMA is connected to at least one MAG.

The local mobility anchor point 901 is configured to receive a PBU message sent by the mobile access gateway 902, where the PBU message carries an ID of the interface to be registered, and the local mobility anchor point 901 allocates and registers the interface to the to-be-registered interface. The same HNP is stored in the BCE created for the interface to be registered, and sends a PBA message to the mobile access gateway 902;

The mobile access gateway 902 is configured to receive a PBA message sent by the local mobility anchor 901. The system for registering an interface prefix in the PMIPv6 provided by the embodiment of the present invention, by assigning the same HNP to different interfaces, the MN connecting the interface configures an IP address for the interface according to the HNP; The problem of IP address resources being wasted. At the same time, the embodiment of the present invention configures different IP addresses of the same home network prefix for each interface, so that the local mobility anchor can correctly forward the received packet to the corresponding mobile access gateway according to the IP address of each interface, thereby avoiding At the same time, the packet is forwarded to multiple mobile access gateways, which causes waste of resources and network security.

The local mobility anchor 901 may also set the status of the BCE to an inactive state when the BCE is created for the interface to be registered; when the IP address configured for the interface to be registered or registered is placed in the corresponding BCE, Set the status of the BCE that is placed in the network address to the active state.

The mobile access gateway 902 may also obtain an IP address configured for the interface to be registered in the PBA message after receiving the PBA message, and send a PBU carrying the IP address configured for the interface to be registered to the local mobility anchor 901. The message, the PBU message is a second proxy binding update message. After the local mobility anchor 901 receives the PBU message sent by the mobile access gateway 902 again, the IP address configured for the to-be-registered interface in the PBU message is placed in the BCE corresponding to the to-be-registered interface, and The status identifier of the BCE is changed to an active state; when the local mobility anchor 901 forwards the packet, the address of the mobile access gateway 902 recorded in the BCE matching the destination address of the packet is obtained, and the packet is forwarded. The mobile access gateway 902 is provided.

Therefore, when registering, the LMA will place a BCE corresponding to the interface to be registered for the IP address configured for the interface to be registered, so that when the LMA forwards the packet, the LMA obtains a unique BCE according to the address matching, and forwards the packet. The MAG recorded by the BCE avoids resource waste and network security problems caused by forwarding packets to multiple mobile access gateways at the same time, thereby saving network resources and ensuring data security.

Or the local mobility anchor 901 may further determine, when the packet is forwarded and the BCE that matches the destination address of the packet is not obtained, the BCE that matches the destination address prefix of the document and the status identifier is inactive. Obtaining, by the mobile access gateway recorded in the binding cache directory, a network address configured for the registered interface corresponding to the binding cache directory, and placing the obtained network address into a corresponding binding cache directory. The mobile access gateway 902 is configured to acquire a network address configured for the registered interface corresponding to the binding cache directory, and notify the local mobility anchor 901 of the network address information. The local mobility anchor 901 sends a network address request message to the mobile access gateway 902 recorded in the binding cache directory, where the network address request message carries the ID of the registered interface recorded in the BCE. After receiving the network address request message, the mobile access gateway 902 obtains an IP address configured for the registered interface, and sends a network address response carrying the IP address configured for the registered interface to the local mobility anchor 901. Message. The local mobility anchor 901 receives the network address response message sent by the mobile access gateway 902, where the network address response message carries the IP address configured by the mobile access gateway 902 for the registered interface; The BCE corresponding to the registered interface is placed in the BCE corresponding to the registered interface; the local mobility anchor 901 acquires the BCE that matches the destination address of the packet, and forwards the packet to the BCE. Mobile access gateway 902 recorded in.

Therefore, when receiving the BME, the LMA determines that the BCE that matches the destination address prefix of the packet and the status identifier is inactive is in the case that the BCE matching the destination address of the packet is not obtained, indicating the MAG. Acquiring and returning the IP address configured by the interface recorded in the BCE, and placing the IP address configured for the interface into the BCE corresponding to the interface, so that the LMA searches for the purpose of the text after the update. The BCEs that match the address correctly forward the text to the corresponding MAG, which avoids resource waste and network security problems caused by forwarding packets to multiple mobile access gateways at the same time, further saving network resources and ensuring data security.

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

Claim

A method for registering an interface prefix in PMIPv6, which is characterized in that:

Assigning, to the to-be-registered interface, a home network prefix that is the same as the registered interface, and storing the home network prefix in a binding cache directory created for the to-be-registered interface;

And sending a proxy binding acknowledgement message to the mobile access gateway, where the proxy binding acknowledgement message carries a home network prefix allocated for the to-be-registered interface.

The method for registering an interface prefix in the PMIPv6 according to claim 1, wherein the status of the binding cache directory created for the interface to be registered is an inactive state.

The method for registering an interface prefix in the PMIPv6 according to claim 1, wherein the proxy binding acknowledgement message further includes a home address identifier, so that the mobile access gateway learns that the user needs to obtain the home address identifier according to the home address identifier. The IP address configured for the interface.

The method for registering an interface prefix in the PMIPv6 according to claim 2 or 3, wherein the sending the proxy binding acknowledgement message to the mobile access gateway further comprises: receiving the second proxy sent by the mobile access gateway a binding update message, where the second proxy binding update message carries a network address configured by the mobile access gateway and configured for the to-be-registered interface;

And placing a network address configured for the to-be-registered interface into a binding cache directory corresponding to the to-be-registered interface;

Set the status of the binding cache directory to the active state.

The method for registering an interface prefix in the PMIPv6 according to claim 4, wherein the binding of the network address configured for the interface to be registered to the interface to be registered includes:

Setting a network address configured for the to-be-registered interface into a home network prefix entry in a binding cache directory corresponding to the to-be-registered interface, or in a binding cache directory corresponding to the to-be-registered interface Adding a home address entry, placing the network address configured for the interface to be registered into the hometown Address entry.

The method for registering an interface prefix in the PMIPv6 according to claim 4, wherein the setting the status identifier of the binding cache directory to an active state further comprises:

After receiving the packet, when obtaining the binding cache directory that matches the destination address of the packet, obtaining the address of the mobile access gateway recorded in the binding cache directory that matches the destination address of the packet;

Forwarding the message to the mobile access gateway.

The method for registering an interface prefix in the PMIPv6 according to claim 6, wherein the setting the status identifier of the binding cache directory to an active state further includes:

After receiving the packet, when the binding cache directory that matches the destination address of the packet is not obtained, the binding cache directory that matches the destination address prefix of the packet and the status identifier is inactive is obtained. An identifier of the recorded registered interface and an address of the mobile access gateway corresponding to the registered interface;

Obtaining, by the mobile access gateway, a network address configured for the registered interface;

Placing a network address configured for the registered interface into a binding cache directory corresponding to the registered interface;

Setting a status identifier of the binding cache directory corresponding to the registered interface to an active state.

The method for registering an interface prefix in the PMIPv6 according to claim 7, wherein the obtaining, by the mobile access gateway, the network address configured for the registered interface includes:

Sending a network address request message to the mobile access gateway, where the network address request message carries an identifier of the registered interface;

Receiving a network address response message sent by the mobile access gateway, where the network address response message carries a network address configured by the mobile access gateway for the registered interface.

The method for registering an interface prefix in the PMIPv6 according to claim 6, wherein the setting a network address configured for the registered interface to a binding cache directory corresponding to the registered interface includes: Locating a network address configured for the registered interface into a home network prefix entry in a binding cache directory corresponding to the registered interface, or in a binding cache directory corresponding to the registered interface An home address entry that places the home address entry for the network address configured for the registered interface.

The method for registering an interface prefix in the PMIPv6 according to claim 2, wherein after the sending the proxy binding acknowledgement message to the mobile access gateway, the method further includes:

Set the status of the binding cache directory to the active state.

The method for registering an interface prefix in the PMIPv6 according to claim 10, wherein the obtaining, by the mobile access gateway, the network address configured for the registered interface includes:

The method for registering an interface prefix in the PMIPv6 according to claim 10, wherein the placing a network address configured for the registered interface into a binding cache directory corresponding to the registered interface includes :

Locating a network address configured for the registered interface into a home network prefix entry in a binding cache directory corresponding to the registered interface, or in a binding cache directory corresponding to the registered interface An home address entry that places the network address configured for the registered interface into the hometown Address entry.

13. A local mobility anchor, characterized in that:

a message receiving unit (501), configured to receive a proxy binding update message sent by the mobile access gateway, where the proxy binding update message carries an identifier of the interface to be registered;

a directory setting unit (502), configured to allocate, to the to-be-registered interface, a home network prefix that is the same as the registered interface, and store the home network prefix in a binding cache directory created for the to-be-registered interface;

The message sending unit (503) is configured to send a proxy binding acknowledgement message to the mobile access gateway, where the proxy binding acknowledgement message carries a home network prefix allocated for the to-be-registered interface.

The local mobility anchor according to claim 13, further comprising: a status identifier setting unit (604), configured to: when the binding cache directory is created, set a status identifier of the binding cache directory to Inactive state; and when the network address configured for the interface to be registered or registered is placed in the binding cache directory, the status identifier of the binding cache directory is set to the active state.

The local mobility anchor according to claim 14, further comprising: a home address flag adding unit (607), configured to add a home address flag to the proxy binding confirmation message, so as to enable the mobile connection According to the home address flag, the ingress gateway knows that it needs to obtain an IP address configured for the interface.

The local mobility anchor according to claim 14 or 15, further comprising: an interface address placing unit (605), configured to receive the registered second interface in the second proxy binding update message The configured network address is placed in a binding cache directory corresponding to the registered interface;

The address matching unit (606), when forwarding the message, determines a binding cache directory that matches the destination address of the message.

The local mobility anchor according to claim 14, further comprising: an address matching unit (706), configured to determine a binding cache directory that matches a destination address of the packet;

a prefix matching unit (708), configured to: when the address matching unit (706) fails to obtain the report When the destination address of the file matches the binding cache directory, the binding cache directory that matches the destination address prefix of the packet and the status identifier is inactive is determined;

a network address request sending unit (709), configured to send a network address request message to the mobile access gateway in the binding cache directory determined by the prefix matching unit (708), where the network address request message carries the prefix matching unit Determining an identifier of a corresponding registered interface of the binding cache directory; a network address response receiving unit (710), configured to receive a network address response message sent by the mobile access gateway, where the network address response message carries the mobile a network address configured by the access gateway for the registered interface;

The interface address placement unit (705) is configured to place a network address configured for the registered interface into a binding cache directory corresponding to the registered interface.

18. A registration system for interface prefixes in PMIPv6, comprising: a local mobility anchor (901) and at least one mobile access gateway (902), said local mobility anchor (901) and at least one of said The mobile access gateway (902) is connected;

The local mobility anchor (901) is configured to receive a proxy binding update message sent by the mobile access gateway (902), where the proxy binding update message carries an identifier of the interface to be registered, and is the to-be-registered The interface allocates the same home network prefix as the registered interface, and stores the home network prefix in the binding cache directory created for the to-be-registered interface, and sends a proxy binding confirmation message to the mobile access gateway;

The mobile access gateway (902) is configured to receive a proxy binding acknowledgement message sent by the local mobility anchor (901).

The system for registering an interface prefix in the PMIPv6 according to claim 18, wherein the local mobility anchor (901) is further configured to: when the binding cache directory is created for the interface to be registered, the binding is set. The status of the cache directory is identified as being inactive. When the network address configured for the interface to be registered or registered is placed in the corresponding binding cache directory, the status identifier of the binding cache directory where the network address is placed is set to Activation status.

20. The system for registering interface prefixes in PMIPv6 according to claim 18, wherein: The mobile access gateway (902) is further configured to: after receiving the proxy binding acknowledgement message, obtain a network address configured for the to-be-registered interface in the proxy binding acknowledgement message, to the local mobility anchor point (901) Sending a second proxy binding update message carrying a network address configured for the to-be-registered interface;

The local mobility anchor (901) is further configured to receive the second proxy binding update message, and insert, in the second proxy binding update message, a network address configured for the to-be-registered interface. The binding cache directory corresponding to the registered interface is mentioned.

The system for registering an interface prefix in the PMIPv6 according to claim 19 or 20, wherein the local mobility anchor (901) is further configured to: when the packet is forwarded, when the packet is not obtained When the destination address of the file matches the binding cache directory, determine a binding cache directory that matches the destination address prefix of the packet and the status identifier is inactive, and the mobile access gateway recorded in the binding cache directory Obtaining a network address configured for the registered interface corresponding to the binding cache directory, and placing the obtained network address into a corresponding binding cache directory;

The mobile access gateway (902) is further configured to acquire a network address configured for the registered interface corresponding to the binding cache directory, and notify the local mobility anchor (901) of the network address information.