CN102647708A - Distributive mobile IPv6 method based on network mobile management and routing optimization - Google Patents
Distributive mobile IPv6 method based on network mobile management and routing optimization Download PDFInfo
- Publication number
- CN102647708A CN102647708A CN2012101012986A CN201210101298A CN102647708A CN 102647708 A CN102647708 A CN 102647708A CN 2012101012986 A CN2012101012986 A CN 2012101012986A CN 201210101298 A CN201210101298 A CN 201210101298A CN 102647708 A CN102647708 A CN 102647708A
- Authority
- CN
- China
- Prior art keywords
- address
- maar
- session
- mobile
- message
- 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
Abstract
The invention relates to a distributive mobile IPv6 method based on network mobile management and routing optimization. The method provided by the invention simultaneously realizes three goals that: 1, a distributive network entity takes part in the mobile management work for mobile users, and the mobile users do not need to take part in the mobile management work; 2, the transparency of the moving of the mobile users to the opposite conversation side is realized; and 3, the routing optimization is realized, i.e. the two conversation sides can be directly communicated through an access router, and the communication through going to other access routers is not needed. The goals of the invention are realized through the following ways that the storage information in an AAA server is expanded, the concept of family address and forwarding address is redefined, four message formats and two mobile options respectively carrying the opposite conversation side family address and the opposite conversation side current access router address are defined, and the updating and communication flow process is made again.
Description
Technical field
The present invention relates to the communications field, be specifically related to the distributed mobile IP v 6 method of a kind of mobile management Network Based and routing optimality.
Background technology
Internet and mobile communication are two industries the most noticeable in world today's message area.At any time, any place, people hope to obtain Internet service, so just produced technology-mobile IP (MIP) that Internet is combined with mobile communication.The MIP technology is mobile node (MN just; Be commonly referred to as computer or router etc.) with fixed IP addresses or IP address prefix; Realize crossing over the roaming function of different segment, and guarantee that the network legal power of network IP can not change in roam procedure, as shown in Figure 1.
MIP is one of Internet main application of carrying, and wherein the MIP that carried of IPv4 network is called MIPv4, and the MIP that the IPv6 network is carried is called MIPv6.At present, IETF mainly contains mobile IP v 6 (Mobile IPv6, MIPv6 to the research of MIPv6; RFC3775, RFC6275), proxy mobile IPv 6 (Proxy Mobile IPv6, PMIPv6; RFC5213), layered mobile IPv 6 (Hierarchical Mobile IPv6, HMIPv6 is RFC5380) with two stack mobile IP v 6 (Dual-Stack Mobile IPv6; DSMIPv6, RFC5454, RFC5555) etc.The network design of these MIP all is centralized.Central entity in the network (HA/LMA/MAP) will be distributed to IP address of MN or address prefix, and this address or address prefix all remain unchanged when MN moves, thereby realizes the continuity of IP session.
This centralized mobile management scheme exists deficiency and limitation, mainly shows following aspect:
(1) phenomenon that exists route not optimize.If MN and Correspondent Node (CN) all compare near couple in router, yet the data message that sends between them must pass through the forwarding through central entity.Make route not optimize like this, the time-delay that has also improved network simultaneously;
(2) central entity is not only kept the relevant context of MN, but also will have the ability of encapsulation or decapsulation to the related data message of MN.When the scale expansion of network, the increase of MN and CN quantity, the data message between MN and the CN all needs the processing of this central entity, and central entity will can't bear the heavy load;
(3) receive the influence of single point failure easily, lack the granularity of mobile management service.If this central entity lost efficacy or restarted, then the communication disruption between MN and the CN influences service quality.
In order to address the above problem, IETF is incorporated into the notion of " distributed " among the MIP.In the mobile network, distributed mobile management can be applied on mobile core network, Access Network and the main frame, and is as shown in Figure 2.In mobile core network, two kinds of distributed management method of mobile can be arranged, a distributed management method of mobile that is based on core aspect (being HA/LMA), another is based on the distributed management method of mobile of couple in router aspect (being AR/FA/MAG).In the distributed management method of mobile based on the core aspect, when MN when a HA or LMA switch to another HA or LMA, these two HA or LMA need set up corresponding contact, guarantee not interrupting of session.In Access Network, has only a kind of distributed management method of mobile, promptly based on the distributed management method of mobile of access aspect (be AP, and have the function of part A R).In the Host Based distributed management method of mobile, MN can directly communicate by letter with CN, but need be by domain name analysis system (DNS).
At present, IETF is the elementary step also for the research of distributed MIP, does not have perfect solution, does not also have relevant RFC.For in distributed management method of mobile, routing optimality reduces time-delay better, does not mention especially.
According to above-mentioned situation, this paper proposes the distributed mobile IP v 6 method of a kind of mobile management Network Based and routing optimality.During this method makes that MN moves, do not need the processing of local mobility anchor with communicating by letter between original CN.MN takes the mode of routing optimality and original CN to communicate, and alleviates the burden of local mobility anchor better, and MN need not participate in the work of any mobile management simultaneously, guarantees the transparency to CN that moves of MN again.
Summary of the invention
The method that the purpose of this invention is to provide the distributed MIPv6 of a kind of mobile management Network Based and routing optimality.This side's method has three characteristics: the first, the work of network mobility management is responsible for by network entity, and the mobile subscriber does not participate in the work of mobile management; The second, moving of mobile subscriber has the transparency to session the other side; Three, routing optimality, promptly the session both sides pass through the router direct communication that inserted, other couple in router communications of needn't detouring.The objective of the invention is to realize like this:
1, MAAR is based on the network entity of the distributed MIPv6 of network mobility management and routing optimality.MAAR has the function of mobility anchor and couple in router concurrently.A network can have a plurality of MAAR, the user is born the task of access and mobile management.MAAR distributes an IPv6 address or address prefix can for the new user who inserts.In the present invention, MAAR distributes a unique and routable IPv6 address for the new user who inserts.
2, the aaa server of MN always writes down the address of the MAAR of the current access of MN.
3, home address and Care-of Address no longer are directed against MN, but are directed against the session between the MN:
● the MAAR that the MN of initiation session is inserted during initial initiation session for its configured address as the MN of initiation session home address to this session, the MN of initiation session is the MAAR of current access its configured address is directed against this session as the MN of initiation session a Care-of Address;
● the MAAR that the MN that accepts session is inserted when initially accepting session for its configured address as the home address of the MN that accepts session to this session, the MN that accepts session is the MAAR of current access its configured address is directed against this session as the MN that accepts session a Care-of Address.
No matter how the MN of initiation session and the MN that accepts session move between session, with regard to this session, home address all is immovable, and just Care-of Address is changing.The data message of the MN of initiation session and the MN that accepts session transmission, destination address all is the home address of session opposite end forever, source address all is the home address of oneself forever.
4, the working rules of MAAR are following:
● MAAR keeps two address binding tables: " tunnel address binding table " and " Care-of Address binding table ".The address binding of " tunnel address binding table " lining is the binding of MAAR address of session the other side's home address access current with it, and the address binding of " Care-of Address binding table " lining is the binding of session one's own side's home address and Care-of Address.
● MAAR is for the MN data sent message that is inserted; The address of at first in " tunnel address binding table ", searching session the other side's MAAR according to destination address (being session the other side's home address), the tunnel between the MAAR through MN and session the other side's the MAAR mails to data message session the other side's MAAR then.
● MAAR at first searches session one's own side's Care-of Address according to destination address (being session one's own side's home address) for through tunnel data sent message in " Care-of Address binding table ", issue corresponding M N to data message according to Care-of Address then.
5, two types of DBU/DBA message
In RFC6275, defined 8 kinds of message altogether, the MH type is respectively 0～7; The present invention has defined two new MH types in order to differentiate with centralized motion management method, is respectively 8 and 9; With type is that 8 message is called DBU message, and type is that 9 message is called DBA message.In RFC6275, defined 6 types of mobile options, its type is respectively 0～5, and the present invention defines two new mobile options, and type is respectively 6 and 7 (specifically adopt what types value will pass through relevant departments and examine, adopt 6 and 7 earlier here).Form such as Fig. 3 and shown in Figure 4 of two mobile options of the present invention's definition.Moreover, the present invention adds identifier D with reference to definition message format among the relevant RFC (RFC6275 etc.).
If D=0 representes that then DBU/DBA message is the MAAR of the current access of MN and the mutual information of MAAR that MN inserts before, purpose is the address that obtains the MAAR of the current access of session the other side; If D=1 representes that then DBU/DBA message is interactive messages between the MAAR of MAAR and the current access of session the other side of the current access of MN, the relative address that is used for " tunnel address binding table " that the MAAR of the more current access of new session the other side keeps is bound.For this reason, DBU/DBA message will be done corresponding expansion, to load these information.For the convenience of narrating, the DBU/DBA message during with D=0 is called first kind DBU/DBA message, and respectively like Fig. 5 and as shown in Figure 6, the DBU/DBA message during D=1 is called second type of DBU/DBA message, respectively like Fig. 7 and as shown in Figure 8.
6, the flow process of mobile management
In order to narrate conveniently, we suppose that user A_MN sets up session through A_MAAR1 and user B_MN at first, and B_MN accepts the session of A_MN at first through B_MAAR1.A_MAAR1 is A_HoA1 for the A_MN addresses distributed, and B_MAAR1 is B_HoA1 for the B_MN addresses distributed.Afterwards, A_MN moved to A_MAAR2, and A_MAAR2 is A_HoA2 for the A_MN addresses distributed, and B_MN moves to B_MAAR2, and B_MAAR2 is B_HoA2 for the B_MN addresses distributed.At this moment, A_MAAR2 " tunnel address binding table " kept the binding of B_HoA1 and B_MAAR2 address, and " Care-of Address binding table " kept the binding of A_HoA1 and A_HoA2; B_MAAR2 " tunnel address binding table " kept the binding of A_HoA1 and A_MAAR2 address, and " Care-of Address binding table " kept the binding of B_HoA1 and B_HoA2.Now, A_MN moves to A_MAAR3 again, and mobile management flow process of the present invention is following:
6.1, new technological process more
(1) A_MN inserts A_MAAR3 through RS message, comprises session both sides' home address A_HoA1 and B_HoA1 in the RS message.
(2) after A_MAAR3 received RS message, to the aaa server transmission authentication message of A_MN, message comprised the address of A_MAAR3.
(3) after the aaa server of A_MN is received authentication message, carry out authentication.Authentication is passed through, and the aaa server of A_MN is with the address of the original A_MAAR2 of address substitution of A_MAAR3, and in replying message, comprises the address of A_MAAR2.
(4) after A_MAAR3 receives and replys message, send first kind DBU message to A_MAAR2, message comprises A_HoA1 and B_HoA1.
(5) after A_MAAR2 receives first kind DBU message; In " tunnel address binding table ", search the binding of B_HoA1 and B_MAAR2 address and eliminate this binding according to B_HoA1; In " Care-of Address binding table ", check and accept the binding of A_HoA1 and A_HoA2 and eliminate this binding according to A_HoA1; Reply first kind DBA message to A_MAAR3 then, comprise the address of B_MAAR2 in the message.
(6) after A_MAAR3 receives the first kind DBA message of answer; The binding of at first in " tunnel address binding table ", setting up B_HoA1 and B_MAAR2 address; Distribute address A_HoA3 for A_MN then; And the binding of in " Care-of Address binding table ", setting up A_HoA1 and A_HoA3, send second type of DBU message to B_MAAR2 at last, message comprises A_HoA1.
(7) after B_MAAR2 receives second type of DBU message, in " tunnel address binding table ", search the binding of A_HoA1 and A_MAAR2 address, and change to the A_MAAR3 address to the A_MAAR2 address, reply second type of DBA message to A_MAAR3 then according to A_HoA1.
(8) after A_MAAR3 receives second type of DBA message, inform A_MN to the A_HoA3 address through RA message.If A_MN initiates through A_MAAR3 or accepts new session, will use the home address of A_HoA3 as new session.
6.2, communication process
6.2.1, A_MN mails to the data message of B_MN
(1) A_MN mails to the data message of B_MN, and as before, destination address is B_HoA1, and source address is A_HoA1.A_MAAR3 mails to B_MAAR2 to data message through the tunnel between A_MAAR3 and the B_MAAR2 then according to destination address B_HoA1 searches B_HoA1 and B_MAAR2 address in " tunnel address binding table " binding.
(2) after B_MAAR2 received tunnel data sent message, at first according to destination address B_HoA1, the binding of in " Care-of Address binding table ", searching B_HoA1 and B_HoA2 was then issued B_MN to data message according to B_HoA2 then.
6.2.2, B_MN mails to the data message of A_MN
(1) B_MN mails to the data message of A_MN, and as before, destination address is A_HoA1, and source address is B_HoA1.B_MAAR2 mails to A_MAAR3 to data message through the tunnel between B_MAAR2 and the A_MAAR3 then according to destination address A_HoA1 searches A_HoA1 and A_MAAR3 address in " tunnel address binding table " binding.
(2) after A_MAAR3 received tunnel data sent message, at first according to destination address A_HoA1, the binding of in " Care-of Address binding table ", searching A_HoA1 and A_HoA3 was then issued A_MN to data message according to A_HoA3 then.
Description of drawings
Fig. 1 moves the network structure of IP
Fig. 2 distributed network structure figure
Being used to of Fig. 3 the present invention definition carried the mobile option sketch map of session the other side's IPv6 address
Being used to of Fig. 4 the present invention definition carried the mobile option sketch map of address of the MAAR of the current access of session the other side
Fig. 5 first kind DBU message format sketch map
Fig. 6 first kind DBA message format sketch map
Second type of DBU message format of Fig. 7 sketch map
Second type of DBA message format of Fig. 8 sketch map
Fig. 9 communication process sketch map of the present invention
Figure 10 sketch map of the present invention
Embodiment
The present invention proposes the distributed mobile IP v 6 method of a kind of mobile management Network Based and routing optimality.Provide an instance of the present invention below, and combine Figure 10 to specify practical implementation instance of the present invention.
Here suppose that user A_MN sets up session through A_MAAR1 and user B_MN at first, and user B_MN sets up session through B_MAAR1 and user A_MN at first.Afterwards, A_MN moved to A_MAAR2, and A_MAAR2 is A_HoA2 for the A_MN addresses distributed, and B_MN moves to B_MAAR2, and B_MAAR2 is B_HoA2 for the B_MN addresses distributed.At this moment, A_MAAR2 " tunnel address binding table " kept the binding of B_HoA1 and B_MAAR2 address, and " Care-of Address binding table " kept the binding of A_HoA1 and A_HoA2; B_MAAR2 " tunnel address binding table " kept the binding of A_HoA1 and A_MAAR2 address, and " Care-of Address binding table " kept the binding of B_HoA1 and B_HoA2.
We are provided with as follows:
The address of A_MAAR1 is aec0:0:0:1::1/64; The address of A_MAAR2 is bec0:0:0:1::1/64, and the address of A_MAAR3 is cec0:0:0:1::1/64, and A_HoA1 is aec0:0:0:1::2/64; A_HoA2 is bec0:0:0:1::2/64, and A_HoA3 is cec0:0:0:1::2/64.
The address of B_MAAR1 is dec0:0:0:1::1/64, and the address of B_MAAR2 is eec0:0:0:1::1/64, and B_HoA1 is dec0:0:0:1::2/64, and B_HoA2 is eec0:0:0:1::2/64.
1, present, user A_MN moves to A_MAAR3 again, and renewal process is following:
(1) user A_MN leaves A_MAAR2, when inserting A_MAAR3, sends RS message to A_MAAR3, and this message comprises the A_HoA1 of user A_MN and the B_HoA1 of user B_MN;
(2) A_MAAR3 sends authentication message to aaa server, and message comprises the address of A_MAAR3;
(3) AAA carries out authentication after receiving authentication message, the address that authentication is replaced A_MAAR2 through the back with the address of A_MAAR3, and, comprise the address information of A_MAAR2 to A_MAAR3 transmission authentication response message;
(4) after A_MAAR3 receives authentication response message, send first kind DBU message to A_MAAR2, message comprises A_HoA1 and B_HoA1;
(5) A_MAAR2 searches the address binding of B_HoA1 and B_MAAR2 according to B_HoA1 and eliminates and bind in " tunnel address binding table "; In " Care-of Address binding table ", search the binding of A_HoA1 and A_HoA2 and eliminate binding according to A_HoA1; Reply first kind DBA message to A_MAAR3 then, comprise the address of B_MAAR2 in the message;
(6) A_MAAR3 receives first kind DBA message; The binding of at first in " tunnel address binding table ", setting up B_HoA1 and B_MAAR2 address; Distribute new address A_HoA3 for user A_MN then; And the binding of in " Care-of Address binding table ", setting up A_HoA1 and A_HoA3, send second type of DBU message to B_MAAR2 at last, comprise A_HoA1.
(7) B_MAAR2 receives second type of DBU message, in " tunnel address binding table ", searches the binding of A_HoA1 and A_MAAR2 address according to A_HoA1, and changes to the address of A_MAAR3 with the address of A_MAAR2, replys second type of DBA message to A_MAAR3 then.
(8) A_MAAR3 receives second type of DBA message, through RA message A_HoA3 is sent to user A_MN.
2, user A_MN and user B_MN communicate process
2.1, user A_MN mails to the data message of user B_MN
(1) user A_MN sends to the data message of user B_MN, and destination address all is B_HoA1 forever, and source address is all to be A_HoA1 forever.When such data message arrived the A_MAAR3 of A_MN access, A_MAAR3 searched " tunnel address binding table " according to B_HoA1 and learns the binding of B_HoA1 and B_MAAR2 address, and the tunnel through A_MAAR3 and B_MAAR2 mails to B_MAAR2 then;
(2) B_MAAR2 receives such data message, searches " Care-of Address binding table " according to destination address B_HoA1, learns the binding of B_HoA1 and B_HoA2, and data message is sent to user B_MN.
2.2, user B_MN mails to the data message of user A_MN
(1) user B_MN sends to the data message of user A_MN; Destination address all is A_HoA1 forever; Source address all is B_HoA1 forever; When such data message arrived the B_MAAR2 of B_MN access, B_MAAR2 searched " tunnel address binding table " according to A_HoA1 and learns the binding of A_HoA1 and A_MAAR3 address, mail to A_MAAR3 through the tunnel between B_MAAR2 and the A_MAAR3 then;
(2) A_MAAR3 receives such data message, searches " Care-of Address binding table " according to destination address A_HoA1, learns the binding of A_HoA1 and A_HoA3, and data message is sent to user A_MN.
Claims (4)
1. the distributed mobile IP v 6 method of mobile management Network Based and routing optimality is characterized in that:
A, MAAR are based on the network entity of the distributed MIPv6 of network mobility management and routing optimality; Have the function of mobility anchor and couple in router concurrently; The mobile subscriber is born the task of access and mobile management; And for the new mobile subscriber who inserts distributes an IPv6 address or address prefix, in the present invention, MAAR distributes a unique and routable IPv6 address for the new mobile subscriber who inserts;
B, aaa server always can write down the address of the MAAR of the current access of mobile subscriber; When the mobile subscriber switches to new MAAR from old MAAR; The address that aaa server is used new MAAR replaces the address of old MAAR, and informs the address of old MAAR to new MAAR;
C, home address and Care-of Address are no longer to the mobile subscriber, but to the session between the mobile subscriber, no matter the how many times switching takes place between session the session both sides, the home address of session is constant, and just Care-of Address changes;
D, with the extension of message in the mobile IP v 6; Definition MH type is 8 and 9 message, is called DBU and DBA message respectively, defines two kinds of new mobile options simultaneously; The mobile option types value is respectively 6 and 7, is used to carry the address of MAAR of session the other side's home address and the current access of session the other side;
The task of E, mobile management is mainly born by MAAR, and the user no longer bears the task of any mobile management, follows three principles simultaneously: the first, the work of network mobility management is responsible for by network entity, and the mobile subscriber does not participate in the work of mobile management; The second, moving of mobile subscriber has the transparency to session the other side; Three, routing optimality, i.e. the router direct communication of session both sides through inserting separately.
2. method according to claim 1 is characterized in that said step C specifically comprises:
The MAAR that C1, the initial initiation of mobile subscriber are inserted when perhaps accepting a session is directed against the home address of this session as the mobile subscriber for its configured address; When the mobile subscriber switched to new MAAR from old MAAR, new MAAR was that its configured address is as the Care-of Address of mobile subscriber to original session;
Switch no matter how many times takes place between session the C2 mobile subscriber, the data message source address that the mobile subscriber sends to session the other side all is the home address of oneself forever, and destination address all is the home address of session opposite end forever.
3. method according to claim 1 is characterized in that said step D specifically comprises:
D1, adopt the DBU/DBA of new MH types value; And with reference to the BU/BA message format that defines in the mobile IP v 6; Add identifier D, if D=0 representes that then DBU/DBA message is the mutual information of MAAR of access before the MAAR of the current access of mobile subscriber switches with the mobile subscriber; If D=1; Represent that then DBU/DBA message is interactive messages between the MAAR of MAAR and the current access of session the other side of the current access of mobile subscriber, will before a kind of DBU/DBA message be called first kind DBU/DBA message, the latter is called second type of DBU/DBA message;
D2, first kind DBU/DBA message; Three effects are arranged: the one, be that the home address that 6 mobile option carries is searched " tunnel address binding table " according to type; The MAAR of original record, the relevant current access of information feedback mobile subscriber and eliminate this binding with session the other side; The 2nd, the mobile subscriber's of carrying according to home address option in the message home address is searched and is bound and eliminate this binding in " Care-of Address binding table " accordingly, and the 3rd, in the MAAR of the current access of mobile subscriber, set up by " tunnel address binding table "; " the tunnel address binding table " that the MAAR that second type of DBU/DBA message is used for the more current access of new session the other side keeps;
D3, in first kind DBU message, to add a home address option and types value be 6 mobile option; Carry mobile subscriber's home address and session the other side's home address respectively, in the first kind DBA message, adding a types value is that 6 and types values are 7 mobile option; The address of corresponding respectively carrying session the other side's the home address and the MAAR of the current access of session the other side; Second type of DBU message is added a home address option, is used to carry mobile subscriber's home address.
4. method according to claim 1 is characterized in that said step e specifically comprises:
The MAAR of E1, the current access of mobile subscriber safeguards two address binding tables: " tunnel address binding table " and " Care-of Address binding table "; The address binding of " tunnel address binding table " lining is the binding of MAAR address of session the other side's home address access current with it, and the address binding of " Care-of Address binding table " lining is the binding of session one's own side's home address and Care-of Address;
E2, MAAR are for the mobile subscriber's data sent message that inserts; The address of at first in " tunnel address binding table ", searching session the other side's MAAR according to destination address (being session the other side's home address), the tunnel between the MAAR through this mobile subscriber and session the other side's the MAAR mails to data message session the other side's MAAR then;
E3, MAAR are for passing through tunnel data sent message; At first in " Care-of Address binding table ", search session one's own side's Care-of Address, issue the corresponding mobile user to data message according to Care-of Address then according to destination address (being session one's own side's home address).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101012986A CN102647708A (en) | 2012-04-06 | 2012-04-06 | Distributive mobile IPv6 method based on network mobile management and routing optimization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101012986A CN102647708A (en) | 2012-04-06 | 2012-04-06 | Distributive mobile IPv6 method based on network mobile management and routing optimization |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102647708A true CN102647708A (en) | 2012-08-22 |
Family
ID=46660244
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012101012986A Pending CN102647708A (en) | 2012-04-06 | 2012-04-06 | Distributive mobile IPv6 method based on network mobile management and routing optimization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102647708A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102938919A (en) * | 2012-11-15 | 2013-02-20 | 北京邮电大学 | Selectable route optimization method of distributed mobile management |
| CN113923593A (en) * | 2021-10-12 | 2022-01-11 | 南京信息工程大学 | On-demand distributed edge node mobility management method |
-
2012
- 2012-04-06 CN CN2012101012986A patent/CN102647708A/en active Pending
Non-Patent Citations (1)
| Title |
|---|
| ZHENGMING MA,XUN ZHANG: "A Route Optimization solution support for Distributed Mobility Management", 《DISTRIBUTED MOBILITY MANAGEMENT INTERNET-DRAFT IETF》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102938919A (en) * | 2012-11-15 | 2013-02-20 | 北京邮电大学 | Selectable route optimization method of distributed mobile management |
| CN102938919B (en) * | 2012-11-15 | 2016-03-30 | 北京邮电大学 | The routing optimization method of selectable distributed mobile management |
| CN113923593A (en) * | 2021-10-12 | 2022-01-11 | 南京信息工程大学 | On-demand distributed edge node mobility management method |
| CN113923593B (en) * | 2021-10-12 | 2023-10-27 | 南京信息工程大学 | On-demand distributed edge node mobile management method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Zhu et al. | A survey of mobility support in the Internet | |
| Das et al. | IDMP: An intradomain mobility management protocol for next-generation wireless networks | |
| CN100574503C (en) | A kind of terminal and terminal switching method and system | |
| JP4794520B2 (en) | System, access gateway, home agent, and program for optimizing communication path in network-driven mobility management protocol | |
| Shin et al. | Distributed mobility management for efficient video delivery over all-IP mobile networks: Competing approaches | |
| Gladisch et al. | Survey on mobility and multihoming in future internet | |
| US20100220738A1 (en) | Apparatus and Method for Route Optimization for Proxy Mobile Internet Protocol Version Six Local Routing | |
| CN102256236A (en) | System and method for mobility management under separate mapping mechanism | |
| CN100505686C (en) | Method for implementing communication of mobile IPv6 node and IPv4 communication buddy | |
| Luo et al. | An approach for building scalable proxy mobile IPv6 domains | |
| Wozniak | Mobility management solutions for current IP and future networks | |
| Yan et al. | Network mobility support in PMIPv6 network | |
| JPWO2009101780A1 (en) | POSITION INFORMATION MANAGEMENT DEVICE, NETWORK EDGE DEVICE, AND MOBILE TERMINAL | |
| Leung et al. | Proxy mobile ipv6 | |
| CN101147366A (en) | Mobile communication system, edge router, mobile management method used in them, program and recording medium | |
| Giust et al. | HDMM: deploying client and network-based distributed mobility management: A hybrid approach | |
| CN102647708A (en) | Distributive mobile IPv6 method based on network mobile management and routing optimization | |
| De La Oliva et al. | The costs and benefits of combining different IP mobility standards | |
| CN102612169A (en) | Distributed mobile IPv6 (Internet Protocol version 6) method based on network mobility management and non-routing optimization | |
| Zhu et al. | Rfc 6301: A survey of mobility support in the internet | |
| Condeixa et al. | Centralized, distributed or replicated IP mobility? | |
| CN105764041B (en) | A kind of IPv6 method of mobile communication based on name data network coating | |
| Hong et al. | Analysis of the usage of a logical interface in PMIPv6 | |
| Muslam et al. | Distributed mobility management with mobile Host Identity Protocol proxy | |
| Leiter et al. | Survey on pmipv6-based mobility management architectures for software-defined networking |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20120822 |