CN103581346B - File transmitting method, system and local mobile anchor - Google Patents
File transmitting method, system and local mobile anchor Download PDFInfo
- Publication number
- CN103581346B CN103581346B CN201210251144.5A CN201210251144A CN103581346B CN 103581346 B CN103581346 B CN 103581346B CN 201210251144 A CN201210251144 A CN 201210251144A CN 103581346 B CN103581346 B CN 103581346B
- Authority
- CN
- China
- Prior art keywords
- address
- lma
- publicly
- message
- 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.)
- Active
Links
Abstract
The invention discloses a kind of file transmitting method, system and LMA, applied to the scene between MAG and LMA there are NAT, this method comprises: LMA is the publicly-owned IPv4 home address of MN distribution and port numbers for accessing the support IPv4 of MAG；NAT carries out address conversion to the message received according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN, and sends message according to the address after conversion.The present invention is that MN distributes publicly-owned IPv4 home address and port numbers by LMA, when subsequently received message, NAT can be converted according to the address of distribution to E-Packet, to realize between MAG and LMA, there are when NAT, support of the PMIPv6 for IPv4, it realizes in the domain PMIPv6, supports the mobile management of IPv4 mobile terminal.
Description
Technical field
The present invention relates to the communications fields, in particular to a kind of file transmitting method and system and local mobile anchor.
Background technique
Internet protocol version 4(Internet Protocol version6, referred to as IPv4) to Internet protocol version
This 6(Internet Protocol version6, referred to as IPv6) transition be a long-term process, cross and tide at this
Cheng Zhong, IPv6 and IPv4 agreement will all use in identical network structure.Therefore the MN in the domain PMIPv6 may be in IPv4-
It is operated under only, IPv6-only or double mode stacks, and Mobile Access Gateway (Mobile Access Gateway, letter
Referred to as MAG) with local mobile anchor (Local MobilityAnchor, referred to as LMA) between network may be an IPv4
Or the network of IPv6.Therefore, regardless of transmission network is IPv4 or IPv6 network, identical mobility entity in the domain PMIPv6
It requires to provide movement for the mobile node (Mobile Node, referred to as MN) of IPv4-only, IPv6-only or double mode stacks
Property management, realize MN in moving process, the holding of conversation continuity.
Fig. 1 is the network architecture schematic diagram that IPv4 is supported according to the PMIPv6 of the relevant technologies, under scene shown in Fig. 1
Mobile management problem, request for comments (Request For Comments, referred to as RFC) 5844(IPv4Support for
Proxy Mobile IPv6) propose between a kind of MAG and LMA that there is no network address translation (Network Address
Translation, referred to as NAT) when, the support in the domain PMIPv6 for IPv4.HoA is home address (Home in Fig. 1
Address) CoA is Care-of Address (Care-ofAddress).
In RFC5844:
(1) all mobility entities, LMA and MAG support double stacks, and LMA and MAG can be with configuration of IP v4 and/or IPv6
Address.
(2) regardless of the type of transmission network, the mobile management signaling between MAG and LMA is all based on IPv6's.
(3) MN by this agreement support obtain LMA for its distribution IPv4 home address (Home Address, referred to as
HoA).
In this agreement, tool of the proxy mobile IPv 6 (Proxy Mobile IPv6, referred to as PMIPv6) to the support of IPv4
Body process (without NAT between MAG and LMA) is as shown in Fig. 2, include the following steps:
Step S202 supports the MN of IPv4 to be moved in the domain PMIPv6, first completion access authentication procedure.In access authentication
In the process, MAG obtains the IP agreement version that MN is supported from the strategy file (policy profile) of MN, such as MN is supported
IPv4 or IPv6.
Step S204, MAG support type according to the IP agreement version of MN, initiate agency of trademark registration process.If MN is IPv4 section
Point, then MAG carried in agent binding update (Proxy Binding Update, referred to as PBU) message of initiation full 0 or
IPv4 home address request comprising MN IPv4 home address selects (IPv4Home Address Request Option), uses
In generation or the IPv4 home address of renewed treaty MN.
Step S206, after LMA receives PBU message, the banding cache entry (Banding of creation or update about MN
Cache Entry, referred to as BCE), compared to PMIPv6, the IPv4 home address that MN is increased in the BCE of MN is (including corresponding
Subnet mask), distribution to MN IPv4 default router address.And in the PBA for being back to MAG, by the local IPv4
Location response selection (IPv4HomeAddress Reply Option) carries the IPv4 home address of MN.
Step S208, MAG receive agent binding confirmation (the Proxy Binding from LMA
Acknowledgement, referred to as PBA) after message, list of entries (Banding Update is updated in the binding about MN
List Entry, referred to as BUL) in increase the IPv4 home address (including subnet mask) and MN for distributing to MN connecting interface
IPv4 default router address (selects (IPv4Default-RouterAddress by the IPv4 mistake routing address in PBA
Option it) obtains).In addition, IPv4DHCP supports the S mark in model selection (IPv4DHCP Support Mode option)
Position indicates that MAG is as dhcp response agency (DHCP Relay Agent) or DHCP server.
Step S210, MN by DynamicHost be arranged agreement (Dynamic Host Configuration Protocol,
Referred to as DHCP) process obtain LMA be MN distribution IPv4 home address.
Tunnel packet between LMA and MAG can use IPv4-or-IPv6-over-IPv6, IPv4-or-IPv6-over-
The tunnel styles such as IPv4 are packaged.
With the fast development of mobile Internet, the mobile Internet from smart phone and other mobile terminals is connect
Enter, accelerating exhausting for the address IPv4, can not be all one unique public networks of mobile terminal configuration in existing net
The address IPv4.A kind of method for mitigating the problem is exactly multiple terminal configurations address private ip v4, shares one in network communications
A publicly-owned address IPv4.Therefore, in the actual deployment of network, NAT can be disposed in the interface of private and public network, into
The conversion of the private and public address IPv4 of row.
But agreement RFC5844 is to, there are when NAT, PMIPv6 does not propose the support of IPv4 between MAG and LMA
Effective solution scheme, so needing to propose a kind of scheme to solve the problems, such as the mobile management in the scene.
Summary of the invention
The present invention provides a kind of file transmitting method, system and LMA, at least to solve in the related technology, agreement
RFC5844 is to, there are when NAT, PMIPv6 is asked for what the support of IPv4 was not put forward effective solutions between MAG and LMA
Topic.
According to an aspect of the invention, there is provided a kind of file transmitting method, applied between MAG and LMA, there are NAT's
Scene, this method comprises: LMA is the publicly-owned IPv4 home address of shifting MN distribution and port numbers for accessing the support IPv4 of MAG；NAT
Address conversion is carried out to the message received according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN,
And message is sent according to the address after conversion.
Preferably, LMA is the publicly-owned IPv4 home address of MN distribution for accessing the support IPv4 of MAG and port numbers include: LMA
Receive the request message from MAG, wherein request message carries publicly-owned IPv4 home address request and port numbers request；
LMA is according to the publicly-owned IPv4 home address and port numbers that request message is that MN distribution is not used by；LMA sends confirmation to MAG and disappears
Breath, wherein confirmation message carries publicly-owned IPv4 home address and port numbers.
Preferably, in NAT according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to receiving
Message carry out address conversion before, the above method further include: LMA receive MN transmission DynamicHost setting protocol DHCP asks
It asks；LMA is that MN distributes the address private ip v4.
Preferably, above-mentioned request message also carries MN mark, before LMA sends confirmation message to MAG, the above method
Further include: LMA is identified as MN creation BCE according to MN, and publicly-owned IPv4 home address and port numbers are added in BCE.
Preferably, LMA according to request message be the MN publicly-owned IPv4 home address that is not used by of distribution and port numbers it
Before, the above method further include: the client carried in the DHCP request that LMA is sent according to the MN mark and MN that carry in request message
End identifies, and whether judges the MN for requesting the MN of the publicly-owned IPv4 home address of distribution and port numbers and request to distribute IPv4 private address
It is same MN；If it is same MN, LMA is the publicly-owned IPv4 home address and port numbers that MN distribution is not used by.
Preferably, after LMA sends confirmation message to MAG, the above method further include: MAG is from received confirmation message
It is middle to obtain publicly-owned IPv4 home address and port numbers；MAG is that MN creates BUL, and publicly-owned IPv4 home address and port numbers are added
It is added in BUL.
Preferably, above-mentioned request message also carries indication message, receives the request message from MAG in LMA
Later, the above method further include: the indication message that LMA is carried from request message knows that MN is same interface in difference
The switching carried out between MAG.
Preferably, in NAT according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to receiving
Message carry out address conversion before, the above method further include: LMA receive MN transmission DHCP request；LMA is asked according to DHCP
Client identification in asking determines that MN is transmitted across DHCP request to LMA；LMA is that MN is distributed with identical private ip v4 before switching
Location.
Preferably, above-mentioned request message also carries MN mark, before LMA sends confirmation message to MAG, the above method
Further include: LMA is that MN is distributed and identical publicly-owned IPv4 home address and port numbers before switching according to request message；LMA according to
MN mark is updated the BCE of MN.
Preferably, after LMA sends confirmation message to MAG, the above method further include: MAG is from received confirmation message
It is middle to obtain publicly-owned IPv4 home address and port numbers；MAG is that MN creates BUL, and publicly-owned IPv4 home address and port numbers are added
It is added in BUL.
Preferably, above-mentioned request message is agent binding update messages, and above-mentioned confirmation message is proxy binding acknowledgment messages.
Preferably, carry whether be used to indicate NAT total with MAG in publicly-owned IPv4 home address request or port numbers request
The mark deposited, in the case where NAT and MAG coexist, in NAT according to the private of publicly-owned IPv4 home address and port numbers and MN
Before thering is the address IPv4 to carry out address conversion to the message received, the above method further include: LMA forwards the message received
To MAG.
Preferably, in NAT according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to receiving
Message carry out address conversion before, the above method further include: NAT is with binding the address private ip v4 and the publicly-owned local IPv4
Location, port numbers.
Preferably, NAT is according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to receiving
It includes: that NAT receives message from MN that message, which carries out address conversion,；NAT converts the source address of message and source port number
At publicly-owned IPv4 home address and port numbers.
Preferably, NAT is according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to receiving
It includes: that NAT is received and is sent to publicly-owned IPv4 home address and port numbers from peer node that message, which carries out address conversion,
Message；NAT by the destination address of message and destination slogan be converted into MN the address private ip v4 and its corresponding port numbers.
According to another aspect of the present invention, a kind of LMA is provided, comprising: receiving module, for receiving asking from MAG
Seek message, wherein request message carries publicly-owned IPv4 home address request and port numbers request；Distribution module is used for basis
Request message is the publicly-owned IPv4 home address and port numbers that MN distribution is not used by；Sending module confirms for sending to MAG
Message, wherein confirmation 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, there are NAT's applied between MAG and LMA
Scene, the system include: MN, MAG, LMA and NAT, wherein LMA includes: distribution module, is distributed for the MN to access MAG public
There are IPv4 home address and port numbers, wherein MN supports IPv4；NAT coexists with MAG or LMA, comprising: conversion module is used for
Address conversion is carried out to the message received according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN；
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, and when subsequently received message, NAT can
Converted with the address according to distribution to E-Packet, to realize between MAG and LMA there are when NAT, PMIPv6 for
The support of IPv4 realizes in the domain PMIPv6, support the mobile management of IPv4 mobile terminal.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes part of this application, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 is the network architecture schematic diagram that IPv4 is supported according to the PMIPv6 of the relevant technologies；
Fig. 2 is the interaction diagrams that IPv4 is supported according to the PMIPv6 of the relevant technologies；
Fig. 3 is the flow chart of file transmitting method according to an embodiment of the present invention；
Fig. 4 is the schematic diagram of NAT according to an embodiment of the present invention Yu MAG coexistence scenario；
Fig. 5 is the schematic diagram of NAT according to an embodiment of the present invention Yu LMA coexistence scenario；
Fig. 6 is the interaction diagrams of the file transmitting method of preferred embodiment one according to the present invention；
Fig. 7 is the schematic diagram of NAT address translation process according to the preferred embodiment of the invention；
Fig. 8 is the interaction diagrams of the file transmitting method of preferred embodiment two according to the present invention；
Fig. 9 is the interaction diagrams of the file transmitting method of preferred embodiment three according to the present invention；
Figure 10 is the interaction diagrams of the file transmitting method of preferred embodiment four according to the present invention；
Figure 11 is the structural block diagram of LMA according to an embodiment of the present invention；
Figure 12 is the structural block diagram of transmitting system according to an embodiment of the present invention.
Specific embodiment
It should be noted that in the absence of conflict, the features in the embodiments and the embodiments of the present application can phase
Mutually combination.The present invention will be described in detail below with reference to the accompanying drawings and embodiments.
The embodiment of the invention provides a kind of file transmitting methods, applied to the scene between MAG and LMA there are NAT, Fig. 3
It is the flow chart of file transmitting method according to an embodiment of the present invention, as shown in figure 3, including the following steps, namely S302 to step
S304。
Step S302, LMA are the publicly-owned IPv4 home address of MN distribution and port numbers for accessing the support IPv4 of MAG.
Step S304, NAT are according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to receiving
Message carry out address conversion, and according to after conversion address send message.
In the related technology, agreement RFC5844 between MAG and LMA there are when NAT, PMIPv6 for IPv4 support not
The problem of putting forward effective solutions.It is that MN distributes publicly-owned IPv4 home address and end by LMA in the embodiment of the present invention
Slogan, when subsequently received message, NAT can be converted according to the address of distribution to E-Packet, thus realize MAG with
There are when NAT between LMA, support of the PMIPv6 for IPv4 realizes in the domain PMIPv6, supports the shifting of IPv4 mobile terminal
Dynamic management.The above-mentioned port numbers for MN distribution can be one, be also possible to multiple.
Preferably, step S302 includes: that LMA receives the request message from MAG, wherein request message carries public affairs
There are IPv4 home address request and port numbers request；LMA is that MN distributes the publicly-owned local IPv4 being not used by according to request message
Address and port numbers；LMA sends confirmation message to MAG, wherein confirmation message carries publicly-owned IPv4 home address and port
Number.The publicly-owned IPv4 home address and port numbers being not used by for MN distribution, can be to avoid the conflict of subsequent generation.
Before NAT carries out address conversion according to the address private ip v4 and publicly-owned IPv4 home address, port numbers, LMA
Distribute private address to MN, can be realized by following operation: LMA receives the DHCP request of MN transmission；LMA is that MN distribution is private
There is the address IPv4.
It should be noted that distribution private address, publicly-owned address and port numbers do not distinguish sequencing.
Above-mentioned request message can also carry MN mark, and before LMA sends confirmation message to MAG, the above method is also
Including: LMA is identified as MN creation banding cache entry BCE according to MN, and publicly-owned IPv4 home address and port numbers are added to
In BCE.
In order to guarantee that publicly-owned IPv4 home address and port numbers and the address private ip v4 of distribution are for the same MN
, before the LMA publicly-owned IPv4 home address being not used by according to request message for MN distribution and port numbers, the above method is also
It include: the client identification carried in DHCP request of the LMA according to the MN mark and MN transmission that are carried in request message, judgement is asked
Whether seek the MN of the MN for distributing publicly-owned IPv4 home address and port numbers and request distribution IPv4 private address is same MN；If
It is same MN, LMA is the publicly-owned IPv4 home address and port numbers that MN distribution is not used by.
After LMA sends confirmation message to MAG, the above method further include: MAG obtains public affairs from received confirmation message
There are IPv4 home address and port numbers；MAG is that MN creation binding updates list of entries BUL, and by publicly-owned IPv4 home address and
Port numbers are added in BUL.
The case where being switched to another MAG from a MAG for MN, above-mentioned request message also carry switching instruction letter
Breath, after LMA receives the request message from MAG, the above method further include: the switching that LMA is carried from request message
Instruction information knows that MN is the switching that same interface carries out between different MAG.This preferred embodiment makes LMA know that MN is cut
Another MAG is changed to, to provide foundation for subsequent allocations address, for example, distributing and identical address before switching for MN.
(1) address private ip v4 is distributed for MN
In NAT according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to the message received
Before carrying out address conversion, the above method further include: LMA receives the DHCP request of MN transmission；LMA is according in DHCP request
Client identification determines that MN is transmitted across DHCP request to LMA；LMA is that MN is distributed and switched the preceding address identical private ip v4.
(2) publicly-owned IPv4 home address and port numbers are distributed for MN
Above-mentioned request message also carries MN mark, before LMA sends confirmation message to MAG, the above method further include:
LMA is that MN is distributed and identical publicly-owned IPv4 home address and port numbers before switching according to request message；LMA is according to MN mark pair
The BCE of MN is updated.
The case where being switched to MAG for MN, MAG need to create BUL for MN, store publicly-owned IPv4 home address and the end of MN
Slogan, after LMA sends confirmation message to MAG, the above method further include: MAG obtains publicly-owned from received confirmation message
IPv4 home address and port numbers；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 confirmation message is proxy binding acknowledgment messages.
Preferably, carry whether be used to indicate NAT total with MAG in publicly-owned IPv4 home address request or port numbers request
The mark deposited, in the case where NAT and MAG coexist, in NAT according to the private of publicly-owned IPv4 home address and port numbers and MN
Before thering is the address IPv4 to carry out address conversion to the message received, the above method further include: LMA forwards the message received
To MAG.In this preferred embodiment, whether coexisted with MAG using mark instruction NAT, when can be subsequently received message,
The operation that LMA is carried out provides an intuitive foundation.
It is as follows for the address translation operation of NAT:
In NAT according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN to the message received
Before carrying out address conversion, NAT binds the address private ip v4 and publicly-owned IPv4 home address, port numbers.
NAT receives the message from MN；The source address of message and source port number are converted into the publicly-owned local IPv4 by NAT
Address and port numbers.NAT receives the message for being sent to publicly-owned IPv4 home address and port numbers from peer node；
NAT by the destination address of message and destination slogan be converted into MN the address private ip v4 and its corresponding port numbers.
In a preferred embodiment, when supporting the MN of IPv4 to be moved in the domain PMIPv6 of NAT scene, MAG is to LMA
PBU message is sent, which carries the request of IPv4 network address conversion port number and publicly-owned IPv4 home address request.LMA
It is the group of publicly-owned IPv4 home address and port numbers that MN distribution is not used by according to the PBU message after receiving PBU message
It closes, and the DHCP server coexisted with LMA is that MN distributes the address private ip v4.The NAT coexisted with MAG or LMA is according to above-mentioned
The address of distribution and port number information carry out address conversion to the message of contact MN.
When supporting the MN of IPv4 to switch between the MAG in the domain PMIPv6 of NAT scene, MAG sends PBU message to LMA, should
PBU message carries the request of IPv4 network address conversion port number and publicly-owned IPv4 home address request.After LMA receives PBU, according to
The PBU message, the combination of publicly-owned IPv4 home address and port numbers before continuing as MN distribution switching, keeps switching front and back,
It is constant for the publicly-owned IPv4 home address of MN distribution and the combination of port numbers；The DHCP server coexisted simultaneously with LMA is according to MN
The address identical private ip v4 before being identified as MN distribution and switching.The NAT coexisted with MAG or LMA is according to the address of above-mentioned distribution
And port number information, address conversion is carried out to the message of contact MN.
In order to keep technical solution of the present invention and implementation method clearer, below in conjunction with preferred embodiment in fact
Existing process is described in detail.
In embodiments of the present invention, when there are when NAT, the mobile management of IPv4 is supported in PMIPv6 between MAG and LMA
Two kinds of scenes can be divided into, it is as shown in Figure 4 and Figure 5 respectively.
Fig. 4 is the schematic diagram of NAT according to an embodiment of the present invention Yu MAG coexistence scenario, as shown in figure 4, in this scene,
NAT coexists with MAG function.For example, the DHCP server coexisted with LMA is that MN distributes IPv4 demesne when MN accesses MAG1
Location, MN use this private address to be communicated as source address.When MN is moved in the domain PMIPv6, after MN accesses MAG2, with
The DHCP server that LMA coexists continues as MN and distributes one and identical IPv4 private address before switching.
Fig. 5 is the schematic diagram of NAT according to an embodiment of the present invention Yu LMA coexistence scenario, as shown in figure 5, in this scene,
NAT coexists with LMA function.For example, the DHCP server coexisted with LMA is that MN distributes IPv4 demesne when MN accesses MAG1
Location, MN use this private address to be communicated as source address.When MN is moved in the domain PMIPv6, MN can keep from
It is obtained at the DHCP server that LMA coexists and switches preceding identical IPv4 private address.
Preferred embodiment one
This preferred embodiment describes under NAT and MAG Coexistence Situation, and when MN accesses some MAG, PMIPv6 is supported
The mobile management process of IPv4.Fig. 6 is the interaction diagrams of the file transmitting method of preferred embodiment one according to the present invention, such as
Shown in Fig. 6, include the following steps, namely S602 to step S612.
Step S602, MN are moved in the domain PMIPv6, access MAG1.
Step S604, MN initiate the address DHCPv4 and obtain, from DHCP server(Fig. 6 and subsequent drawings with DHCP-S table
Show DHCP server) a privately owned address IPv4 is obtained, it is used for subsequent communication session.In this preferred embodiment, LMA with
DHCP server coexists.It should be noted that step S604(obtains the address private ip v4) and step S606, step S610 etc.
There is no specific sequencing relationship.
Step S606, in access authentication procedure, MAG1 knows that MN only supports IPv4 protocol stack, example by relational approach
Such as, it is IPv4 version that MAG1 obtains the IP agreement version of MN support from the policy profile of MN.MAG1 is that MN sends PBU
Message carries MN ID option, for identifying MN to LMA in the PBU message.
In this preferred embodiment, MAG1 carries the IPv4NAT Home Address an of full 0 in PBU message
RequestOption, for being that MN distributes a publicly-owned IPv4 home address to LMA request.MAG1 can be by disappearing in PBU
Marker is increased in breath newly (for example, in IPv4NAT Home Address Request Option and NAT Port Request
Identified in the field of Option), show that NAT coexists with MAG1, such as 1 expression NAT and MAG1 coexists, and does not have on 0 expression MAG1
Nat feature.
MAG1 carries the NAT Port Request Option an of full 0 in PBU message, for being MN to LMA request
It distributes port (port) number.
IPv4NAT Home Address when subsequent MAG1 sends the PBU message that updates to LMA, in PBU message
Request Option and NAT Port Request Option can carry the publicly-owned address IPv4 that LMA is distributed and No. port.
Step S608, LMA is received after the PBU message of MAG1, if carrying a full 0 in PBU message
The NAT PortRequest Option of IPv4NAT Home Address Request Option and full 0, then LMA is in IPv4
In publicly-owned address pool and the pond port (0 ~ 65535), a publicly-owned IPv4 home address and several No. port are selected for MN
(LMA selects undefined and be not used by No. port as far as possible, such as some No. port are used by specific application, and selection should be avoided
Such No. port).LMA must assure that this publicly-owned address IPv4 and several No. port combinations were not previously allocated to other ends
End subscriber.
LMA is that MN creates corresponding BCE, and publicly-owned IPv4 home address and No. port that MN is distributed are added in BCE, real
Existing above- mentioned information and MN are identified and the binding of the address MAG.
Step S610, LMA send PBA message to MAG1, carry the publicly-owned IPv4 family that LMA is MN distribution in the PBA message
Township address and No. port.Publicly-owned IPv4 home address and No. port pass through IPv4NAT Home Address Request respectively
Option and NAT PortReply Option is carried.
It is subsequent, the report of MN is sent to from peer node (Correspondent Node, referred to as CN) when LMA is received
Wen Shi, according to the destination address and destination slogan of message, LMA E-Packets to corresponding MAG.
The dhcp message that LMA is sent by the MN-ID option and MN that carry in PBU message is (in order to obtaining private ip v4
Location) in carry client option, come identify judge request agency mobile management service client and request IPv4 it is privately owned
Whether the client of address is same client, if it is, distributing address and sending PBA message.It should be noted that this two
Network Access Identifier (Network Access Identifier, referred to as NAI) or device link layer mark can be used in a option
Know symbol.
Step S612, MAG1 receive the PBA message from LMA, and MAG1 is from IPv4NAT Home Address
In Request Option and NAT Port Reply Option obtain LMA be MN distribution publicly-owned IPv4 home address and
No. port.MAG1 be MN create BUL, and in BUL add MN publicly-owned IPv4 home address and No. port.
The NAT device binding DHCP server coexisted with MAG1 is the IPv4 private address of MN distribution and LMA is MN distribution
Publicly-owned IPv4 home address, No. port.
When NAT is received from the message of MN, NAT device by from the source address and source port number of the message of MN,
Being converted into LMA is the publicly-owned IPv4 home address and No. port that MN is distributed.
The publicly-owned IPv4 home address and No. port that LMA is MN distribution are sent to from peer node when NAT is received
When message, the destination address of this message and destination slogan are converted into IPv4 private address and the corresponding port of MN by NAT device
Number.
Fig. 7 is the schematic diagram of NAT address translation process according to the preferred embodiment of the invention, as shown in fig. 7, CN is opposite end
Node, Src indicate source, and Dst indicates purpose, and top half describes NAT and receives the processed of message from MN in Fig. 7
Journey: after NAT is received from the message of MN, NAT by the source address of message and source port number substitute for LMA be MN distribute public affairs
There are IPv4 home address and port numbers.Lower half portion describes NAT and receives the treatment process for being sent to the message of MN in Fig. 7: when
When NAT receives the message for being sent to MN, the destination address of message and destination slogan are replaced with the address private ip v4 of MN by NAT
With corresponding port numbers.
Preferred embodiment two
This preferred embodiment describes NAT and when MAG coexists, and when MN switches between MAG, PMIPv6 supports IPv4's
Mobile management process.Fig. 8 is the interaction diagrams of the file transmitting method of preferred embodiment two according to the present invention, such as Fig. 8 institute
Show, includes the following steps, namely S802 to step S814.
Step S802, MN are moved under 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 phase of LMA
Close information.
Step S806, MN initiate the address DHCPv4 and obtain, and obtain from LMA and switch the preceding address identical private ip v4, use
In subsequent communication session.LMA identifies whether it is that the address of same user asks according to the client identification option in dhcp message
It asks, if same user, then distributes for MN and switch the preceding address identical private ip v4.
It should be noted that step S806 and step S808, step S812 etc. are without specific sequencing relationship.
Step S808, in access authentication procedure, MAG2 knows that MN only supports IPv4 protocol stack, example by relational approach
Such as, it is IPv4 version that MAG2 obtains the IP agreement version of MN support from the policy profile of MN.MAG2 is that MN sends PBU
Message carries MN ID option, for identifying MN to LMA in the PBU message.
MAG2 carries the IPv4 NAT Home Address Request Option an of full 0 in PBU message, is used for
It is that MN distributes a publicly-owned address IPv4 to LMA request.MAG2 can by PBU message increase newly marker (for example,
Identified in the field of IPv4 NAT Home Address Request Option and NAT Port Request Option), table
Bright NAT and MAG2 coexists, such as 1 expression NAT and MAG2 coexists, and 0 indicates no nat feature on MAG2.
MAG2 carries the NAT PortRequest Option an of full 0 in PBU, for being that MN is distributed to LMA request
No. port.
IPv4NAT HomeAddress when subsequent MAG2 sends the PBU message that updates to LMA, in PBU
RequestOption and NAT Port Request Option can carry the publicly-owned address IPv4 that LMA is distributed and No. port.
Step S810, LMA are received after the PBU message of MAG2, are indicated option according to the switching in PBU message, are obtained
Know that MN is switching of the same interface between different MAG.
If carrying the IPv4NAT HomeAddress Request Option and full 0 of a full 0 in PBU message
NATPort Request Option, then LMA continue as MN distribution previous (MN is at MAG1) if the publicly-owned address pool of IPv4 and
Dry No. port.LMA must assure that this publicly-owned address IPv4 and No. port combination are not previously allocated to other terminal users.
LMA maintenance updates the BCE of MN, and the publicly-owned IPv4 home address and port information of MN distribution are updated in BCE.
Step S812, LMA send PBA message to MAG2, carry the publicly-owned local IPv4 that LMA is MN distribution in PBA message
Address and No. port.Publicly-owned IPv4 home address and No. port pass through IPv4NAT Home Address Request respectively
Option and NAT Port Reply Option is carried.
It is subsequent, when LMA receives the message for being sent to MN from CN, according to the destination address and destination port of message
Number, it E-Packets to corresponding MAG.
Step S814, MAG2 receive the PBA message from LMA, and MAG2 is from IPv4NAT Home Address
In Request Option and NAT Port Reply Option obtain LMA be MN distribution publicly-owned IPv4 home address and
No. port.MAG2 be MN create BUL, and in BUL add MN publicly-owned IPv4 home address and No. port.
The NAT device binding DHCP server coexisted with MAG is the IPv4 private address of MN distribution and LMA is MN distribution
Publicly-owned IPv4 home address, No. port.
When NAT is received from the message of MN, NAT device turns from the source address and source port number of MN message
Change the publicly-owned IPv4 home address and No. port that LMA is MN distribution into.
The publicly-owned IPv4 home address and No. port that LMA is MN distribution are sent to from peer node when NAT is received
When message, the destination address of this message and destination slogan are converted into the address private ip v4 and corresponding port of MN by NAT device
Number.
Address conversion on NAT can be with reference to shown in Fig. 7.
Preferred embodiment three
This preferred embodiment describes under NAT and LMA Coexistence Situation, and when MN accesses some MAG, PMIPv6 is supported
The mobile management process of IPv4.Fig. 9 is the interaction diagrams of the file transmitting method of preferred embodiment three according to the present invention, such as
Shown in Fig. 9, include the following steps, namely S902 to step S912.
Step S902, MN are moved in the domain PMIPv6, access MAG1.
Step S904, MN initiate the address DHCPv4 and obtain, and obtain the privately owned address IPv4 from DHCP Server, use
In subsequent communication session.It should be noted that step S904 and step S906, step S910 etc. are without specific sequencing
Relationship.
Step S906, in access authentication procedure, MAG1 knows that MN only supports IPv4 protocol stack by relational approach, such as
The IP agreement version that MAG1 obtains MN support from the policy profile of MN is IPv4 version.MAG1 is that MN transmission PBU disappears
Breath carries MN ID option, for identifying MN to LMA in the PBA message.
In this preferred embodiment, MAG1 will carry the IPv4NAT Home Address Request an of full 0 in PBU
Option, for being that MN distributes a publicly-owned IPv4 home address to LMA request.MAG1 can be by new in PBU message
Increase marker (for example, IPv4NAT Home Address Request Option and NAT PortRequest Option's
Identified in field), show that NAT coexists with MAG1, such as 1 expression NAT and MAG1 coexists, 0 indicates no nat feature on MAG1.
MAG1 carries the NAT PortRequest Option an of full 0 in PBU message, for being MN to LMA request
Distribution port.
Step S908, LMA is received after the PBU message of MAG, if carrying a full 0 in PBU message
After the IPv4NAT Home Address Request Option and NAT PortRequest Option of full 0, then LMA exists
In the publicly-owned address pool of IPv4 and the pond port (0 ~ 65535), a publicly-owned IPv4 home address and several port are selected for MN
Number (LMA selects undefined and used No. port as far as possible, such as some No. port are used by specific application, and selection should be avoided
Such No. port).LMA must assure that this publicly-owned address IPv4 and No. port combination are not previously allocated to other terminals and use
Family.
LMA is that MN creates corresponding BCE, and publicly-owned IPv4 home address and No. port that MN is distributed are added in BCE.
Step S910, LMA send PBA message to MAG1, and can not carry LMA in the PBA message is the publicly-owned of MN distribution
IPv4 home address and No. port.Publicly-owned IPv4 home address and No. port pass through IPv4NAT Home Address respectively
Request Option and NAT PortReply Option is carried.MAG1 receives the PBA message from LMA.
Step S912, the NAT device binding LMA coexisted with LMA is the IPv4 private address of MN distribution and LMA is MN distribution
Publicly-owned IPv4 home address, No. port.LMA by client identification in the DHCP request that MN is sent and can come
From the MN mark in the PBU that MAG1 replaces MN to send, come the public affairs for being determined as the IPv4 private address of MN distribution and being distributed for MN
Have that IPv4 home address, No. port from same mobile node.
When NAT is received from the message of MN, NAT device will be from the source address of MN message and source port number conversion
At the publicly-owned IPv4 home address that LMA is MN distribution and No. port.
The publicly-owned IPv4 home address and No. port that LMA is MN distribution are sent to from peer node when NAT is received
When message, the destination address of this message and destination slogan are converted into the address private ip v4 and corresponding port of MN by NAT device
Number.
Address conversion on NAT is as shown in Figure 7.
Preferred embodiment four
This preferred embodiment describes NAT and when LMA coexists, and when MN switches between MAG, PMIPv6 supports IPv4's
Mobile management process.Figure 10 is the interaction diagrams of the file transmitting method of preferred embodiment four according to the present invention, such as Figure 10
It is shown, include the following steps, namely S1002 to step S1014.
Step S1002, MN are moved under 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 LMA's
Relevant information.
Step S1006, MN initiate the address DHCPv4 and obtain, and the privately owned address IPv4 are obtained from LMA, for subsequent
Communication session.After switching to MAG2, LMA can be distributed still and be switched the preceding address identical private ip v4 to MN, for example, passing through
The client identification field in DHCP request message that MN is sent identifies whether it is same client.It should be noted that step
Rapid S1006 and step S1008, step S1012 etc. are without specific sequencing relationship.
Step S1008, in access authentication procedure, MAG2 knows that MN only supports IPv4 protocol stack, example by relational approach
If the MAG2 IP agreement version for obtaining MN support from the policy profile of MN is IPv4 version.MAG2 is that MN sends PBU
Message carries MN ID option, for identifying MN to LMA in message.
MAG2 will carry the IPv4NAT Home Address Request Option an of full 0 in PBU, for
LMA request is that MN distributes a publicly-owned address IPv4.MAG2 can by PBU message increase newly marker (such as
Identified in the field of IPv4NAT Home Address Request Option and NAT Port Request Option), table
Bright NAT and MAG2 coexists, such as 1 expression NAT and MAG2 coexists, and 0 indicates no nat feature on MAG2.
MAG2 carries the NAT Port Request Option an of full 0 in PBU, for being that MN is distributed to LMA request
One No. port.
Step S1010, LMA are received after the PBU message of MAG2, according to switching instruction option in PBU message, are known
MN is switching of the same interface between different MAG.
If carrying the NAT of IPv4NAT Home the Address Request Option and full 0 of a full 0 in PBU
PortRequest Option, then LMA continues as the previous publicly-owned address pool of (MN is at MAG1) IPv4 of MN distribution and No. port.
LMA must assure that this publicly-owned address IPv4 and No. port combination are not previously allocated to other terminal users.
LMA maintenance updates the BCE of MN, and the publicly-owned IPv4 home address and port information of MN distribution are updated in BCE；
Step S1012, LMA send PBA message to MAG2, and can not carry LMA in PBA message is the publicly-owned of MN distribution
IPv4 home address and No. port.Publicly-owned IPv4 home address and No. port pass through IPv4NAT Home respectively
AddressRequest Option and NAT PortReply Option is carried.MAG2 receives the PBA message from LMA.
Step S1014, the NAT device binding LMA coexisted with LMA is the IPv4 private address of MN distribution and LMA is MN points
The publicly-owned IPv4 home address matched, No. port.
When NAT is received from the message of MN, NAT device turns from the source address and source port number of MN message
Change the publicly-owned IPv4 home address and No. port that LMA is MN distribution into.
The publicly-owned IPv4 home address and No. port that LMA is MN distribution are sent to from peer node when NAT is received
When message, the destination address of this message and destination slogan are converted into the address private ip v4 and corresponding port of MN by NAT device
Number.
Address conversion on NAT can be with reference to shown in Fig. 7.
It should be noted that step shown in the flowchart of the accompanying drawings can be in such as a group of computer-executable instructions
It is executed in computer system, although also, logical order is shown in flow charts, and it in some cases, can be with not
The sequence being same as herein executes shown or described step.
The embodiment of the invention also provides a kind of LMA, the LMA can be used to implement above-mentioned file transmitting method.Figure 11 is
The structural block diagram of LMA according to an embodiment of the present invention, as shown in figure 11, the LMA are distributed including the first receiving module 1102, first
Module 1104 and sending module 1106.Its structure is described in detail below.
First receiving module 1102, for receiving the request message from MAG, wherein request message carries publicly-owned
IPv4 home address request and port numbers request；First distribution module 1104 is connected to the first receiving module 1102, is used for basis
The received request message of first receiving module 1102 is the publicly-owned IPv4 home address and port numbers that MN distribution is not used by；It sends
Module 1106 is connected to the first distribution module 1104, for sending confirmation message to MAG, wherein confirmation message carries first
The publicly-owned IPv4 home address and port numbers that distribution module 1104 is distributed.
Preferably, above-mentioned LMA further include: the second receiving module, for receiving the DHCP request of MN transmission；Second distribution mould
Block is connected to the second receiving module, is that MN distributes the address private ip v4 for LMA.
Preferably, above-mentioned request message also carries MN mark, above-mentioned LMA further include: creation module is connected to first point
With module 1104, MN creation BCE is identified as according to MN；Adding module is connected to creation module, for by the publicly-owned local IPv4
Location and port numbers are added in BCE.
Preferably, above-mentioned LMA further include: judgment module is connected to the first receiving module 1102, for according to request message
The client identification carried in the DHCP request that the MN mark and MN of middle carrying are sent judges request with distributing the publicly-owned local IPv4
Whether the MN of the MN of location and port numbers and request distribution IPv4 private address is same MN；It is MN distribution if it is same MN, LMA
The publicly-owned IPv4 home address and port numbers being not used by.
Preferably, above-mentioned request message also carries indication message, above-mentioned LMA further include: knows module, is connected to
First receiving module 1102, the indication message for carrying from request message know that MN is same interface in different MAG
Between the switching that carries out.
Preferably, above-mentioned LMA further include: third receiving module is connected to and knows module, for receiving the DHCP of MN transmission
Request；Determining module is connected to third receiving module, for determining that MN is sent out to LMA according to the client identification in DHCP request
Pass through DHCP request；Third distribution module, is connected to determining module, for distributing with identical private ip v4 before switching for MN
Location.
Preferably, above-mentioned request message also carries MN mark, above-mentioned LMA further include: the 4th distribution module is used for basis
Request message is that MN is distributed and switched preceding identical publicly-owned IPv4 home address and port numbers；Update module is connected to the 4th point
With module, for being updated according to MN mark to the BCE of MN.
The embodiment of the invention also provides a kind of transmitting systems should applied to the scene between MAG and LMA there are NAT
Transmitting system can be used to implement above-mentioned file transmitting method.Figure 12 is transmitting system according to an embodiment of the present invention
Structural block diagram, as shown in figure 11, which includes: MN1202, MAG1204, LMA1206 and NAT1208.Below
Its structure is described in detail.
LMA 1206 includes: distribution module 12062, for distributing publicly-owned IPv4 family for the MN 1202 of access MAG 1204
Township address and port numbers, wherein MN 1202 supports IPv4；NAT 1208 coexists with MAG 1204 or LMA 1206, comprising: turns
Change the mold block 12082, for according to the address private ip v4 of publicly-owned IPv4 home address and port numbers and MN 1202 to reception
The message arrived carries out address conversion；Sending module 12084 is connected to conversion module 12082, for according to conversion module 12082
Address after conversion sends message.
In the related technology, agreement RFC5844 between MAG and LMA there are when NAT, PMIPv6 for IPv4 support not
The problem of putting forward effective solutions.It is that MN distributes publicly-owned IPv4 home address and end by LMA in the embodiment of the present invention
Slogan, when subsequently received message, NAT can be converted according to the address of distribution to E-Packet, thus realize MAG with
There are when NAT between LMA, support of the PMIPv6 for IPv4 realizes in the domain PMIPv6, supports the shifting of IPv4 mobile terminal
Dynamic management.
It should be noted that LMA and transmitting system described in Installation practice correspond to above-mentioned method reality
Example is applied, concrete implementation process had carried out detailed description in embodiment of the method, and details are not described herein.
In conclusion according to the abovementioned embodiments of the present invention, a kind of file transmitting method, system and LMA are provided.This hair
Bright by LMA is that MN distributes publicly-owned IPv4 home address and port numbers, and when subsequently received message, NAT can be according to distribution
Address is converted to E-Packet, to realize between MAG and LMA support of the PMIPv6 for IPv4 there are when NAT, i.e.,
It realizes in the domain PMIPv6, supports the mobile management of IPv4 mobile terminal.
Obviously, those skilled in the art should be understood that each module of the above invention or each step can be with general
Computing device realize that they can be concentrated on a single computing device, or be distributed in multiple computing devices and formed
Network on, optionally, they can be realized with the program code that computing device can perform, it is thus possible to which they are stored
Be performed by computing device in the storage device, perhaps they are fabricated to each integrated circuit modules or by they
In multiple modules or step be fabricated to single integrated circuit module to realize.In this way, the present invention is not limited to any specific
Hardware and software combines.
The foregoing is only a preferred embodiment of the present invention, is not intended to restrict the invention, for the skill of this field
For art personnel, the invention may be variously modified and varied.All within the spirits and principles of the present invention, made any to repair
Change, equivalent replacement, improvement etc., should all be included in the protection scope of the present invention.
Claims (16)
1. a kind of file transmitting method, which is characterized in that deposited applied between Mobile Access Gateway MAG and local mobile anchor LMA
In the scene of network address translation NAT, which comprises
LMA is the publicly-owned IPv4 home address of mobile node MN distribution and port numbers for accessing the support IPv4 of MAG；
NAT is according to the address private ip v4 of the publicly-owned IPv4 home address and port numbers and the MN to the report received
Text carries out address conversion, and sends the message according to the address after conversion；
Wherein, LMA is the publicly-owned IPv4 home address of MN distribution for accessing the support IPv4 of MAG and port numbers include: that the LMA connects
Receive the request message from the MAG, wherein the request message carries publicly-owned IPv4 home address request and port numbers
Request；The LMA is according to the publicly-owned IPv4 home address and port numbers that the request message is that MN distribution is not used by；Institute
It states LMA and sends confirmation message to the MAG, wherein the confirmation message carries the publicly-owned IPv4 home address and port
Number；
Wherein, in the LMA according to the publicly-owned IPv4 home address and end that the request message is that MN distribution is not used by
Before slogan, the method also includes: the LMA is sent according to the MN mark carried in the request message and the MN
The client identification carried in DHCP request judges that request distributes MN and the request distribution of publicly-owned IPv4 home address and port numbers
Whether the MN of IPv4 private address is same MN；If it is same MN, the LMA is not used by publicly-owned for MN distribution
IPv4 home address and port numbers.
2. the method according to claim 1, wherein in NAT according to the publicly-owned IPv4 home address and port
Number and the MN the address private ip v4 address conversion is carried out to the message that receives before, the method also includes:
The LMA receives the DynamicHost setting protocol DHCP that the MN is sent and requests；
The LMA is that the MN distributes the address the private ip v4.
3. the method according to claim 1, wherein the request message also carries MN mark, in the LMA
Before sending confirmation message to the MAG, the method also includes:
The LMA is identified as the MN according to the MN and creates banding cache entry BCE, and by the publicly-owned IPv4 home address
It is added in the BCE with port numbers.
4. the method according to claim 1, wherein the LMA to the MAG send confirmation message after,
The method also includes:
The MAG obtains the publicly-owned IPv4 home address and port numbers from the received confirmation message；
The MAG is that MN creation binding updates list of entries BUL, and the publicly-owned IPv4 home address and port numbers are added
It is added in the BUL.
5. the method according to claim 1, wherein the request message also carries indication message,
After the LMA receives the request message from the MAG, the method also includes: the LMA is from the request message
The indication message of carrying knows that the MN is the switching that same interface carries out between different MAG.
6. according to the method described in claim 5, it is characterized in that, in NAT according to the publicly-owned IPv4 home address and port
Number and the MN the address private ip v4 address conversion is carried out to the message that receives before, the method also includes:
The LMA receives the DHCP request that the MN is sent；
The LMA determines that the MN is transmitted across DHCP request to the LMA according to the client identification in the DHCP request；
The LMA is that the MN is distributed and switched the preceding address identical private ip v4.
7. according to the method described in claim 5, it is characterized in that, the request message also carries MN mark, in the LMA
Before sending confirmation message to the MAG, the method also includes:
The LMA is that the MN is distributed and identical publicly-owned IPv4 home address and port before switching according to the request message
Number；
The LMA is updated the BCE of the MN according to MN mark.
8. according to the method described in claim 5, it is characterized in that, the LMA to the MAG send confirmation message after,
The method also includes:
The MAG obtains the publicly-owned IPv4 home address and port numbers from the received confirmation message；
The MAG is that the MN creates BUL, and the publicly-owned IPv4 home address and port numbers are added in the BUL.
9. according to claim 2, method described in any one of 4 to 8, which is characterized in that the request message is agent binding
Update message, the confirmation message are proxy binding acknowledgment messages.
10. described according to the method described in claim 3, it is characterized in that, the request message is agent binding update messages
Confirmation message is proxy binding acknowledgment messages.
11. the method according to any one of claim 2 to 8, which is characterized in that the publicly-owned IPv4 home address request
Or carried in the port numbers request and be used to indicate the mark whether NAT coexists with the MAG, in the NAT and institute
It states in the case that MAG coexists, in NAT according to the private ip v4 of the publicly-owned IPv4 home address and port numbers and the MN
Before address carries out address conversion to the message received, the method also includes:
The message received is transmitted to the MAG by the LMA.
12. the method according to any one of claim 2 to 8, which is characterized in that in NAT according to the publicly-owned IPv4 family
Before the address private ip v4 of township address and port numbers and the MN carry out address conversion to the message received, the side
Method further include:
The binding address the private ip v4 NAT and the publicly-owned IPv4 home address, port numbers.
13. the method according to any one of claim 2 to 8, which is characterized in that NAT is according to the publicly-owned local IPv4
The address private ip v4 of address and port numbers and the MN carry out address conversion to the message received
The NAT receives the message from the MN；
The source address of the message and source port number are converted into the publicly-owned IPv4 home address and port numbers by the NAT.
14. the method according to any one of claim 2 to 8, which is characterized in that NAT is according to the publicly-owned local IPv4
The address private ip v4 of address and port numbers and the MN carry out address conversion to the message received
The NAT receives the message for being sent to publicly-owned the IPv4 home address and port numbers from peer node；
The destination address of the message and destination slogan are converted into the address private ip v4 and its correspondence of the MN by the NAT
Port numbers.
15. a kind of local mobile anchor LMA characterized by comprising
Receiving module, for receiving the request message from Mobile Access Gateway MAG, wherein the request message carries public affairs
There are IPv4 home address request and port numbers request；
Distribution module, for according to the request message be the mobile node MN publicly-owned IPv4 home address that is not used by of distribution and
Port numbers；
Sending module, for sending confirmation message to the MAG, wherein the confirmation message carries the publicly-owned IPv4 family
Township address and port numbers；
Wherein, it is carried in the DHCP request that the LMA is sent according to the MN mark carried in the request message and the MN
Client identification judges that request distributes the MN of publicly-owned IPv4 home address and port numbers and the MN of request distribution IPv4 private address
It whether is same MN；If it is same MN, the LMA is the publicly-owned IPv4 home address and port that MN distribution is not used by
Number.
16. a kind of transmitting system, which is characterized in that deposited applied between Mobile Access Gateway MAG and local mobile anchor LMA
In the scene of network address translation NAT, the system comprises: mobile node MN, MAG, LMA and NAT, wherein
The LMA includes: distribution module, for the publicly-owned IPv4 home address of MN distribution and the port to access the MAG
Number, wherein the MN supports IPv4；Wherein, the LMA is sent according to the MN mark carried in request message and the MN
The client identification carried in DHCP request judges that request distributes MN and the request distribution of publicly-owned IPv4 home address and port numbers
Whether the MN of IPv4 private address is same MN；If it is same MN, the LMA is not used by publicly-owned for MN distribution
IPv4 home address and port numbers；
Wherein, the distribution module is also used to: receiving the request message from the MAG, wherein the request message carries
There are publicly-owned IPv4 home address request and port numbers request；According to the request message be the MN distribution be not used by it is publicly-owned
IPv4 home address and port numbers；Confirmation message is sent to the MAG, wherein the confirmation message carries described publicly-owned
IPv4 home address and port numbers
The NAT coexists with the MAG or the LMA, comprising: conversion module, for according to the publicly-owned IPv4 home address
Address conversion is carried out to the message received with the address private ip v4 of port numbers and the MN；Sending module is used for basis
Address after conversion sends the message.
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 CN103581346A (en) | 2014-02-12 |
| CN103581346B true 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) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1729460A4 (en) * | 2004-03-25 | 2009-12-09 | Panasonic Corp | Dynamic network management system, dynamic network management device, and dynamic network management method |
| CN101754168B (en) * | 2008-12-04 | 2012-09-19 | 中国移动通信集团公司 | Method, device and system for switching among multiple interfaces of mobile node |
| CN101754173B (en) * | 2008-12-16 | 2013-03-13 | 中国移动通信集团公司 | Home address allocation, method and system for transmitting message by using same |
| CN101977246B (en) * | 2010-09-07 | 2014-03-12 | 南京中兴软件有限责任公司 | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility |
-
2012
- 2012-07-19 CN CN201210251144.5A patent/CN103581346B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN103581346A (en) | 2014-02-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101653546B1 (en) | Method of private addressing in proxy mobile ip networks | |
| CN103442347B (en) | Mobile node, home agent and redirect method | |
| CN101448252B (en) | Network switching implementation method, system thereof and mobile nodes | |
| JP4430106B2 (en) | System and method for providing IPv6 service | |
| EP2011300B1 (en) | Ip mobility within a communication system | |
| Ferretti et al. | A survey on handover management in mobility architectures | |
| CN101383755B (en) | Proxy mobile IPv6 switching method and related network entity | |
| CN101803329A (en) | Detection of mobility functions implemented in a mobile node | |
| US20060280146A1 (en) | Handover support for multiple types of traffic | |
| KR20150074220A (en) | System and protocols for inter-mobility access gateway tunneling for fast handoff transition | |
| US20130176943A1 (en) | System and Method for Distributed Mobility Management | |
| CN101977246B (en) | Method and system for supporting PMIPv6 (Proxy Mobile IPv6) mobility | |
| Muslam et al. | Network-based mobility and host identity protocol | |
| Giust et al. | HDMM: deploying client and network-based distributed mobility management: A hybrid approach | |
| CN101998566B (en) | Method and device for switching mobile access gateway (MAG) in proxy mobile Internet protocol (PMIP) | |
| CN103581346B (en) | File transmitting method, system and local mobile anchor | |
| Louin et al. | Network and host based distributed mobility | |
| WO2010000188A1 (en) | A method and apparatus for realizing handover between mobility management domains | |
| JP2009095034A (en) | Mobility managing method and mobile terminal | |
| Wakikawa et al. | The applicability of virtual interface for inter‐technology handoffs in Proxy Mobile IPv6 | |
| KR20040089203A (en) | The Mobility Management Method and System using SIP protocol and SIP Mobility Agent in Wireless Communication Networks | |
| Ren et al. | Implementation and test of PMIPv6 dual stack protocol | |
| Yunjing et al. | A novel mobility management mechanism based on destination address overwritten and id/locator separation | |
| EP2568715A1 (en) | Mobile node, care of address acquisition method and system thereof, and dhcp server | |
| Lee et al. | Network independent mobility management scheme using virtual IP addressing |
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 |