WO2012097663A1 - Procédé et système pour la prise en charge par le protocole pmipv6 de la distribution de préfixes ipv6 - Google Patents

Procédé et système pour la prise en charge par le protocole pmipv6 de la distribution de préfixes ipv6 Download PDF

Info

Publication number
WO2012097663A1
WO2012097663A1 PCT/CN2011/084640 CN2011084640W WO2012097663A1 WO 2012097663 A1 WO2012097663 A1 WO 2012097663A1 CN 2011084640 W CN2011084640 W CN 2011084640W WO 2012097663 A1 WO2012097663 A1 WO 2012097663A1
Authority
WO
WIPO (PCT)
Prior art keywords
dhcpv6
prefix
mag
lma
message
Prior art date
Application number
PCT/CN2011/084640
Other languages
English (en)
Chinese (zh)
Inventor
周星月
朱春晖
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012097663A1 publication Critical patent/WO2012097663A1/fr

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and system for supporting IPv6 prefix allocation by Proxy Mobile Internet Protocol version 6 (IPv6).
  • IPv6 Proxy Mobile Internet Protocol version 6
  • Proxy Mobile IPv6 is a network-based mobile IP management protocol. ⁇ does not require mobile devices to participate in any mobility management tasks. The network is responsible for user equipment mobility management, and the mobile devices themselves are not aware of mobile mobility. The impact of the three-tier connection. For a Mobility Node (MN), the MN considers itself to be Home Link, no matter where it moves. As shown in Figure 1, 3GPP is based on the ⁇ network architecture and corresponding interfaces. The key nodes and functions of ⁇ 6 are as follows:
  • LMA Local Mobility Anchor
  • PDN GW Packet Data Network Gateway
  • MAG Mobile Access Gateway Blocks the network layer changes brought by mobile switching, and the proxy MN completes the binding update.
  • the corresponding network element service gateway Serving GW (S5/8) the trusted non-3GPP IP access network Trusted Non-3GPP IP Access (S2a), and the evolved packet data gateway ePDG (S2b) provide MAG functions.
  • Proxy Binding Update PBU
  • Proxy Binding Acknowledgement PBA
  • the PBU is sent by the MAG to the LMA
  • the PBA is sent by the LMA to the MAG.
  • the two messages appear as message pairs.
  • the MAG passes its own proxy address and user equipment MN through the PBU.
  • the home address binding relationship is sent to the LMA, and the LMA saves the corresponding relationship to correctly forward the uplink and downlink packets of the MN.
  • the PBU is mainly used for binding update, binding cycle update, and unbinding.
  • the corresponding LMA confirms the PBU request by sending a PBA message to the MAG.
  • the Dynamic Host Configuration Protocol provides an automatic configuration mechanism for IP parameters.
  • the host can automatically configure IP parameters such as IP address, DNS server address, and default gateway address for hosts on the network through the DHCP protocol.
  • the DHCP operating mode is a client-server (CS) mode. That is, the network host runs the DHCP client module, and the DHCP server module is deployed in the corresponding network.
  • DHCP also supports the DHCP Relay relay mode, which is used to forward user DHCP messages to the DHCP server. The host does not distinguish between the DHCP Relay Agent and the DHCP Server.
  • the DHCP message request object is the DHCP Server.
  • the S2a interface defines a connection to an Evolved Packet Core (EPC) through a trusted non-3GPP IP access network.
  • EPC Evolved Packet Core
  • S2a is based on the PMIPv6 mobility management protocol.
  • the non-3GPP IP access network supports the DHCP server function.
  • the user equipment can request IP from the DHCPv4v6 server (non-3GPP IP access network) through DHCPv4/v6 (DHCP protocol supporting IPv4 and DHCP protocol supporting IPv6). Parameters, such as DNSv4/v6 server address.
  • the 3GPP has introduced the prefix delegation function to support the allocation of IPv6 prefixes with a prefix length of less than 64 to the MN through DHCPv6. This enables the MN with the Router function to implement subnetting management and support for the subnets behind it. Stateless IPv6 address allocation (can also be DHCP).
  • the current standard has explained how to support refix delegation on GTP-based S5/8 and DSMIP-based S2c. How 3GPP supports PMIP-based S5/8, S2a and S2b support prefix delegation is currently a blank state, that is, ⁇ supports refix delegation. There is currently no public solution. There may be a problem: The mobile terminal can obtain the IPv6 prefix from the delegating router through DHCPv6. DHCPv6 runs on the user plane for PMIPv6. The network nodes MAG and LMA can be said to be transparent.
  • the terminal After the terminal obtains an additional IPv6 prefix on the current IP connection (different from the home network prefix of PMIPv6), the terminal uses the IPv6 address that belongs to the prefix to communicate, and the MAG and the LMA do not perceive the IPv6 prefix at this time, that is, the MAG. There is no corresponding prefix information in the local forwarding table of the LMA. This may cause the packet to be forwarded with the delegated prefix to fail. For example, when the MAG receives the 4 ⁇ message from the MN with the delegated prefix as the source address.
  • the packet may be discarded because the corresponding binding association is not found; or when the MAG does not have the source address and the home network prefix (Home Network Prefix) for the uplink packet, the LMA ⁇ is from the response node ( Node) The packet sent by the peer communication node to the MN. When the destination address of the packet contains the delegated prefix, the LMA may discard the packet because the corresponding binding association cannot be found.
  • the main purpose of the present invention is to provide a method and system for supporting IPv6 prefix allocation by the PMIPv6 protocol, which is used to solve the technical problem of how PMIPv6 supports IPv6 prefix allocation.
  • a proxy mobile internet protocol version 6 ( ⁇ ) protocol supports IPv6 prefix allocation, and the method includes:
  • the DHCPv6 prefix delegation process triggers the mobile access gateway (MAG) to perform the delegation prefix and the PMIPv6 binding update list.
  • MAG mobile access gateway
  • LMA local mobility anchor
  • the association between the proxy prefix and the PMIPv6 binding update list entry and the PMIPv6 binding cache entry triggered by the DHCPv6 prefix delegation process is:
  • the MAG acts as a DHCPv6 relay agent to transfer DHCPv6 messages between the MN and the DHCPv6 server.
  • the DHCPv6 message is forwarded to the DHCPv6 server through the LMA, and the DHCPv6 message is transmitted as the PMIPv6 user plane data to the DHCPv6 server through the PMIP tunnel.
  • LMA can identify DHCPv6 messages;
  • the MAG and the LMA associate the delegation prefix delivered by the DHCPv6 process with the local PMIPv6 binding update list entry and the local PMIPv6 binding cache entry.
  • DHCPv6 prefix delegation process is specifically:
  • the MN is connected to the network, and a PMIP tunnel is established between the MAG and the LMA;
  • the MN sends a DHCPv6 Solicit request to the MAG.
  • the request contains one or more associated prefixes.
  • the MAG encapsulates the DHCPv6 request message in the PMIP tunnel and sends it to the LMA.
  • the LMA decapsulates the packet and sends it to the DHCPv6 server.
  • the DHCPv6 server After receiving the DHCPv6 Solicit request, the DHCPv6 server sends the IPv6 prefix information to the MAG through the DHCPv6 Advertize advertisement. After receiving the advertisement, the LMA encapsulates the message in the PMIP tunnel and sends it to the MAG. The MAG decapsulates the message and processes it accordingly. After being sent to the MN;
  • the MN sends a DHCPv6 Request to the MAG, and the request message includes the IPv6 prefix information sent by the advertisement message.
  • the MAG processes the message and encapsulates it in the PMIP tunnel and sends it to the LMA.
  • the LMA decapsulates the message and sends it to the DHCPv6 server.
  • the DHCPv6 server After receiving the DHCPv6 Request, the DHCPv6 server sends a DHCPv6 Reply message to the MAG. After receiving the response, the LMA encapsulates the message in the PMIP tunnel and sends it to the MAG. The MAG decapsulates the message and sends it to the MN.
  • the association between the proxy prefix and the PMIPv6 binding update list entry and the PMIPv6 binding cache entry triggered by the DHCPv6 prefix delegation process is:
  • the MAG acts as a relay proxy node of the DHCPv6 or acts as a DHCPv6 server, and the DHCPv6 message is transparently transmitted through the LMA or not through the LMA;
  • the MAG triggers the PMIPv6 signaling interaction with the LMA when the DHCPv6 prefix delegation process is completed, and notifies the LMA of the delegation prefix information, so that the LMA updates the local PMIPv6 binding cache entry, and associates the delegation prefix with the PMIPv6 binding cache entry.
  • the MAG also performs association between the delegation prefix and the PMIPv6 binding update list entry.
  • the MAG triggers the ⁇ signaling interaction with the LMA when the DHCPv6 prefix delegation process is completed, and the steps of implementing the association between the delegation prefix and the ⁇ binding update list entry and the ⁇ 6 binding cache entry are:
  • the MAG After receiving the DHCPv6 Reply message from the DHCPv6 server, the MAG sends a proxy binding update PBU message to the LMA.
  • the PBU message contains the proxy prefix information and the PMIPv6 binding cache entry to be associated with the DHCPv6 prefix delegation process.
  • the LMA After receiving the PBU message, the LMA sends a proxy binding confirmation PBA message to the MAG, and associates the delivered proxy prefix information with the PMIPv6 binding cache entry.
  • the MAG After receiving the PBA message, the MAG updates the local PMIPv6 binding update list entry, and associates the delegation prefix with the PMIPv6 binding update list entry.
  • the MAG triggers the PMIPv6 signaling interaction with the LMA when the DHCPv6 prefix delegation process is completed, and implements the delegation prefix and the PMIPv6 binding update list entry and the ⁇ binding cache entry.
  • the associated steps are specifically as follows:
  • the MAG sends a PBU message to the LMA before sending the DHCPv6 Reply message to the MN.
  • the PBU message includes the delegation prefix information sent in the DHCPv6 prefix delegation process and the ⁇ binding cache entry information to be associated.
  • the LMA After receiving the PBU message, the LMA sends a PBA message to the MAG and sends the PBA message.
  • the present invention further provides a system for supporting IPv6 prefix allocation by using a proxy mobile IPv6 protocol, which includes a MN, a MAG, an LMA, a DHCP server, and a method for supporting an IPv6 prefix allocation according to the present invention.
  • a proxy mobile IPv6 protocol which includes a MN, a MAG, an LMA, a DHCP server, and a method for supporting an IPv6 prefix allocation according to the present invention.
  • the MN is configured to obtain an IPv6 prefix by using a DHCPv6 prefix delegation process
  • the MAG is configured to perform an association between a delegation prefix and a ⁇ binding update list entry triggered by a DHCPv6 prefix delegation process;
  • the LMA is used to associate the delegation prefix with the ⁇ binding cache entry triggered by the DHCPv6 prefix delegation process.
  • the MAG is further configured to transfer a DHCPv6 message between the MN and the DHCPv6 server as a DHCPv6 relay agent, where the LMA is further used to forward a DHCPv6 message between the MAG and the DHCPv6 server, and the DHCPv6 message is used as the PMIPv6 user plane data. Transferred to the DHCPv6 server via the PMIP tunnel;
  • the MAG and the LMA After the MAG and the LMA complete the DHCPv6 prefix entrusting process, the MAG and the LMA associate the proxy prefix delivered by the DHCPv6 process with the local PMIPv6 binding update list entry and the local PMIPv6 binding cache entry.
  • the MAG is further used as a DHCPv6 relay agent to transfer a DHCPv6 message between the MN and the DHCPv6 server, and the DHCPv6 message is transparently transmitted through the LMA or not through the LMA;
  • the MAG is further configured to trigger a ⁇ signaling interaction with the LMA when the DHCPv6 prefix delegation process is completed, and notify the LMA of the delegation prefix information, so that the LMA updates the local ⁇ binding cache entry, and binds the delegation prefix and ⁇ 6.
  • the MAG updates the local PMIPv6 binding update list entry after receiving the PBA message.
  • the suffix is associated with the PMIPv6 binding update list entry.
  • the DHCPv6 prefix delegation process triggers the association between the mobile access gateway MAG and the local mobility anchor LMA to perform the delegation prefix and the PMIPv6 binding cache entry.
  • the invention can avoid the situation that the MAG and/or the LMA does not perceive the IPv6 prefix change, causing the packet to be forwarded to contain the proxy prefix to fail, and the PMIPv6 protocol supports the IPv6 prefix allocation.
  • Figure 1 is a 3GPP based PMIPv6 network architecture and corresponding interface
  • Embodiment 2 is a schematic flow chart of Embodiment 1;
  • Embodiment 3 is a schematic flow chart of Embodiment 2;
  • Fig. 4 is a flow chart showing the third embodiment. detailed description
  • the invention is further explained below by means of three examples.
  • the embodiment 1 and the embodiment 2 are in the scenario that the DHCPv6 relay function is running on the MAG.
  • the third embodiment is a scenario in which the DHCPv6 server (the Delegating Router) is running on the MAG.
  • the mobile node MN is connected to the network.
  • the MAG also acts as a DHCPv6 relay agent to transfer DHCPv6 messages between the MN and the DHCPv6 Server. It is assumed that the DHCPv6 message needs to be forwarded to the DHCPv6 server through the LMA, that is, the DHCPv6 Server is in the LMA. Later (or with LMA), the DHCPv6 message is transmitted as PMIPv6 user plane data to the DHCPv6 Server via the PMIP tunnel.
  • the specific implementation steps are as follows:
  • Step 201 The MN is connected to the network, and the network adopts PMIPv6 as the mobility management association of the MN.
  • a PMIP tunnel is established between the MAG and the LMA to complete a PMIPv6-based IP connection between the MN and the network;
  • Step 202 The MN sends a DHCPv6 Solicit request to the DHCPv6 Relay agent, where the request message includes one or more IA_PD option(s) (the association identifier of the delegation prefix) is used to carry the IPv6 prefix information to be requested, and the DHCPv6 Relay (MAG) receives
  • the request message is processed according to the DHCPv6 relay agent function defined in RFC3315, the DHCPv6 request message is encapsulated in the PMIP tunnel and transmitted to the LMA, and the LMA is decapsulated and sent to the DHCPv6 Server (Delegating Router);
  • Step 203 The DHCPv6 Server (Delegating Router) receives the request message, and after the verification, the IA_PD option(s) containing the delivered IPv6 prefix information in the DHCPv6 Advertize advertisement message is sent to the DHCPv6 Relay agent, and the LMA will receive the notification message after receiving the notification message.
  • the message is encapsulated in the PMIP tunnel and sent to the DHCPv6 Relay Agent (MAG).
  • MAG DHCPv6 Relay Agent
  • Step 204 The MN sends a DHCPv6 Request request message to the DHCPv6 Relay agent, which is sent to the MAG from the IA_PD option(s) of the copy in the Advertize message.
  • the MAG processes the message and encapsulates it in the PMIP tunnel, and the LMA decapsulates the message and sends the message.
  • Step 205 The DHCPv6 Server (Delegating Router) receives the Request message, and sends a DHCPv6 Reply message to the DHCPv6 Relay agent after the verification.
  • the LMA encapsulates the message in the PMIP tunnel and sends it to the DHCPv6 Relay Agent (MAG).
  • MAG DHCPv6 Relay Agent
  • Step 206 Since both the MAG and the LMA participate in the DHCPv6 prefix Delegation process, both the MAG and the LMA can be aware of the completion of the DHCPv6 prefix Delegation process, and the corresponding MN can successfully receive the IPv6 packet of the Delegated Prefix.
  • the message is transmitted in the current PMIP tunnel, and the MAG and LMA will automatically update the local PMIPv6. Bind the cache list to the local PMIPv6 binding.
  • the MAG associates the delegate prefix delivered by the DHCPv6 process with the local PMIPv6 binding update list entry (BLE).
  • BLE local PMIPv6 binding update list entry
  • the LMA associates the delegate prefix delivered by the DHCPv6 process with the local PMIPv6 binding. In the cache entry, the PMIP tunnel of the DHCPv6 message transmission is a one-to-one relationship.
  • MN may also be included in the first DHCPv6 Solicit message
  • the RAPID_COMMIT option triggers the fast DHCPv6 process.
  • the Delegating Router directly replies to the DHCPv6 Reply message, which contains the IPv6 prefix delegation prefix information. The same is true for the following Examples 2 and 3.
  • Example 2
  • the mobile node MN is connected to the network.
  • the MAG also acts as a DHCPv6 Relay agent to transfer DHCPv6 messages between the MN and the DHCPv6 Server.
  • the DHCPv6 Server location is not restricted. It may be in any location.
  • the DHCPv6 Server may be in the LMA. Behind (or with LMA), it may also be in the local network, the latter LMA can not perceive the DHCPv6 process, that is, the DHCPv6 message will not pass the LMA.
  • the MAG triggers the PMIP signaling interaction process to notify the LMA delegated prefix.
  • the specific implementation steps are as follows:
  • Step 301 The MN is connected to the network, the network adopts PMIP as the mobility management protocol of the MN, and the PMIP tunnel is established between the MAG and the LMA to complete the PMIP-based IP connection between the MN and the network;
  • Step 302 The MN sends a DHCPv6 Solicit request to the DHCPv6 Relay agent, where the request message includes one or more IA_PD option(s) (the association identifier of the delegation prefix) carries the IPv6 prefix information to be requested, and the DHCPv6 Relay (MAG) receives the request message.
  • the DHCPv6 request message is sent to the Delegating Router.
  • Step 303 The DHCPv6 Server (Delegating Router) receives the request message, and includes the IA_PD of the delivered IPv6 prefix information in the DHCPv6 Advertize advertisement message after the verification.
  • the option(s) is sent to the DHCPv6 relay agent, and the MAG processes the message and sends it to the MN.
  • Step 304 The MN sends a DHCPv6 Request request message to the DHCPv6 Relay agent, and sends the IA_PD option(s) from the copy in the Advertize message to the MAG.
  • the MAG processes the message and sends the message to the Delegating Router.
  • Step 305 The DHCPv6 Server (Delegating Router) receives the Request message, and sends a DHCPv6 Reply (MAG) response message to the DHCPv6 Relay agent after the verification;
  • Step 306 the MAG receives the DHCPv6 message sent by the MN (Solicit or Request message) ), the MAG sends a proxy binding update PBU message request to the LMA to associate a DHCPv6 delegated Prefix;
  • Step 307 After receiving the PBU message, the LMA sends a proxy binding confirmation PBA message to the MAG to confirm. If the DHCPv6 server is combined with the LMA, the LMA directly updates the local PMIPv6 binding cache entry, and the delegated prefix (es) ) is associated with the PMIPv6 binding cache entry. Otherwise, the LMA requests the DHCPv6 Server to allocate the delegated prefix in the DHCPv6 process.
  • Step 308 The MAG receives the PBA message, forwards the DHCPv6 Reply message to the MN, updates the local PMIPv6 binding update list entry, and associates the delegate prefix delegated prefix(es) with the ⁇ binding update list entry.
  • Example 3 The MAG receives the PBA message, forwards the DHCPv6 Reply message to the MN, updates the local PMIPv6 binding update list entry, and associates the delegate prefix delegated prefix(es) with the ⁇ binding update list entry.
  • the mobile node is connected to the network, and the MAG is also used as the DHCPv6 server to deliver the delegated prefix to the MN.
  • the specific implementation steps are as follows:
  • Step 401 The MN is connected to the network, the network adopts PMIP as the mobility management protocol of the MN, and the PMIP tunnel is established between the MAG and the LMA to complete the PMIP-based IP connection between the MN and the network;
  • Step 402 the MN sends a DHCPv6 Solicit request to the Delegating Router, requesting to cancel
  • the information includes one or more IA_PD option(s) (the association identifier of the delegation prefix) carrying the IPv6 prefix information to be requested;
  • Step 403 The DHCPv6 Server (Delegating Router) receives the request message, and sends the IA_PD option(s) containing the delivered IPv6 prefix information to the MN in the DHCPv6 Advertize Advertisement message.
  • the DHCPv6 Server (Delegating Router) receives the request message, and sends the IA_PD option(s) containing the delivered IPv6 prefix information to the MN in the DHCPv6 Advertize Advertisement message.
  • Step 404 The MN sends a DHCPv6 Request request message to the DHCPv6 Relay agent, and sends the IB_option(s) from the copy in the Advertize message to the Delegating Router.
  • Step 405 The Delegating Router (MAG) sends a PBU message to the LMA before sending the Reply message.
  • the message includes the entrusted IPv6 prefix information (corresponding to the IA_PD option(s) information in the Reply message) and the ⁇ binding cache entry information to be associated in the DHCPv6 prefix delegation process;
  • Step 406 After receiving the PBU message, the LMA sends a PBA message to the MAG for confirmation.
  • the LMA updates the local PMIPv6 binding cache entry, and associates the delegated prefix(es) with the PMIPv6 binding cache entry.
  • Step 407 After receiving the PBA message, the MAG sends a DHCPv6 Reply message to the MN, updates the local PMIPv6 binding update list entry, and associates the delegated prefix (es) with the PMIPv6 binding update list entry.
  • the MAG may also forward the DHCPv6 Reply message directly to the MN without receiving the PBA message, and the present invention is not particularly limited.
  • other embodiments of the present invention also provide a system in which the proxy mobile IPv6 protocol supports IPv6 prefix allocation.
  • the present invention provides a system for supporting IPv6 prefix allocation by the proxy mobile IPv6 protocol, where the system includes a MN, a MAG, an LMA, and a DHCP server: the MN is configured to obtain an IPv6 prefix by using a DHCPv6 prefix delegation process.
  • the MAG acts as a DHCPv6 relay agent to transfer DHCPv6 messages between the MN and the DHCPv6 server, and the DHCPv6 message is forwarded to the DHCPv6 server through the LMA; or the MAG acts as a relay proxy node of the DHCPv6 or as a DHCPv6 server, and the DHCPv6 message is transparently transmitted through the LMA.
  • the MAG is also used to perform the association between the delegation prefix and the PMIPv6 binding update list entry triggered by the DHCPv6 prefix delegation process.
  • the LMA is also used to perform the delegation prefix under the trigger of the DHCPv6 prefix delegation process. The association between PMIPv6 binding cache entries.
  • the MAG is used as a DHCPv6 relay agent to transfer DHCPv6 messages between the MN and the DHCPv6 server.
  • the MAG is also used as a DHCPv6 relay agent to transfer between the MN and the DHCPv6 server.
  • the DHCPv6 message is used to forward the DHCPv6 message between the MAG and the DHCPv6 server.
  • the DHCPv6 message is transmitted as the PMIPv6 user plane data to the DHCPv6 server through the PMIP tunnel.
  • the MAG and the LMA After the MAG and the LMA complete the DHCPv6 prefix delegation process, the MAG The LMA and the LMA automatically associate the delegate prefix delivered by the DHCPv6 process with their local ⁇ binding update list entry and the local ⁇ 6 binding cache entry.
  • the MAG acts as a relay proxy node of DHCPv6 or as a DHCPv6 server, and the DHCPv6 message is transparently transmitted through the LMA or not through the LMA
  • the MAG is also used as a DHCPv6 relay agent to transfer DHCPv6 between the MN and the DHCPv6 server.
  • the message is that the DHCPv6 message is not forwarded to the DHCPv6 server by the LMA; the MAG is further configured to trigger the PMIPv6 signaling interaction with the LMA when the DHCPv6 prefix delegation process is completed, and notify the LMA of the delegation prefix information, so that the LMA is updated locally.
  • the PMIPv6 binding cache entry associates the delegation prefix with the PMIPv6 binding cache entry.
  • the MAG updates the local PMIPv6 binding update list entry and binds the delegation prefix to the PMIPv6. Update the list item association.
  • the present invention can prevent the MAG and/or LMA from being aware of the change of the IPv6 prefix caused by the failure of the packet to be forwarded, and the PMIPv6 protocol to support the IPv6 prefix allocation.

Landscapes

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

Abstract

L'invention concerne un procédé et un système pour la prise en charge par le protocole PMIPv6 de la distribution de préfixes IPv6, afin de résoudre le problème technique de la façon dont PMIPv6 doit prendre en charge la distribution de préfixes IPv6. Dans la présente invention, lorsqu'un nœud de mobilité obtient le préfixe IPv6 par le processus DHCPv6 de délégation par préfixe, ledit processus DHCPv6 de délégation par préfixe déclenche l'association, par une passerelle d'accès de mobilité (mobility access gateway, MAG) et un point d'ancrage local de mobilité (local mobility anchor, LMA), du préfixe de délégation avec l'entrée d'antémémoire d'association PMIPv6. La présente invention empêche une situation, rencontrée dans la technique antérieure, où la transmission du message contenant le préfixe de délégation échoue en raison de l'absence de détection par la MAG et / ou le LMA du changement du préfixe IPv6, de telle façon que le protocole PMIPv6 prenne en charge la distribution de préfixes IPv6.
PCT/CN2011/084640 2011-01-20 2011-12-26 Procédé et système pour la prise en charge par le protocole pmipv6 de la distribution de préfixes ipv6 WO2012097663A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110023250.3 2011-01-20
CN201110023250.3A CN102611761B (zh) 2011-01-20 2011-01-20 PMIPv6协议支持IPv6前缀分配的方法及系统

