CN103581346A - Message sending method, message sending system and local mobility anchor - Google Patents
Message sending method, message sending system and local mobility anchor Download PDFInfo
- Publication number
- CN103581346A CN103581346A CN201210251144.5A CN201210251144A CN103581346A CN 103581346 A CN103581346 A CN 103581346A CN 201210251144 A CN201210251144 A CN 201210251144A CN 103581346 A CN103581346 A CN 103581346A
- Authority
- CN
- China
- Prior art keywords
- address
- lma
- message
- publicly
- mag
- 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
Landscapes
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
The invention discloses a message sending method, a message sending system and a local mobility anchor (LMA) which are used in a scene in which NAT (network address translation) exists between an MAG (mobile access gateway) and the LMA. The method comprises the following steps: the LMA assigns a public IPv4 home address and a port number to an MN (mobile node) which is accessed to the MAG and supports IPv4; and the NAT translates the address of a received message according to the public IPv4 home address, the port number and a private IPv4 address of the MN and sends the message according to the translated address. According to the invention, the LMA assigns the public IPv4 home address and the port number to the MN, and the NAT can carry out translation according to the assigned address so as to forward a message after the message is received. Therefore, when the NAT exists between the MAG and the LMA, PMIPv6 supports IPv4, namely, mobile management of an IPv4 mobile terminal is supported in a PMIPv6 domain.
Description
Technical field
The present invention relates to the communications field, in particular to a kind of file transmitting method and system and local mobile anchor.
Background technology
Internet protocol version 4(Internet Protocol version6, referred to as IPv4) to internet protocol version 6(Internet Protocol version6, referred to as IPv6) transition be a long-term process, in this transient process, IPv6 and IPv4 agreement all will be used in identical network configuration.Therefore the MN in PMIPv6 territory may operate under IPv4-only, IPv6-only or two mode stack, and Mobile Access Gateway (Mobile Access Gateway, referred to as MAG) with local mobile anchor (Local MobilityAnchor, referred to as LMA) between network may be the network of an IPv4 or IPv6.Therefore, no matter transmission network is IPv4, or IPv6 network, in PMIPv6 territory, identical mobility entity all needs mobile node (the Mobile Node for IPv4-only, IPv6-only or two mode stacks, referred to as MN) mobile management is provided, realize MN in moving process, the maintenance of conversation continuity.
Fig. 1 supports the network architecture schematic diagram of IPv4 according to the PMIPv6 of correlation technique, for the mobile management problem under scene shown in Fig. 1, (Request For Comments requests for comments, referred to as RFC) 5844(IPv4Support for Proxy Mobile IPv6) proposed not exist between a kind of MAG and LMA network address translation (Network Address Translation, referred to as NAT) time, in PMIPv6 territory for the support of IPv4.In Fig. 1, HoA is that home address (Home Address) CoA is Care-of Address (Care-ofAddress).
In RFC5844:
(1) all mobility entities, LMA and MAG support two stacks, LMA and MAG can configuration of IP v4 and/or the address of IPv6.
(2) no matter the type of transmission network how, the mobile management signaling between MAG and LMA is all based on IPv6.
(3) MN obtains by this agreement support the IPv4 home address (Home Address, referred to as HoA) that LMA is its distribution.
In this agreement, proxy mobile IPv 6 (Proxy Mobile IPv6, referred to as PMIPv6) as shown in Figure 2, comprises the steps: the detailed process of the support of IPv4 (between MAG and LMA without NAT)
Step S202, supports the MN of IPv4 to move in PMIPv6 territory, first completes access authentication procedure.In access authentication procedure, MAG obtains the IP protocol version that MN supports from the strategy file (policy profile) of MN, and for example MN supports IPv4 or IPv6.
Step S204, MAG supports type according to the IP protocol version of MN, initiates agency of trademark registration process.If MN is IPv4 node, agent binding update (the Proxy Binding Update that MAG is initiating, referred to as PBU) the IPv4 home address request of carrying full 0 or comprising MN IPv4 home address in message selects (IPv4Home Address Request Option), for generating or the IPv4 home address of the MN that renews a contract.
Step S206, LMA receives after PBU message, establishment or renewal are about banding cache entry (the Banding Cache Entry of MN, referred to as BCE), than PMIPv6, in the BCE of MN, increased MN IPv4 home address (comprising corresponding subnet mask), be dispensed to the IPv4 default router address of MN.And in being back to the PBA of MAG, by the response of IPv4 home address, select (IPv4HomeAddress Reply Option) to carry the IPv4 home address of MN.
Step S208, MAG receives agent binding confirmation (the Proxy Binding Acknowledgement that comes from LMA, referred to as PBA) after message, in the Binding Update list of entries about MN (Banding Update List Entry, referred to as BUL), increase the IPv4 default router address (selecting (IPv4Default-RouterAddress Option) to obtain by the IPv4 mistake routing address in PBA) of the IPv4 home address (comprising subnet mask) and the MN that distribute to MN connecting interface.In addition, IPv4DHCP support mode selects the S flag bit in (IPv4DHCP Support Mode option) to represent that MAG is as dhcp response agency (DHCP Relay Agent) or DHCP is server.
Step S210, it is the IPv4 home address that MN distributes that MN arranges agreement (Dynamic Host Configuration Protocol, referred to as DHCP) Procedure Acquisition LMA by DynamicHost.
Channel message between LMA and MAG can adopt the tunnel styles such as IPv4-or-IPv6-over-IPv6, IPv4-or-IPv6-over-IPv4 to encapsulate.
Along with the fast development of mobile Internet, come from the mobile Internet access of smart mobile phone and other mobile terminal, accelerating exhausting of IPv4 address, in existing network, can not be unique public network IP v4 address of all mobile terminal configuration.A kind of method that alleviates this problem is exactly a plurality of terminal configuration private ip v4 addresses, shares a publicly-owned IPv4 address in network service.Therefore, in the actual deployment of network, can dispose NAT at the interface of privately owned and public network, carry out the conversion of privately owned and publicly-owned IPv4 address.
But agreement RFC5844 is when existing NAT between MAG and LMA, PMIPv6 does not propose effective solution for the support of IPv4, so need to propose a kind of scheme, solves the mobile management problem in this scene.
Summary of the invention
The invention provides a kind of file transmitting method, system and LMA, at least to solve in correlation technique, when there is NAT between MAG and LMA in agreement RFC5844, and PMIPv6 does not propose the problem of effective solution for the support of IPv4.
According to an aspect of the present invention, provide a kind of file transmitting method, be applied to exist between MAG and LMA the scene of NAT, the method comprises: LMA distributes publicly-owned IPv4 home address and port numbers for accessing the MN that moves of the support IPv4 of MAG; NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, and sends message according to the address after conversion.
Preferably, the MN of support IPv4 that LMA is access MAG distribute publicly-owned IPv4 home address and port numbers to comprise: LMA receives the request message from MAG, wherein, request message carries the request of publicly-owned IPv4 home address and port numbers request; LMA is that MN distributes publicly-owned IPv4 home address and the port numbers not being used according to request message; LMA sends acknowledge message to MAG, and wherein, acknowledge message carries publicly-owned IPv4 home address and port numbers.
Preferably, before NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, said method also comprises: the DynamicHost that LMA receives MN transmission arranges protocol DHCP request; LMA is that MN distributes private ip v4 address.
Preferably, above-mentioned request message also carries MN sign, and before LMA sends acknowledge message to MAG, said method also comprises: LMA is designated MN according to MN and creates BCE, and publicly-owned IPv4 home address and port numbers are added in BCE.
Preferably, at LMA, according to request message, be before MN distributes the publicly-owned IPv4 home address and port numbers not being used, said method also comprises: LMA is according to the client identification carrying in the DHCP request of the MN sign of carrying in request message and MN transmission, and judgement request distributes whether the MN of publicly-owned IPv4 home address and port numbers and the MN of request distributing IP v4 private address are same MN; If same MN, LMA is that MN distributes publicly-owned IPv4 home address and the port numbers not being used.
Preferably, at LMA, after MAG sends acknowledge message, said method also comprises: MAG obtains publicly-owned IPv4 home address and port numbers from the acknowledge message receiving; MAG is that MN creates BUL, and publicly-owned IPv4 home address and port numbers are added in BUL.
Preferably, above-mentioned request message also carries indication message, after LMA receives the request message from MAG, said method also comprises: the indication message that LMA carries from request message knows that MN is the switching that same interface carries out between different MAG.
Preferably, before NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, said method also comprises: LMA receives the DHCP request that MN sends; LMA determines that according to the client identification in DHCP request MN sent DHCP request to LMA; LMA is that MN distributes and switches front identical private ip v4 address.
Preferably, above-mentioned request message also carries MN sign, and before LMA sends acknowledge message to MAG, said method also comprises: LMA is that MN distributes and switches front identical publicly-owned IPv4 home address and port numbers according to request message; LMA upgrades the BCE of MN according to MN sign.
Preferably, at LMA, after MAG sends acknowledge message, said method also comprises: MAG obtains publicly-owned IPv4 home address and port numbers from the acknowledge message receiving; MAG is that MN creates BUL, and publicly-owned IPv4 home address and port numbers are added in BUL.
Preferably, above-mentioned request message is agent binding update messages, and above-mentioned acknowledge message is proxy binding acknowledgment messages.
Preferably, in the request of publicly-owned IPv4 home address or port numbers request, carry and be used to indicate the sign whether NAT coexists with MAG, in the situation that NAT and MAG coexist, before NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, said method also comprises: LMA by the message repeating receiving to MAG.
Preferably, before NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, said method also comprises: NAT binding private ip v4 address and publicly-owned IPv4 home address, port numbers.
Preferably, NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving and comprises: NAT receives the message that comes from MN; NAT converts the source address of message and source port number to publicly-owned IPv4 home address and port numbers.
Preferably, NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving and comprises: NAT receives the message that comes from the publicly-owned IPv4 home address of being sent to of peer node and port numbers; NAT converts the destination address of message and destination slogan to private ip v4 address and the corresponding port numbers thereof of MN.
According to a further aspect in the invention, provide a kind of LMA, having comprised: receiver module, for receiving the request message from MAG, wherein, request message carries the request of publicly-owned IPv4 home address and port numbers request; Distribution module, for according to request message being publicly-owned IPv4 home address and the port numbers that MN distribution is not used; Sending module, for sending acknowledge message to MAG, wherein, acknowledge message carries publicly-owned IPv4 home address and port numbers.
In accordance with a further aspect of the present invention, a kind of transmitting system is provided, be applied to exist between MAG and LMA the scene of NAT, this system comprises: MN, MAG, LMA and NAT, wherein, LMA comprises: distribution module, is used to the MN of access MAG to distribute publicly-owned IPv4 home address and port numbers, wherein, MN supports IPv4; NAT, coexists with MAG or LMA, comprising: modular converter, carries out address transition for the private ip v4 address according to publicly-owned IPv4 home address and port numbers and MN to the message receiving; Sending module, for sending message according to the address after conversion.
The present invention is that MN distributes publicly-owned IPv4 home address and port numbers by LMA, follow-up while receiving message, NAT can change to E-Packet according to the address of distributing, thereby realized while there is NAT between MAG and LMA, PMIPv6 is for the support of IPv4, realized in PMIPv6 territory, supported the mobile management of IPv4 mobile terminal.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, forms the application's a part, and schematic description and description of the present invention is used for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 supports the network architecture schematic diagram of IPv4 according to the PMIPv6 of correlation technique;
Fig. 2 supports the interaction diagrams of IPv4 according to the PMIPv6 of correlation technique;
Fig. 3 is according to the flow chart of the file transmitting method of the embodiment of the present invention;
Fig. 4 is according to the coexist schematic diagram of scene of the NAT of the embodiment of the present invention and MAG;
Fig. 5 is according to the coexist schematic diagram of scene of the NAT of the embodiment of the present invention and LMA;
Fig. 6 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention one;
Fig. 7 is the schematic diagram of NAT address translation process according to the preferred embodiment of the invention;
Fig. 8 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention two;
Fig. 9 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention three;
Figure 10 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention four;
Figure 11 is according to the structured flowchart of the LMA of the embodiment of the present invention;
Figure 12 is according to the structured flowchart of the transmitting system of the embodiment of the present invention.
Embodiment
It should be noted that, in the situation that not conflicting, embodiment and the feature in embodiment in the application can combine mutually.Describe below with reference to the accompanying drawings and in conjunction with the embodiments the present invention in detail.
The embodiment of the present invention provides a kind of file transmitting method, is applied to exist between MAG and LMA the scene of NAT, and Fig. 3 is according to the flow chart of the file transmitting method of the embodiment of the present invention, as shown in Figure 3, comprises that following step S302 is to step S304.
Step S302, LMA distributes publicly-owned IPv4 home address and port numbers for accessing the MN of the support IPv4 of MAG.
Step S304, NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, and sends message according to the address after conversion.
In correlation technique, when there is NAT between MAG and LMA in agreement RFC5844, and PMIPv6 does not propose the problem of effective solution for the support of IPv4.In the embodiment of the present invention, by LMA, be that MN distributes publicly-owned IPv4 home address and port numbers, follow-up while receiving message, NAT can change to E-Packet according to the address of distributing, thereby realized while there is NAT between MAG and LMA, PMIPv6, for the support of IPv4, has realized in PMIPv6 territory, supports the mobile management of IPv4 mobile terminal.Above-mentioned port numbers of distributing for MN can be one, can be also a plurality of.
Preferably, step S302 comprises: LMA receives the request message from MAG, and wherein, request message carries the request of publicly-owned IPv4 home address and port numbers request; LMA is that MN distributes publicly-owned IPv4 home address and the port numbers not being used according to request message; LMA sends acknowledge message to MAG, and wherein, acknowledge message carries publicly-owned IPv4 home address and port numbers.For MN distributes publicly-owned IPv4 home address and the port numbers not being used, can avoid the conflict of follow-up generation.
Before NAT carries out address transition according to private ip v4 address and publicly-owned IPv4 home address, port numbers, LMA distributes private address to MN, can realize by following operation: LMA receive the DHCP request that MN sends; LMA is that MN distributes private ip v4 address.
It should be noted that, distribute private address, publicly-owned address and port numbers not to distinguish sequencing.
Above-mentioned request message can also carry MN sign, and before LMA sends acknowledge message to MAG, said method also comprises: LMA is designated MN according to MN and creates banding cache entry BCE, and publicly-owned IPv4 home address and port numbers are added in BCE.
For the publicly-owned IPv4 home address that guarantees to distribute and port numbers and private ip v4 address are for same MN, at LMA, according to request message, be before MN distributes the publicly-owned IPv4 home address and port numbers not being used, said method also comprises: LMA is according to the client identification carrying in the DHCP request of the MN sign of carrying in request message and MN transmission, and judgement request distributes whether the MN of publicly-owned IPv4 home address and port numbers and the MN of request distributing IP v4 private address are same MN; If same MN, LMA is that MN distributes publicly-owned IPv4 home address and the port numbers not being used.
At LMA, after MAG sends acknowledge message, said method also comprises: MAG obtains publicly-owned IPv4 home address and port numbers from the acknowledge message receiving; MAG is that MN creates Binding Update list of entries BUL, and publicly-owned IPv4 home address and port numbers are added in BUL.
For MN, from a MAG, be switched to the situation of another MAG, above-mentioned request message also carries indication message, after LMA receives the request message from MAG, said method also comprises: the indication message that LMA carries from request message knows that MN is the switching that same interface carries out between different MAG.This preferred implementation makes LMA know that MN is switched to another MAG, so that for subsequent allocations address provides foundation, for example, for MN distributes and switches before identical address.
(1) for MN distributes private ip v4 address
Before NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, said method also comprises: LMA receives the DHCP request that MN sends; LMA determines that according to the client identification in DHCP request MN sent DHCP request to LMA; LMA is that MN distributes and switches front identical private ip v4 address.
(2) for MN distributes publicly-owned IPv4 home address and port numbers
Above-mentioned request message also carries MN sign, and before LMA sends acknowledge message to MAG, said method also comprises: LMA is that MN distributes and switches front identical publicly-owned IPv4 home address and port numbers according to request message; LMA upgrades the BCE of MN according to MN sign.
For MN, be switched to the situation of MAG, MAG need to create BUL for MN, publicly-owned IPv4 home address and the port numbers of store M N, at LMA, after MAG sends acknowledge message, said method also comprises: MAG obtains publicly-owned IPv4 home address and port numbers from the acknowledge message receiving; MAG is that MN creates BUL, and publicly-owned IPv4 home address and port numbers are added in BUL.
Above-mentioned request message is agent binding update messages, and above-mentioned acknowledge message is proxy binding acknowledgment messages.
Preferably, in the request of publicly-owned IPv4 home address or port numbers request, carry and be used to indicate the sign whether NAT coexists with MAG, in the situation that NAT and MAG coexist, before NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, said method also comprises: LMA by the message repeating receiving to MAG.In this preferred implementation, utilize sign indication NAT whether to coexist with MAG, can be for follow-up while receiving message, the operation that LMA carries out provides a foundation intuitively.
For the address transition operation of NAT, as follows:
Before NAT carries out address transition according to the private ip v4 address of publicly-owned IPv4 home address and port numbers and MN to the message receiving, NAT binding private ip v4 address and publicly-owned IPv4 home address, port numbers.
NAT receives the message that comes from MN; NAT converts the source address of message and source port number to publicly-owned IPv4 home address and port numbers.NAT receives the message that comes from the publicly-owned IPv4 home address of being sent to of peer node and port numbers; NAT converts the destination address of message and destination slogan to private ip v4 address and the corresponding port numbers thereof of MN.
In a preferred embodiment, when supporting that the MN of IPv4 moves in the PMIPv6 territory of NAT scene, MAG sends PBU message to LMA, and this PBU message is carried IPv4 network address conversion port number request and the request of publicly-owned IPv4 home address.LMA receives after PBU message, according to described PBU message, is that MN distributes the publicly-owned IPv4 home address that is not used and the combination of port numbers, and with the DHCP server that LMA coexists be that MN distributes private ip v4 address.The NAT coexisting with MAG or LMA, according to the address of above-mentioned distribution and port number information, carries out address transition to the message of contact MN.
When supporting that the MN of IPv4 switches between the MAG in the PMIPv6 territory of NAT scene, MAG sends PBU message to LMA, and this PBU message is carried IPv4 network address conversion port number request and the request of publicly-owned IPv4 home address.LMA receives after PBU, according to described PBU message, continues as MN and distributes publicly-owned IPv4 home address before switching and the combination of port numbers, and before and after keeping switching, the publicly-owned IPv4 home address distributing for MN and the combination of port numbers are constant; The DHCP server coexisting with LMA is designated MN according to MN and distributes and switch front identical private ip v4 address simultaneously.The NAT coexisting with MAG or LMA, according to the address of above-mentioned distribution and port number information, carries out address transition to the message of contact MN.
In order to make technical scheme of the present invention and implementation method clearer, below in conjunction with preferred embodiment, its implementation procedure is described in detail.
In embodiments of the present invention, when there is NAT between MAG and LMA, in PMIPv6, support the mobile management of IPv4 can be divided into two kinds of scenes, respectively as shown in Figure 4 and Figure 5.
Fig. 4 is that as shown in Figure 4, in this scene, NAT and MAG function coexist according to the coexist schematic diagram of scene of the NAT of the embodiment of the present invention and MAG.For example, when MN access MAG1, the DHCP server coexisting with LMA is MN distributing IP v4 private address, and MN is used this private address to communicate as source address.When MN moves in PMIPv6 territory, after MN access MAG2, the DHCP server coexisting with LMA continue as MN distribute one with switch front identical IPv4 private address.
Fig. 5 is that as shown in Figure 5, in this scene, NAT and LMA function coexist according to the coexist schematic diagram of scene of the NAT of the embodiment of the present invention and LMA.For example, when MN access MAG1, the DHCP server coexisting with LMA is MN distributing IP v4 private address, and MN is used this private address to communicate as source address.When MN moves in PMIPv6 territory, MN can keep the DHCP server from coexisting with LMA to obtain and switch front identical IPv4 private address.
Preferred embodiment one
What this preferred embodiment was described is that NAT and MAG coexist in situation, and when MN accesses certain MAG, PMIPv6 supports the mobile management flow process of IPv4.Fig. 6 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention one, as shown in Figure 6, comprises that following step S602 is to step S612.
Step S602, MN moves in PMIPv6 territory, access MAG1.
Step S604, MN initiates DHCPv4 address acquisition, from DHCP server(Fig. 6 and subsequent drawings, with DHCP-S, represents DHCP server) obtain a privately owned IPv4 address, for follow-up communication session.In this preferred embodiment, LMA and DHCP server coexist.It should be noted that, step S604(obtains private ip v4 address) there is no clear and definite sequencing relation with step S606, step S610 etc.
Step S606, in access authentication procedure, MAG1 knows that by relational approach MN only supports IPv4 protocol stack, for example, the IP protocol version that MAG1 obtains MN support from the policy profile of MN is IPv4 version.MAG1 is that MN sends PBU message to LMA, carries MN ID option, for identifying MN in this PBU message.
In this preferred embodiment, MAG1 carries the IPv4NAT Home Address RequestOption of a full 0 in PBU message, for asking to LMA, is that MN distributes a publicly-owned IPv4 home address.MAG1 can be by newly-increased flag in PBU message (for example, in the field of IPv4NAT Home Address Request Option and NAT Port Request Option, identify), show that NAT and MAG1 coexist, for example 1 represents that NAT and MAG1 coexist, and 0 represents there is no nat feature on MAG1.
MAG1 carries the NAT Port Request Option of a full 0 in PBU message, for asking to LMA, is that MN distributes port (port) number.
When follow-up MAG1 sends the PBU message upgraded to LMA, the IPv4NAT Home Address Request Option in PBU message and NAT Port Request Option can carry publicly-owned IPv4 address that LMA distributes and No. port.
Step S608, LMA receives after the PBU message that comes from MAG1, if carried the IPv4NAT Home Address Request Option of a full 0 and the NAT PortRequest Option of full 0 in PBU message, LMA is in the publicly-owned address pool of IPv4 and port pond (0 ~ 65535), for MN selects a publicly-owned IPv4 home address and several No. port, (LMA selects undefined and No. port of not being used as far as possible, for example some are used by application-specific for No. port, should avoid selecting such No. port).LMA must guarantee that this publicly-owned IPv4 address and several combinations of No. port are not assigned to other terminal use.
LMA is that MN creates corresponding BCE, is added to publicly-owned IPv4 home address that MN distributes and No. port in BCE, realizes that above-mentioned information identifies with MN and the binding of MAG address.
Step S610, LMA sends PBA message to MAG1, carries LMA and be publicly-owned IPv4 home address that MN distributes and No. port in this PBA message.Publicly-owned IPv4 home address and carrying by IPv4NAT Home Address Request Option and NAT PortReply Option respectively for No. port.
Follow-up, when LMA receives that coming from peer node (Correspondent Node, referred to as CN) is sent to the message of MN, according to the destination address of message and destination slogan, LMA E-Packets to corresponding MAG.
The client option carrying in the dhcp message (in order to obtain private ip v4 address) that LMA sends by the MN-ID option that carries in PBU message and MN, identify and judge whether the client of request broker mobile management service and the client of request IPv4 private address are same clients, if so, distribute the concurrent PBA of the sending message in address.It should be noted that, these two options can be used Network Access Identifier (Network Access Identifier, referred to as NAI) or device link layer identifier.
Step S612, MAG1 receives the PBA message that comes from LMA, it is the publicly-owned IPv4 home address that distributes of MN and No. port that MAG1 obtains LMA from IPv4NAT Home Address Request Option and NAT Port Reply Option.MAG1 is that MN creates BUL, and in BUL, adds the publicly-owned IPv4 home address of MN and No. port.
The NAT device binding DHCP server coexisting with MAG1 is that the IPv4 private address that distributes of MN and LMA are the publicly-owned IPv4 home address that distributes of MN, No. port.
When NAT receives the message that comes from MN, NAT device will come from source address and the source port number of the message of MN, converts LMA to and be publicly-owned IPv4 home address that MN distributes and No. port.
When NAT receives that coming from peer node is sent to LMA and is the message of the publicly-owned IPv4 home address that distributes of MN and No. port, NAT device converts the destination address of this message and destination slogan to IPv4 private address and the respective ends slogan of MN.
Fig. 7 is the schematic diagram of NAT address translation process according to the preferred embodiment of the invention, as shown in Figure 7, CN is peer node, Src represents source, Dst represents object, in Fig. 7, the first half has been described the processing procedure that NAT receives the message that comes from MN: when NAT receives after the message that comes from MN, it is publicly-owned IPv4 home address and the port numbers of MN distribution that NAT substitutes the source address of message and source port number for LMA.In Fig. 7, the latter half has been described the processing procedure that NAT receives the message that is sent to MN: when NAT receives the message that is sent to MN, NAT replaces with the destination address of message and destination slogan private ip v4 address and the corresponding port numbers of MN.
Preferred embodiment two
This preferred embodiment is described is NAT and MAG while coexisting, when MN switches between MAG, and the mobile management flow process of PMIPv6 support IPv4.Fig. 8 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention two, as shown in Figure 8, comprises that following step S802 is to step S814.
Step S802, MN moves to MAG2 from MAG1, and MN accesses MAG2.
Step S804, MAG1 perception MN has left its link, and MAG1 sends logout message to LMA, nullifies MN in the relevant information of LMA.
Step S806, MN initiates DHCPv4 address acquisition, obtains and private ip v4 address identical switching, for follow-up communication session from LMA.LMA is according to the client identification option in dhcp message, and whether identification is same user's Address requests, if same user, for MN distributes and switch front identical private ip v4 address.
It should be noted that, step S806 and step S808, step S812 etc. do not have clear and definite sequencing relation.
Step S808, in access authentication procedure, MAG2 knows that by relational approach MN only supports IPv4 protocol stack, for example, the IP protocol version that MAG2 obtains MN support from the policy profile of MN is IPv4 version.MAG2 is that MN sends PBU message to LMA, carries MN ID option, for identifying MN in this PBU message.
MAG2 carries the IPv4 NAT Home Address Request Option of a full 0 in PBU message, for asking to LMA, is that MN distributes a publicly-owned IPv4 address.MAG2 can be by newly-increased flag in PBU message (for example, in the field of IPv4 NAT Home Address Request Option and NAT Port Request Option, identify), show that NAT and MAG2 coexist, for example 1 represents that NAT and MAG2 coexist, and 0 represents there is no nat feature on MAG2.
MAG2 carries the NAT PortRequest Option of a full 0 in PBU, for asking to LMA, is that MN distributes No. port.
When follow-up MAG2 sends the PBU message upgraded to LMA, the IPv4NAT HomeAddress RequestOption in PBU and NAT Port Request Option can carry publicly-owned IPv4 address that LMA distributes and No. port.
Step S810, LMA receives after the PBU message that comes from MAG2, according to the switching indication option in PBU message, knows that MN is the switching of same interface between different MAG.
If carried the IPv4NAT HomeAddress Request Option of a full 0 and the NATPort Request Option of full 0 in PBU message, LMA continues as MN and distributes the previous publicly-owned address pool of (MN is under MAG1) IPv4 and several No. port.LMA must guarantee that the combination of this publicly-owned IPv4 address and No. port is not assigned to other terminal use.
The BCE of LMA maintenance update MN upgrades publicly-owned IPv4 home address and port information that MN distributes in BCE.
Step S812, LMA sends PBA message to MAG2, carries LMA and be publicly-owned IPv4 home address that MN distributes and No. port in PBA message.Publicly-owned IPv4 home address and carrying by IPv4NAT Home Address Request Option and NAT Port Reply Option respectively for No. port.
Follow-up, when LMA receives that coming from CN is sent to the message of MN, according to the destination address of message and destination slogan, E-Packet to corresponding MAG.
Step S814, MAG2 receives the PBA message that comes from LMA, it is the publicly-owned IPv4 home address that distributes of MN and No. port that MAG2 obtains LMA from IPv4NAT Home Address Request Option and NAT Port Reply Option.MAG2 is that MN creates BUL, and in BUL, adds the publicly-owned IPv4 home address of MN and No. port.
The NAT device binding DHCP server coexisting with MAG is that the IPv4 private address that distributes of MN and LMA are the publicly-owned IPv4 home address that distributes of MN, No. port.
When NAT receives the message that comes from MN, NAT device will come from source address and the source port number of MN message, converts LMA to and be publicly-owned IPv4 home address that MN distributes and No. port.
When NAT receives that coming from peer node is sent to LMA and is the message of the publicly-owned IPv4 home address that distributes of MN and No. port, NAT device converts the destination address of this message and destination slogan to private ip v4 address and the respective ends slogan of MN.
Address transition on NAT can be with reference to shown in figure 7.
Preferred embodiment three
What this preferred embodiment was described is that NAT and LMA coexist in situation, and when MN accesses certain MAG, PMIPv6 supports the mobile management flow process of IPv4.Fig. 9 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention three, as shown in Figure 9, comprises that following step S902 is to step S912.
Step S902, MN moves in PMIPv6 territory, access MAG1.
Step S904, MN initiates DHCPv4 address acquisition, obtains a privately owned IPv4 address, for follow-up communication session from DHCP Server.It should be noted that, step S904 and step S906, step S910 etc. do not have clear and definite sequencing relation.
Step S906, in access authentication procedure, MAG1 knows that by relational approach MN only supports IPv4 protocol stack, for example from the policy profile of MN, to obtain the IP protocol version that MN supports be IPv4 version to MAG1.MAG1 is that MN sends PBU message to LMA, carries MN ID option, for identifying MN in this PBA message.
In this preferred embodiment, MAG1 will carry the IPv4NAT Home Address Request Option of a full 0 in PBU, for asking to LMA, is that MN distributes a publicly-owned IPv4 home address.MAG1 can be by newly-increased flag in PBU message (for example, in the field of IPv4NAT Home Address Request Option and NAT PortRequest Option, identify), show that NAT and MAG1 coexist, for example 1 represents that NAT and MAG1 coexist, and 0 represents there is no nat feature on MAG1.
MAG1 carries the NAT PortRequest Option of a full 0 in PBU message, for asking to LMA, is that MN distributes No. port.
Step S908, LMA receives after the PBU message that comes from MAG, if in PBU message, carried the IPv4NAT Home Address Request Option of a full 0 and the NAT PortRequest Option of full 0 after, LMA is in the publicly-owned address pool of IPv4 and port pond (0 ~ 65535), for MN selects a publicly-owned IPv4 home address and several No. port, (LMA selects undefined and No. port of being used as far as possible, for example some are used by application-specific for No. port, should avoid selecting such No. port).LMA must guarantee that the combination of this publicly-owned IPv4 address and No. port is not assigned to other terminal use.
LMA is that MN creates corresponding BCE, is added to publicly-owned IPv4 home address that MN distributes and No. port in BCE.
Step S910, LMA sends PBA message to MAG1, can not carry LMA and be publicly-owned IPv4 home address that MN distributes and No. port in this PBA message.Publicly-owned IPv4 home address and carrying by IPv4NAT Home Address Request Option and NAT PortReply Option respectively for No. port.MAG1 receives the PBA message that comes from LMA.
Step S912, the NAT device coexisting with LMA binding LMA is that the IPv4 private address that distributes of MN and LMA are the publicly-owned IPv4 home address that distributes of MN, No. port.LMA can replace the MN in PBU that MN sends to identify by coming from the client identification in the DHCP request that MN sends and coming from MAG1, be defined as IPv4 private address that MN distributes and for the publicly-owned IPv4 home address of MN distribution, come from same mobile node No. port.
When NAT receives the message that comes from MN, by coming from the source address of MN message and source port number, to convert LMA to be the publicly-owned IPv4 home address that distributes of MN and No. port to NAT device.
When NAT receives that coming from peer node is sent to LMA and is the message of the publicly-owned IPv4 home address that distributes of MN and No. port, NAT device converts the destination address of this message and destination slogan to private ip v4 address and the respective ends slogan of MN.
Address transition on NAT as shown in Figure 7.
Preferred embodiment four
This preferred embodiment is described is NAT and LMA while coexisting, when MN switches between MAG, and the mobile management flow process of PMIPv6 support IPv4.Figure 10 is according to the interaction diagrams of the file transmitting method of the preferred embodiment of the present invention four, as shown in figure 10, comprises that following step S1002 is to step S1014.
Step S1002, MN moves to MAG2 from MAG1, and MN accesses MAG2.
Step S1004, MAG1 perception MN has left its link, and MAG1 sends logout message to LMA, nullifies MN in the relevant information of LMA.
Step S1006, MN initiates DHCPv4 address acquisition, obtains a privately owned IPv4 address, for follow-up communication session from LMA.Switch to after MAG2, LMA can still distribute and switch front identical private ip v4 address to MN, and for example, whether the client identification field in the DHCP request message sending by MN is identified is same client.It should be noted that, step S1006 and step S1008, step S1012 etc. do not have clear and definite sequencing relation.
Step S1008, in access authentication procedure, MAG2 knows that by relational approach MN only supports IPv4 protocol stack, for example from the policy profile of MN, to obtain the IP protocol version that MN supports be IPv4 version to MAG2.MAG2 is that MN sends PBU message to LMA, carries MN ID option, for identifying MN in message.
MAG2 will carry the IPv4NAT Home Address Request Option of a full 0 in PBU, for asking to LMA, is that MN distributes a publicly-owned IPv4 address.MAG2 can for example, by newly-increased flag (identifying in the field of IPv4NAT Home Address Request Option and NAT Port Request Option) in PBU message, show that NAT and MAG2 coexist, for example 1 represents that NAT and MAG2 coexist, and 0 represents there is no nat feature on MAG2.
MAG2 carries the NAT Port Request Option of a full 0 in PBU, for being No. port, one of MN distribution to LMA request.
Step S1010, LMA receives after the PBU message that comes from MAG2, according to switching indication option in PBU message, knows that MN is the switching of same interface between different MAG.
If carried the IPv4NAT Home Address Request Option of a full 0 and the NAT PortRequest Option of full 0 in PBU, LMA continues as MN and distributes the previous publicly-owned address pool of (MN is under MAG1) IPv4 and No. port.LMA must guarantee that the combination of this publicly-owned IPv4 address and No. port is not assigned to other terminal use.
The BCE of LMA maintenance update MN upgrades publicly-owned IPv4 home address and port information that MN distributes in BCE;
Step S1012, LMA sends PBA message to MAG2, can not carry LMA and be publicly-owned IPv4 home address that MN distributes and No. port in PBA message.Publicly-owned IPv4 home address and carrying by IPv4NAT Home AddressRequest Option and NAT PortReply Option respectively for No. port.MAG2 receives the PBA message that comes from LMA.
Step S1014, the NAT device coexisting with LMA binding LMA is that the IPv4 private address that distributes of MN and LMA are the publicly-owned IPv4 home address that distributes of MN, No. port.
When NAT receives the message that comes from MN, NAT device will come from source address and the source port number of MN message, converts LMA to and be publicly-owned IPv4 home address that MN distributes and No. port.
When NAT receives that coming from peer node is sent to LMA and is the message of the publicly-owned IPv4 home address that distributes of MN and No. port, NAT device converts the destination address of this message and destination slogan to private ip v4 address and the respective ends slogan of MN.
Address transition on NAT can be with reference to shown in figure 7.
It should be noted that, in the step shown in the flow chart of accompanying drawing, can in the computer system such as one group of computer executable instructions, carry out, and, although there is shown logical order in flow process, but in some cases, can carry out shown or described step with the order being different from herein.
The embodiment of the present invention also provides a kind of LMA, and this LMA can be for realizing above-mentioned file transmitting method.Figure 11 is according to the structured flowchart of the LMA of the embodiment of the present invention, and as shown in figure 11, this LMA comprises the first receiver module 1102, the first distribution module 1104 and sending module 1106.Below its structure is described in detail.
The first receiver module 1102, for receiving the request message from MAG, wherein, request message carries the request of publicly-owned IPv4 home address and port numbers request; The first distribution module 1104, is connected to the first receiver module 1102, for the request message receiving according to the first receiver module 1102, is that MN distributes publicly-owned IPv4 home address and the port numbers not being used; Sending module 1106, is connected to the first distribution module 1104, and for sending acknowledge message to MAG, wherein, acknowledge message carries publicly-owned IPv4 home address and the port numbers that the first distribution module 1104 is distributed.
Preferably, above-mentioned LMA also comprises: the second receiver module, the DHCP request sending for receiving MN; The second distribution module, is connected to the second receiver module, for LMA, is that MN distributes private ip v4 address.
Preferably, above-mentioned request message also carries MN sign, and above-mentioned LMA also comprises: creation module, be connected to the first distribution module 1104, and according to MN, be designated MN and create BCE; Add module, be connected to creation module, for adding publicly-owned IPv4 home address and port numbers to BCE.
Preferably, above-mentioned LMA also comprises: judge module, be connected to the first receiver module 1102, for the client identification carrying in the DHCP that MN identifies and MN the sends request of carrying according to request message, whether the MN of the MN of the judgement request publicly-owned IPv4 home address of distribution and port numbers and request distributing IP v4 private address is same MN; If same MN, LMA is that MN distributes publicly-owned IPv4 home address and the port numbers not being used.
Preferably, above-mentioned request message also carries indication message, above-mentioned LMA also comprises: know module, be connected to the first receiver module 1102, for the indication message of carrying from request message, know that MN is the switching that same interface carries out between different MAG.
Preferably, above-mentioned LMA also comprises: the 3rd receiver module, is connected to and knows module, the DHCP request sending for receiving MN; Determination module, is connected to the 3rd receiver module, for determining that according to the client identification of DHCP request MN sent DHCP request to LMA; The 3rd distribution module, is connected to determination module, is used to MN to distribute and switches front identical private ip v4 address.
Preferably, above-mentioned request message also carries MN sign, and above-mentioned LMA also comprises: the 4th distribution module, for being MN distribution according to request message and switching front identical publicly-owned IPv4 home address and port numbers; Update module, is connected to the 4th distribution module, for the BCE of MN being upgraded according to MN sign.
The embodiment of the present invention also provides a kind of transmitting system, is applied to exist between MAG and LMA the scene of NAT, and this transmitting system can be for realizing above-mentioned file transmitting method.Figure 12 is according to the structured flowchart of the transmitting system of the embodiment of the present invention, and as shown in figure 11, this transmitting system comprises: MN1202, MAG1204, LMA1206 and NAT1208.Below its structure is described in detail.
In correlation technique, when there is NAT between MAG and LMA in agreement RFC5844, and PMIPv6 does not propose the problem of effective solution for the support of IPv4.In the embodiment of the present invention, by LMA, be that MN distributes publicly-owned IPv4 home address and port numbers, follow-up while receiving message, NAT can change to E-Packet according to the address of distributing, thereby realized while there is NAT between MAG and LMA, PMIPv6, for the support of IPv4, has realized in PMIPv6 territory, supports the mobile management of IPv4 mobile terminal.
It should be noted that, the LMA describing in device embodiment and transmitting system are corresponding to above-mentioned embodiment of the method, and its concrete implementation procedure had been carried out detailed description in embodiment of the method, did not repeat them here.
In sum, according to the abovementioned embodiments of the present invention, a kind of file transmitting method, system and LMA are provided.The present invention is that MN distributes publicly-owned IPv4 home address and port numbers by LMA, follow-up while receiving message, NAT can change to E-Packet according to the address of distributing, thereby realized while there is NAT between MAG and LMA, PMIPv6 is for the support of IPv4, realized in PMIPv6 territory, supported the mobile management of IPv4 mobile terminal.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on the network that a plurality of calculation elements form, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in storage device and be carried out by calculation element, or they are made into respectively to each integrated circuit modules, or a plurality of modules in them or step are made into single integrated circuit module to be realized.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any modification of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (17)
1. a file transmitting method, is characterized in that, is applied to exist between Mobile Access Gateway MAG and local mobile anchor LMA the scene of network address translation NAT, and described method comprises:
LMA distributes publicly-owned IPv4 home address and port numbers for accessing the mobile node MN of the support IPv4 of MAG;
NAT carries out address transition according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN to the message receiving, and sends described message according to the address after conversion.
2. method according to claim 1, is characterized in that, LMA distributes publicly-owned IPv4 home address and port numbers to comprise for accessing the MN of the support IPv4 of MAG:
Described LMA receives the request message from described MAG, and wherein, described request message carries the request of publicly-owned IPv4 home address and port numbers request;
Described LMA is that described MN distributes publicly-owned IPv4 home address and the port numbers not being used according to described request message;
Described LMA sends acknowledge message to described MAG, and wherein, described acknowledge message carries described publicly-owned IPv4 home address and port numbers.
3. method according to claim 1, is characterized in that, according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN, the literary composition of SR is carried out to method described in address transition also comprise at NAT:
The DynamicHost that described LMA receives described MN transmission arranges protocol DHCP request;
Described LMA is that described MN distributes described private ip v4 address.
4. method according to claim 2, is characterized in that, described request message also carries MN sign, and before described LMA sends acknowledge message to described MAG, described method also comprises:
Described LMA is designated described MN according to described MN and creates banding cache entry BCE, and described publicly-owned IPv4 home address and port numbers are added in described BCE.
5. method according to claim 2, is characterized in that, is that before described MN distributes the publicly-owned IPv4 home address and port numbers not being used, described method also comprises at described LMA according to described request message:
Described LMA is according to the client identification carrying in the DHCP request of the MN sign of carrying in described request message and described MN transmission, and judgement request distributes whether the MN of publicly-owned IPv4 home address and port numbers and the MN of request distributing IP v4 private address are same MN;
If same MN, described LMA is that described MN distributes publicly-owned IPv4 home address and the port numbers not being used.
6. method according to claim 2, is characterized in that, at described LMA, after described MAG sends acknowledge message, described method also comprises:
Described MAG obtains described publicly-owned IPv4 home address and port numbers from the described acknowledge message receiving;
Described MAG is that described MN creates Binding Update list of entries BUL, and described publicly-owned IPv4 home address and port numbers are added in described BUL.
7. method according to claim 2, it is characterized in that, described request message also carries indication message, after described LMA receives the request message from described MAG, described method also comprises: the indication message that described LMA carries from described request message knows that described MN is the switching that same interface carries out between different MAG.
8. method claimed in claim 7, is characterized in that, before NAT carries out address transition according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN to the message receiving, described method also comprises:
Described LMA receives the DHCP request that described MN sends;
Described LMA determines that according to the client identification in described DHCP request described MN sent DHCP request to described LMA;
Described LMA is that described MN distributes and switches front identical private ip v4 address.
9. method according to claim 7, is characterized in that, described request message also carries MN sign, and before MAG described in described LMA sends acknowledge message, described method also comprises:
Described LMA is that described MN distributes and switches front identical publicly-owned IPv4 home address and port numbers according to described request message;
Described LMA upgrades the BCE of described MN according to described MN sign.
10. method according to claim 7, is characterized in that, at described LMA, after described MAG sends acknowledge message, described method also comprises:
Described MAG obtains described publicly-owned IPv4 home address and port numbers from the described acknowledge message receiving;
Described MAG is that described MN creates BUL, and described publicly-owned IPv4 home address and port numbers are added in described BUL.
11. according to the method described in any one in claim 2 to 10, it is characterized in that, described request message is agent binding update messages, and described acknowledge message is proxy binding acknowledgment messages.
12. according to the method described in any one in claim 2 to 10, it is characterized in that, in the request of described publicly-owned IPv4 home address or described port numbers request, carry and be used to indicate the sign whether described NAT coexists with described MAG, in the situation that described NAT and described MAG coexist, before NAT carries out address transition according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN to the message receiving, described method also comprises:
Described LMA gives described MAG by the message repeating receiving.
13. according to the method described in any one in claim 2 to 10, it is characterized in that, before NAT carries out address transition according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN to the message receiving, described method also comprises:
Described NAT binds described private ip v4 address and described publicly-owned IPv4 home address, port numbers.
14. according to the method described in any one in claim 2 to 10, it is characterized in that, NAT carries out address transition according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN to the message receiving and comprises:
Described NAT receives the message that comes from described MN;
Described NAT converts the source address of described message and source port number to described publicly-owned IPv4 home address and port numbers.
15. according to the method described in any one in claim 2 to 10, it is characterized in that, NAT carries out address transition according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN to the message receiving and comprises:
Described NAT receives the message that comes from the described publicly-owned IPv4 home address of being sent to of peer node and port numbers;
Described NAT converts the destination address of described message and destination slogan to private ip v4 address and the corresponding port numbers thereof of described MN.
16. 1 kinds of local mobile anchor LMA, is characterized in that, comprising:
Receiver module, for receiving the request message from Mobile Access Gateway MAG, wherein, described request message carries the request of publicly-owned IPv4 home address and port numbers request;
Distribution module, for according to described request message being publicly-owned IPv4 home address and the port numbers that mobile node MN distribution is not used;
Sending module, for sending acknowledge message to described MAG, wherein, described acknowledge message carries described publicly-owned IPv4 home address and port numbers.
17. 1 kinds of transmitting systems, is characterized in that, are applied to exist between Mobile Access Gateway MAG and local mobile anchor LMA the scene of network address translation NAT, and described system comprises: mobile node MN, MAG, LMA and NAT, wherein,
Described LMA comprises: distribution module, and be used to the described MN of the described MAG of access to distribute location, publicly-owned IPv4 local and port numbers, wherein, described MN supports IPv4;
Described NAT, coexists with described MAG or described LMA, comprising: modular converter, for the message receiving being carried out to address transition according to the private ip v4 address of described publicly-owned IPv4 home address and port numbers and described MN; Sending module, for sending described message according to the address after conversion.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210251144.5A CN103581346B (en) | 2012-07-19 | 2012-07-19 | File transmitting method, system and local mobile anchor |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210251144.5A CN103581346B (en) | 2012-07-19 | 2012-07-19 | File transmitting method, system and local mobile anchor |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103581346A true CN103581346A (en) | 2014-02-12 |
| CN103581346B CN103581346B (en) | 2019-06-18 |
Family
ID=50052254
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210251144.5A Active CN103581346B (en) | 2012-07-19 | 2012-07-19 | File transmitting method, system and local mobile anchor |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103581346B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1729460A1 (en) * | 2004-03-25 | 2006-12-06 | Matsushita Electric Industrial Co., Ltd. | Dynamic network management system, dynamic network management device, and dynamic network management method |
| CN101754168A (en) * | 2008-12-04 | 2010-06-23 | 中国移动通信集团公司 | Changing method between multiple interfaces of mobile node, Apparatus and system |
| CN101754173A (en) * | 2008-12-16 | 2010-06-23 | 中国移动通信集团公司 | Home address allocation, method and system for transmitting message by using same |
| CN101977246A (en) * | 2010-09-07 | 2011-02-16 | 南京中兴软件有限责任公司 | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility |
-
2012
- 2012-07-19 CN CN201210251144.5A patent/CN103581346B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1729460A1 (en) * | 2004-03-25 | 2006-12-06 | Matsushita Electric Industrial Co., Ltd. | Dynamic network management system, dynamic network management device, and dynamic network management method |
| CN101754168A (en) * | 2008-12-04 | 2010-06-23 | 中国移动通信集团公司 | Changing method between multiple interfaces of mobile node, Apparatus and system |
| CN101754173A (en) * | 2008-12-16 | 2010-06-23 | 中国移动通信集团公司 | Home address allocation, method and system for transmitting message by using same |
| CN101977246A (en) * | 2010-09-07 | 2011-02-16 | 南京中兴软件有限责任公司 | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103581346B (en) | 2019-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7929556B2 (en) | Method of private addressing in proxy mobile IP networks | |
| CN102106166B (en) | Anchoring services of a mobile station attached to a first service domain at a home agent in a second service domain | |
| CA2563911C (en) | System and method for providing ipv6 services | |
| US6862274B1 (en) | Method and system capable of providing mobility support for IPv4/IPv6 inter-networking | |
| RU2409907C2 (en) | Internet protocol combination and mobility method | |
| US6845094B1 (en) | Network address translation based internet protocol mobility | |
| EP1665714B1 (en) | Reachability maintainance of a moving network based on temporary name identifiers | |
| CN101621785A (en) | Registration, communication and switching method of mobile nodes and device thereof | |
| CN101855882A (en) | Mobile ip route optimization in ip version transition scenarios | |
| US20070088853A1 (en) | Communication method between IPv6 mobile node and IPv4-based node using DSTM in MIPv6 environment | |
| EP1139634A2 (en) | Transcient tunneling for dynamic home addressing on mobile hosts | |
| US9326125B2 (en) | Device and method for realizing identity and locator separation network | |
| CN101977246B (en) | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility | |
| CN101483636B (en) | Method, system, customer terminal for mobile IP establishment, and anchor point management apparatus | |
| CN103581346A (en) | Message sending method, message sending system and local mobility anchor | |
| CN101754173B (en) | Home address allocation, method and system for transmitting message by using same | |
| KR101314883B1 (en) | Method for vertical handover in heterogeneous wireless internet service network | |
| Yan et al. | Performance study of the dual‐stack mobile IP protocols in the evolving mobile internet | |
| EP2568715A1 (en) | Mobile node, care of address acquisition method and system thereof, and dhcp server | |
| KR20040066432A (en) | Method for Mobility Support using Mobile IP In Networks | |
| Wakikawa et al. | The applicability of virtual interface for inter‐technology handoffs in Proxy Mobile IPv6 | |
| KR100848456B1 (en) | Apparatus and method for address registration of mobile nodes based on wireless broadband access network | |
| Zhou et al. | Network-based mobility management for LISP network | |
| CN100466609C (en) | Method for implementing communication of IPv6 mobile node and IPv4 communication buddy | |
| KR20080002076A (en) | Wireless internet connection system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |