WO2013034003A1 - 一种移动性管理方法和系统 - Google Patents

一种移动性管理方法和系统 Download PDF

Info

Publication number
WO2013034003A1
WO2013034003A1 PCT/CN2012/076271 CN2012076271W WO2013034003A1 WO 2013034003 A1 WO2013034003 A1 WO 2013034003A1 CN 2012076271 W CN2012076271 W CN 2012076271W WO 2013034003 A1 WO2013034003 A1 WO 2013034003A1
Authority
WO
WIPO (PCT)
Prior art keywords
access gateway
node
mobile access
address
communication peer
Prior art date
Application number
PCT/CN2012/076271
Other languages
English (en)
French (fr)
Inventor
霍玉臻
骆文
沈岷
江鸿
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013034003A1 publication Critical patent/WO2013034003A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a mobility management method and system.
  • IP Transmission Control Protocol/Internet Protocol
  • IP provides routing for the Internet. It assigns logical addresses, ie IP addresses, to all nodes (including hosts and routers), and each port of each host is assigned.
  • An IP address includes the network prefix and the host part.
  • the IP addresses of all hosts on the same link usually have the same network prefix and different host parts. This allows IP to be routed based on the network prefix portion of the destination node's IP address, allowing the router to maintain a simple network prefix route without having to maintain a separate route for each host. In this case, since the network prefix route is used, when the node switches from one link to another without changing its IP address, the node cannot receive the data packet on the new link. Therefore, it is impossible to communicate with other nodes.
  • IP Mobile IP, MIP
  • Proxy MIP Proxy MIP
  • MIP Mobile IP
  • PMIP Proxy MIP
  • HA Home Agent
  • LMA Local Mobility Anchor
  • FIG. 1 shows the logical architecture of the PMIP protocol, including the mobile node (Mobile Node, MN), Correspondence Node (CN), Mobile Access Gateway (MAG), and LMA.
  • the CN can be a fixed node or a mobile node, that is, it has a corresponding MAG and LMA.
  • the MAG is the first hop router of the MN, and its main functions include assigning a Care of Address (CoA) to the MN when it is accessed, and performing PMIP Binding (MMIP Binding) with the MN's anchor LMA instead of the MN. .
  • the LMA acts as the anchor of the MN. Its main functions include assigning the Home of Address (HoA) to the MN and processing the above PMIP binding.
  • HoA Home of Address
  • the main purpose of the PMIP binding performed between the MAG and the LMA is to let both parties know the address of the other party, the above CoA and HoA, and save it locally.
  • a bidirectional tunnel is established between the MAG and the LMA for the MN.
  • the IP address finally obtained by the MN is the HoA assigned by the LMA.
  • the MAG is generally located at a lower topology, such as at the edge of a metropolitan area network; and the LMA is generally located at a higher topology, such as the core of the provincial backbone.
  • the MAG and the LMA are often connected by a multi-hop router.
  • the mobility management of the PMIP protocol is reflected in the fact that the MN's mobility can change the currently connected MAG while keeping the MN's IP address (ie HoA) unchanged.
  • changing the currently connected MAG means changing/switching the connection to the target MAG (tMAG, target MAG) from the previously connected source MAG (sMAG, source MAG).
  • tMAG allocates a new CoA to the MN, and performs PMIP binding with the MN's anchor LMA for the MN, updating the information saved by the two parties mentioned above, and between tMAG and LMA.
  • the MN establishes a new two-way tunnel.
  • FIG. 2 shows the process of sending and receiving IP 4 messages between MN and CN.
  • the IP data packet between the MN and the CN must pass through the tunnel between the sMAG and the LMA before the switchover. After the switchover, the tunnel must pass through the tunnel between the tMAG and the LMA.
  • the path between the MN and the CN can be expressed as MN ⁇ ->MAG ⁇ ->LMA ⁇ ->CN, that is, all IP data messages between the MN and the CN must be detoured to the MN's anchor LMA.
  • the MAG has a routing function, and there is an IP network connection between the MAG and the CN (as shown in Figure 1), IP packets cannot be directly sent and received through the MAG, and there is a waste of the packet transmission path.
  • the solid line in FIG. 3 indicates that there is a wasteful route of the transmission path, and the dotted line indicates a route that is not wasted by the transmission path.
  • the waste of the transmission path causes the carrier to waste the transmission of the bearer resources, which leads to an increase in the operating cost.
  • the delay of sending and receiving IP packets between the ⁇ and the CN is increased, which is not conducive to improving the user experience.
  • the above CN may also be located in the PMIP domain, applying the PMIP mobility management mechanism described above (for example, CN is another mobile node, that is, CN shown in FIG. 1).
  • CN is also connected to a MAG and also has an anchor LMA.
  • the IP packet transmission path between the MN and the CN is: MN ⁇ -> MAG of the MN ⁇ -> LMA of the MN ⁇ -> MAG ⁇ ->CN of the LMA ⁇ ->CN of the CN. It can be seen that in this scenario, the packet transmission and reception between the MN and the CN must bypass the anchor point LMA of both, and the waste of the packet transmission path is more obvious, and the above-mentioned adverse consequences are more serious. Summary of the invention
  • the technical problem to be solved by the embodiments of the present invention is to provide a mobility management method and system, to solve the problem that the message forwarding wastes system resources after the MAG handover.
  • an embodiment of the present invention provides a mobility management method, including: after a mobile node (MN) switches from a source mobile access gateway to a target mobile access gateway, the mapping server of the MN reports to the The mobile access gateway of the correspondent node (CN) of the MN sends node information directed to the MN and address information directed to the target mobile access gateway;
  • MN mobile node
  • CN correspondent node
  • the mapping server of the MN After the MN switches from the source mobile access gateway to the target mobile access gateway, the mapping server of the MN sends node information directed to the MN and points to the target mobile to a mapping server of the CN. Address information of the access gateway, the mapping server of the CN forwarding the node information directed to the MN and address information directed to the target mobile access gateway to the CN's mobile access gateway.
  • the node information that is directed to the MN includes: one of the identifier information of the MN, a home address, and a home network prefix, or a combination thereof;
  • the address information directed to the target mobile access gateway includes one or a combination of the following: an address of the target mobile access gateway, and a care-of address (CoA) assigned by the target mobile access gateway to the node to which it is attached.
  • COA care-of address
  • the method further includes:
  • the current mobile access gateway of the MN After the current mobile access gateway of the MN receives the first data packet between the MN and the CN, the following entry is added to the newly created communication peer table or the existing communication peer table: a mapping relationship between node information of the MN and node information directed to the CN;
  • the current mobile access gateway of the MN is the source mobile access gateway or the target mobile access gateway.
  • the synchronization of the communication peer table to the mapping server of the MN includes: the current mobile access gateway of the MN periodically and periodically synchronizes the locally created and maintained communication peer table to the mapping server;
  • mapping server after receiving the request sent by the mapping server periodically, synchronizing the locally created and maintained communication peer table to the mapping server;
  • the newly created communication peer table entry is synchronized to the mapping server.
  • the method further includes: the current mobile access gateway of the MN updates the communication peer table by one of the following steps or a combination thereof:
  • the communication peer table is deleted;
  • the current mobile access gateway of the MN deletes the corresponding entry of the offline node that is offline or powered off in the local communication peer table. ;
  • the mobile node attached to the current mobile access gateway of the MN is offline or powered off, the corresponding entry of the offline node that is offline or powered off in the communication peer table is deleted.
  • the method further includes: the mapping server updating the communication peer table by one of the following steps or a combination thereof:
  • mapping server deletes the entry in the communication peer table that is longer than the specified time, where the specified time is greater than a synchronization period of the synchronous communication peer table between the mobile access gateway and the mapping server;
  • the mapping server After receiving the message that the peer node is offline or shut down, the mapping server deletes the corresponding entry of the peer node in the local communication peer table;
  • the mapping server After receiving the message that the mobile node is offline or powered off, the mapping server deletes the corresponding entry of the mobile node in the local communication peer table.
  • the method further includes: the source mobile access After the gateway actively or receives the request of the mapping server of the MN, the communication peer table that is not locally synchronized to the mapping server of the MN is sent to the mapping server of the MN; the communication peer table is sent to the And the target mobile access gateway sends the communication peer table to the mapping server of the MN by the target mobile access gateway.
  • the method further includes: the MN current mobile access gateway establishes an address mapping relationship table locally, and caches an address mapping relationship of one or more peer nodes of the MN, where the address mapping relationship table is Each entry represents an address mapping relationship of a peer node, including node information pointing to the peer node and address information of the mobile access gateway pointing to the peer node;
  • the current mobile access gateway of the MN is the source mobile access gateway or the target mobile access gateway.
  • the method further includes: updating, by the MN current mobile access gateway, the address mapping relationship table by one of the following steps or a combination thereof:
  • the mobile access gateway of the MN learns that the mobile node attached thereto is offline or powered off, if the mobile access gateway of the opposite node of all other mobile nodes attached thereto is different from the offline or shutdown mobile
  • the mobile access gateway of the peer node of the node deletes the peer node related entry of the offline or shutdown mobile node in the address mapping relationship.
  • the method further includes:
  • the local mobile access gateway updates the locally saved address by using the address mapping relationship of the CN in the message.
  • An address mapping relationship of the CN and sending a message for updating the address mapping relationship of the CN to the mapping server of the MN, and carrying a handover indication that the CN is simultaneously switched during the MN handover;
  • the MN mapping server After receiving the message of updating the address mapping relationship of the CN, the MN mapping server updates the address mapping relationship of the CN, and sends the target mobile connection to the CN-switched mobile access gateway. Address information of the gateway.
  • the embodiment of the present invention further provides a mapping server, where the mapping server includes a switching update unit, and the setting is:
  • the mapping server After the mobile node (MN) accessing the mapping server switches from the source mobile access gateway to the target mobile access gateway, sends a pointer to the MN to the mobile access gateway of the opposite node (CN) of the MN. Node information and address information pointing to the target mobile access gateway;
  • mapping server Or after the mobile node (MN) accessing the mapping server switches from the source mobile access gateway to the target mobile access gateway, sending, to the mapping server of the CN, node information that points to the MN and points to the The address information of the target mobile access gateway is forwarded by the mapping server of the CN to the node information of the MN and the address information directed to the target mobile access gateway to the mobile access gateway of the CN.
  • MN mobile node
  • the node information that points to the MN includes: the identifier information of the MN, One or a combination of the township address and the home network prefix;
  • the address information of the target mobile access gateway includes one or a combination of the following: an address of the target mobile access gateway, and a care-of address assigned by the target mobile access gateway to the node attached thereto (CoA) ).
  • the communication peer table management unit is configured to: receive a communication peer table that is synchronized by the source mobile access gateway, where the communication peer table includes node information that points to the MN and points to the CN The mapping relationship of node information.
  • the communication peer table management unit is further configured to update the communication peer table by one of the following manners or a combination thereof:
  • the handover update unit is further configured to: after receiving the message that is updated by the source mobile access server and update the address mapping relationship of the CN, update the address mapping relationship of the CN, and send the address mapping relationship to the CN
  • the switched mobile access gateway sends address information to the target mobile access gateway, and the address mapping relationship of the CN includes node information pointing to the CN and address information of the mobile access gateway pointing to the CN.
  • the embodiment of the present invention further provides an access gateway, where the access gateway is moved as the source after the mobile node (MN) accessing the mapping server switches from the source mobile access gateway to the target mobile access gateway.
  • MN mobile node
  • the communication peer table creation unit and the synchronization unit are included, where:
  • the communication peer table creation unit is configured to: after receiving the first data packet between the MN and the peer node (CN) of the MN, newly establish a communication peer table or an existing one The following entry is added to the communication peer table: a mapping relationship between the node information pointing to the MN and the node information pointing to the CN;
  • the synchronization unit is configured to: synchronize the communication peer table to the mapping server;
  • the synchronization unit is configured to synchronize the communication peer table to the mapping server by:
  • the locally created and maintained communication peer table is synchronously synchronized to the mapping server; or, after receiving the request sent by the mapping server periodically, the locally created and maintained communication peer table is synchronized to the mapping server;
  • the newly created communication peer table entry is synchronized to the mapping server.
  • the access gateway further includes an update unit, configured to update the communication peer table by one of the following manners or a combination thereof:
  • the synchronization unit After the synchronization unit synchronizes the local communication peer table to the mapping server of the MN, deleting the communication peer table;
  • the synchronization unit is further configured to: actively or receive the location information before the mapping server sends the address information of the target mobile access gateway to the mobile access gateway of the CN or the mapping server of the CN After the request of the mapping server of the MN, the communication peer table that is not synchronized to the mapping server is sent to the mapping server; or the communication peer table that is not synchronized to the mapping server is sent to the local The target mobile access gateway sends the communication peer table to the mapping server by the target mobile access gateway.
  • the access gateway further includes a mapping relationship table creating unit, configured to: establish an address mapping relationship table locally, and cache an address mapping relationship of one or more CNs of the MN, where the address mapping relationship table is Each entry represents a CN's address mapping relationship, including node information pointing to the CN and address information of the mobile access gateway pointing to the CN.
  • a mapping relationship table creating unit configured to: establish an address mapping relationship table locally, and cache an address mapping relationship of one or more CNs of the MN, where the address mapping relationship table is Each entry represents a CN's address mapping relationship, including node information pointing to the CN and address information of the mobile access gateway pointing to the CN.
  • the foregoing access gateway further includes a mapping relationship table updating unit, configured to update the address mapping relationship table by one of the following manners or a combination thereof:
  • the access gateway further includes a mapping update unit, configured to: use the message when receiving a message that is updated by the mapping server of the CN and that is updated by the mapping server of the CN during the MN handover
  • the address mapping relationship of the CN in the CN updates the locally stored address mapping relationship of the CN, and sends a message for updating the address mapping relationship of the CN to the mapping server, and carries a handover indication that the CN is simultaneously switched during the MN handover.
  • the handover management method provided by the embodiment of the present invention enables the MN to ensure that the transmission and reception of IP packets between the MN and the CN without waste on the transmission path after the terminal moves, and meets the mobility requirement of the MN.
  • Figure 1 is a logical architecture diagram of an existing PMIP protocol
  • FIG. 2 is a schematic diagram of a process of transmitting and receiving IP packets between a MN and a CN according to the existing PMIP protocol
  • FIG. 3 is a schematic diagram of a transmission path waste problem existing according to the existing PMIP protocol
  • FIG. 4 is a logical architecture of the modified PMIP protocol.
  • FIG. 5 is a schematic diagram of a process of transmitting and receiving IP packets between a MN and a CN according to a modified PMIP protocol
  • Figure 6a is a schematic diagram of an example of an address mapping relationship table
  • 6b, 6c are schematic diagrams of examples of a communication peer table
  • 7 is a schematic diagram of Embodiment 1 of a mobility management method according to the present invention
  • Embodiment 8 is a schematic diagram of Embodiment 2 of a mobility management method according to the present invention.
  • Embodiment 3 of a mobility management method according to the present invention is a schematic diagram of Embodiment 3 of a mobility management method according to the present invention.
  • FIG. 10 is a schematic diagram of Embodiment 4 of a mobility management method according to the present invention.
  • FIG. 11 is a schematic diagram of Embodiment 5 of a mobility management method according to the present invention.
  • FIG. 12 is a schematic diagram of Embodiment 6 of a mobility management method according to the present invention.
  • Embodiment 7 of the mobility management method of the present invention.
  • FIG. 14 is a block diagram of a source mobile access gateway according to an embodiment of the present invention.
  • FIG. 15 is a block diagram of a mapping server in accordance with an embodiment of the present invention. Preferred embodiment of the invention
  • the CN is a communication peer node of the MN, and the CN may have multiple.
  • the sMAG-MN/MAG-MN refers to the MAG currently accessed by the MN, and the proxy care-of address assigned by the MAG to the MN is CoAl.
  • the tMAG-MN refers to the MAG after the MN moves, that is, the MAG accessed by the MN after the handover, and the proxy care-of address assigned by the MAG to the MN is CoA2.
  • the MAG-CN refers to the MAG currently accessed by the CN, and the proxy assignment address assigned by the MAG to the CN is CoA3.
  • the tMAG-CN refers to the MAG after the CN moves, that is, the MAG that is accessed by the CN after the handover, and the proxy care-of address assigned by the MAG to the CN is CoA4.
  • the MAPS-MN refers to the MAPS accessed by the MN.
  • the home network prefix (HNP) assigned by the MASS to the MN is HNP1
  • the home address obtained by the MN according to the HNP1 configuration is ⁇ 1.
  • the MAPS-CN refers to the MAPS accessed by the CN.
  • the home network prefix assigned by the MAPS to the CN is HNP3, and the home address obtained by the CN according to the HNP3 configuration is HoA3.
  • the address of the MAG may be an interface address, or any other address that can represent the MAG.
  • the node information pointed to the MN or the CN in the embodiment of the present invention is information for indicating which MN or CN is, and may be one of the following information of the MN or the CN or a combination thereof. : identification (ID), home address, and home network prefix; the address information pointed to the MAG in the present invention is a letter indicating which MAG is a MN or a MA attached or attached to the MAG.
  • CoA can also be a combination of the address of the MAG and the CoA.
  • the information indicating the node information of the MN or the CN is specifically represented by the information, and the information indicating the address information of the MAG is determined by the specific application scenario or the information that may be obtained by the corresponding network element, which is not limited by the present invention.
  • the detailed description of the embodiments is merely illustrative and should not be construed as limiting.
  • the sMAG-MN address information refers to the address of the sMAG-MN, the proxy care-of address (CoA) assigned by the sMAG-MN to the MN, or a combination of the first two information
  • the address information pointing to the tMAG-MN refers to The address of the tMAG-MN, the proxy care-of address (CoA) assigned by the tMAG-MN to the MN, or a combination of the first two information
  • the address information of the MAG-CN pointing to the opposite node CN of the MN refers to the pair of the MN
  • the address of the MAG-CN of the end node CN, the MAG-CN of the opposite node CN of the MN is the proxy care-of address (CoA) assigned by the CN or a combination of the first two pieces of information.
  • the mapping server allocates the home network prefix (HNP) for the MN or the CN.
  • HNP home network prefix
  • the MN or the CN receives the router advertisement message (the message carries the HNP), the address configuration is performed to obtain the source. From HNP's home address HoA.
  • a HNP can only be assigned to one terminal, that is, both HNP and HoA can uniquely refer to a specific MN.
  • the MAPS/MAG may not know the HoA configured by the MN or CN. In specific network applications, it is also possible for the MAPS/MAG to obtain the HoA configured by the MN or CN.
  • the mapping relationship in the MAPS/MAG is the mapping relationship between the HNP and the CoA or MAG address.
  • the mapping in the MAPS/MAG is the mapping relationship between the HoA and the CoA or the MAG address, or the mapping between the HNP and the CoA or MAG address.
  • FIG. 4 shows the modified PMIP protocol architecture.
  • the modified PMIP protocol architecture includes the mobile node MN, the communication peer CN, the mobile access gateway MAG, and the MAPS.
  • the modified PMIP protocol architecture no longer has LMA network elements.
  • the CN may be a fixed node or a mobile node, that is, has a corresponding MAG and MAPS.
  • the MAG is the first hop router of the MN. Its main function is to allocate the care-of address CoA for the MN in the existing PMIP architecture, and to perform the PMIP binding between the MN and the anchor MAPS instead of the MN. :
  • the MAPS Query the MAPS to obtain the address of the MAG (MAG-CN) to which the communication peer CN is currently connected or the care-of address CoA of the CN.
  • a bidirectional tunnel is established between the MAG (MAG-MN) of the MN and the MAG of the CN, and the IP data between the MN and the CN is forwarded.
  • MAG-MN MAG-MN
  • the MAPS retains the MN registration, deregistration, and update functions in the LMA function, assigns the HNP function, and establishes and maintains the BCE function, but does not act as an anchor for the MN.
  • the IP data packet between the MN and the CN does not need to go through the MAPS.
  • the MAPS needs to save the address of the current MAG-MN and/or the CoA of the MN, and use the node information pointing to the MN as an index, for example, using the MN ID, HoA or MN's Home Network Prefix (HNP) as an index.
  • the MAG for the communication partner CN or CN of the MN is queried according to the relevant information of the MN.
  • Figure 5 shows the process of sending and receiving IP packets between the MN and the CN when the modified PMIP architecture is applied. As shown in Figure 5, the IP data packet between the MN and the CN needs to pass through the tunnel between the MAG-MN and the MAG-CN.
  • the MN When the MN sends an uplink IP packet to the CN, the MN needs to send the IP packet to the MAG-MN. Subsequent to the existing PMIP mechanism, the MAG-MN needs to query the address of the MAG-CN in the embodiment of the present invention. After querying the address of the MAG-CN (such as the IP address of the MAG-CN), the MAG-MN uses the address of the MAG-CN as the destination to establish a tunnel from the MAG-MN to the MAG-CN (for example, an IP in IP tunnel). At the same time, the above IP packet is placed in the tunnel and sent directly to the MAG-CN. After receiving the IP packet from the tunnel, the MAG-CN sends an IP packet to the CN.
  • the MAG-CN After receiving the IP packet from the tunnel, the MAG-CN sends an IP packet to the CN.
  • the MAG-MN can also query the CoA of the CN, and replace the address of the MAG-CN with the CoA address of the CN, and can achieve the same purpose. At this time, the MAG-MN uses the CoA as the end point and establishes the tunnel of the MAG-MN to the MAG-CN with the same effect. It is also worth noting that when the MAG-MN queries the address of the MAG-CN of the CN (or the CoA of the CN), it first queries the local cache, and if it does not query, it can query other network elements. For example, the anchor MAPS (MAPS-CN) of CN can be queried according to the HoA of CN. After querying the desired result, MAG-MN caches the query results locally. The advantage of caching the query results locally is that it can avoid frequent logins to other network elements.
  • MAPS MPS-CN
  • the CN when the CN sends a downlink IP packet to the MN, the same method as above is used, and the principle is the same, and will not be described again.
  • the path of the IP packet transmitted and received between the MN and the CN becomes the MAG ⁇ ->CN of the MAG ⁇ ->CN of the MN ⁇ ->MN, and does not need to pass through the anchor point of the MN (or MN and CN).
  • the MAPS network element avoids a series of problems such as waste of the transmission path.
  • the MAG-MN needs to cache the address of the MAG-CN or the CoA of the CN.
  • the CN's HoA or HNP or ID is used as an index to form a mapping relationship between the peer nodes, such as the HoA or HNP or ID of the CN, mapped to the MAG-CN address or the CN's CoA, which is referred to as an address mapping relationship.
  • the MAG-MN needs to locally cache multiple address mapping relationships. In this case, an address mapping relationship table is formed. As shown in FIG.
  • the address mapping relationship table is structured. Address Mapping Relationship Table Each entry includes node information pointing to the CN and address information pointing to the MAG-CN.
  • FIG. 6a is only an example, where the index entry carries node information that points to the CN, except that it may be a HoA of the CN, a HNP or an ID of the CN, or any combination of multiple HoA/HNP/IDs.
  • Value entry carrying MAG-CN The address information may be the address of the MAG-CN or the combination of the CoA of the CN or the address of the MAG-CN and the CoA of the CN.
  • the address mapping relationship table is a global table saved on the MAG, that is, the address mapping relationships of all the peer nodes of all the MNs attached to the MAG are stored in the same table. It is worth noting that the MN's own address mapping relationship, that is, the mapping between the MN's HoA or HNP or ID and the MAG-MN address or the MN's CoA can also be stored in the address mapping table.
  • the MAG-MN can delete the entries in the following manner.
  • the following methods can be used separately or in combination.
  • A1 Aging mechanism.
  • the MAG-MN sets the aging timer T3. After the T3 times out, the MAG-MN deletes the corresponding entry in the address mapping table. An aging timer needs to be started for each address mapping entry.
  • A2 Peer notification mechanism. After the MAPS-CN determines that the CN is offline or shuts down, it notifies the MAPS-MN that the CN is disconnected or shuts down. After receiving the notification message, the MAPS-MN deletes the corresponding CN entry in the communication peer list. Optionally, the MAPS-MN notifies the MAG-MN to delete the corresponding CN entry in the locally maintained communication peer table.
  • the MAG-MN After receiving the message, the MAG-MN deletes the corresponding CN entry in the locally maintained communication peer table, and checks whether there are other communication peers in the address mapping relationship table (not just the communication peer of the MN, but The communication peers of all the terminals attached to the MAG-MN continue to use the corresponding mapping relationship in the address table entry, that is, check whether there are other MAGs of the MAG of the other communication peers and the MAG of the CN, if all the MAGs of the communication peers The MAG-MN deletes the corresponding entry in the address mapping relationship table. If there is no CN entry in the communication peer table maintained by the local device, the MAG-MN still needs to check the above address mapping table.
  • A3 Local notification mechanism.
  • the MAG-MN deletes all the information of the MN, and at the same time performs the check of the address mapping relationship table as described in A2. If the mobile access gateway of the opposite end node of all other mobile nodes attached to the MAG-MN is different from the mobile access gateway of the opposite end node of the offline or powered off MN, the address mapping relationship is deleted.
  • the MN's Correspondence Node Table (CNT) also known as the MN-CN mapping table, needs to be created and maintained locally on the MAPS or MAG.
  • CNTs may take two forms:
  • the first form is a partial table. As shown in Figure 6b, MAG/MAPS needs to create and maintain a communication peer table for each MN attached to it, and save it in the binding information of the MN.
  • the table can be found by the HoA or HNP or ID of the MN, and the HoA or HNP or ID of the communication peer of the MN can be known in the table.
  • the second form is a global table.
  • MAG/MAPS maintains only one table for all MNs attached to it, and fills in the table with all MN's communication peer information, and uses MN's HoA. Or HNP or ID as an index.
  • the HoA or HNP or ID of the communication peer CN of the designated MN can also be known.
  • the MAG When receiving the IP data packet between the MN and the CN, the MAG obtains the HoA or HNP of the communication peer from the data packet, or obtains the ID of the communication peer, and establishes the MN-CN mapping table as described above.
  • the MAG needs to synchronize the local CNTs to the MAPS and delete the CNTs that have been synchronized to the MAPS. Among them, you can take one of the following ways to synchronize:
  • the new entry can be synchronized to the MAPS immediately, and the CNT is newly created or updated by the MAPS;
  • the MAG can also maintain the CNT-segment time locally, and then periodically synchronize the CNT to the MAPS, and the MAPS creates or updates the CNT;
  • the MAG can also not actively synchronize the CNT to the MAPS.
  • the MAPS periodically queries the MAG to obtain the newly created CNT entry.
  • the MAG considers that the locally maintained CNT is not synchronized to the CNT entry of the MAPS.
  • the MAG determines whether the communication peer is a new communication peer according to whether the communication peer exists in the locally maintained CNT. When there is no communication peer information in the CNTs that are maintained by the MAG, the MAG determines that the communication peer is a new communication peer. You need to create a new CNT entry and synchronize to the MAPS immediately or periodically. This may result in repeated updates of some CNT entries. MAPS will combine all CNT entries from the MAG into a complete CNT. For repeated updates, The MAPS needs to overwrite the original entry.
  • the MAPS-MN notifies the MN's tMAG-MN address or the new CoA to the relevant CN's MAG (ie MAG-CN) in the process of the MN registering with the post-MAPS related information by the MN.
  • Embodiments 1 and 2 are shown.
  • the MAG-MN can delete the entries in the following manner.
  • the following methods can be used separately or in combination.
  • the MAG-MN sets the synchronization timer T1. After the T1 times out, the MAG-MN synchronizes the communication peer table created and maintained in the T1 time to the MAPS-MN, deletes the locally maintained communication peer table, and restarts the synchronization timer. Tl. Or the MAPS-MN sets the synchronization timer T1. After the T1 times out, the MAG-MN obtains the communication peer table created and maintained by the MAG-CN in the T1 time and restarts the synchronization timer T1, and the MAG-MN deletes the local maintenance. Communication peer table. The value indicates that the minimum value of T1 can be 0, that is, real-time synchronization. At this time, Tl can be not set.
  • ⁇ 2 Peer notification mechanism. After the peer MAPS-CN determines that the communication peer is offline or shuts down, it notifies the MAPS-MN of the CN offline or shutdown message. After receiving the notification message, the MAPS-MN deletes the corresponding CN entry in the communication peer table. Optionally, the MAPS-MN notifies the MAG-MN to delete the corresponding CN entry of the locally maintained communication peer table. After receiving the message, the MAG-MN deletes the corresponding CN entry in the communication maintenance peer table of the local maintenance. If there is no such entry, the MAG-MN ignores the message or considers that it has been successfully deleted.
  • B3 Local notification mechanism.
  • the MAG-MN deletes all information of the MN, including the locally maintained communication peer table.
  • the MAPS-MN can delete the entries in the following manner.
  • the following methods can be used separately or in combination.
  • C1 Aging mechanism. After the MAPS- ⁇ obtains the communication peer table from the MAG- ⁇ , the MAPS-MN needs to locally start an aging timer T2, which needs to be longer than the time T1 of the MAG-CN local maintenance communication peer table. An aging timer needs to be started for each CNT entry, or only one aging timer is started for the CNT entry obtained from the MAG-MN-batch. When T2 times out After that, the MAPS-MN needs to delete the corresponding entry. For the repeated communication peer entry obtained from the MAG-MN, the MAPS-MN needs to terminate the original T2 and restart T2.
  • C2 Peer notification mechanism. After the peer MAPS-CN determines that the communication peer is offline or shuts down, deletes all information about the CN on the MAPS-CN, and notifies the MAPS-MN of the CN offline or shutdown message, after the MAPS-MN receives the notification message, Delete the corresponding CN entry in the communication peer table.
  • the MAG-MN When the MN is offline or powered off, the MAG-MN notifies the MAPS-MN of the MN offline or shutdown message.
  • the MAPS-MN deletes all the information of the MN, including the communication peer table, and needs to take the MN offline or shutdown message according to the communication peer.
  • the table notifies the MAG-CN of the communication peer CN of all MNs, and can directly notify the MAG-CN, or notify the MAPS-CN first, notify the MAG-CN by the MAPS-CN, and process the MAG-CN as the peer notification mechanism in B2.
  • the MN at this time is equivalent to the communication peer of the CN.
  • the embodiment of the invention provides a mobility management method, including:
  • the mapping server of the MN After the mobile node (MN) switches from the source mobile access gateway to the target mobile access gateway, the mapping server of the MN sends a node directed to the MN to the mobile access gateway of the opposite node (CN) of the MN. Information and address information pointing to the target mobile access gateway;
  • the mapping server of the MN After the MN switches from the source mobile access gateway to the target mobile access gateway, the mapping server of the MN sends node information directed to the MN and points to the target mobile to a mapping server of the CN.
  • the address information of the access gateway, the mapping server of the CN forwards the node information directed to the MN and the address information directed to the target mobile access gateway to the mobile access gateway of the CN.
  • the node information of the node includes: one of the node identification information, the home address, and the home network prefix, or a combination thereof; the address information that points to the mobile access gateway includes one or a combination of the following: the mobile access gateway An address, a care-of address (CoA) assigned by the mobile access gateway to a node attached thereto; the node is a mobile node or a correspondent node, and the mobile access gateway includes a target mobile access gateway.
  • the current mobile access gateway of the MN receives the first data packet between the MN and the CN, the following entry is added to the newly created communication peer table or the existing communication peer table. : a mapping relationship between the node information of the MN and the node information of the CN; and synchronizing the communication peer table to the mapping server of the MN;
  • the current mobile access gateway of the MN is the source mobile access gateway or the target mobile access gateway.
  • Synchronizing the communication peer table to the mapping server of the MN includes:
  • the current mobile access gateway of the MN periodically actively synchronizes the locally created and maintained communication peer table to the mapping server;
  • mapping server after receiving the request sent by the mapping server periodically, synchronizing the locally created and maintained communication peer table to the mapping server;
  • the newly created communication peer table entry is synchronized to the mapping server.
  • the current mobile access gateway of the MN updates the communication peer table by one of the following methods or a combination thereof:
  • the communication peer table is deleted;
  • the current mobile access gateway of the MN deletes the corresponding entry of the offline node that is offline or powered off in the local communication peer table.
  • the mapping server updates the communication peer table by one of the following methods or a combination thereof: the mapping server deletes an entry in the communication peer table that is longer than a specified time, where the specified time is greater than the mobile connection Synchronizing the synchronization period of the communication peer table between the gateway and the mapping server;
  • the mapping server After receiving the message that the peer node is offline or shut down, the mapping server deletes the corresponding entry of the peer node in the local communication peer table;
  • mapping server After the mapping server receives the offline or shutdown message of the mobile node, deleting the local communication pair The corresponding entry of the mobile node in the terminal table.
  • mapping server of the MN Before the mapping server of the MN sends the address information of the target mobile access gateway to the mobile access gateway of the CN or the mapping server of the CN, the mapping server further includes:
  • the communication peer table that is not locally synchronized to the mapping server of the MN is sent to the mapping server of the MN; Sending to the target mobile access gateway, the target mobile access gateway sends the communication peer table to the mapping server of the MN.
  • the method further includes: the current mobile access gateway of the MN establishes an address mapping relationship table locally, and caches an address mapping relationship of one or more peer nodes of the MN, where each address mapping relationship table is The entry represents an address mapping relationship of a peer node, including node information pointing to the peer node and address information of the mobile access gateway pointing to the peer node; the current mobile access gateway of the MN is the source Mobile access gateway or target mobile access gateway.
  • the current mobile access gateway of the MN updates the address mapping relationship table by one of the following methods or a combination thereof:
  • the current mobile access gateway of the MN learns that the opposite node is offline or shut down, if the mobile access gateway of the opposite node of all the mobile nodes attached thereto and the mobile node of the offline or closed peer node If the gateways are different, the related items of the peer node that are offline or powered off in the address mapping relationship table are deleted.
  • the mobile access gateway of the MN learns that the mobile node attached thereto is offline or powered off, if the mobile access gateway of the opposite node of all other mobile nodes attached thereto is different from the offline or shutdown mobile
  • the mobile access gateway of the peer node of the node deletes the peer node related entry of the offline or shutdown mobile node in the address mapping relationship.
  • the local mobile access gateway updates the locality by using the address mapping relationship of the CN in the message. Save the address mapping relationship of the CN and send the update CN
  • the message of the address mapping relationship is sent to the mapping server of the MN, and carries a handover indication that the CN is simultaneously switched during the MN handover;
  • the MN mapping server After receiving the message of updating the address mapping relationship of the CN, the MN mapping server updates the address mapping relationship of the CN, and sends the target mobile connection to the CN-switched mobile access gateway. Address information of the gateway.
  • FIG. 7 is a first embodiment of the mobility management method of the present invention.
  • the present embodiment is applicable to the MAPS-MN directly informing the communication peer MAG-CN to update the HNP-tMAG-MN address mapping or HNP-new CoA mapping of the MN. As shown in Figure 7, the following steps are specifically included:
  • Step 701 The triggering is performed by the MAG-MN.
  • the MAPS-MN decides to notify the MAG-CN to update the HNP-MAG-MN address mapping or HNP-CoA mapping of the MN.
  • the MAPS-MN obtains all the CNs of the MN in the communication peer table, and queries the corresponding MAG-CN address or the CoA of the CN according to the CN, and then sends a CoA update message to the MAG-CN, where the message carries the HNP of the MN, and carries tMAG-MN address or CoA2 (ie HNP1 and tMAG-MN address or HNP1 and CoA2 mapping).
  • the MAPS-MN in order for the MAPS-MN to query the address of the MAG-CN or the CoA of the CN, when the MAG-MN synchronizes the CNT to the MAPS-MN, or the MAPS-MN queries the MAG-MN for the CNT, the MAG-MN
  • the MAG-CN address or the CN's CoA needs to be notified to the MAPS-MN at the same time.
  • the MAPS-MN also needs to save the information locally.
  • the purpose of the CoA update message is to send the HNP1 and tMAG-MN address mapping or HNP1-CoA2 mapping to the MAG-CN.
  • the name of the message can be another name as long as the message carries the above information.
  • Step 702 After receiving the message, the MAG-CN updates the locally stored address mapping of the HNP1 and the sMAG-MN or the HNP1-CoAl mapping relationship to the address mapping of the HNP1 and the tMAG-MN or the HNP1-CoA2 mapping.
  • Step 703 After successfully updating the foregoing mapping, the MAG-CN returns a CoA update response to the MAPS- ⁇ .
  • the purpose of the CoA update response message is to respond to the CoA update message of step 701.
  • the name of the message may be other names as long as the message completes the above functions.
  • Step 704 this step is an optional step.
  • step 704 and step 705 are performed.
  • the MAG-CN sends a CoA update message to the MAPS-CN, where the message carries the HNP of the MN, the tMAG-MN address, or the CoA2 (ie, the HNP1 and tMAG-MN addresses or the mapping between HNP1 and CoA2).
  • the purpose of the CoA update message is to send the address mapping of HNP1 and tMAG-MN or the HNP1-CoA2 mapping to the MAPS-CN.
  • the name of the message can be another name as long as the message carries the above information.
  • Step 705 this step is an optional step.
  • the MAPS-CN updates the locally stored HNP1 and sMAG-MN address mapping or HNP1-CoAl mapping relationship to address mapping of HNP1 and tMAG-MN or HNP1. -CoA2 mapping, and return to MAG-CN
  • the purpose of the CoA update response message is to respond to the CoA update message of step 704, and the name of the message may be another name as long as the message completes the above functions.
  • MAPS-CN and MAPS - MN may also be the same MAPS. At this time, there is no need for message interaction between the MAPS-MN and the MAPS-CN, that is, steps 704 and 705 need not be performed.
  • FIG. 8 is a second embodiment of the mobility management method of the present invention.
  • the embodiment is applicable to the MAPS-MN protocol.
  • Step 801 is triggered by the MAG-MN.
  • the MAPS-MN decides to inform the MAG-CN to update the HNP-MAG-MN address mapping or HNP-CoA mapping of the MN.
  • the MAPS-MN acquires all CNs of the MN in the communication peer table, and then sends a CoA update message to the MAPS-CN, the message carries the HNP of the MN, and the tMAG-MN address or CoA2 (ie, HNP1 and tMAG-MN address or HNP1) Mapping with CoA2), also need to carry CN's HNP or Ho A or ID.
  • the purpose of the CoA update message is to send the address mapping of HNP1 and tMAG-MN or the HNP1-CoA2 mapping to the MAPS-CN.
  • the name of the message can be another name as long as the message carries the above information.
  • Step 802 After receiving the CoA update message, the MAPS-CN according to the CN carried in the message
  • the HNP or HoA or ID queries the corresponding MAG-CN address or the CN's CoA, and then sends a CoA update message to the MAG-CN, where the message carries the MN's HNP, tMAG-MN address, or CoA2 (ie, HNP1 and tMAG-MN addresses or HNP1 and CoA2 mapping).
  • the purpose of the CoA update message is to send the HNP1 and tMAG-MN address mapping or HNP1-CoA2 mapping to the MAG-CN.
  • the name of the message can be another name as long as the message carries the above information.
  • Step 803 After receiving the message, the MAG-CN updates the address mapping or the HNP1-CoAl mapping relationship between the HNP1 and the sMAG-MN to be the address mapping of the HNP1 and the tMAG-MN or the HNP1-CoA2 mapping.
  • Step 804 After successfully updating the foregoing mapping, the MAG-CN returns a CoA update response to
  • the purpose of the CoA update response message is to respond to the CoA update message of step 803, and the name of the message may be another name as long as the message completes the above functions.
  • Step 805 The MAPS-CN returns a CoA update response to the MAPS-MN.
  • the purpose of the CoA update response message is to respond to the CoA update message of step 801, and the name of the message may be another name as long as the message completes the above functions.
  • FIG. 9 is a third embodiment of the mobility management method of the present invention.
  • the embodiment is applicable to the MAG periodically updating the MN-CN mapping table (ie, CNT) stored locally by the MAPS. As shown in Figure 9, the following steps are specifically included:
  • Step 901 After the MN accesses the PMIPv6 domain through the attach procedure, the MN successfully registers with the MAPS-MN through the sMAG-MN. MAPS-MN assigns the home network prefix (HNP1) to the MN, establishing/creating New Binding Cache Entry (BCE, Binding Cache Entry). The MAPS-MN caches the binding relationship between the MN and the sMAG-MN, and can be expressed as a mapping relationship between HNP1 and CoAl, or a mapping relationship between HNP1 and sMAG-MN addresses. The sMAG-MN establishes the mapping relationship of HNP-CoA of the MN, that is, the mapping relationship of HNP1-CoAl.
  • HNP1 home network prefix
  • BCE Binding Cache Entry
  • Step 902 When the sMAG-MN receives the uplink IP data packet sent by the MN to the CN, it checks locally whether the mapping relationship between the CN and the MAG-CN is cached, that is, the node information pointing to the CN and the MAG-CN The mapping relationship between the address information, which may be specifically represented by the mapping relationship between the HNP3 (the home network prefix of the CN) / the address of the HoA3 and the MAG-CN, or the mapping between the HNP3/HoA3 and the CoA3 of the CN. If not, the query is made to the MAPS-MN/MAPS-CN.
  • the sMAG-MN caches the query result locally; if so, directly uses the local cache mapping relationship.
  • the sMAG-MN uses the address of the MAG-CN or the CoA3 of the CN as the destination to establish a tunnel from the sMAG-MN to the MAG-CN (for example, an IP in IP tunnel).
  • the IP data packet is placed in the tunnel and sent directly to the sMAG-MN.
  • MAG-CN On the other hand, when the CN sends an IP data packet to the MN, the MAG-CN also needs to perform the above operation to directly send the IP data packet to the sMAG-MN through the tunnel from the sMAG-MN to the MAG-CN.
  • Step 903 After the sMAG-MN receives the IP data packet between the first MN and the CN, the mapping between the HoA3/HNP3 of the CN and the CoA3 of the CN is established locally, or the HoA3/HNP3 and the MAG-CN are established. The mapping relationship of addresses.
  • step 904 this step and step 903 have no fixed sequence.
  • the sMAG-MN After receiving the IP data packet between the first MN and the CN, the sMAG-MN checks whether the MN and CN CNT entries (that is, the MN-CN mapping relationship) need to be established. When the mapping relationship between the HoA3/HNP3 of the CN and the CoA3 or the HoA3/HNP3 of the CN and the address of the MAG-CN is new or not yet established, a new CNT entry is required.
  • the sMAG-MN establishes a CNT entry as shown in Figure 6b or Figure 6c.
  • the sMAG-MN maintains the CNT table locally for a period of time. If a new communication peer occurs during this time, the mapping relationship between the MN and the new communication peer needs to be added to the MN's CNT table.
  • Step 905 After the time when the sMAG-MN locally maintains the CNT table of the MN expires, the sMAG-MN sends a MN-CN mapping relationship synchronization message to the MAPS-MN, and the message carries the MN-CN mapping relationship, that is, the newly created CNT entry. If the MAPS-MN uses the method shown in FIG. 7 to update the communication peer, the message also needs to carry the address of the MAG-CN or the CoA3 of the CN. The purpose of the MN-CN mapping relationship synchronization message is to send the MN-CN mapping relationship to the MAPS-MN.
  • the name of the message can be other names as long as the message carries the above information.
  • Step 906 the MAPS-MN establishes or maintains the CNT of the MN.
  • MAPS has not yet established MN CNTs to create new CNTs. If the MAPS has established the CNT of the MN, the CNT entry is obtained from the sMAG-MN and added to the CNT. If the MN-CN mapping synchronization message also carries the address of the MAG-CN or the CoA3 of the CN, the MAPS-MN also needs to save the information locally, and the information may be stored in the CNT or separately.
  • Step 907 the MAPS-MN sends a MN-CN mapping relationship synchronization completion message to the sMAG-MN;
  • the purpose of the MN-CN mapping relationship synchronization completion message is to respond to the MN-CN mapping relationship synchronization message of step 905, and the name of the message may be other names as long as the message completes the above functions.
  • Step 908 After the sMAG-MN completes the MN-CN mapping relationship synchronization, the locally saved MN-CN mapping relationship that has been updated to the MAPS-MN, that is, the CNT, is deleted.
  • This step can be performed immediately after step 907.
  • step 909 the MN moves and replaces the MAG.
  • the MN accesses the PMIPv6 domain through the attach procedure, it sends a route request (RS, Router Solicitation) message to its tMAG-MN.
  • RS Router Solicitation
  • the sMAG-MN After the sMAG-MN detects the MN handover/movement, optionally, the sMAG-MN initiates a DeRegister procedure to the MAPS-MN. If the MAP message of the sMAG-MN is received before the MAPS-MN returns the PBA (Proxy Binding Ack) message, the MAPS-MN still needs to maintain the mapping relationship between HoAl/HNP1 and CoAl, or HoAl/HNP1 and sMAG- The mapping relationship of MN addresses.
  • PBA Proxy Binding Ack
  • Step 910 The tMAG-MN sends a PBU message to the MAPS-MN, instead of registering with the MAS-MN, the message carries the MN identity (MN ID), and the tMAG-MN is the newly assigned proxy broadcast address CoA2 and the home network prefix of the MN. HNP1.
  • Step 911 The MAPS-MN receives the PBU message, updates the binding cache list BCE of the MN, and returns a PBA message to the tMAG-MN.
  • Step 912 After the tMAG-MN receives the PBA message, the tMAG-MN returns a RA (Router Advertisement Advertisement) message to the MN.
  • RA Raster Advertisement Advertisement
  • Step 913 After receiving the PBA message, the tMAG-MN establishes a mapping of the HNP-CoA of the MN. Relationship, that is, the mapping relationship of HNP1-CoA2.
  • Steps 914-916 after the tMAG-MN receives the IP data message between the first MN and the CN (here, the new communication peer of the MN), it needs to be locally as described in steps 904-908.
  • the mapping relationship of the MN-CN is established and periodically synchronized to the MAPS-MN.
  • Step 917 A forwarding tunnel is established between the tMAG-MN and the sMAG-MN, and the address mapping of the HoA/HNP and the MAG-CN or the mapping of the HoA/HNP and the CoA is synchronized to the tMAG-MN during the establishment process.
  • the address mapping relationship table may not be synchronized to the tMAG-MN.
  • the tMAG-MN needs to re-establish the address mapping or HoA/HNP of the HoA/HNP and the MAG-CN according to step 903 or step 904.
  • CoA mapping and MN-CN mapping, at which point the tMAG-MN may resynchronize the MN-CN mapping table that the sMAG-MN has synchronized to the MAPS-MN.
  • Step 918 the sMAG-MN synchronizes the MN-CN mapping relationship that has not been synchronized to the MAPS-MN to the MAPS-MN, and the specific synchronization step is the same as steps 904-908.
  • the sMAG-MN may optionally indicate that the MAPS-MN does not synchronize the last synchronization after the terminal is switched.
  • the indication may be completed by adding an indication in the message in step 905, or may be used.
  • the new message name is implemented.
  • This step can be performed after the sMAG-MN detects that the terminal has been switched off, or is triggered by the forwarding tunnel established between the sMAG-MN and the tMAG-MN, and is executed in parallel with step 917.
  • Step 919 After the MAPS-MN performs step 910 and step 918, the MAPS-MN is triggered to initiate an update of the communication peer.
  • the specific update method is shown in Figure 7 and Figure 8.
  • Step 920 After all the communication peers of the MN complete the update, the MAPS-MN sends an update completion message to the tMAG-MN.
  • the purpose of the update completion message is to notify the MAG that the update of the communication peer has been completed.
  • the name of the message may be another name as long as the message completes the above functions.
  • Step 921 After the MAG-CN completes the mapping of the HNP1/HoAl and the tMAG-MN address of the MN or the update of the HNP1/HoAl and CoA2 mapping, that is, after the tunnel between the tMAG-MN and the MAG-CN is established, the tMAG-MN A forwarding tunnel between the tMAG-MN and the sMAG-MN is released. Thereafter, the data between the MN and the CN will be forwarded through the tMAG-MN and the MAG-CN.
  • FIG. 10 is a fourth embodiment of the mobility management method of the present invention.
  • the embodiment is applicable to the MN-CN mapping table in which the MAG periodically updates the MAPS local storage.
  • the following steps are specifically included: Steps 1001-1016, the same steps as 901-916.
  • Step 1017 A forwarding tunnel is established between the tMAG-MN and the sMAG-MN, and the mapping between the HoA/HNP and the MAG-CN or the mapping between the HoA/HNP and the CoA is synchronized to the tMAG-MN, and the sMAG-MN is localized.
  • the mapping relationship maintained by the MN-CN that has not been synchronized to the MAPS-MN is synchronized to the tMAG-MN.
  • the address mapping relationship table and the MN-CN mapping table may not be synchronized to the tMAG-MN.
  • the address mapping relationship table and the MN-CN are established by the tMAG-MN according to step 1003 or step 1004. Mapping table, at this time tMAG-MN may resynchronize the MN-CN mapping table that the sMAG-MN has synchronized to the MAPS-MN.
  • Step 1018 The tMAG-MN synchronizes the MN-CN mapping relationship that has not been synchronized to the MAPS-MN to the MAPS-MN.
  • the specific synchronization step is the same as the step 1004-1008.
  • the tMAG-MN is optional, and may indicate that the MAPS-MN does not synchronize the last synchronization after the terminal is switched.
  • the indication may be completed by adding an indication in the message of step 1005, or may be used.
  • the new message name is implemented. This step is triggered by the forwarding tunnel established between the sMAG-MN and the tMAG-MN, and is executed in parallel with 1017.
  • Steps 1020 and 1021 are the same as steps 920 and 921.
  • FIG. 11 is a fifth embodiment of the mobility management method of the present invention. This embodiment is applicable to MAPS periodically from
  • the MAG obtains the MN-CN mapping table. As shown in Figure 11, the following steps are specifically included:
  • Steps 1101-1104 are the same as steps 901-904.
  • Step 1105 After the time when the sMAG-MN locally maintains the CNT table of the MN expires, the MAPS-MN sends a MN-CN mapping relationship acquisition message to the sMAG-MN.
  • the purpose of the MN-CN mapping relationship acquisition message is to notify the sMAG-MN that the MN-CN mapping relationship needs to be obtained.
  • the name of the message can be another name as long as the message performs the above functions.
  • Step 1106 The sMAG-MN sends a MN-CN mapping synchronization message to the MAPS-MN, and the message carries the MN-CN mapping relationship, that is, the newly created CNT entry. If the MAPS-MN uses the method shown in Figure 7 to update the communication peer, the message also needs to carry the address of the MAG-CN or the CoA3 of the CN.
  • the purpose of the MN-CN mapping relationship synchronization message is to send the MN-CN mapping relationship to the MAPS-MN.
  • the name of the message can be other names as long as the message carries the above information.
  • Step 1107 the same step 906.
  • Step 1108 After the sMAG-MN completes the MN-CN mapping relationship synchronization, the locally saved MN-CN mapping relationship that has been updated to the MAPS-MN is deleted, that is, the CNT.
  • This step can be performed immediately after step 1106.
  • Steps 1109-1112 the same steps as 909-912.
  • Step 1113 After receiving the PBU message of the tMAG-MN, the MAPS-MN needs to obtain the mapping relationship from the sMAG-MN that has not been synchronized to the local MN-CN. The specific acquisition steps are synchronized to 1105-1108.
  • Step 1114 the MAPS-MN initiates an update of the communication peer.
  • the specific update method is shown in Figure 7 and Figure 8. This step can be performed at any time after step 1113.
  • Steps 1115-1119 the same steps as 913-917.
  • Steps 1120-1121 the same steps as 920-921.
  • FIG. 12 is a sixth embodiment of the mobility management method of the present invention. This embodiment is applicable to the MAG real-time update MAP-CN mapping table stored locally by MAPS. As shown in FIG. 12, the following steps are specifically included: Steps 1201-1203, the same steps as 901-903. In step 1204, there is no fixed sequence between this step and step 1203. After receiving the IP data packet between the first MN and the CN, the sMAG-MN checks whether the CNT entry of the MN and the CN (that is, the MN-CN mapping relationship) needs to be established.
  • the sMAG-MN establishes a CNT entry as shown in Figure 6b or Figure 6c.
  • Step 1205 After the MN-CN mapping relationship is established, the sMAG-MN sends the MN-CN mapping synchronization message to the MAPS-MN, and the message carries the MN-CN mapping relationship, that is, the newly created CNT entry. If the MAPS-MN uses the method shown in Figure 7 to update the communication peer, the message also needs to carry the address of the MAG-CN or the CoA3 of the CN.
  • Steps 1206-1208 the same steps as 906-908.
  • Steps 1209-1212 the same steps as 909-912.
  • Step 1213 The MAPS-MN initiates an update of the communication peer.
  • the specific update method is shown in Figure 7 and Figure 8. This step can be performed at any time after step 1210.
  • Steps 1214-1217 after the tMAG-MN receives the IP data packet between the first MN and the CN (here, the new communication peer of the MN), it needs to be locally as described in steps 1204-1208.
  • the mapping relationship of the MN-CN is established and synchronized to the MAPS-MN in real time.
  • Step 1218 the same step 917.
  • Steps 1219-1220 the same steps as 920-921.
  • FIG. 13 is a seventh embodiment of the mobility management method of the present invention. This embodiment is applicable to the update of the address mapping relationship table when the CN and the MN move simultaneously when the address mapping relationship table is updated. As shown in Figure 13, the following steps are specifically included:
  • Step 1301 The sMAG-MN receives the CoA update request sent by the mapping server of the communication peer CN during the handover.
  • the message carries the HNP of the CN, the tMAG-CN address, or the new CoA4 allocated by the tMAG-CN for the CN (ie, the HNP3 and tMAG-CN addresses or the mapping of HNP3 and CoA4).
  • Step 1302 After receiving the message, the sMAG-MN updates the address mapping relationship of the locally saved CN.
  • Step 1303 The sMAG-MN sends a CoA update message to the MAPS-MN, where the message carries the HNP of the CN, the tMAG-CN address, or the CoA4 of the CN (ie, the mapping between the HNP3 and the tMAG-CN address or the HNP3 and the CoA4 of the CN).
  • the message needs to carry a handover indication, which is used to indicate that the MAPS-MN is caused by the simultaneous handover of the CN during the MN handover, so as to be distinguished from the normal update.
  • a new message may also be used for distinguishing.
  • the information carried in the new message is the same as the information in this step except the switching indication.
  • Step 1304 After receiving the message, the MAPS-MN updates the locally saved address mapping relationship table.
  • Steps 1306-1308 the same steps 703-705.
  • Step 1309 the MAPS-MN returns a CoA update response to the sMAG-MN, and optionally, the sMAG-MN returns a CoA update response to the MAPS-CN. This step can be performed after step 1304.
  • the foregoing embodiment of the present invention describes the establishment of a forwarding tunnel between the tMAG-MN and the sMAG-MN by taking the PMIP process as an example. This embodiment is also applicable to Fast Handovers for Proxy Mobile IPv6 (FPMIP).
  • the embodiment of the present invention further provides a mobility management system, including: a mapping server and a source mobile access gateway, as shown in FIG. 15, 14, respectively, wherein:
  • the mapping server includes a handover update unit 1501, which is set to:
  • the mobile node (MN) accessing the mapping server switches from the source mobile access gateway to the target mobile access gateway, to the mobile access gateway of the opposite node (CN) of the MN Sending node information directed to the MN and address information directed to the target mobile access gateway; or, the mobile node (MN) accessing the mapping server switches from the source mobile access gateway to the target mobile access gateway And sending, to the mapping server of the CN, node information that is directed to the MN and address information that is directed to the target mobile access gateway, and the node information and the pointing point of the MN are mapped by the mapping server of the CN The address information of the target mobile access gateway is forwarded to the mobile access gateway of the CN.
  • the source mobile access gateway includes a communication peer table creation unit 1401 and a synchronization unit 1402, and the mapping server further includes a communication peer table management unit 1502, where:
  • the communication peer table creation unit 1401 is configured to: after receiving the first data packet between the MN and the CN, add the following table to the newly created communication peer table or the existing communication peer table.
  • Item a mapping relationship between node information pointing to the MN and node information pointing to the CN;
  • the synchronization unit 1402 is configured to: synchronize the communication peer table to the mapping server; and the communication peer table management unit 1502 is configured to: receive the communication peer table synchronized by the source mobile access gateway.
  • the synchronization unit 1402 is configured to synchronize the communication peer table to the mapping server by:
  • the locally created and maintained communication peer table is synchronously synchronized to the mapping server; or, after receiving the request sent by the mapping server periodically, the locally created and maintained communication peer table is synchronized to the mapping server;
  • the newly created communication peer table entry is synchronized to the mapping server.
  • the source mobile access gateway further includes an update unit 1403, configured to update the communication peer table by one of the following manners or a combination thereof:
  • the synchronization unit After the synchronization unit synchronizes the local communication peer table to the mapping server of the MN, deleting the communication peer table;
  • the corresponding entry of the offline node that is offline or shut down in the local communication peer table is deleted;
  • the mobile node attached to the source mobile access gateway is offline or powered off, the corresponding entry of the offline or shutdown mobile node in the communication peer table is deleted.
  • the communication peer table management unit 1502 is further configured to update the communication peer table by one of the following methods or a combination thereof:
  • the synchronization unit 1402 of the source mobile access gateway is further configured to: before the mapping server sends the address information of the target mobile access gateway to the mobile access gateway of the CN or the mapping server of the CN, After the request of the mapping server of the MN is received or received, the communication peer table that is not synchronized to the mapping server is sent to the mapping server; or the communication peer that is not locally synchronized to the mapping server is actively sent. The table is sent to the target mobile access gateway, and the communication mobile access gateway sends the communication peer table to the mapping server.
  • the source mobile access gateway further includes a mapping relationship table creating unit 1404, configured to locally establish an address mapping relationship table, and cache an address mapping relationship of one or more peer nodes of the MN, and the address mapping relationship Each entry of the table represents an address mapping relationship of a peer node, including node information pointing to the peer node and address information of the mobile access gateway pointing to the correspondent node.
  • a mapping relationship table creating unit 1404 configured to locally establish an address mapping relationship table, and cache an address mapping relationship of one or more peer nodes of the MN, and the address mapping relationship
  • Each entry of the table represents an address mapping relationship of a peer node, including node information pointing to the peer node and address information of the mobile access gateway pointing to the correspondent node.
  • the source mobile access gateway further includes a mapping relationship table updating unit 1405, configured to update the address mapping relationship table by one of the following methods or a combination thereof:
  • the peer node When the peer node is offline or shut down, if the mobile access gateway of the opposite node of all the mobile nodes attached thereto is different from the mobile access gateway of the offline or closed peer node, the address is deleted.
  • the source mobile access gateway further includes a mapping update unit 1406, configured to: when receiving, by the mapping server of the CN, the message of updating the address mapping relationship of the CN, The address mapping relationship of the CN in the message updates the locally stored address mapping relationship of the CN, and sends a message for updating the address mapping relationship of the CN to the mapping server, and carries a handover indication that the CN is simultaneously switched during the MN handover;
  • the handover update unit 1501 is further configured to: after receiving the message of updating the address mapping relationship of the CN, update an address mapping relationship of the CN, and send the direction to the mobile switched gateway after the CN handover The address information of the target mobile access gateway.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device so that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.
  • the handover management method provided by the embodiment of the present invention enables the MN to ensure that the transmission of IP packets between the MN and the CN is not wasted on the transmission path after the terminal moves, and meets the mobility requirement of the MN. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种移动性管理方法和系统,所述方法包括:在移动节点(MN)从源移动接入网关切换到目标移动接入网关后,所述MN的映射服务器向所述MN的对端节点(CN)的移动接入网关发送指向所述MN的节点信息和指向所述目标移动接入网关的地址信息;或者,在所述MN从所述源移动接入网关切换到所述目标移动接入网关后,所述MN的映射服务器向所述CN的映射服务器发送指向所述MN的节点信息和指向所述目标移动接入网关的地址信息,所述CN的映射服务器将所述指向所述MN的节点信息和指向所述目标移动接入网关的地址信息转发给所述CN的移动接入网关。