Publications (1)

Publication Number Publication Date
WO2012097663A1 true WO2012097663A1 (fr) 2012-07-26

Family

ID=46515137

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/084640 WO2012097663A1 (fr) 2011-01-20 2011-12-26 Procédé et système pour la prise en charge par le protocole pmipv6 de la distribution de préfixes ipv6

Country Status (2)

Country Link
CN (1) CN102611761B (fr)
WO (1) WO2012097663A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103686671B (zh) * 2012-09-14 2019-01-18 中兴通讯股份有限公司 一种通知接入网位置信息的方法和系统
JP6029449B2 (ja) * 2012-12-17 2016-11-24 三菱電機株式会社 スマートメータシステム、管理ルータおよびメータ
CN103249026B (zh) * 2013-05-23 2015-09-16 中国科学院计算机网络信息中心 一种PMIPv6中支持HNP重编号的方法
CN104883408A (zh) * 2014-02-28 2015-09-02 中兴通讯股份有限公司 一种处理NAT64前缀的方法、网络设备及DHCPv6服务器
CN105827746A (zh) * 2016-03-11 2016-08-03 中国互联网络信息中心 一种代理移动IPv6中网络前缀主动重配置的方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080263353A1 (en) * 2007-04-23 2008-10-23 Ralph Edward Droms Autoconfigured prefix delegation based on distributed hash
CN101449529A (zh) * 2006-05-19 2009-06-03 华为技术有限公司 将dhcpv6和aaa用于移动台前缀委派和增强的邻居发现

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101449529A (zh) * 2006-05-19 2009-06-03 华为技术有限公司 将dhcpv6和aaa用于移动台前缀委派和增强的邻居发现
US20080263353A1 (en) * 2007-04-23 2008-10-23 Ralph Edward Droms Autoconfigured prefix delegation based on distributed hash

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SARIKAYA, B. ET AL.: "DHCPv6 Based Home Network Prefix Delegation For PMIPv6. draft-sarikaya-netlmm-prefix-delegation-01.txt", NETWORK WORKING GROUP INTERNET-DRAFT, 9 November 2007 (2007-11-09), pages 5 *
ZHOU, XINGYUE: "Prefix Delegation for Proxy Mobile IPv6 draft-zhou-netext-pd-pmip", IETF, 4 May 2011 (2011-05-04), pages 1 - 6, Retrieved from the Internet <URL:www.ietf.org/proceedings/80/slides/netext-S.pdf> *

Also Published As

Publication number Publication date
CN102611761B (zh) 2017-12-15
CN102611761A (zh) 2012-07-25

Similar Documents

Publication Publication Date Title
KR101653546B1 (ko) 프록시 모바일 ｉｐ 네트워크들에서의 사설 어드레싱 방법
US9578548B2 (en) System and method for configuring multiple IP connections
JP5421392B2 (ja) 宅内ネットワーク内におけるプロキシモバイルＩＰｖ６のサポート
EP2782372B1 (fr) Procédé, élément réseau et équipement utilisateur permettant de réaliser une séparation d&#39;identifiant et d&#39;emplacement et une attribution d&#39;identifiant d&#39;interface
CN102984295B (zh) 一种移动终端及其地址分配方法
JP4968328B2 (ja) モバイルｉｐ通信システム、モバイルｉｐ通信装置およびモバイルｉｐ通信方法
WO2012156171A1 (fr) Relocalisation de passerelle distribuée avec attribution d&#39;adresse de protocole internet centrale
CN112867086B (zh) 一种报文处理方法及装置
JP5052675B2 (ja) モバイルノードのプロキシバインディングを制御する方法
WO2012097663A1 (fr) Procédé et système pour la prise en charge par le protocole pmipv6 de la distribution de préfixes ipv6
EP2466815B1 (fr) Procédé et système de déclenchement d&#39;acheminement de message de communication, d&#39;informations et de données et de configuration de routage
WO2011157141A2 (fr) Procédé et appareil d&#39;attribution d&#39;adresses de protocole internet version 6
WO2011009253A1 (fr) Procédé et système de recherche d&#39;un nom de domaine dans un réseau mobile
WO2011011940A1 (fr) Procédé et système pour établir une connexion de réseau mobile
WO2007135844A1 (fr) Système de commande de communication mobile
EP2716090B1 (fr) Procédé de transmission de données et entité de réseau local
JP2006333406A (ja) 基地局、移動局およびパケット通信システム並びに通信制御方法
WO2013007129A1 (fr) Procédé de traitement de réexpédition de paquets, élément et système de réseau
EP3021529B1 (fr) Procédé et dispositif de mise en oeuvre d&#39;un réseau privé virtuel de couche 3
JP4791402B2 (ja) 移動通信システム及び移動通信プログラム
WO2012159350A1 (fr) Nœud mobile, procédé et système associé d&#39;acquisition d&#39;adresse ip temporaire, et serveur dhcp
EP2668795B1 (fr) Hip proxy et procédé de gestion de mobilité dans un système de communication sans fil
JP4791401B2 (ja) 移動通信システム及び移動通信プログラム
JP4727613B2 (ja) 移動通信システム及び移動通信プログラム
EP2708067B1 (fr) Relocalisation de passerelle distribuée avec attribution d&#39;adresse de protocole internet centrale

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11856257

Country of ref document: EP

Kind code of ref document: A1