CN101064648A - System for realizing mobile IPv6 and its method for establishing user connection - Google Patents
System for realizing mobile IPv6 and its method for establishing user connection Download PDFInfo
- Publication number
- CN101064648A CN101064648A CNA2006100796454A CN200610079645A CN101064648A CN 101064648 A CN101064648 A CN 101064648A CN A2006100796454 A CNA2006100796454 A CN A2006100796454A CN 200610079645 A CN200610079645 A CN 200610079645A CN 101064648 A CN101064648 A CN 101064648A
- Authority
- CN
- China
- Prior art keywords
- message
- pmipv6
- pmipv6 client
- client
- address
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明提供了一种实现移动IPv6的系统及其用户连接建立方法,该系统主要包括:PMIPv6 Client(IP代理移动IP版本6客户):设置于ASN(接入服务网络)或移动网关或移动网桥,通过和家乡代理进行信息交互代理MN(移动节点)执行移动IPv6功能。利用本发明,可以实现MS仅支持SimpleIPv6,无须实现Mobile IPv6,从而使MS功能简单。
The present invention provides a system for realizing mobile IPv6 and a method for establishing user connection thereof. The system mainly includes: PMIPv6 Client (IP proxy mobile IP version 6 client): set in ASN (access service network) or mobile gateway or mobile network The bridge acts as a proxy for the MN (Mobile Node) to perform mobile IPv6 functions by exchanging information with the home agent. Utilizing the present invention, it can be realized that MS only supports SimpleIPv6 without implementing Mobile IPv6, so that the functions of MS are simple.
Description
Technical Field
The invention relates to the field of communication, in particular to a system for realizing mobile IPv6 and a user connection establishing method thereof.
Background
A BWA (Broadband wireless access) device may provide a convenient Broadband access manner for a user. At present, broadband wireless access equipment based on a private protocol exists, and broadband wireless access equipment based on a standard protocol also exists. Broadband wireless access devices defined by the IEEE (institute of electrical and electronics engineers) 802.16 standard are a subset of a family of standards for broadband wireless access technologies. The BWA device includes a WIMAX (worldwide interoperability for microwave access) device.
The WiMAX forum defines a Multiple Hosts architecture based on G-RS (gateway relay station)/G-MS (gateway mobile station) as shown in fig. 1. The G-RS/G-MS is connected to a plurality of G-hosts through a first interface and connected to an ASN (access service network) through a second interface. Wherein, the first interface is a G-interface which adopts 802.3 or 802.11 two-layer transmission technology; the second interface is the R1 interface, and R1 employs 802.16e wireless two-layer transport technology. The ASN and the CSN (connection service network) are connected through an R3 reference point, and the CSN of NAP + V-NSP (network access provider and visited network service provider) and the CSN of H-NSP (home network service provider) are connected through an R5 reference point.
In WIMAX IPv6 networks, the MIPv6(IP client mobile IPv6) of the CMIPv6(IP client mobile IPv6) standard is currently adopted, see RFC 3775. MIPv6 relates to three functional entities HA (home agent), MN (mobile node) and CN (peer communication node). The client of CMIPv6 is located at the MS/G-Host. During the movement of R3, the MS/G-Host performs (full state or stateless) address autoconfiguration and takes this newly formed address as its CoA (care-of address).
The MS/G-Host registers HoA and registers CoA with HA on its home link, and sends data packet containing destination option of 'binding update' to HA, which registers the binding and returns a data packet containing destination option of 'binding acknowledgement' to MS/G-Host. The HA intercepts all data packets with the home address of the MS/G-Host, and each intercepted data packet is encapsulated by IPv6 and sent to the care-of address registered by the mobile node by adopting a tunneling technology.
In the prior art, a method for communication between communication nodes in the WIMAX IPv6 network includes: if a communication node wants to communicate with another MS/G-Host away from the home network, the routing process of the data packet is: from the correspondent node to the HA, from the HA to the MS/G-Host, and from the MS/G-Host to another correspondent node away from the home network. This type of routing is commonly referred to as triangular routing. In order to avoid the triangular routing problem, the MS/G-Host may send a binding update carrying the current CoA to any one of the correspondent nodes, which caches the current CoA carried in the binding update and directly sends a packet to the MS/G-Host.
The disadvantages of the above method are:
1. the method requires that the MS must realize Mobile IPv6, and cannot adopt the MS only supporting Simple IPv6 (Simple IPv6), so that the function of the MS is complex;
2. the method needs to waste air interface resources for CoA registration;
3. since the 3G network (e.g., WCDMA) does not support CMIPv6, communicating according to this method makes the interconnection of WiMAX and the 3G network (e.g., WCDMA) problematic;
4. since the G-Host and the G-MS/G-RS are usually Mobile networks installed on trains, automobiles or ships, the G-Host is often a terminal used by passengers fixed relative to the G-MS/G-RS, and the Mobile IPv6 function cannot be realized, so that the method cannot be used in the existing WiMAX Mobile multi-Host network.
Disclosure of Invention
In view of the problems existing in the prior art, the present invention aims to provide a system for implementing Mobile IPv6 and a user connection establishment method thereof, so that an MS that only supports Simple IPv6 can be implemented without implementing Mobile IPv 6.
The purpose of the invention is realized by the following technical scheme:
a system for implementing mobile IPv6, including a home agent, further comprising:
IP proxy mobile IP version 6Client PMIPv6 Client: and the mobile node MN is arranged in an access service network ASN or a mobile gateway or a mobile bridge and performs the function of mobile IPv6 by acting on the information interaction agent MN with the home agent.
The PMIPv6Client comprises:
PMIPv6Client control plane PMIPv6Client CP: the proxy MN performs the control plane functions of the mobile IPv 6;
PMIPv6Client data plane PMIPv6Client DP: and the proxy MN executes the data plane function of mobile IPv6 on a data path between the MN and the home agent HA.
The PMIPv6Client CP agent MN executes mobile detection, care-of address CoA generation and returns to the home location;
the PMIPv6Client CP agent MN executes the processing of mobile head Mobility heads;
the PMIPv6Client CP agent MN sends the Binding update Updates message;
the PMIPv6Client CP agent MN executes the receiving and processing of the binding acknowledgement messages;
the PMIPv6Client CP agent MN receives the Binding refreshing request message and sends a Binding updating Update message as a response;
the PMIPv6Client CP agent MN receives the Mobile prefix advertisement messages and the routing advertisement messages sent to the MN contain the prefix information in the Mobile prefix advertisement messages;
the PMIPv6Client CP agent MN receives the binding error message;
and/or the presence of a gas in the gas,
the PMIPv6Client CP agent MN receives the ICMP error message of the Internet control message protocol;
and/or the presence of a gas in the gas,
the PMIPv6Client CP agent MN executes a return routability procedure;
and/or
The PMIPv6Client CP acts on MN to discover the dynamic home address HA address.
The PMIPv6Client CP acting on MN to perform mobility detection specifically includes:
for worldwide interoperability for microwave access WiMAX networks, the mobility detection may be supported with the assistance of a radio resource management module or a handover control module.
The PMIPv6Client CP and the authenticator are placed together, and the PMIPv6Client CP and the HA obtain a key required by the PMIPv6 through the authenticator and the AAA server.
The PMIPv6Client DP agent MN executes IPv6 tunnel encapsulation and decapsulation;
the PMIPv6Client DP agent MN executes the starting and the closing of the route optimization;
the PMIPv6Client DP agent MN executes packet sending containing home address HoA options and interaction of IP security protocol IPsec;
and/or the presence of a gas in the gas,
the PMIPv6Client DP agent MN executes multicast address audience of multicast group member protocol, and receives a tunnel multicast packet from HA;
and/or the presence of a gas in the gas,
the PMIPv6Client DP agent MN executes the routing header processing of the 2-type routing header;
and/or the presence of a gas in the gas,
the PMIPv6Client DP establishes and maintains an address pool of the proxied MN;
and/or the presence of a gas in the gas,
for a wireless network, the PMIPv6Client DP supports Proxy DAD, and replaces MN to execute DAD function.
The PMIPv6Client CP and the PMIPv6Client DP are arranged in the same AR or are respectively arranged in different ARs.
The MN includes a mobile station and a host device.
The system of the mobile IPv6 is applicable to a multi-host Multiple Hosts architecture of a WIMAX system, and the WIMAX system comprises: the mobile gateway or the mobile bridge is connected with each host device through a first interface and connected with the ASN through a second interface.
The mobile gateway comprises: a gateway mobile station G-MS or a gateway relay station G-RS, said mobile bridge comprising: a bridge mobile station or a bridge transit station.
A PMIPv6 user connection establishment method comprises the following steps:
A. performing access authentication on MN;
B. MN automatically configures link-local address LLA, and DAD is carried out on LLA;
C. PMIPv6Client generates CoA of MN, completes MIPv6 registration.
The step A specifically comprises the following steps:
PMIPv6Client obtains AAA key, HA address and HoA or DHCP server address by performing AAA access authentication message interaction with the home H-AAA server of MN.
The step B specifically comprises the following steps:
once a data path between the MN and the PMIPv6Client is established, the MN starts to carry out LLA automatic configuration; after the MN performs LLA automatic configuration, a Neighbor Solicitation message is initiated, DAD is performed on the LLA, and the Neighbor Solicitation message contains experimental tentativeLLA;
PMIPv6Client establishes and maintains the proxied MN IP Address Cache; comparing the addresses in the LLA and the Address Cache, and if the addresses are matched, replacing a matched Address owner to send Proxy Neighbor Advertisements; otherwise, add the LLA to the Address cache.
The step C specifically comprises the following steps:
c1, when the authenticator gets DHCP server address in the access process, the DHCPproxy/Relay downloads DHCP server address and MN identification from the authenticator; or, the DHCP server address is statically configured;
c2, MN uses DHCPv6 to carry out MN HoA distribution and IP host configuration;
c3, PMIPv6Client obtains HoA of MN from DHCP Proxy/Relay;
c4 and PMIPv6Client acquire the interface identifier from the LLA, and attach the interface identifier to the prefix broadcasted by the AR to the CMIPv6 node to generate the CoA of the MN; or, the PMIPv6Client takes the IP address of the AR as the CoA of the MN;
c5, PMIPv6Client sends MIPv6 registration message containing HoA, CoA and security data of MN, HA responds binding confirmation message to PMIPv6 Client.
The step C2 specifically includes:
the MN sends a DHCPv6Solicit message; the DHCP Proxy/Relay transfers the received DHCPv6Solicit message to the DHCP server, and transfers the DHCPv6 advertisement message responded by the DHCP server to the MN; MN selects the needed DHCP Server, responds DHCPv6Request message to the selected DHCP Server through DHCP Proxy/Relay, the DHCP Server sends DHCPv6 Reply message containing HoA and IP host configuration options to DHCP Proxy/Relay;
or,
the MN sends a DHCPv6Solicit message; DHCP Proxy/Relay responds DHCPv6 advertisement message to MN; the MN responds to the DHCPv6Request message to the DHCP Proxy/Relay.
The step C3 specifically includes:
after the DHCP Proxy/Relay obtains the HoA of the MN by a DHCPv6 method, the HoA is sent to the PMIPv6Client through the HoA Address source language, and the HoA Address source language comprises the MN identification.
The step C specifically comprises the following steps:
c7, when in the access process, after the PMIPv6Client obtains the HoA of the MN, the PMIPv6Client obtains the interface identifier from the LLA, and attaches the interface identifier to the prefix of the AR where the interface identifier is located and broadcasts the prefix to the CMIPv6 node to generate the CoA of the MN; or, the PMIPv6Client takes the IP address of the AR as the CoA of the MN;
c8, PMIPv6Client sends MIPv6 registration message containing HoA, CoA and security data of MN to HA, HA responds binding confirmation message to PMIPv6 Client.
The step C5 and the step C8 further comprise:
after finishing MIPv6 registration, sending a DHCP _ gating.Release message for releasing a DHCP gating function, wherein the DHCP gating function is used for avoiding that the MN initiates IP communication before an end-to-end data path is established; after the R3 session is established, the DHCP Proxy/Relay sends a DHCPv6 Reply message to the MN.
The step C further comprises the following steps:
when the ASN/G-MS/G-RS supports the PMIPv6 and CMIPv6 dual modes, the DHCP Proxy/Relay informs the MIP mode adopted by the ASN Fn through an R3_ Mobility _ Context message.
The step C further comprises the following steps:
when the initial connection is established, after the PMIPv6Client sends a MIPv6 registration message to the HA, before the HA responds to a binding confirmation message to the PMIPv6Client, the HA interacts with the H-AAA to acquire an MN-HA key and a PMIPv6 Client-HA key.
The method is suitable for a V-NSP scene of the HA network service provider at the visit place or an H-NSP scene of the home location network service provider.
A PMIPv6 user connection establishment method comprises the following steps:
D. performing access authentication on MN;
E. MN automatically configures link-local address LLA, and DAD is carried out on LLA;
F. PMIPv6Client generates CoA of MN, completes MIPv6 registration and acts as DAD;
G. the MN automatically configures the HoA through router discovery.
The step D specifically comprises the following steps:
PMIPv6Client obtains AAA key, HA address and HL prefix by performing AAA access authentication message interaction with the H-AAA server of MN.
The step D also comprises the following steps:
PMIPv6Client obtains the HoA of the MN by performing AAA access authentication message interaction with the H-AAA server of the MN.
The step E specifically comprises the following steps:
once a data path between the MN and the PMIPv6Client is established, the MN starts to carry out LLA automatic configuration; after the MN performs LLA automatic configuration, a Neighbor Solicitation message is initiated, DAD is performed on the LLA, and the Neighbor Solicitation message contains a tentative LLA;
PMIPv6Client establishes and maintains the proxied MN IP Address Cache; comparing the addresses in the LLA and the Address Cache, and if the addresses are matched, replacing a matched Address owner to send Proxy Neighbor Advertisements; otherwise, add the LLA to the Address cache.
The step F specifically comprises the following steps:
f1, when the authenticator obtains the HoA of the MN in the access process, the PMIPv6Client directly obtains the HoA from the authenticator; otherwise, the PMIPv6Client extracts the interface identifier from the LLA, attaches the interface identifier to the HL prefix and then generates the HoA of the MN; the PMIPv6Client attaches the interface identifier to a prefix broadcasted to the CMI Pv6 node by the AR where the interface identifier is located to generate the CoA of the MN, or the IP address of the AR where the interface identifier is located is used as the CoA of the MN;
f2, PMIPv6Client sends MIPv6 registration message containing HoA, CoA and security data of MN; after the HA replaces the MN to complete the DAD, a binding confirmation message is responded to the PMIPv6 Client.
The step F further comprises the following steps:
when the initial connection is established, after the PMIPv6Client sends a MIPv6 registration message to the HA, before the HA responds to a binding confirmation message to the PMIPv6Client, the HA interacts with the H-AAA to acquire an MN-HA key and a PMIPv6 Client-HA key.
The step G specifically comprises the following steps:
the MN sends a router request message, after the AR where the PMIPv6Client is located successfully registers in the MIPv6, the AR responds to the MN with a router advertisement message carrying an HL prefix, the MN learns the HL prefix according to the router advertisement message, automatically configures HoA according to the HL prefix,
or,
after the AR where the PMIPv6Client is located finishes MIPv6 registration, a router advertisement message carrying an HL prefix is actively sent to the MN, the MN learns the HL prefix according to the router advertisement message, and the HoA is automatically configured according to the HL prefix.
The step G further comprises:
the MN initiates a stateless DHCPv6 to obtain IP host configuration information.
Further comprising:
the method is suitable for Multiple Hosts architecture of WIMAX system, and the WIMAX system comprises the following steps: the system comprises host equipment, a mobile gateway or a mobile bridge, and ASN and CSN which are connected with each other, wherein the mobile gateway or the mobile bridge is connected with each host equipment through a first interface and is connected with the ASN through a second interface, and the mobile gateway or the mobile bridge transfers information between the host equipment and the ASN.
The message between the host device and the ASN comprises: neighbor request message IPv6Neighbor Solicitation, Neighbor broadcast message Neighbor Advertisement, Router request message Router Solicitation, or Router broadcast message Router Advertisement.
The step E specifically comprises the following steps:
once a data path between the MN and the PMIPv6Client DP is established, the MN starts to carry out LLA automatic configuration; after the MN performs LLA automatic configuration, a Neighbor Solicitation message is initiated, DAD is performed on the LLA, and the Neighbor Solicitation message contains a tentative LLA;
PMIPv6Client DP supports LLA agent DAD, establishes and maintains the agent MN IPAddress Cache, PMIPv6Client DP learns MN LLA from MN Neighbor Solicitation message; PMIPv6Client DP compares the addresses in the latent LLA and the Address Cache; if the matching exists, the Proxy neighbor address notification message is sent instead of the matching address owner; if there is no match, then only the tentative LLA is added to the Address cache.
The step F specifically comprises the following steps:
f3, PMIPv6Client DP obtains the interface identifier from the LLA, attaches the interface identifier to the prefix broadcasted by the AR to the CMIPv6 node to generate the CoA of the MN, or takes the IP address of the AR as the CoA of the MN;
f4, PMIPv6Client DP sends registration start message containing CoA or LLA of MN to PMIPv6Client CP, starts MIPv6 registration process;
f5, if PMIPv6Client DP obtains the HoA of MN, PMIPv6Client DP directly uses the HoA; otherwise, PMIPv6Client DP obtains the interface identifier from the LLA or CoA, attaches the interface identifier to HL prefix and then generates the HoA of MN;
f6, PMIPv6Client CP sends MIPv6 registration message containing HoA, CoA and security data of MN, HA replaces MN to finish DAD, responds to binding confirmation message to PMIPv6Client CP; the PMIPv6Client CP sends a registration success message to the PMIPv6Client DP.
The step G specifically comprises the following steps:
the MN sends a router request message, after the AR where the PMIPv6Client DP is located successfully registers in the MIPv6, the AR responds to the MN with a router advertisement message carrying an HL prefix, the MN learns the HL prefix according to the router advertisement message, automatically configures HoA according to the HL prefix,
or,
after the PMIPv6 AR where the Client DP is located finishes MIPv6 registration, actively sending a router advertisement message carrying an HL prefix to the MN, the MN learns the HL prefix according to the router advertisement message, automatically configuring an HoA according to the HL prefix,
the MN initiates a stateless DHCPv6 to obtain IP host configuration information.
Further comprising:
the method is suitable for Multiple Hosts architecture of WIMAX system, and the WIMAX system comprises the following steps: the system comprises host equipment, a mobile gateway or a mobile bridge, and ASN and CSN which are connected with each other, wherein the mobile gateway or the mobile bridge is connected with each host equipment through a first interface and is connected with the ASN through a second interface, and the mobile gateway or the mobile bridge transfers information between the host equipment and the ASN.
The message between the host device and the ASN comprises: IPv6Neighbor Solicitation, Neighbor Advertisement, Router Solicitation or Router Advertisement.
It can be seen from the above technical solutions that, by providing a mechanism of Proxy MIPv6, the present invention adds a new functional entity PMIPv6Client (PMIPv6 Client) to an ASN or G-MS/G-RS, which has the following advantages:
1. the MS only supporting Simple IPv6 can be used, and the MS does not need to realize Mobile IPv6, so that the function of the MS is Simple;
2. PMIPv6Client (PMIPv6 Client) can be arranged at the network side, and CoA registration does not need to waste air interface resources;
3. because the MS only supporting Simple IPv6 can be used, the MIP problem when WiMAX and 3G networks (such as WCDMA) are interconnected can be solved;
4. the restriction of WiMAX mobile multi-Host is solved because G-Host supporting only Simple IPv6 can be used.
Drawings
FIG. 1 is a block diagram of a Multiple Hosts architecture based on G-RS/G-MS;
FIG. 2 is a functional block diagram of the PMIPv6Client according to the present invention;
FIG. 3 is a diagram of a protocol stack of the PMIPv6 data plane according to the present invention;
FIG. 4 is a diagram of a data plane protocol stack of a WiMAX network PMIPv 6;
fig. 5 is a schematic diagram of a data plane protocol stack of a multi host network PMIPv6 based on 802.16 relay;
fig. 6 is a schematic diagram of a data plane protocol stack of a multi host network PMIPv 6;
FIG. 7 is a flow chart of a DHCPv 6-based PMIPv6 user connection establishment procedure according to the present invention;
FIG. 8 is a flow chart illustrating a process for establishing a connection for a PMIPv6 user based on automatic configuration according to the present invention;
FIG. 9 is a flowchart of a process for establishing connections for users based on automatically configured PMIPv6 according to the present invention;
fig. 10 is a flowchart of a process of establishing a connection based on an automatically configured PMIPv6 user according to the present invention.
Detailed Description
The invention provides a system for realizing mobile IPv6 and a user connection establishing method thereof, the core of the invention is as follows: a new functional entity PMIPv6Client (PMIPv6 Client) is added in the ASN or the mobile gateway or the mobile bridge, and the mobile IPv6 function is executed by the information interaction agent MN with the authenticator and the home agent.
The system of the present invention is described in detail below, and the system of the present invention is based on MIPv6, and its main inventive point is that a new functional entity PMIPv6Client is added to the ASN or mobile gateway or mobile bridge for acting MN to execute mobile IPv6 function, while MN only needs to support Simple IPv6 function and does not need to support mobile IPv6 function.
The mobile bridge described above comprises: a bridge mobile station or a bridge transit station. In a WiMAX network, the mobile gateway includes: G-MS or G-RS, MN can be MS or G-Host, and the movement brought by CoA update is transparent to MN.
The functional block diagram of adding a new functional entity PMIPv6Client to the ASN or G-MS/G-RS provided by the invention is shown in FIG. 2. The PMIPv6Client comprises two subfunction entities of PMIPv6Client CP and PMIPv6Client DP.
The PMIPv6Client CP performs control plane functions of the mobile IPv6 in proxy for the MN, as supported by registration, and the PMIPv6Client CP is co-located with the Authenticator. PMIPv6 the client CP and HA get the key needed by PMIPv6 through Authenticator and AAA; in the authentication process, the PMIPv6Client CP and the HA search through AAA information interaction to obtain the relevant information required by MIP registration.
The PMIPv6Client CP proxy MN performs the following control plane functions of mobile IPv 6:
1. supporting reception of a Binding Error message;
2. supporting reception of an ICMP error message;
3. support mobile detection, CoA generation and home return;
4. support the processing of Mobility heads;
5. support for return routability procedure;
6. the transmission of Binding Updates messages is supported;
7. supporting the receiving and processing of Binding Acknowledgements (Binding acknowledgement) messages;
8. supporting the receiving of a Binding Refresh Request message and responding with a Binding Update message;
9. the method supports the receiving of Mobile Prefix Advertisements, and Prefix information in the Mobile Prefix Advertisement message is contained in the Router Advertisement message sent to the MN;
10. support a dynamic HA address discovery mechanism;
11. for WiMAX networks, Proxy DAD (Proxy duplicate address detection) is supported.
PMIPv6Client DP proxy MN performs the data plane functions of Mobile IPv6, such as support of tunnel, and PMIPv6Client DP is always placed on the data path between MN and HA.
PMIPv6Client DP should support the following functions:
1. the method supports packet transmission with HoA options and supports Ipsec (IP Security protocol) interaction;
2. supporting IPv6 tunnel encapsulation and decapsulation;
3. supporting 2-type routing header processing;
4. the starting and the closing of route optimization are supported;
5. the multicast address audience which can support the multicast group member protocol should be able to receive the tunnel multicast packet from the HA when supporting the multicast address audience;
6. the method supports the establishment and maintenance of the proxied MN IP Address Cache (Address pool), supports Proxy DAD for the WiMAX network, and replaces the MN to complete the DAD function.
The PMIPv6Client CP and the PMIPv6Client DP can be arranged in the same AR or respectively arranged in different ARs, the different ARs support the functions of searching the IPv6 adjacent node and discovering the router of the MN, and the different ARs and the MN belong to the same Link.
The HA and AAA in fig. 2 are located in the CSN (connection service network), and the functions of the HA and AAA are the same as those of the prior art.
The protocol stack of the data plane of PMIPv6 is shown in fig. 3, and PMIPv6 supports route optimization. The HA and CN MIP data surface processing is the same as the prior art.
In the downlink (CN- > MN) direction, PMIPv6Client DP is used as the end point of MIPv6 tunnel, and when PMIPv6Client DP receives IP packet from HA or CN, the following processes are carried out:
1. checking the IP destination address of the outer layer of the tunnel, judging whether the IP destination address is the CoA of the MN of the proxy of the tunnel, and if so, receiving the IP packet and carrying out subsequent processing; otherwise, the IP packet is discarded.
2. And performing tunnel de-encapsulation processing on the received IP packet.
3. Checking the tunnel inner layer IP destination address of the IPv6 packet subjected to tunnel de-encapsulation, judging whether the address is the HoA (home address) of the MN of the proxy, and if so, sending the IPv6 packet subjected to tunnel de-encapsulation to the MN; otherwise, the IP packet is discarded.
In the uplink (MN- > CN) direction, when the PMIPv6 does not support the reverse tunnel function, for the IPv6 packet sent by all visiting MNs, the PMIPv6Client DP completes the function of the router; when the PMIPv6 supports the reverse tunnel function, the PMIPv6Client DP is used as the starting point of the MIPv6 reverse tunnel, and the IPv6 packets sent by all visiting MNs are processed as follows:
1. checking the IP source address of the IPv6 packet, judging whether the IP source address is the HoA of the MN of the proxy of the IPv6 packet, and if not, directly routing the received IP packet and sending the IP packet; if yes, performing tunnel encapsulation processing on the received IP packet, adding an outer layer IP header with CoA of MN as a source address and IPv6 address of HA or CN as a destination address, and performing subsequent processing;
2. and routing the IP packet subjected to tunnel encapsulation according to the outer IP header, and sending out.
The protocol stack of the PMIPv6 data plane is illustrated in fig. 4-6 for an embodiment of a WiMAX network. Fig. 4 is a schematic diagram of a data plane protocol stack of WiMAX network PMIPv6, fig. 5 is a schematic diagram of a data plane protocol stack of multi-host network PMIPv6 based on 802.16 relay, and fig. 6 is a schematic diagram of a data plane protocol stack of multi-host network PMIPv 6.
In fig. 4, PMIPv6Client DP is located on ASN, MS is connected to PMIPv6Client DP via 802.16R1, and tunnel (DP) between BS and PMIPv6Client DP forms a logical Link of IPv 6.
In fig. 5, PMIPv6Client DP is located on ASN and supports multiple hosts function based on 802.16 relay, and the logical Link of IPv6 is formed by 802.16G-Interface connection between MS and PMIPv6Client DP, R1 connection, and tunnel (DP) between BS and PMIPv6Client DP.
In FIG. 6, PMIPv6Client DP is located at G-MS/G-RS, supporting G-MS/G-RS based Multiple Hosts functionality.
The method of the present invention is described in detail below with reference to the accompanying drawings.
In terms of PMIPv6 signaling plane processing, a flow of PMIPv6 user connection establishment process based on DHCPv6 (dynamic host configuration protocol IPv6) is shown in fig. 7, where the HA is in V-NSP (visited network service provider), and for the HA is in H-NSP (home network service provider), the V-AAA in fig. 7 only needs to be removed.
The PMIPv6 user connection establishment procedure shown in fig. 7 includes the following steps:
and step 71, access authentication.
In the access authentication process, whether the network allocates the HoA to the MN is determined; PMIPv6Client obtains AAA key, HA address, and HoA or DHCP server address by performing AAA access authentication message interaction with H-AAA of MN (including MS or G-Host).
Step 72, automatic configuration LLA (link-local address) and DAD (duplicate address detection).
Once a data path between the MN and the PMIPv6Client is established, the MN starts to carry out LLA automatic configuration; after the MN performs LLA automatic configuration, a Neighbor Solicitation message is initiated, DAD is performed on the LLA, and the Neighbor Solicitation message contains tentative LLA.
PMIPv6Client supports Proxy DAD (Proxy DAD) of LLA, establishes and maintains Proxy MN IP Address Cache, PMIPv6Client can learn LLA of MN from Neighbor Solicitation message of MN; PMIPv6Client compares the addresses in the tentative LLA and the Address Cache; if the matching exists, the Proxy neighbor address notification message is sent instead of the matching address owner; if there is no match, then only the tentative LLA is added to the Address cache.
And step 73, configuring the DHCP server.
If the Authenticator obtains the DHCP server address in step 71, the DHCPProxy/Relay may download the DHCP server address and MN identification (MAC address) from the Authenticator; DHCP Proxy/Relay can also statically configure DHCP server address, execute step 74-step 77; otherwise, steps 78-79 are performed. Step 74-step 77, IP address assignment and IP host configuration.
In the PMIPv6 scheme, the MN is transparent to IP movement, and the MN utilizes DHCPv6 to carry out MNHoA allocation and IP host configuration; the MN initiates a DHCPv6Solicit message to discover available DHCPservers; after receiving DHCPv6Solicit message, DHCP Proxy/Relay transfers the message to DHCP server; any DHCP server which can meet the requirements of MN can respond DHCPv6 advertisement message to DHCP Proxy/Relay; the DHCP Proxy/Relay transfers the DHCPv6 advertisement message to the MN; the MN selects a proper DHCP Server, and then sends a DHCPv6Request message to the DHCP Server through a DHCP Proxy/Relay; the DHCP Server generates a DHCPv6 Reply message containing the HoA and IP host configuration options and sends the message to the DHCPproxy/Relay. The steps in the dashed box in fig. 7 are optional steps.
Or,
the MN sends a DHCPv6Solicit message; DHCP Proxy/Relay responds DHCPv6 advertisement message to MN; the MN responds to the DHCPv6Request message to the DHCP Proxy/Relay.
Steps 78-79 are performed.
Step 78-step 79.
For the case that the ASN/G-MS/G-RS supports PMIPv6 and CMIPv6 dual modes, the DHCPproxy/Relay informs the MIP mode adopted by the ASN Fn through R3_ Mobility _ Context message; if the ASN/G-MS/G-RS supports only PMIPv6, this step can be omitted;
PMIPv6Client extracts interface identifier (interface identifier) from LLA, attaches the interface identifier to the prefix broadcasted by the AR to CMIPv6 node, and generates CoA of MN;
the PMIPv6Client may also use the IP address of the AR as the CoA of the MN, i.e. different MNs of the PMIPv6Client proxy will use the same CoA, which may bring additional requirements to the HA, requiring that the HA cannot support CoA uniqueness checking on the MN.
Step 711-step 712.
After the DHCP Proxy/Relay obtains the HoA by the DHCPv6 or AAA method, the HoA is sent to the PMIPv6Client by the HoA Address private (source), and the HoA _ Address source contains the MN identifier (MAC Address).
Step 713-step 716, MIPv6 registration
After CoA generation and HoA acquisition of the MN, the PMIPv6Client can initiate MIPv6BU (registration message), and MIPv6BU includes the following information:
1. HoA of MN;
2. CoA of MN;
3. security services, such as MN-AAA authentication mobility options.
The HA responds to a binding confirmation message to the PMIPv6 Client;
wherein, the steps 714 to 715 are optional, and when the initial connection is established, after the PMIPv6Client sends the MIPv6 registration message to the HA, before the HA replies the binding confirmation message to the PMIPv6Client, the HA interacts with the H-AAA to acquire the MN-HA key and the PMIPv6 Client-HA key.
Step 717-step 718, DHCP reply:
after successful MIPv6 registration, PMIPv6Client sends DHCP _ gating.Release message, and then DHCP Proxy/Relay sends DHCPv6 Reply message to MN after R3 session is established; DHCP Gating is used to avoid the MN initiating IP communications before the end-to-end data path is established.
The process of establishing connection for the PMIPv6 user based on automatic configuration provided by the invention is shown in FIG. 8, wherein in a V-NSP scene of the HA, for an H-NSP scene of the HA, only the V-AAA in FIG. 8 needs to be removed.
The PMIPv6 user connection establishment procedure shown in fig. 8 includes the following steps:
and step 81, access authentication.
In the access authentication process, whether the network allocates the HoA to the MN is determined; PMIPv6Client obtains AAA key, HA address, HL prefix and HoA by performing AAA access authentication message interaction with H-AAA of MN (including MS or G-Host). The HoA of the MN is optional.
Step 82, automatically configuring the LLA and DAD.
Once a data path between the MN and the PMIPv6Client is established, the MN starts to carry out LLA automatic configuration; after the MN performs LLA automatic configuration, a Neighbor Solicitation message is initiated, DAD is performed on the LLA, and the Neighbor Solicitation message contains the tentative LLA.
PMIPv6Client supports Proxy DAD (Proxy DAD) of LLA, establishes and maintains Proxy MN IP Address Cache, PMIPv6Client can learn LLA of MN from Neighbor Solicitation message of MN; PMIPv6Client compares the addresses in the tentative LLA and the Address Cache; if the matching exists, the Proxy neighbor address notification message is sent instead of the matching address owner; if there is no match, then only the tentative LLA is added to the Address cache.
Step 83, HoA and CoA generation.
If the authenticator obtained the HoA of the MN in the above step 81, the PMIPv6Client obtains the HoA directly from the authenticator; otherwise, the PMIPv6Client extracts the interface identifier from the LLA, attaches the interface identifier to the HL prefix and generates the HoA of the MN;
PMIPv6Client extracts interface identifier from LLA, attaches the identifier to the prefix broadcasted by AR to CMIPv6 node, and generates CoA of MN;
the PMIPv6Client may also use the IP address of the AR as the CoA of the MN, i.e. different MNs of the PMIPv6Client proxy will use the same CoA, which may bring additional requirements to the HA, requiring that the HA cannot support CoA uniqueness checking on the MN.
Step 84-step 88, MIPv6 registration and proxy DAD.
After obtaining CoA and HoA of MN, PMIPv6Client can initiate MIPv6 registration message BU; MIPv6BU includes the following information:
1. HoA of MN;
2. CoA of MN;
3. security services, such as MN-AAA authentication mobility options. The HA needs Proxy DAD (Proxy DAD) to support HoA; after the HA replaces the MN to finish DAD, responding a binding confirmation message to the PMIPv6 Client;
and step 85-step 86, which is optional, when the initial connection is established, after the PMIPv6Client sends the MIPv6 registration message to the HA, before the HA responds to the binding confirmation message to the PMIPv6Client, the HA interacts with the H-AAA to acquire the MN-HA key and the PMIPv6 Client-HA key.
Step 89-step 810, router discovery.
The MN initiates an RS (router solicitation) message to request RA (router advertisement) message response of an AR where the PMIPv6Client is located so as to learn the on-link prefix; after the PMIPv6Client is successfully registered in the AR of the MIPv6 (the HoA passes through the Proxy DAD of the HA), an RA message carrying the HL prefix is sent to the MN, and the MN learns the HL prefix according to the RA message.
Or,
after finishing MIPv6 registration, the AR where the PMIPv6Client is located actively sends RA information carrying HL prefix to the MN, and the MN learns the HL prefix according to the RA information.
Step 811, automatically configure the HoA/DHCPv6 configuration.
The MN automatically configures the HoA according to the learned HL prefix; the MN may initiate a stateless DHCPv6 to obtain IP host configuration information.
According to the connection establishment process of the PMIPv6 user shown in fig. 8, another connection establishment process based on the automatically configured PMIPv6 user provided by the present invention is shown in fig. 9, and the connection establishment process of the user supports multiple hosts of a MIMAX system, where HA is in a V-NSP scenario, and for HA is in an H-NSP scenario, it only needs to remove V-AAA in fig. 9.
The process of establishing connection by the user shown in fig. 9 also includes steps 81 to 811 of the process of establishing connection by the PMIPv6 user shown in fig. 8, and in the process of establishing connection by the user shown in fig. 9, the G-MS/G-RS relays messages between the host device and the ASN, such as a request message for a Neighbor node IPv6Neighbor Solicitation, a Neighbor broadcast message Neighbor Advertisement, a Router request message Router Solicitation, or a Router broadcast message Router Advertisement. The relay is made to ensure the IP logic Link between the AR where the MN (G-Host) and the PMIPv6Client are located.
Another process for establishing a connection based on an automatically configured PMIPv6 user according to the present invention is shown in fig. 10, and supports the case where PMIPv6Client CP and PMIPv6Client DP are separated.
The PMIPv6 user connection establishment procedure shown in fig. 10 includes the following steps:
In the access authentication process, whether the network allocates the HoA to the MN is determined; PMIPv6Client obtains AAA key, HA address, HL prefix and HoA by performing AAA access authentication message interaction with H-AAA of MN (including MS or G-Host). The HoA of the MN is optional.
Step 102, automatically configuring the LLA and the DAD.
Once a data path between the MN and the PMIPv6Client DP is established, the MN starts to carry out LLA automatic configuration; after the MN performs LLA automatic configuration, a Neighbor Solicitation message is initiated, DAD is performed on the LLA, and the Neighbor Solicitation message contains the tentative LLA.
PMIPv6Client DP supports Proxy DAD of LLA, establishes and maintains Proxy MN IP Address Cache, PMIPv6Client DP can learn MN LLA from MN NeighborSolitization message; PMIPv6Client DP compares the addresses in latent LLA and Address cache; if there is a match, sending a ProxyNeighbor Advertisements message instead of the matching address owner; if there is no match, then only the tentative LLA is added to the Address Cache.
Step 103, HoA and CoA generation.
PMIPv6Client DP extracts the interface identifier from LLA, and attaches the identifier to the prefix broadcasted by the AR to the CMIPv6 node to generate CoA of MN;
the PMIPv6Client DP may also use the IP address of the AR where the Client DP is located as the CoA of the MN, i.e. different MNs of the PMIPv6Client DP proxy will use the same CoA, which may bring additional requirements to the HA, requiring that the HA cannot support CoA uniqueness checking on the MN.
PMIPv6Client DP sends registration start message to PMIPv6Client CP, the registration start message includes CoA or LLA of MN.
If the HoA is given by the Authenticator, the PMIPv6Client DP can be directly used; otherwise, PMIPv6Client DP extracts the interface identifier from CoA or LLA, attaches it after HL prefix, and generates HoA of MN.
Step 104-step 108, MIPv6 registration and proxy DAD.
After CoA generation and HoA acquisition of the MN, the PMIPv6Client CP may initiate a MIPv6 registration message BU; MIPv6BU includes the following information:
1. HoA of MN;
2. CoA of MN;
3. security services, such as MN-AAA authentication mobility options.
The HA needs Proxy DAD (Proxy DAD) to support HoA; after the HA replaces the MN to finish DAD, responding a binding confirmation message to the PMIPv6Client CP;
step 109, the PMIPv6Client CP sends a registration success message to the PMIPv6Client DP, and notifies the PMIPv6 that the Client DP is successfully registered, where the registration success message includes the HL prefix.
Step 1010-step 1011, router discovery.
The MN initiates an RS (router solicitation) message, requests RA (router advertisement) message response of an AR where PMIPv6Client DP is located, so as to learn on-link prefix; after the PMIPv6 AR where the Client DP is located successfully registers in the MIPv6 (the HoA passes through the Proxy DAD of the HA), the RA schottky barrier carrying the HL prefix is sent to the MN, and the MN learns the HL prefix according to the RA schottky barrier.
Or,
after finishing MIPv6 registration, the AR where the PMIPv6Client DP is located actively sends RA messages carrying HL prefix to the MN, and the MN learns the HL prefix according to the RA messages.
Step 1012, automatically configuring the HoA/DHCPv6 configuration.
The MN automatically configures the HoA according to the learned HL prefix; the MN may initiate a stateless DHCPv6 to obtain IP host configuration information.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (39)
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100796454A CN101064648A (en) | 2006-04-30 | 2006-04-30 | System for realizing mobile IPv6 and its method for establishing user connection |
| PCT/CN2007/001478 WO2007128239A1 (en) | 2006-04-30 | 2007-04-29 | System for implementing mobile ipv6 and method for establishing user link in the system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100796454A CN101064648A (en) | 2006-04-30 | 2006-04-30 | System for realizing mobile IPv6 and its method for establishing user connection |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101064648A true CN101064648A (en) | 2007-10-31 |
Family
ID=38667445
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006100796454A Pending CN101064648A (en) | 2006-04-30 | 2006-04-30 | System for realizing mobile IPv6 and its method for establishing user connection |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101064648A (en) |
| WO (1) | WO2007128239A1 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010017724A1 (en) * | 2008-08-11 | 2010-02-18 | 华为技术有限公司 | Method and apparatus for assisting relocation of mobile access gateway |
| CN102387063A (en) * | 2010-08-30 | 2012-03-21 | 中兴通讯股份有限公司 | Processing method and system during internet protocol flow migration (IFOM) error |
| WO2012159518A1 (en) * | 2011-05-26 | 2012-11-29 | 中兴通讯股份有限公司 | Method and system for acquiring e-srvcc stn-sr |
| WO2013026295A1 (en) * | 2011-08-24 | 2013-02-28 | 中兴通讯股份有限公司 | System and method for node communication between proxy mobile ip domains |
| CN103002064A (en) * | 2012-11-20 | 2013-03-27 | 中兴通讯股份有限公司 | Method, user node and remote access server for releasing address |
| US8594103B2 (en) | 2008-03-26 | 2013-11-26 | Huawei Technologies Co., Ltd. | Network access method, authentication method, communications systems and relevant devices |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100885748B1 (en) * | 2007-08-07 | 2009-02-26 | 포스데이타 주식회사 | Method and apparatus for supporting MIP6 service in wireless communication network |
| CN102761425B (en) * | 2012-07-20 | 2018-06-12 | 中兴通讯股份有限公司 | Charging method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7840217B2 (en) * | 2004-07-23 | 2010-11-23 | 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 (en) * | 2004-10-08 | 2006-04-20 | Yaskawa Information Systems Co Ltd | MobileIPv6 network system and communication method therefor, router device, MobileNode, and recording medium |
-
2006
- 2006-04-30 CN CNA2006100796454A patent/CN101064648A/en active Pending
-
2007
- 2007-04-29 WO PCT/CN2007/001478 patent/WO2007128239A1/en not_active Ceased
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8594103B2 (en) | 2008-03-26 | 2013-11-26 | Huawei Technologies Co., Ltd. | Network access method, authentication method, communications systems and relevant devices |
| US8925067B2 (en) | 2008-03-26 | 2014-12-30 | Huawei Technologies Co., Ltd | Network access authentication |
| US9467447B2 (en) | 2008-03-26 | 2016-10-11 | Huawei Technologies Co., Ltd. | Network access method, authentication method, communications system and relevant devices |
| WO2010017724A1 (en) * | 2008-08-11 | 2010-02-18 | 华为技术有限公司 | Method and apparatus for assisting relocation of mobile access gateway |
| CN102387063A (en) * | 2010-08-30 | 2012-03-21 | 中兴通讯股份有限公司 | Processing method and system during internet protocol flow migration (IFOM) error |
| CN102387063B (en) * | 2010-08-30 | 2015-10-21 | 中兴通讯股份有限公司 | Processing method during a kind of IFOM mistake and system |
| WO2012159518A1 (en) * | 2011-05-26 | 2012-11-29 | 中兴通讯股份有限公司 | Method and system for acquiring e-srvcc stn-sr |
| WO2013026295A1 (en) * | 2011-08-24 | 2013-02-28 | 中兴通讯股份有限公司 | System and method for node communication between proxy mobile ip domains |
| CN102958039A (en) * | 2011-08-24 | 2013-03-06 | 中兴通讯股份有限公司 | Method and system for proxy mobile IP (internet protocol) inter-domain node communication |
| CN102958039B (en) * | 2011-08-24 | 2018-03-06 | 中兴通讯股份有限公司 | A kind of proxy-mobile IP domain intermediate node communication system and method |
| CN103002064A (en) * | 2012-11-20 | 2013-03-27 | 中兴通讯股份有限公司 | Method, user node and remote access server for releasing address |
| US10050932B2 (en) | 2012-11-20 | 2018-08-14 | Zte Corporation | Method, user node and remote access server for releasing address |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2007128239A1 (en) | 2007-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1262090C (en) | System for managing mobile nodes in mobile network | |
| CN200947608Y (en) | Multi-stack wireless transmission/receiving units for performing media independent delivery | |
| CN1298148C (en) | Micro mobile network route system and method | |
| CN1640074A (en) | Mobile management method and mobile terminal | |
| CN1817013A (en) | Terminal and communication system | |
| CN101043411A (en) | Method and system for realizing mobile VPN service in hybrid network | |
| CN101053233A (en) | Method and system for controlling mobility in a communication network, and related network and computer program products | |
| CN1943211A (en) | Framework of media-independent pre-authentication | |
| CN1774889A (en) | Arrangement for IPv6 Mobile Nodes Traversing IPv4 Networks | |
| CN1531263A (en) | Communication system, connection device, communication method, and authentication method | |
| CN1481081A (en) | virtual private network system | |
| CN1486094A (en) | Method and device for mobile communication using load balancing | |
| CN101060491A (en) | Mobile terminal, control apparatus, home agent and packet communications method | |
| CN1853384A (en) | Mobile communication method, mobile communication apparatus, home agent apparatus, access router information server apparatus, and mobile communication system | |
| CN1863145A (en) | Method for correcting service quality in interworking WLAN | |
| CN101064938A (en) | Method for applying MIP when the mobile terminal switched between 3GPP and non-3GPP access system | |
| CN1741523A (en) | Key exchange protocol method for realizing main machine transferability and multi-home function | |
| CN1659830A (en) | Method and device for routing optimization in nested mobile network | |
| CN101064866A (en) | Method and system for routing address of short message | |
| CN1960566A (en) | Evolution mobile communication network, method for managing mobility between 3GPP and non-3GPP access network | |
| CN101064648A (en) | System for realizing mobile IPv6 and its method for establishing user connection | |
| CN1816171A (en) | Mobile node, base station, router and packet communication system | |
| CN101043737A (en) | Terminal and terminal switching method and system | |
| CN1961537A (en) | Communication system, mobile terminal and access router | |
| CN101047977A (en) | Radio communication system and method and call method used in the system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |