WO2007128239A1 - Système d'implémentation d'ipv6 mobile et procédé d'établissement de lien utilisateur dans le système - Google Patents

Système d'implémentation d'ipv6 mobile et procédé d'établissement de lien utilisateur dans le système Download PDF

Info

Publication number
WO2007128239A1
WO2007128239A1 PCT/CN2007/001478 CN2007001478W WO2007128239A1 WO 2007128239 A1 WO2007128239 A1 WO 2007128239A1 CN 2007001478 W CN2007001478 W CN 2007001478W WO 2007128239 A1 WO2007128239 A1 WO 2007128239A1
Authority
WO
WIPO (PCT)
Prior art keywords
pmipv6
client
message
lla
proxy
Prior art date
Application number
PCT/CN2007/001478
Other languages
English (en)
Chinese (zh)
Inventor
Ruobin Zheng
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007128239A1 publication Critical patent/WO2007128239A1/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/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/069—Authentication using certificates or pre-shared keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • 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/18—Service support devices; Network management devices
    • H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy

Definitions

  • the present invention relates to the field of communications, and in particular, to a system for implementing mobile IPv6 and a method for establishing a user connection thereof. Background of the invention
  • BWA Broadband wireless access
  • WIMAX Worldwide Interoperability for Microwave Access
  • the Multiple Hosts architecture based on G-RS (Gateway-Relay Station)/G-MS (Gateway-Mobile Station) defined by the WiMAX Forum is shown in Figure 1.
  • the G-RS/G-MS connects to multiple G-Hosts through the first interface and connects to the ASN (Access Service Network) through the second interface.
  • the first interface is a G-interface interface, the G-interface uses 802. 3 or 802.11 Layer 2 transmission technology; the second interface is an R1 interface, and the R1 uses 802.16e wireless Layer 2 transmission technology.
  • ASN and CSN (Connectivity Service Network) are connected through R3 reference point, CSN of NAP+V-NSP (Network Access Point Visited-Network Service Provider, network access provider and visited network service provider)
  • CSNs of the H-NSP Home-Network Service Provider
  • MIPv6 IP Client Mobile IPv6
  • CMIPv6 IP Client Mobile IPv6
  • RFC 3775 RFC 3775.
  • ⁇ ⁇ 6 involves three functional entities HA (Home Agent, Home Agent), MN (Mobile Node, Mobile) Node) and CN (Correspondent Node, peer-to-peer communication node).
  • the client for CMIPv6 is located at MS/G_Host.
  • MS/G-Host performs a (full state or stateless) address autoconfiguration and uses this newly formed address as its CoA (Care of Address).
  • the MS/G-Host registers the HoA and registers its CoA with the HA on its home link, MS/G-Host to it
  • HA sends a packet containing the "Binding Update” destination option, and HA registers the binding and returns a packet containing the "Binding Confirmation" destination option to MS/G-Host.
  • the HA intercepts all data packets whose addresses are the home address of the MS/G-Host, and each intercepted data packet is encapsulated in IPv6 and transmitted to the care-of address registered by the mobile node by using tunnel technology.
  • a method for communication between communication nodes in the above WIMAX IPv6 network is as follows: If a communication node is to communicate with another MS/G-Host leaving the home network, the routing process of the data packet is: from the communication node Go to HA, from HA to MS/G-Hos1:, then from MS/G-Host to another communication node that leaves the home network. This type of routing is often referred to as a triangular route.
  • the MS/G-Host may send a binding update carrying the current CoA to any communication node, and the communication node caches the current CoA carried on the binding update and directly sends the data packet to the MS. /G-Host.
  • G-Host and G-MS/G-RS are usually mobile networks set up on trains, cars or ships, G-Host is often used as a terminal for fixed passengers relative to G-MS/G-RS.
  • Mobile IPv6 functionality is generally not implemented, making this method inaccessible to existing WiMAX mobile Multihost networks. Summary of the invention
  • the purpose of the embodiment of the present invention is to provide a mobile IPv6-enabled system and a user connection establishment method thereof, so that the MS can only support Simple IPv6 MS, and does not need to implement Mobile IPv6.
  • a system for implementing mobile IPv6, including a home agent may be provided, the system further comprising:
  • IP Proxy Mobile IP Version 6 Client PMIPv6 Client Set to access service network ASN and mobile gateway or ASN and mobile bridge, through the information interaction with the home agent, the proxy mobile node MN performs mobile IPv6 function.
  • a method for establishing a PMIPv6 user connection including: performing access authentication on a MN;
  • the MN automatically configures a link-local address LLA, and performs MD on the LLA;
  • the PMIPvG Client generates the CoA of the MN, and completes the explicit MIPv6 registration.
  • a method for establishing a PMIPv6 user connection including: performing access authentication on a 3 ⁇ 4 ⁇ ;
  • the MN automatically configures the link-local address LLA, and performs DAD on the LLA;
  • ⁇ Client generates the CoA of the MN, completes the MIPv6 registration, and delegates the DAD;
  • the MN automatically configures the HoA through router discovery.
  • a new functional entity PMIPv6 Client (PMIPv6 client) is added to the ASN or G-MS/G-RS by proposing a mechanism of Proxy MIPv6, which is an embodiment of the present invention.
  • PMIPv6 client PMIPv6 client
  • the technical solution in at least has the following advantages:
  • MS can be used only for Simple IPv6, MS does not need to implement Mobile IPv6, which makes MS function simple;
  • the PMIPv6 client (PMIPv6 client) can be set on the network side.
  • the CoA registration does not need to waste air interface resources.
  • Figure 1 is a structural diagram of a Multiple Hosts architecture based on G-RS/G-MS;
  • FIG. 2 is a functional block diagram of a PMIPv6 Client according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a protocol stack of a PMIPv6 data plane according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a PMIPv6 data plane protocol stack of a WiMAX network
  • FIG. 5 is a schematic diagram of a PMIPv6 data plane protocol stack of a Multihost network based on 802.16 transit;
  • FIG. 6 is a schematic diagram of a PMIPv6 data plane protocol stack of a Multihost network
  • FIG. 7 is a flow chart of a DHCPv6-based PMIPv6 user connection establishment process according to an embodiment of the present invention.
  • FIG. 8 is a flow chart of a process for establishing a connection based on an automatically configured PMIPv6 user according to an embodiment of the present invention
  • FIG. 9 is a flowchart of a process for establishing a connection based on an automatically configured PMIPv6 user according to another embodiment of the present invention.
  • FIG. 10 is a flowchart of establishing a connection based on an automatic configuration of a PMIPv6 user according to another embodiment of the present invention. Flow chart.
  • the embodiments of the present invention provide a system for implementing mobile IPv6 and a method for establishing a user connection thereof.
  • a new functional entity PMIPv6 Client (PMIPv6) is added to the ASN and the mobile gateway or the ASN and the mobile bridge. Customer), through the information exchange agent with the authenticator and home agent, the MN performs the mobile IPv6 function.
  • the system described in the embodiment of the present invention is described in detail below.
  • the system in the embodiment of the present invention is based on MIPv6, which mainly adds a new functional entity ⁇ Client to the ASN and the mobile gateway or the ASN and the mobile bridge, and is used by the proxy MN to perform the mobile.
  • IPv6 functionality while MN only needs to support simple Simple IPv6 functionality, without the need to support Mobile IPv6 functionality.
  • the mobile bridge described above includes: a bridge mobile station or a bridge relay station.
  • the mobile gateway includes: G-MS or G-RS, the MN may be MS or G_Host, and the movement brought by the CoA update is transparent to Li.
  • FIG. 2 A functional block diagram of adding a new functional entity PMIPv6 CI i ent in ASN or G-MS/G-RS according to an embodiment of the present invention is shown in FIG. 2 .
  • the PMIPv6 Client includes two sub-function entities, PMIPv6 Client CP and PMIPv6 Client DP.
  • the MN performs the mobile IPv6 control plane functions, such as registration support, ⁇ Client CP and Authenticator (authenticator).
  • the PMIPv6 Client CP and HA obtain the key required for PMIPv6 through Authenticator and AAA.
  • the PMIPv6 Client CP and HA retrieve the relevant information required for MIP registration through AAA information interaction retrieval.
  • ⁇ Client CP agent performs the following control plane functions of mobile IPv6:
  • ⁇ Client DP proxy The MN performs the data plane function of mobile IPv6, such as tunnel support.
  • ⁇ Client DP is always placed on the data path between MN and HA.
  • the PMIPv6 Client DP should support the following features:
  • a multicast address listener that can support the multicast group member protocol. When supporting the multicast address listener, it should be able to receive the tunnel multicast packet from the HA;
  • the above PMIPv6 Client CP and PMIPv6 Client DP may be placed in the same AR (access router) or respectively placed in different ARs.
  • the different ARs support the IPv6 neighbor search and router discovery function, the different AR. It belongs to the same Link (connection) as MN.
  • the HA and AAA in Figure 2 are located in the CSN (Connected Service Network), and the functions of HA and AAA are similar to the prior art.
  • the protocol stack of the above PMIPv6 data plane is shown in Figure 3.
  • PMIPv6 supports route optimization. Among them, HA and CN MIP data surface processing is similar to the prior art.
  • PMIPv6 Client DP is used as the end point of the MIPv6 tunnel.
  • the PMIPv6 Client DP receives the IP packet from the HA or CN, the following processing is performed:
  • the PMIPv6 Client DP completes the function of the router for all IPv6 packets sent by the visiting MN; when PMIPv6 supports the reverse tunnel function, ⁇ Client DP serves as the starting point of the MIPv6 reverse tunnel.
  • the IPv6 packets sent by all visited MNs are processed as follows:
  • the IP packet processed by the tunnel is routed according to the outer IP header and sent out.
  • FIG. 4 is a schematic diagram of a PMIPv6 data plane protocol stack of a WiMAX network
  • FIG. 5 is a schematic diagram of a PMIPv6 data plane protocol stack of a Multihost network based on 802.16,
  • FIG. 6 is a schematic diagram of a PMIPv6 data plane protocol stack of a Multihost network.
  • the PMIPv6 Client DP is located in the ASN, and the MS and the PMIPv6 Client DP form an IPv6 logical link through the 802.16 R1 connection and the tunnel (DP) between the BS and the PMIPv6 Client DP.
  • the PMIPv6 Client DP is located in the ASN and supports multiplexed Hosts based on 802.16 relay.
  • MS and PMIPv6 Client DP pass 802. 16 G_Interface connection, Rl connection, BS and PMIPv6 Client
  • the tunnel between DPs constitutes a logical link of IPv6.
  • the PMIPv6 Client DP is located in G-MS/G-RS and supports G-MS/G-RS based Multiple Hosts.
  • the process of the PMIPv6 user connection establishment process shown in Figure 7 includes the following steps:
  • Step 71 Access authentication.
  • the PMIPv6 Client obtains the AAA key, the HA address, and the HoA or the AAA access authentication message through the H-AAA of the MS (including the MS or the G-Host).
  • DHCP server address it is determined whether the network assigns HoA to the MN; the PMIPv6 Client obtains the AAA key, the HA address, and the HoA or the AAA access authentication message through the H-AAA of the MS (including the MS or the G-Host).
  • Step 72 Automatically configure LLA (link-local address) and DAD (duplicate address detection).
  • the MN After reading the data path between the PMIPv6 Clients, the MN starts the LLA automatic configuration. After the MN performs the LLA auto-configuration, it initiates a Neighbor Solicitation message, performs DAD on the LLA, and contains a tentative (experimental) LLA in the Neighbor Solicitation message.
  • the PMIPv6 Client supports the Proxy DAD (Proxy DAD) of LLA, establishes and maintains the proxy IP Address Cache, and the ⁇ Client can learn the appropriate LLA from the Neighbor Solicitation message; ⁇ Client compares the addresses in the tentative LLA and the Address Cache. If there is a match, the Proxy Neighbor Advertisements message is sent instead of the matching address owner; if there is no match, only the tentative LLA is forced into the Address Cache.
  • Proxy DAD Proxy DAD
  • Step 73 DHCP server configuration.
  • the DHCP Proxy/Relay can download the DHCP server address and the MN identity (MAC address) from the Authenticator; the DHCP proxy/Relay can also statically configure the DHCP server address, and perform step 74 - Step 77; Otherwise, perform steps 78-79. Step 74 - Step 77, IP Address Assignment and IP Host Configuration.
  • MN is transparent to IP mobility, MN uses DHCPv6 for MN HoA allocation and IP host configuration; MN initiates DHCPv6 Solicit message to discover available DHCP server; after receiving DHCP v6 Solicit message, DHCP Proxy/ Relay relays the message to the DHCP server.
  • Any DHCP server that can meet the MN requirements can respond to the DHCP v6 Advertise message to the DHCP Proxy/Relay; DHCP Proxy/Relay relays the DHCP v6 Advertise message to the MN; the MN selects the appropriate DHCP server, and then sends The DHCP v6 Request message is sent to the DHCP server via DHCP Proxy/Relay; the DHCP Server generates a DHCPv6 Reply message, which contains the HoA and IP host configuration options and sends it to the DHCP Pro X y/Relay.
  • the steps in the virtual box in Figure 7 are optional steps.
  • the MN sends a DHCPv6 Solicit message; the DHCP Proxy/Relay responds to the DHCPv6 Advertise message to the MN; it should respond to the DHCPv6 Request message to the DHCP Proxy/Relay.
  • Steps 78 - 79 are identical to Steps 78 - 79.
  • DHCP Proxy/Relay notifies ASN Fn of the MIP mode through R3_Mobility_Context message; if ASN/G-MS/G-RS only Support ⁇ , this step can be omitted;
  • Step 710 CoA is generated.
  • ⁇ Client extracts the interface identifier from the LLA and appends it to the prefix that the AR broadcasts to the CMIPv6 node to generate the CoA of the MN;
  • the PMIPv6 client can also use the IP address of the AR as the MN's CoA. That is, the different MNs of the PMIPv6 Client proxy will use the same CoA. This will impose additional requirements on the HA, and the HA cannot support the CoA uniqueness check on the MN.
  • the DHCP Proxy/Relay After obtaining the HoA by the DHCPv6 or AAA method, the DHCP Proxy/Relay sends the HoA to the PMIPv6 Client through the HoA_Address primitive.
  • the HoA-Address source contains the MN identifier (MAC address).
  • Step 713 - Step 716 MIPv6 registration
  • the PMIPv6 Client can initiate MIPv6 BU (registration message).
  • the MIPv6 BU includes the following information:
  • Security credentials such as MN-AAA authentication mobile options.
  • the HA responds with a binding confirmation message to the PMIPv6 Client
  • Step 714 - Step 715 is optional.
  • the HA obtains the MN by interacting with the H-AAA before the HA responds to the binding confirmation message to the PMIPW Client.
  • - HA key and PMIPv6 Client-HA key are optional.
  • the PMIPv6 Client After successful MIPv6 registration, the PMIPv6 Client sends a DHCP-Gating. Release message, and then the DHCP Proxy/Relay sends a DHCP v6 Reply message to the patient after the R3 session is established.
  • DHCP Gating is used to avoid the MN at the end. Initiate IP communication before the end of the data path is established.
  • the process of establishing a connection based on the automatic configuration of the PMIPv6 user is as shown in FIG. 8 , where the HA is in the V-NSP scenario, and for the HA in the H-NSP scenario, only the V-AAA in FIG. 8 is needed. Can be removed.
  • the process of the PMIPv6 user connection establishment process shown in Figure 8 includes the following steps:
  • Step 81 Access authentication.
  • the PMIPv6 client obtains an AAA key, an HA address, an HL prefix, and an AAA access authentication message exchange with the H-AAA of the MN (including the MS or the G-Host). And HoA.
  • the HoA of the above MN is optional.
  • Step 82 Automatically configure LLA and DAD.
  • the MN starts the LLA automatic configuration.
  • the MN initiates a Neighbor Solicitation message, performs DAD on the LLA, and the Neighbor Solicitation message includes the tentative LLA.
  • the PMIPv6 Client supports the LMA Proxy DAD (Proxy DAD), establishes and maintains the proxy MN IP Address Cache, and the ⁇ Client can learn the LLA from the Neighbor Solicitation message; ⁇ Client compares the addresses in the tentative LLA and the Address Cache If there is a match, the Proxy Neighbor Advertisements message is sent instead of the matching address owner; if there is no match, only the tentative LLA is forced into the Address Cache. Step 83: HoA and CoA are generated.
  • LMA Proxy DAD Proxy DAD
  • the authenticator obtains the HoA of the MN
  • the PMIPv6 Client obtains the HoA directly from the authenticator; otherwise, the PMIPv6 Client extracts the interface identifier from the LLA, and appends it to the HL prefix to generate the HoA of the MN;
  • the PMIPv6 client extracts the interface identifier from the LLA and attaches it to the prefix that the AR broadcasts to the CMIPv6 node to generate the CoA.
  • the PMIPv6 client can also use the IP address of the AR as the CoA of the MN, that is, the different MN of the PMIPv6 Client proxy.
  • the same CoA will be used, which will impose additional requirements on HA, requiring HA to not support CoA uniqueness checks.
  • Step 84 - Step 88 MIPv6 Registration and Proxy DAD.
  • the PMIPv6 Client can initiate the MIPv6 registration message BU;
  • ⁇ BU includes the following information:
  • the HA needs to support the ProA DAD of the HoA (the proxy DAD); after the HA completes the DAD instead of the MN, it responds to the binding confirmation message to the PMIPv6 Client; Step 85-Step 86, this step is optional, and is sent in the PMIPv6 Client when the initial connection is established. After the MIPv6 registration message is sent to the HA, the HA obtains the MN-HA key and the PMIPv6 Client-HA key by interacting with the H-AAA before the HA responds to the binding confirmation message to the PMIPv6 Client. Step 89 - Step 810, Router Discovery.
  • the MN initiates an RS (Router Solicitation) message, and requests the RA (Router Advertisement) message of the AR where the PMIPv6 client is located to learn the on-link prefix.
  • RS Raster Solicitation
  • RA Raster Advertisement
  • Step 811 Automatically configure HoA/DHCPv6 configuration.
  • the MN automatically configures the HoA based on the learned HL prefix; the MN can initiate a stateless DHCPv6 to obtain IP host configuration information.
  • FIG. 9 Another process for establishing a connection based on the automatic configuration of the PMIPv6 user is provided in FIG. 9.
  • the user establishes a connection process to support the Multihosts of the MIMAX system, wherein the HA In the V-NSP scenario, for the HA in the H-NSP scenario, simply remove the V-AAA in Figure 9.
  • the process of establishing a connection by the user shown in FIG. 9 also includes step 81 to step 811 of the process of establishing a connection by the PMIPv6 user shown in FIG. 8, in the process of establishing a connection by the user shown in FIG.
  • G-MS/G- The RS transits the message between the host device and the ASN, for example, the neighbor node request message IPv6 Neighbor Solicitation, the neighbor broadcast message Neighbor Advertisement, the router request message Router Solicitation, or the router broadcast message Router Advertisement.
  • the neighbor node request message IPv6 Neighbor Solicitation the neighbor broadcast message Neighbor Advertisement
  • the router request message Router Solicitation the router broadcast message Router Advertisement
  • FIG. 10 Another process for establishing a connection based on an automatically configured PMIPv6 user according to an embodiment of the present invention is shown in FIG. 10, which supports the separation of PMIPv6 Client CP and PMIPv6 Client DP.
  • the process of the PMIPv6 user connection establishment process shown in FIG. 10 includes the following steps:
  • Step 101 Access authentication.
  • Step 102 Automatically configure LLA and DAD.
  • the MN starts the LLA automatic configuration. After the LLA automatically configures, the MN initiates a Neighbor Solicitation message, performs DAD on the LLA, and the Neighbor Solicitation message includes the tentative LJLA.
  • ⁇ Client DP supports LLA's Proxy DAD (Proxy DAD), establishing and maintaining the proxy MN IP
  • ⁇ Client DP can learn the LLA from the MN's Neighbor Solicitation message; ⁇ Client DP compares the address in the tentative LLA and the Address Cache; if there is a match, the Proxy Neighbor Advertisements message is sent instead of the matching address owner; There is a match, and Bay 1 J only puts the tentative LLA into the Address Cache. Step 103, HoA and CoA are generated.
  • Client DP extracts the interface identifier from the LLA, and attaches it to the prefix that the AR broadcasts to the CMIPv6 node to generate the CoA of the Gu;
  • ⁇ Client DP can also use the IP address of the AR as the CoA of the MN, that is, the different MNs of the PMIPv6 Client DP proxy will use the same CoA, which will bring additional requirements to the HA, and the HA cannot support the CoA uniqueness of the MN. an examination.
  • the PMIPv6 Client DP sends a registration start message to the PMIPv6 Client CP, which includes the MN's CoA or LLA. If the HoA has been given by the Authenticator, the PMIPv6 Client DP can be used directly; otherwise, the PMIPv6 Client DP extracts the interface identifier from the CoA or LLA and appends it to the HL prefix to generate the MN's ⁇ . Step 104 - Step 108, ⁇ 6 registration and proxy DAD. After the CoA generation and HoA acquisition of the MN, the PMIPv6 Client CP can initiate the MIPv6 registration message BU; the MIPv6 BU includes the following information:
  • Security credentials such as Li-AAA certified mobile options.
  • HA needs to support HoA's Proxy DAD (proxy DAD); HA replaces MN after completing DAD, responding to binding confirmation
  • the message is sent to the PMIPv6 Client CP.
  • Step 1010 - Step 1011 the router finds.
  • the MN initiates an RS (Router Solicitation) message requesting the RA of the AR where the PMIPv6 Client DP is located (Router
  • Advertisement The message is replied to learn the on-link prefix (online prefix); ⁇
  • the AR where the client DP is registered after the MIPv6 registration is successful (HoA ⁇ passes the proxy DAD of the HA), and the RA message carrying the HL prefix is sent to the MN according to the RA.
  • the message learns the HL prefix.
  • Step 1012 Automatically configure HoA/DHCPv6 configuration.
  • the MN automatically configures the HoA based on the learned HL prefix; the MN can initiate a stateless DHCPv6 to obtain IP host configuration information.

Abstract

L'invention concerne un système d'implémentation d'IPv6 mobile et un procédé d'établissement de lien utilisateur dans le système, le système comprenant principalement: un client PMIPv6, qui est placé au niveau d'un ASN (réseau de service d'accès) et une passerelle mobile, ou au niveau d'un ASN et d'un pont mobile, le client PMIPv6 fait office d'agent de noeuds mobiles en échangeant des informations avec un agent local, de manière à exécuter une fonction IPv6 mobile. Le procédé faisant appel aux étapesde mise en oeuvre d'une authentification d'accès à un MN; de configuration, par un MN, d'une LLA (adresse de ligne locale) de manière automatique afin de traiter une DAD (détection d'adresse double) sur la LLA; de création, par un client PMIPv6, d'une CoA (adresse temporaire) de MN afin de terminer l'enregistrement MIPv6. A l'aide de l'invention, seul un IPv6 simple supporté par une MS est implémenté, plutôt qu'un IPv6 mobile, de sorte que la fonction de la MS est simple.
PCT/CN2007/001478 2006-04-30 2007-04-29 Système d'implémentation d'ipv6 mobile et procédé d'établissement de lien utilisateur dans le système WO2007128239A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610079645.4 2006-04-30
CNA2006100796454A CN101064648A (zh) 2006-04-30 2006-04-30 实现移动IPv6的系统及其用户连接建立方法

Publications (1)

Publication Number Publication Date
WO2007128239A1 true WO2007128239A1 (fr) 2007-11-15

Family

ID=38667445

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/001478 WO2007128239A1 (fr) 2006-04-30 2007-04-29 Système d'implémentation d'ipv6 mobile et procédé d'établissement de lien utilisateur dans le système

Country Status (2)

Country Link
CN (1) CN101064648A (fr)
WO (1) WO2007128239A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110264775A1 (en) * 2007-08-07 2011-10-27 Posco ICT Co., Ltd. Method and apparatus for supporting mipv6 service in a wireless communication network
CN102761425A (zh) * 2012-07-20 2012-10-31 中兴通讯股份有限公司 计费方法及装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101547383B (zh) 2008-03-26 2013-06-05 华为技术有限公司 一种接入认证方法及接入认证系统以及相关设备
CN101651593A (zh) * 2008-08-11 2010-02-17 华为技术有限公司 一种辅助移动接入网关迁移的方法与装置
CN102387063B (zh) * 2010-08-30 2015-10-21 中兴通讯股份有限公司 一种ifom错误时的处理方法和系统
CN102802222B (zh) * 2011-05-26 2017-06-06 中兴通讯股份有限公司 一种e‑srvcc stn‑sr的获取方法和系统
CN102958039B (zh) * 2011-08-24 2018-03-06 中兴通讯股份有限公司 一种代理移动ip域间节点通信系统及方法
CN103002064A (zh) 2012-11-20 2013-03-27 中兴通讯股份有限公司 一种释放地址的方法、用户节点及远程接入服务器

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060018291A1 (en) * 2004-07-23 2006-01-26 Cisco Technology, Inc. Methods and apparatus for achieving route optimization and location privacy in an IPV6 network
US20060029014A1 (en) * 2004-08-04 2006-02-09 Jagadish Maturi System and method for establishing dynamic home agent addresses and home addresses using the mobile IPv6 protocol
JP2006109373A (ja) * 2004-10-08 2006-04-20 Yaskawa Information Systems Co Ltd ＭｏｂｉｌｅＩＰｖ６ネットワークシステムおよびその通信方法、ルータ装置、ＭｏｂｉｌｅＮｏｄｅおよび記録媒体

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060018291A1 (en) * 2004-07-23 2006-01-26 Cisco Technology, Inc. Methods and apparatus for achieving route optimization and location privacy in an IPV6 network
US20060029014A1 (en) * 2004-08-04 2006-02-09 Jagadish Maturi System and method for establishing dynamic home agent addresses and home addresses using the mobile IPv6 protocol
JP2006109373A (ja) * 2004-10-08 2006-04-20 Yaskawa Information Systems Co Ltd ＭｏｂｉｌｅＩＰｖ６ネットワークシステムおよびその通信方法、ルータ装置、ＭｏｂｉｌｅＮｏｄｅおよび記録媒体

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110264775A1 (en) * 2007-08-07 2011-10-27 Posco ICT Co., Ltd. Method and apparatus for supporting mipv6 service in a wireless communication network
CN102761425A (zh) * 2012-07-20 2012-10-31 中兴通讯股份有限公司 计费方法及装置
CN102761425B (zh) * 2012-07-20 2018-06-12 中兴通讯股份有限公司 计费方法及装置

Also Published As

Publication number Publication date
CN101064648A (zh) 2007-10-31

Similar Documents

Publication Publication Date Title
US7616615B2 (en) Packet forwarding apparatus for connecting mobile terminal to ISP network
JP5118055B2 (ja) 移動体ネットワーク上におけるインターネット・プロトコル・トンネリング
US8040850B2 (en) Advanced internet protocol with flash-OFDM methods and systems
JP3587984B2 (ja) 移動通信システム、パケットゲートウェイ装置、位置情報管理方法、および、位置情報通知方法
JP4909357B2 (ja) イーサネット伝送プロトコルを基礎とするデータパケットを少なくとも１つのモバイル通信ユニットと通信システムとの間において伝送する方法
Leung et al. WiMAX forum/3GPP2 proxy mobile IPv4
US20100017528A1 (en) Mobile terminal management system, network device, and mobile terminal operation control method used for them
US20070268919A1 (en) Using DHCPv6 and AAA for Mobile Station Prefix Delegation and Enhanced Neighbor Discovery
JP4681656B2 (ja) クライアントモバイルｉｐ（ｃｍｉｐ）に代わるプロキシモバイルｉｐ（ｐｍｐ）の加入者固有の強制
US8175102B2 (en) Neighbor discovery method and apparatus for mobile node in heterogeneous network environment
WO2007128239A1 (fr) Système d'implémentation d'ipv6 mobile et procédé d'établissement de lien utilisateur dans le système
WO2009007870A2 (fr) Optimisation de la mobilité d'un serveur mandataire
KR20080075306A (ko) 비손실 모바일 ｉｐ 패킷 전달 방법 및 그 시스템
WO2008022597A1 (fr) Procédé et dispositif pour transfert intercellulaire de terminal procédé et dispositif permettant d'obtenir l'adresse d'une entité d'accès d'origine
KR20100004964A (ko) 모바일 ｉｐ 통신 시스템, 모바일 ｉｐ 통신 장치 및 모바일 ｉｐ 통신 방법
CN100563221C (zh) 一种终端地址相关信息获取方法及系统
KR100915513B1 (ko) 프락시 모바일 ＩＰｖ６에서 패킷 손실을 줄이기 위한 패킷버퍼링 장치 및 방법
US8045569B1 (en) Mechanism to verify packet data network support for internet protocol mobility
WO2009155863A1 (fr) Procédé et système destinés à prendre en charge une sécurité de mobilité dans un réseau de prochaine génération
WO2007143950A1 (fr) Appareil et procédé de mise en œuvre de l'amorce du nœud en double pile d'un réseau hétérogène
JP3573098B2 (ja) 移動網における移動端末管理システム、アクセスルータ、移動端末管理方法
WO2011050679A1 (fr) Réseau de communication et procédé d'accès de terminal mis en oeuvre grâce à une infrastructure de réseau wimax
CN101790146A (zh) 分配地址信息的方法、网络设备和网络系统
CN101651662A (zh) 简单互联网协议地址的分配方法与装置
KR20030035587A (ko) 이동통신에서의 인터넷 프로토콜 가상 사설망 서비스처리장치 및 방법

Legal Events

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

Ref document number: 07721051

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

Country of ref document: EP

Kind code of ref document: A1