Description

一种移动性管理方法和系统
技术领域
本发明涉及移动通信领域, 具体涉及一种移动性管理方法和系统。
背景技术
传输控制协议 /因特网互联协议 ( Transmission Control Protocol/Internet Protocol, TCP/IP )在初始设计时未考虑终端会发生拓朴位置改变的情况, 即 TCP/IP协议本身不支持移动性。 在传统的 TCP/IP网络环境中, IP为因特网 (Internet)提供了路由功能, 它给所有节点 (包括主机和路由器)都分配了逻 辑地址, 即 IP地址, 且每台主机的各个端口都分配一个 IP地址。 IP地址包 括网络前缀和主机部分, 同一条链路上的所有主机的 IP地址通常有相同的网 络前缀和不同的主机部分。 这使得 IP可以依据目的节点的 IP地址的网络前 缀部分来进行路由选择, 从而使路由器秩序保存一条简单的网络前缀路由, 而不必为每台主机保存一条单独的路由。 在这种情况下, 由于釆用了网络前 缀路由, 因此当节点从一条链路切换到另一条链路而没有改变其 IP地址时, 该节点则不可能在新链路上接收到数据报文, 从而也就无法与其他节点进行 通信。
随着用户对移动性和信息的需求急剧上升, 越来越多的人希望在移动的 过程中高速地接入互联网, 获取急需的信息, 完成想做的事情。 因此, 移动 互联网成为未来互联网的发展方向,但是传统 TCP/IP协议不支持移动性的缺 陷, 使得对移动节点的移动性管理成为移动互联网面对的一大难题。
为了解决移动性管理问题, 业界比较流行的移动性管理技术, 如, 移动
IP ( Mobile IP, MIP ) 、 代理移动 IP ( Proxy MIP, PMIP )等, 均通过引入固 定锚点 (Anchor ) 的方式来支持终端的移动性。 例如, MIP协议使用家乡代 理( Home agent, HA )作为锚点、 PMIP协议使用本地移动性锚点( Local Mobility Anchor, LMA )作为错点。
图 1 所示的是 PMIP协议的逻辑架构, 包括移动节点 (Mobile Node, MN )、通信对端( Correspondent Node, CN )、移动接入网关( Mobile Access Gateway, MAG )以及 LMA。 其中 CN可以是固定节点, 也可以是移动节点, 即具有相应的 MAG和 LMA。 MAG是 MN的第一跳路由器, 其主要作用包 括在 MN接入时为其分配转交地址( Care of Address, CoA )以及代替 MN执 行与 MN的锚点 LMA之间的 PMIP绑定( PMIP Binding ) 。 LMA作为 MN 的锚点, 其主要作用包括为 MN分配家乡地址(Home of Address, HoA ) 以 及处理上述 PMIP绑定。 MAG与 LMA之间执行的 PMIP绑定的主要目的是 让双方均获知对方的地址、 上述 CoA和 HoA, 并将保存在本地。 此外, 在执 行 PMIP的绑定过程中,还为 MN在 MAG和 LMA之间建立了一条双向隧道。 值得说明的是, MN最后获取到的 IP地址是 LMA为其分配的 HoA。 在通常 的网络部署中, MAG—般位于拓朴较低的位置, 比如位于城域网的边缘; 而 LMA则一般位于拓朴较高的位置, 比如省干网的核心部分。 MAG与 LMA 之间实际上往往通过多跳路由器相连。
PMIP协议的移动性管理体现在随着 MN 的移动能改变当前连接到的 MAG, 同时保持 MN的 IP地址(即 HoA ) 不变。 如图 2所示, 改变当前连 接的 MAG是指从先前连接的源 MAG ( sMAG, source MAG )改变 /切换连接 到目标 MAG ( tMAG, target MAG ) 。 在改变到 tMAG以后, tMAG为 MN 分配一个新的 CoA, 并为 MN执行与 MN的锚点 LMA之间的 PMIP绑定, 更新上文提及双方保存的信息, 以及在 tMAG与 LMA之间为 MN建立新的 双向隧道。
图 2所示为 MN与 CN之间收发 IP 4艮文的过程示意图。 如图 2所示, MN与 CN之间的 IP数据报文在切换前必须经过 sMAG与 LMA之间的隧道, 在切换后必须经过 tMAG与 LMA之间的隧道。
如图 2和图 3所示,在 MN移动,并改变连接的 MAG(以下称之为切换) 前 后 , MN 与 CN 间 收发 IP 4艮文 的 路径 都 可 表 达 为 MN<->MAG<->LMA<->CN , 即 , 所有 MN与 CN之间的 IP数据报文都必须 绕路到 MN的锚点 LMA。 即使 MAG有路由功能, 且 MAG与 CN之间有 IP 网相连接(如图 1所示) , IP报文也不能直接通过 MAG收发, 存在报文传 递路径的浪费。特别是当 MN目前位置远离其锚点 LMA,且 MN目前位置距 离 CN较近时, 上述传输路径浪费问题将会更加明显。 图 3中的实线所表示 的为存在传输路径浪费的路由, 虚线所表示的则为无传输路径浪费的路由。 传输路径的浪费一方面会导致运营商传输承载资源的浪费, 导致了运营成本 增加; 另一方面增加了 ΜΝ与 CN间收发 IP报文的时延, 不利于改善用户的 业务体验; 再一方面是使大量的 IP报文汇聚到 MN的锚点 LMA (通常一个 LMA能服务很多个 MN ) , 使 LMA容易成为性能瓶颈, 增大了报文在该节 点拥塞的可能性, 导致整体网络质量下降, 造成 MN业务受阻甚至无法实现 (如, 语音视频等实时业务) 。
还值得说明的是, 上述 CN也可以位于 PMIP域, 应用上述的 PMIP移动 性管理机制 (例如, CN是另一个移动节点, 也即图 1中所示的 CN, ) 。 此 时 CN也连接到一个 MAG, 也有一个锚点 LMA。 在这种情况下, MN与 CN 之间的 IP报文的收发路径为: MN<->MN的 MAG<->MN的 LMA<->CN的 LMA<->CN的 MAG<->CN。 由此可见在这种场景下, MN与 CN间的报文收 发必须绕路经过两者的锚点 LMA, 报文传递路径的浪费更加明显, 造成的上 述不良后果更加严重。 发明内容
本发明实施例要解决的技术问题是提供一种移动性管理方法和系统, 以 解决 MAG切换后, 报文转发浪费系统资源问题。
为了解决上述问题, 本发明实施例提供了一种移动性管理方法, 包括: 在移动节点( MN )从源移动接入网关切换到目标移动接入网关后, 所述 MN的映射服务器向所述 MN的对端节点(CN )的移动接入网关发送指向所 述 MN的节点信息和指向所述目标移动接入网关的地址信息;
或者,
在所述 MN从所述源移动接入网关切换到所述目标移动接入网关后, 所 述 MN的映射服务器向所述 CN的映射服务器发送指向所述 MN的节点信息 和指向所述目标移动接入网关的地址信息, 所述 CN的映射服务器将所述指 向所述 MN的节点信息和指向所述目标移动接入网关的地址信息转发给所述 CN的移动接入网关。
可选的, 指向所述 MN的节点信息包括: 所述 MN的标识信息、 家乡地 址和家乡网络前缀之一或其组合;
指向所述目标移动接入网关的地址信息包括如下之一或其组合: 所述目 标移动接入网关的地址, 所述目标移动接入网关为其上附着的节点分配的转 交地址(CoA ) 。
可选的, 所述方法还包括,
所述 MN当前的移动接入网关收到所述 MN和 CN之间的第一个数据报 文后, 在本地新建的通信对端表或已有的通信对端表中增加如下表项: 指向 所述 MN的节点信息和指向所述 CN的节点信息的映射关系;
以及, 将所述通信对端表同步到所述 MN的映射服务器;
所述 MN当前的移动接入网关为所述源移动接入网关或目标移动接入网 关。
可选的, 将所述通信对端表同步到所述 MN的映射服务器包括: 所述 MN当前的移动接入网关周期性主动将本地创建和维护的通信对端 表同步给所述映射服务器;
或者, 接收到映射服务器周期性发送的请求后将本地创建和维护的通信 对端表同步给所述映射服务器;
或者, 所述 MN当前的移动接入网关每次新建通信对端表的表项时, 将 新建的通信对端表表项同步给所述映射服务器。
可选的, 所述方法还包括, 所述 MN当前的移动接入网关通过如下步骤 之一或其组合更新所述通信对端表:
所述 MN当前的移动接入网关在将本地的通信对端表同步给所述 MN的 映射服务器后, 删除所述通信对端表;
所述 MN当前的移动接入网关下附着的移动节点的对端节点离线或关机 后, 所述 MN当前移动接入网关将本地通信对端表中该离线或关机的对端节 点相应表项删除; 所述 MN当前移动接入网关其下附着的移动节点离线或关机时, 删除所 述通信对端表中该离线或关机的移动节点相应表项。
可选的, 所述方法还包括: 所述映射服务器通过如下步骤之一或其组合 更新所述通信对端表:
所述映射服务器删除通信对端表中建立时间超过指定时间的表项, 所述 指定时间大于所述移动接入网关与所述映射服务器之间同步通信对端表的同 步周期;
所述映射服务器接收到对端节点离线或关机的消息后, 删除本地通信对 端表中该对端节点相应表项;
所述映射服务器接收到移动节点离线或关机的消息后, 删除本地通信对 端表中该移动节点相应表项。
可选的, 所述 MN的映射服务器向 CN的移动接入网关或所述 CN的映 射服务器发送指向所述目标移动接入网关的地址信息前, 所述方法还包括: 所述源移动接入网关, 主动或接收到所述 MN的映射服务器的请求后, 将本地未同步给所述 MN的映射服务器的通信对端表发送给所述 MN的映射 服务器; 的通信对端表发送给所述目标移动接入网关, 由所述目标移动接入网关将所 述通信对端表发送给所述 MN的映射服务器。
可选的, 所述方法还包括: 所述 MN当前的移动接入网关在本地建立地 址映射关系表, 緩存所述 MN的一个或多个对端节点的地址映射关系, 所述 地址映射关系表的每个表项代表一个对端节点的地址映射关系, 包括指向该 对端节点的节点信息和指向该对端节点的移动接入网关的地址信息;
所述 MN当前的移动接入网关为所述源移动接入网关或目标移动接入网 关。
可选的, 所述方法还包括: 所述 MN当前的移动接入网关通过如下步骤 之一或其组合更新所述地址映射关系表:
将地址映射关系表中建立时间超过预设时间的表项删除; 当所述 MN当前的移动接入网关获知对端节点离线或关机时, 如果其上 附着的所有移动节点的对端节点的移动接入网关与所述离线或关机的对端节 点的移动接入网关均不相同, 则删除所述地址映射关系表中所述离线或关机 的对端节点相关表项;
当所述 MN 当前的移动接入网关获知其上附着的移动节点离线或关机 时, 如果其上附着的其它所有移动节点的对端节点的移动接入网关均不同于 所述离线或关机的移动节点的对端节点的移动接入网关, 则删除所述地址映 射关系中所述离线或关机的移动节点的对端节点相关表项。
可选的, 所述方法还包括:
所述源移动接入网关在所述 MN切换期间接收到所述 CN的映射服务器 发送的更新所述 CN的地址映射关系的消息时, 用所述消息中的 CN的地址 映射关系更新本地保存的该 CN的地址映射关系, 并发送更新所述 CN的地 址映射关系的消息给所述 MN的映射服务器, 携带 MN切换期间 CN同时切 换的切换指示;
所述 MN的映射服务器接收到所述更新所述 CN的地址映射关系的消息 后, 更新所述 CN的地址映射关系, 并向所述 CN切换后的移动接入网关发 送指向所述目标移动接入网关的地址信息。
本发明实施例还提供一种映射服务器所述映射服务器包括切换更新单 元, 其设置为:
在所述映射服务器中接入的移动节点( MN )从源移动接入网关切换到目 标移动接入网关后, 向所述 MN的对端节点(CN )的移动接入网关发送指向 所述 MN的节点信息和指向所述目标移动接入网关的地址信息;
或者, 在所述映射服务器中接入的移动节点(MN )从源移动接入网关切 换到目标移动接入网关后, 向所述 CN的映射服务器发送指向所述 MN的节 点信息和指向所述目标移动接入网关的地址信息, 通过所述 CN的映射服务 器将所述指向所述 MN的节点信息和指向所述目标移动接入网关的地址信息 转发给所述 CN的移动接入网关。
可选的, 所述指向所述 MN的节点信息包括: 所述 MN的标识信息、 家 乡地址和家乡网络前缀之一或其组合;
所述指向所述目标移动接入网关的地址信息包括如下之一或其组合: 所 述目标移动接入网关的地址, 所述目标移动接入网关为其上附着的节点分配 的转交地址(CoA ) 。
可选的, 所述通信对端表管理单元设置为: 接收所述源移动接入网关同 步过来的通信对端表, 所述通信对端表包括指向所述 MN的节点信息和指向 所述 CN的节点信息的映射关系。
可选的, 所述通信对端表管理单元还设置为通过如下方式之一或其组合 更新所述通信对端表:
删除通信对端表中建立时间超过指定时间的表项, 所述指定时间大于移 动接入网关与所述映射服务器之间同步通信对端表的同步周期;
接收到对端节点离线或关机的消息后, 删除本地通信对端表中该对端节 点^]应表项;
接收到移动节点离线或关机的消息后, 删除本地通信对端表中该移动节 点相应表项。
可选的, 所述切换更新单元还设置为: 接收到所述源移动接入服务器发 送的更新所述 CN的地址映射关系的消息后, 更新所述 CN的地址映射关系, 并向所述 CN切换后的移动接入网关发送指向所述目标移动接入网关的地址 信息,所述 CN的地址映射关系, 包括指向该 CN的节点信息和指向该 CN的 移动接入网关的地址信息。
本发明实施例还提供一种接入网关, 当在映射服务器中接入的移动节点 ( MN )从源移动接入网关切换到目标移动接入网关后, 所述接入网关作为所 述源移动接入网关时, 包括通信对端表创建单元和同步单元, 其中:
所述通信对端表创建单元设置为: 收到所述 MN和所述 MN的对端节点 ( CN )之间的第一个数据报文后, 在本地新建的通信对端表或已有的通信对 端表中增加如下表项: 指向所述 MN的节点信息和指向所述 CN的节点信息 的映射关系;
所述同步单元设置为: 将所述通信对端表同步到所述映射服务器; 可选的, 所述同步单元是设置为通过如下方式将所述通信对端表同步到 所述映射服务器:
周期性主动将本地创建和维护的通信对端表同步给所述映射服务器; 或者, 接收到映射服务器周期性发送的请求后将本地创建和维护的通信 对端表同步给所述映射服务器;
或者, 每次新建通信对端表的表项时, 将新建的通信对端表表项同步给 所述映射服务器。
可选的, 上述接入网关还包括更新单元, 其设置为通过如下方式之一或 其组合更新所述通信对端表:
在所述同步单元将本地的通信对端表同步给所述 MN的映射服务器后, 删除所述通信对端表;
所述源移动接入网关下附着的移动节点的对端节点离线或关机后, 将本 地通信对端表中该离线或关机的对端节点相应表项删除;
所述源移动接入网关下附着的移动节点离线或关机时, 删除所述通信对 端表中该离线或关机的移动节点相应表项。
可选的, 所述同步单元还设置为: 在所述映射服务器向 CN的移动接入 网关或所述 CN的映射服务器发送指向所述目标移动接入网关的地址信息前, 主动或接收到所述 MN的映射服务器的请求后, 将本地未同步给所述映射服 务器的通信对端表发送给所述映射服务器; 或者, 主动将本地未同步给所述 映射服务器的通信对端表发送给所述目标移动接入网关, 由所述目标移动接 入网关将所述通信对端表发送给所述映射服务器。
可选的, 上述接入网关还包括映射关系表创建单元, 其设置为: 在本地 建立地址映射关系表, 緩存所述 MN的一个或多个 CN的地址映射关系, 所 述地址映射关系表的每个表项代表一个 CN的地址映射关系,包括指向该 CN 的节点信息和指向该 CN的移动接入网关的地址信息。
可选的, 上述接入网关还包括映射关系表更新单元, 其设置为通过如下 方式之一或其组合更新所述地址映射关系表:
将地址映射关系表中建立时间超过预设时间的表项删除; 获知对端节点离线或关机时, 如果其上附着的所有移动节点的对端节点 的移动接入网关与所述离线或关机的对端节点的移动接入网关均不相同, 则 删除所述地址映射关系表中所述离线或关机的对端节点相关表项;
获知其上附着的移动节点离线或关机时, 如果其上附着的其它所有移动 节点的对端节点的移动接入网关均不同于所述离线或关机的移动节点的对端 节点的移动接入网关, 则删除所述地址映射关系中所述离线或关机的移动节 点的对端节点相关表项。
可选的, 上述接入网关还包括映射更新单元, 其设置为: 在所述 MN切 换期间接收到所述 CN的映射服务器发送的更新所述 CN的地址映射关系的 消息时, 用所述消息中的 CN的地址映射关系更新本地保存的该 CN的地址 映射关系, 并发送更新所述 CN的地址映射关系的消息给所述映射服务器, 携带所述 MN切换期间 CN同时切换的切换指示。
本发明实施例提供的切换管理方法, 实现当终端移动后, 使得 MN在改 变 MAG后, 保证 MN与 CN之间 IP报文的收发无传输路径上的浪费, 满足 MN的移动性需求。
附图概述
附图说明用来提供对本发明的进一步理解, 并且构成说明书的一部分, 与本发明的实施例一起用于解释本发明, 并不构成对本发明的限制。 在附图 中:
图 1是现有 PMIP协议的逻辑架构图;
图 2是根据现有 PMIP协议的 MN与 CN之间收发 IP报文的过程示意图; 图 3是根据现有 PMIP协议存在的传输路径浪费问题的示意图; 图 4是改造后的 PMIP协议的逻辑架构图;
图 5是根据改造后的 PMIP协议的 MN与 CN之间收发 IP报文的过程示 意图;
图 6a为地址映射关系表的实例示意图;
图 6b、 6c为通信对端表的示例示意图; 图 7是本发明移动性管理方法实施例一的示意图;
图 8是本发明移动性管理方法实施例二的示意图;
图 9是本发明移动性管理方法实施例三的示意图;
图 10是本发明移动性管理方法实施例四的示意图;
图 11是本发明移动性管理方法实施例五的示意图;
图 12是本发明移动性管理方法实施例六的示意图;
图 13是本发明移动性管理方法实施例七的示意图;
图 14是本发明实施例源移动接入网关框图;
图 15是本发明实施例映射服务器框图。 本发明的较佳实施方式
下文中将结合附图对本发明的实施例进行详细说明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互任意组合。
为了更清楚的描述本发明实施例的内容,在本发明实施例中做如下规定:
CN为 MN的通信对端节点, CN可以有多个。
sMAG-MN/MAG-MN是指 MN当前接入的 MAG, 该 MAG为 MN分配 的代理转交地址为 CoAl。
tMAG-MN是指 MN移动后的 MAG, 即切换后的 MN接入的 MAG, 该 MAG为 MN分配的代理转交地址为 CoA2。
MAG-CN是指 CN当前接入的 MAG,该 MAG为 CN分配的代理转交地 址为 CoA3。
tMAG-CN是指 CN移动后的 MAG, 即切换后的 CN接入的 MAG, 该 MAG为 CN分配的代理转交地址为 CoA4。
MAPS-MN是指 MN接入的 MAPS , 该 MAPS为 MN分配的家乡网络前 缀(Home Network Prefix, HNP )为 HNPl , MN根据 HNPl配置得到的家乡 地址为 ΗοΑ1。 MAPS-CN是指 CN接入的 MAPS ,该 MAPS为 CN分配的家乡网络前缀 为 HNP3 , CN根据 HNP3配置得到的家乡地址为 HoA3。
在本发明实施例中, MAG的地址(包括 MN的 MAG还 CN的 MAG)可以 是接口地址, 也可以是其它任何可以代表 MAG的地址。
需要说明的是,本发明实施例中所说的指向所述 MN或 CN的节点信息, 是用于表明是哪一个 MN或 CN的信息, 可以是 MN或 CN的下述信息之一 或其组合: 标识(ID )、 家乡地址和家乡网络前缀; 本发明所说的指向 MAG 的地址信息是用于表明哪一个 MAG是 MN或 CN附着或曾附着的 MAG的信
( CoA ) , 还可以是 MAG的地址和 CoA的组合。 指向所述 MN或 CN的节 点信息具体釆用什么信息表示, 指向 MAG的地址信息具体釆用什么信息表 示, 均由具体应用场景或相应网元可能得到的信息决定, 本发明对此不做限 定, 实施例中的具体描述仅为示意, 不应作为对本发明的限制。
具体地 ,指向 sMAG-MN地址信息指所述 sMAG-MN的地址、 sMAG-MN 为所述 MN分配的代理转交地址( CoA )或前两个信息的组合;指向 tMAG-MN 的地址信息指所述 tMAG-MN的地址、 tMAG-MN为所述 MN分配的代理转 交地址( CoA )或前两个信息的组合; 指向 MN的对端节点 CN的 MAG-CN 的地址信息指所述 MN的对端节点 CN的 MAG-CN的地址、 MN的对端节点 CN的 MAG-CN为所述 CN分配的代理转交地址( CoA )或前两个信息的组 合。
需要说明的是, 映射服务器( Mapping server, MAPS )为 MN或 CN分配 的是家乡网络前缀(HNP ) , MN或 CN收到路由器通告消息 (该消息中携 带 HNP )后, 进行地址配置, 获得源自 HNP的家乡地址 HoA。 在 PMIPv6 中, 一个 HNP只能分配给一个终端, 也就是说, HNP和 HoA都能唯一指代 一个特定的 MN。 MAPS/MAG有可能不知道 MN或 CN配置的 HoA, 在具体 的网络应用中, MAPS/MAG也有可能获得 MN 或 CN 配置的 HoA。 当 MAPS/MAG不知道 HoA时, MAPS/MAG中的映射关系为 HNP与 CoA或 MAG地址的映射关系, 当 MAPS/MAG知道 HoA时, MAPS/MAG中的映射 关系可以为 HoA与 CoA或 MAG地址的映射关系,也可以为 HNP与 CoA或 MAG地址的映射关系。
对现有的 PMIP机制进行改造, 图 4为改造后的 PMIP协议架构。
与现有 PMIP协议的逻辑架构(如图 1所示)相比, 改造后的 PMIP协议 架构所包含的网元为移动节点 MN、 通信对端 CN、 移动接入网关 MAG以及 MAPS。 改造后的 PMIP协议架构不再具有 LMA网元。 其中 CN可以是固定 节点, 也可以是移动节点, 即具有相应的 MAG和 MAPS。
MAG是 MN的第一跳路由器,其主要作用除了现有的 PMIP架构中的为 MN分配转交地址 CoA,以及代替 MN执行与 MN的锚点 MAPS之间的 PMIP 绑定外, 还需要具备如下功能:
向 MAPS查询, 获得通信对端 CN当前连接的 MAG ( MAG-CN ) 的地 址或 CN的转交地址 CoA。
在 MN的 MAG ( MAG-MN )和 CN的 MAG之间建立双向隧道, 转发 MN与 CN之间的 IP数据 4艮文。
MAPS保留了 LMA功能中的处理 MN注册、注销及更新功能 ,分配 HNP 功能, 建立和维护 BCE功能, 但不作为 MN的锚点, MN与 CN之间的 IP 数据报文, 不需要经过 MAPS。 MAPS需要保存当前 MAG-MN的地址和 /或 MN的 CoA, 并以指向 MN的节点信息作为索引, 例如以 MN的 ID、 HoA或 者 MN的家乡网络前缀( Home Network Prefix, HNP )作为索引, 以供 MN 的通信对端 CN或 CN的 MAG根据 MN的相关信息来查询。
图 5所示为应用改造后的 PMIP架构时, MN与 CN之间收发 IP报文的 过程示意图。如图 5所示, MN与 CN之间的 IP数据报文需要经过 MAG-MN 与 MAG-CN之间的隧道。
当 MN向 CN发送上行 IP报文时 , MN需要将 IP报文发送到 MAG-MN。 后续与现有 PMIP机制所不同的是, 在本发明实施例中 MAG-MN需要查询 MAG-CN的地址。 在查询到 MAG-CN的地址(如 MAG-CN的 IP地址后 ) , MAG-MN用 MAG-CN的地址作为终点, 建立 MAG-MN到 MAG-CN的隧道 (如, IP in IP隧道),同时将上述 IP报文放在隧道中,直接发送给 MAG-CN。 当 MAG-CN收到隧道中传递来的 IP报文以后, 将 IP报文发送给 CN。
需要说明的是, MAG-MN也可以查询 CN的 CoA, 用 CN的 CoA地址 代替上述的 MAG-CN的地址, 也能达到相同的目的。 此时, MAG-MN使用 CoA作为终点, 建立 MAG-MN到 MAG-CN的隧道, 效果等同。 还值得说明 的是, MAG-MN在查询 CN的 MAG-CN的地址(或 CN的 CoA ) 时, 首先 在本地緩存中查询, 若查询不到再到其他网元上查询。 例如, 可以到 CN的 锚点 MAPS ( MAPS-CN )根据 CN的 HoA来查询。 查询到所需的结果以后, MAG-MN再将查询结果緩存在本地。将查询结果緩存在本地的好处是能避免 频繁的到其他网元去执行查询操作。
同样道理, CN向 MN发送下行 IP报文时, 也使用上述类似的方法, 原 理相同, 不再赘述。 使用本发明的这种方法, MN与 CN间收发 IP报文的路 径变为 MN<->MN的 MAG<->CN的 MAG<->CN, 无需经过 MN (或者 MN 以及 CN ) 的锚点 MAPS网元, 避免了传输路径的浪费等一系列问题。
应用上述改造后的 PMIP机制 , 当 MN移动, 并需要从其 sMAG-MN切 换到目标 tMAG-MN 时, 直接使用现有的 PMIP切换机制会致使在切换后 MAG-CN仍然将 CN发给 MN的 IP报文发给 sMAG-MN, 因为 MAG-CN本 地緩存的 MN的 MAG地址仍然是 sMAG-MN, 而此时的 MN 已经不在该 在本发明实施例中, 为了避免 MAG向 MAPS的频繁的查询通信对端的 MAG的地址或通信对端的 CoA (避免每收到 MN发给 CN的一个 IP报文, 都要去查询一次 ) , MAG-MN需要将上述 MAG-CN的地址或 CN的 CoA緩 存到本地, 同时以 CN的 HoA或 HNP或 ID作为索引, 组成一个对端节点的 映射关系 ,如 CN的 HoA或 HNP或 ID,映射到 MAG-CN地址或 CN的 CoA, 简称其为地址映射关系。 当 MN的 CN不止一个时, MAG-MN需要本地緩存 多个上述的地址映射关系, 此时就构成了一张地址映射关系表, 如图 6a所示 为该地址映射关系表的一种结构。 地址映射关系表每个表项包括指向 CN的 节点信息和指向 MAG-CN的地址信息。 图 6a中仅为一种示例, 其中, 索引 项中携带指向 CN的节点信息, 除了可以为 CN的 HoA, 也可以是 CN的 HNP或 ID, 或者 HoA/HNP/ID之中任意多项组合, 值项携带指向 MAG-CN 的地址信息 , 可以是 MAG-CN的地址或者 CN的 CoA或者 MAG-CN的地址 与 CN的 CoA的组合。
其中,该地址映射关系表是 MAG上保存的一张全局表, 即是该 MAG下 附着的所有 MN的所有对端节点的地址映射关系都保存在同一张表。 值得说 明的是, MN自身的地址映射关系,即 MN的 HoA或 HNP或 ID与 MAG-MN 地址或 MN的 CoA的映射关系也可以保存在该地址映射关系表中。
对于该地址映射关系表, MAG-MN可以釆用下列方式来删除其中的表 项。 下列方式可以单独釆用, 也可以组合釆用。
A1: 老化机制。 MAG-MN设置老化定时器 T3 , 当 T3超时后, MAG-MN 将地址映射关系表中的相应的表项删除。 对于每个地址映射关系表项都需要 启动一个老化定时器。
A2: 对端通知机制。 当 MAPS-CN判断出 CN离线或关机后, 将 CN离 线或关机的消息通知 MAPS-MN, MAPS-MN收到通知消息后, 删除通信对 端表中相应的 CN表项。 可选的 , 此时 MAPS-MN通知 MAG-MN删除本地 维护的通信对端表相应的 CN表项。 MAG-MN收到消息后, 将本地维护的通 信对端表中相应的 CN表项删除, 同时在地址映射关系表检查是否还有其它 通信对端 (不仅仅是 MN的通信对端, 而是 MAG-MN上附着的所有终端的 通信对端)在继续使用地址表项中相应的映射关系, 即检查是否还有其它通 信对端的 MAG与 CN的 MAG是相同的 MAG, 若所有通信对端的 MAG都 不再是 CN的 MAG, 则 MAG-MN删除地址映射关系表中相应的表项。 若本 地维护的通信对端表中没有 CN表项,则 MAG-MN仍然需要进行上述地址映 射关系表的检查。
A3: 本端通知机制。 当 MN离线或关机时 , MAG-MN删除 MN的所有 信息, 同时进行如 A2所述的地址映射关系表的检查。 其中, 如果 MAG-MN 上附着的其它所有移动节点的对端节点的移动接入网关均不同于所述离线或 关机的 MN的对端节点的移动接入网关, 则删除所述地址映射关系中所述离 线或关机的 MN的对端节点相关表项。 另外, MAPS 或 MAG 上需要本地创建、 维护 MN 的通信对端表 ( Correspondent Node Table, CNT ) , 也称 MN-CN映射表。 CNT可能釆用 两种形式:
第一种形式为局部表, 如图 6b所示, MAG/MAPS需为其下附着的每个 MN都创建、 维护一张通信对端表, 并可将其保存在 MN的绑定信息中, 通 过 MN的 HoA或 HNP或 ID能够找到该表,并在该表中能够获知该 MN的通 信对端的 HoA或 HNP或 ID。
第二种形式为全局表, 如图 6c所示, MAG/MAPS 为其下附着的全体 MN仅维护一张表, 将所有 MN的通信对端信息都填入这张表, 并以 MN的 HoA或 HNP或 ID作为索引。 在该表中, 也能获知指定 MN的通信对端 CN 的 HoA或 HNP或 ID。
MAG在收到 MN与 CN之间的 IP数据报文时, 从数据报文中获得通信 对端的 HoA或 HNP, 或者获得通信对端的 ID, 并建立如上所述的 MN-CN 映射表。
MAG需要将本地的 CNT同步到 MAPS,并删除已同步到 MAPS的 CNT。 其中, 可以釆取如下方式之一进行同步:
在每新建 CNT的一个表项后(通常 MN会有多个通信对端), 可以立即 同步该新建表项到 MAPS, 由 MAPS来新建或更新该 CNT;
MAG也可以在本地维护 CNT—段时间,然后定期将 CNT同步到 MAPS, 由 MAPS新建或更新该 CNT;
MAG也可以不主动同步 CNT到 MAPS, 由 MAPS定期向 MAG查询获 得新建的 CNT表项。
需要说明的是, MAG认为本地维护的 CNT总是没有同步到 MAPS 的 CNT表项, MAG根据本地维护的 CNT中是否存在通信对端的信息来判断该 通信对端是否是新的通信对端, 当 MAG本地维护的 CNT中没有某个通信对 端的信息时, MAG判断该通信对端是新的通信对端, 需要新建 CNT表项, 立即 /定期同步到 MAPS。 此时可能会造成某些 CNT表项的重复更新。 MAPS 将从 MAG获得所有 CNT表项组合成一个完整的 CNT,对于重复更新的表项, MAPS需要覆盖原有表项。
依赖该通信对端表, MAPS-MN在 MN通过 tMAG-MN注册到 MAPS后 相关信息的过程, 将 MN的 tMAG-MN地址或新 CoA通知给相关的 CN的 MAG (即 MAG-CN ) , 如实施例一、 二所示。
对于该通信对端表, MAG-MN可以釆用下列方式来删除其中的表项。 下 列方式可以单独釆用, 也可以组合釆用。
B1 : 老化机制。 MAG-MN设置同步定时器 T1 , 当 T1超时后, MAG-MN 将在 T1时间内创建并维护的通信对端表同步给 MAPS-MN, 同时删除本地维 护的通信对端表并重启同步定时器 Tl。 或者 MAPS-MN设置同步定时器 Tl , 当 T1超时后,从 MAG-MN获取 MAG-CN在 T1时间内创建并维护的通信对 端表并重启同步定时器 T1 , 同时 MAG-MN删除本地维护的通信对端表。 值 得说明的是 T1的最小取值可以为 0, 即实时同步, 此时可以不设置 Tl。
Β2: 对端通知机制。 当对端 MAPS-CN判断出通信对端离线或关机后, 将 CN离线或关机的消息通知 MAPS-MN, MAPS-MN收到通知消息后,删除 通信对端表中相应的 CN表项。 可选的 , 此时 MAPS-MN通知 MAG-MN删 除本地维护的通信对端表相应的 CN表项。 MAG-MN收到消息后, 将本地维 护的通信对端表中相应的 CN表项删除,若没有该表项,则 MAG-MN忽略该 消息或者认为已经成功删除。
B3: 本端通知机制。 当 MN离线或关机时, MAG-MN删除该 MN的所 有信息, 包括本地维护的通信对端表。
对于该通信对端表, MAPS-MN 可以釆用下列方式来删除其中的表项。 下列方式可以单独釆用, 也可以组合釆用。
C1:老化机制。当 MAPS-匪从 MAG-匪获得通信对端表后 , MAPS-MN 需要本地启动一个老化定时器 T2, 该定时器需要比 MAG-CN本地维护通信 对端表的时间 T1长。 对于每个 CNT表项都需要启动一个老化定时器, 或者 对于从 MAG-MN—批获得的 CNT表项只启动一个老化定时器。 当 T2超时 后 , MAPS-MN需要删除对应的表项。对于从 MAG-MN获得的重复的通信对 端表项, MAPS-MN需要终止原 T2, 并重新启动 T2。
C2: 对端通知机制。 当对端 MAPS-CN判断出通信对端离线或关机后, 删除 MAPS-CN上的关于 CN的所有信息,同时将 CN离线或关机的消息通知 MAPS-MN, MAPS-MN收到通知消息后,删除通信对端表中相应的 CN表项。
C3: 本端通知机制。 当 MN离线或关机时, MAG-MN将 MN离线或关 机的消息通知 MAPS-MN, MAPS-MN删除 MN的所有信息, 包括通信对端 表, 同时需要将 MN离线或关机的消息根据通信对端表通知所有 MN的通信 对端 CN的 MAG-CN , 可以直接通知 MAG-CN , 也可以先通知 MAPS-CN , 由 MAPS-CN通知 MAG-CN, MAG-CN的处理如 B2中对端通知机制所述, 此时的 MN相当于 CN的通信对端。
本发明实施例提供一种移动性管理方法, 包括:
在移动节点( MN )从源移动接入网关切换到目标移动接入网关后, 所述 MN的映射服务器向所述 MN的对端节点(CN )的移动接入网关发送指向所 述 MN的节点信息和指向所述目标移动接入网关的地址信息;
或者,
在所述 MN从所述源移动接入网关切换到所述目标移动接入网关后, 所 述 MN的映射服务器向所述 CN的映射服务器发送指向所述 MN的节点信息 和指向所述目标移动接入网关的地址信息, 所述 CN的映射服务器将所述指 向所述 MN的节点信息和指向所述目标移动接入网关的地址信息转发给所述 CN的移动接入网关。
其中, 指向节点的节点信息包括: 所述节点的标识信息、 家乡地址和家 乡网络前缀之一或其组合; 指向移动接入网关的地址信息包括如下之一或其 组合: 所述移动接入网关的地址, 所述移动接入网关为其上附着的节点分配 的转交地址(CoA ) ; 所述节点为移动节点或对端节点, 所述移动接入网关 包括目标移动接入网关。 其中, 所述 MN当前的移动接入网关收到所述 MN和 CN之间的第一个 数据报文后,在本地新建的通信对端表或已有的通信对端表中增加如下表项: 指向所述 MN的节点信息和指向所述 CN的节点信息的映射关系; 以及, 将所述通信对端表同步到所述 MN的映射服务器;
所述 MN当前的移动接入网关为所述源移动接入网关或目标移动接入网 关。
将所述通信对端表同步到所述 MN的映射服务器包括:
所述 MN当前的移动接入网关周期性主动将本地创建和维护的通信对端 表同步给所述映射服务器;
或者, 接收到映射服务器周期性发送的请求后将本地创建和维护的通信 对端表同步给所述映射服务器;
或者, 所述 MN当前的移动接入网关每次新建通信对端表的表项时, 将 新建的通信对端表表项同步给所述映射服务器。
其中, 所述 MN当前的移动接入网关通过如下方式之一或其组合更新所 述通信对端表:
所述 MN当前的移动接入网关在将本地的通信对端表同步给所述 MN的 映射服务器后, 删除所述通信对端表;
所述 MN当前的移动接入网关下附着的移动节点的对端节点离线或关机 后, 所述 MN当前移动接入网关将本地通信对端表中该离线或关机的对端节 点相应表项删除;
所述 MN当前移动接入网关其下附着的移动节点离线或关机时, 删除所 述通信对端表中该离线或关机的移动节点相应表项。
其中,所述映射服务器通过如下方式之一或其组合更新所述通信对端表: 所述映射服务器删除通信对端表中建立时间超过指定时间的表项, 所述 指定时间大于所述移动接入网关与所述映射服务器之间同步通信对端表的同 步周期;
所述映射服务器接收到对端节点离线或关机的消息后, 删除本地通信对 端表中该对端节点相应表项;
所述映射服务器接收到移动节点离线或关机的消息后, 删除本地通信对 端表中该移动节点相应表项。
所述 MN的映射服务器向 CN的移动接入网关或所述 CN的映射服务器 发送指向所述目标移动接入网关的地址信息前, 还包括:
所述源移动接入网关主动或接收到所述 MN的映射服务器的请求后将本 地未同步给所述 MN的映射服务器的通信对端表发送给所述 MN的映射服务 器; 的通信对端表发送给所述目标移动接入网关, 由所述目标移动接入网关将所 述通信对端表发送给所述 MN的映射服务器。
其中, 所述方法还包括: 所述 MN当前的移动接入网关在本地建立地址 映射关系表, 緩存所述 MN的一个或多个对端节点的地址映射关系, 所述地 址映射关系表的每个表项代表一个对端节点的地址映射关系, 包括指向该对 端节点的节点信息和指向该对端节点的移动接入网关的地址信息; 所述 MN 当前的移动接入网关为所述源移动接入网关或目标移动接入网关。
所述 MN当前的移动接入网关通过如下方式之一或其组合更新所述地址 映射关系表:
将地址映射关系表中建立时间超过预设时间的表项删除;
当所述 MN当前的移动接入网关获知对端节点离线或关机时, 如果其上 附着的所有移动节点的对端节点的移动接入网关与所述离线或关机的对端节 点的移动接入网关均不相同, 则删除所述地址映射关系表中所述离线或关机 的对端节点相关表项;
当所述 MN 当前的移动接入网关获知其上附着的移动节点离线或关机 时, 如果其上附着的其它所有移动节点的对端节点的移动接入网关均不同于 所述离线或关机的移动节点的对端节点的移动接入网关, 则删除所述地址映 射关系中所述离线或关机的移动节点的对端节点相关表项。
其中, 所述源移动接入网关在所述 MN切换期间接收到所述 CN的映射 服务器发送的更新所述 CN的地址映射关系的消息时, 用所述消息中的 CN 的地址映射关系更新本地保存的该 CN的地址映射关系,并发送更新所述 CN 的地址映射关系的消息给所述 MN的映射服务器, 携带 MN切换期间 CN同 时切换的切换指示;
所述 MN的映射服务器接收到所述更新所述 CN的地址映射关系的消息 后, 更新所述 CN的地址映射关系, 并向所述 CN切换后的移动接入网关发 送指向所述目标移动接入网关的地址信息。
实施例一
图 7是本发明移动性管理方法实施例一, 本实施例适用于 MAPS-MN直 接通知通信对端 MAG-CN更新 MN的 HNP-tMAG-MN地址映射或 HNP-新 CoA映射。 如图 7所示, 具体包括以下步骤:
步骤 701 ,受到 MAG-MN的触发,具体触发参见实施例四-七, MAPS-MN 决定通知 MAG-CN更新 MN的 HNP-MAG-MN地址映射或 HNP-CoA的映射。 MAPS-MN在通信对端表中获取 MN的所有 CN, 同时根据 CN查询对应的 MAG-CN地址或 CN的 CoA, 然后向该 MAG-CN发送 CoA更新消息, 消息 中携带 MN的 HNP ,还携带 tMAG-MN地址或 CoA2 (即 HNP1与 tMAG-MN 地址或 HNP1与 CoA2的映射 ) 。
在本实施例中,为了使 MAPS-MN可以查询到 MAG-CN的地址或 CN的 CoA, 当 MAG-MN向 MAPS-MN同步 CNT, 或 MAPS-MN向 MAG-MN查 询 CNT 时, MAG-MN需要同时将 MAG-CN地址或 CN 的 CoA通知给 MAPS-MN, MAPS-MN也需要在本地保存该信息。
CoA 更新消息的目的就是将 HNP1 与 tMAG-MN 的地址映射或者 HNPl-CoA2 映射发送给 MAG-CN。 消息的名称可以是其它名称, 只要该消 息携带了上述信息即可。
步骤 702, MAG-CN收到该消息后,更新本地保存的 HNP1与 sMAG-MN 的地址映射或者 HNPl-CoAl映射关系为 HNP1与 tMAG-MN的地址映射或者 HNPl-CoA2映射。
步骤 703 , MAG-CN在成功更新上述映射后, 返回 CoA 更新响应给 MAPS-匪。 CoA更新响应消息的目的就是回应步骤 701的 CoA更新消息,消息的名 称可以是其它名称, 只要该消息完成上述功能即可。
步骤 704, 本步骤为可选步骤, 当 MAPS-CN需要直接通知 CN的通信对 端接入的 MAG更新 CN切换后的 MAG地址或 CN的新 CoA时执行步骤 704 和步骤 705。 MAG-CN向 MAPS-CN发送 CoA更新消息, 消息中携带 MN的 HNP、 tMAG-MN地址或 CoA2(即 HNPl与 tMAG-MN地址或 HNPl与 CoA2 的映射) 。
CoA 更新消息的目的就是将 HNP1 与 tMAG-MN 的地址映射或者 HNPl-CoA2映射发送给 MAPS-CN。 消息的名称可以是其它名称, 只要该消 息携带了上述信息即可。
步骤 705, 本步骤为可选步骤, MAPS-CN收到该 CoA更新消息后, 更 新本地保存的 HNP1与 sMAG-MN的地址映射或者 HNPl-CoAl映射关系为 HNP1与 tMAG-MN的地址映射或者 HNPl-CoA2映射, 并向 MAG-CN返回
CoA更新响应消息。
CoA更新响应消息的目的就是回应步骤 704的 CoA更新消息,消息的名 称可以是其它名称, 只要该消息完成上述功能即可。
MAPS-CN 和 MAPS - MN 也可能是同一个 MAPS。 此时, 不需要 MAPS-MN与 MAPS-CN之间进行消息交互, 即不需要执行步骤 704和 705。
实施例二
图 8是本发明移动性管理方法实施例二, 本实施例适用于 MAPS-MN通
HNP-新 CoA映射。 如图 8所示, 具体包括以下步骤:
步骤 801 ,受到 MAG-MN的触发,具体触发参见实施例四-七。 MAPS-MN 决定通知 MAG-CN更新 MN的 HNP-MAG-MN地址映射或 HNP-CoA的映射。 MAPS-MN在通信对端表中获取 MN的所有 CN,然后向 MAPS-CN发送 CoA 更新消息,消息中携带 MN的 HNP, 以及, tMAG-MN地址或 CoA2 (即 HNP1 与 tMAG-MN地址或 HNP1与 CoA2的映射) , 同时需要携带 CN的 HNP或 Ho A或 ID。
CoA 更新消息的目的就是将 HNP1 与 tMAG-MN 的地址映射或者 HNPl-CoA2映射发送给 MAPS-CN。 消息的名称可以是其它名称, 只要该消 息携带了上述信息即可。
步骤 802 , MAPS-CN收到该 CoA更新消息后,根据消息中携带的 CN的
HNP或 HoA或 ID查询对应的 MAG-CN地址或 CN的 CoA,然后向该 MAG-CN 发送 CoA更新消息, 消息中携带 MN的 HNP、 tMAG-MN地址或 CoA2 (即 HNP1与 tMAG-MN地址或 HNP1与 CoA2的映射 ) 。
CoA 更新消息的目的就是将 HNP1 与 tMAG-MN 的地址映射或者 HNPl-CoA2 映射发送给 MAG-CN。 消息的名称可以是其它名称, 只要该消 息携带了上述信息即可。
步骤 803 , MAG-CN收到该消息后,更新本地保存的 HNP1与 sMAG-MN 的地址映射或者 HNPl-CoAl映射关系为 HNP1与 tMAG-MN的地址映射或者 HNPl-CoA2映射。
步骤 804 , MAG-CN在成功更新上述映射后, 返回 CoA 更新响应给
MAPS-CN„
CoA更新响应消息的目的就是回应步骤 803的 CoA更新消息,消息的名 称可以是其它名称, 只要该消息完成上述功能即可。
步骤 805 , MAPS-CN返回 CoA更新响应给 MAPS-MN。
CoA更新响应消息的目的就是回应步骤 801的 CoA更新消息,消息的名 称可以是其它名称, 只要该消息完成上述功能即可。
实施例三
图 9是本发明移动性管理方法实施例三, 本实施例适用于 MAG定期更 新 MAPS本地存储的 MN-CN映射表(即 CNT ) 。 如图 9所示, 具体包括以 下步骤:
步骤 901 , MN通过附着过程接入到 PMIPv6域内后,通过 sMAG-MN在 MAPS-MN成功注册。 MAPS-MN为 MN分配家乡网络前缀 (HNP1), 建立 /更 新绑定緩存列表(BCE, Binding Cache Entry ) 。 MAPS-MN緩存 MN 与 sMAG-MN的绑定关系,具体可表现为 HNP1与 CoAl的映射关系,或者 HNP1 与 sMAG-MN地址的映射关系。 sMAG-MN建立 MN的 HNP-CoA的映射关 系, 即 HNP1 -CoAl的映射关系。
步骤 902, sMAG-MN收到 MN的发送给 CN的上行 IP数据报文时, 在 本地检查是否緩存有 CN与 MAG-CN的映射关系即指向所述 CN的节点信息 与指向所述 MAG-CN的地址信息之间的映射关系,该映射关系可具体表现为 HNP3 ( CN的家乡网络前缀) /HoA3与 MAG-CN的地址的映射关系, 或者 HNP3/HoA3 与 CN 的 CoA3 之间 的映射关系 , 若没有, 则向 MAPS-MN/MAPS-CN查询, 获得上述映射关系后, sMAG-MN将查询结果緩 存在本地; 若有则直接使用本地緩存的映射关系。 sMAG-MN使用 MAG-CN 的地址或 CN的 CoA3作为终点, 建立 sMAG-MN到 MAG-CN的隧道(如, IP in IP隧道 ) , 同时将上述 IP数据报文放在隧道中, 直接发送给 MAG-CN。 反之, 当 CN发送 IP数据报文给 MN时, MAG-CN也需要做上述操作, 将 IP数据报文通过 sMAG-MN到 MAG-CN的隧道直接发送给 sMAG-MN。
步骤 903 , sMAG-MN收到第一个 MN与 CN之间的 IP数据报文后 , 需 要在本地建立 CN 的 HoA3/HNP3 与 CN 的 CoA3 的映射关系, 或者建立 HoA3/HNP3与 MAG-CN的地址的映射关系。
步骤 904,本步骤与步骤 903没有固定的先后顺序。 sMAG-MN收到第一 个 MN与 CN之间的 IP数据报文后, 检查是否需要建立 MN与 CN的 CNT 表项 (即 MN-CN映射关系) 。 当 CN的 HoA3/HNP3与 CN的 CoA3或者 HoA3/HNP3与 MAG-CN的地址的映射关系是新建的或者还未建时, 需要新 建 CNT表项。 sMAG-MN建立如图 6b或图 6c所示的 CNT表项。 sMAG-MN 本地维护该 CNT表一段时间, 若在该时间内出现新的通信对端, 需要将 MN 与该新通信对端的映射关系添加到 MN的 CNT表中。
步骤 905 , sMAG-MN本地维护 MN的 CNT表的时间到期后 , sMAG-MN 发送 MN-CN映射关系同步消息给 MAPS-MN,消息中携带 MN-CN映射关系, 即新建的 CNT表项。若 MAPS-MN釆用如图 7所示的方法更新通信对端, 则 此消息中还需要携带 MAG-CN的地址或 CN的 CoA3。 MN-CN 映射关系同步消息的目的就是将 MN-CN 映射关系发送给 MAPS-MN。 消息的名称可以是其它名称, 只要该消息携带了上述信息即可。
步骤 906, MAPS-MN建立或维护 MN的 CNT。 MAPS还未建立 MN的 CNT则新建 CNT。 若 MAPS已经建立 MN的 CNT, 则将从 sMAG-MN获得 CNT表项加入 CNT。 若 MN-CN映射关系同步消息中还携带了 MAG-CN的 地址或 CN的 CoA3 ,则 MAPS-MN还需要在本地保存该信息,该信息可以保 存在 CNT内, 也可以单独保存。
步骤 907 , MAPS-MN发送 MN-CN映射关系同步完成消息给 sMAG-MN;
MN-CN映射关系同步完成消息的目的就是回应步骤 905的 MN-CN映射 关系同步消息, 消息的名称可以是其它名称, 只要该消息完成上述功能即可。
步骤 908, 当 sMAG-MN完成 MN-CN映射关系同步后, 删除本地保存 的已经更新到 MAPS-MN的 MN-CN映射关系 , 即 CNT。
本步骤可以在步骤 907后立即执行。
步骤 909, MN移动, 并更换 MAG。 MN通过附着过程接入到 PMIPv6 域内后, 向所属的 tMAG-MN发送路由请求( RS , Router Solicitation ) 消息。
当 sMAG-MN检测到 MN切换 /移动后 ,可选地, sMAG-MN向 MAPS-MN 发起去注册( DeRegister )流程。若 MAPS-MN返回代理绑定确认( PBA, Proxy Binding Ack )消息前收到了 sMAG-MN的 DeRegister消息 , 则 MAPS-MN仍 需要保留 HoAl/HNPl与 CoAl的映射关系, 或者 HoAl/HNPl与 sMAG-MN 地址的映射关系。
步骤 910, tMAG-MN向 MAPS-MN发送 PBU消息 ,代替 MN向 MAPS-MN 注册, 消息中携带 MN标识(MN ID ) 、 tMAG-MN为 MN新分配的代理广 播地址 CoA2和 MN的家乡网络前缀 HNP1。
步骤 911 , MAPS-MN接收 PBU消息, 更新 MN的绑定緩存列表 BCE , 并向 tMAG-MN返回 PBA消息。
步骤 912, tMAG-MN收到 PBA消息后, tMAG-MN向 MN返回路由通 告 ( RA, Router Advertisement ) 消息。
步骤 913 , tMAG-MN收到 PBA消息后, 建立 MN的 HNP-CoA的映射 关系, 即 HNPl-CoA2的映射关系。
步骤 914-916, 当 tMAG-MN收到第一个 MN与 CN (此处指 MN的新的 通信对端)之间的 IP数据报文后, 需要如步骤 904-908所述的, 在本地建立 MN-CN的映射关系, 并定期同步到 MAPS-MN。
步骤 917, tMAG-MN与 sMAG-MN之间建立转发隧道, 在建立过程中 将 HoA/HNP 与 MAG-CN 的地址映射或 HoA/HNP与 CoA的映射同步给 tMAG-MN„
在本步骤中, 上述地址映射关系表可以不同步到 tMAG-MN, 此时, 需 要由 tMAG-MN重新按照步骤 903 , 或步骤 904建立 HoA/HNP与 MAG-CN 的地址映射或 HoA/HNP与 CoA的映射和 MN-CN映射, 此时 tMAG-MN可 能会将 sMAG-MN已经同步的 MN-CN映射表重新同步给 MAPS-MN。
步骤 918, sMAG-MN将还未同步给 MAPS-MN的 MN-CN映射关系同步 到 MAPS-MN, 具体的同步步骤同步骤 904-908。 在该步骤中, sMAG-MN可 选的, 可以指示 MAPS-MN此次同步未为终端切换走后的最后一次同步, 该 指示可以通过在步骤 905的消息中增加指示来完成, 也可以通过使用新消息 名称来实现。 本步骤在 sMAG-MN检测到终端已经切换走后即可以执行, 或 者受到 sMAG-MN与 tMAG-MN之间的转发隧道建立的触发, 和步骤 917并 行执行。
步骤 919, 当 MAPS-MN执行完步骤 910和步骤 918后,触发 MAPS-MN 发起通信对端的更新。 具体的更新方式如图 7、 图 8所示。
步骤 920,当 MN所有的通信对端都完成更新后, MAPS-MN给 tMAG-MN 发送更新完成消息。
更新完成消息的目的就是通知 MAG 已经完成还通信对端的更新, 消息 的名称可以是其它名称, 只要该消息完成上述功能即可。
步骤 921 , 当 MAG-CN完成 MN的 HNPl/HoAl与 tMAG-MN地址的映 射或 HNPl/HoAl与 CoA2映射的更新后 , 即当 tMAG-MN与 MAG-CN之间 的隧道建立后 , tMAG-MN释放所述 tMAG-MN与 sMAG-MN之间的转发隧 道。 此后, MN与 CN之间的数据将通过 tMAG-MN与 MAG-CN进行转发。
实施例四
图 10是本发明移动性管理方法实施例四, 本实施例适用于 MAG定期更 新 MAPS本地存储的 MN-CN映射表。 如图 10所示, 具体包括以下步骤: 步骤 1001-1016, 同步骤 901-916。
步骤 1017, tMAG-MN与 sMAG-MN之间建立转发隧道, 在建立过程 中将 HoA/HNP与 MAG-CN的地址映射或 HoA/HNP与 CoA的映射同步给 tMAG-MN,将 sMAG-MN本地维护的 ,还未同步到 MAPS-MN的 MN-CN的 映射关系同步到 tMAG-MN。
在本步骤中, 上述地址映射关系表和 MN-CN 映射表可以不同步到 tMAG-MN, 此时, 需要由 tMAG-MN重新按照步骤 1003 , 或步骤 1004建立 上述地址映射关系表和 MN-CN映射表,此时 tMAG-MN可能会将 sMAG-MN 已经同步的 MN-CN映射表重新同步给 MAPS-MN。
步骤 1018, tMAG-MN将还未同步给 MAPS-MN的 MN-CN映射关系同 步到 MAPS-MN,具体的同步步骤同步骤 1004-1008。在该步骤中, tMAG-MN 可选的, 可以指示 MAPS-MN此次同步未为终端切换走后的最后一次同步, 该指示可以通过在步骤 1005的消息中增加指示来完成,也可以通过使用新消 息名称来实现。 本步骤在受到 sMAG-MN与 tMAG-MN之间的转发隧道建立 的触发, 和 1017并行执行。
步骤 1020、 1021 , 同步骤 920、 921。
此后, MN与 CN之间的数据将通过 tMAG-MN与 MAG-CN进行转发。
实施例五
图 11是本发明移动性管理方法实施例五。本实施例适用于 MAPS定期从
MAG获取 MN-CN映射表。 如图 11所示, 具体包括以下步骤:
步骤 1101-1104, 同步骤 901-904。 步骤 1105 , sMAG-MN本地维护 MN的 CNT表的时间到期后 , MAPS-MN 向 sMAG-MN发送 MN-CN映射关系获取消息。
MN-CN映射关系获取消息的目的就是通知 sMAG-MN需要获取 MN-CN 映射关系。 消息的名称可以是其它名称, 只要该消息执行了上述功能即可。
步骤 1106, sMAG-MN发送 MN-CN映射关系同步消息给 MAPS-MN, 消息中携带 MN-CN映射关系, 即新建的 CNT表项。 若 MAPS-MN釆用如图 7所示的方法更新通信对端, 则此消息中还需要携带 MAG-CN的地址或 CN 的 CoA3。
MN-CN 映射关系同步消息的目的就是将 MN-CN 映射关系发送给 MAPS-MN。 消息的名称可以是其它名称, 只要该消息携带了上述信息即可。
步骤 1107, 同步骤 906。
步骤 1108, 当 sMAG-MN完成 MN-CN映射关系同步后, 删除本地保存 的已经更新到 MAPS-MN的 MN-CN映射关系 , 即 CNT。
本步骤可以在步骤 1106后立即执行。
步骤 1109-1112, 同步骤 909-912。
步骤 1113 , 当 MAPS-MN 收到 tMAG-MN 的 PBU 消息后, 需要从 sMAG-MN获取还未同步到本地的 MN-CN的映射关系。 具体获取步骤同步 骤 1105-1108。
步骤 1114, MAPS-MN发起通信对端的更新。 具体的更新方式如图 7、 图 8所示。 本步骤在步骤 1113后的任意时刻都可以执行。
步骤 1115-1119, 同步骤 913-917。
步骤 1120-1121 , 同步骤 920-921。
实施例六
图 12是本发明移动性管理方法实施例六。 本实施例适用于 MAG实时更 新 MAPS本地存储的 MN-CN映射表。 如图 12所示, 具体包括以下步骤: 步骤 1201-1203 , 同步骤 901-903。 步骤 1204,本步骤与步骤 1203没有固定的先后顺序。 sMAG-MN收到第 一个 MN与 CN之间的 IP数据报文后,检查是否需要建立 MN与 CN的 CNT 表项 (即 MN-CN映射关系) 。 当 CN的 HoA3/HNP3与 CN的 CoA3或者 HoA3/HNP3与 MAG-CN的地址的映射关系是新建的或者还未建时, 需要新 建 CNT表项。 sMAG-MN建立如图 6b或图 6c所示的 CNT表项。
步骤 1205, sMAG-MN建立了 MN-CN映射关系后, 立即发送 MN-CN 映射关系同步消息给 MAPS-MN, 消息中携带 MN-CN映射关系, 即新建的 CNT表项。 若 MAPS-MN釆用如图 7所示的方法更新通信对端, 则此消息中 还需要携带 MAG-CN的地址或 CN的 CoA3。
步骤 1206-1208, 同步骤 906-908。
步骤 1209-1212, 同步骤 909-912。
步骤 1213 , MAPS-MN发起通信对端的更新。 具体的更新方式如图 7、 图 8所示。 本步骤在步骤 1210后的任意时刻都可以执行。
步骤 1214-1217, 当 tMAG-MN收到第一个 MN与 CN (此处指 MN的新 的通信对端)之间的 IP数据报文后, 需要如步骤 1204-1208所述的, 在本地 建立 MN-CN的映射关系, 并实时同步到 MAPS-MN。
步骤 1218, 同步骤 917。
步骤 1219-1220, 同步骤 920-921。
此后, MN与 CN之间的数据将通过 tMAG-MN与 MAG-CN进行转发。
实施例七
图 13是本发明移动性管理方法实施例七。本实施例适用釆用方式一实现 地址映射关系表更新时, 当 CN与 MN同时移动时地址映射关系表的更新。 如图 13所示, 具体包括以下步骤:
步骤 1301 , sMAG-MN在切换期间收到通信对端 CN的映射服务器发送 的 CoA更新请求。 消息中携带 CN的 HNP、 tMAG-CN地址或 tMAG-CN为 CN分配的新 CoA4 (即 HNP3与 tMAG-CN地址或 HNP3与 CoA4的映射)。 步骤 1302, sMAG-MN收到该消息后, 更新本地保存的 CN的地址映射 关系。
步骤 1303 , sMAG-MN向 MAPS-MN发送 CoA更新消息, 消息中携带 CN的 HNP、 tMAG-CN地址或 CN的 CoA4 (即 HNP3与 tMAG-CN地址或 HNP3与 CN的 CoA4的映射) 。 同时消息中需要携带切换指示, 用于指示 MAPS-MN该更新是由于 MN切换期间 CN同时切换引起的, 以便和正常的 更新区分。 可选的, 此处也可以釆用新消息来进行区分, 此时新消息中携带 的信息除了切换指示外, 其它与本步骤中的信息相同。
步骤 1304 , MAPS-MN收到该消息后, 更新本地保存的地址映射关系表。 步骤 1305, MAPS-MN根据步骤 1303的指示, 得知此次更新是由于 MN 切换期间 CN同时切换引起的,因此需要向 CN的 tMAG-CN重新更新 MN的 tMAG-MN地址或 CoA2。 若 MAPS-MN已经向 sMAG-CN ( CN的切换前的 MAG )发送过 CoA更新, 则此时需重新指示 tMAG-CN进行 CoA更新, MAPS-MN向 tMAG-CN发送 CoA更新消息, 消息中携带 MN的 HNP、 tMAG-MN地址或 CoA2 (即 HNPl与 tMAG-MN地址或 HNPl与 CoA2的映 射) 。
步骤 1306-1308, 同步骤 703-705。
步骤 1309, MAPS-MN向 sMAG-MN返回 CoA更新响应 , 同时可选的 , sMAG-MN向 MAPS-CN返回 CoA更新响应。本步骤在步骤 1304后即可执行。
本发明的上述实施例均以 PMIP流程为例描述了 tMAG-MN与 sMAG-MN 之间转发隧道的建立, 该实施例同样适用于 PMIP的快速切换( FPMIP, Fast Handovers for Proxy Mobile IPv6 ) 。 本发明实施例还提供一种移动性管理系统, 包括: 映射服务器、 源移动 接入网关, 分别如图 15, 14所示, 其中:
所述映射服务器包括切换更新单元 1501 , 设置为:
在所述映射服务器中接入的移动节点( MN )从所述源移动接入网关切换 到所述目标移动接入网关后, 向所述 MN的对端节点(CN )的移动接入网关 发送指向所述 MN的节点信息和指向所述目标移动接入网关的地址信息; 或者, 在所述映射服务器中接入的移动节点(MN )从源移动接入网关切 换到目标移动接入网关后, 向所述 CN的映射服务器发送指向所述 MN的节 点信息和指向所述目标移动接入网关的地址信息, 通过所述 CN的映射服务 器将所述指向所述 MN的节点信息和指向所述目标移动接入网关的地址信息 转发给所述 CN的移动接入网关。
其中, 所述源移动接入网关包括通信对端表创建单元 1401 和同步单元 1402, 所述映射服务器还包括通信对端表管理单元 1502, 其中:
所述通信对端表创建单元 1401设置为:收到所述 MN和 CN之间的第一 个数据报文后, 在本地新建的通信对端表或已有的通信对端表中增加如下表 项: 指向所述 MN的节点信息和指向所述 CN的节点信息的映射关系;
所述同步单元 1402设置为: 将所述通信对端表同步到所述映射服务器; 所述通信对端表管理单元 1502设置为:接收所述源移动接入网关同步过 来的通信对端表。
其中,所述同步单元 1402设置为通过如下方式将所述通信对端表同步到 所述映射服务器:
周期性主动将本地创建和维护的通信对端表同步给所述映射服务器; 或者, 接收到映射服务器周期性发送的请求后将本地创建和维护的通信 对端表同步给所述映射服务器;
或者, 每次新建通信对端表的表项时, 将新建的通信对端表表项同步给 所述映射服务器。
其中, 所述源移动接入网关还包括更新单元 1403 , 设置为通过如下方式 之一或其组合更新所述通信对端表:
在所述同步单元将本地的通信对端表同步给所述 MN的映射服务器后, 删除所述通信对端表;
所述源移动接入网关下附着的移动节点的对端节点离线或关机后, 将本 地通信对端表中该离线或关机的对端节点相应表项删除; 所述源移动接入网关下附着的移动节点离线或关机时, 删除所述通信对 端表中该离线或关机的移动节点相应表项。
其中,所述通信对端表管理单元 1502还设置为通过如下方式之一或其组 合更新所述通信对端表:
删除通信对端表中建立时间超过指定时间的表项, 所述指定时间大于移 动接入网关与所述映射服务器之间同步通信对端表的同步周期;
接收到对端节点离线或关机的消息后, 删除本地通信对端表中该对端节 点^]应表项;
接收到移动节点离线或关机的消息后, 删除本地通信对端表中该移动节 点相应表项。
其中, 所述源移动接入网关的同步单元 1402还设置为: 在所述映射服务 器向 CN的移动接入网关或所述 CN的映射服务器发送指向所述目标移动接 入网关的地址信息前, 主动或接收到所述 MN的映射服务器的请求后将本地 未同步给所述映射服务器的通信对端表发送给所述映射服务器; 或者, 主动 将本地未同步给所述映射服务器的通信对端表发送给所述目标移动接入网 关, 由所述目标移动接入网关将所述通信对端表发送给所述映射服务器。
其中, 所述源移动接入网关还包括映射关系表创建单元 1404, 设置为在 本地建立地址映射关系表, 緩存所述 MN的一个或多个对端节点的地址映射 关系, 所述地址映射关系表的每个表项代表一个对端节点的地址映射关系, 包括指向该对端节点的节点信息和指向该对端节点的移动接入网关的地址信 息。
其中, 所述源移动接入网关还包括映射关系表更新单元 1405, 设置为通 过如下方式之一或其组合更新所述地址映射关系表:
将地址映射关系表中建立时间超过预设时间的表项删除;
获知对端节点离线或关机时, 如果其上附着的所有移动节点的对端节点 的移动接入网关与所述离线或关机的对端节点的移动接入网关均不相同, 则 删除所述地址映射关系表中所述离线或关机的对端节点相关表项;
获知其上附着的移动节点离线或关机时, 如果其上附着的其它所有移动 节点的对端节点的移动接入网关均不同于所述离线或关机的移动节点的对端 节点的移动接入网关, 则删除所述地址映射关系中所述离线或关机的移动节 点的对端节点相关表项。
其中, 所述源移动接入网关还包括映射更新单元 1406, 设置为: 在所述 MN切换期间接收到所述 CN的映射服务器发送的更新所述 CN的地址映射关 系的消息时, 用所述消息中的 CN的地址映射关系更新本地保存的该 CN的 地址映射关系, 并发送更新所述 CN的地址映射关系的消息给所述映射服务 器, 携带所述 MN切换期间 CN同时切换的切换指示;
所述切换更新单元 1501还设置为接收到所述更新所述 CN的地址映射关 系的消息后, 更新所述 CN的地址映射关系, 并向所述 CN切换后的移动接 入网关发送指向所述目标移动接入网关的地址信息。
显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而可以将它们存储在存储装置中由计算装置来执行, 或者 将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软件 结合。
以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。
工业实用性 本发明实施例提供的切换管理方法, 实现当终端移动后, 使得 MN在改 变 MAG后, 保证 MN与 CN之间 IP报文的收发无传输路径上的浪费, 满足 MN的移动性需求。

Claims

权 利 要 求 书
1、 一种移动性管理方法, 其包括:
在移动节点( MN )从源移动接入网关切换到目标移动接入网关后, 所述 MN的映射服务器向所述 MN的对端节点(CN )的移动接入网关发送指向所 述 MN的节点信息和指向所述目标移动接入网关的地址信息;
或者,
在所述 MN从所述源移动接入网关切换到所述目标移动接入网关后, 所 述 MN的映射服务器向所述 CN的映射服务器发送指向所述 MN的节点信息 和指向所述目标移动接入网关的地址信息, 所述 CN的映射服务器将所述指 向所述 MN的节点信息和指向所述目标移动接入网关的地址信息转发给所述 CN的移动接入网关。
2、 如权利要求 1所述的方法, 其中,
指向所述 MN的节点信息包括: 所述 MN的标识信息、 家乡地址和家乡 网络前缀之一或其组合;
指向所述目标移动接入网关的地址信息包括如下之一或其组合: 所述目 标移动接入网关的地址, 所述目标移动接入网关为其上附着的节点分配的转 交地址(CoA ) 。
3、 如权利要求 1所述的方法, 所述方法还包括,
所述 MN当前的移动接入网关收到所述 MN和 CN之间的第一个数据报 文后, 在本地新建的通信对端表或已有的通信对端表中增加如下表项: 指向 所述 MN的节点信息和指向所述 CN的节点信息的映射关系;
以及, 将所述通信对端表同步到所述 MN的映射服务器;
所述 MN当前的移动接入网关为所述源移动接入网关或目标移动接入网 关。
4、 如权利要求 3所述的方法, 其中,
将所述通信对端表同步到所述 MN的映射服务器包括:
所述 MN当前的移动接入网关周期性主动将本地创建和维护的通信对端 表同步给所述映射服务器; 或者, 接收到映射服务器周期性发送的请求后将本地创建和维护的通信 对端表同步给所述映射服务器;
或者, 所述 MN当前的移动接入网关每次新建通信对端表的表项时, 将 新建的通信对端表表项同步给所述映射服务器。
5、 如权利要求 3所述的方法, 所述方法还包括, 所述 MN当前的移动接 入网关通过如下步骤之一或其组合更新所述通信对端表:
所述 MN当前的移动接入网关在将本地的通信对端表同步给所述 MN的 映射服务器后, 删除所述通信对端表;
所述 MN当前的移动接入网关下附着的移动节点的对端节点离线或关机 后, 所述 MN当前移动接入网关将本地通信对端表中该离线或关机的对端节 点相应表项删除;
所述 MN当前移动接入网关其下附着的移动节点离线或关机时, 删除所 述通信对端表中该离线或关机的移动节点相应表项。
6、 如权利要求 3所述的方法, 所述方法还包括: 所述映射服务器通过如 下步骤之一或其组合更新所述通信对端表:
所述映射服务器删除通信对端表中建立时间超过指定时间的表项, 所述 指定时间大于所述移动接入网关与所述映射服务器之间同步通信对端表的同 步周期;
所述映射服务器接收到对端节点离线或关机的消息后, 删除本地通信对 端表中该对端节点相应表项;
所述映射服务器接收到移动节点离线或关机的消息后, 删除本地通信对 端表中该移动节点相应表项。
7、 如权利要求 3所述的方法, 其中, 所述 MN的映射服务器向 CN的移 动接入网关或所述 CN的映射服务器发送指向所述目标移动接入网关的地址 信息前, 所述方法还包括:
所述源移动接入网关, 主动或接收到所述 MN的映射服务器的请求后, 将本地未同步给所述 MN的映射服务器的通信对端表发送给所述 MN的映射 服务器; 的通信对端表发送给所述目标移动接入网关, 由所述目标移动接入网关将所 述通信对端表发送给所述 MN的映射服务器。
8、 如权利要求 2所述的方法, 所述方法还包括: 所述 MN当前的移动接 入网关在本地建立地址映射关系表, 緩存所述 MN的一个或多个对端节点的 地址映射关系, 所述地址映射关系表的每个表项代表一个对端节点的地址映 射关系, 包括指向该对端节点的节点信息和指向该对端节点的移动接入网关 的地址信息;
所述 MN当前的移动接入网关为所述源移动接入网关或目标移动接入网 关。
9、 如权利要求 8所述的方法, 所述方法还包括: 所述 MN当前的移动接 入网关通过如下步骤之一或其组合更新所述地址映射关系表:
将地址映射关系表中建立时间超过预设时间的表项删除;
当所述 MN当前的移动接入网关获知对端节点离线或关机时, 如果其上 附着的所有移动节点的对端节点的移动接入网关与所述离线或关机的对端节 点的移动接入网关均不相同, 则删除所述地址映射关系表中所述离线或关机 的对端节点相关表项;
当所述 MN 当前的移动接入网关获知其上附着的移动节点离线或关机 时, 如果其上附着的其它所有移动节点的对端节点的移动接入网关均不同于 所述离线或关机的移动节点的对端节点的移动接入网关, 则删除所述地址映 射关系中所述离线或关机的移动节点的对端节点相关表项。
10、 如权利要求 8所述的方法, 所述方法还包括:
所述源移动接入网关在所述 MN切换期间接收到所述 CN的映射服务器 发送的更新所述 CN的地址映射关系的消息时, 用所述消息中的 CN的地址 映射关系更新本地保存的该 CN的地址映射关系, 并发送更新所述 CN的地 址映射关系的消息给所述 MN的映射服务器, 携带 MN切换期间 CN同时切 换的切换指示;
所述 MN的映射服务器接收到所述更新所述 CN的地址映射关系的消息 后, 更新所述 CN的地址映射关系, 并向所述 CN切换后的移动接入网关发 送指向所述目标移动接入网关的地址信息。
11、 一种映射服务器所述映射服务器包括切换更新单元, 其设置为: 在所述映射服务器中接入的移动节点( MN )从源移动接入网关切换到目 标移动接入网关后, 向所述 MN的对端节点(CN )的移动接入网关发送指向 所述 MN的节点信息和指向所述目标移动接入网关的地址信息;
或者, 在所述映射服务器中接入的移动节点(MN )从源移动接入网关切 换到目标移动接入网关后, 向所述 CN的映射服务器发送指向所述 MN的节 点信息和指向所述目标移动接入网关的地址信息, 通过所述 CN的映射服务 器将所述指向所述 MN的节点信息和指向所述目标移动接入网关的地址信息 转发给所述 CN的移动接入网关。
12、 如权利要求 11所述的映射服务器, 其中,
所述指向所述 MN的节点信息包括: 所述 MN的标识信息、 家乡地址和 家乡网络前缀之一或其组合;
所述指向所述目标移动接入网关的地址信息包括如下之一或其组合: 所 述目标移动接入网关的地址, 所述目标移动接入网关为其上附着的节点分配 的转交地址(CoA ) 。
13、 如权利要求 11所述的映射服务器, 其中,
所述通信对端表管理单元设置为: 接收所述源移动接入网关同步过来的 通信对端表, 所述通信对端表包括指向所述 MN的节点信息和指向所述 CN 的节点信息的映射关系。
14、 如权利要求 13所述的映射服务器, 其中, 所述通信对端表管理单元 还设置为通过如下方式之一或其组合更新所述通信对端表:
删除通信对端表中建立时间超过指定时间的表项, 所述指定时间大于移 动接入网关与所述映射服务器之间同步通信对端表的同步周期;
接收到对端节点离线或关机的消息后, 删除本地通信对端表中该对端节 点^]应表项;
接收到移动节点离线或关机的消息后, 删除本地通信对端表中该移动节 点^]应表项。
15、 如权利要求 13所述的映射服务器, 其中,
所述切换更新单元还设置为: 接收到所述源移动接入服务器发送的更新 所述 CN的地址映射关系的消息后, 更新所述 CN的地址映射关系, 并向所 述 CN切换后的移动接入网关发送指向所述目标移动接入网关的地址信息, 所述 CN的地址映射关系,包括指向该 CN的节点信息和指向该 CN的移动接 入网关的地址信息。
16、 一种接入网关, 当在映射服务器中接入的移动节点(MN )从源移动 接入网关切换到目标移动接入网关后, 所述接入网关作为所述源移动接入网 关时, 包括通信对端表创建单元和同步单元, 其中:
所述通信对端表创建单元设置为: 收到所述 MN和所述 MN的对端节点 ( CN )之间的第一个数据报文后, 在本地新建的通信对端表或已有的通信对 端表中增加如下表项: 指向所述 MN的节点信息和指向所述 CN的节点信息 的映射关系;
所述同步单元设置为: 将所述通信对端表同步到所述映射服务器。
17、 如权利要求 16所述的接入网关, 其中,
所述同步单元是设置为通过如下方式将所述通信对端表同步到所述映射 服务器:
周期性主动将本地创建和维护的通信对端表同步给所述映射服务器; 或者, 接收到映射服务器周期性发送的请求后将本地创建和维护的通信 对端表同步给所述映射服务器;
或者, 每次新建通信对端表的表项时, 将新建的通信对端表表项同步给 所述映射服务器。
18、 如权利要求 16所述的接入网关, 其还包括更新单元, 其设置为通过 如下方式之一或其组合更新所述通信对端表:
在所述同步单元将本地的通信对端表同步给所述 MN的映射服务器后, 删除所述通信对端表;
所述源移动接入网关下附着的移动节点的对端节点离线或关机后, 将本 地通信对端表中该离线或关机的对端节点相应表项删除;
所述源移动接入网关下附着的移动节点离线或关机时, 删除所述通信对 端表中该离线或关机的移动节点相应表项。
19、 如权利要求 16所述的接入网关, 其中,
所述同步单元还设置为: 在所述映射服务器向 CN的移动接入网关或所 述 CN的映射服务器发送指向所述目标移动接入网关的地址信息前, 主动或 接收到所述 MN的映射服务器的请求后, 将本地未同步给所述映射服务器的 通信对端表发送给所述映射服务器; 或者, 主动将本地未同步给所述映射服 务器的通信对端表发送给所述目标移动接入网关, 由所述目标移动接入网关 将所述通信对端表发送给所述映射服务器。
20、 如权利要求 16所述的接入网关, 其还包括映射关系表创建单元, 其 设置为: 在本地建立地址映射关系表, 緩存所述 MN的一个或多个 CN的地 址映射关系, 所述地址映射关系表的每个表项代表一个 CN的地址映射关系, 包括指向该 CN的节点信息和指向该 CN的移动接入网关的地址信息。
21、 如权利要求 20所述的接入网关, 其还包括映射关系表更新单元, 其 设置为通过如下方式之一或其组合更新所述地址映射关系表:
将地址映射关系表中建立时间超过预设时间的表项删除;
获知对端节点离线或关机时, 如果其上附着的所有移动节点的对端节点 的移动接入网关与所述离线或关机的对端节点的移动接入网关均不相同, 则 删除所述地址映射关系表中所述离线或关机的对端节点相关表项;
获知其上附着的移动节点离线或关机时, 如果其上附着的其它所有移动 节点的对端节点的移动接入网关均不同于所述离线或关机的移动节点的对端 节点的移动接入网关, 则删除所述地址映射关系中所述离线或关机的移动节 点的对端节点相关表项。
22、如权利要求 20所述的接入网关,其还包括映射更新单元,其设置为: 在所述 MN切换期间接收到所述 CN的映射服务器发送的更新所述 CN的地 址映射关系的消息时, 用所述消息中的 CN的地址映射关系更新本地保存的 该 CN的地址映射关系, 并发送更新所述 CN的地址映射关系的消息给所述 映射服务器, 携带所述 MN切换期间 CN同时切换的切换指示。
PCT/CN2012/076271 2011-09-06 2012-05-30 一种移动性管理方法和系统 WO2013034003A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2011102619277A CN102984687A (zh) 2011-09-06 2011-09-06 一种移动性管理方法和系统
CN201110261927.7 2011-09-06

Publications (1)

Publication Number Publication Date
WO2013034003A1 true WO2013034003A1 (zh) 2013-03-14

Family

ID=47831490

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/076271 WO2013034003A1 (zh) 2011-09-06 2012-05-30 一种移动性管理方法和系统

Country Status (2)

Country Link
CN (1) CN102984687A (zh)
WO (1) WO2013034003A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9295016B2 (en) 2013-06-12 2016-03-22 Microsoft Technology Licensing, Llc Cooperative phase tracking in distributed multiple-input multiple-output system

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015180024A1 (zh) * 2014-05-26 2015-12-03 华为技术有限公司 网络移动管理的处理方法和设备
CN108093084B (zh) * 2018-01-11 2020-09-08 中国科学院声学研究所 一种移动网络实体的动态位置信息局部更新和查询方法
CN109408416B (zh) * 2018-09-20 2021-01-26 新华三技术有限公司 一种地址映射表项页管理方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754168A (zh) * 2008-12-04 2010-06-23 中国移动通信集团公司 移动节点多接口间的切换方法、装置及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179457B (zh) * 2006-11-09 2010-10-27 华为技术有限公司 一种基于本地移动管理域中路由优化的切换方法
CN100521660C (zh) * 2007-09-13 2009-07-29 北京交通大学 一种一体化网络移动切换管理的实现方法
CN101123536B (zh) * 2007-09-19 2010-12-15 北京交通大学 实现一体化网络位置管理的方法
US8599843B2 (en) * 2009-03-02 2013-12-03 Futurewei Technologies, Inc. Apparatus and method for route optimization for proxy mobile internet protocol version six local routing

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754168A (zh) * 2008-12-04 2010-06-23 中国移动通信集团公司 移动节点多接口间的切换方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WU, QIN ET AL.: "Proxy MIP extension for local routing optimization", IETF.ORG, 26 October 2009 (2009-10-26), pages 7, Retrieved from the Internet <URL:http://tools.ietf.org/html/draft-wu-netext-local-ro-04> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9295016B2 (en) 2013-06-12 2016-03-22 Microsoft Technology Licensing, Llc Cooperative phase tracking in distributed multiple-input multiple-output system

Also Published As

Publication number Publication date
CN102984687A (zh) 2013-03-20

Similar Documents

Publication Publication Date Title
JP3573266B2 (ja) デスティネーションノードへパケットを配信する経路設定パスを確立する方法
JP3573265B2 (ja) パケットを無線デバイスに送信するステップ
JP3568852B2 (ja) 有線サブネットにアクセスする無線デバイス用にパケット経路設定アドレスを割り当てる方法及び装置
JP3501994B2 (ja) デスティネーションノードへパケットを分配するルーティングパスを確立する方法
EP1011241B1 (en) Wireless access to packet-based networks
US7606201B2 (en) Handover enabler
US20050088994A1 (en) Method and system for local mobility management
CN102196402A (zh) 无线通信系统中终端切换的方法及系统
JP2009529265A (ja) 動的ルータ広告を使用する高速ハンドオーバのための方法及びシステム
EP3043597B1 (en) Service processing methods and network controller
WO2008000133A1 (fr) Procédé, système et appareil de réalisation d&#39;un transfert rapide
JPWO2009057296A1 (ja) 移動端末及びネットワークノード並びにパケット転送管理ノード
WO2011085618A1 (zh) 一种终端切换的方法及相应的通信网络
JP5052675B2 (ja) モバイルノードのプロキシバインディングを制御する方法
WO2009149631A1 (zh) 状态切换信息处理方法、移动接入网关和移动终端
WO2013034003A1 (zh) 一种移动性管理方法和系统
WO2013004138A1 (zh) 基于lisp的移动性实现方法及隧道路由器
WO2013178013A1 (zh) 移动节点注册方法、互通方法、切换方法和网元
WO2013007131A1 (zh) 移动性管理的方法及移动接入网关
WO2013007133A1 (zh) 报文转发路径管理方法、系统及网元
WO2013007129A1 (zh) 报文转发处理方法、网元及系统
WO2003107600A1 (en) A method and system for local mobility management
WO2017152690A1 (zh) 一种代理移动IPv6中网络前缀主动重配置的方法
WO2013044688A1 (zh) 一种在pmip域间漫游时的节点通信方法及通信系统
KR20050079407A (ko) 무선 인터넷 시스템에서 통신 상태 정보를 이용한 소프트핸드오버 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12830616

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12830616

Country of ref document: EP

Kind code of ref document: A1