CN107040616A - The conversion method and packet sending and receiving method of TCP/DN/IP Web-compatible TCP/IP networks - Google Patents
The conversion method and packet sending and receiving method of TCP/DN/IP Web-compatible TCP/IP networks Download PDFInfo
- Publication number
- CN107040616A CN107040616A CN201610081189.0A CN201610081189A CN107040616A CN 107040616 A CN107040616 A CN 107040616A CN 201610081189 A CN201610081189 A CN 201610081189A CN 107040616 A CN107040616 A CN 107040616A
- Authority
- CN
- China
- Prior art keywords
- address
- tcp
- domain name
- message
- pseudo
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
- H04L61/3025—Domain name generation or assignment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5061—Pools of addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses the conversion method and packet sending and receiving method of TCP/DN/IP Web-compatible TCP/IP networks, the message that can send application program encapsulates the transparent translation between TCP/DN/IP encapsulation in TCP/IP.Its technical scheme is：By designing encapsulation/decapsulation flow different from OSI network model; utilize dummy address technology; the IP messages that application program is sent pellucidly are converted to the message of TCP/DN/IP encapsulation format; so as to normally be forwarded between the different IP domains in TCP/DN/IP protocol definitions, and in receiving terminal normal reduction.It can so allow TCP/DN/IP agreements to be applied to carry traditional web application realized based on TCP/IP completely compatiblely, allow escalation process to become extremely smooth.
Description
Technical field
The present invention relates to Internet technology, more particularly to the related technology of IP network address spatial spread.
Background technology
IPv4 is originally the network designed for US military, only with the address of 32 bits, is accommodated up to less than 4,300,000,000
Main frame.With the rapid extension of IP network, IPv4 addresses are exhausted.
Industry has successively introduced the problem of NAT technologies and IPv6 technologies are to solve address shortage.But NAT technologies destroy net
The symmetry of network, and IPv6 faces huge difficulty because of incompatible with existing network in popularization.
《Telecommunication science》The article that 8th periodical in 2014 is stepped on《Dual network layered scheme --- brand-new Next Generation Internet solution
Certainly scheme》Describe the scheme of a brand-new solution IPv4 address shortage.This scheme passes through the Longitudinal Extension on IP protocol stack
Go out new level, the highly compatible to existing IPv4 networks can be kept while unlimited address is expanded, be can yet be regarded as one
Solve the good scheme of the not enough problem in the IPv4 network address.
But this scheme there is also an issue：When ISP is upgraded to the new IP domains of TCP/DN/IP protocol requirements, because
Limited for main flow type of operating system, main frame easily can be upgraded to TCP/DN/IP agreements by updating operation in the domain
Application software species on stack, but main frame is various, it is generally difficult to all update in a short time, and no longer someone safeguards for part
Application software even can not will upgrade to support TCP/DN/IP protocol stacks forever.Fail answering for upgrading in TCP/DN/IP networks
The main frame overseas with current IP can not be accessed, thus objectively still have the problem of upgrading not smooth enough.
Specifically, in the Open System Interconnection reference model OSI that International Organization for standardization ISO is designed, network is divided
For 7 layers.Data are transmitted successively when sending from high level to low layer, and the content that upper strata is sent all is considered as data by every layer, are added certainly
Transmitted again to low layer on oneself head.In receiving terminal, data are transmitted from low layer to high level, after this layer of additional head is divested every time
Give upper strata.
The communication process of typical ICP/IP protocol is as shown in Figure 1.On implementing, due to frequent in network access
Host domain name is used on ground, and application program needs voluntarily to translate domain names into as IP by DNS, then by IP, transport layer protocol type
The transmission function of operating system protocol stack offer is provided to the data for needing to send.Operating system protocol stack is opened up according in Fig. 1
The principle shown successively encapsulated message head and sends message.
TCP/DN/IP agreements with the addition of UDP header and the header of a domain name layer in stack.Main frame is in assembly
, it is necessary to insert the domain name of destination host during the domain name layer header of TCP/DN/IP messages, therefore function is sent in design agreement stack
When, it is necessary to allow using directly transmitting the domain name, transport layer protocol type and user data of destination host as parameter.And message
After IP network layer is delivered to from domain name Internet, it is still desirable to translate domain names into as IP address to insert the target of IP headers
Address field.The letter of gethostbyname classes should be now directly invoked in IP network layer by the network protocol stack of operating system
Number is translated domain names into as IP address.
Fig. 2A and 2B show the internal flow chart of standard type TCP/DN/IP agreement stack functions.Please referring also to Fig. 2A and
Send () function in 2B, figure refers to all of network protocol stack offer and possesses the function for sending message function.In this flow chart
Consider the situation that user directly uses IP address as object invocation function.If user is called using IP address, Huo Zhejing
Cross after domain name mapping and find that destination host is not yet upgraded, then still select traditional TCP/IP packing forms.Only in user
It is called using domain name, and in the case that destination host is promoted, can just selects TCP/DN/IP encapsulation.
But, the packaged type of this standard has a problem that：Transmission function based on ICP/IP protocol stack and it is based on
The interface of the transmission function of TCP/DN/IP protocol stacks is different.TCP/DN/IP protocol stacks require that application program is passed when calling
Enter destination host domain name and non-ip address.If the incoming only IP address of application program, then protocol stack will be because of missing
Domain-name information and domain name layer can not be filled and (especially, have substantial amounts of multiple domain names under TCP/DN/IP frameworks to be resolved to
Same IP situation).Traditional web application based on TCP/IP will be unable to be carried on TCP/DN/IP networks.
The content of the invention
The brief overview of one or more aspects given below is to provide to the basic comprehension in terms of these.This general introduction is not
The extensive overview of all aspects contemplated, and it is also non-to be both not intended to identify the key or decisive key element of all aspects
Attempt to define the scope in terms of any or all.Its unique purpose is to provide the one of one or more aspects in simplified form
A little concepts think the sequence of more detailed description given later.
It is an object of the invention to solve the above problems, there is provided a kind of TCP/DN/IP Web-compatibles TCP/IP networks
Conversion method, file transmitting method and message method of reseptance, the message that application program can be sent TCP/IP encapsulation and
Transparent translation between TCP/DN/IP encapsulation.
The technical scheme is that：Present invention is disclosed a kind of conversion of TCP/DN/IP Web-compatibles TCP/IP networks
Method, including application program send the flow of message and the flow of application program reception message, wherein：
The flow that application program sends message includes：
Application call system protocol stack is IP address by dns resolution destination host domain name, and protocol stack is parsed
And check analysis result, if the result returned shows that destination host is not upgraded, or it is promoted but with where application program
Main frame be in identical IP domains, then return to the obtained IP address of parsing to application program；Otherwise, according to destination host domain name and
The IP address that parsing is obtained inquires about correspondence list item in address translation table, first divides if in the absence of correspondence list item from dummy address pond
With a untapped pseudo- IP address, and the IP that newly-increased one obtains including destination host domain name, parsing in address translation table
Address and the list item of newly assigned pseudo- IP address, and the result of pseudo- IP address as the DNS query is returned into application program；
When application program sends message, protocol stack is by the destination host IP address in IP headers and address translation table
Pseudo- IP address row are compared, and ICP/IP protocol stack encapsulated message is used if in the absence of correspondence list item, if it there is correspondence list item from
Destination host domain name and the parsing IP address of destination host are taken out in the correspondence list item, domain name layer header is added to message and inserts
Destination host domain name, adds UDP heads, IP header destination addresses is changed to the parsing IP address of destination host domain name；
The message for carrying out bottom is sent；
The flow that application program receives message includes：
Application program receives the message from bottom；
Protocol stack judges whether message is TCP/DN/IP encapsulation, if not TCP/DN/IP encapsulation then directly carries out standard IP
The reception of message；
If TCP/DN/IP is encapsulated, then：
From domain name layer extraction source host domain name and the source host domain name is parsed so as to obtaining corresponding IP address, or directly
Source IP address is extracted from IP layers as the parsing IP address of source host domain name；
Source host domain name is searched in address translation table, wherein corresponding pseudo- IP address is taken out if it there is corresponding entry,
Increase a list item newly in address translation table if in the absence of corresponding entry, content includes：Newly assigned one from dummy address pond
Individual untapped pseudo- IP address, the source host domain name extracted from domain name layer, and IP address is parsed accordingly；And
The TCP/DN/IP encapsulation in message is removed, the message received is reduced into standard IP messages and by source IP address
It is changed to corresponding newly assigned pseudo- IP address；
Message is submitted to application program by protocol stack.
According to an embodiment of the conversion method of the TCP/DN/IP Web-compatible TCP/IP networks of the present invention, dummy address pond
It is made up of the pseudo- IP address that will not be truly used for network access, the list item of address translation table includes pseudo- IP address, domain name and parsing
IP address, using address translation table and its pseudo- IP address, is carried when message is extended into TCP/DN/DP encapsulation by TCP/IP encapsulation
For correct destination host domain name.
According to an embodiment of the conversion method of the TCP/DN/IP Web-compatible TCP/IP networks of the present invention, if using journey
The message that sequence is sent carries source host IP address in application layer, then the address conversion is source host before being issued by message
Domain name addresses, wherein being adjusted to message format to ensure that receiving terminal reduces the address information of application layer, mesh is reached in message
The domain name addresses in application layer is converted back into pseudo- IP address using address translation table after mark main frame.
According to an embodiment of the conversion method of the TCP/DN/IP Web-compatible TCP/IP networks of the present invention, address conversion
Table deletes the list item not used based on time aging mechanism.
Present invention further teaches a kind of file transmitting method in TCP/DN/IP Web-compatible TCP/IP networks, including：
Application call system protocol stack is IP address by dns resolution destination host domain name, and protocol stack is parsed
And check analysis result, if the result returned shows that destination host is not upgraded, or it is promoted but with where application program
Main frame be in identical IP domains, then return to the obtained IP address of parsing to application program, otherwise,
Corresponding list item is inquired about in address translation table with the IP address that parsing is obtained according to destination host domain name, if being not present
Corresponding to list item and a untapped pseudo- IP address is then first distributed from dummy address pond, and increase one newly in address translation table includes
The list item of destination host domain name, the IP address that parsing is obtained and newly assigned pseudo- IP address, and the pseudo- IP address is looked into as DNS
The result of inquiry returns to application program；
When application program sends message, protocol stack is by the destination host IP address in IP headers and address translation table
Pseudo- IP address row are compared, and ICP/IP protocol stack encapsulated message is used if in the absence of correspondence list item, if it there is correspondence list item from
Destination host domain name and the parsing IP address of destination host are taken out in the correspondence list item, domain name layer header is added to message and inserts
Destination host domain name, adds UDP heads, IP header destination addresses is set to the parsing IP address of destination host domain name；
The message for carrying out bottom is sent.
According to an embodiment of the file transmitting method in TCP/DN/IP Web-compatible TCP/IP networks of the present invention,
Dummy address pond is made up of the pseudo- IP address that will not be truly used for network access, and the list item of address translation table includes pseudo- IP address, domain
Name and parsing IP address, using address translation table and its pseudo- IP address, TCP/DN/DP is being extended to by message by TCP/IP encapsulation
Correct destination host domain name is provided during encapsulation.
According to an embodiment of the file transmitting method in TCP/DN/IP Web-compatible TCP/IP networks of the present invention,
Address translation table deletes the list item not used based on time aging mechanism.
Present invention further teaches a kind of message method of reseptance in TCP/DN/IP Web-compatible TCP/IP networks, including：
Application program receives the message from bottom；
Protocol stack judges whether message is TCP/DN/IP encapsulation, if not TCP/DN/IP encapsulation then directly carries out standard IP
The reception of message；
If TCP/DN/IP is encapsulated, then：
From domain name layer extraction source host domain name and the domain name is parsed so as to obtaining corresponding IP address, or directly from IP layers
Source IP address is extracted as the parsing IP address of source host domain name；
Source host domain name is searched in address translation table, wherein corresponding pseudo- IP address is taken out if it there is corresponding entry,
Increase a list item newly in address translation table if in the absence of corresponding entry, content includes：Newly assigned one from dummy address pond
Individual untapped pseudo- IP address, the source host domain name extracted from domain name layer, and IP address is parsed accordingly；And
The TCP/DN/IP encapsulation in message is removed, the message received is reduced into standard IP messages and by source IP address
It is changed to corresponding newly assigned pseudo- IP address；
Message is submitted to application program by protocol stack.
According to an embodiment of the message method of reseptance in TCP/DN/IP Web-compatible TCP/IP networks of the present invention,
Dummy address pond is made up of the pseudo- IP address that will not be truly used for network access, and the list item of address translation table includes pseudo- IP address, domain
Name and parsing IP address, using address translation table and its pseudo- IP address, TCP/DN/DP is being extended to by message by TCP/IP encapsulation
Correct destination host domain name is provided during encapsulation.
According to an embodiment of the message method of reseptance in TCP/DN/IP Web-compatible TCP/IP networks of the present invention,
Address translation table deletes the list item not used based on time aging mechanism.
Present invention contrast prior art has following beneficial effect：The present invention is by designing different from OSI network model
Encapsulation/decapsulation flow, using dummy address and address translation table technology, the IP messages that application program is sent pellucidly are converted to
The message of TCP/DN/IP encapsulation format, so as to normally be forwarded between the different IP domains in TCP/DN/IP protocol definitions,
And in receiving terminal normal reduction.The transformation mechanism suitable for ALG is have also contemplated that simultaneously.The present invention this ICP/IP protocol and
The method of transparent bi-directional conversion between TCP/DN/IP agreements, can allow TCP/DN/IP agreements to be applied to carrying completely compatiblely and pass
The web application realized based on TCP/IP of system, allows escalation process to become extremely smooth.
Brief description of the drawings
Fig. 1 shows that standard ICP/IP protocol stack encapsulates flow chart.
Fig. 2A and 2B show the internal flow chart of standard type TCP/DN/IP agreement stack functions.
Fig. 3 shows that standard type TCP/DN/IP protocol stacks encapsulate flow chart.
Fig. 4 shows that compatible type TCP/DN/IP protocol stacks encapsulate flow chart.
Fig. 5 A and 5B show the internal flow chart of compatible type TCP/DN/IP agreement stack functions.
Fig. 6 shows the preferable of the file transmitting method in TCP/DN/IP Web-compatible TCP/IP networks of the present invention
The flow chart of embodiment.
Fig. 7 shows the preferable of the message method of reseptance in TCP/DN/IP Web-compatible TCP/IP networks of the present invention
The flow chart of embodiment.
Fig. 8 shows that client TCP/IP applications access the schematic diagram of TCP/DN/IP main frames.
Fig. 9 shows that service end TCP/IP applications receive the schematic diagram that TCP/DN/IP main frames are accessed.
Figure 10 shows the schematic diagram of TCP/DN/IP protocol stacks.
Embodiment
After the detailed description of embodiment of the disclosure is read in conjunction with the following drawings, it better understood when the present invention's
Features described above and advantage.In the accompanying drawings, each component is not necessarily drawn to scale, and with similar correlation properties or feature
Component may have same or like reference.
The embodiment of the conversion method of TCP/DN/IP Web-compatible TCP/IP networks
Figure 10 shows the schematic diagram of TCP/DN/IP protocol stacks, and Fig. 3 shows that standard type TCP/DN/IP protocol stacks are encapsulated
Flow chart.As seen from Figure 3, main frame assembled TCP/DN/IP messages domain name layer header when, it is necessary to insert the domain of destination host
Name, thus design agreement stack send function when, it is necessary to allow using directly by the domain name of destination host, transport layer protocol type and
User data is transmitted as parameter.And message from domain name Internet after IP network layer is delivered to, it is still desirable to translate domain names into
For IP address to insert the DAF destination address field of IP headers.Now should be by the network protocol stack of operating system in IP network layer
The function for directly invoking gethostbyname classes is translated domain names into as IP address.
For the sending method of compatible traditional web application based on TCP/IP, the present invention is devised such as Fig. 4 institutes
The compatible type TCP/DN/IP protocol stacks encapsulation flow shown.As shown in figure 4, application program still works in a traditional way, i.e., voluntarily
Domain name by dns resolution destination host is IP address, and then IP address is passed to the function for sending message as parameter.
IP network layer is completed after encapsulation, message is sent to packet capture before link layer, in IP headers and data (i.e. in Fig. 4
TCP/UDP heads+Data) between insertion TCP/DN/IP protocol requirements domain name layer header and UDP heads so that message format is met
TCP/DN/IP definition.
But, domain name is not one-to-one with IP address.One domain name may resolve to multiple IP address, IP
Location is also possibly corresponding to multiple domain names.When the target ip address in IP headers determines target domain name, it would be desirable to
Which type of domain name of the insertion be accurately known that.Therefore, the present invention designs the method using dummy address pond, it is specific as follows to state.
The conversion method of the TCP/DN/IP Web-compatible TCP/IP networks of the present invention mainly includes two flows：Using journey
Sequence sends the flow of message and the flow of application program reception message.Wherein application program sends flow such as Fig. 6 institutes of message
Show, the flow that application program receives message is as shown in Figure 7.
Fig. 6 is referred to, the detailed description of the flow of message is sent the following is application program.
Application call system protocol stack is IP address by dns resolution destination host domain name, and protocol stack is parsed
And check analysis result.If return result show that destination host is not upgraded, or it is promoted but with application program where
Main frame be in identical IP domains, then return to the obtained IP address of parsing to application program, otherwise, according to destination host domain name and
The IP address that parsing is obtained inquires about correspondence list item in address translation table, first divides if in the absence of correspondence list item from dummy address pond
With a untapped pseudo- IP address, and the IP that newly-increased one obtains including destination host domain name, parsing in address translation table
Address and the list item of newly assigned pseudo- IP address, and the result of pseudo- IP address as the DNS query is returned into application program.
When application program sends message, protocol stack is by the destination host IP address in IP headers and address translation table
Pseudo- IP address row are compared, and ICP/IP protocol stack encapsulated message is used if in the absence of correspondence list item, if it there is correspondence list item from
Destination host domain name and the parsing IP address of destination host are taken out in the corresponding list item of address translation table, message addition domain name layer is given
Header simultaneously inserts destination host domain name, adds UDP heads, IP header destination addresses are changed to the parsing IP of destination host domain name
Location.The message for finally carrying out bottom is sent.
As shown in Figure 5A, inside compatible type TCP/DN/IP agreement stack functions, dummy address pond is previously created, dummy address
Pond is made up of the IP address that in fact will not be accessed.It is recommended that 127.0.0.0/8 removing 127.0.0.1 are used, and multicast
It is (current as available dummy address that location (224.0.0.0~239.255.255.255) removes limited allocated several addresses
Probably add up to 272M address space) it is put into pond.A conversion table is created in dummy address pond, " pseudo- IP address ", " domain is included
Name " and " parsing address " three are arranged.
This table is sky at first：
| Pseudo- IP address | Domain name | Parse address |
| …… | …… | …… |
Capturing operation system domain name mapping function (most of ICP/IP protocol stacks realization in should be
Gethostbyname () function), replaced with our own function (i.e. the domain name mapping function of user's calling system when can adjust
Us are used to the function that substitutes).
Application program can call first parsing domain name function to obtain the corresponding IP address of destination host domain name, now I
The alternative functions of oneself be called.Alternative functions are first carried out the DNS query of standard to obtain the IP and possibility of target domain name
The alias of presence.Because TCP/DN/IP schemes have used alias to indicate the upgrading shape of main frame in DNS systems in design
State, now we can determine whether whether destination host has upgraded by checking whether there is the alias of specified format, and be assisted with which kind of
Stack is discussed to access.
If destination host is not upgraded, ICP/IP protocol stack addressing must be used；Although if destination host has been upgraded
But it is in same IP domains, then all may be used using ICP/IP protocol stack or TCP/DN/IP protocol stacks with source host.It is recommended that using
TCP/IP is to improve efficiency；Other situations must use TCP/DN/IP protocol stacks.
It is exemplified below.
For example cn and us are two IP domains, there is following several situations：
1) host.cn will access 1-1-1-1.cn
DNS need not now be inquired about.Host.cn has found that 1-1-1-1.cn is identical with the domain suffix of oneself, can be with
Judge destination host and lay oneself open in same IP domains；Host machine part is the deformation of IP address and can directly parse IP simultaneously
Address (meets naming conventions of the TCP/DN/IP to DNS).Can determine whether out destination host support TCP/DN/IP and with source host
In same IP domains.
Now all may be used using TCP/IP or TCP/DN/IP.
2) host.cn will access same IP domains main frame foo.cn (assuming that its IP is 1.1.1.1)
DNS, which must now be inquired about, can just obtain IP address.If foo.cn does not upgrade, then DNS will be returned directly
The corresponding IP address 1.1.1.1 of foo.cn.Because the alias that dnip is prefix did not occur in centre, host.cn is now known that
Foo.cn does not support TCP/DN/IP.ICP/IP protocol stack must now be used.
The support TCP/DN/IP if the destination host has been upgraded, then what DNS was returned will be that foo.cn is mapped as alias
Dnip.foo.cn (there is individual dnip prefix to be mark, behind do not require it must is foo.cn), and dnip.foo.cn
It is mapped as IP 1.1.1.1.Host.cn can determine whether out that foo.cn supports TCP/DN/IP, and be in same IP domains with source host.This
When all may be used using TCP/IP or TCP/DN/IP.
3) host.cn will access other IP domains main frame such as foo.us, 1-1-1-1.us etc.
DNS, which must now be inquired about, can just obtain IP address.By TCP/DN/IP forwarding rules, what the DNS in cn domains was returned is
The IP address of domain name router (may so map：Foo.us → dnip.router.cn → A.B.C.D, 1-1-1-1.us →
Dnip.router.cn → A.B.C.D), host.cn knows that destination host is located in another IP domain and supports TCP/DN/IP.
TCP/DN/IP agreements must now be used.
If it is determined that using TCP/IP, directly returning to real IP；If it is determined that using TCP/DN/IP, being grasped as follows
Make：
1st, still untapped dummy address is found in dummy address pond, the dummy address is set up and is returned with domain name and DNS systems
IP mapping relations and record in address translation table.If a domain name returns to multiple IP address, they are added respectively
Enter conversion table.Example is as follows：
In upper table, we have selected a series of IP that 127.0.0.2 starts as dummy address.Assuming that passing through DNS query
Multiple IP are returned during www.sina.com.cn, it is added in table one by one；Also assume that bbs.aaa.com and
Www.aaa.com corresponds to same IP (100.100.100.100), same to add in table.
If existing domain name and the corresponding entries of IP in table, it need not repeat to add.
This conversion table is arranged as major key using dummy address, and domain name, IP allow to repeat, but domain name+IP does not allow to repeat.
2nd, the dummy address is returned to as the return value of our own replacement domain name analytical function and calls this function
Application program.
Application program initiates the flow of network communication, as shown in Figure 5 B after the IP of domain name mapping function return has been obtained：
(1) if the Target IP of message is not dummy address, illustrate above domain name mapping function return is real IP, i.e.,
We determine to use TCP/IP access target main frames.We need not comprehend this kind of message, transparent transmission.
(2) if what application program attempted to access that is a main frame needed with TCP/DN/IP protocol access, then it is obtained
To IP must be our dummy address provided above.Now we should can see, the IP destination addresses of message exactly I
The dummy address that provides.
(3) list item corresponding with dummy address is now searched into conversion table, parsing IP and target domain name is therefrom extracted, used
Parse the destination address in the IP heads of IP replacement messages, and the UDP heads of insertion TCP/DN/IP protocol requirements and domain after IP
In name header, the destination host field that the domain name of destination host is inserted to domain name header.
(4) complete after aforesaid operations, message is still a legal IP message.System protocol stack is given by this message
Bottom is continued with.Because inserting new field, the length of message has increased, and the specification according to IP is needed if necessary to super
The message for crossing MTU carries out burst.
The message for carrying out bottom is sent.
Fig. 7 is referred to, the detailed description of the flow of message is received the following is application program.
Application program receives the message from bottom.
In the protocol stack of receiving terminal, message can be transmitted along path from bottom to top.When message is from link layer (MAC
Layer+LLC sublayers) message is intercepted and captured when being passed up to IP layers.
Protocol stack judges whether message is TCP/DN/IP encapsulation, if not TCP/DN/IP encapsulation then directly carries out standard IP
The reception of message.If TCP/DN/IP encapsulation is then from domain name layer extraction source host domain name, then pass through gethostbyname () class
Function parses its corresponding IP or directly from IP layers of extraction source host ip.
If message is TCP/DN/IP encapsulation, the UDP heads and domain name header that contain TCP/DN/IP protocol packages is needed to go
Remove, revert to the message of TCP/IP encapsulation of a standard (if TCP/UDP messages are, it is necessary to recalculate the school on pseudo- head
Test and).But, if only doing such operation, application program is when responding this message, and main frame will be unable to know whether other side props up
TCP/DN/IP is held, does not also know that source IP address is the true address of peer or the interface IP address of domain name router, therefore
Also by that response message can not be converted to appropriate packing forms to be recycled to peer.
Therefore we search source host domain name in address translation table, taken if it there is corresponding entry after source IP is obtained
Go out wherein corresponding pseudo- IP address, increase a list item newly in address translation table if in the absence of corresponding entry, content includes：From
A newly assigned untapped pseudo- IP address in dummy address pond, the source host domain name extracted from domain name layer, and corresponding solution
Analyse IP address；
Then remove TCP/DN/IP encapsulation, the message received is reduced into standard IP messages and by the IP sources of message
Location is changed to the pseudo- IP address of foregoing new distribution.
Message is submitted to application program by protocol stack.
Some agreements such as FTP, H.323 etc., due to carrying IP address in application layer, when message is changed, if not
The address that application layer is carried is changed simultaneously, then end main frame will be unable to normally to set up Opposite direction connection.Conversion includes two
Individual link：First link and second link.
In first link, message is before main frame is sent, it is necessary to be domain name by IP address conversion in application layer
Location.The conversion regime of the mode of conversion and the NAT agreements based on IPv4 is similar, and difference is application claims by IP
Location is converted to domain name, and the length or type of the two do not ensure unanimously to connect, it is necessary to make message format appropriate be adjusted to ensure that
Receiving end can correctly reduce the address information of application layer.The present invention is not construed as limiting to the form of adjustment, and only requiring can be by source master
Machine domain name is correctly sent to end main frame, and can correctly be reduced to reference format to end main frame.
In second link, after message arrives at destination host, what is now carried in application layer is the domain name after conversion
Location, and application program can only receive the address of IP forms.Now there is still a need for domain name is converted back into IP.
A untapped dummy address can now be found and foundation turns with being inserted after the corresponding relation of the domain name in application layer
Change in table (but without corresponding IP address).When application program receives the IP address in application layer and attempts to initiate to this address
During connection, it will send the IP messages that Target IP is this dummy address.Now system is according to the anti-domain for finding destination host of dummy address
Name, goes out real IP, and encapsulate out correct TCP/DN/IP messages according to both by dns resolution.
Preferably, conversion table can constantly increase during system operation, it can introduce and be deleted no longer according to the mechanism of time aging
The map entry used.
The embodiment of file transmitting method in TCP/DN/IP Web-compatible TCP/IP networks
Fig. 6 is referred to, application program sends the detailed description of the flow of message.
Application call system protocol stack is IP address by dns resolution destination host domain name, and protocol stack is parsed
And check analysis result.If return result show that destination host is not upgraded, or it is promoted but with application program where
Main frame be in identical IP domains, then return to the obtained IP address of parsing to application program, otherwise, according to destination host domain name and
The IP address that parsing is obtained inquires about correspondence list item in address translation table, first divides if in the absence of correspondence list item from dummy address pond
With a untapped pseudo- IP address, and the IP that newly-increased one obtains including destination host domain name, parsing in address translation table
Address and the list item of newly assigned pseudo- IP address, and the result of pseudo- IP address as the DNS query is returned into application program.
When application program sends message, protocol stack is by the destination host IP address in IP headers and address translation table
Pseudo- IP address row are compared, and ICP/IP protocol stack encapsulated message is used if in the absence of correspondence list item, if it there is correspondence list item from
Destination host domain name and the parsing IP address of destination host are taken out in the corresponding list item of address translation table, message addition domain name layer is given
Header simultaneously inserts destination host domain name, adds UDP heads, IP header destination addresses are changed to the parsing IP of destination host domain name
Location.The message for finally carrying out bottom is sent.
As shown in Figure 5A, inside compatible type TCP/DN/IP agreement stack functions, dummy address pond is previously created, dummy address
Pond is made up of the IP address that in fact will not be accessed.It is recommended that 127.0.0.0/8 removing 127.0.0.1 are used, and multicast
It is (current as available dummy address that location (224.0.0.0~239.255.255.255) removes limited allocated several addresses
Probably add up to 272M address space) it is put into pond.A conversion table is created in dummy address pond, " pseudo- IP address ", " domain is included
Name " and " parsing address " three are arranged.
This table is sky at first：
| Pseudo- IP address | Domain name | Parse address |
| …… | …… | …… |
Capturing operation system domain name mapping function (most of ICP/IP protocol stacks realization in should be
Gethostbyname () function), replaced with our own function (i.e. the domain name mapping function of user's calling system when can adjust
Us are used to the function that substitutes).
Application program can call first parsing domain name function to obtain the corresponding IP address of destination host domain name, now I
The alternative functions of oneself be called.Alternative functions are first carried out the DNS query of standard to obtain the IP and possibility of target domain name
The alias of presence.Because TCP/DN/IP schemes have used alias to indicate the upgrading shape of main frame in DNS systems in design
State, now we can determine whether whether destination host has upgraded by checking whether there is the alias of specified format, and be assisted with which kind of
Stack is discussed to access.
If destination host is not upgraded, ICP/IP protocol stack addressing must be used；Although if destination host has been upgraded
But it is in same IP domains, then all may be used using ICP/IP protocol stack or TCP/DN/IP protocol stacks with source host.It is recommended that using
TCP/IP is to improve efficiency；Other situations must use TCP/DN/IP protocol stacks.
It is exemplified below.
For example cn and us are two IP domains, there is following several situations：
1) host.cn will access 1-1-1-1.cn
DNS need not now be inquired about.Host.cn has found that 1-1-1-1.cn is identical with the domain suffix of oneself, can be with
Judge destination host and lay oneself open in same IP domains；Host machine part is the deformation of IP address and can directly parse IP simultaneously
Address (meets naming conventions of the TCP/DN/IP to DNS).Can determine whether out destination host support TCP/DN/IP and with source host
In same IP domains.
Now all may be used using TCP/IP or TCP/DN/IP.
2) host.cn will access same IP domains main frame foo.cn (assuming that its IP is 1.1.1.1)
DNS, which must now be inquired about, can just obtain IP address.If foo.cn does not upgrade, then DNS will be returned directly
The corresponding IP address 1.1.1.1 of foo.cn.Because the alias that dnip is prefix did not occur in centre, host.cn is now known that
Foo.cn does not support TCP/DN/IP.ICP/IP protocol stack must now be used.
The support TCP/DN/IP if the destination host has been upgraded, then what DNS was returned will be that foo.cn is mapped as alias
Dnip.foo.cn (there is individual dnip prefix to be mark, behind do not require it must is foo.cn), and dnip.foo.cn
It is mapped as IP 1.1.1.1.Host.cn can determine whether out that foo.cn supports TCP/DN/IP, and be in same IP domains with source host.This
When all may be used using TCP/IP or TCP/DN/IP.
3) host.cn will access other IP domains main frame such as foo.us, 1-1-1-1.us etc.
DNS, which must now be inquired about, can just obtain IP address.By TCP/DN/IP forwarding rules, what the DNS in cn domains was returned is
The IP address of domain name router (may so map：Foo.us → dnip.router.cn → A.B.C.D, 1-1-1-1.us →
Dnip.router.cn → A.B.C.D), host.cn knows that destination host is located in another IP domain and supports TCP/DN/IP.
TCP/DN/IP agreements must now be used.
If it is determined that using TCP/IP, directly returning to real IP；If it is determined that using TCP/DN/IP, being grasped as follows
Make：
1st, still untapped dummy address is found in dummy address pond, the dummy address is set up and is returned with domain name and DNS systems
IP mapping relations and record in address translation table.If a domain name returns to multiple IP address, they are added respectively
Enter conversion table.Example is as follows：
| Dummy address | Domain name | True address |
| 127.0.0.2 | www.sina.com.cn | 61.172.201.195 |
| 127.0.0.3 | www.sina.com.cn | 61.172.201.237 |
| 127.0.0.4 | www.sina.com.cn | 61.172.201.239 |
| 127.0.0.5 | www.sina.com.cn | 61.172.201.194 |
| 127.0.0.6 | bbs.aaa.com | 100.100.100.100 |
| 127.0.0.7 | www.aaa.com | 100.100.100.100 |
| …… | …… | …… |
| 127.255.255.254 | - | - |
In upper table, we have selected a series of IP that 127.0.0.2 starts as dummy address.Assuming that passing through DNS query
Multiple IP are returned during www.sina.com.cn, it is added in table one by one；Also assume that bbs.aaa.com and
Www.aaa.com corresponds to same IP (100.100.100.100), same to add in table.
If existing domain name and the corresponding entries of IP in table, it need not repeat to add.
This conversion table is arranged as major key using dummy address, and domain name, IP allow to repeat, but domain name+IP does not allow to repeat.
2nd, the dummy address is returned to as the return value of our own replacement domain name analytical function and calls this function
Application program.
Application program initiates the flow of network communication, as shown in Figure 5 B after the IP of domain name mapping function return has been obtained：
(1) if the Target IP of message is not dummy address, illustrate above domain name mapping function return is real IP, i.e.,
Destination host is not yet upgraded, or with the upgrading main frame in IP domains, we are still using TCP/IP encapsulation in the hope of more efficient
Rate.We need not comprehend this kind of message, transparent transmission.
(2) if application program has to use TCP/DN/IP access target main frames, then the IP that it is obtained must be us
Dummy address provided above.Now we should can see, the IP destination addresses dummy address that exactly we provide of message.
(3) list item corresponding with dummy address is now searched into conversion table, parsing IP and target domain name is therefrom extracted, used
Parse the destination address in the IP heads of IP replacement messages, and the UDP heads of insertion TCP/DN/IP protocol requirements and domain after IP
In name header, the destination host field that the domain name of destination host is inserted to domain name header.
(4) complete after aforesaid operations, message is still a legal IP message.System protocol stack is given by this message
Bottom is continued with.Because inserting new field, the length of message has increased, and the specification according to IP is needed if necessary to super
The message for crossing MTU carries out burst.
The message for finally carrying out bottom is sent.
The embodiment of message method of reseptance in TCP/DN/IP Web-compatible TCP/IP networks
Fig. 7 is referred to, the detailed description of the flow of message is received the following is application program.
Application program receives the message from bottom.
In the protocol stack of receiving terminal, message can be transmitted along path from bottom to top.When message is from link layer (MAC
Layer+LLC sublayers) message is intercepted and captured when being passed up to IP layers.
Protocol stack judges whether message is TCP/DN/IP encapsulation, if not TCP/DN/IP encapsulation then directly carries out standard IP
The reception of message, if TCP/DN/IP encapsulation is then from domain name layer extraction source host domain name, then pass through gethostbyname () class
Function parses its corresponding IP or directly from IP layers of extraction source host ip.
If message is TCP/DN/IP encapsulation, the UDP heads and domain name header that contain TCP/DN/IP protocol packages is needed to go
Remove, revert to the message of TCP/IP encapsulation of a standard (if TCP/UDP messages are, it is necessary to recalculate the school on pseudo- head
Test and).But, if only doing such operation, application program is when responding this message, and main frame will be unable to know whether other side props up
TCP/DN/IP is held, does not also know that source IP address is the true address of peer or the interface IP address of domain name router, therefore
Also by that response message can not be converted to appropriate packing forms to be recycled to peer.
Therefore we search source host domain name in address translation table, taken if it there is corresponding entry after source IP is obtained
Go out wherein corresponding pseudo- IP address, increase a list item newly in address translation table if in the absence of corresponding entry, content includes：From
A newly assigned untapped pseudo- IP address in dummy address pond, the source host domain name extracted from domain name layer, and corresponding solution
Analyse IP address；
Then TCP/DN/IP encapsulation is removed, the message received is reduced into standard IP messages and by the IP sources of message
Address is changed to the pseudo- IP address of foregoing new distribution.
Message is submitted to application program by protocol stack.
Client TCP/IP applications access the citing of the flow of TCP/DN/IP main frames
As shown in figure 8, there is a main frame host.cn in China national domain, its IP address is 100.1.1.1, above there is 2 bases
To access the server1.com (2.1.1.1) and server2.com (2.1.1.2) in global area respectively in TCP/IP application.
A domain name router CN DNR is responsible for being forwarded between global area and China national domain on the border of domain, and it is in global area
IP address be 1.1.1.1, IP address in China national domain is 200.1.1.1.
Message is as follows in each link content：
Conversion table content simultaneously on main frame host.cn is as follows：
| Dummy address | Domain name | True IP |
| 127.0.0.2 | server1.com | 100.1.1.1 |
| 127.0.0.3 | server2.com | 100.1.1.1 |
Service end TCP/IP applications receive the citing for the flow that TCP/DN/IP main frames are accessed
As shown in figure 9, there is a server .com in global area, its IP address is 2.2.2.2；China national domain
In have 2 main frames host1.cn and host2.cn, IP address is respectively 100.1.1.1 and 100.1.1.2.A domain on the border of domain
Name router CN DNR are responsible for being forwarded between global area and China national domain, and its IP address in global area is
1.1.1.1, the IP address in China national domain is 200.1.1.1.
Message sent to exemplified by Server.com by host1.cn and host2.cn, main frame message each link in a network
Key message is as follows：
Conversion table content simultaneously on server .com is as follows：
| Dummy address | Domain name | True IP address |
| 127.0.0.2 | host1.cn | 1.1.1.1 |
| 127.0.0.3 | host2.cn | 1.1.1.1 |
Although for make explanation simplify the above method is illustrated and is described as a series of actions, it should be understood that and understand,
The order that these methods are not acted is limited, because according to one or more embodiments, some actions can occur in different order
And/or with from it is depicted and described herein or herein it is not shown and describe but it will be appreciated by those skilled in the art that other
Action concomitantly occurs.
Those skilled in the art will further appreciate that, the various illustratives described with reference to the embodiments described herein
Logic plate, module, circuit and algorithm steps can be realized as electronic hardware, computer software or combination of the two.To be clear
Explain to Chu this interchangeability of hardware and software, various illustrative components, frame, module, circuit and step be above with
Its functional form makees vague generalization description.Such feature be implemented as hardware or software depend on concrete application and
Put on the design constraint of total system.Technical staff can be realized described for every kind of application-specific with different modes
Feature, but such realize that decision-making should not be interpreted to cause departing from the scope of the present invention.
General place can be used with reference to various illustrative logic plates, module and the circuit that presently disclosed embodiment is described
Reason device, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) other are compiled
Journey logical device, discrete door or transistor logic, discrete nextport hardware component NextPort or its be designed to carry out function described herein
Any combinations are realized or performed.General processor can be microprocessor, but in alternative, the processor can be appointed
What conventional processor, controller, microcontroller or state machine.Processor is also implemented as the combination of computing device, example
The one or more microprocessors that are cooperated with the combination of microprocessor, multi-microprocessor, with DSP core such as DSP or it is any its
His such configuration.
It can be embodied directly in hardware, in by processor with reference to the step of the method or algorithm that embodiment disclosed herein is described
Embodied in the software module of execution or in combination of the two.Software module can reside in RAM memory, flash memory, ROM and deposit
Reservoir, eprom memory, eeprom memory, register, hard disk, removable disk, CD-ROM or known in the art appoint
In the storage medium of what other forms.Exemplary storage medium is coupled to processor to enable the processor from/to the storage
Medium is read and write-in information.In alternative, storage medium can be integrated into processor.Processor and storage medium can
Reside in ASIC.ASIC can reside in user terminal.In alternative, processor and storage medium can be used as discrete sets
Part is resident in the user terminal.
In one or more exemplary embodiments, described function can be in hardware, software, firmware or its any combinations
It is middle to realize.If being embodied as computer program product in software, each function can be used as the instruction of one or more bars or generation
Code storage is transmitted on a computer-readable medium or by it.Computer-readable medium includes computer-readable storage medium and communication
Both media, it includes any medium for facilitating computer program to shift from one place to another.Storage medium can be can quilt
Any usable medium that computer is accessed.It is non-limiting as example, such computer-readable medium may include RAM, ROM,
EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage apparatus can be used to carry or store instruction
Or the desirable program code and any other medium that can be accessed by a computer of data structure form.Any connection is also by by rights
Referred to as computer-readable medium.If for example, software is to use coaxial cable, fiber optic cables, twisted-pair feeder, digital subscriber line
Or the wireless technology of such as infrared, radio and microwave etc is passed from web site, server or other remote sources (DSL)
Send, then the coaxial cable, fiber optic cables, twisted-pair feeder, DSL or such as infrared, radio and microwave etc is wireless
Technology is just included among the definition of medium.Disk (disk) and dish (disc) as used herein include compact disc
(CD), laser disc, laser disc, digital versatile disc (DVD), floppy disk and blu-ray disc, which disk (disk) are often reproduced in the way of magnetic
Data, and dish (disc) laser reproduce data optically.Combinations of the above should also be included in computer-readable medium
In the range of.
It is for so that any person skilled in the art all can make or use this public affairs to provide of this disclosure be previously described
Open.Various modifications of this disclosure all will be apparent for a person skilled in the art, and as defined herein general
Suitable principle can be applied to spirit or scope of other variants without departing from the disclosure.Thus, the disclosure is not intended to be limited
Due to example described herein and design, but it should be awarded and principle disclosed herein and novel features phase one
The widest scope of cause.
Claims (10)
1. a kind of conversion method of TCP/DN/IP Web-compatibles TCP/IP networks, including application program send the flow of message with
And application program receives the flow of message, wherein：
The flow that application program sends message includes：
Application call system protocol stack is IP address by dns resolution destination host domain name, and protocol stack is parsed and examined
Look into analysis result, if return result show that destination host is not upgraded, or it is promoted but with the master where application program
Machine is in identical IP domains, then returns and parse obtained IP address to application program；Otherwise, according to destination host domain name and parsing
Obtained IP address inquires about correspondence list item in address translation table, and first one is distributed from dummy address pond if in the absence of correspondence list item
Individual untapped pseudo- IP address, and the IP address that newly-increased one obtains including destination host domain name, parsing in address translation table
With the list item of newly assigned pseudo- IP address, and the result of pseudo- IP address as the DNS query is returned into application program；
When application program sends message, protocol stack is by the pseudo- IP in the destination host IP address in IP headers and address translation table
Address column is compared, and ICP/IP protocol stack encapsulated message is used if in the absence of correspondence list item, from this pair if it there is correspondence list item
Answer and destination host domain name and the parsing IP address of destination host are taken out in list item, add domain name layer header to message and insert target
Host domain name, adds UDP heads, IP header destination addresses is changed to the parsing IP address of destination host domain name；
The message for carrying out bottom is sent；
The flow that application program receives message includes：
Application program receives the message from bottom；
Protocol stack judges whether message is TCP/DN/IP encapsulation, if not TCP/DN/IP encapsulation then directly carries out standard IP messages
Reception；
If TCP/DN/IP is encapsulated, then：
From domain name layer extraction source host domain name and the source host domain name is parsed so as to obtaining corresponding IP address, or directly from IP
Layer extracts source IP address as the parsing IP address of source host domain name；
Source host domain name is searched in address translation table, wherein corresponding pseudo- IP address is taken out if it there is corresponding entry, if not
There is corresponding entry and then increase a list item newly in address translation table, content includes：Newly assigned one not from dummy address pond
The pseudo- IP address used, the source host domain name extracted from domain name layer, and IP address is parsed accordingly；And
The TCP/DN/IP encapsulation in message is removed, the message received is reduced into standard IP messages and source IP address is changed
For corresponding newly assigned pseudo- IP address；
Message is submitted to application program by protocol stack.
2. the conversion method of TCP/DN/IP Web-compatibles TCP/IP networks according to claim 1, it is characterised in that pseudo-
Address pool is made up of the pseudo- IP address that will not be truly used for network access, and the list item of address translation table includes pseudo- IP address, domain name
With parsing IP address, using address translation table and pseudo- IP address, message is being extended to TCP/DN/DP encapsulation by TCP/IP encapsulation
When correct destination host domain name is provided.
3. the conversion method of TCP/DN/IP Web-compatibles TCP/IP networks according to claim 1, it is characterised in that if
The message that application program is sent carries source host IP address in application layer, then the address conversion is by message before being issued
Source host domain name addresses, wherein being adjusted to message format to ensure that receiving terminal reduces the address information of application layer, in message
The domain name addresses in application layer is converted back into pseudo- IP address using address translation table after arrival destination host.
4. the conversion method of TCP/DN/IP Web-compatibles TCP/IP networks according to claim 2, it is characterised in that ground
Location conversion table deletes the list item not used based on time aging mechanism.
5. a kind of file transmitting method in TCP/DN/IP Web-compatible TCP/IP networks, including：
Application call system protocol stack is IP address by dns resolution destination host domain name, and protocol stack is parsed and examined
Look into analysis result, if return result show that destination host is not upgraded, or it is promoted but with the master where application program
Machine is in identical IP domains, then returns and parse obtained IP address to application program, otherwise, according to destination host domain name and parsing
Obtained IP address inquires about correspondence list item in address translation table, and first one is distributed from dummy address pond if in the absence of correspondence list item
Individual untapped pseudo- IP address, and the IP address that newly-increased one obtains including destination host domain name, parsing in address translation table
With the list item of newly assigned pseudo- IP address, and the result of pseudo- IP address as the DNS query is returned into application program；
When application program sends message, protocol stack is by the pseudo- IP in the destination host IP address in IP headers and address translation table
Address column is compared, and ICP/IP protocol stack encapsulated message is used if in the absence of correspondence list item, from this pair if it there is correspondence list item
Answer and destination host domain name and the parsing IP address of destination host are taken out in list item, add domain name layer header to message and insert target
Host domain name, adds UDP heads, IP header destination addresses is set to the parsing IP address of destination host domain name；
The message for carrying out bottom is sent.
6. the file transmitting method according to claim 5 in TCP/DN/IP Web-compatible TCP/IP networks, its feature
It is, dummy address pond is made up of the pseudo- IP address that will not be truly used for network access, the list item of address translation table is with including puppet IP
Location, domain name and parsing IP address, using address translation table and its pseudo- IP address, TCP/ is being extended to by message by TCP/IP encapsulation
DN/DP provides correct destination host domain name when encapsulating.
7. the file transmitting method according to claim 6 in TCP/DN/IP Web-compatible TCP/IP networks, its feature
It is, address translation table deletes the list item not used based on time aging mechanism.
8. a kind of message method of reseptance in TCP/DN/IP Web-compatible TCP/IP networks, including：
Application program receives the message from bottom；
Protocol stack judges whether message is TCP/DN/IP encapsulation, if not TCP/DN/IP encapsulation then directly carries out standard IP messages
Reception；
If TCP/DN/IP is encapsulated, then：
From domain name layer extraction source host domain name and the domain name is parsed so as to obtain corresponding IP address, or directly extracted from IP layer
Source IP address as source host domain name parsing IP address；
Source host domain name is searched in address translation table, wherein corresponding pseudo- IP address is taken out if it there is corresponding entry, if not
There is corresponding entry and then increase a list item newly in address translation table, content includes：Newly assigned one not from dummy address pond
The pseudo- IP address used, the source host domain name extracted from domain name layer, and IP address is parsed accordingly；And
The TCP/DN/IP encapsulation in message is removed, the message received is reduced into standard IP messages and source IP address is changed
For corresponding newly assigned pseudo- IP address；
Message is submitted to application program by protocol stack.
9. the message method of reseptance according to claim 8 in TCP/DN/IP Web-compatible TCP/IP networks, its feature
It is, dummy address pond is made up of the pseudo- IP address that will not be truly used for network access, the list item of address translation table is with including puppet IP
Location, domain name and parsing IP address, using address translation table and its pseudo- IP address, TCP/ is being extended to by message by TCP/IP encapsulation
DN/DP provides correct destination host domain name when encapsulating.
10. the message method of reseptance according to claim 9 in TCP/DN/IP Web-compatible TCP/IP networks, it is special
Levy and be, address translation table deletes the list item not used based on time aging mechanism.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610081189.0A CN107040616B (en) | 2016-02-04 | 2016-02-04 | Conversion method and message receiving and transmitting method for TCP/DN/IP network compatible with TCP/IP network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610081189.0A CN107040616B (en) | 2016-02-04 | 2016-02-04 | Conversion method and message receiving and transmitting method for TCP/DN/IP network compatible with TCP/IP network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107040616A true CN107040616A (en) | 2017-08-11 |
| CN107040616B CN107040616B (en) | 2020-01-10 |
Family
ID=59532743
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610081189.0A Expired - Fee Related CN107040616B (en) | 2016-02-04 | 2016-02-04 | Conversion method and message receiving and transmitting method for TCP/DN/IP network compatible with TCP/IP network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107040616B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108650179A (en) * | 2018-04-17 | 2018-10-12 | 达闼科技（北京）有限公司 | A kind of method, retransmission unit and the computer readable storage medium of configuration forwarding table |
| CN114710570A (en) * | 2022-03-16 | 2022-07-05 | 深圳市风云实业有限公司 | UDP data zero-copy transmission method based on kernel mode protocol stack |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104135446A (en) * | 2014-07-15 | 2014-11-05 | 武汉绿色网络信息服务有限责任公司 | System and method of implementing transition from IPv4 (Internet Protocol Version4) to IPv6 (Internet Protocol Version6) based on SDN (Software Defined Network) |
| US9009353B1 (en) * | 2014-04-11 | 2015-04-14 | Cable Television Laboratories, Inc. | Split network address translation |
| CN104734963A (en) * | 2015-03-24 | 2015-06-24 | 电子科技大学 | IPv4 and IPv6 network interconnection method based on SDN |
-
2016
- 2016-02-04 CN CN201610081189.0A patent/CN107040616B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9009353B1 (en) * | 2014-04-11 | 2015-04-14 | Cable Television Laboratories, Inc. | Split network address translation |
| CN104135446A (en) * | 2014-07-15 | 2014-11-05 | 武汉绿色网络信息服务有限责任公司 | System and method of implementing transition from IPv4 (Internet Protocol Version4) to IPv6 (Internet Protocol Version6) based on SDN (Software Defined Network) |
| CN104734963A (en) * | 2015-03-24 | 2015-06-24 | 电子科技大学 | IPv4 and IPv6 network interconnection method based on SDN |
Non-Patent Citations (1)
| Title |
|---|
| 李实: "双网络层方案--全新的下一代互联网解决方案", 《电信科学》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108650179A (en) * | 2018-04-17 | 2018-10-12 | 达闼科技（北京）有限公司 | A kind of method, retransmission unit and the computer readable storage medium of configuration forwarding table |
| CN114710570A (en) * | 2022-03-16 | 2022-07-05 | 深圳市风云实业有限公司 | UDP data zero-copy transmission method based on kernel mode protocol stack |
| CN114710570B (en) * | 2022-03-16 | 2023-08-25 | 深圳市风云实业有限公司 | UDP data zero-copy transmission method based on kernel mode protocol stack |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107040616B (en) | 2020-01-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11425037B2 (en) | Stateless protocol translation | |
| CN1711739B (en) | Method and device for supporting a 6to4 tunneling protocol across a network address translation mechanism | |
| JP4130962B2 (en) | System and method for using a domain name to route data sent to a destination on a network | |
| CN1965515B (en) | Arrangement for reaching IPv4 public network nodes by a node in an IPv4 private network via an IPv6 access network | |
| US6581108B1 (en) | Managing multiple private data networks using network and payload address translation | |
| CN102132544B (en) | Method for receiving data packet in ipv6 domain, and associated device and residential gateway | |
| CN100431299C (en) | Method and system for centrally allocating addresses and port numbers | |
| JP2003510904A (en) | Packet network interfacing | |
| US20070147421A1 (en) | ISATAP router for tunneling packets and method thereof | |
| CN101800781B (en) | Tunnel transition method and system for passing through NAT | |
| CN102035900B (en) | NAT (network address translation) traversal method, system and relay server by relay mode | |
| CN103856580B (en) | A kind of method that IPv6 client computer accesses IPv4 servers | |
| CN101325580B (en) | Method for implementing FTP application-layer gateway based on NAT-PT | |
| CN102934410A (en) | Enhancing ds-lite with private ipv4 reachability | |
| US8612557B2 (en) | Method for establishing connection between user-network of other technology and domain name system proxy server for controlling the same | |
| CN102045244A (en) | IPV4 (Internet Protocol Version 4) network as well as implementation method and system for intercommunicating with new network | |
| CN102907073B (en) | DNS Server, gateways and methods for managing an identifier of a port range in the transmission of data | |
| KR100896438B1 (en) | Tunneling ipv6 packet through ipv4 network using a tunnel entry based on ipv6 prefix | |
| CN107040616A (en) | The conversion method and packet sending and receiving method of TCP/DN/IP Web-compatible TCP/IP networks | |
| CN103888554B (en) | IPv4 and the domain name analytic method and system of IPv6 intercommunications | |
| CN108494751A (en) | The method and device of the publicly-owned addresses effective use IPv4 | |
| CN101355568B (en) | Method and system for binding router interface supported by static state PAT | |
| CN104717639A (en) | Access method for mobile client to internet and access gateway server | |
| CN100388673C (en) | Method for implementing intra-site automatic tunnel | |
| CN100355315C (en) | Method for implementing telephone number to uniform resource identifier mapping business |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20200110 Termination date: 20220204 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |