WO2017008288A1 - Ip地址管理方法、装置、ip地址锚点及移动节点 - Google Patents

Ip地址管理方法、装置、ip地址锚点及移动节点 Download PDF

Info

Publication number
WO2017008288A1
WO2017008288A1 PCT/CN2015/084149 CN2015084149W WO2017008288A1 WO 2017008288 A1 WO2017008288 A1 WO 2017008288A1 CN 2015084149 W CN2015084149 W CN 2015084149W WO 2017008288 A1 WO2017008288 A1 WO 2017008288A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
anchor
prefix
address prefix
assigned
Prior art date
Application number
PCT/CN2015/084149
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 华为技术有限公司
Priority to SG11201800098WA priority Critical patent/SG11201800098WA/en
Priority to JP2018501168A priority patent/JP6592584B2/ja
Priority to EP15898016.9A priority patent/EP3310099B1/en
Priority to CN201580079413.6A priority patent/CN107534919B/zh
Priority to PCT/CN2015/084149 priority patent/WO2017008288A1/zh
Publication of WO2017008288A1 publication Critical patent/WO2017008288A1/zh
Priority to ZA2018/00200A priority patent/ZA201800200B/en
Priority to US15/870,171 priority patent/US10728828B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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/08—Mobility data transfer
    • H04W8/087—Mobility data transfer for preserving data network PoA address despite hand-offs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/668—Internet protocol [IP] address subnets

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an IP address management method, apparatus, IP address anchor, and mobile node.
  • a mobile node (English: Mobile Node; MN for short) refers to a mobile terminal device such as a mobile phone, a tablet computer, or a portable computer. Due to the mobility of the MN, the MN will move between multiple Internet Protocol (English: Internet Protocol; IP) subnets. In order to ensure that the MN can still communicate with the communication peer node (English: Correspondent Node; CN) after the IP subnet moves, the mobility management solution emerges.
  • IP Internet Protocol
  • DMM Distributed Mobility Management
  • multiple IP subnets are included, and each IP subnet is deployed with an IP address anchor.
  • the existing IP address management method is as follows: When the MN moves from the first IP subnet to the second IP subnet, the IP address anchor in the second IP subnet assigns an IP address prefix to the MN. . The IP address anchor then provides the assigned IP address prefix and the valid IP address prefix that the MN is using to the MN to cause the MN to continue the existing network session or initiate a new network session using the IP address prefix described above.
  • the inventor has found that the prior art has at least the following problem: since the same IP address anchor can be assigned a different IP address prefix, the MN cannot accurately determine the change according to the received IP address prefix. Whether the accessed IP subnet has changed.
  • the embodiment of the present invention provides an IP address management method, apparatus, IP address anchor, and mobile node.
  • the technical solution is as follows:
  • an IP address management method includes:
  • IP address anchor detects that the mobile node MN accesses the IP subnet where the IP address anchor is located, Obtaining a valid IP address prefix that the MN is using;
  • the IP address anchor sends the handover indication information to the MN according to the valid IP address prefix, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the sending, by the IP address anchor, the handover indication information to the MN according to the valid IP address prefix including:
  • the IP address anchor allocates an IP address prefix to the MN, and the IP address assigned by the IP address anchor The prefix is distinguished from the IP address prefix assigned by the other IP address anchor in the valid IP address prefix;
  • IP address prefix is already assigned by the IP address anchor in the valid IP address prefix, the IP address anchor is to be assigned by the IP address anchor and the valid IP address prefix.
  • IP address prefix assigned by other IP address anchors is distinguished by the identifier;
  • the IP address anchor sends the handover indication information to the MN, where the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type
  • the identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the sending, by the IP address anchor, the handover indication information to the MN according to the valid IP address prefix including:
  • the IP address anchor sends the handover indication information to the MN according to the determination result, where the handover indication information includes a first indicator or a second indicator;
  • the first indicator is used to indicate that the IP subnet accessed by the MN has changed
  • the second indicator is used to indicate that the IP subnet accessed by the MN has not changed.
  • the IP address anchor determines, according to the valid IP address prefix, an IP sub-accessed by the MN Whether the web has changed, including:
  • the IP address anchor determines that the IP subnet accessed by the MN has changed
  • the IP address anchor determines whether the IP address prefix assigned by the IP address anchor corresponds to a predetermined identifier.
  • the predetermined identifier corresponds to an IP address prefix allocated by the MN to the MN before accessing the IP subnet where the IP address anchor is located;
  • the IP address anchor determines that the IP subnet accessed by the MN does not change
  • the IP address anchor determines that the IP subnet accessed by the MN has changed.
  • the method further includes:
  • the IP address anchor allocates an IP address prefix to the MN, and the IP address assigned by the IP address anchor The prefix is distinguished from the IP address prefix assigned by the other IP address anchor in the valid IP address prefix;
  • IP address prefix is already assigned by the IP address anchor in the valid IP address prefix, the IP address anchor is to be assigned by the IP address anchor and the valid IP address prefix.
  • IP address prefix assigned by other IP address anchors is distinguished by the identifier;
  • the IP address anchor sends a route advertisement message to the MN, where the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier.
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the IP address anchor will be by the IP address
  • the IP address prefix assigned by the anchor is distinguished from the IP address prefix assigned by the other IP address anchor in the valid IP address prefix, including:
  • the IP address anchor is a first type identifier corresponding to an IP address prefix assigned by the IP address anchor;
  • the IP address anchor is a second type corresponding to an IP address prefix assigned by another IP address anchor. Type identification.
  • the IP address anchor determines the valid IP Whether there is an IP address prefix assigned by the IP address anchor in the address prefix, including:
  • the IP address anchor determines whether the network identifier corresponding to the IP address anchor exists in the network identifier corresponding to each of the valid IP address prefixes, where the network identifier is an anchor identifier or a network number;
  • the IP address anchor determines that the IP address prefix allocated by the IP address anchor in the valid IP address prefix is already included;
  • the IP address anchor determines that there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix.
  • the IP address anchor obtains a valid IP address prefix that is used by the MN, including:
  • the IP address anchor sends an information acquisition request carrying the node identifier of the MN to the location manager LM, so that the LM searches for the MN from the pre-stored entry according to the node identifier of the MN.
  • a valid IP address prefix and a network identifier corresponding to each of the valid IP address prefixes wherein each entry includes a correspondence between a node identifier, a network identifier, an IP address prefix, and an expiration date of the IP address prefix, where the MN is
  • the IP address prefix allocated to the MN before the IP subnet to which the IP address anchor is located also has a predetermined identifier;
  • the IP address anchor receives the valid IP address prefix fed back by the LM and a network identifier corresponding to each of the valid IP address prefixes.
  • the method further includes:
  • the IP address anchor sends an information storage request to the LM, where the information storage request carries a node identifier of the MN, a network identifier corresponding to the IP address anchor point, and is allocated by the IP address anchor point.
  • An IP address prefix and an expiration date of an IP address prefix assigned by the IP address anchor such that the LM stores a target entry according to the information storage request, and correspondingly sets the predetermined identifier in the target entry, and
  • the predetermined identifier is removed from an entry in which an IP subnet allocated by the MN before accessing the IP subnet where the IP address anchor is located is allocated to the MN;
  • the target entry includes: a node identifier of the MN, a network identifier corresponding to the IP address anchor, an IP address prefix allocated by the IP address anchor, and an IP address assigned by the IP address anchor. The correspondence between the validity periods of the prefixes.
  • the method further includes:
  • the IP address anchor detects whether a target IP address prefix exists in the valid IP address prefix, where the target IP address prefix refers to an IP address prefix that is not used by the network session for a predetermined duration;
  • the IP address anchor sends an entry deletion indication that carries the node identifier of the MN and the target IP address prefix to the LM, so that The LM deletes an entry in which a correspondence between the node identifier of the MN and the target IP address prefix is recorded.
  • an IP address management method includes:
  • the mobile node MN After the mobile node MN accesses the IP subnet where the IP address anchor is located, the mobile node MN receives the handover indication information sent by the IP address anchor point;
  • the MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier.
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor;
  • Determining, by the MN, whether the accessed IP subnet has changed according to the handover indication information including:
  • IP address prefix allocated by the IP address anchor meets a predetermined condition; wherein the predetermined condition is: an IP address prefix allocated by the IP address anchor is received by the MN The IP address prefix assigned by the IP address anchor exists in the previous handover indication information received by the MN and is identified as being assigned by another IP address anchor;
  • the MN determines that the accessed IP subnet has changed
  • the MN determines that the accessed IP subnet has not changed.
  • the handover indication information includes a first indicator or a second indicator, where the first indicator is used to indicate the MN The accessed IP subnet has changed, and the second indicator is used to indicate that the IP subnet accessed by the MN has not changed;
  • Determining, by the MN, whether the accessed IP subnet has changed according to the handover indication information including:
  • the MN determines that the accessed IP subnet has changed
  • the MN determines that the accessed IP subnet has not changed.
  • the method further includes:
  • the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier, where the type identifier is used to distinguish the identifier by the IP address.
  • the IP address prefix assigned by the anchor is prefixed with the IP address assigned by other IP address anchors.
  • the type identifier includes a first type identifier and/or Or a second type of identification
  • the first type identifier is set corresponding to an IP address prefix assigned by the IP address anchor;
  • the second type identifier is set corresponding to an IP address prefix assigned by another IP address anchor.
  • the method further includes:
  • the MN distinguishes between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor according to the type identifier.
  • the method further includes:
  • the MN When the MN needs to initiate a new network session to the communication peer node CN, the MN selects to use the preferred IP address as the source IP address for the new network session;
  • the preferred IP address refers to an IP address prefix assigned according to the IP address anchor point.
  • the IP address generated by the host address of the MN.
  • the method further includes:
  • the MN selects the preferred IP address as the source IP address for the existing network session
  • the MN keeps the source IP address used by the existing network session unchanged.
  • the MN determines whether an existing network session with the CN can use the preferred IP address as the source IP address, include:
  • the MN acquires a transport layer protocol used by an application corresponding to the existing network session, and determines, according to the transport layer protocol, whether the existing network session can use the preferred IP address as a source IP address.
  • the method further includes:
  • the MN determines that the accessed IP subnet has changed, the MN queries to obtain an IP address of the communication peer node CN that is closest to the MN;
  • the MN establishes a network session with the nearest CN according to the IP address.
  • an IP address management apparatus which is applied to an IP address anchor, and the apparatus includes:
  • An address obtaining module configured to detect, when the mobile node MN accesses the IP address anchor point Obtain a valid IP address prefix that the MN is using when the IP subnet is used;
  • an information sending module configured to send, according to the valid IP address prefix, handover indication information to the MN, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the information sending module includes:
  • An address determining sub-module configured to determine whether an IP address prefix allocated by the IP address anchor is already in the valid IP address prefix
  • a prefix allocation submodule configured to allocate an IP address prefix to the MN when there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix;
  • a difference identifier submodule configured to distinguish, between the IP address prefix assigned by the IP address anchor and an IP address prefix allocated by another IP address anchor in the valid IP address prefix
  • a first sending submodule configured to send the handover indication information to the MN, where the handover indication information includes: an IP address prefix allocated by the IP address anchor, and an IP address prefix allocated by another IP address anchor And a type identifier for distinguishing between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the information sending module includes:
  • a change determining submodule configured to determine, according to the valid IP address prefix, whether an IP subnet accessed by the MN has changed
  • a second sending submodule configured to send the handover indication information to the MN according to the determination result, where the handover indication information includes a first indicator or a second indicator;
  • the first indicator is used to indicate that the IP subnet accessed by the MN has changed
  • the second indicator is used to indicate that the IP subnet accessed by the MN has not changed.
  • the change determining sub-module includes:
  • An address determining sub-module configured to determine whether an IP address prefix allocated by the IP address anchor is already in the valid IP address prefix
  • a first determining submodule configured to determine that an IP subnet accessed by the MN has changed when there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix
  • An identifier determining sub-module configured to determine, when the IP address prefix assigned by the IP address anchor is in the valid IP address prefix, whether the IP address prefix assigned by the IP address anchor corresponds to a predetermined identifier, where the predetermined identifier corresponds to an IP address prefix allocated by the MN to the MN before accessing the IP subnet where the IP address anchor is located;
  • a second determining sub-module configured to determine that the IP subnet accessed by the MN does not change when the IP address prefix assigned by the IP address anchor corresponds to the predetermined identifier
  • the first determining submodule is further configured to determine that the IP subnet accessed by the MN has changed when the IP address prefix assigned by the IP address anchor does not correspond to the predetermined identifier.
  • the device further includes:
  • a prefix allocation submodule configured to allocate an IP address prefix to the MN when there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix;
  • a difference identifier submodule configured to distinguish, between the IP address prefix assigned by the IP address anchor and an IP address prefix allocated by another IP address anchor in the valid IP address prefix
  • a message sending submodule configured to send a route advertisement message to the MN, where the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the difference identifier sub-module is specifically used to:
  • the second type identifier is set corresponding to the IP address prefix assigned by other IP address anchors.
  • the address determining sub-module includes:
  • a network identifier determining sub-module configured to determine, in the network identifier corresponding to each of the valid IP address prefixes, whether the network identifier corresponding to the IP address anchor point exists; wherein the network identifier is an anchor point identifier or a network number;
  • a first determining submodule configured to determine, when the network identifier corresponding to the IP address anchor exists, an IP address prefix already allocated by the IP address anchor in the valid IP address prefix;
  • a second determining submodule configured to determine, in the absence of the network identifier corresponding to the IP address anchor, that the IP address prefix is not allocated by the IP address anchor in the valid IP address prefix.
  • the address obtaining module includes:
  • an acquisition submodule configured to send, to the location manager LM, an information acquisition request that carries the node identifier of the MN; so that the LM searches for the MN according to the node identifier of the MN, and obtains the MN from the pre-stored entry.
  • a valid IP address prefix and a network identifier corresponding to each of the valid IP address prefixes wherein each entry includes a correspondence between a node identifier, a network identifier, an IP address prefix, and an expiration date of the IP address prefix, the MN
  • the IP address prefix assigned to the MN by the IP subnet accessed before accessing the IP subnet where the IP address anchor is located also corresponds to a predetermined identifier;
  • the address receiving submodule is configured to receive the valid IP address prefix of the LM feedback and a network identifier corresponding to each of the valid IP address prefixes.
  • the device further includes:
  • a requesting storage submodule configured to send an information storage request to the LM, where the information storage request carries a node identifier of the MN, a network identifier corresponding to the IP address anchor point, and is allocated by the IP address anchor point IP address prefix and an expiration date of the IP address prefix assigned by the IP address anchor; such that the LM stores the target entry according to the information storage request, and correspondingly sets the predetermined identifier in the target entry, and Removing the predetermined identifier from an entry in which an IP subnet that the MN accesses before accessing the IP subnet where the IP address anchor is located is assigned an IP address prefix assigned to the MN;
  • the target entry includes: a node identifier of the MN, a network identifier corresponding to the IP address anchor, an IP address prefix allocated by the IP address anchor, and an IP address assigned by the IP address anchor. The correspondence between the validity periods of the prefixes.
  • the device further includes:
  • An address detection submodule configured to detect whether a target IP address prefix exists in the valid IP address prefix, where the target IP address prefix refers to an IP address prefix that is not used by the network session for a predetermined duration;
  • a sending submodule configured to: when the target IP address prefix exists in the valid IP address prefix, send an entry deletion indication that carries the node identifier of the MN and the target IP address prefix to the LM, to Causing the LM to delete the node identifier of the MN and the target IP An entry for the correspondence between address prefixes.
  • a fourth aspect provides an IP address management apparatus, which is applied to a mobile node MN, where the apparatus includes:
  • the information receiving module is configured to receive the handover indication information sent by the IP address anchor point after accessing the IP subnet where the IP address anchor is located;
  • the change determining module is configured to determine, according to the handover indication information, whether the accessed IP subnet has changed.
  • the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier, where The type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor;
  • the change judging module includes:
  • condition determining sub-module configured to determine whether an IP address prefix allocated by the IP address anchor meets a predetermined condition; wherein the predetermined condition is that an IP address prefix assigned by the IP address anchor is in the MN The received previous handover indication information does not exist, or the IP address prefix allocated by the IP address anchor exists in the previous handover indication information received by the MN and is identified as being assigned by another IP address anchor;
  • a third determining submodule configured to determine that the accessed IP subnet has changed when an IP address prefix allocated by the IP address anchor satisfies the predetermined condition
  • a fourth determining submodule configured to determine that the accessed IP subnet has not changed when the IP address prefix allocated by the IP address anchor does not satisfy the predetermined condition.
  • the handover indication information includes a first indicator or a second indicator, where the first indicator is used to indicate the MN The accessed IP subnet has changed, and the second indicator is used to indicate that the IP subnet accessed by the MN has not changed;
  • the change judging module includes:
  • a fifth determining submodule configured to determine that the accessed IP subnet has changed when the first indicator is included in the handover indication information
  • the sixth determining submodule is configured to determine that the accessed IP subnet has not changed when the second indicator is included in the handover indication information.
  • the device further includes:
  • a message receiving submodule configured to receive a route advertisement message sent by the IP address anchor point
  • the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier, where the type identifier is used to distinguish the identifier by the IP address.
  • the IP address prefix assigned by the anchor is prefixed with the IP address assigned by other IP address anchors.
  • the type identifier includes a first type identifier and/or Or a second type of identification
  • the first type identifier is set corresponding to an IP address prefix assigned by the IP address anchor;
  • the second type identifier is set corresponding to an IP address prefix assigned by another IP address anchor.
  • the device further includes:
  • the address area numerator module is configured to distinguish an IP address prefix allocated by the IP address anchor from an IP address prefix assigned by another IP address anchor according to the type identifier.
  • the device further includes:
  • a first selection submodule configured to use a preferred IP address as the source IP address for the new network session when the MN needs to initiate a new network session to the communication peer node CN;
  • the preferred IP address refers to an IP address generated according to an IP address prefix allocated by the IP address anchor and a host address of the MN.
  • the device further includes:
  • a session judging sub-module configured to determine whether an existing IP session with the communication peer node CN can use the preferred IP address as the source IP address; wherein the preferred IP address is allocated according to the IP address anchor point An IP address prefix and an IP address generated by the host address of the MN;
  • a second selection submodule configured to use the preferred IP address as the source IP address for the existing network session when the existing network session can use the preferred IP address as the source IP address;
  • a third selection submodule configured to keep the source IP address used by the existing network session unchanged when the existing network session cannot use the preferred IP address as the source IP address.
  • the session determining sub-module is specifically configured to:
  • the device further includes:
  • An address querying module configured to: when the MN determines that the accessed IP subnet has changed, query an IP address of the communication peer node CN that is closest to the MN;
  • a session establishing module configured to establish a network session with the nearest CN according to the IP address.
  • an IP address anchor comprising: a processor, a memory, and a transceiver, wherein the memory is configured to store one or more instructions configured to be configured by Executing by the processor;
  • the processor is configured to acquire a valid IP address prefix that the MN is using when detecting that the mobile node MN accesses the IP subnet where the IP address anchor is located;
  • the processor is further configured to: according to the valid IP address prefix, control the transceiver to send handover indication information to the MN; to enable the MN to determine, according to the handover indication information, whether the accessed IP subnet is Has changed.
  • the processor is specifically configured to:
  • the MN is assigned an IP address prefix, and the IP address prefix assigned by the IP address anchor is associated with the valid IP address.
  • the IP address prefix assigned by another IP address anchor in the address prefix is distinguished by the identifier;
  • IP address prefix already has an IP address prefix assigned by the IP address anchor, then The IP address prefix assigned by the IP address anchor is distinguished from the IP address prefix assigned by another IP address anchor in the valid IP address prefix;
  • the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the processor is specifically configured to:
  • the transceiver is controlled to send the handover indication information to the MN, where the handover indication information includes a first indicator or a second indicator;
  • the first indicator is used to indicate that the IP subnet accessed by the MN has changed
  • the second indicator is used to indicate that the IP subnet accessed by the MN has not changed.
  • the processor is specifically configured to:
  • IP address prefix assigned by the IP address anchor is already in the valid IP address prefix, it is determined whether the IP address prefix allocated by the IP address anchor corresponds to a predetermined identifier, where the predetermined identifier corresponds to the The IP subnet that the MN accesses before accessing the IP subnet where the IP address anchor is located is an IP address prefix allocated by the MN;
  • IP address prefix assigned by the IP address anchor corresponds to the predetermined identifier, determining that the IP subnet accessed by the MN does not change;
  • IP address prefix assigned by the IP address anchor does not correspond to the predetermined identifier, it is determined that the IP subnet accessed by the MN has changed.
  • the processor is further configured to: if the valid IP address prefix is not in the IP address anchor Pointing the assigned IP address prefix, assigning an IP address prefix to the MN, and assigning an IP address prefix assigned by the IP address anchor to an IP address assigned by another IP address anchor in the valid IP address prefix. Address prefix difference identifier;
  • the processor is further configured to: if an IP address prefix allocated by the IP address anchor in the valid IP address prefix, the IP address prefix assigned by the IP address anchor and the valid IP address The IP address prefix assigned by another IP address anchor in the prefix is distinguished by the identifier;
  • the processor is further configured to control the transceiver to send a route advertisement message to the MN, where the route advertisement message includes: an IP address prefix allocated by the IP address anchor, and is allocated by another IP address anchor point.
  • the processor is specifically configured to:
  • the second type identifier is set corresponding to the IP address prefix assigned by other IP address anchors.
  • the processor is specifically configured to:
  • the network identifier Determining, in the network identifier corresponding to each of the valid IP address prefixes, whether the network identifier corresponding to the IP address anchor point exists; wherein the network identifier is an anchor point identifier or a network number;
  • IP address anchor If there is no network identifier corresponding to the IP address anchor, it is determined that there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix.
  • the processor is specifically used to:
  • an information acquisition request carrying a node identifier of the MN to the location manager LM, so that the LM searches for a source that is used by the MN from a pre-stored entry according to the node identifier of the MN.
  • a valid IP address prefix and a network identifier corresponding to each of the valid IP address prefixes wherein each entry includes a correspondence between a node identifier, a network identifier, an IP address prefix, and an expiration date of the IP address prefix, where the MN is connected
  • the IP address prefix assigned to the IP subnet before the IP subnet in which the IP address anchor is located also has a predetermined identifier;
  • the processor is further configured to control the transceiver to send an information storage request to the LM, where
  • the information storage request carries a node identifier of the MN, a network identifier corresponding to the IP address anchor, an IP address prefix allocated by the IP address anchor, and an IP address prefix allocated by the IP address anchor.
  • An expiration date such that the LM stores a target entry according to the information storage request, and correspondingly sets the predetermined identifier in the target entry, and the predetermined identifier is recorded from the MN in accessing the IP
  • the IP subnet accessed before the IP subnet where the address anchor is located is removed from the entry of the IP address prefix assigned by the MN;
  • the target entry includes: a node identifier of the MN, a network identifier corresponding to the IP address anchor, an IP address prefix allocated by the IP address anchor, and an IP address assigned by the IP address anchor. The correspondence between the validity periods of the prefixes.
  • the processor is further configured to detect whether a target IP address prefix exists in the valid IP address prefix,
  • the target IP address prefix refers to an IP address prefix that is not used by the network session for a predetermined duration;
  • the processor is further configured to: if the target IP address prefix exists in the valid IP address prefix, control the transceiver to send, to the LM, a node identifier carrying the MN and the target IP address prefix
  • the entry deletion indication causes the LM to delete an entry in which the correspondence between the node identifier of the MN and the target IP address prefix is recorded.
  • a mobile node MN comprising: a processor, a memory, and a transceiver, wherein the memory is configured to store one or more instructions, the instructions being configured to be by the processor carried out;
  • the processor is configured to, after accessing the IP subnet where the IP address anchor is located, control the transceiver to receive the handover indication information sent by the IP address anchor point;
  • the processor is further configured to determine, according to the handover indication information, whether the accessed IP subnet has changed.
  • the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier.
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor;
  • the processor is specifically configured to:
  • the predetermined condition is: the last handover indication information received by the IP address prefix by the IP address anchor at the MN
  • the IP address prefix assigned by the IP address anchor exists in the previous handover indication information received by the MN and is identified as being assigned by another IP address anchor;
  • IP address prefix allocated by the IP address anchor satisfies the predetermined condition, it is determined that the accessed IP subnet has changed;
  • IP address prefix assigned by the IP address anchor does not satisfy the predetermined condition, it is determined that the accessed IP subnet has not changed.
  • the handover indication information includes a first indicator or a second indicator, where the first indicator is used to indicate the MN The accessed IP subnet has changed, and the second indicator is used to indicate that the IP subnet accessed by the MN has not changed;
  • the processor is specifically configured to:
  • the second indicator is included in the handover indication information, it is determined that the accessed IP subnet has not changed.
  • the processor is further configured to control the transceiver to receive the route sent by the IP address anchor Announcement message
  • the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier, where the type identifier is used to distinguish the identifier by the IP address.
  • the IP address prefix assigned by the anchor is prefixed with the IP address assigned by other IP address anchors.
  • the type identifier includes a first type identifier and/or Or a second type of identification
  • the first type identifier is set corresponding to an IP address prefix assigned by the IP address anchor;
  • the second type identifier is set corresponding to an IP address prefix assigned by another IP address anchor.
  • the processor is further configured to A type identifier that distinguishes between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the processor is further configured to: when the MN needs to initiate a new network session to the communication peer node CN Selecting a preferred IP address as the source IP address for the new network session;
  • the preferred IP address refers to an IP address generated according to an IP address prefix allocated by the IP address anchor and a host address of the MN.
  • the processor is further configured to determine whether an existing network session with the communication peer node CN can Using the preferred IP address as the source IP address; wherein the preferred IP address refers to an IP address generated according to the IP address prefix assigned by the IP address anchor and the host address of the MN;
  • the processor is further configured to: if the existing network session can use the preferred IP address as the source IP address, select the preferred IP address as the source IP address for the existing network session;
  • the processor is further configured to keep the source IP address used by the existing network session unchanged if the existing network session cannot use the preferred IP address as the source IP address.
  • the processor is specifically configured to:
  • the processor is further configured to: when the MN determines that the accessed IP subnet has changed, query to obtain a communication pair that is closest to the MN. IP address of the end node CN;
  • the processor is further configured to establish a network session with the nearest CN according to the IP address.
  • the handover indication information is sent to the MN according to the valid IP address prefix that the MN is using, so that the MN determines the connection according to the handover indication information. Whether the incoming IP subnet has changed; solves the problem that the existing MN cannot judge whether the IP subnet to which it is connected has changed; so that the MN can accurately determine the IP subnet to which it is connected. Whether the technical effect of the change has occurred.
  • the IP address prefix assigned by the IP address anchor is distinguished from the IP address prefix assigned by the other IP address anchor by the type identifier, so that The MN can distinguish the two different types of IP address prefixes based on the type identifier. Further, the MN achieves the technical effect of reducing routing redundancy by selecting the preferred IP address as the source IP address for the new network session and the existing network session that can handle the change of the IP address.
  • FIG. 1 is a schematic diagram of an implementation environment according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of an IP address management method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of an IP address management method according to another embodiment of the present invention.
  • FIG. 4 is a flowchart of an IP address management method according to another embodiment of the present invention.
  • FIG. 5A is a flowchart of an IP address management method according to another embodiment of the present invention.
  • Figure 5B is a flow chart of step 502 involved in the embodiment of Figure 5A;
  • FIG. 6 is a block diagram of an IP address management apparatus according to an embodiment of the present invention.
  • FIG. 7 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • FIG. 8 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • FIG. 9 is a block diagram of an address determining sub-module according to an embodiment of the present invention.
  • FIG. 10 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • FIG. 11 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • FIG. 12 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • FIG. 13 is a block diagram of another IP address management apparatus according to the embodiment shown in Figures 11 and 12;
  • FIG. 14 is a block diagram of an IP address management system according to an embodiment of the present invention.
  • IP address anchor 15 is a structural block diagram of an IP address anchor provided by an embodiment of the present invention.
  • FIG. 16 is a structural block diagram of an MN according to an embodiment of the present invention.
  • FIG. 1 shows a schematic diagram of an implementation environment involved in an embodiment of the present invention.
  • the implementation environment includes multiple IP subnets.
  • IP subnet 1 and IP subnet 2 are taken as an example.
  • IP address anchors 120 and CN140 are deployed in each IP subnet.
  • the implementation environment also includes an MN 160 that is moveable among the plurality of IP subnets described above. among them:
  • the MN 160 may be a mobile terminal device such as a mobile phone, a tablet computer, or a portable computer.
  • the IP address anchor 120 is used to provide mobility support for the MN 160.
  • the IP address anchor 120 may be a gateway device, such as a public data network (Public Data Network; PND) gateway PGW.
  • PND Public Data Network
  • the CN 160 may be a server for providing network services to the MN 160.
  • the network service may be a download service, a video service, a network telephone service, or the like.
  • the service functions and service resources of the CN140 in different IP subnets may be the same or different.
  • FIG. 2 shows a flowchart of an IP address management method provided by an embodiment of the present invention. This embodiment is described by using the IP address management method in the IP address anchor 120 in the implementation environment shown in FIG.
  • the IP address management method may include the following steps:
  • Step 202 The IP address anchor acquires a valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address anchor is located.
  • Step 204 The IP address anchor sends the handover indication information to the MN according to the valid IP address prefix, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the IP address management method provided by this embodiment is based on the IP address anchor, when detecting the MN accessing the IP subnet where the IP address anchor is located, according to the valid IP address that the MN is using.
  • the SN sends the handover indication information to the MN; the MN can not determine whether the IP subnet to which the access has been changed has been solved in the prior art; and the MN can accurately determine whether the IP subnet to which it is connected has been The technical effect of the change.
  • FIG. 3 is a flowchart of an IP address management method according to another embodiment of the present invention. This embodiment is described by using the IP address management method in the MN 160 in the implementation environment shown in FIG.
  • the IP address management method may include the following steps:
  • Step 302 After accessing the IP subnet where the IP address anchor is located, the MN receives the handover indication information sent by the IP address anchor point.
  • Step 304 The MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the IP address management method receives the handover indication information sent by the IP address anchor through the MN, and determines whether the accessed IP subnet has changed according to the handover indication information;
  • the MN with technology can not judge whether the IP subnet to which it is connected has changed; the technical effect that enables the MN to accurately determine whether the IP subnet to which it is connected has changed.
  • FIG. 4 is a flowchart of an IP address management method according to another embodiment of the present invention. This embodiment is exemplified by applying the IP address management method to the implementation environment shown in FIG. 1.
  • the IP address management method may include the following steps:
  • Step 401 The IP address anchor acquires a valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address anchor is located.
  • the validity period of the IP address prefix is set accordingly.
  • the IP address prefix that is within the validity period and has not been released is the valid IP address prefix.
  • Step 402 The IP address anchor determines whether there is an IP address prefix assigned by the IP address anchor in the valid IP address prefix.
  • step 403 If not, the following step 403 is performed, and after step 403, step 404 is performed; if so, step 404 is directly executed.
  • the IP subnet currently accessed by the MN is IP subnet 2, and the IP address anchor in IP subnet 2 is recorded as anchor#2.
  • the MN may be moved from other IP subnets to IP subnet 2. Therefore, there may be an IP address prefix assigned by the other IP address anchors to the MN in the above valid IP address prefix.
  • the MN moves from IP subnet 1 to IP subnet 2, and the IP address anchor in IP subnet 1 is recorded as Anchor#1, when the anchor#2 detects that the MN accesses the IP subnet 2, the obtained valid IP address prefix of the MN may include the IP address prefix assigned by the anchor#1 for the MN, which is denoted as prefix#1. .
  • the valid IP address prefix used by the MN acquired by the anchor#2 may include the IP address prefix assigned by the anchor#2 for the MN, which is denoted as prefix#2.
  • prefix#2 the IP address prefix assigned by the anchor#2 for the MN.
  • the anchor #2 detects that the MN is accessing the IP subnet 2, and the acquired MN is using.
  • the prefix #1 and prefix#2 can be included in the valid IP address prefix.
  • the IP address anchor allocates an IP address prefix to the MN.
  • anchor#2 assigns an IP address prefix to the MN, which is denoted as prefix#2.
  • anchor #2 performs the following step 404.
  • the anchor #2 when there is already an IP address prefix assigned by the anchor #2 in the valid IP address prefix that the MN is using, the anchor #2 does not need to allocate an IP address prefix to the MN, and directly performs the following step 404.
  • Step 404 the IP address anchor distinguishes the IP address prefix assigned by the IP address anchor from the IP address prefix assigned by the other IP address anchor in the valid IP address prefix.
  • the IP address anchor is set to the first type identifier corresponding to the IP address prefix assigned by the IP address anchor; and/or, the IP address anchor is the IP address prefix corresponding to the other IP address anchor. Two types of identification.
  • the first type identifier is H-prefix
  • the second type identifier is F-prefix
  • the IP address anchor sets the first type identifier H-prefix corresponding to prefix #2.
  • the IP address anchor is set to the prefix type 1 corresponding to the second type identifier F-prefix.
  • the IP address anchor sets the first type identifier H-prefix corresponding to prefix #2, and sets the second type identifier F-prefix for prefix #1.
  • Step 405 The IP address anchor sends the handover indication information to the MN, where the handover indication information includes: The IP address prefix assigned by the IP address anchor, the IP address prefix assigned by other IP address anchors, and the type identifier.
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor. That is, the first type identifier and/or the second type identifier introduced in the above step 404.
  • the handover indication information is sent to the MN in the form of a route advertisement (RA: Router) message.
  • RA Router
  • the MN receives the handover indication information sent by the IP address anchor.
  • Step 406 The MN determines whether the IP address prefix allocated by the IP address anchor meets a predetermined condition.
  • step 407 is performed; if not, the following step 408 is performed.
  • the predetermined condition is that the IP address prefix assigned by the IP address anchor does not exist in the previous handover indication information received by the MN, or the IP address prefix assigned by the IP address anchor is received in the previous MN.
  • the handover indication information exists and is identified as being assigned by other IP address anchors.
  • the MN After receiving the handover indication information sent by the IP address anchor in the currently accessed IP subnet, the MN can distinguish the IP address prefix assigned by the IP address anchor and the assignment by other IP address anchors according to the type identifier. IP address prefix.
  • the MN determines that the corresponding prefix#2 is the anchor#2 allocation according to the first type identifier H-prefix. IP address prefix.
  • the MN performs the following Step 407.
  • the MN performs the following step 408.
  • step 407 the MN determines that the accessed IP subnet has changed.
  • step 408 the MN determines that the accessed IP subnet has not changed.
  • the IP address management method sends an IP address to the MN according to the valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address is anchored by the IP address anchor. And switching the indication information, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed; and solves the problem that the MN that exists in the prior art cannot determine whether the IP subnet accessed by the MN has changed. So that the MN can accurately determine the IP subnet it is connected to. Whether the technical effect of the change has occurred.
  • the IP address management method provided in this embodiment distinguishes the IP address prefix assigned by the IP address anchor from the IP address prefix assigned by other IP address anchors by using the type identifier;
  • the change of the IP address prefix included in the handover indication information and the change of the corresponding type identifier can accurately determine whether the IP subnet to which the access has been changed has changed; on the other hand, the MN can easily distinguish according to the type identifier.
  • Two different types of IP address prefixes are used, so that different types of IP address prefixes can be utilized more reasonably during network sessions, thereby reducing routing redundancy.
  • FIG. 5A is a flowchart of an IP address management method according to another embodiment of the present invention. This embodiment is exemplified by applying the IP address management method to the implementation environment shown in FIG. 1.
  • the IP address management method may include the following steps:
  • Step 501 The IP address anchor acquires a valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address anchor is located.
  • Step 502 The IP address anchor determines, according to the valid IP address prefix, whether the IP subnet accessed by the MN has changed.
  • this step may include the following sub-steps:
  • the IP address anchor determines whether there is an IP address prefix assigned by the IP address anchor in the valid IP address prefix.
  • step 502d is performed; if so, the following step 502b is performed.
  • IP subnet currently accessed by the MN is IP subnet 2
  • IP address anchor in IP subnet 2 is recorded as anchor#2.
  • the valid IP address prefix that the MN acquired by anchor#2 is using includes prefix#1, prefix#2, and prefix#3.
  • Anchor #2 determines whether there is an IP address prefix assigned by anchor#2 among the above three IP address prefixes.
  • the anchor #2 finds that the three IP address prefixes are not the IP address prefix assigned by the anchor#2 to the MN, and then the anchor #2 performs the following step 502d to determine that the IP subnet accessed by the MN has changed.
  • anchor#2 finds that prefix#1 is an IP address prefix assigned by anchor#2 to the MN, and anchor#2 performs the following step 502b.
  • Step 502b The IP address anchor determines whether the IP address prefix assigned by the IP address anchor corresponds to a predetermined identifier.
  • step 502c is performed; if not, the following step 502d is performed.
  • the predetermined identifier corresponds to an IP address prefix allocated by the MN to the MN before accessing the IP subnet where the IP address anchor is located.
  • the predetermined identification can be recorded as a current anchor.
  • anchor#2 When anchor#2 finds that prefix #1 is an IP address prefix assigned by anchor#2 to the MN, anchor#2 further determines whether prefix#1 corresponds to a predetermined identifier current anchor. When the prefix #1 corresponds to the predetermined identifier current anchor, it indicates that the IP subnet accessed by the MN has not changed; otherwise, when the prefix#1 does not correspond to the predetermined identifier current anchor, such as prefix#2 or prefix#3, there is a reservation. When the current anchor is identified, the IP subnet accessed by the MN has changed.
  • step 502c the IP address anchor determines that the IP subnet accessed by the MN has not changed.
  • step 502d the IP address anchor determines that the IP subnet accessed by the MN has changed.
  • Step 503 The IP address anchor sends the handover indication information to the MN according to the determination result, where the handover indication information includes the first indicator or the second indicator.
  • the first indicator is used to indicate that the IP subnet accessed by the MN has changed
  • the second indicator is used to indicate that the IP subnet accessed by the MN has not changed.
  • the MN receives the handover indication information sent by the IP address anchor.
  • Step 504 The MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the MN determines that the accessed IP subnet has changed.
  • the MN determines that the accessed IP subnet has not changed.
  • the method further includes the following steps:
  • IP address anchor assigns an IP address prefix to the MN, and the IP address prefix and the valid IP address prefix assigned by the IP address anchor are assigned.
  • IP address prefix assigned by other IP address anchors is distinguished.
  • IP address anchor will be assigned by the IP address anchor and the IP address prefix by the other IP address in the valid IP address prefix.
  • the assigned IP address prefix distinguishes the identifier.
  • the IP address anchor sends a route advertisement message to the MN, where the route advertisement message includes: an IP address prefix assigned by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier.
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the MN receives a route advertisement message sent by the IP address anchor.
  • the MN distinguishes between the IP address prefix assigned by the IP address anchor and the IP address prefix assigned by other IP address anchors according to the type identifier.
  • the IP address anchor informs the MN of the currently available IP address prefix by using the route advertisement message, and uses the type identifier to distinguish the IP address prefix assigned by itself from the IP address prefix assigned by other IP address anchors, so that the MN according to the type
  • the identifier can easily distinguish two different types of IP address prefixes, so that different types of IP address prefixes can be utilized more reasonably in the subsequent network session, thereby reducing routing redundancy.
  • the handover indication information may be carried in the route advertisement message and sent to the MN.
  • the IP address management method sends an IP address to the MN according to the valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address is anchored by the IP address anchor. And switching the indication information, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed; and solves the problem that the MN that exists in the prior art cannot determine whether the IP subnet accessed by the MN has changed.
  • a technical effect is achieved that enables the MN to accurately determine whether the IP subnet to which it is connected has changed.
  • the IP address management method provided in this embodiment determines whether the IP subnet accessed by the MN has changed by using the IP address anchor point, and directly informs the MN of the determination result, thereby reducing the processing overhead of the MN side.
  • the step 402 in the embodiment shown in FIG. 4 and the step 502a in the embodiment shown in FIG. 5A that is, the IP address anchor determine whether the valid IP address prefix has been anchored by the IP address.
  • the steps of assigning an IP address prefix may include the following sub-steps:
  • the IP address anchor determines whether the network identifier corresponding to the IP address anchor exists in the network identifier corresponding to each valid IP address prefix.
  • the IP address anchor determines that the IP address prefix already assigned by the IP address anchor in the valid IP address prefix.
  • the IP address anchor determines that there is no IP address prefix assigned by the IP address anchor in the valid IP address prefix.
  • the network identifier is an anchor identifier or a network number.
  • Different IP address anchors correspond to different network identifiers. Taking the network identifier as the anchor identifier as an example, different IP address anchors can be distinguished by different anchor identifiers such as anchor#1, anchor#2, anchor#3.
  • the IP address anchor When obtaining the valid IP address prefix used by the MN, the IP address anchor obtains the network identifier corresponding to each valid IP address prefix, and determines whether the valid IP address prefix has an IP address prefix assigned by itself.
  • the valid IP address prefix used by the MN obtained by anchor#2 includes prefix#1, prefix#2, and prefix#3, and the network identifiers corresponding to the three IP address prefixes are anchor#1, anchor#2, and anchor, respectively. #3. Then, anchor#2 can determine that the three IP address prefixes have an IP address prefix assigned by itself, namely prefix#2.
  • a separate entity may be deployed in the implementation environment shown in FIG. 1 as a location manager (English: Location Manager; LM for short).
  • the LM can cover multiple IP subnets, that is, the relationship between the LM and the IP address anchor can be one-to-many.
  • the LM is used to record a list of valid IP address prefixes assigned by each IP address anchor to the MN. For example, multiple entries may be stored in the LM, and each entry includes a correspondence between a node identifier, a network identifier, an IP address prefix, and an expiration date of the IP address prefix.
  • the IP address anchor can query the LM for the valid IP address prefix that the MN is using.
  • the step of obtaining an effective IP address prefix that the MN is using by the IP address anchor may include the following sub-steps:
  • the IP address anchor sends an information acquisition request carrying the node identifier of the MN to the LM, so that the LM searches for the valid IP address prefix used by the MN and each valid IP address from the pre-stored entry according to the node identifier of the MN.
  • the network identifier corresponding to the prefix is the network identifier corresponding to the prefix.
  • the IP address anchor receives the valid IP address prefix of the LM feedback and the network identifier corresponding to each valid IP address prefix.
  • LM stores multiple entries as shown in Table-1 below:
  • anchor#2 When anchor #2 detects that MN#1 accesses IP subnet 2, anchor#2 sends an information acquisition request carrying MN#1 to LM. Accordingly, the LM searches for a entry containing the node identifier MN#1 from the pre-stored entries, such as entries 1 and 2 in Table-1 above, and the LM sends the above entries 1 and 2 to anchor#2. Accordingly, anchor#2 can obtain the valid IP address prefixes that MN#1 is using from the received entries, namely prefix#1 and prefix#3.
  • the anchor #2 can distinguish the IP address prefix assigned by itself from MN#1 and the IP address prefix assigned by other IP address anchors to MN#1 according to the network identifier corresponding to each valid IP address prefix. Both prefix #1 and prefix #3 described above are not IP address prefixes assigned by anchor#2 to MN#1.
  • the LM stored entry further includes a predetermined identifier current anchor.
  • the anchor #2 After receiving the above items 1 and 2 sent by the LM, the anchor #2 detects that the prefix #1 assigned by the anchor#1 corresponds to the predetermined identifier current anchor, indicating that the MN#1 is the IP subnet 1 to which the anchor#1 is located. Moving to the IP subnet 2 where anchor#2 is located, the IP subnet accessed by MN#1 has changed.
  • the IP address anchor After the IP address anchor assigns an IP address prefix to the MN, it sends an information storage request to the LM.
  • the information storage request carries the node identifier of the MN, the network identifier corresponding to the IP address anchor, the IP address prefix assigned by the IP address anchor, and the validity period of the IP address prefix assigned by the IP address anchor. So that the LM stores the target entry according to the information storage request, and correspondingly sets a predetermined identifier in the target entry, and sets the predetermined identifier from the IP subnet to which the MN is located before the IP subnet where the access IP address anchor is located.
  • the entry for the IP address prefix assigned to the MN is removed.
  • the target entry includes: a node identifier of the MN, a network identifier corresponding to the IP address anchor, an IP address prefix assigned by the IP address anchor, and a validity period between the IP address prefix assigned by the IP address anchor. relationship.
  • anchor#2 After anchor#2 receives the above items 1 and 2 sent by the LM, it detects that MN#1 is found. If the valid IP address prefix being used does not have an IP address prefix assigned by itself, then anchor#2 assigns an IP address prefix to MN#1, which is denoted as prefix#2. Also, anchor#2 sets the validity period corresponding to prefix#2, and is recorded as time#5. After that, the anchor #2 sends an information storage request to the LM, where the information storage request carries the node identifier MN#1, the network identifier anchor#2, the IP address prefix prefix#2, and the validity period time#5. Correspondingly, the LM updates the pre-stored entry after receiving the information storage request sent by anchor#2.
  • the updated entries can be as shown in Table-2 below:
  • Anchor #2 stores the entry 1 in Table-2, and correspondingly sets the predetermined identifier current anchor in the entry, and the predetermined identifier current anchor from the entry 2 in Table-2 (ie, entry 1 in Table-1) Remove.
  • the IP address anchor detects whether there is a target IP address prefix in the valid IP address prefix, and the target IP address prefix refers to an IP address prefix that is not used by the network session for a predetermined duration. If the target IP address prefix exists in the valid IP address prefix, the IP address anchor sends an entry deletion indication carrying the MN node identifier and the target IP address prefix to the LM, so that the LM deletes the MN node identifier and the target IP address. An entry for the correspondence between the prefixes.
  • anchor#2 when anchor#2 detects that prefix#3 is not used by the network session for more than the predetermined duration, it indicates that MN#1 no longer needs to use the prefix#3, and anchor#2 sends the MN#1 and prefix to the LM. #3's entry deletion indication.
  • the LM after receiving the above-mentioned entry deletion instruction sent by anchor#2, the LM deletes entry 3 in Table-2 above.
  • the embodiment of the present invention can ensure the accuracy and real-time performance of the entries stored in the LM on the one hand, and save the storage resources of the LM on the other hand.
  • a mobility management (English: Mobility Management; MM) entity is deployed in the subnet.
  • the MM entity is responsible for performing signaling interactions between the IP address anchor and the LM related to mobility management.
  • the MM entity can be deployed as a separate entity, or the MM entity can be integrated with the IP address anchor.
  • the process by which the IP address anchor queries the LM for the valid IP address prefix that the MN is using is as follows:
  • the IP address anchor sends an information acquisition request carrying the node identifier of the MN to the MM entity;
  • the MM entity forwards the information acquisition request to the LM.
  • the LM searches for the valid IP address prefix used by the MN and the network identifier corresponding to each valid IP address prefix from the pre-stored entry according to the node identifier of the MN;
  • the LM sends the valid IP address prefix and the network identifier corresponding to each valid IP address prefix to the MM entity;
  • the MM entity forwards the valid IP address prefix and the network identifier corresponding to each valid IP address prefix to the IP address anchor.
  • the following describes and describes the selection of different types of IP address prefixes when the MN performs a network session.
  • the IP address prefix assigned by the IP address anchor and the other IP address are identified by the type identifier.
  • the MN can distinguish the two different types of IP address prefixes based on the type identifier. The following describes and describes the selection of different types of IP address prefixes in the case of new network sessions and existing network sessions.
  • the MN When the MN needs to initiate a new network session to the CN, the MN chooses to use the preferred IP address as the source IP address for the new network session.
  • the preferred IP address refers to an IP address generated according to an IP address prefix assigned by an IP address anchor in the currently accessed IP subnet and a host address of the MN.
  • the MN moves from the IP subnet 1 to the IP subnet 2, and the RA message sent by the anchor #2 in the IP subnet 2 to the MN includes: prefix #1 and prefix #2.
  • the prefix #1 is correspondingly provided with a second type identifier F-prefix
  • the prefix #2 is correspondingly provided with a first type identifier H-prefix.
  • the IP address generated by the MN according to prefix #1 and its own host address is IP address#1
  • the IP address generated according to prefix#2 and its own host address is IP address#2.
  • the MN chooses to use the IP address #2 as the source IP address to communicate with the CN for the new network session, thereby achieving the purpose of reducing routing redundancy.
  • the MN determines whether the existing network session with the CN can use the preferred IP address as the source IP address.
  • the preferred IP address refers to an IP address generated according to an IP address prefix assigned by an IP address anchor in the currently accessed IP subnet and a host address of the MN. If the existing network session can use the preferred IP address as the source IP address, the MN selects the preferred IP address as the source IP address for the existing network session; otherwise, if the existing network session cannot use the preferred IP address as the source IP address, Then the MN keeps the source IP address used by the existing network session unchanged.
  • the existing network session uses IP address#1 as the source IP address. Communicate with the CN.
  • the MN determines whether the existing network session itself can handle the change of the IP address, that is, whether the existing network session can communicate with the CN using the IP address #2 as the source IP address. If yes, the MN chooses to use the IP address #2 as the source IP address to communicate with the CN for the existing network session, thereby achieving the purpose of reducing routing redundancy.
  • the MN keeps the source IP address IP address#1 used by the existing network session unchanged, and uses the tunnel between the anchor#2 and the anchor#1 (English: tunnel) for the existing network session.
  • the service flow provides continuity support to ensure that the existing network session is not affected.
  • the MN determines whether the existing network session with the CN can use the preferred IP address as the source IP address, which can be implemented in various ways.
  • the MN obtains configuration information of an application corresponding to the existing network session, and determines, according to the configuration information, whether the existing network session can use the preferred IP address as the source IP address. For example, when an application developer develops an application, it is explicitly set by setting the socket option.
  • the MN obtains a transport layer protocol used by an application corresponding to the existing network session, and determines, according to the transport layer protocol, whether the existing network session can use the preferred IP address as the source IP address. For another example, since MPTCP (English: Multipath TCP) itself is capable of handling changes in the IP address, if the transport layer protocol used by the existing network session is MPTCP, then the existing network session is made to use the preferred IP address as the source. IP address.
  • MPTCP English: Multipath TCP
  • the MN keeps the source IP address used by the existing network session unchanged.
  • the IP address prefix assigned by the IP address anchor is distinguished from the IP address prefix assigned by the other IP address anchor by the type identifier. So that the MN can distinguish the two different types of IP address prefixes based on the type identifier.
  • the MN achieves the technical effect of reducing routing redundancy by selecting the preferred IP address as the source IP address for the new network session and the existing network session that can handle the change of the IP address.
  • the MN may query the IP address of the CN that is closest to the MN, and establish a network session with the nearest CN according to the IP address, thereby further Reduce the purpose of routing redundancy.
  • FIG. 6 shows a block diagram of an IP address management apparatus according to an embodiment of the present invention.
  • the IP address management device can be applied to an IP address anchor.
  • the IP address management apparatus may include an address obtaining module 610 and an information sending module 620.
  • the address obtaining module 610 is configured to obtain a valid IP address prefix that the MN is using when detecting that the mobile node MN accesses the IP subnet where the IP address anchor is located.
  • the information sending module 620 is configured to send, according to the valid IP address prefix, handover indication information to the MN, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the IP address management apparatus sends an IP address to the MN according to the valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address is anchored by the IP address anchor.
  • Switching indication information solving the problem that the existing MN cannot judge whether the IP subnet to which it is connected has changed; and the technology that enables the MN to accurately determine whether the IP subnet to which it is connected has changed. effect.
  • FIG. 7 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • the IP address management device can be applied to an IP address anchor.
  • the IP address management apparatus may include an address obtaining module 610 and an information sending module 620.
  • the address obtaining module 610 is configured to obtain a valid IP address prefix that the MN is using when detecting that the mobile node MN accesses the IP subnet where the IP address anchor is located.
  • the information sending module 620 is configured to send, according to the valid IP address prefix, handover indication information to the MN, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the information sending module 620 includes: an address determining submodule 620a, a prefix assigning submodule 620b, a distinguishing identifier submodule 620c, and a first sending submodule 620d.
  • the address judging sub-module 620a is configured to determine whether an IP address prefix allocated by the IP address anchor is already in the valid IP address prefix.
  • the prefix allocation sub-module 620b is configured to allocate an IP address prefix to the MN when there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix.
  • the difference identifier sub-module 620c is configured to distinguish the IP address prefix assigned by the IP address anchor from the IP address prefix assigned by another IP address anchor in the valid IP address prefix.
  • the first sending submodule 620d is configured to send the handover indication information to the MN, where the handover indication information includes: an IP address prefix allocated by the IP address anchor, and an IP address assigned by another IP address anchor A prefix and a type identifier for distinguishing between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the IP address management apparatus sends an IP address to the MN according to the valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address is anchored by the IP address anchor.
  • Switching indication information solving the problem that the existing MN cannot judge whether the IP subnet to which it is connected has changed; and the technology that enables the MN to accurately determine whether the IP subnet to which it is connected has changed. effect.
  • FIG. 8 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • the IP address management device can be applied to an IP address anchor.
  • the IP address management apparatus may include an address obtaining module 610 and an information sending module 620.
  • the address obtaining module 610 is configured to obtain a valid IP address prefix that the MN is using when detecting that the mobile node MN accesses the IP subnet where the IP address anchor is located.
  • the information sending module 620 is configured to send, according to the valid IP address prefix, handover indication information to the MN, so that the MN determines, according to the handover indication information, whether the accessed IP subnet has changed.
  • the information sending module 620 includes: a change determining submodule 620e and a second sending submodule 620f.
  • the change determining sub-module 620e is configured to determine, according to the valid IP address prefix, whether an IP subnet accessed by the MN has changed.
  • the second sending sub-module 620f is configured to send the handover indication information to the MN according to the determination result, where the handover indication information includes a first indicator or a second indicator.
  • the first indicator is used to indicate that the IP subnet accessed by the MN has changed
  • the second indicator is used to indicate that the IP subnet accessed by the MN has not changed.
  • the change determining sub-module 620e includes: an address determining sub-module 620e1, a first determining sub-module 620e2, an identifier determining sub-module 620e3, and a second determining sub-module 620e4.
  • the address judging sub-module 620e1 is configured to determine whether an IP address prefix allocated by the IP address anchor is already in the valid IP address prefix.
  • the first determining sub-module 620e2 is configured to determine that the IP subnet accessed by the MN has changed when there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix.
  • the identifier judging module 620e3 is configured to determine, when the IP address prefix is allocated by the IP address anchor in the valid IP address prefix, whether the IP address prefix assigned by the IP address anchor corresponds to a predetermined identifier. And the predetermined identifier corresponds to an IP address prefix allocated by the MN to the MN before accessing the IP subnet where the IP address anchor is located.
  • the second determining sub-module 620e4 is configured to determine that the IP subnet accessed by the MN does not change when the IP address prefix assigned by the IP address anchor corresponds to the predetermined identifier.
  • the first determining sub-module 620e2 is further configured to determine that the IP subnet accessed by the MN has changed when the IP address prefix assigned by the IP address anchor does not correspond to the predetermined identifier.
  • the device further includes: a prefix allocation submodule, a difference identifier submodule, and a message sending submodule (not shown).
  • a prefix allocation submodule configured to allocate an IP address prefix to the MN when there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix.
  • the difference identifier submodule is configured to distinguish the IP address prefix assigned by the IP address anchor from the IP address prefix assigned by another IP address anchor in the valid IP address prefix.
  • a message sending submodule configured to send a route advertisement message to the MN, where the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the IP address management apparatus is detected by the IP address anchor point.
  • the MN accesses the IP subnet where the IP address is located, the MN sends the handover indication information to the MN according to the valid IP address prefix that the MN is using.
  • the identifier sub-module is specifically configured to: set a first type identifier corresponding to an IP address prefix allocated by the IP address anchor point; And/or, setting a second type identifier corresponding to an IP address prefix assigned by another IP address anchor.
  • the address determining sub-module includes: a network identifier judging sub-module 91, a first determining sub-module 92, and a second The sub-module 93 is determined.
  • the network identifier determining sub-module 91 is configured to determine whether the network identifier corresponding to the IP address anchor exists in the network identifier corresponding to each of the valid IP address prefixes, where the network identifier is an anchor identifier or a network number. .
  • the first determining sub-module 92 is configured to determine, when the network identifier corresponding to the IP address anchor exists, an IP address prefix already allocated by the IP address anchor in the valid IP address prefix.
  • the second determining sub-module 93 is configured to determine, when the network identifier corresponding to the IP address anchor does not exist, that the valid IP address prefix does not have an IP address prefix allocated by the IP address anchor.
  • the address obtaining module includes: a request acquiring submodule and an address receiving submodule (not shown in the figure).
  • Requesting an acquisition submodule configured to send, to the location manager LM, an information acquisition request that carries the node identifier of the MN; so that the LM searches for the MN according to the node identifier of the MN, and obtains the MN from the pre-stored entry.
  • a valid IP address prefix and a network identifier corresponding to each of the valid IP address prefixes wherein each entry includes a correspondence between a node identifier, a network identifier, an IP address prefix, and an expiration date of the IP address prefix, the MN
  • the IP address prefix assigned to the MN by the IP subnet accessed before accessing the IP subnet where the IP address anchor is located also corresponds to a predetermined identifier.
  • the address receiving submodule is configured to receive the valid IP address prefix of the LM feedback and a network identifier corresponding to each of the valid IP address prefixes.
  • the apparatus further includes: requesting a storage submodule (not shown).
  • a requesting storage submodule configured to send an information storage request to the LM, where the information storage request carries a node identifier of the MN, a network identifier corresponding to the IP address anchor point, and is allocated by the IP address anchor point IP address prefix and an expiration date of the IP address prefix assigned by the IP address anchor; such that the LM stores the target entry according to the information storage request, and correspondingly sets the predetermined identifier in the target entry, and The predetermined identifier is removed from an entry in which the IP subnet that the MN accesses before accessing the IP subnet where the IP address anchor is located is assigned an IP address prefix assigned to the MN.
  • the target entry includes: a node identifier of the MN, a network identifier corresponding to the IP address anchor, an IP address prefix allocated by the IP address anchor, and an IP address assigned by the IP address anchor. The correspondence between the validity periods of the prefixes.
  • the device further includes: an address detection submodule and an indication transmission submodule (not shown).
  • An address detection submodule is configured to detect whether a target IP address prefix exists in the valid IP address prefix, where the target IP address prefix refers to an IP address prefix that is not used by the network session for a predetermined duration.
  • a sending submodule configured to: when the target IP address prefix exists in the valid IP address prefix, send an entry deletion indication that carries the node identifier of the MN and the target IP address prefix to the LM, to The LM deletes an entry in which a correspondence between the node identifier of the MN and the target IP address prefix is recorded.
  • FIG. 10 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • the IP address management device can be applied to the MN.
  • the IP address management apparatus may include an information receiving module 1010 and a change judging module 1020.
  • the information receiving module 1010 is configured to receive the handover indication information sent by the IP address anchor point after accessing the IP subnet where the IP address anchor is located.
  • the change determining module 1020 is configured to determine, according to the handover indication information, whether the accessed IP subnet has changed.
  • the IP address management apparatus receives the handover indication information sent by the IP address anchor through the MN, and determines whether the accessed IP subnet has changed according to the handover indication information; A MN with a technology cannot judge whether the IP subnet to which it is connected has changed; so that the MN can accurately determine whether the IP subnet to which it is connected has changed.
  • FIG. 11 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • the IP address management device can be applied to the MN.
  • the IP address management apparatus may include an information receiving module 1010 and a change judging module 1020.
  • the information receiving module 1010 is configured to receive the handover indication information sent by the IP address anchor point after accessing the IP subnet where the IP address anchor is located.
  • the change determining module 1020 is configured to determine, according to the handover indication information, whether the accessed IP subnet has changed.
  • the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier, where the type identifier is used to distinguish the identifier by
  • the IP address prefix assigned by the IP address anchor is prefixed with the IP address assigned by other IP address anchors.
  • the change determining module 1020 includes: a condition determining sub-module 1020a, a third determining sub-module 1020b, and a fourth determining sub-module 1020c.
  • the condition judging sub-module 1020a is configured to determine whether the IP address prefix allocated by the IP address anchor meets a predetermined condition, where the predetermined condition is that the IP address prefix assigned by the IP address anchor is in the The last handover indication information received by the MN does not exist, or the IP address prefix allocated by the IP address anchor exists in the previous handover indication information received by the MN and is identified as being assigned by another IP address anchor. .
  • the third determining sub-module 1020b is configured to determine that the accessed IP subnet has changed when the IP address prefix allocated by the IP address anchor satisfies the predetermined condition.
  • the fourth determining sub-module 1020c is configured to determine that the accessed IP subnet has not changed when the IP address prefix allocated by the IP address anchor does not satisfy the predetermined condition.
  • the IP address management apparatus receives the handover indication information sent by the IP address anchor through the MN, and determines whether the accessed IP subnet has changed according to the handover indication information;
  • the MN with technology can not judge whether the IP subnet to which it is connected has changed; the technical effect that enables the MN to accurately determine whether the IP subnet to which it is connected has changed.
  • FIG. 12 is a block diagram of an IP address management apparatus according to another embodiment of the present invention.
  • the IP address management device can be applied to the MN.
  • the IP address management apparatus may include an information receiving module 1010 and a change judging module 1020.
  • the information receiving module 1010 is configured to receive the handover indication information sent by the IP address anchor point after accessing the IP subnet where the IP address anchor is located.
  • the change determining module 1020 is configured to determine, according to the handover indication information, whether the accessed IP subnet has changed.
  • the handover indication information includes a first indicator or a second indicator, where the first indicator is used to indicate that an IP subnet accessed by the MN has changed, where the The second indicator is used to indicate that the IP subnet accessed by the MN has not changed.
  • the change determining module 1020 includes: a fifth determining sub-module 1020d and a sixth determining sub-module 1020e.
  • the fifth determining sub-module 1020d is configured to determine that the accessed IP subnet has changed when the first indicator is included in the handover indication information.
  • the sixth determining sub-module 1020e is configured to determine that the accessed IP subnet has not changed when the second indicator is included in the handover indication information.
  • the device further includes: a message receiving submodule (not shown).
  • the message receiving submodule is configured to receive a route advertisement message sent by the IP address anchor.
  • the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier, where the type identifier is used to distinguish the identifier by the IP address.
  • the IP address prefix assigned by the anchor is prefixed with the IP address assigned by other IP address anchors.
  • the IP address management apparatus receives the handover indication information sent by the IP address anchor through the MN, and determines whether the accessed IP subnet has changed according to the handover indication information;
  • the MN with technology can not judge whether the IP subnet to which it is connected has changed; the technical effect that enables the MN to accurately determine whether the IP subnet to which it is connected has changed.
  • the type identifier includes a first type identifier and/or a second type identifier.
  • the first type identifier is set corresponding to an IP address prefix assigned by the IP address anchor.
  • the second type identifier is set corresponding to an IP address prefix assigned by another IP address anchor.
  • the apparatus further includes: an address area molecular module 131.
  • the address area numerator module 131 is configured to distinguish an IP address prefix allocated by the IP address anchor from an IP address prefix assigned by another IP address anchor according to the type identifier.
  • the device further includes: a first selection sub-module 132.
  • the first selection sub-module 132 is configured to select a preferred IP address as the source IP address for the new network session when the MN needs to initiate a new network session to the communication peer node CN.
  • the preferred IP address refers to an IP address generated according to an IP address prefix allocated by the IP address anchor and a host address of the MN.
  • the device further includes: a session determining sub-module 133, a second selecting sub-module 134, and a third selecting sub-module 135.
  • the session judging sub-module 133 is configured to determine whether an existing network session with the communication peer node CN can use the preferred IP address as the source IP address; wherein the preferred IP address is allocated according to the IP address anchor point.
  • the second selection sub-module 134 is configured to select the preferred IP address as the source IP address for the existing network session when the existing network session can use the preferred IP address as the source IP address.
  • the third selection sub-module 135 is configured to keep the source IP address used by the existing network session unchanged when the existing network session cannot use the preferred IP address as the source IP address.
  • the session determining sub-module 133 is specifically configured to:
  • the apparatus further includes: an address query module and a session establishment module (not shown).
  • the address querying module is configured to: when the MN determines that the accessed IP subnet has changed, query the IP address of the communication peer node CN that is closest to the MN.
  • a session establishing module configured to establish a network session with the nearest CN according to the IP address.
  • IP address management apparatus provided by the foregoing embodiment, only the division of each functional module is described as an example in the IP address management. In actual applications, the foregoing functions may be assigned to different functional modules according to requirements. Completion, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the IP address management apparatus and the method embodiment of the IP address management method provided by the foregoing embodiments are in the same concept, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • FIG. 14 shows a block diagram of an IP address management system provided by an embodiment of the present invention.
  • the IP address management system includes an IP address anchor 1410 and an MN 1420. among them:
  • the IP address anchor 1410 may include an IP address management device as provided by the embodiment shown in FIG. 6, FIG. 7, or FIG.
  • the MN 1420 may include an IP address management apparatus as provided in the embodiment shown in FIG. 10, FIG. 11, or FIG.
  • IP address anchor 1500 includes a bus 1510, and a processor 1520, a memory 1530, and a transceiver 1540 that communicate over bus 1510.
  • the memory 1530 is configured to store one or more instructions that are configured to be executed by the processor 1520. among them:
  • the processor 1520 is configured to obtain a valid IP address prefix that the MN is using when detecting that the mobile node MN accesses the IP subnet where the IP address anchor is located.
  • the processor 1520 is further configured to: according to the valid IP address prefix, control the transceiver 1540 to send handover indication information to the MN; to enable the MN to determine the accessed IP sub-subject according to the handover indication information. Has the web changed?
  • the IP address anchor provided by this embodiment sends the handover indication information to the MN according to the valid IP address prefix that the MN is using when detecting that the MN accesses the IP subnet where the IP address anchor is located;
  • the problem that the MN cannot determine whether the IP subnet accessed by the MN has changed has been solved in the prior art; and the technical effect of enabling the MN to accurately determine whether the IP subnet to which it is connected has changed is achieved.
  • the processor 1520 is specifically used. to:
  • the MN is assigned an IP address prefix, and the IP address prefix assigned by the IP address anchor is associated with the valid IP address.
  • the IP address prefix assigned by another IP address anchor in the address prefix is distinguished by the identifier;
  • IP address prefix assigns the IP address anchor to the IP address prefix. If there is an IP address prefix assigned by the IP address anchor in the valid IP address prefix, the IP address prefix assigned by the IP address anchor and the other IP address in the valid IP address prefix are anchored.
  • the assigned IP address prefix distinguishes the identifier
  • the transceiver 1540 Controlling the transceiver 1540 to send the handover indication information to the MN, where the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type The identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor.
  • the processor 1520 is specifically configured to:
  • the transceiver 1540 is controlled to send the handover indication information to the MN, where the handover indication information includes a first indicator or a second indicator;
  • the first indicator is used to indicate that the IP subnet accessed by the MN has changed
  • the second indicator is used to indicate that the IP subnet accessed by the MN has not changed.
  • the processor 1520 is specifically configured to:
  • IP address prefix assigned by the IP address anchor is already in the valid IP address prefix, it is determined whether the IP address prefix allocated by the IP address anchor corresponds to a predetermined identifier, where the predetermined identifier corresponds to the The IP subnet that the MN accesses before accessing the IP subnet where the IP address anchor is located is an IP address prefix allocated by the MN;
  • IP address prefix assigned by the IP address anchor corresponds to the predetermined identifier, The IP subnet accessed by the MN has not changed.
  • IP address prefix assigned by the IP address anchor does not correspond to the predetermined identifier, it is determined that the IP subnet accessed by the MN has changed.
  • the processor 1520 is further configured to: if the IP address prefix is not allocated by the IP address anchor in the valid IP address prefix, assign an IP address prefix to the MN, and allocate the IP address by the anchor point.
  • the IP address prefix is distinguished from the IP address prefix assigned by the other IP address anchor in the valid IP address prefix;
  • the processor 1520 is further configured to: if an IP address prefix allocated by the IP address anchor in the valid IP address prefix, the IP address prefix assigned by the IP address anchor and the valid IP The IP address prefix assigned by another IP address anchor in the address prefix is distinguished by the identifier;
  • the processor 1520 is further configured to control the transceiver 1540 to send a route advertisement message to the MN, where the route advertisement message includes: an IP address prefix allocated by the IP address anchor, and an anchor point by another IP address.
  • the route advertisement message includes: an IP address prefix allocated by the IP address anchor, and an anchor point by another IP address.
  • the processor 1520 is specifically configured to:
  • the second type identifier is set corresponding to the IP address prefix assigned by other IP address anchors.
  • the processor 1520 is specifically configured to:
  • the network identifier Determining, in the network identifier corresponding to each of the valid IP address prefixes, whether the network identifier corresponding to the IP address anchor point exists; wherein the network identifier is an anchor point identifier or a network number;
  • IP address anchor If there is no network identifier corresponding to the IP address anchor, it is determined that there is no IP address prefix allocated by the IP address anchor in the valid IP address prefix.
  • the processor 1520 is specifically configured to:
  • a valid IP address prefix and a network identifier corresponding to each of the valid IP address prefixes wherein each entry includes a correspondence between a node identifier, a network identifier, an IP address prefix, and an expiration date of the IP address prefix, where the MN is The IP address prefix allocated to the MN before the IP subnet to which the IP address anchor is located also has a predetermined identifier;
  • the transceiver 1540 is configured to receive the valid IP address prefix of the LM feedback and a network identifier corresponding to each of the valid IP address prefixes.
  • the processor 1520 is further configured to control the transceiver 1540 to send an information storage request to the LM, where the information storage request carries a node identifier of the MN, a network identifier corresponding to the IP address anchor point, An IP address prefix assigned by the IP address anchor and an expiration date of an IP address prefix assigned by the IP address anchor; such that the LM stores a target entry according to the information storage request and is in the target entry Corresponding to setting the predetermined identifier, and the predetermined identifier is an IP address prefix assigned to the MN by the IP subnet accessed by the MN before accessing the IP subnet where the IP address anchor is located. Removed from the entry;
  • the target entry includes: a node identifier of the MN, a network identifier corresponding to the IP address anchor, an IP address prefix allocated by the IP address anchor, and an IP address assigned by the IP address anchor. The correspondence between the validity periods of the prefixes.
  • the processor 1520 is further configured to detect whether a target IP address prefix exists in the valid IP address prefix, where the target IP address prefix refers to an IP address prefix that is not used by the network session for a predetermined duration;
  • the processor 1520 is further configured to: if the target IP address prefix exists in the valid IP address prefix, control the transceiver 1540 to send, to the LM, a node identifier carrying the MN and the target IP An entry deletion instruction of the address prefix, such that the LM deletes an entry in which a correspondence between the node identifier of the MN and the target IP address prefix is recorded.
  • FIG. 16 is a structural block diagram of a MN according to an embodiment of the present invention.
  • the MN 1600 includes a bus 1610, and a processor 1620 that communicates over the bus 1610.
  • the memory 1630 is configured to store one or more instructions that are configured to be executed by the processor 1620. among them:
  • the processor 1620 is configured to, after accessing the IP subnet where the IP address anchor is located, control the transceiver connection 1640 to receive the handover indication information sent by the IP address anchor point;
  • the processor 1620 is further configured to determine, according to the handover indication information, whether the accessed IP subnet has changed.
  • the MN receives the handover indication information sent by the IP address anchor, and determines whether the accessed IP subnet has changed according to the handover indication information.
  • the MN cannot determine whether the IP subnet to which it is connected has changed.
  • the technical effect of enabling the MN to accurately determine whether the IP subnet to which it is connected has changed is achieved.
  • the handover indication information includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier.
  • the type identifier is used to distinguish between an IP address prefix assigned by the IP address anchor and an IP address prefix assigned by another IP address anchor;
  • the processor 1620 is specifically configured to:
  • the predetermined condition is: the last handover indication information received by the IP address prefix by the IP address anchor at the MN
  • the IP address prefix assigned by the IP address anchor exists in the previous handover indication information received by the MN and is identified as being assigned by another IP address anchor;
  • IP address prefix allocated by the IP address anchor satisfies the predetermined condition, it is determined that the accessed IP subnet has changed;
  • IP address prefix assigned by the IP address anchor does not satisfy the predetermined condition, it is determined that the accessed IP subnet has not changed.
  • the handover indication information includes a first indicator or a second indicator, where the first indicator is used to indicate that the MN is connected.
  • the IP subnet has changed, and the second indicator is used to indicate that the IP subnet accessed by the MN has not changed;
  • the processor 1620 is specifically configured to:
  • the second indicator is included in the handover indication information, it is determined that the accessed IP subnet has not changed.
  • the processor 1620 is further configured to control the transceiver 1640 to receive a route advertisement message sent by the IP address anchor point;
  • the route advertisement message includes: an IP address prefix allocated by the IP address anchor, an IP address prefix assigned by another IP address anchor, and a type identifier, where the type identifier is used to distinguish the identifier by the IP address.
  • the IP address prefix assigned by the anchor is prefixed with the IP address assigned by other IP address anchors.
  • the type identifier includes a first type identifier and/or a second type identifier
  • the first type identifier is set corresponding to an IP address prefix assigned by the IP address anchor;
  • the second type identifier is set corresponding to an IP address prefix assigned by another IP address anchor.
  • the processor 1620 is further configured to distinguish, according to the type identifier, an IP address prefix allocated by the IP address anchor from an IP address prefix allocated by another IP address anchor.
  • the processor 1620 is further configured to: when the MN needs to initiate a new network session to the communication peer node CN, select a preferred IP address as the source IP address for the new network session;
  • the preferred IP address refers to an IP address generated according to an IP address prefix allocated by the IP address anchor and a host address of the MN.
  • the processor 1620 is further configured to determine whether an existing network session with the communication peer node CN can use the preferred IP address as the source IP address; wherein the preferred IP address refers to the anchor according to the IP address.
  • the processor 1620 is further configured to: if the existing network session can use the preferred IP address as the source IP address, select the preferred IP address as the source IP address for the existing network session;
  • the processor 1620 is further configured to: if the existing network session cannot use the preferred IP address as the source IP address, keep the source IP address used by the existing network session unchanged.
  • the processor 1620 is specifically used. to:
  • the processor 1620 is further configured to: when the MN determines that the accessed IP subnet has changed, query the IP address of the communication peer node CN that is closest to the MN;
  • the processor 1620 is further configured to establish a network session with the nearest CN according to the IP address.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

本发明实施例提供了一种IP地址管理方法、装置、IP地址锚点及移动节点，涉及通信技术领域，所述方法包括：IP地址锚点在检测到移动节点MN接入该IP地址锚点所在的IP子网时，获取MN正在使用的有效IP地址前缀；IP地址锚点根据有效IP地址前缀向MN发送切换指示信息；以使得MN根据切换指示信息确定所接入的IP子网是否已发生变化。本发明解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。

Description

IP地址管理方法、装置、IP地址锚点及移动节点 技术领域
本发明涉及通信技术领域，特别涉及一种IP地址管理方法、装置、IP地址锚点及移动节点。
背景技术
移动节点(英文：Mobile Node；简称：MN)是指诸如手机、平板电脑、便携式计算机之类的移动终端设备。由于MN的移动性，MN会在多个互联网协议(英文：Internet Protocol；简称：IP)子网间发生移动。为了保证MN在IP子网间发生移动后仍然能够与通信对端节点(英文：Correspondent Node；简称：CN)之间保持通信，移动性管理方案应运而生。
目前，分布式的移动性管理方案应用较为广泛。在分布式移动性管理(英文：Distributed Mobility Management；简称：DMM)网络架构中，包含多个IP子网，每个IP子网对应部署有一个IP地址锚点。在DMM网络中，现有的IP地址管理方法如下：当MN从第一IP子网移动至第二IP子网时，第二IP子网中的IP地址锚点会为MN分配一个IP地址前缀。之后，该IP地址锚点会将其分配的IP地址前缀以及MN正在使用的有效IP地址前缀提供给MN，以使得MN使用上述IP地址前缀继续已有网络会话或者发起新的网络会话。
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：由于同一个IP地址锚点可分配不同的IP地址前缀，因此MN无法根据接收到的IP地址前缀的变化情况准确判断其所接入的IP子网是否已发生变化。
发明内容
为了解决现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题，本发明实施例提供了一种IP地址管理方法、装置、IP地址锚点及移动节点。所述技术方案如下：
第一方面，提供了一种IP地址管理方法，所述方法包括：
IP地址锚点在检测到移动节点MN接入所述IP地址锚点所在的IP子网时， 获取所述MN正在使用的有效IP地址前缀；
所述IP地址锚点根据所述有效IP地址前缀向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在第一方面的第一种可能的实施方式中，所述IP地址锚点根据所述有效IP地址前缀向所述MN发送切换指示信息，包括：
所述IP地址锚点判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
所述IP地址锚点向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第一方面，在第一方面的第二种可能的实施方式中，所述IP地址锚点根据所述有效IP地址前缀向所述MN发送切换指示信息，包括：
所述IP地址锚点根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化；
所述IP地址锚点根据判定结果向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符；
其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
结合第一方面的第二种可能的实施方式，在第一方面的第三种可能的实施方式中，所述IP地址锚点根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化，包括：
所述IP地址锚点判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点判定所述MN所接入的IP子网已发生变化；
若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点判断由所述IP地址锚点分配的IP地址前缀是否对应有预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀；
若由所述IP地址锚点分配的IP地址前缀对应有所述预定标识，则所述IP地址锚点判定所述MN所接入的IP子网未发生变化；
若由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识，则所述IP地址锚点判定所述MN所接入的IP子网已发生变化。
结合第一方面的第三种可能的实施方式，在第一方面的第四种可能的实施方式中，所述方法还包括：
若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
所述IP地址锚点向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第一方面的第一种可能的实施方式或者第一方面的第四种可能的实施方式，在第一方面的第五种可能的实施方式中，所述IP地址锚点将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识，包括：
所述IP地址锚点为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；
和/或，
所述IP地址锚点为由其它IP地址锚点分配的IP地址前缀对应设置第二类 型标识。
结合第一方面的第一种可能的实施方式或者第一方面的第三种可能的实施方式，在第一方面的第六种可能的实施方式中，所述IP地址锚点判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀，包括：
所述IP地址锚点判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号；
若存在所述IP地址锚点对应的网络标识，则所述IP地址锚点确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀；
若不存在所述IP地址锚点对应的网络标识，则所述IP地址锚点确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
结合第一方面的第六种可能的实施方式，在第一方面的第七种可能的实施方式中，所述IP地址锚点获取所述MN正在使用的有效IP地址前缀，包括：
所述IP地址锚点向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识；
所述IP地址锚点接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识。
结合第一方面的第七种可能的实施方式，在第一方面的第八种可能的实施方式中，所述方法还包括：
所述IP地址锚点向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除；
其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
结合第一方面的第七种可能的实施方式，在第一方面的第九种可能的实施方式中，所述方法还包括：
所述IP地址锚点检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀；
若所述有效IP地址前缀中存在所述目标IP地址前缀，则所述IP地址锚点向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP地址前缀之间的对应关系的条目。
第二方面，提供了一种IP地址管理方法，所述方法包括：
移动节点MN在接入IP地址锚点所在的IP子网后，接收所述IP地址锚点发送的切换指示信息；
所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在第二方面的第一种可能的实施方式中，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀；
所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化，包括：
所述MN判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配；
若由所述IP地址锚点分配的IP地址前缀满足所述预定条件，则所述MN判定所接入的IP子网已发生变化；
若由所述IP地址锚点分配的IP地址前缀不满足所述预定条件，则所述MN判定所接入的IP子网未发生变化。
结合第二方面，在第二方面的第二种可能的实施方式中，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化；
所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化，包括：
当所述切换指示信息中包括所述第一指示符时，所述MN判定所接入的IP子网已发生变化；
当所述切换指示信息中包括所述第二指示符时，所述MN判定所接入的IP子网未发生变化。
结合第二方面的第二种可能的实施方式，在第二方面的第三种可能的实施方式中，所述方法还包括：
所述MN接收所述IP地址锚点发送的路由通告消息；
其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第二方面的第一种可能的实施方式或者第二方面的第三种可能的实施方式，在第二方面的第四种可能的实施方式中，所述类型标识包括第一类型标识和/或第二类型标识；
所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置；
所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
结合第二方面的第一种可能的实施方式或者第二方面的第三种可能的实施方式，在第二方面的第五种可能的实施方式中，所述方法还包括：
所述MN根据所述类型标识，区分由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第二方面的第五种可能的实施方式，在第二方面的第六种可能的实施方式中，所述方法还包括：
当所述MN需要向通信对端节点CN发起新网络会话时，所述MN为所述新网络会话选择使用首选IP地址作为源IP地址；
其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和 所述MN的主机地址生成的IP地址。
结合第二方面的第五种可能的实施方式，在第二方面的第七种可能的实施方式中，所述方法还包括：
所述MN判断与通信对端节点CN间的已有网络会话能否使用首选IP地址作为源IP地址；其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址；
若所述已有网络会话能够使用所述首选IP地址作为源IP地址，则所述MN为所述已有网络会话选择使用所述首选IP地址作为源IP地址；
若所述已有网络会话无法使用所述首选IP地址作为源IP地址，则所述MN保持所述已有网络会话所使用的源IP地址不变。
结合第二方面的第七种可能的实施方式，在第二方面的第八种可能的实施方式中，所述MN判断与CN间的已有网络会话能否使用首选IP地址作为源IP地址，包括：
所述MN获取所述已有网络会话所对应的应用程序的配置信息，并根据所述配置信息判断所述已有网络会话能否使用所述首选IP地址作为源IP地址；
或者，
所述MN获取所述已有网络会话所对应的应用程序所使用的传输层协议，并根据所述传输层协议判断所述已有网络会话能否使用所述首选IP地址作为源IP地址。
结合第二方面、第二方面的第一种可能的实施方式、第二方面的第二种可能的实施方式、第二方面的第三种可能的实施方式、第二方面的第四种可能的实施方式、第二方面的第五种可能的实施方式、第二方面的第六种可能的实施方式、第二方面的第七种可能的实施方式或者第二方面的第八种可能的实施方式，在第二方面的第九种可能的实施方式中，所述方法还包括：
当所述MN判定所接入的IP子网已发生变化时，所述MN查询获取距离所述MN最近的通信对端节点CN的IP地址；
所述MN根据所述IP地址与所述最近的CN间建立网络会话。
第三方面，提供了一种IP地址管理装置，应用于IP地址锚点中，所述装置包括：
地址获取模块，用于在检测到移动节点MN接入所述IP地址锚点所在的 IP子网时，获取所述MN正在使用的有效IP地址前缀；
信息发送模块，用于根据所述有效IP地址前缀向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在第三方面的第一种可能的实施方式中，所述信息发送模块，包括：
地址判断子模块，用于判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
前缀分配子模块，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，为所述MN分配IP地址前缀；
区别标识子模块，用于将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
第一发送子模块，用于向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第三方面，在第三方面的第二种可能的实施方式中，所述信息发送模块，包括：
变化判定子模块，用于根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化；
第二发送子模块，用于根据判定结果向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符；
其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
结合第三方面的第二种可能的实施方式，在第三方面的第三种可能的实施方式中，所述变化判定子模块，包括：
地址判断子模块，用于判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
第一判定子模块，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，判定所述MN所接入的IP子网已发生变化；
标识判断子模块，用于当所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀时，判断由所述IP地址锚点分配的IP地址前缀是否对应有 预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀；
第二判定子模块，用于当由所述IP地址锚点分配的IP地址前缀对应有所述预定标识时，判定所述MN所接入的IP子网未发生变化；
所述第一判定子模块，还用于当由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识时，判定所述MN所接入的IP子网已发生变化。
结合第三方面的第三种可能的实施方式，在第三方面的第四种可能的实施方式中，所述装置还包括：
前缀分配子模块，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，为所述MN分配IP地址前缀；
区别标识子模块，用于将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
消息发送子模块，用于向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第三方面的第一种可能的实施方式或者第三方面的第四种可能的实施方式，在第三方面的第五种可能的实施方式中，所述区别标识子模块，具体用于：
为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；
和/或，
为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
结合第三方面的第一种可能的实施方式或者第三方面的第三种可能的实施方式，在第三方面的第六种可能的实施方式中，所述地址判断子模块，包括：
网络标识判断子模块，用于判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号；
第一确定子模块，用于当存在所述IP地址锚点对应的网络标识时，确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀；
第二确定子模块，用于当不存在所述IP地址锚点对应的网络标识时，确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
结合第三方面的第六种可能的实施方式，在第三方面的第七种可能的实施方式中，所述地址获取模块，包括：
请求获取子模块，用于向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识；
地址接收子模块，用于接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识。
结合第三方面的第七种可能的实施方式，在第三方面的第八种可能的实施方式中，所述装置还包括：
请求存储子模块，用于向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除；
其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
结合第三方面的第七种可能的实施方式，在第三方面的第九种可能的实施方式中，所述装置还包括：
地址检测子模块，用于检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀；
指示发送子模块，用于当所述有效IP地址前缀中存在所述目标IP地址前缀时，向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP 地址前缀之间的对应关系的条目。
第四方面，提供了一种IP地址管理装置，应用于移动节点MN中，所述装置包括：
信息接收模块，用于在接入IP地址锚点所在的IP子网后，接收所述IP地址锚点发送的切换指示信息；
变化判断模块，用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在第四方面的第一种可能的实施方式中，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀；
所述变化判断模块，包括：
条件判断子模块，用于判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配；
第三判定子模块，用于当由所述IP地址锚点分配的IP地址前缀满足所述预定条件时，判定所接入的IP子网已发生变化；
第四判定子模块，用于当由所述IP地址锚点分配的IP地址前缀不满足所述预定条件时，判定所接入的IP子网未发生变化。
结合第四方面，在第四方面的第二种可能的实施方式中，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化；
所述变化判断模块，包括：
第五判定子模块，用于当所述切换指示信息中包括所述第一指示符时，判定所接入的IP子网已发生变化；
第六判定子模块，用于当所述切换指示信息中包括所述第二指示符时，判定所接入的IP子网未发生变化。
结合第四方面的第二种可能的实施方式，在第四方面的第三种可能的实施方式中，所述装置还包括：
消息接收子模块，用于接收所述IP地址锚点发送的路由通告消息；
其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第四方面的第一种可能的实施方式或者第四方面的第三种可能的实施方式，在第四方面的第四种可能的实施方式中，所述类型标识包括第一类型标识和/或第二类型标识；
所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置；
所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
结合第四方面的第一种可能的实施方式或者第四方面的第三种可能的实施方式，在第四方面的第五种可能的实施方式中，所述装置还包括：
地址区分子模块，用于根据所述类型标识，区分由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第四方面的第五种可能的实施方式，在第四方面的第六种可能的实施方式中，所述装置还包括：
第一选择子模块，用于当所述MN需要向通信对端节点CN发起新网络会话时，为所述新网络会话选择使用首选IP地址作为源IP地址；
其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址。
结合第四方面的第五种可能的实施方式，在第四方面的第七种可能的实施方式中，所述装置还包括：
会话判断子模块，用于判断与通信对端节点CN间的已有网络会话能否使用首选IP地址作为源IP地址；其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址；
第二选择子模块，用于当所述已有网络会话能够使用所述首选IP地址作为源IP地址时，为所述已有网络会话选择使用所述首选IP地址作为源IP地址；
第三选择子模块，用于当所述已有网络会话无法使用所述首选IP地址作为源IP地址时，保持所述已有网络会话所使用的源IP地址不变。
结合第四方面的第七种可能的实施方式，在第四方面的第八种可能的实施方式中，所述会话判断子模块，具体用于：
获取所述已有网络会话所对应的应用程序的配置信息，并根据所述配置信息判断所述已有网络会话能否使用所述首选IP地址作为源IP地址；
或者，
获取所述已有网络会话所对应的应用程序所使用的传输层协议，并根据所述传输层协议判断所述已有网络会话能否使用所述首选IP地址作为源IP地址。
结合第四方面、第四方面的第一种可能的实施方式、第四方面的第二种可能的实施方式、第四方面的第三种可能的实施方式、第四方面的第四种可能的实施方式、第四方面的第五种可能的实施方式、第四方面的第六种可能的实施方式、第四方面的第七种可能的实施方式或者第四方面的第八种可能的实施方式，在第四方面的第九种可能的实施方式中，所述装置还包括：
地址查询模块，用于当所述MN判定所接入的IP子网已发生变化时，查询获取距离所述MN最近的通信对端节点CN的IP地址；
会话建立模块，用于根据所述IP地址与所述最近的CN间建立网络会话。
第五方面，提供了一种IP地址锚点，所述IP地址锚点包括：处理器、存储器和收发器，其中所述存储器用于存储一个或者一个以上的指令，所述指令被配置成由所述处理器执行；
所述处理器，用于在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀；
所述处理器，还用于根据所述有效IP地址前缀，控制所述收发器向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在第五方面的第一种可能的实施方式中，所述处理器，具体用于：
判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则 将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
控制所述收发器向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第五方面，在第五方面的第二种可能的实施方式中，所述处理器，具体用于：
根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化；
根据判定结果，控制所述收发器向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符；
其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
结合第五方面的第二种可能的实施方式，在第五方面的第三种可能的实施方式中，所述处理器，具体用于：
判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则判定所述MN所接入的IP子网已发生变化；
若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则判断由所述IP地址锚点分配的IP地址前缀是否对应有预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀；
若由所述IP地址锚点分配的IP地址前缀对应有所述预定标识，则判定所述MN所接入的IP子网未发生变化；
若由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识，则判定所述MN所接入的IP子网已发生变化。
结合第五方面的第三种可能的实施方式，在第五方面的第四种可能的实施方式中，所述处理器，还用于若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP 地址前缀区别标识；
所述处理器，还用于若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
所述处理器，还用于控制所述收发器向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第五方面的第一种可能的实施方式或者第五方面的第四种可能的实施方式，在第五方面的第五种可能的实施方式中，所述处理器，具体用于：
为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；
和/或，
为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
结合第五方面的第一种可能的实施方式或者第五方面的第三种可能的实施方式，在第五方面的第六种可能的实施方式中，所述处理器，具体用于：
判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号；
若存在所述IP地址锚点对应的网络标识，则确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀；
若不存在所述IP地址锚点对应的网络标识，则确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
结合第五方面的第六种可能的实施方式，在第五方面的第七种可能的实施方式中，所述处理器，具体用于：
控制所述收发器向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识；
控制所述收发器接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识。
结合第五方面的第七种可能的实施方式，在第五方面的第八种可能的实施方式中，所述处理器，还用于控制所述收发器向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除；
其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
结合第五方面的第七种可能的实施方式，在第五方面的第九种可能的实施方式中，所述处理器，还用于检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀；
所述处理器，还用于若所述有效IP地址前缀中存在所述目标IP地址前缀，则控制所述收发器向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP地址前缀之间的对应关系的条目。
第六方面，提供了一种移动节点MN，所述MN包括：处理器、存储器和收发器，其中所述存储器用于存储一个或者一个以上的指令，所述指令被配置成由所述处理器执行；
所述处理器，用于在接入IP地址锚点所在的IP子网后，控制所述收发器接收所述IP地址锚点发送的切换指示信息；
所述处理器，还用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在第六方面的第一种可能的实施方式中，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀；
所述处理器，具体用于：
判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配；
若由所述IP地址锚点分配的IP地址前缀满足所述预定条件，则判定所接入的IP子网已发生变化；
若由所述IP地址锚点分配的IP地址前缀不满足所述预定条件，则判定所接入的IP子网未发生变化。
结合第六方面，在第六方面的第二种可能的实施方式中，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化；
所述处理器，具体用于：
当所述切换指示信息中包括所述第一指示符时，判定所接入的IP子网已发生变化；
当所述切换指示信息中包括所述第二指示符时，判定所接入的IP子网未发生变化。
结合第六方面的第二种可能的实施方式，在第六方面的第三种可能的实施方式中，所述处理器，还用于控制所述收发器接收所述IP地址锚点发送的路由通告消息；
其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第六方面的第一种可能的实施方式或者第六方面的第三种可能的实施方式，在第六方面的第四种可能的实施方式中，所述类型标识包括第一类型标识和/或第二类型标识；
所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置；
所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
结合第六方面的第一种可能的实施方式或者第六方面的第三种可能的实施方式，在第六方面的第五种可能的实施方式中，所述处理器，还用于根据所述类型标识，区分由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
结合第六方面的第五种可能的实施方式，在第六方面的第六种可能的实施方式中，所述处理器，还用于当所述MN需要向通信对端节点CN发起新网络会话时，为所述新网络会话选择使用首选IP地址作为源IP地址；
其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址。
结合第六方面的第五种可能的实施方式，在第六方面的第七种可能的实施方式中，所述处理器，还用于判断与通信对端节点CN间的已有网络会话能否使用首选IP地址作为源IP地址；其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址；
所述处理器，还用于若所述已有网络会话能够使用所述首选IP地址作为源IP地址，则为所述已有网络会话选择使用所述首选IP地址作为源IP地址；
所述处理器，还用于若所述已有网络会话无法使用所述首选IP地址作为源IP地址，则保持所述已有网络会话所使用的源IP地址不变。
结合第六方面的第七种可能的实施方式，在第六方面的第八种可能的实施方式中，所述处理器，具体用于：
获取所述已有网络会话所对应的应用程序的配置信息，并根据所述配置信息判断所述已有网络会话能否使用所述首选IP地址作为源IP地址；
或者，
获取所述已有网络会话所对应的应用程序所使用的传输层协议，并根据所述传输层协议判断所述已有网络会话能否使用所述首选IP地址作为源IP地址。
结合第六方面、第六方面的第一种可能的实施方式、第六方面的第二种可能的实施方式、第六方面的第三种可能的实施方式、第六方面的第四种可能的实施方式、第六方面的第五种可能的实施方式、第六方面的第六种可能的实施方式、第六方面的第七种可能的实施方式或者第六方面的第八种可能的实施方式，在第六方面的第九种可能的实施方式中，所述处理器，还用于当所述MN判定所接入的IP子网已发生变化时，查询获取距离所述MN最近的通信对端节点CN的IP地址；
所述处理器，还用于根据所述IP地址与所述最近的CN间建立网络会话。
本发明实施例提供的技术方案的有益效果包括：
通过IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前缀向MN发送切换指示信息，以使得MN根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
另外，还通过IP地址锚点在向MN提供当前可用的IP地址前缀时，通过类型标识将由该IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀区别标识，使得MN可基于类型标识将上述两种不同类型的IP地址前缀进行区分。进一步地，MN通过为新网络会话和自身能够处理IP地址的变化的已有网络会话选择使用首选IP地址作为源IP地址，达到了减少路由冗余的技术效果。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例所涉及的一种实施环境的示意图；
图2是本发明一个实施例提供的IP地址管理方法的流程图；
图3是本发明另一实施例提供的IP地址管理方法的流程图；
图4是本发明另一实施例提供的IP地址管理方法的流程图；
图5A是本发明另一实施例提供的IP地址管理方法的流程图；
图5B是图5A所示实施例中涉及的步骤502的流程图；
图6是本发明一个实施例提供的IP地址管理装置的框图；
图7是本发明另一实施例提供的IP地址管理装置的框图；
图8是本发明另一实施例提供的IP地址管理装置的框图；
图9是本发明实施例所涉及的地址判断子模块的框图；
图10是本发明另一实施例提供的IP地址管理装置的框图；
图11是本发明另一实施例提供的IP地址管理装置的框图；
图12是本发明另一实施例提供的IP地址管理装置的框图；
图13是根据图11和图12所示实施例提供的另一IP地址管理装置的框图；
图14是本发明一个实施例提供的IP地址管理系统的框图；
图15是本发明一个实施例提供的IP地址锚点的结构方框图；
图16是本发明一个实施例提供的MN的结构方框图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
请参考图1，其示出了本发明实施例所涉及的一种实施环境的示意图。该实施环境中包括多个IP子网，图1中以IP子网1和IP子网2为例。每个IP子网中对应部署有IP地址锚点120和CN140。该实施环境中还包括可在上述多个IP子网中移动的MN160。其中：
MN160可以是诸如手机、平板电脑、便携式计算机之类的移动终端设备。
IP地址锚点120用于为MN160提供移动性支持。在一种可能的实施方式中，IP地址锚点120可以是网关设备，如公共数据网(英文：Public Data Network；简称：PND)网关PGW。
CN160可以是用于向MN160提供网络业务的服务器。例如，该网络业务可以是下载业务、视频业务、网络电话业务等等。不同IP子网中的CN140所具有业务功能和业务资源可以相同，也可以不同。
请参考图2，其示出了本发明一个实施例提供的IP地址管理方法的流程图。本实施例以该IP地址管理方法应用于图1所示实施环境中的IP地址锚点120中进行举例说明。该IP地址管理方法可以包括如下步骤：
步骤202，IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，获取MN正在使用的有效IP地址前缀。
步骤204，IP地址锚点根据有效IP地址前缀向MN发送切换指示信息；以使得MN根据该切换指示信息确定所接入的IP子网是否已发生变化。
综上所述，本实施例提供的IP地址管理方法，通过IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前 缀向MN发送切换指示信息；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
请参考图3，其示出了本发明另一实施例提供的IP地址管理方法的流程图。本实施例以该IP地址管理方法应用于图1所示实施环境中的MN160中进行举例说明。该IP地址管理方法可以包括如下步骤：
步骤302，MN在接入IP地址锚点所在的IP子网后，接收IP地址锚点发送的切换指示信息。
步骤304，MN根据切换指示信息确定所接入的IP子网是否已发生变化。
综上所述，本实施例提供的IP地址管理方法，通过MN接收IP地址锚点发送的切换指示信息，并根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
请参考图4，其示出了本发明另一实施例提供的IP地址管理方法的流程图。本实施例以该IP地址管理方法应用于图1所示实施环境中进行举例说明。该IP地址管理方法可以包括如下步骤：
步骤401，IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，获取MN正在使用的有效IP地址前缀。
IP地址锚点在为MN分配IP地址前缀之后，会相应设置该IP地址前缀的有效期。处于有效期之内且未被释放的IP地址前缀即为有效IP地址前缀。
步骤402，IP地址锚点判断有效IP地址前缀中是否已有由该IP地址锚点分配的IP地址前缀。
若否，则执行下述步骤403，并在步骤403之后执行步骤404；若是，则直接执行步骤404。
结合参考图1，假设MN当前所接入的IP子网是IP子网2，IP子网2中的IP地址锚点记为anchor#2。MN可能是从其它IP子网移动至IP子网2的，因此上述有效IP地址前缀中可能存在其它IP地址锚点为MN分配的IP地址前缀。例如，MN从IP子网1移动至IP子网2，IP子网1中的IP地址锚点记为 anchor#1，则anchor#2在检测到MN接入IP子网2时，获取的MN正在使用的有效IP地址前缀中可以包含由anchor#1为MN分配的IP地址前缀，记为prefix#1。
另外，若MN之前已经接入过IP子网2，则anchor#2获取的MN正在使用的有效IP地址前缀中可以包含由anchor#2为MN分配的IP地址前缀，记为prefix#2。例如，MN从IP子网2移动至IP子网1，又从IP子网1移动至IP子网2，则anchor#2在检测到MN接入IP子网2时，获取的MN正在使用的有效IP地址前缀中可以包含prefix#1和prefix#2。
步骤403，IP地址锚点为MN分配IP地址前缀。
仍然以上述假设为例，当MN正在使用的有效IP地址前缀中没有由anchor#2为其分配的IP地址前缀时，anchor#2为MN分配IP地址前缀，记为prefix#2。之后，anchor#2执行下述步骤404。
另外，当MN正在使用的有效IP地址前缀中已有由anchor#2为其分配的IP地址前缀时，anchor#2无需再为MN分配IP地址前缀，直接执行下述步骤404。
步骤404，IP地址锚点将由该IP地址锚点分配的IP地址前缀与有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识。
具体来讲，IP地址锚点为由该IP地址锚点分配的IP地址前缀对应设置第一类型标识；和/或，IP地址锚点为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
在本实施例中，以第一类型标识为H-prefix，第二类型标识为F-prefix为例。
在第一种可能的实施方式中，IP地址锚点为prefix#2对应设置第一类型标识H-prefix。
在第二种可能的实施方式中，IP地址锚点为prefix#1对应设置第二类型标识F-prefix。
在第三种可能的实施方式中，IP地址锚点为prefix#2对应设置第一类型标识H-prefix，并为prefix#1对应设置第二类型标识F-prefix。
上述三种可能的实施方式均可达到将两种不同类型的IP地址前缀进行区别标识的目的。
步骤405，IP地址锚点向MN发送切换指示信息，该切换指示信息包括： 由该IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识。
其中，类型标识用于区别标识由该IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。也即，上述步骤404中介绍的第一类型标识和/或第二类型标识。
可选地，切换指示信息以路由通告(英文：Router Advertisement；简称：RA)消息的形式发送给MN。
相应地，MN接收IP地址锚点发送的切换指示信息。
步骤406，MN判断由该IP地址锚点分配的IP地址前缀是否满足预定条件。
若是，则执行下述步骤407；若否，则执行下述步骤408。
其中，预定条件是指：由该IP地址锚点分配的IP地址前缀在MN接收的上一条切换指示信息中不存在，或者，由该IP地址锚点分配的IP地址前缀在MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配。
MN在接收到当前所接入的IP子网中的IP地址锚点发送的切换指示信息后，根据类型标识便可区分由该IP地址锚点分配的IP地址前缀和由其它IP地址锚点分配的IP地址前缀。
以上述步骤404中的第三种可能的实施方式为例，MN在接收到anchor#2发送的切换指示信息后，根据第一类型标识H-prefix，确定对应的prefix#2为anchor#2分配的IP地址前缀。当该prefix#2在MN接收的上一条切换指示信息中不存在，或者当该prefix#2在MN接收的上一条切换指示信息中存在且对应第二类型标识F-prefix时，MN执行下述步骤407。当该prefix#2在MN接收的上一条切换指示信息中存在且对应第一类型标识H-prefix时，MN执行下述步骤408。
步骤407，MN判定所接入的IP子网已发生变化。
步骤408，MN判定所接入的IP子网未发生变化。
综上所述，本实施例提供的IP地址管理方法，通过IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前缀向MN发送切换指示信息，以使得MN根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网 是否已发生变化的技术效果。
另外，本实施例提供的IP地址管理方法，通过类型标识将由该IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀区别标识；一方面，使得MN根据前后两条切换指示信息中包含的IP地址前缀的变化以及相应的类型标识的变化，能够准确判断其所接入的IP子网是否已发生变化；另一方面，使得MN根据该类型标识可很容易地分辨出两种不同类型的IP地址前缀，以便后续在进行网络会话时更为合理地利用不同类型的IP地址前缀，达到减少路由冗余的目的。
在上述图4所示实施例中，由MN判定其所接入的IP子网是否已发生变化。在下述图5A所示实施例中，由IP地址锚点判定MN所接入的IP子网是否已发生变化，并将该判定结果直接告知给MN。
请参考图5A，其示出了本发明另一实施例提供的IP地址管理方法的流程图。本实施例以该IP地址管理方法应用于图1所示实施环境中进行举例说明。该IP地址管理方法可以包括如下步骤：
步骤501，IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，获取MN正在使用的有效IP地址前缀。
步骤502，IP地址锚点根据有效IP地址前缀判定MN所接入的IP子网是否已发生变化。
具体来讲，如图5B所示，本步骤可以包括如下几个子步骤：
步骤502a，IP地址锚点判断有效IP地址前缀中是否已有由该IP地址锚点分配的IP地址前缀。
若否，则执行下述步骤502d；若是，则执行下述步骤502b。
结合参考图1，仍然假设MN当前所接入的IP子网是IP子网2，IP子网2中的IP地址锚点记为anchor#2。假设anchor#2获取的MN正在使用的有效IP地址前缀包括prefix#1、prefix#2和prefix#3。anchor#2判断上述三个IP地址前缀中是否已有由anchor#2分配的IP地址前缀。
比如，anchor#2发现上述三个IP地址前缀均不是由anchor#2为MN分配的IP地址前缀，则anchor#2执行下述步骤502d，判定MN所接入的IP子网已发生变化。
再比如，anchor#2发现prefix#1是由anchor#2为MN分配的IP地址前缀，则anchor#2执行下述步骤502b。
步骤502b，IP地址锚点判断由该IP地址锚点分配的IP地址前缀是否对应有预定标识。
若是，则执行下述步骤502c；若否，则执行下述步骤502d。
其中，预定标识对应于MN在接入该IP地址锚点所在的IP子网之前所接入的IP子网为MN分配的IP地址前缀。例如，该预定标识可记为current anchor。
当anchor#2发现prefix#1是由anchor#2为MN分配的IP地址前缀时，anchor#2进一步判断prefix#1是否对应有预定标识current anchor。当prefix#1对应有预定标识current anchor时，说明MN所接入的IP子网未发生变化；反之，当prefix#1未对应有预定标识current anchor，如prefix#2或prefix#3对应有预定标识current anchor时，说明MN所接入的IP子网已发生变化。
步骤502c，IP地址锚点判定MN所接入的IP子网未发生变化。
步骤502d，IP地址锚点判定MN所接入的IP子网已发生变化。
步骤503，IP地址锚点根据判定结果向MN发送切换指示信息，该切换指示信息包括第一指示符或者第二指示符。
其中，第一指示符用于指示MN所接入的IP子网已发生变化，第二指示符用于指示MN所接入的IP子网未发生变化。
相应地，MN接收IP地址锚点发送的切换指示信息。
步骤504，MN根据切换指示信息确定所接入的IP子网是否已发生变化。
当切换指示信息中包括第一指示符时，MN判定所接入的IP子网已发生变化。
当切换指示信息中包括第二指示符时，MN判定所接入的IP子网未发生变化。
可选地，上述步骤502a之后，还包括如下步骤：
1、若有效IP地址前缀中没有由该IP地址锚点分配的IP地址前缀，则IP地址锚点为MN分配IP地址前缀，并将由该IP地址锚点分配的IP地址前缀与有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识。
2、若有效IP地址前缀中已有由该IP地址锚点分配的IP地址前缀，则IP地址锚点将由该IP地址锚点分配的IP地址前缀与有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识。
3、IP地址锚点向MN发送路由通告消息，该路由通告消息包括：由该IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识。
其中，类型标识用于区别标识由该IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
上述步骤1至3在图4所示实施例中已经介绍和说明，具体参见图4所示实施例中的介绍和说明，本实施例对此不再赘述。
相应地，MN接收IP地址锚点发送的路由通告消息。MN根据类型标识，区分由该IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
IP地址锚点通过路由通告消息告知MN当前可使用的IP地址前缀，并利用类型标识将由其自身分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀区别标识，使得MN根据该类型标识可很容易地分辨出两种不同类型的IP地址前缀，以便后续在进行网络会话时更为合理地利用不同类型的IP地址前缀，达到减少路由冗余的目的。
可选地，切换指示信息可以携带在路由通告消息中发送给MN。
综上所述，本实施例提供的IP地址管理方法，通过IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前缀向MN发送切换指示信息，以使得MN根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
另外，本实施例提供的IP地址管理方法，通过IP地址锚点判定MN所接入的IP子网是否已发生变化，并将该判定结果直接告知给MN，减少了MN侧的处理开销。
需要补充说明的一点是，上述图4所示实施例中的步骤402和图5A所示实施例中的步骤502a，也即IP地址锚点判断有效IP地址前缀中是否已有由该IP地址锚点分配的IP地址前缀的步骤，可以包括如下几个子步骤：
(1)，IP地址锚点判断各个有效IP地址前缀分别对应的网络标识中，是否存在该IP地址锚点对应的网络标识。
若是，则执行下述步骤(2)；若否，则执行下述步骤(3)。
(2)，IP地址锚点确定有效IP地址前缀中已有由该IP地址锚点分配的IP地址前缀。
(3)，IP地址锚点确定有效IP地址前缀中没有由该IP地址锚点分配的IP地址前缀。
其中，网络标识为锚点标识或者网络号。不同的IP地址锚点对应于不同的网络标识。以网络标识为锚点标识为例，不同的IP地址锚点可以anchor#1、anchor#2、anchor#3等不同的锚点标识进行区分。
IP地址锚点在获取MN正在使用的有效IP地址前缀时，一并获取各个有效IP地址前缀分别对应的网络标识，据此判断有效IP地址前缀中是否已有由其自身分配的IP地址前缀。
例如，anchor#2获取的MN正在使用的有效IP地址前缀包括prefix#1、prefix#2和prefix#3，该三个IP地址前缀分别对应的网络标识依次为anchor#1、anchor#2和anchor#3。那么，anchor#2便可确定该三个IP地址前缀中已有由其自身分配的IP地址前缀，即prefix#2。
在一种可能的实施方式中，可在图1所示实施环境中部署一个独立实体，记为位置管理器(英文：Location Manager；简称：LM)。LM可以覆盖多个IP子网，即LM与IP地址锚点之间可以是一对多的关系。LM用于记录每个IP地址锚点为MN分配的有效IP地址前缀的列表。比如，LM中可存储多个条目，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系。IP地址锚点可从LM中查询获取MN正在使用的有效IP地址前缀。
具体来讲，IP地址锚点获取MN正在使用的有效IP地址前缀的步骤，可以包括如下几个子步骤：
第一，IP地址锚点向LM发送携带有MN的节点标识的信息获取请求；以使得LM根据MN的节点标识，从预存的条目中查找获取MN正在使用的有效IP地址前缀以及各个有效IP地址前缀分别对应的网络标识。
第二，IP地址锚点接收LM反馈的有效IP地址前缀以及各个有效IP地址前缀分别对应的网络标识。
例如，LM中存储有如下表-1所示的多个条目：
条目序号 节点标识 网络标识 IP地址前缀 有效期 状态
1 MN#1 anchor#1 prefix#1 time#1 current anchor
2 MN#1 anchor#3 prefix#3 time#2  
3 MN#2 anchor#2 prefix#2 time#3 current anchor
4 MN#2 anchor#1 prefix#1 time#4  
… … … … … …
表-1
anchor#2在检测到MN#1接入IP子网2时，anchor#2向LM发送携带有MN#1的信息获取请求。相应地，LM从预存的条目中查找获取包含节点标识MN#1的条目，如上述表-1中的条目1和2，LM将上述条目1和2发送给anchor#2。相应地，anchor#2便可从接收的条目中获取MN#1正在使用的有效IP地址前缀，即prefix#1和prefix#3。
进一步地，anchor#2可根据各个有效IP地址前缀分别对应的网络标识，区分由其自身为MN#1分配的IP地址前缀与由其它IP地址锚点为MN#1分配的IP地址前缀。上述prefix#1和prefix#3均不是由anchor#2为MN#1分配的IP地址前缀。
更进一步地，LM存储的条目中还包括预定标识current anchor。anchor#2接收到LM发送的上述条目1和2之后，检测发现由anchor#1分配的prefix#1对应有预定标识current anchor，则说明MN#1是由anchor#1所处的IP子网1移动至anchor#2所处的IP子网2的，MN#1所接入的IP子网已发生变化。
另外，IP地址锚点为MN分配IP地址前缀之后，向LM发送信息存储请求。该信息存储请求中携带有MN的节点标识、IP地址锚点对应的网络标识、由IP地址锚点分配的IP地址前缀以及由IP地址锚点分配的IP地址前缀的有效期。以使得LM根据该信息存储请求存储目标条目，并在目标条目中对应设置预定标识，而将预定标识从记录有MN在接入IP地址锚点所在的IP子网之前所接入的IP子网为MN分配的IP地址前缀的条目中移除。其中，目标条目包括：MN的节点标识、该IP地址锚点对应的网络标识、由该IP地址锚点分配的IP地址前缀以及由该IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
比如，anchor#2接收到LM发送的上述条目1和2之后，检测发现MN#1 正在使用的有效IP地址前缀中没有由其自身分配的IP地址前缀，则anchor#2为MN#1分配一个IP地址前缀，记为prefix#2。并且，anchor#2设置prefix#2对应的有效期，记为time#5。之后，anchor#2向LM发送信息存储请求，该信息存储请求中携带有节点标识MN#1、网络标识anchor#2、IP地址前缀prefix#2以及有效期time#5。相应地，LM在接收到anchor#2发送的信息存储请求之后，对预存的条目进行更新。更新后的条目可以如下表-2所示：
条目序号 节点标识 网络标识 IP地址前缀 有效期 状态
1 MN#1 anchor#2 prefix#2 time#5 current anchor
2 MN#1 anchor#1 prefix#1 time#1  
3 MN#1 anchor#3 prefix#3 time#2  
4 MN#2 anchor#2 prefix#2 time#3 current anchor
5 MN#2 anchor#1 prefix#1 time#4  
… … … … … …
表-2
anchor#2存储表-2中的条目1，并在该条目中对应设置预定标识current anchor，而将预定标识current anchor从表-2中的条目2(也即表-1中的条目1)中移除。
还需要补充说明的一点是，本发明实施例还提供了一种对LM中存储的条目的维护机制。具体如下：IP地址锚点检测有效IP地址前缀中是否存在目标IP地址前缀，该目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀。若有效IP地址前缀中存在目标IP地址前缀，则IP地址锚点向LM发送携带有MN的节点标识和目标IP地址前缀的条目删除指示，以使得LM删除记录有MN的节点标识和目标IP地址前缀之间的对应关系的条目。
例如，当anchor#2检测发现prefix#3超过预定时长未被网络会话使用时，则说明MN#1已经不需要再使用该prefix#3了，anchor#2向LM发送携带有MN#1和prefix#3的条目删除指示。相应地，LM在接收到anchor#2发送的上述条目删除指示后，将上述表-2中的条目3删除。
本发明实施例通过上述维护机制，一方面可以确保LM中存储的条目的准确性和实时性，另一方面也有利于节约LM的存储资源。
还需要补充说明的一点是，结合参考图1所示的实施环境，可在每个IP 子网中部署一个移动性管理(英文：Mobility Management；简称：MM)实体。MM实体用于负责执行IP地址锚点与LM之间与移动性管理相关的信令交互。MM实体可以作为一个独立实体进行部署，或者MM实体也可与IP地址锚点集成于一体。
例如，IP地址锚点从LM中查询获取MN正在使用的有效IP地址前缀的流程如下：
1，IP地址锚点向MM实体发送携带有MN的节点标识的信息获取请求；
2，MM实体向LM转发该信息获取请求；
3，LM根据MN的节点标识，从预存的条目中查找获取MN正在使用的有效IP地址前缀以及各个有效IP地址前缀分别对应的网络标识；
4，LM向MM实体发送该有效IP地址前缀以及各个有效IP地址前缀分别对应的网络标识；
5，MM实体向IP地址锚点转发该有效IP地址前缀以及各个有效IP地址前缀分别对应的网络标识。
下面，对MN在进行网络会话时，对不同类型的IP地址前缀的选择进行介绍和说明。
在上述图4和图5A所示实施例中已经介绍，IP地址锚点在向MN提供当前可用的IP地址前缀时，通过类型标识将由该IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀区别标识。MN可基于类型标识将上述两种不同类型的IP地址前缀进行区分。下面，分新网络会话和已有网络会话两种情况，对不同类型的IP地址前缀的选择进行介绍和说明。
第一，新网络会话
当MN需要向CN发起新网络会话时，MN为该新网络会话选择使用首选IP地址作为源IP地址。其中，首选IP地址是指根据由当前所接入的IP子网中的IP地址锚点分配的IP地址前缀和MN的主机地址生成的IP地址。
比如，结合参考图1，MN从IP子网1移动至IP子网2，IP子网2中的anchor#2向MN发送的RA消息中包括：prefix#1和prefix#2。其中，prefix#1对应设置有第二类型标识F-prefix，prefix#2对应设置有第一类型标识H-prefix。假设MN根据prefix#1和自身的主机地址生成的IP地址为IP address#1，根据prefix#2和自身的主机地址生成的IP地址为IP address#2。对于新网络会话， MN为该新网络会话选择使用IP address#2作为源IP地址与CN进行通信，从而达到减少路由冗余的目的。
第二，已有网络会话
MN判断与CN间的已有网络会话能否使用首选IP地址作为源IP地址。其中，首选IP地址是指根据由当前所接入的IP子网中的IP地址锚点分配的IP地址前缀和MN的主机地址生成的IP地址。若已有网络会话能够使用首选IP地址作为源IP地址，则MN为该已有网络会话选择使用首选IP地址作为源IP地址；反之，若已有网络会话无法使用首选IP地址作为源IP地址，则MN保持已有网络会话所使用的源IP地址不变。
仍然以上述假设为例，对于已有网络会话，MN在移动至IP子网2之前，也即当MN在接入IP子网1时，该已有网络会话使用IP address#1作为源IP地址与CN进行通信。MN在移动至IP子网2之后，MN判断该已有网络会话自身能否处理IP地址的变化，也即判断该已有网络会话能否使用IP address#2作为源IP地址与CN进行通信。若可以，则MN为该已有网络会话选择使用IP address#2作为源IP地址与CN进行通信，从而达到减少路由冗余的目的。若不可以，则MN保持该已有网络会话所使用的源IP地址IP address#1不变，并利用anchor#2与anchor#1之间的隧道(英文：tunnel)为该已有网络会话的业务流提供连续性支持，保证该已有网络会话不受影响。
另外，MN判断与CN间的已有网络会话能否使用首选IP地址作为源IP地址，可通过多种方式来实现。
在一种可能的实施方式中，MN获取已有网络会话所对应的应用程序的配置信息，并根据该配置信息判断已有网络会话能否使用首选IP地址作为源IP地址。例如，应用程序开发者在开发应用程序时，通过设置socket option的方式进行明确设置。
在第二种可能的实施方式中，MN获取已有网络会话所对应的应用程序所使用的传输层协议，并根据该传输层协议判断已有网络会话能否使用首选IP地址作为源IP地址。再例如，由于MPTCP(英文：Multipath TCP)自身是能够处理IP地址的变化的，所以如果已有网络会话所使用的传输层协议是MPTCP，那么就让该已有网络会话使用首选IP地址作为源IP地址。
另外，若MN无法获知已有网络会话能否使用首选IP地址作为源IP地址，则MN保持该已有网络会话所使用的源IP地址不变。
综上所述，通过IP地址锚点在向MN提供当前可用的IP地址前缀时，通过类型标识将由该IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀区别标识，使得MN可基于类型标识将上述两种不同类型的IP地址前缀进行区分。
进一步地，MN通过为新网络会话和自身能够处理IP地址的变化的已有网络会话选择使用首选IP地址作为源IP地址，达到了减少路由冗余的技术效果。
可选地，当MN判定所接入的IP子网已发生变化时，MN可查询获取距离MN最近的CN的IP地址，并根据该IP地址与上述最近的CN间建立网络会话，从而达到进一步减少路由冗余的目的。
下述为本发明装置实施例，可以用于执行本发明方法实施例。对于本发明装置实施例中未披露的细节，请参照本发明方法实施例。
请参考图6，其示出了本发明一个实施例提供的IP地址管理装置的框图。该IP地址管理装置可应用于IP地址锚点中。该IP地址管理装置可以包括：地址获取模块610和信息发送模块620。
地址获取模块610，用于在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀。
信息发送模块620，用于根据所述有效IP地址前缀向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
综上所述，本实施例提供的IP地址管理装置，通过IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前缀向MN发送切换指示信息；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
请参考图7，其示出了本发明另一实施例提供的IP地址管理装置的框图。该IP地址管理装置可应用于IP地址锚点中。该IP地址管理装置可以包括：地址获取模块610和信息发送模块620。
地址获取模块610，用于在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀。
信息发送模块620，用于根据所述有效IP地址前缀向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在本实施例中，所述信息发送模块620，包括：地址判断子模块620a、前缀分配子模块620b、区别标识子模块620c和第一发送子模块620d。
地址判断子模块620a，用于判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀。
前缀分配子模块620b，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，为所述MN分配IP地址前缀。
区别标识子模块620c，用于将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识。
第一发送子模块620d，用于向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
综上所述，本实施例提供的IP地址管理装置，通过IP地址锚点在检测到MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前缀向MN发送切换指示信息；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
请参考图8，其示出了本发明另一实施例提供的IP地址管理装置的框图。该IP地址管理装置可应用于IP地址锚点中。该IP地址管理装置可以包括：地址获取模块610和信息发送模块620。
地址获取模块610，用于在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀。
信息发送模块620，用于根据所述有效IP地址前缀向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在本实施例中，所述信息发送模块620，包括：变化判定子模块620e和第二发送子模块620f。
变化判定子模块620e，用于根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化。
第二发送子模块620f，用于根据判定结果向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符。
其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
可选地，所述变化判定子模块620e，包括：地址判断子模块620e1、第一判定子模块620e2、标识判断子模块620e3和第二判定子模块620e4。
地址判断子模块620e1，用于判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀。
第一判定子模块620e2，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，判定所述MN所接入的IP子网已发生变化。
标识判断子模块620e3，用于当所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀时，判断由所述IP地址锚点分配的IP地址前缀是否对应有预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀。
第二判定子模块620e4，用于当由所述IP地址锚点分配的IP地址前缀对应有所述预定标识时，判定所述MN所接入的IP子网未发生变化。
所述第一判定子模块620e2，还用于当由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识时，判定所述MN所接入的IP子网已发生变化。
可选地，所述装置还包括：前缀分配子模块、区别标识子模块和消息发送子模块(图中未示出)。
前缀分配子模块，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，为所述MN分配IP地址前缀。
区别标识子模块，用于将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识。
消息发送子模块，用于向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
综上所述，本实施例提供的IP地址管理装置，通过IP地址锚点在检测到 MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前缀向MN发送切换指示信息；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
结合上述图7和图8所示实施例，在一种可能的实施方式中，区别标识子模块，具体用于：为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；和/或，为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
结合上述图7和图8所示实施例，在一种可能的实施方式中，如图9所示，地址判断子模块，包括：网络标识判断子模块91、第一确定子模块92和第二确定子模块93。
网络标识判断子模块91，用于判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号。
第一确定子模块92，用于当存在所述IP地址锚点对应的网络标识时，确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀。
第二确定子模块93，用于当不存在所述IP地址锚点对应的网络标识时，确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
可选地，所述地址获取模块，包括：请求获取子模块和地址接收子模块(图中未示出)。
请求获取子模块，用于向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识。
地址接收子模块，用于接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识。
可选地，所述装置还包括：请求存储子模块(图中未示出)。
请求存储子模块，用于向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除。
其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
可选地，所述装置还包括：地址检测子模块和指示发送子模块(图中未示出)。
地址检测子模块，用于检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀。
指示发送子模块，用于当所述有效IP地址前缀中存在所述目标IP地址前缀时，向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP地址前缀之间的对应关系的条目。
请参考图10，其示出了本发明另一实施例提供的IP地址管理装置的框图。该IP地址管理装置可应用于MN中。该IP地址管理装置可以包括：信息接收模块1010和变化判断模块1020。
信息接收模块1010，用于在接入IP地址锚点所在的IP子网后，接收所述IP地址锚点发送的切换指示信息。
变化判断模块1020，用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
综上所述，本实施例提供的IP地址管理装置，通过MN接收IP地址锚点发送的切换指示信息，并根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变 化的技术效果。
请参考图11，其示出了本发明另一实施例提供的IP地址管理装置的框图。该IP地址管理装置可应用于MN中。该IP地址管理装置可以包括：信息接收模块1010和变化判断模块1020。
信息接收模块1010，用于在接入IP地址锚点所在的IP子网后，接收所述IP地址锚点发送的切换指示信息。
变化判断模块1020，用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在本实施例中，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
相应地，所述变化判断模块1020，包括：条件判断子模块1020a、第三判定子模块1020b和第四判定子模块1020c。
条件判断子模块1020a，用于判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配。
第三判定子模块1020b，用于当由所述IP地址锚点分配的IP地址前缀满足所述预定条件时，判定所接入的IP子网已发生变化。
第四判定子模块1020c，用于当由所述IP地址锚点分配的IP地址前缀不满足所述预定条件时，判定所接入的IP子网未发生变化。
综上所述，本实施例提供的IP地址管理装置，通过MN接收IP地址锚点发送的切换指示信息，并根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
请参考图12，其示出了本发明另一实施例提供的IP地址管理装置的框图。 该IP地址管理装置可应用于MN中。该IP地址管理装置可以包括：信息接收模块1010和变化判断模块1020。
信息接收模块1010，用于在接入IP地址锚点所在的IP子网后，接收所述IP地址锚点发送的切换指示信息。
变化判断模块1020，用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
在本实施例中，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
所述变化判断模块1020，包括：第五判定子模块1020d和第六判定子模块1020e。
第五判定子模块1020d，用于当所述切换指示信息中包括所述第一指示符时，判定所接入的IP子网已发生变化。
第六判定子模块1020e，用于当所述切换指示信息中包括所述第二指示符时，判定所接入的IP子网未发生变化。
可选地，所述装置还包括：消息接收子模块(图中未示出)。
消息接收子模块，用于接收所述IP地址锚点发送的路由通告消息。
其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
综上所述，本实施例提供的IP地址管理装置，通过MN接收IP地址锚点发送的切换指示信息，并根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
结合上述图11和图12所示实施例，在一种可能的实施方式中，所述类型标识包括第一类型标识和/或第二类型标识。
所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置。
所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
结合上述图11和图12所示实施例，在一种可能的实施方式中，如图13所示，所述装置还包括：地址区分子模块131。
地址区分子模块131，用于根据所述类型标识，区分由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
可选地，所述装置还包括：第一选择子模块132。
第一选择子模块132，用于当所述MN需要向通信对端节点CN发起新网络会话时，为所述新网络会话选择使用首选IP地址作为源IP地址。
其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址。
可选地，所述装置还包括：会话判断子模块133、第二选择子模块134和第三选择子模块135。
会话判断子模块133，用于判断与通信对端节点CN间的已有网络会话能否使用首选IP地址作为源IP地址；其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址。
第二选择子模块134，用于当所述已有网络会话能够使用所述首选IP地址作为源IP地址时，为所述已有网络会话选择使用所述首选IP地址作为源IP地址。
第三选择子模块135，用于当所述已有网络会话无法使用所述首选IP地址作为源IP地址时，保持所述已有网络会话所使用的源IP地址不变。
可选地，所述会话判断子模块133，具体用于：
获取所述已有网络会话所对应的应用程序的配置信息，并根据所述配置信息判断所述已有网络会话能否使用所述首选IP地址作为源IP地址；
或者，
获取所述已有网络会话所对应的应用程序所使用的传输层协议，并根据所述传输层协议判断所述已有网络会话能否使用所述首选IP地址作为源IP地址。
结合上述图10、图11或者图12所示实施例，在一种可能的实施方式中，所述装置还包括：地址查询模块和会话建立模块(图中未示出)。
地址查询模块，用于当所述MN判定所接入的IP子网已发生变化时，查询获取距离所述MN最近的通信对端节点CN的IP地址。
会话建立模块，用于根据所述IP地址与所述最近的CN间建立网络会话。
需要说明的是，上述实施例提供的IP地址管理装置在进行IP地址管理时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的IP地址管理装置与IP地址管理方法的方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
请参考图14，其示出了本发明一个实施例提供的IP地址管理系统的框图。该IP地址管理系统包括IP地址锚点1410和MN1420。其中：
IP地址锚点1410可以包括如上述图6、图7或图8所示实施例提供的IP地址管理装置。
MN1420可以包括如上述图10、图11或图12所示实施例提供的IP地址管理装置。
请参考图15，其示出了本发明一个实施例提供的IP地址锚点的结构方框图。如图15所示，IP地址锚点1500包括：总线1510，以及通过总线1510通信的处理器1520、存储器1530和收发器1540。其中，存储器1530用于存储一个或者一个以上的指令，该指令被配置成由处理器1520执行。其中：
所述处理器1520，用于在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀。
所述处理器1520，还用于根据所述有效IP地址前缀，控制所述收发器1540向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
综上所述，本实施例提供的IP地址锚点，通过在检测到MN接入该IP地址锚点所在的IP子网时，根据MN正在使用的有效IP地址前缀向MN发送切换指示信息；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
在基于图15所示实施例提供的可选实施例中，所述处理器1520，具体用 于：
判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
控制所述收发器1540向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
在基于图15所示实施例提供的可选实施例中，所述处理器1520，具体用于：
根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化；
根据判定结果，控制所述收发器1540向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符；
其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
在基于图15所示实施例提供的可选实施例中，所述处理器1520，具体用于：
判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则判定所述MN所接入的IP子网已发生变化；
若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则判断由所述IP地址锚点分配的IP地址前缀是否对应有预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀；
若由所述IP地址锚点分配的IP地址前缀对应有所述预定标识，则判定所 述MN所接入的IP子网未发生变化；
若由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识，则判定所述MN所接入的IP子网已发生变化。
在基于图15所示实施例提供的可选实施例中，
所述处理器1520，还用于若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
所述处理器1520，还用于若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
所述处理器1520，还用于控制所述收发器1540向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
在基于图15所示实施例提供的可选实施例中，所述处理器1520，具体用于：
为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；
和/或，
为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
在基于图15所示实施例提供的可选实施例中，所述处理器1520，具体用于：
判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号；
若存在所述IP地址锚点对应的网络标识，则确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀；
若不存在所述IP地址锚点对应的网络标识，则确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
在基于图15所示实施例提供的可选实施例中，所述处理器1520，具体用于：
控制所述收发器1540向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识；
控制所述收发器1540接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识。
在基于图15所示实施例提供的可选实施例中，
所述处理器1520，还用于控制所述收发器1540向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除；
其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
在基于图15所示实施例提供的可选实施例中，
所述处理器1520，还用于检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀；
所述处理器1520，还用于若所述有效IP地址前缀中存在所述目标IP地址前缀，则控制所述收发器1540向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP地址前缀之间的对应关系的条目。
请参考图16，其示出了本发明一个实施例提供的MN的结构方框图。如图16所示，MN1600包括：总线1610，以及通过总线1610通信的处理器1620、 存储器1630和收发器1640。其中，存储器1630用于存储一个或者一个以上的指令，该指令被配置成由处理器1620执行。其中：
所述处理器1620，用于在接入IP地址锚点所在的IP子网后，控制所述收发器接1640收所述IP地址锚点发送的切换指示信息；
所述处理器1620，还用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
综上所述，本实施例提供的MN，通过接收IP地址锚点发送的切换指示信息，并根据该切换指示信息确定所接入的IP子网是否已发生变化；解决了现有技术存在的MN无法判断其所接入的IP子网是否已发生变化的问题；达到了使得MN能够准确判断其所接入的IP子网是否已发生变化的技术效果。
在基于图16所示实施例提供的可选实施例中，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀；
所述处理器1620，具体用于：
判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配；
若由所述IP地址锚点分配的IP地址前缀满足所述预定条件，则判定所接入的IP子网已发生变化；
若由所述IP地址锚点分配的IP地址前缀不满足所述预定条件，则判定所接入的IP子网未发生变化。
在基于图16所示实施例提供的可选实施例中，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化；
所述处理器1620，具体用于：
当所述切换指示信息中包括所述第一指示符时，判定所接入的IP子网已发生变化；
当所述切换指示信息中包括所述第二指示符时，判定所接入的IP子网未发生变化。
在基于图16所示实施例提供的可选实施例中，
所述处理器1620，还用于控制所述收发器1640接收所述IP地址锚点发送的路由通告消息；
其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
在基于图16所示实施例提供的可选实施例中，所述类型标识包括第一类型标识和/或第二类型标识；
所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置；
所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
在基于图16所示实施例提供的可选实施例中，
所述处理器1620，还用于根据所述类型标识，区分由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
在基于图16所示实施例提供的可选实施例中，
所述处理器1620，还用于当所述MN需要向通信对端节点CN发起新网络会话时，为所述新网络会话选择使用首选IP地址作为源IP地址；
其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址。
在基于图16所示实施例提供的可选实施例中，
所述处理器1620，还用于判断与通信对端节点CN间的已有网络会话能否使用首选IP地址作为源IP地址；其中，所述首选IP地址是指根据由所述IP地址锚点分配的IP地址前缀和所述MN的主机地址生成的IP地址；
所述处理器1620，还用于若所述已有网络会话能够使用所述首选IP地址作为源IP地址，则为所述已有网络会话选择使用所述首选IP地址作为源IP地址；
所述处理器1620，还用于若所述已有网络会话无法使用所述首选IP地址作为源IP地址，则保持所述已有网络会话所使用的源IP地址不变。
在基于图16所示实施例提供的可选实施例中，所述处理器1620，具体用 于：
获取所述已有网络会话所对应的应用程序的配置信息，并根据所述配置信息判断所述已有网络会话能否使用所述首选IP地址作为源IP地址；
或者，
获取所述已有网络会话所对应的应用程序所使用的传输层协议，并根据所述传输层协议判断所述已有网络会话能否使用所述首选IP地址作为源IP地址。
在基于图16所示实施例提供的可选实施例中，
所述处理器1620，还用于当所述MN判定所接入的IP子网已发生变化时，查询获取距离所述MN最近的通信对端节点CN的IP地址；
所述处理器1620，还用于根据所述IP地址与所述最近的CN间建立网络会话。
应当理解的是，在本文中使用的，除非上下文清楚地支持例外情况，单数形式“一个”(“a”、“an”、“the”)旨在也包括复数形式。还应当理解的是，在本文中使用的“和/或”是指包括一个或者一个以上相关联地列出的项目的任意和所有可能组合。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (48)

  1. 一种IP地址管理方法，其特征在于，所述方法包括：
    IP地址锚点在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀；
    所述IP地址锚点根据所述有效IP地址前缀向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
  2. 根据权利要求1所述的方法，其特征在于，所述IP地址锚点根据所述有效IP地址前缀向所述MN发送切换指示信息，包括：
    所述IP地址锚点判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
    若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    所述IP地址锚点向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  3. 根据权利要求1所述的方法，其特征在于，所述IP地址锚点根据所述有效IP地址前缀向所述MN发送切换指示信息，包括：
    所述IP地址锚点根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化；
    所述IP地址锚点根据判定结果向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符；
    其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所 述第二指示符用于指示所述MN所接入的IP子网未发生变化。
  4. 根据权利要求3所述的方法，其特征在于，所述IP地址锚点根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化，包括：
    所述IP地址锚点判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
    若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点判定所述MN所接入的IP子网已发生变化；
    若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点判断由所述IP地址锚点分配的IP地址前缀是否对应有预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀；
    若由所述IP地址锚点分配的IP地址前缀对应有所述预定标识，则所述IP地址锚点判定所述MN所接入的IP子网未发生变化；
    若由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识，则所述IP地址锚点判定所述MN所接入的IP子网已发生变化。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则所述IP地址锚点将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    所述IP地址锚点向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  6. 根据权利要求2或5所述的方法，其特征在于，所述IP地址锚点将由所 述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识，包括：
    所述IP地址锚点为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；
    和/或，
    所述IP地址锚点为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
  7. 根据权利要求2或4所述的方法，其特征在于，所述IP地址锚点判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀，包括：
    所述IP地址锚点判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号；
    若存在所述IP地址锚点对应的网络标识，则所述IP地址锚点确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀；
    若不存在所述IP地址锚点对应的网络标识，则所述IP地址锚点确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
  8. 根据权利要求7所述的方法，其特征在于，所述IP地址锚点获取所述MN正在使用的有效IP地址前缀，包括：
    所述IP地址锚点向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识；
    所述IP地址锚点接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；
    所述方法还包括：
    所述IP地址锚点向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点 分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除；
    其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述IP地址锚点检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀；
    若所述有效IP地址前缀中存在所述目标IP地址前缀，则所述IP地址锚点向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP地址前缀之间的对应关系的条目。
  10. 一种IP地址管理方法，其特征在于，所述方法包括：
    移动节点MN在接入IP地址锚点所在的IP子网后，接收所述IP地址锚点发送的切换指示信息；
    所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
  11. 根据权利要求10所述的方法，其特征在于，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀；
    所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化，包括：
    所述MN判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀 在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配；
    若由所述IP地址锚点分配的IP地址前缀满足所述预定条件，则所述MN判定所接入的IP子网已发生变化；
    若由所述IP地址锚点分配的IP地址前缀不满足所述预定条件，则所述MN判定所接入的IP子网未发生变化。
  12. 根据权利要求10所述的方法，其特征在于，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化；
    所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化，包括：
    当所述切换指示信息中包括所述第一指示符时，所述MN判定所接入的IP子网已发生变化；
    当所述切换指示信息中包括所述第二指示符时，所述MN判定所接入的IP子网未发生变化。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述MN接收所述IP地址锚点发送的路由通告消息；
    其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  14. 根据权利要求11或13所述的方法，其特征在于，所述类型标识包括第一类型标识和/或第二类型标识；
    所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置；
    所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
  15. 根据权利要求11或13所述的方法，其特征在于，所述方法还包括：
    所述MN根据所述类型标识，区分由所述IP地址锚点分配的IP地址前缀与 由其它IP地址锚点分配的IP地址前缀。
  16. 根据权利要求10至15任一所述的方法，其特征在于，所述方法还包括：
    当所述MN判定所接入的IP子网已发生变化时，所述MN查询获取距离所述MN最近的通信对端节点CN的IP地址；
    所述MN根据所述IP地址与所述最近的CN间建立网络会话。
  17. 一种IP地址管理装置，其特征在于，应用于IP地址锚点中，所述装置包括：
    地址获取模块，用于在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀；
    信息发送模块，用于根据所述有效IP地址前缀向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
  18. 根据权利要求17所述的装置，其特征在于，所述信息发送模块，包括：
    地址判断子模块，用于判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
    前缀分配子模块，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，为所述MN分配IP地址前缀；
    区别标识子模块，用于将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    第一发送子模块，用于向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  19. 根据权利要求17所述的装置，其特征在于，所述信息发送模块，包括：
    变化判定子模块，用于根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化；
    第二发送子模块，用于根据判定结果向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符；
    其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
  20. 根据权利要求19所述的装置，其特征在于，所述变化判定子模块，包括：
    地址判断子模块，用于判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
    第一判定子模块，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，判定所述MN所接入的IP子网已发生变化；
    标识判断子模块，用于当所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀时，判断由所述IP地址锚点分配的IP地址前缀是否对应有预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀；
    第二判定子模块，用于当由所述IP地址锚点分配的IP地址前缀对应有所述预定标识时，判定所述MN所接入的IP子网未发生变化；
    所述第一判定子模块，还用于当由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识时，判定所述MN所接入的IP子网已发生变化。
  21. 根据权利要求20所述的装置，其特征在于，所述装置还包括：
    前缀分配子模块，用于当所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀时，为所述MN分配IP地址前缀；
    区别标识子模块，用于将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    消息发送子模块，用于向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  22. 根据权利要求18或21所述的装置，其特征在于，所述区别标识子模 块，具体用于：
    为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；
    和/或，
    为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
  23. 根据权利要求18或20所述的装置，其特征在于，所述地址判断子模块，包括：
    网络标识判断子模块，用于判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号；
    第一确定子模块，用于当存在所述IP地址锚点对应的网络标识时，确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀；
    第二确定子模块，用于当不存在所述IP地址锚点对应的网络标识时，确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
  24. 根据权利要求23所述的装置，其特征在于，所述地址获取模块，包括：
    请求获取子模块，用于向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识；
    地址接收子模块，用于接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；
    所述装置还包括：
    请求存储子模块，用于向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP 地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除；
    其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
  25. 根据权利要求24所述的装置，其特征在于，所述装置还包括：
    地址检测子模块，用于检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀；
    指示发送子模块，用于当所述有效IP地址前缀中存在所述目标IP地址前缀时，向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP地址前缀之间的对应关系的条目。
  26. 一种IP地址管理装置，其特征在于，应用于移动节点MN中，所述装置包括：
    信息接收模块，用于在接入IP地址锚点所在的IP子网后，接收所述IP地址锚点发送的切换指示信息；
    变化判断模块，用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
  27. 根据权利要求26所述的装置，其特征在于，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀；
    所述变化判断模块，包括：
    条件判断子模块，用于判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配；
    第三判定子模块，用于当由所述IP地址锚点分配的IP地址前缀满足所述预定条件时，判定所接入的IP子网已发生变化；
    第四判定子模块，用于当由所述IP地址锚点分配的IP地址前缀不满足所述预定条件时，判定所接入的IP子网未发生变化。
  28. 根据权利要求26所述的装置，其特征在于，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化；
    所述变化判断模块，包括：
    第五判定子模块，用于当所述切换指示信息中包括所述第一指示符时，判定所接入的IP子网已发生变化；
    第六判定子模块，用于当所述切换指示信息中包括所述第二指示符时，判定所接入的IP子网未发生变化。
  29. 根据权利要求28所述的装置，其特征在于，所述装置还包括：
    消息接收子模块，用于接收所述IP地址锚点发送的路由通告消息；
    其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  30. 根据权利要求27或29所述的装置，其特征在于，所述类型标识包括第一类型标识和/或第二类型标识；
    所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置；
    所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
  31. 根据权利要求27或29所述的装置，其特征在于，所述装置还包括：
    地址区分子模块，用于根据所述类型标识，区分由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  32. 根据权利要求26至31任一所述的装置，其特征在于，所述装置还包 括：
    地址查询模块，用于当所述MN判定所接入的IP子网已发生变化时，查询获取距离所述MN最近的通信对端节点CN的IP地址；
    会话建立模块，用于根据所述IP地址与所述最近的CN间建立网络会话。
  33. 一种IP地址锚点，其特征在于，所述IP地址锚点包括：处理器、存储器和收发器，其中所述存储器用于存储一个或者一个以上的指令，所述指令被配置成由所述处理器执行；
    所述处理器，用于在检测到移动节点MN接入所述IP地址锚点所在的IP子网时，获取所述MN正在使用的有效IP地址前缀；
    所述处理器，还用于根据所述有效IP地址前缀，控制所述收发器向所述MN发送切换指示信息；以使得所述MN根据所述切换指示信息确定所接入的IP子网是否已发生变化。
  34. 根据权利要求33所述的IP地址锚点，其特征在于，所述处理器，具体用于：
    判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
    若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    控制所述收发器向所述MN发送所述切换指示信息，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  35. 根据权利要求33所述的IP地址锚点，其特征在于，所述处理器，具体用于：
    根据所述有效IP地址前缀判定所述MN所接入的IP子网是否已发生变化；
    根据判定结果，控制所述收发器向所述MN发送所述切换指示信息，所述切换指示信息包括第一指示符或者第二指示符；
    其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化。
  36. 根据权利要求35所述的IP地址锚点，其特征在于，所述处理器，具体用于：
    判断所述有效IP地址前缀中是否已有由所述IP地址锚点分配的IP地址前缀；
    若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则判定所述MN所接入的IP子网已发生变化；
    若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则判断由所述IP地址锚点分配的IP地址前缀是否对应有预定标识，所述预定标识对应于所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀；
    若由所述IP地址锚点分配的IP地址前缀对应有所述预定标识，则判定所述MN所接入的IP子网未发生变化；
    若由所述IP地址锚点分配的IP地址前缀未对应有所述预定标识，则判定所述MN所接入的IP子网已发生变化。
  37. 根据权利要求36所述的IP地址锚点，其特征在于，
    所述处理器，还用于若所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀，则为所述MN分配IP地址前缀，并将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    所述处理器，还用于若所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀，则将由所述IP地址锚点分配的IP地址前缀与所述有效IP地址前缀中由其它IP地址锚点分配的IP地址前缀区别标识；
    所述处理器，还用于控制所述收发器向所述MN发送路由通告消息，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚 点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  38. 根据权利要求34或37所述的IP地址锚点，其特征在于，所述处理器，具体用于：
    为由所述IP地址锚点分配的IP地址前缀对应设置第一类型标识；
    和/或，
    为由其它IP地址锚点分配的IP地址前缀对应设置第二类型标识。
  39. 根据权利要求34或36所述的IP地址锚点，其特征在于，所述处理器，具体用于：
    判断各个所述有效IP地址前缀分别对应的网络标识中，是否存在所述IP地址锚点对应的网络标识；其中，所述网络标识为锚点标识或者网络号；
    若存在所述IP地址锚点对应的网络标识，则确定所述有效IP地址前缀中已有由所述IP地址锚点分配的IP地址前缀；
    若不存在所述IP地址锚点对应的网络标识，则确定所述有效IP地址前缀中没有由所述IP地址锚点分配的IP地址前缀。
  40. 根据权利要求39所述的IP地址锚点，其特征在于，所述处理器，具体用于：
    控制所述收发器向位置管理器LM发送携带有所述MN的节点标识的信息获取请求；以使得所述LM根据所述MN的节点标识，从预存的条目中查找获取所述MN正在使用的有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；其中，每个条目包括节点标识、网络标识、IP地址前缀以及IP地址前缀的有效期之间的对应关系，所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀还对应有预定标识；
    控制所述收发器接收所述LM反馈的所述有效IP地址前缀以及各个所述有效IP地址前缀分别对应的网络标识；
    所述处理器，还用于控制所述收发器向所述LM发送信息存储请求，所述信息存储请求中携带有所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前 缀的有效期；以使得所述LM根据所述信息存储请求存储目标条目，并在所述目标条目中对应设置所述预定标识，而将所述预定标识从记录有所述MN在接入所述IP地址锚点所在的IP子网之前所接入的IP子网为所述MN分配的IP地址前缀的条目中移除；
    其中，所述目标条目包括：所述MN的节点标识、所述IP地址锚点对应的网络标识、由所述IP地址锚点分配的IP地址前缀以及由所述IP地址锚点分配的IP地址前缀的有效期之间的对应关系。
  41. 根据权利要求40所述的IP地址锚点，其特征在于，
    所述处理器，还用于检测所述有效IP地址前缀中是否存在目标IP地址前缀，所述目标IP地址前缀是指超过预定时长未被网络会话使用的IP地址前缀；
    所述处理器，还用于若所述有效IP地址前缀中存在所述目标IP地址前缀，则控制所述收发器向所述LM发送携带有所述MN的节点标识和所述目标IP地址前缀的条目删除指示，以使得所述LM删除记录有所述MN的节点标识和所述目标IP地址前缀之间的对应关系的条目。
  42. 一种移动节点MN，其特征在于，所述MN包括：处理器、存储器和收发器，其中所述存储器用于存储一个或者一个以上的指令，所述指令被配置成由所述处理器执行；
    所述处理器，用于在接入IP地址锚点所在的IP子网后，控制所述收发器接收所述IP地址锚点发送的切换指示信息；
    所述处理器，还用于根据所述切换指示信息确定所接入的IP子网是否已发生变化。
  43. 根据权利要求42所述的MN，其特征在于，所述切换指示信息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀；
    所述处理器，具体用于：
    判断由所述IP地址锚点分配的IP地址前缀是否满足预定条件；其中，所述预定条件是指：由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条 切换指示信息中不存在，或者，由所述IP地址锚点分配的IP地址前缀在所述MN接收的上一条切换指示信息中存在且被标识为由其它IP地址锚点分配；
    若由所述IP地址锚点分配的IP地址前缀满足所述预定条件，则判定所接入的IP子网已发生变化；
    若由所述IP地址锚点分配的IP地址前缀不满足所述预定条件，则判定所接入的IP子网未发生变化。
  44. 根据权利要求42所述的MN，其特征在于，所述切换指示信息包括第一指示符或者第二指示符；其中，所述第一指示符用于指示所述MN所接入的IP子网已发生变化，所述第二指示符用于指示所述MN所接入的IP子网未发生变化；
    所述处理器，具体用于：
    当所述切换指示信息中包括所述第一指示符时，判定所接入的IP子网已发生变化；
    当所述切换指示信息中包括所述第二指示符时，判定所接入的IP子网未发生变化。
  45. 根据权利要求44所述的MN，其特征在于，
    所述处理器，还用于控制所述收发器接收所述IP地址锚点发送的路由通告消息；
    其中，所述路由通告消息包括：由所述IP地址锚点分配的IP地址前缀、由其它IP地址锚点分配的IP地址前缀以及类型标识，所述类型标识用于区别标识由所述IP地址锚点分配的IP地址前缀与由其它IP地址锚点分配的IP地址前缀。
  46. 根据权利要求43或45所述的MN，其特征在于，所述类型标识包括第一类型标识和/或第二类型标识；
    所述第一类型标识与由所述IP地址锚点分配的IP地址前缀对应设置；
    所述第二类型标识与由其它IP地址锚点分配的IP地址前缀对应设置。
  47. 根据权利要求43或45所述的MN，其特征在于，
    所述处理器，还用于根据所述类型标识，区分由所述IP地址锚点分配的IP 地址前缀与由其它IP地址锚点分配的IP地址前缀。
  48. 根据权利要求42至47任一所述的装置，其特征在于，
    所述处理器，还用于当所述MN判定所接入的IP子网已发生变化时，查询获取距离所述MN最近的通信对端节点CN的IP地址；
    所述处理器，还用于根据所述IP地址与所述最近的CN间建立网络会话。
PCT/CN2015/084149 2015-07-15 2015-07-15 Ip地址管理方法、装置、ip地址锚点及移动节点 WO2017008288A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
SG11201800098WA SG11201800098WA (en) 2015-07-15 2015-07-15 Ip address management method and apparatus, ip address anchor, and mobile node
JP2018501168A JP6592584B2 (ja) 2015-07-15 2015-07-15 Ｉｐアドレス管理方法及び装置、ｉｐアドレスアンカー、並びにモバイルノード
EP15898016.9A EP3310099B1 (en) 2015-07-15 2015-07-15 Ip address management method, device, ip address anchor and mobile node
CN201580079413.6A CN107534919B (zh) 2015-07-15 2015-07-15 Ip地址管理方法、装置、ip地址锚点及移动节点
PCT/CN2015/084149 WO2017008288A1 (zh) 2015-07-15 2015-07-15 Ip地址管理方法、装置、ip地址锚点及移动节点
ZA2018/00200A ZA201800200B (en) 2015-07-15 2018-01-10 Ip address management method and apparatus,ip address anchor,and mobile node
US15/870,171 US10728828B2 (en) 2015-07-15 2018-01-12 IP address management method and apparatus, IP address anchor, and mobile node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/084149 WO2017008288A1 (zh) 2015-07-15 2015-07-15 Ip地址管理方法、装置、ip地址锚点及移动节点

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/870,171 Continuation US10728828B2 (en) 2015-07-15 2018-01-12 IP address management method and apparatus, IP address anchor, and mobile node

Publications (1)

Publication Number Publication Date
WO2017008288A1 true WO2017008288A1 (zh) 2017-01-19

Family

ID=57756741

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/084149 WO2017008288A1 (zh) 2015-07-15 2015-07-15 Ip地址管理方法、装置、ip地址锚点及移动节点

Country Status (7)

Country Link
US (1) US10728828B2 (zh)
EP (1) EP3310099B1 (zh)
JP (1) JP6592584B2 (zh)
CN (1) CN107534919B (zh)
SG (1) SG11201800098WA (zh)
WO (1) WO2017008288A1 (zh)
ZA (1) ZA201800200B (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11115330B2 (en) * 2018-03-14 2021-09-07 Juniper Networks, Inc. Assisted replication with multi-homing and local bias
FR3080967A1 (fr) * 2018-05-02 2019-11-08 Orange Procede d'envoi d'une information et de reception d'une information pour la gestion de reputation d'une ressource ip
US11456987B1 (en) 2021-05-07 2022-09-27 State Farm Mutual Automobile Insurance Company Systems and methods for automatic internet protocol address management

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101213790A (zh) * 2005-06-28 2008-07-02 三星电子株式会社 执行快速切换的装置和方法
CN102625987A (zh) * 2009-08-28 2012-08-01 瑞典爱立信有限公司 网络前缀选择
CN103974226A (zh) * 2013-01-25 2014-08-06 中兴通讯股份有限公司 一种异构网络中的分布式位置管理方法及系统
WO2015009735A1 (en) * 2013-07-15 2015-01-22 Qualcomm Incorporated System and method to assign an internet protocol address to a mobile device during a handoff

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2005241850B2 (en) * 2004-05-10 2009-03-19 Lg Electronics Inc. Minimized IP connectivity establishment procedures
US7676838B2 (en) * 2004-07-26 2010-03-09 Alcatel Lucent Secure communication methods and systems
JP2006237815A (ja) * 2005-02-23 2006-09-07 Kddi Corp 通信セッション切替方法およびシステム
US8191106B2 (en) * 2007-06-07 2012-05-29 Alcatel Lucent System and method of network access security policy management for multimodal device
CN101765092B (zh) * 2008-12-24 2011-07-20 华为技术有限公司 一种网络切换方法、装置及系统
TW201703490A (zh) * 2011-11-29 2017-01-16 內數位專利控股公司 Ｉｐ姨動性管理方法、裝置及系統

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101213790A (zh) * 2005-06-28 2008-07-02 三星电子株式会社 执行快速切换的装置和方法
CN102625987A (zh) * 2009-08-28 2012-08-01 瑞典爱立信有限公司 网络前缀选择
CN103974226A (zh) * 2013-01-25 2014-08-06 中兴通讯股份有限公司 一种异构网络中的分布式位置管理方法及系统
WO2015009735A1 (en) * 2013-07-15 2015-01-22 Qualcomm Incorporated System and method to assign an internet protocol address to a mobile device during a handoff

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3310099A4 *

Also Published As

Publication number Publication date
EP3310099B1 (en) 2020-02-26
US20180139685A1 (en) 2018-05-17
SG11201800098WA (en) 2018-02-27
ZA201800200B (en) 2019-09-25
CN107534919A (zh) 2018-01-02
JP6592584B2 (ja) 2019-10-16
JP2018526872A (ja) 2018-09-13
CN107534919B (zh) 2020-01-17
EP3310099A1 (en) 2018-04-18
US10728828B2 (en) 2020-07-28
EP3310099A4 (en) 2018-06-20

Similar Documents

Publication Publication Date Title
CN113115480B (zh) 地址信息发送方法、获取方法、装置、设备及介质
US11381961B2 (en) Method, apparatus, network device, and system for releasing IP address
JP6564934B2 (ja) 分散型ソフトウェア定義ネットワークパケットコアシステムにおけるモビリティ管理のためのシステムおよび方法
CN106790732B (zh) 地址转换方法、装置及系统、网络标识控制方法及装置
EP3209043B1 (en) Mobility management method, apparatus, and system
JP2021504991A (ja) アプリケーションのためのトラフィックをハンドリングするための方法および機能
EP3528447B1 (en) Communication method and apparatus
US10945180B2 (en) Mobility management method, apparatus, and system
WO2021036927A1 (zh) 域名地址获取的方法和设备
US10924518B2 (en) UPF programming over enhanced N9 interface
CN109314909B (zh) 一种锚点网关的切换方法、装置及系统
WO2019085728A1 (zh) 通信方法及装置
JP7467669B2 (ja) 接続確立方法、通信装置、およびシステム
EP3754949A1 (en) Method for acquiring and providing service, and user equipment and management server
WO2017008288A1 (zh) Ip地址管理方法、装置、ip地址锚点及移动节点
US12107927B2 (en) Apparatus, method, and computer program
WO2019157953A1 (zh) 一种位置更新的方法、装置和系统
JP2018102005A (ja) 通信システム
WO2017113047A1 (zh) 一种pdn连接的释放方法、装置及用户设备
KR101967379B1 (ko) Sdn 컨트롤러의 모바일 노드 관리 방법 및 장치
US8473625B1 (en) Preservation of network address translation (NAT) state across wireless sessions
JP2016034116A (ja) 経路設定装置、経路設定方法、経路設定プログラムおよび通信システム
US11039501B2 (en) Converged controller selection method, device, and converged controller selection system
KR101235357B1 (ko) 채널 할당 방법 및 장치
US20220141134A1 (en) Multi-access edge computing device and network access control method

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: 15898016

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 11201800098W

Country of ref document: SG

WWE Wipo information: entry into national phase

Ref document number: 2015898016

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2018501168

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE