CN1863375A - Registering method of mobile node to communication node in mobile IPv6 standard - Google Patents
Registering method of mobile node to communication node in mobile IPv6 standard Download PDFInfo
- Publication number
- CN1863375A CN1863375A CNA2005100691405A CN200510069140A CN1863375A CN 1863375 A CN1863375 A CN 1863375A CN A2005100691405 A CNA2005100691405 A CN A2005100691405A CN 200510069140 A CN200510069140 A CN 200510069140A CN 1863375 A CN1863375 A CN 1863375A
- Authority
- CN
- China
- Prior art keywords
- mobile node
- node
- mobile
- address
- communication
- 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.)
- Granted
Links
Images
Abstract
This invention discloses a method for registering mobile nodes to communication nodes in IPv6 standard in the communication field, in which, the mobile node generates a temporary multicast address for managing all communication nodes, when the communication node communicates with the mobile node, it computes a corresponding multicast address in terms of the rule and asks to join in the multicast set, the mobile node accesses the network of other places to register to the home town agent, which feeds back the binding confirmation and the mobile node sends the binding refreshed message to the multicast addresses of all communication nodes after receiving the confirmation or the home town agent does it in stead to register to all communication nodes.
Description
Technical field
The present invention relates to network communication field, relate in particular to the middle mobile node of mobile IP v 6 (Internet Protocolversion 6) to the communication node process registration.
Background technology
Along with the development of mobile communication technology, increasing portable terminal has appearred on the Internet.The mobile subscriber needs mobile anywhere or anytime access service and roaming service.Internet engineering task tissue (Internet Engineering Task Force, IETF) (MobilitySupport for Internet Protocol version 6, MIPv6) standard is exactly to be used for supporting access and the roaming service of mobile node in the IPv6 network to the RFC3775 of Zhi Dinging.In MIPv6, some terms have been carried out standard definition:
1, (Mobile Node, MN): can move between different sub-network, the while still with its home address sign, need not change its home address to mobile node.
2, communication node (Correspondent Node, CN): be the peer node that all and mobile node communicate.
3, home link (Home Link): be the link that mobile node moves preceding place.
4, foreign link (Foreign Link): be that mobile node moves the link that the back is inserted.
5, home address (Home-of Address, HoA): the permanent address that is used to identify mobile node that to be mobile node obtain at home link.
6, Care-of Address (Care-of Address, CoA): be that mobile node inserts the temporary address that obtains behind the foreign link.
7, home agent (Home Agent, HA): be a router on the home link, when mobile node leaves home link, insert foreign link after, be used to preserve the log-on message of mobile node, and the Care-of Address that forwards the packet to mobile node.
8, binding (binding): be the home address of mobile node and the corresponding relation of Care-of Address, be used for to home agent and communication node registration.
As shown in Figure 1, mobile node is inserting new link, and (Binding Update, BU) message allows home agent and communication node all know own present care-of address to home agent and communication node registration can to use Binding Update behind the acquisition Care-of Address.
As shown in Figure 2, consider safety factor, but mobile node returns routing procedure (Return Routability Procedure will carrying out earlier before communication node registration, RRP), wherein Home of TestInit (HoTI) message will be forwarded to communication node through home agent, and Home of Test (HoT) will get back to communication node through home agent.Even under the situation of packet loss not, a complete RRP also needs about 1.5 times of loopback delays, and (round trip times, RTT), and mobile node and home agent registration need about 1 times RTT.
As shown in Figure 3, when mobile node after the succeeding in registration of communication node, communication node and mobile node just need not be transmitted by home agent and can direct communication again.When new communication node will be communicated by letter with mobile node, at first can transmit by home agent, MIPv6 starts route optimization mechanism, registering to communication node shown in the execution graph 1 then.After succeeding in registration, can directly communicate by letter as Fig. 3 with mobile node.Though MIPv6 has solved the macroscopical mobile problem of mobile node.But far and mobile when more frequent again when mobile node apart from home network and communication node, can cause a large amount of logon messages, and message is lost easily also.
In view of the above problems, Motorola Inc.'s invention disclosed patent application " a kind of communication system and method " (open day: on July 16th, 2003, publication number: CN1430844A) use multicast service to transmit binding update messages, avoided increasing such message effectively, as shown in figure 13, this method requires mobile node 106 binding update messages to send in the known protocol of communication node 104, and described mobile node 106 can be an individual node, also can be a plurality of nodes.Multicast service unit 105 comprises the multi-cast registration entity (Entity) that is used for allocation of multicast addresses, also comprises the domain name system (DNS) that is used for writing down domain name, IP address and multicast address binding.Mobile node 106 comprises a lot of existing mobile IPv 6 protocol mobile node operations, but the tabulation that does not keep a plurality of communication nodes 104.Mobile node 106 obtains multicast address from the multi-cast registration entity, and multicast address is for good and all relevant with mobile node 106, and is registered to DNS by mobile node 106.
Before setting up communication between communication node 104 and the mobile node 106, communication node 104 is called out DNS to obtain the IP address for mobile node 106 local addresss, and DNS returns the permanent multicast address of local address and multicast group.Communication node 104 utilizes multicast address to be scheduled to the multicast group, and beginning is communicated by letter with mobile node 106 at the local address place.When mobile node 106 moves to field network, obtain Care-of Address after, periodically Care-of Address is sent to multicast address with Binding Update (BU) message ground form, and the multicast service unit with binding message be distributed in the multicast group communication node 104.When the bottom multicast mechanism of communication node 104 by the agreement of IPv6 group when Binding Update is received in multicast service unit 105, will in banding cache, increase the local address of mobile node 106 and the binding relationship of Care-of Address.
As can be seen, this invention utilizes the multi-cast registration entity in the multicast service unit 105 to obtain multicast address, and with the local address and the multicast address permanent bindings of mobile node 106, has bigger potential safety hazard.In addition, mobile node 106 need be registered to the binding relationship of local address and multicast address on the DNS, needs to change existing dns server, implements to have big difficulty.And mobile node 106 do not keep the tabulation of a plurality of communication nodes 104, has compatibility issue with existing standard, can't gather yet and utilize the clean culture binding to come the communication node that needs the clean culture binding is bound.
In addition, in order to solve the problem that the MIPv6 microcosmic moves, IETF proposed again hierarchy mobile IP v 6 (Hierarchical Mobile IPv6 Mobility Management, HMIPv6).HMIPv6 has defined the topological structure in a MAP territory, make mobile node in same MAP territory, not need when mobile to home agent and communication node registration, only between the MAP territory move just need be to home agent and communication node registration, thereby significantly reduced mobile node required authentication in frequent moving process, the message amount of registration.In HMIPv6, comprise following term:
1, (Access Router AR) is the default router of mobile node to couple in router;
2, (Mobility Anchor Point is that mobile node inserts the router in the field network MAP) to mobile positioning point, and as the local agent of mobile node, move this locality of management mobile node;
3, (Regional Care-of Address RCoA) is the Care-of Address of the corresponding MAP of mobile node acquisition to regional care-of address;
4, (On-link Care-of Address LCoA) is the Care-of Address of the corresponding A R of mobile node acquisition to on-link care-of address;
5, local binding (Local Binding Update) is that mobile node is used for to MAP binding RCoA and LcoA.
As shown in Figure 4, after mobile node enters the MAP territory, utilize the router advertisement that receives to form RCoA and LCoA, carry out this locality registration to MAP then, again to home agent and communication node registration.After succeeding in registration (as shown in Figure 5), the grouping that all communication nodes mail to mobile node arrives MAP earlier, is forwarded to mobile node by MAP with the tunnel; The grouping that same all mobile nodes mail to communication node is forwarded to MAP with the tunnel earlier and mails to communication node again.
As shown in Figure 6, when mobile node moves in the MAP territory, obtain only need carry out this locality registration behind the new LCoA, and no longer need to home agent and communication node registration to MAP.The grouping that all communication nodes mail to mobile node arrives MAP earlier, is forwarded to mobile node by MAP with the tunnel; The grouping that same all mobile nodes mail to communication node is forwarded to MAP with the tunnel earlier and mails to communication node again.Have only mobile node between the territory, just to need when mobile as shown in Figure 4 to MAP and home agent, communication node registration.
As mentioned above, HMIPv6 has significantly reduced the quantity of the registration association message that mobile node uses when mobile in the MAP territory, the microcosmic of mobile node in the MAP territory moved good management role.But, when mobile node is mobile between the territory, still inevitably to not reduce relevant RTT to home agent and communication node registration.
Summary of the invention
Technical problem to be solved by this invention be prior art exist in MIPv6 or HMIPv6, potential safety hazard is many, the realization difficulty is big, and can't reduce the shortcoming of RTT time delay, in the hope of propose a kind of can be in MIPv6 and HMIPv6 safety, simply reduce in the mobile IP v 6 standard of RTT time delay mobile node to the communication node process registration.
Mobile node may further comprise the steps to the communication node process registration in the mobile IP v 6 standard of the present invention:
Mobile node generates an interim multicast address that is used for managing all communication nodes;
When communication node was communicated by letter with mobile node, communication node calculated corresponding multicast address according to rule, and request adds multicast group;
Mobile node inserts field network, and to the home agent registration, home agent returns binding acknowledgement again;
Mobile node just sends the multicast address of Binding Update message to corresponding all communication nodes after receiving the binding acknowledgement of home agent, perhaps replace mobile node to send the multicast address of Binding Update message, to all communication node registrations to corresponding all communication nodes by home agent.
The method of the invention further may further comprise the steps:
The first step, mobile node generate an interim multicast address of corresponding all communication nodes, and form an interim multicast address that is used for the supervisory communications node that may repeat hardly;
In second step, when communication node was communicated by letter with mobile node, the rule according to the first step behind the home address of acquisition mobile node calculated corresponding multicast address, and communication node is by sending the multicast group that the request of MLD request message adds correspondence then;
In the 3rd step, mobile node is recorded in the address of communication node in the Binding Update tabulation; As shown in Figure 7, wherein the CN Address territory, IPv6 address of communication node is the address of communication node, the home address HoA territory of mobile node is the home address of mobile node, the Care-of Address CoA territory that mobile node sends in the Binding Update message is empty (because also not obtaining CoA now), initialization life span Init LT territory is initial life span, and residue life span Rem LT territory is remaining life span;
In the 4th step, after mobile node moved to field network acquisition Care-of Address, beginning was registered to home agent, this process is identical with the registration process of standard MIPv6, if succeed in registration, home agent promptly returns binding acknowledgement, and (Binding Acknowledge BAck) gives mobile node;
The 5th step, after mobile node is received binding acknowledgement from home agent, send the multicast address of Binding Update message to corresponding all communication nodes, and to all communication node registrations, revise the Binding Update tabulation simultaneously, insert the Care-of Address that is obtained in the CoA territory, the InitLT territory is the initialization life span of Binding Update;
In the 6th step, after binding end life cycle, communication node withdraws from multicast group in sign off or the banding cache, and mobile node is also with its deletion from the Binding Update tabulation.
In the method for the invention, the message of multicast binding does not need to confirm, if certain communication node is not received the Binding Update message, just it is handled as the new communication node in the 6th step.But communication node can return the binding acknowledgement message, the receiving group binding of notice mobile node.For the communication node of not supporting the multicast binding,, will handle as the new communications nodes in the 6th step owing to do not receive multicast Binding Update message.
In described the 4th step, also comprise following aspect:
If what mobile node inserted is the HMIPv6 network, then mobile node is at first registered to MAP; Behind the binding acknowledgement that obtains MAP, beginning is registered to home agent;
If succeed in registration, home agent returns binding acknowledgement and gives mobile node.
In described the 5th step, as having new communication node to communicate by letter with mobile node this moment, then this new communication node adds corresponding multicast group according to described mode of second step.Simultaneously, grouping will be forwarded to mobile node by the tunnel by home agent.Also might communication node just receive the multicast binding message from mobile node after adding multicast group, like this, the Care-of Address of mobile node is just directly mail in grouping.After mobile node is received this grouping, no matter transmit from home agent, still directly send from communication node, all as described in the 3rd step, in the Binding Update tabulation, create respective items, directly send the Binding Update message then to communication node, the CoA territory of the respective items in the Binding Update tabulation is inserted the Care-of Address of acquisition, setting the InitLT territory simultaneously is the initialization life span of Binding Update again.
In described the 5th step, can also use home agent to send multicast binding message.Home agent equally also can obtain the multicast address of all communication nodes of communicating by letter with this mobile node by the rule of the first step returning binding acknowledgement in the mobile node, represents mobile node to send the Binding Update message to this multicast address then.Mobile node is revised the Binding Update tabulation after receiving the binding acknowledgement message of home agent, insert the Care-of Address of acquisition in the CoA territory, and the InitLT territory is the initialization life span of Binding Update.
The method of the invention makes mobile node when communication node is registered, and no longer needs to send successively the Binding Update message to all communication nodes.Pass through multicasting technology, only need send a Binding Update message to the multicast address of corresponding all communication nodes by mobile node or home agent, disposable to all communication node registrations, significantly reduced the use amount of registration association message, reduced the handover delay of mobile node.
Description of drawings
Fig. 1 be in the method for the invention among the MIPv6 mobile node to home agent and communication node registration schematic diagram.
Return the routing procedure schematic diagram but Fig. 2 is that mobile node moves among the MIPv6 in the method for the invention before communication node registration.
Fig. 3 is the direct communication process schematic diagram of registering among the MIPv6 in the method for the invention between back mobile node and communication node.
Fig. 4 is that mobile node enters behind the MAP territory to MAP and home agent, communication node registration process schematic diagram in the method for the invention.
Fig. 5 is that registration back mobile node passes through MAP communication process schematic diagram with communication node in the method for the invention.
Fig. 6 be in the method for the invention in the MAP territory registration schematic diagram when mobile.
Fig. 7 is the tabulation of the Binding Update on the mobile node in the method for the invention.
Fig. 8 is the topological structure schematic diagram of multicast binding registration method.
Fig. 9 is the Binding Update tabulation of MN in home link and CN1 and CN2 communication process in the method for the invention.
Figure 10 is by mobile node multicast binding registration schematic diagram in the method for the invention.
Figure 11 is multicast binding back Binding Update tabulation in the method for the invention.
Figure 12 is by home agent multicast binding registration schematic diagram in the method for the invention.
Figure 13 is the structural representation as one of prior art of the present invention.
Embodiment
Be described in further detail below in conjunction with the enforcement of accompanying drawing technical scheme:
The method of the invention utilizes the multicast binding to register to communication node, be with HMIPv6 register method difference with general MIPv6: it all adds a specific interim multicast group with all communication nodes of communicating by letter with mobile node, mobile node sends the Binding Update message to communication node no longer successively, but utilize multicast, send a Binding Update message by mobile node or home agent to the multicast address of corresponding all communication nodes, disposable to all communication node registrations.The difference of the method and Motorola's patent (publication number CN1430844A) is: do not need in the multicast service unit multi-cast registration entity to concentrate and distribute multicast address, generated automatically by mobile node in this method; Do not need DNS to manage the corresponding relation of multicast address and mobile node concentratedly, this method is by mobile node management; Multicast address is not permanent relevant with mobile node, but the interim interim multicast address that distributes; Preserve the Binding Update tabulation on the mobile node, made the clean culture Binding Update also can use in the method.
Core concept of the present invention is: generate an interim multicast address that is used for managing all communication nodes by mobile node according to certain rule, when communication node is communicated by letter with mobile node, communication node calculates corresponding multicast address according to rule, and request adds multicast group.Then, mobile node inserts field network, and to the home agent registration, home agent returns binding acknowledgement again.Mobile node just sends the multicast address of Binding Update message to corresponding all communication nodes after receiving the binding acknowledgement of home agent, perhaps replace mobile node to send the multicast address of Binding Update message, to all communication node registrations to corresponding all communication nodes by home agent.
Mainly comprise following several territory (as shown in Figure 7) in the Binding Update tabulation (Binding Update List) among the MIPv6, specify as follows: CN Address, the IPv6 address of communication node; HoA, the home address of mobile node; CoA, the Care-of Address that mobile node sends in the Binding Update message; Init LT, the initialization life span, unit is a millisecond (ms), represents the initialization life span of this binding; RemLT, the residue life span, unit be millisecond (ms), represent this binding the residue life span.
On the home link in the MIPv6 network among Fig. 8 mobile node MN is arranged, home agent HA and communication node CN1 have communication node CN2 and CN3 respectively on two foreign link.Suppose this moment mobile node just on home link initialization finish, obtained link-local address and HoA, and essential information such as default gateway, also do not begin to communicate by letter with other communication nodes.At this moment, the tabulation of the Binding Update on the mobile node is for empty.Present embodiment is supposed described equipment as not specifying, all supports the multicast binding, and does not carry out RRP and relevant operation before the multicast binding.
1. mobile node is when home link,
1.1 mobile node obtains multicast address
Mobile node MN is after the local link initialization finishes, obtain home address 2001 ∷ f04:75ff:fefb:30b1/64, take out preceding 48 (2001:0000:0000) of home address simultaneously, interface identifier with the EUI-64 form, being added to forms the interim multicast address ff1e:2001 ∷ f04:75ff:fefb:30b1 that may repeat hardly on Format Prefix ff1e ∷/12, is used for managing the communication node that all communicate with.Certainly, mobile node MN also can use additive method to generate multicast address.
1.2 the formation of multicast group
When communication node CN1 will communicate by letter with MN, at first can obtain the home address of MN.Then, can obtain the multicast address ff1e:2001 ∷ f04:75ff:fefb:30b1 of corresponding all communication nodes according to aforesaid multicast address create-rule.CN1 sends the request of MLD request message according to this multicast address and adds corresponding multicast group.Afterwards, CN1 begins the proper communication with MN.
After MN receives the grouping that CN1 sends, newly-increased record in the Binding Update tabulation, wherein CN Address territory is the IP address 2001 ∷ f04:75ff:fefb:30b2/64 of CN1, the HoA territory is the home address 2001 ∷ f04:75ff:fefb:30b1/64 of mobile node, the CoA territory is empty, sets InitLT territory and RemLT territory simultaneously.
At this moment, there is communication node CN2 to communicate by letter again with mobile node MN.Equally, CN1 calculates corresponding multicast address according to the home address of MN earlier, just begins to communicate by letter with MN after the multicast group of this multicast address correspondence of request adding.After MN receives grouping from CN2, also in the Binding Update tabulation, increase a record, as shown in Figure 9, wherein CN Address territory is the IP address 3ffe ∷ 2d0:d0ff:fedf:f4d6/64 of CN2, the HoA territory is the home address 2001 ∷ f04:75ff:fefb:30b1/64 of mobile node, the CoA territory is empty, sets InitLT territory and RemLT territory simultaneously.
For not having multicast server on the communication node of not supporting the multicast binding or the communication node place link, communication node can not ask to add multicast group so, and it is just communicated by letter with mobile node according to the rule of MIPv6.But after mobile node is received grouping from communication node,, all to carry out aforesaid processing no matter whether communication node supports the multicast binding.
2. after mobile node inserts foreign link
2.1 register to home agent
As shown in figure 10, after moving to subnet when mobile node MN with network prefix 3ffe ∷/64, can obtain Care-of Address 3ffe ∷ f04:75ff:fefb:30b1/64, MN registers to home agent HA transmission Binding Update message according to the registration process of MIPv6 then.HA can carry out some detections after receiving the Binding Update message of MN, if success just sends the binding acknowledgement message to MN.
2.2 register to communication node
MN just sends the Binding Update message to multicast address ff1e:2001 ∷ f04:75ff:fefb:30b1, as shown in figure 10 after receiving the binding acknowledgement of HA.Because each communication node has added the multicast group of this multicast address correspondence in advance,, and in arbitrary branch of MN and communication node, has only a Binding Update message so each communication node all can receive the Binding Update message that MN sends.MN checks the Binding Update tabulation, inserts Care-of Address 3ffe ∷ f04:75ff:fefb:30b1/64 in the CoA territory, and corresponding territories such as change InitLT, RemLT, shown among Figure 11 preceding two.
If replace MN to send multicast binding message by HA, as shown in figure 12, HA just can calculate the multicast address ff1e:2001 ∷ f04:75ff:fefb:30b1 of corresponding all communication nodes according to above-mentioned multicast address create-rule after receiving the Binding Update message of MN so, when MN sends binding acknowledgement, HA just replaces this multicast address of MN to send the Binding Update message.MN checks the Binding Update tabulation after receiving the binding acknowledgement of HA, insert Care-of Address 3ffe ∷ f04:75ff:fefb:30b1/64 in the CoA territory, and corresponding territories such as change InitLT, RemLT.
2.3 new communications nodes
After MN sends multicast binding message, there is new communication node CN3 to communicate with again.CN3 can obtain the multicast address of corresponding all communication nodes according to aforesaid multicast address create-rule: ff1e:2001 ∷ f04:75ff:fefb:30b1 behind the home address that obtains MN.CN3 adds multicast group by the request of MLD request message.If at this moment just receive multicast Binding Update message,, directly grouping is sent to the Care-of Address 3ffe ∷ f04:75ff:fefb:30b1/64 of MN then just CN3 upgrades oneself banding cache so from MN.Otherwise meeting in group is forwarded to MN by HA by the tunnel.After MN received new grouping, no matter forward by HA, still CN3 directly sended over, and the Binding Update that all CN3 is added oneself is tabulated, and shown among Fig. 7 the 3rd, corresponding territory is set; Afterwards, MN sends the Binding Update message to this communication node separately, insert Care-of Address 3ffe ∷ f04:75ff:fefb:30b1/64 in the CoA territory with respective items in the Binding Update tabulation then, corresponding territories such as change InitLT, RemLT, all the other handling processes are identical with registration process among the MIPv6, shown among Figure 11 the 3rd.
Communication node does not need to return binding acknowledgement behind receiving group binding message, still, communication node also can be told mobile node receiving group binding by binding acknowledgement.
As communication node when MN sends Binding Update request message (Binding Refresh RequestMessage), MN can inquire about the Binding Update tabulation, if there is respective items, just send the Binding Update message separately, and upgrade the domains of dependence such as InitLT, RemLT of respective items in the Binding Update tabulation to it.Otherwise, ignore the Binding Update request message of receiving.
3. mobile node inserts HMIPv6
Embodiment inserts the situation of MIPv6 foreign link for mobile node as mentioned above.If what mobile node inserted is the foreign link of HMIPv6, mobile node is wanted to register to MAP earlier so, just begins to register to home agent after receiving the binding acknowledgement of MAP.Afterwards processing procedure and the foregoing description are identical, do not repeat them here.
4. withdraw from multicast group
Behind the sign off of communication node and mobile node, after perhaps finished the life cycle of binding in the banding cache, communication node just withdrawed from this interim multicast group.Mobile node is also deleted the item of correspondence from the Binding Update tabulation.
The present invention proposes in a kind of mobile IP v 6 and the hierarchy mobile IP v 6 network, mobile node carries out process registration to the communication node that all and this mobile node communicate.The communication node that it allows all and mobile node communicate adds a specific interim multicast group, when mobile node inserts new subnet, after obtaining new Care-of Address, can use multicasting technology, send to the communication node that all communicate with it with the Binding Update message is disposable.The present invention has defined the forming process of above-mentioned multicast group, and the concrete process of utilizing the multicast binding to register, can significantly reduce the usage quantity of mobile node association message of Binding Update in the communication node registration process, reduce the handover delay of mobile node.
Claims (8)
1, mobile node is characterized in that to the communication node process registration in a kind of mobile IP v 6 standard, may further comprise the steps:
Mobile node generates an interim multicast address that is used for managing all communication nodes;
When communication node was communicated by letter with mobile node, communication node calculated corresponding multicast address according to rule, and request adds multicast group;
Mobile node inserts field network, and to the home agent registration, home agent returns binding acknowledgement again;
Mobile node just sends the multicast address of Binding Update message to corresponding all communication nodes after receiving the binding acknowledgement of home agent, perhaps replace mobile node to send the multicast address of Binding Update message, to all communication node registrations to corresponding all communication nodes by home agent.
2, mobile node is characterized in that to the communication node process registration in the mobile IP v 6 standard according to claim 1, further may further comprise the steps:
The first step, mobile node generate an interim multicast address of corresponding all communication nodes, and form an interim multicast address that is used for the supervisory communications node that may repeat hardly;
In second step, when communication node was communicated by letter with mobile node, the rule according to the first step behind the home address of acquisition mobile node calculated corresponding multicast address, and communication node is by sending the multicast group that the request of MLD request message adds correspondence then;
In the 3rd step, mobile node is recorded in the address of communication node in the Binding Update tabulation;
In the 4th step, after mobile node moved to field network acquisition Care-of Address, beginning was to the home agent registration, and this process is identical with the registration process of standard mobile IP v 6, if succeed in registration, home agent promptly returns binding acknowledgement and gives mobile node;
The 5th step, after mobile node is received binding acknowledgement from home agent, send the multicast address of Binding Update message to corresponding all communication nodes, and to all communication node registrations, revise the Binding Update tabulation simultaneously, insert the Care-of Address that is obtained in the Care-of Address CoA territory that mobile node sends in the Binding Update message, initialization life span InitLT territory is the initialization life span of Binding Update;
In the 6th step, after binding end life cycle, communication node withdraws from multicast group in sign off or the banding cache, and mobile node is also with its deletion from the Binding Update tabulation.
3, in the mobile IP v 6 standard according to claim 1 mobile node to the communication node process registration, it is characterized in that, the message of multicast binding does not need to confirm, if certain communication node is not received the Binding Update message, then it is handled as the new communication node in the 6th step.
4, in the mobile IP v 6 standard according to claim 1 mobile node to the communication node process registration, it is characterized in that address list comprises with the lower part described in the 3rd step: the CN Address territory, IPv6 address of communication node, the home address HoA territory of mobile node, CoA territory, Init LT territory, residue life span Rem LT territory.
5, mobile node is characterized in that to the communication node process registration in the mobile IP v 6 standard according to claim 4, and the Care-of Address CoA territory that described mobile node sends in the Binding Update message is for empty.
6, mobile node is characterized in that to the communication node process registration in the mobile IP v 6 standard according to claim 1, in described the 4th step, also comprises following aspect:
If what mobile node inserted is H mobile IP v 6 network, then mobile node is at first registered to MAP; Behind the binding acknowledgement that obtains MAP, beginning is registered to home agent;
If succeed in registration, home agent returns binding acknowledgement and gives mobile node.
7, mobile node is characterized in that to the communication node process registration in the mobile IP v 6 standard according to claim 1, in described the 5th step, further comprises following aspect:
Communicate by letter with mobile node if any new communication node, then this new communication node adds corresponding multicast group according to described mode of second step;
Divide into groups simultaneously to be forwarded to mobile node by home agent by the tunnel, the Care-of Address of mobile node is directly mail in grouping;
After mobile node is received this grouping,, still directly send, all as described in the 3rd step, in the Binding Update tabulation, create respective items from communication node no matter transmit from home agent;
Directly send the Binding Update message then to communication node;
The CoA territory of the respective items in the Binding Update tabulation is inserted the Care-of Address of acquisition, setting the InitLT territory simultaneously is the initialization life span of Binding Update again.
8, mobile node is characterized in that to the communication node process registration in the mobile IP v 6 standard according to claim 1, in described the 5th step, further may further comprise the steps:
Use home agent to send multicast binding message;
Home agent obtains the multicast address of all communication nodes of communicating by letter with this mobile node returning binding acknowledgement in the mobile node by the described rule of the first step;
On behalf of mobile node, home agent send the Binding Update message to this multicast address;
Mobile node is revised the Binding Update tabulation after receiving the binding acknowledgement message of home agent, insert the Care-of Address of acquisition in the CoA territory, and the InitLT territory is the initialization life span of Binding Update.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100691405A CN100463548C (en) | 2005-05-11 | 2005-05-11 | Registering method of mobile node to communication node in mobile IPv6 standard |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100691405A CN100463548C (en) | 2005-05-11 | 2005-05-11 | Registering method of mobile node to communication node in mobile IPv6 standard |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1863375A true CN1863375A (en) | 2006-11-15 |
| CN100463548C CN100463548C (en) | 2009-02-18 |
Family
ID=37390676
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100691405A Expired - Fee Related CN100463548C (en) | 2005-05-11 | 2005-05-11 | Registering method of mobile node to communication node in mobile IPv6 standard |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100463548C (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101772111A (en) * | 2008-12-31 | 2010-07-07 | 阿德利亚科技(北京)有限责任公司 | Multicast client wireless roaming method and equipment |
| CN101360027B (en) * | 2007-07-30 | 2012-06-27 | 华为技术有限公司 | Method, apparatus and system for acquiring registering result and router migration |
| CN105119832A (en) * | 2015-09-29 | 2015-12-02 | 东北大学 | MIPv6 security mobility management system based on identification cryptology and mobility authentication method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1158742A1 (en) * | 2000-05-24 | 2001-11-28 | Motorola, Inc. | Communication system and method therefor |
| US6804221B1 (en) * | 2000-06-26 | 2004-10-12 | Alcatel | Micromobility using multicast |
| CN1177433C (en) * | 2002-04-19 | 2004-11-24 | 华为技术有限公司 | Method for managing broadcast of multi-broadcast service source in mobile network |
| US7457289B2 (en) * | 2002-12-16 | 2008-11-25 | Cisco Technology, Inc. | Inter-proxy communication protocol for mobile IP |
-
2005
- 2005-05-11 CN CNB2005100691405A patent/CN100463548C/en not_active Expired - Fee Related
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101360027B (en) * | 2007-07-30 | 2012-06-27 | 华为技术有限公司 | Method, apparatus and system for acquiring registering result and router migration |
| CN101772111A (en) * | 2008-12-31 | 2010-07-07 | 阿德利亚科技(北京)有限责任公司 | Multicast client wireless roaming method and equipment |
| CN101772111B (en) * | 2008-12-31 | 2014-05-21 | 安移通网络科技（中国）有限公司 | Multicast client wireless roaming method and equipment |
| CN105119832A (en) * | 2015-09-29 | 2015-12-02 | 东北大学 | MIPv6 security mobility management system based on identification cryptology and mobility authentication method |
| CN105119832B (en) * | 2015-09-29 | 2018-01-02 | 东北大学 | The MIPv6 safety movings management system and mobile authentication method of ID-based cryptosystem |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100463548C (en) | 2009-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101268670B (en) | Multihomed mobile node, homed proxy and method for enabling simultaneous use of home network and foreign network | |
| CN102106166B (en) | Anchoring services of a mobile station attached to a first service domain at a home agent in a second service domain | |
| US7788405B2 (en) | Method for automatic configuration of prefixes at maps in HMIPv6 | |
| CN100394733C (en) | System and method for supporting mobility of mobile node using regional anchor point in future internet | |
| KR101439270B1 (en) | Support for continuity of tunnel communications for mobile nodes having multiple care of addressing | |
| CN1315314C (en) | Communication system and method therefor | |
| AU2004307038B2 (en) | Method and system for discovering a mobility anchor point and managing mobility of a mobile node in a network system supporting mobile IP | |
| CN1711792A (en) | Method and apparatus for handoff of a wireless packet data services connection | |
| CN101534496B (en) | Method for obtaining home link information by user | |
| CN101052200A (en) | Route renewing method in mobile communication system | |
| CN100525299C (en) | Apparatus and methods for performing binding procedure in respect of mobile node in foreign packet data network | |
| US20100082796A1 (en) | Mobile communication management system and mobile communication management method | |
| CN1784059A (en) | Fast switching method in MAP field of HMIPv6 | |
| CN1914883A (en) | Method and apparatus providing address management in a flat structure mobile network | |
| CN101047673A (en) | Method and system for acquiring terminal address correlation information | |
| CN1788508A (en) | Methods and apparatus for extending mobile IP | |
| CN1437367A (en) | Multicast business realizing method in mobile network | |
| CN102651862A (en) | IP (Internet Protocol) address configuration method of WAP (Wireless Application Protocol) gateway and equipment thereof | |
| CN1863375A (en) | Registering method of mobile node to communication node in mobile IPv6 standard | |
| CN1977510A (en) | Telecommunications | |
| CN101047996B (en) | Method, system for acquiring target network transmission address information and its application | |
| CN101193117B (en) | Intercommunication method, access network and wireless network between terminals | |
| CN1773988A (en) | A service universal block radio business supporting internodel communication method | |
| CN101682902B (en) | Mobile communication system, position registration method, terminal, and home agent | |
| CN101047645A (en) | Double-stack support extension method of layer mobile IPv6 protocol |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090218 Termination date: 20190511 |