CN1551583A - Data packet commmunication device - Google Patents
Data packet commmunication device Download PDFInfo
- Publication number
- CN1551583A CN1551583A CNA2004100008851A CN200410000885A CN1551583A CN 1551583 A CN1551583 A CN 1551583A CN A2004100008851 A CNA2004100008851 A CN A2004100008851A CN 200410000885 A CN200410000885 A CN 200410000885A CN 1551583 A CN1551583 A CN 1551583A
- Authority
- CN
- China
- Prior art keywords
- address
- mentioned
- ipv6
- ipv4
- packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
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/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/251—Translation of Internet protocol [IP] addresses between different IP versions
-
- 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
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/659—Internet protocol version 6 [IPv6] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- 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/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
Abstract
Disclosed is a packet-switched communication apparatus receiving and forwarding messages which are used to obtain an address corresponding to a domain name assigned to a device connected to a network from the domain name and to obtain such a domain name from the address. The communication apparatus comprises mapping retaining means for retaining mappings between network-dependent parts of addresses which are used in a first network and address translators; address translator selecting means for selecting an address translators, based on an address included in a received packet; address obtaining means for obtaining a substitutive address to replace the address included in the received packet from the selected address translator; and address replacement means for replacing the address included in the received packet by using the obtained substitutive address.
Description
Technical field
The present invention relates to data packet communication, refer to that especially forwarding is used for finding out corresponding address from the domain name that is endowed the machine that is connected with network, perhaps finds out the packet communication apparatus of the message of domain name from the address
(DNS Relay Server [DNS proxy server]).
Technical background
Here lift a technology (protocol conversion) that under the different situation of the communication protocol of the net under the terminal of the net under certain terminal and communication object, realizes two communication between terminals.
For example, the Internet Protocol (IP) that uses in the internet, though Internet Protocol edition 4 (IPv4) is popularized in the whole world now, but there is the exhausted worry of operable address meeting, as the method that addresses this problem, come on the agenda of the referred reality of Internet Protocol version 6 (IPv6).But, for existing Internet system all at one stroke from IPv4 change to IPv6 come in fact impossible.Therefore, proposed when the net of net that uses IPv4 and use IPv6 communicates, to carry out ways of connecting by the agreement of conversion IP packet.As concrete mapping mode, known by IETF (Internet Engineering Task Force) disclosed RFC (Request ForComments) 2765, be documented in ' NAT-PT ' among the RFC2766, be documented in ' SOCKS64 ' among the RFC3089, be documented in ' carrying relay [transport relay] ' among the RFC3142 etc.
Because these all are the mutual conversion of carrying out IPv4 address and IPv6 address, so be necessary to generate in advance mutual transformation rule [translation rule] and the maintenance in IPv4 address and IPv6 address.This transformation rule has the method and the method that dynamically generates with the generation of communicating by letter of static setting in advance, under the latter's the situation, as the opportunity of the generation of transformation rule, utilized the title of DNS (DomainName System) to solve the technology of [name resolution].
DNS is that to specify what be endowed the machine that is connected with network be modification domain name fully (FQDN:Fully Qualified Domain Name) in the title of whole world uniform system, the system of retrieval and this domain name associated attributes value (resource record [resource record]) generally is used for obtaining the IP address from domain name.This is called the title solution from the operation that domain name obtains the IP address.At present, utilize most of application software of internet all to utilize DNS to obtain the IP address of communication object.
In the conversion of IPv4 and IPv6, utilize this DNS, monitor the message of the DNS of exchange when the communication beginning always, the request message that solves with title is an opportunity, generates the transformation rule of IP address.Further, replace the IP address in the answer message that title solves and return to the requestor that title solves according to the address mapping rule that generates.For these functions are provided, in the requestor's that title solves terminal with accept between the dns server of inquiry the DNS Relay Server of cooperating with IPv4/IPv6 converting means [IPv4/IPv6 translator] to be set.
Below be that example illustrates concrete action to communicate to the IPv4 terminal from the IPv6 terminal.
At first, the IPv6 terminal of transmitter side for title solves, is accepted the IPv6 address of lateral terminal to DNS Relay Server inquiry [query].The DNS Relay Server of accepting inquiry carries out inquiry to other dns server, and reception is as the notice of the address of the above-mentioned receiver side terminal of its answer.At this, be under the situation of IPv4 address in the notice that receives, the IPv4 address that the DNS Relay Server just will be answered message replaces to the IPv6 address of [temporary] temporarily, foldback IPv6 terminal.At this moment, the DNS Relay Server generates the address mapping rule that the IPv4 address before temporary IP v6 address after the replacement and the replacement is mapped to the request of IPv4/IPv6 converting means.The address mapping rule that generates is maintained in the interior table (address mapping table [addresstranslation table]) of IPv4/IPv6 converting means.
The IPv6 terminal of transmitter side sends to the IPv6 packet temporary IP v6 address of the receiver side terminal notified by the title solution.The sender address of this IPv6 packet is the IPv6 address of transmitter side terminal self.The DNS Relay Server receives this IPv6 packet, carries out inquiry to the IPv4/IPv6 converting means.The IPv4/IPv6 converting means is with reference to address mapping table, retrieval and the sender's of IPv6 packet corresponding IPv4 address, IPv6 address.Owing in address mapping table, maintain the corresponding IPv4 address of temporary IP v6 packet of generation when solving, so can access the IPv4 address of receiver side terminal with title.
Next, the IPv4/IPv6 converting means is with reference to the address mapping table search IPv4 address corresponding with the sender's of IPv6 packet IPv6 address.But, at this moment,, therefore can not get IPv4 address as target because the transformation rule of sender address does not also generate.Therefore, the IPv4/IPv6 converting means is redistributed the interim IPv4 address of the IPv6 address of relative transmitter side terminal, and this address mapping rule is logined in address mapping table again.With this obtain with sender and each self-corresponding IPv4 address of recipient after, above-mentioned IP v6 packet just is transformed into the IPv4 packet that sender and recipient's address is replaced to corresponding IPv4 address respectively, and sends to the recipient.
Then, owing in address mapping table, login the transformation rule that sender address and recipient address are arranged, so the packet that transmits between two terminals just carries out the packet conversion according to transformation rule.In addition, the address mapping rule that dynamically generates during owing to communication is interim, therefore at sign off, through just automatic discarded behind the certain hour.
In addition, be the communication of carrying out to the IPv4 terminal from the IPv6 terminal described in the above-mentioned example, but, the communication of carrying out address mapping at the needs that carry out from the IPv4 terminal between communication that the IPv6 terminal is carried out, IPv4 terminal (for example, there is the possibility of repetition the address, crosses over the communication of two IPv4 people net), use in the communication etc. of the communication protocol beyond the IP, also with same order calculated address transformation rule, carry out communication (for example, patent documentation 1) by address mapping.
Above-mentioned utilize DNS that IPv4 address and IPv6 address are mapped to need to replace the IP address that is included in the answer message that title solves.This IP address is not included in the IP packet header, and is included in the pay(useful) load that is right after IP packet header.
In addition, at DNS, also have that to find out the IP address opposite with the domain name of designated communication object, the processing that is called as ' [reverselookup] ask in backward process ' of the domain name of the object that is endowed this IP address is found out in the assigned ip address.It mainly is utilization in the communication etc. between Email or server that this backward process is ask.
Particularly, in the network that connects IPv4 net and IPv6 net by protocol conversion, Email in fact is necessary service, in addition, be accompanied by the progress of the IPv6ization of visit net, for example, the demand that can envision for the IPv6 client that connects the server constructed in the IPv4 net and user side will increase from now on gradually.Therefore, in order to use these services, realize that the backward process inquiry of the DNS of leap IPv4 net and IPv6 net is indispensable.
Must carry out in the communication of IP address mapping, the IP address that the temporary ip address that each terminal will be distributed to communication object by address conversion device is identified as communication object communicates.For this reason, the terminal of carrying out the inquiry of backward process inquiry specifies interim IP address to come the domain name of inquiry correspondence.On the other hand, because dns server has been grasped the real ip address of terminal and the corresponding relation between this terminal domain name, so in order correctly to obtain the title of communication object, just must be to the real ip address of dns server inquiry terminal.Therefore, the backward process of crossing over the DNS of IPv4 net and IPv6 net is ask and need will be become the address of reality for the address of inquiry appointment from interim address mapping between terminal that the request backward process is ask and dns server.
In the packet that the backward process of DNS is ask, specifically, will ask the pay(useful) load part that is stored in back, IP packet header with FQDN with the corresponding backward process in IPv4 address or IPv6 address as the key of inquiry.For this reason, the conversion of IP address needs the backward process inquiry FQDN of conversion pay(useful) load part.Partly comprise under the situation of address mapping of packet of IP address in this pay(useful) load carrying out,, can carry out conversion of IP packet header and pay(useful) load conversion simultaneously for the protocol conversion arrangement of SOCKS64 and so on ALG (ALG) mode.But,, handle so be difficult to carry out protocol conversion at a high speed owing to carry out whole conversion process by application software.
On the other hand, the protocol conversion of NAT-PT mode owing to only carry out the replacement in IP packet header, can be carried out conversion process at a high speed so the hardware by special use carries out mapping function.Because between common agreement, communicating by letter, it nearly all is the processing of only carrying out the conversion of IP packet header, do not need the conversion of pay(useful) load, so from the viewpoint NAT-PT mode as all processing speeds is favourable, yet, under the situation that needs the pay(useful) load conversion, just need to prepare in addition ALG, after carrying out the conversion of IP packet header by the IPv4/IPv6 converting means, this packet is sent to ALG carries out the pay(useful) load conversion.
In the NAT-PT mode, use DNS Relay Server and so on be used for the ALG of pay(useful) load conversion the time, the transformation rule of address is remained on where become problem, but, can think to keep with reference to the highest IPv4/IPv6 converting means of the frequency of the transformation rule of address, from processing speed this to put be favourable.Under this situation, the occasion of the address mapping in each ALG carries out pay(useful) load has just become to IPv4/IPv6 converting means inquiry displacement to use the address.
[non-patent literature 1]
E.Nordmark, " RFC2765 ", " online ", in February, 2000, internet＜URL:http: //www.ietf.org/rfc/rfc2765.txt 〉
[non-patent literature 2]
H.Kitamura, " RFC3089 ", " online ", April calendar year 2001, internet＜URL:http: //www.ietf.org/rfc/rfc3089.txt 〉
[non-patent literature 3]
Beyond the J.Hagino, " RFC3142 ", " online ", July calendar year 2001, internet＜URL:http: //www.ietf.org/rfc/rfc3142.txt
[patent documentation 1]
The spy opens the 2000-156710 communique
Under the interconnective situation of carrying out large-scale IPv4 net and IPv6 net, for load balance [load balance] with avoid fault, can consider in the tie point mode of a plurality of IPv4/IPv6 converting means of use side by side.In addition, also it is contemplated that and to use IPv4 people's net of the individual address of stipulating to be connected to the IPv6 net by RFC1918, between each net and IPv6 net, communicate, perhaps transform to the conversion of IPv6 and transform to the conversion of IPv4 from IPv4, the mode that between different IPv4 nets, communicates from IPv6 by combination.
But the existing ALG that is used for the pay(useful) load conversion can not judge to which request displacement of a plurality of IPv4/IPv6 converting means with the address for well.
Summary of the invention
The present invention makes in view of above problem points, designed a kind of communicator (dns-proxy server [DNS proxy server]), its following formation, that is, has the device that the value of the prefix of expression network in the IPv6 address in the network and the IPv4/IPv6 converting means that uses this prefix are mapped and keep; Needing conversion to be included under the situation of IP address of pay(useful) load part of IP packet of the title request of solving,, select the corresponding IPv4/IPv6 converting means of value with this prefix, the request corresponding address with reference to the address that is contained in this packet.
In addition, at the packet of asking with the DNS backward process is in the pay(useful) load conversion of object, communicator judges that the content of the packet before the conversion is that the backward process of IPv4 address is ask and which of the backward process inquiry of IPv6 address, be inquiry or answer [response], with reference to the IPv6 address that is positioned at the different position of this packet, select the IPv4/IPv6 converting means according to different situations.
Also have, communicator of the present invention can be mapped the prefix of a plurality of IPv4/IPv6 converting means and an IPv6 address.
By packet communication apparatus of the present invention (dns-proxy server), cross in the network system that a plurality of IPv4/IPv6 converting means are connected with each other in IPv4 net and IPv6 Netcom, the address is used in the displacement that can be used for the pay(useful) load conversion from suitable IPv4/IPv6 converting means acquisition, and carries out the conversion of the IP address of upper layer.Further, be mapped by prefix a plurality of IPv4/IPv6 converting means and an IPv6 address, when being necessary to the IPv4/IPv6 converting means request address corresponding with prefix, owing at this moment can switch this person's of being requested IPv4/IPv6 converting means, the load of IPv4/IPv6 converting means is disperseed.
Further, in network system of the present invention, ask owing to can cross over the DNS backward process of IPv4 net and IPv6 net, thus even between IPv4 net and IPv6 net, also can with existing only the same service of using Email and client/server system etc. on the IPv4 network.
In addition, can not obtain from the IPv4/IPv6 converting means that is requested the address under the situation of corresponding address, use the address, just can avoid the obstruction of converting means etc. by the IPv4/IPv6 converting means request displacement to other corresponding once more with this prefix.
Description of drawings
Fig. 1 is the pie graph of communications network system that is provided with the DNS Relay Server of the present invention the 1st embodiment.
Fig. 2 is the calcspar of expression with the formation of the DNS Relay Server 1a of embodiment.
Fig. 3 is the key diagram of signal with prefix-converting means table of comparisons 160 of embodiment.
Fig. 4 is the key diagram of signal with message id-IPv6 table of comparisons 190 of embodiment.
Fig. 5 is the figure of signal with the form of the DNS message of embodiment.
Fig. 6 is the figure of signal with the form of the head 21 of the DNS message of embodiment.
Fig. 7 is the figure of signal with the form of the information office 22 of the DNS message of embodiment.
Fig. 8 is signal with the figure of the form of the answer portion 23 of the DNS message of embodiment, authority portion 24, additional information portion 25.
To be signal carry out the figure of the order of the processing that the backward process of the address of IPv6 terminal askes from the IPv4 terminal to Fig. 9.
To be signal carry out the figure of the order of the processing that the backward process of the address of IPv4 terminal askes from the IPv6 terminal to Figure 10.
Figure 11 is the pie graph of communications network system of the 2nd embodiment that is provided with the DNS Relay Server of embodiments of the present invention.
Figure 12 is the calcspar of the formation of the DNS Relay Server 1b among signal the 2nd embodiment of the present invention.
Figure 13 is the key diagram of the prefix-network numbering table of comparisons 170 with embodiment.。
Figure 14 is the key diagram of signal with network numbering-IPv4/IPv6 converting means table of comparisons 180 of embodiment.
Figure 15 is the pie graph of communications network system of the 3rd embodiment that is provided with the IPv4/IPv6 converting means that comprises the DNS Relay Server of embodiments of the present invention
Figure 16 is the calcspar of signal with the formation of the IPv4/IPv6 converting means 1c of embodiment.
Embodiment
Followingly embodiments of the invention are described with reference to accompanying drawing.
The 1st embodiment of the present invention at first is described.
Fig. 1 is the pie graph of communications network system that is provided with the DNS Relay Server of the 1st embodiment of the present invention.
In IPv6 network 600, owing to only use IPv6 as communication protocol, so can only assigned ip v6 address when backward process is ask.In addition, in IPv4 network 400 and IPv4 network 410, owing to only use IPv4 as communication protocol, so can only assigned ip v4 address when backward process is ask.
IPv4/ IPv6 converting means 101 and 102 is to be used for the destination address of the IP packet that will send from the network that connects and sender address to transform to IPv6 or transform to the device of IPv4 from IPv6 from IPv4.
Fig. 2 is the calcspar of the formation of the DNS Relay Server 1a among signal the 1st embodiment.
Message parse portion 12 resolves the message that receives, and judges whether it is inquiry or the answer message that backward process is ask, according to the content of message, and the IPv4 address or the IPv6 address of appointment when extracting for example backward process inquiry.
Address mapping information inquiry generating unit 13 generates the message that is used for being used for to the inquiry of IPv4/IPv6 address conversion device the address of IPv4, the mutual conversion of IPv6 according to the address that extracts by message parse portion 12.
The inquiry of address mapping information is answered analysis unit 14 and is received the answer message that the message that is generated by address mapping information inquiry generating unit 13 is returned and resolve its content.
Message is replaced handling part 15 will or answer the IPv4 address of appointment in the message or the IPv6 address replaces to from the displacement of IPv4/IPv6 address conversion device notice and uses the address in inquiry that above-mentioned backward process is ask.
Prefix-converting means the table of comparisons [prefix-translatorreference table] 160 of the value of the prefix of IPv4/IPv6 converting means information retaining section 16 maintenance expression IPv6 addresses and the corresponding relation of IPv4/IPv6 converting means.
Message id-IPv6 the address translation table [message ID-IPv6 address referencetable] 190 of the ID of message id maintaining part 18 maintenance expression IPv4 message and the corresponding relation of sender IPv6 address.
Fig. 3 represents to remain on the content of the prefix-converting means table of comparisons 160 of IPv4/IPv6 converting means information retaining section 16.
This prefix-converting means table of comparisons 160 is made up of the zone 162 of the information of the zone 161 of writing down prefix, record IPv4/IPv6 converting means.Prefix posting field 161 by the zone 163 of the IPv6 address value of record 128 bits, will represent that the part of the prefix of IPv6 address forms with the zone of representing from the bit number of the length that comes directly towards and write down 164.IPv4/IPv6 converting means information area t62 is made up of the zone 166 of UDP (the User Datagram Protocol) port numbering [port number] of the zone 165 of the IPv6 address of record IPv4/IPv6 converting means, record IPv4/IPv6 converting means.
Fig. 4 represents to remain on the content of the message id-IPv6 address translation table 190 of message id maintaining part 18.
This message id-IPv6 address translation table 190 is made up of the zone 191 of record IPv6 address, the zone 192 of recording messages ID.
Secondly, the backward process inquiry to the DNS in the communications network system that is provided with the DNS Relay Server of the 1st embodiment describes.
The backward process of DNS is ask by carrying out IP address mapping that backward process askes and is become backward process to ask the title (FQDN) of usefulness, realize to the title (PTR (PoinTeR) record) of this FQDN of dns server inquiry.
Carry out with the IPv4 address under the situation of backward process inquiry, use the backward process inquiry FQDN of additional " in-addr.arpa ".This backward process inquiry becomes with FQDN divides the IPv4 address of 32 bits by 8 bits, represent the respectively value of 8 bits with 10 carry digits, the order of 4 10 carry digits is turned around the form of distinguishing and be attached to the front of " in-addr.arpa " with period.For example, when searching domain name, backward process is ask and with FQDN just is from IPv4 address " 192.168.1.142 "
“142.1.168.192.in-addr.arpa”。
In addition, under the situation of carrying out the backward process inquiry with the IPv6 address, use the backward process inquiry FQDN of additional " ip6.arpa ".This backward process is ask the order that becomes the numeral that the IPv6 address of 128 bits is represented by 16 systems with FQDN and is turned the form of distinguishing and be attached to the front of " ip6.arpa " with period around.For example, the backward process of " 2001:1001 ∷ 200:e2ff:fe53:986b " inquiry is " b.6.8.9.3.5.e.f.f.f.2.e.0.0.2.0.0.0.0.0.0.0.0.0.1.0.0.1. 1.0.0.2.ip6.arpa " just with FQDN.
In addition, the backward process of IPv6 is ask and generally is expressed as with FQDN
" [x20011001000000000200e2fffe53986b/128 ] .ip6.arpa " (" " exactly is backslash).
In addition, in IPv6, sometimes because the actual installation mode backward process of system inquiry is not " ip6.arpa " with FQDN yet, but " ip6.int ".
Above-mentioned DNS message below is described.
As shown in Figure 5, DNS message is made up of head [header section] 21, information office [questionsection] 22, answer portion [answer section] 23, authority portion [authority section] 24, additional information portion [additional section] 25.In addition, the part beyond the head 21 not necessarily all exists.
As shown in Figure 6, head 21 is by the id field 210 of giving message uniquely, whether expression is the sign 211[QR field 211 to the answer of inquiry], the inquiry type field [OPCODE field] 212 of the type of expression inquiry, sign 213[flag 213] (annotate: please note and indicate 211 difference), reservation area field [reserved field] 214, expression message is the answer code field [RCODE field] 215 of the answer type of the occasion of answer, expression is stored in information office's item number field [QDCOUNT field] 216 of number of the project of information office 22, expression is stored in the answer portion resource record digital section [ANCOUNT field] 217 of number of the resource record of answer portion 23, expression is stored in the authority resource record digital section [NSCOUNTfield] 218 of number of the resource record of authority portion 24, expression is stored in additional information resource record digital section [ARCOUNT field] 219 formations such as grade of number of the resource record of additional information portion 25.
As shown in Figure 7, information office 22 is made up of domain name field [QNAME] 220, inquiry record type field [QTYPE] 221,222 of inquiry rank field [QCLASS].Domain name field 220 is the fields that store the FQDN that is used for inquiry, in the occasion that the backward process inquiry is ask, stores backward process inquiry FQDN.In inquiry record type field 221, storing the expression inquiry is IPv4 or the information of IPv6.
Answer portion 23, authority portion 24, additional information portion 25 are made of common field shown in Figure 8 respectively.That is, by the life span field [TTL field] of time of the buffer memory that storage is used for the domain name field [NAME field] 230 of the FQDN of inquiry, inquiry record type field [TYPE field] 231 that the expression inquiry is IPv4 or IPv6, the answer that stores inquiry remains on DNS Relay Server 1a, the resource record field [RDATAfield] 232 that stores the title that the answer by inquiry solves constitutes.
In addition, any field for packed data length, under the FQDN same case of all or part of and other the field of FQDN, is not to store FQDN but the pointer that stores the top part of pointing to the character string consistent with other field.The device that receives this DNS message just can access the FQDN that pointer the place ahead is put down in writing with reference to pointer.
Ask information for the DNS backward process, the value of the sign 211 of head 21 is 0, and the field that is right after it only has information office 22.
In addition, for the answer message that DNS backward process inquiry is ask, the id field 210 that the value of the ID of inquiry message is kept intact and is replicated and is stored in head 21, the value of sign 211 becomes 1.In addition, in information office 22, the content of the information office 22 of inquiry message is stored by former state.
Have again, inquiry message for DNS backward process inquiry, the domain name field 230 that is stored in answer portion with FQDN is ask in the backward process of above-mentioned IP v4 or IPv6, the value 12 of expression PTR record is stored in inquiry record type field 231, in addition, the FQDN that is endowed the machine with assigned address is stored in resource record field 232.But the domain name field of answer portion 230 is usually because identical with information office 22, storage be that the pointer with the top of FQDN is ask in the backward process of pointing to the domain name field 220 that is documented in information office.
Concrete action when next, DNS Relay Server 1a being received DNS message describes.
As the 1st kind of situation, the action when DNS Relay Server 1a receives the inquiry that the backward process of IPv6 address askes is described at first.
The DNS message that sends acceptance division 11 receptions is sent to message parse portion 12.
Message parse portion 12 resolves the content of the DNS message that receives, the words of using FQDN are ask in the backward process that contains band " ip6.arpa " (or " ip6.int ") in DNS message, be judged to be the backward process that is used for inquiry PTR record and ask DNS message, ask the backward process of DNS message from this backward process and ask with extracting the IPv6 address the FQDN.Then, message parse portion 12 sends to address mapping information inquiry generating unit 13 to this IPv6 address.
The IPv6 address that address mapping information inquiry generating unit 13 usefulness extract, retrieval is maintained at the prefix-converting means table of comparisons 160 of IPv4/IPv6 converting means information retaining section 16, the information of the corresponding IPv4/IPv6 converting means of prefix of the IPv6 address of obtaining and extracting is previously selected an IPv4/IPv6 converting means.At this moment under the situation that retrieves a plurality of IPv4/IPv6 converting means, just obtain the information of multiple arrangement, select (or a plurality of) IPv4/IPv6 converting means.
Then, to the IPv4/IPv6 converting means inquiry IPv4 address of selecting corresponding with the IPv6 address that extracts.At this moment, under the situation that can not get corresponding IPv4 address from the IPv4/IPv6 converting means that carries out inquiry, just to other the IPv4/IPv6 converting means inquiry IPv4 address corresponding of selection with the IPv6 address that extracts.Then, perhaps obtain the IPv4 address, perhaps repeat inquiry and finish up to inquiry to whole IPv4/IPv6 converting means of obtaining.This time, also can keeper [administrator] is predefined to decide number of times being defined as on the number of times that repeats.
The answer of the IPv4 address corresponding with the IPv6 address that is sent by the IPv4/IPv6 converting means is answered analysis unit 14 receptions via sending acceptance division 11 by the inquiry of address mapping information, answer analysis unit 14 by the inquiry of address mapping information and from answer message, extract the IPv4 address, obtain the IPv4 address corresponding with the IPv6 address.Then resulting IPv4 address is sent to message and replace handling part 15.
Replace handling part 15 in message, become backward process to ask the IPv4 address mapping that obtains and use FQDN, the IPv6 backward process inquiry that is included in the information office of the backward process inquiry DNS message that receives is at the beginning replaced to the backward process inquiry that contains the IPv4 address with FQDN use FQDN, generate new backward process and ask DNS message.Newly-generated backward process is ask DNS message and is sent to and keeps title to solve other dns server of information via sending acceptance division 11.
On the other hand, though whole converting means has been repeated inquiry (stipulated number repeat finish), but finally do not obtaining under the situation of IPv4 address, just the backward process that receives is being ask DNS message former state and send to and keep title to solve other dns server of information.
Next, as the 2nd kind of situation, the action when DNS Relay Server 1a is received the inquiry that the backward process of IPv4 address askes describes.
The DNS message that sends acceptance division 11 receptions is sent to message parse portion 12.
Message parse portion 12 resolves the content of the DNS message of receiving, the words of using FQDN are ask in the backward process that contains band " in-addr.arpa " in DNS message, be judged to be the backward process that is used for inquiry PTR record and ask DNS message, the backward process of asking DNS message from this backward process is ask with extracting the Ipv4 address the FQDN, and sends to address mapping information inquiry generating unit 13.
The IPv4 address that address mapping information inquiry generating unit 13 usefulness extract, retrieval is maintained at the prefix-converting means table of comparisons 160 of IPv4/IPv6 converting means information retaining section 16, the information of the corresponding IPv4/IPv6 converting means of prefix of the Ipv6 address of obtaining and extracting is previously selected the corresponding IPv4/IPv6 converting means of prefix of (or a plurality of) and the IPv6 address that extracts previously.Then, to the selecteed IPv4/IPv6 converting means inquiry IPv6 address corresponding with the IPv4 address.At this moment, as the above-mentioned situation that has obtained a plurality of IPv4/IPv6 converting means under, each device is repeated inquiry.
Result as inquiry, the answer of the IPv6 address of the IPv4 address that sent by the IPv4/IPv6 converting means is answered analysis unit 14 by the inquiry of address mapping information and received via sending acceptance division 11, answer analysis unit 14 by the inquiry of address mapping information and from answer message, extract the IPv6 address, obtain the IPv6 address corresponding with the IPv4 address.Then the IPv6 address that obtains is sent to message and replace handling part 15.
Replace handling part 15 in message, become backward process to ask the IPv6 address mapping that obtains and use FQDN, ask IPv4 backward process in the information office of DNS message and ask and replace to the backward process that contains the IPv6 address with FQDN and ask and use FQDN being included in the backward process that receives at the beginning, generate new backward process inquiry DNS message.Newly-generated backward process is ask DNS message and is sent to and keeps title to solve other dns server of information via sending acceptance division 11.
In addition, at this moment, the message id that the backward process that is included in the dns server that sends to other is ask in the DNS message is corresponding with the sender's who replaces preceding backward process inquiry inquiry Ipv6 address, is recorded in the message id-Ipv6 address translation table (with reference to Fig. 4) of ID maintaining part 18.
On the other hand, finally do not obtaining under the situation of Ipv6 address, just the backward process that receives is being ask DNS message former state and send to and keep title to solve other dns server of information.
Next, as the 3rd kind of situation, the action when DNS Relay Server 1a is received the answer that the backward process of IPv4 address is ask describes.
The DNS message that transmission acceptance division 11 receives is sent to message parse portion 12.
Message parse portion 12 resolves the content of the DNS message that receives, if the judgment is Yes the words that returning of DNS message answered (result that title solves) are ask in backward process, then ask with extracting the IPv4 address the FQDN, and send to address mapping information inquiry generating unit 13 from the backward process of the information office 22 (with reference to Fig. 6) that is stored in DNS message.
The IPv4 address that address mapping information inquiry generating unit 13 usefulness extract, retrieval is maintained at the prefix-converting means table of comparisons 160 of IPv4/IPv6 converting means information retaining section 16, obtain and send backward process and ask the sender's of DNS message the information of the corresponding IPv4/IPv6 converting means of prefix of IPv6 address, selects the corresponding IPv4/IPv6 converting means of prefix of one (or a plurality of) and sender's IPv6 address.
Then, the inquiry of the IPv6 address corresponding with the IPv4 address that is extracted by message parse portion 12 sends the IPv6 address that request is replaced the IPv4 address that extracts via sending acceptance division 11.At this moment,, select under the situation of a plurality of IPv4/IPv6 converting means, just each device is carried out inquiry repeatedly as the above-mentioned information that obtains a plurality of IPv4/IPv6 converting means.
After the answer message that sends out the IPv6 address corresponding with the IPv4 address from the IPv4/IPv6 converting means, the inquiry of address mapping information is answered analysis unit 14 and is received this answer message via sending acceptance division 11.The inquiry of address mapping information is answered analysis unit 14 and extract the IPv6 address from is answered message, sends to message and replaces handling part 15.
Replace handling part 15 in message, ask the IPv4 backward process of the information office 22 of answering message and answer portion 23 (with reference to Fig. 7) and ask to replace to ask and use FQDN being stored in the backward process that receives from dns server with the corresponding backward process in the IPv6 address that receives from the IPv4/IPv6 converting means with FQDN, generate new answer message, and send to the inquiry person that DNS message is ask in backward process via sending acceptance division 11.
At this moment, pointer in the domain name field of representing information office 22 is stored under the situation of answer portion 23, because the position through this replacement pointer changes, so the correct pointer with the top of the consistent character string of FQDN is ask in the backward process of the information office 22 after replacing to sensing and replacing.
On the other hand, finally do not obtaining under the situation of IPv6 address, the answer message former state that receives is being sent to the inquiry person that DNS message is ask in backward process.
At last, as the 4th kind of situation, the action when DNS Relay Server 1a is received the answer that the backward process of IPv6 address is ask describes.
The DNS message that sends acceptance division 11 receptions is sent to message parse portion 12.
Message parse portion 12 resolves the content of the DNS message that receives, the words of the DNS message that the inquiry of the PTR in " ip6.arpa " in the DNS message or " ip6.int " territory record is answered (result that title solves) if the judgment is Yes, just ask with extracting the IPv6 address the FQDN, and send to address mapping information inquiry generating unit 13 from the backward process of the information office 22 (with reference to Fig. 6) that is stored in DNS message.
The IPv6 address that address mapping information inquiry generating unit 13 usefulness extract, retrieval is maintained at the prefix-converting means table of comparisons 160 of IPv4/IPv6 converting means information retaining section 16, the information of the corresponding IPv4/IPv6 converting means of prefix of the IPv6 address of obtaining and extracting is previously selected one (or a plurality of) IPv4/IPv6 converting means corresponding with the prefix of the IPv6 address that extracts previously.
Then, via sending the inquiry that acceptance division 11 sends the IPv4 address corresponding with the IPv6 address that is extracted by message parse portion 12, the IPv4 address that request is replaced the IPv6 address that extracts.At this moment, as the above-mentioned situation that has obtained a plurality of IPv4/IPv6 converting means under, each device is carried out inquiry repeatedly.
After the answer message that sends out the IPv4 address corresponding with the IPv6 address from the IPv4/IPv6 converting means, the inquiry of address mapping information is answered analysis unit 14 and is received this answer message via sending acceptance division 11.The inquiry of address mapping information is answered analysis unit 14 and extract the IPv6 address from is answered message, and sends to message replacement handling part 15.
Replace handling part 15 in message, ask the IPv6 backward process of the information office 22 of answering message and answer portion 23 (with reference to Fig. 7) and ask with FQDN and replace to the backward process inquiry FQDN corresponding being stored in the backward process that receives from dns server with the IPv4 address that receives from the IPv4/IPv6 converting means, generate new answer message, and send to the inquiry person that DNS message is ask in backward process via sending acceptance division 11.
At this moment, what store in answer portion 23 is under the situation of pointer owing to through the position of this replacements pointer variation has taken place, so replace to point to replace after the backward process inquiry of the information office 22 correct pointer of the top of the consistent character string of FQDN.
On the other hand, finally do not obtaining under the situation of IPv4 address, the answer message former state that just will receive sends to the inquiry person that DNS message is ask in backward process.
Next, the action of carrying out in the communications network system of the 1st embodiment when the address of IPv6 terminal is ask in the backward process of IPv4 terminal is described.
Here, at first, in the formation of Fig. 1, following setting address and title.
FQDN " hostX.v4.net ", IPv4 address " 192.168.0.2 " are paid IPv4 terminal 412.
FQDN " hostY.v6.net ", IPv6 address " 2001 ∷ 1 " are paid IPv6 terminal 602.In addition, the dns server 601 following formations that are connected with IPv6 network 600 promptly, can be answered the backward process of the IPv6 address that belongs to subnet " 2001 ∷/96 " and ask, and carry out the solution of the title of this scope.Further, DNS Relay Server 1a sets the backward process inquiry inquiry that will belong to the IPv6 address of subnet " 2001 ∷/96 " for and sends dns server 601 to.
IPv4/IPv6 converting means 101 distributes interim IPv4 address " 10.0.0.1 " to IPv6 terminal 602, makes IPv6 address " 2001 ∷ 1 " and the corresponding login in IPv4 address " 10.0.0.1 " at address mapping table.
In addition, 101 pairs of the IPv4/IPv6 converting means IPv4 address that is connected all machines on the IPv4 network 400 generates the interim IPv6 address added prefix " 3ffe:1 ∷/96 ".Have, on IPv4/IPv6 converting means 101, login in advance has the address mapping information of DNS Relay Server 1a again.
The IPv4 address that 102 pairs of IPv4/IPv6 converting means are connected all machines on the IPv4 network 410 generates the interim IPv6 address that has added prefix " 3ffe:2 ∷/96 ".In addition, on IPv4/IPv6 converting means 102, also login the address mapping information that DNS Relay Server 1a is arranged equally in advance with IPv4/IPv6 converting means 101.
Fig. 9 is the precedence diagram that carries out the processing of asking from the backward process of the address of IPv4 terminal 402 to IPv6 terminals 602.
The message A of title that IPv4 terminal 402 is assigned to inquiry in the machine of IPv4 address " 10.0.0.1 " sends to nearest dns server 401.When dns server 401 can not solve title at oneself, just message A is sent to DNS Relay Server 1a.This message A is sending to the way of IPv6 network 600 from IPv4 network 400, is transformed into the IPv6 packet at IPv4/IPv6 converting means 101 from the IPv4 packet, arrives DNS Relay Server 1a then.
Next, DNS Relay Server 1a utilizes the prefix-converting means table of comparisons 160 of the IPv4 address search IPv4/IPv6 converting means information retaining section 16 that extracts, obtain the information of the IPv4/IPv6 converting means 101 corresponding, select the IPv4/IPv6 converting means 101 corresponding with this prefix with the prefix " 3ffe:1 ∷/96 " of the sender address of message A.
Then, DNS Relay Server 1a sends the IP packet E of the inquiry displacement corresponding with " 10.0.0.1 " with the IPv6 address to selected IPv4/IPv6 converting means 101.
The IPv4/IPv6 converting means 101 that receives IP packet E (displacement IPv6 address inquiry) is with reference to address mapping table, retrieve the IPv6 address corresponding with " 10.0.0.1 ", obtain " 2001 ∷ 1 " as corresponding IPv6 address, and send the IP packet F of answer displacement with the IP address to DNS Relay Server 1a.
" [x20010000000000000000000000000001/128 ] .ip6.arpa ", then with conversion the message A ' of FQDN part of inquiry content send to dns server.At this moment, DNS Relay Server 1a is mapped the sender's of the message id of message A ' and message A IPv6 address, and is kept in the message id-IPv6 address translation table 190 of ID maintaining part.
The dns server 601 that receives message A ' will answer with
The message B of PTR record (domain name) " hostY.v6.net " that " [x20010000000000000000000000000001/128 ] .ip6.arpa " is corresponding sends to DNS Relay Server 1a as the answer to message A '.
Message B is in the domain name field of information office 22, " [x20010000000000000000000000000001/128 ] .ip6.arpa " that uses FQDN ask in the backward process that stores promising IPv6, domain name field in answer portion 23 stores the pointer of the top of pointing to the character string consistent with the domain name field of information office 22.
" [x20010000000000000000000000000001/128 ] .ip6.arpa " resolves, and extracts the IPv6 address " 2001 ∷ 1 " of IPv6 terminal 602.
Next, the DNS Relay Server 1a message id-IPv6 address translation table 190 of the IPv6 address search ID maintaining part 18 that extracts, because the ID of the message A ' that writes down previously is identical with the ID of message B, so obtain the sender address corresponding with the ID of message B (IPv6 address) " 3ffe:1 ∷ c0a8:1 ".Further utilize the IPv6 address that obtains, prefix-converting means the table of comparisons 160 of retrieval IPv4/IPv6 converting means information retaining section 16, obtain the information of IPv4/IPv6 converting means 101 from the prefix " 3ffe:1 ∷/96 " of IPv6 address, select the IPv4/IPv6 converting means 101 corresponding with this prefix.
Then, DNS Relay Server 1a sends the IP packet G of the inquiry displacement corresponding with " 2001 ∷ 1 " with the Ipv4 address to IPv4/IPv6 converting means 101.
The IPv4/IPv6 converting means 101 that receives IP packet G (displacement IPv4 address inquiry) is with reference to address mapping table, retrieval and " 2001 ∷ 1 " corresponding IPv4 address, obtain corresponding IPv4 address " 10.0.0.1 ", and send the IP packet H of answer displacement with the IP address to DNS Relay Server 1a.
" [x20010000000000000000000000000001/128 ] .ip6.arpa " replaces to the backward process of generation and askes with FQDN " 1.0.0.10.in-addr.arpa ".Then, the message B ' that has revised the pointer of the domain name field in the refer message is sent to IPv4 terminal 402.
Message B ' is being sent to the way of IPv4 network 400 from IPv6 network 600, is transformed into the IPv4 packet at IPv4/IPv6 converting means 101 from the IPv6 packet, arrives IPv4 terminal 402 then.
By above processing, the backward process of the IPv6 address of IPv4 network ask finish.
Action when next, the backward process of the address of carrying out the IPv4 terminal from the IPv6 terminal being ask describes.
Figure 10 precedence diagram that to be expression carry out the processing that the backward process of the address of IPv4 terminal 412 askes by IPv6 terminal 602.
The message C of title that IPv6 terminal 602 is assigned to inquiry in the machine of IPv6 address " 3ffe:2 ∷ c0a8:2 " sends to nearest dns server 601.When dns server 601 can not solve title at oneself, just message C is sent to DNS Relay Server 1a.
" [x3ffe00020000000000000000c0a80002/128 ] .ip6.arpa " resolves, and extracts IPv6 address " 3ffe:2 ∷ c0a8:2 ".
Next, DNS Relay Server 1a utilizes the prefix-converting means table of comparisons 160 of the IPv6 address search IPv4/IPv6 converting means information retaining section 16 that extracts, obtain and information, select the IPv4/IPv6 converting means 102 corresponding with this prefix with the corresponding IPv4/IPv6 converting means 102 of the prefix " 3ffe:2 ∷/96 " of the IPv6 address of message C inquiry.
Then, DNS Relay Server 1a sends the IP packet I of the inquiry displacement corresponding with " 3ffe:2 ∷ c0a8:2 " with the IPv4 address to the IPv4/IPv6 converting means of selecting 102.
The IPv4/IPv6 converting means 102 that receives IP packet I (displacement IPv4 address inquiry) is with reference to address mapping table, retrieval and " 3ffe:2 ∷ c0a8:2 " corresponding IPv4 address, obtain " 192.168.0.2 " as corresponding IPv4 address, and will answer the IP packet of replacing and send to DNS Relay Server 1a with the IP address.
" [x3ffe00020000000000000000c0a80002/128 ] .ip6.arpa " replaces to the backward process of generation and askes with FQDN " 2.0.168.192.in-addr.arpa ", then to the dns server 411 message C ' of FQDN part of inquiry content that sent conversion.Message C ' is being sent to the way of IPv4 network 400 from IPv6 network 600, is transformed into the IPv4 packet at IPv4/IPv6 converting means 102 from the IPv6 packet, arrives dns server 411 then.
Receive the dns server 411 of message C ', the message D that will answer PTR record (domain name) " hostX.v4.net " corresponding with " 2.0.168.192.in-addr.arpa " sends to DNS Relay Server 1a as the answer to message C '.
Message D is being sent to the way of IPv6 network 600 from IPv4 network 400, is transformed into the IPv6 packet at IPv4/IPv6 converting means 102 from the IPv4 packet, arrives DNS Relay Server 1a then.This message D askes with FQDN " 2.0.168.192.in-addr.arpa " in the backward process that the domain name field of information office 22 stores IPv4, stores the pointer of the top of pointing to the character string consistent with the domain name field of information office 22 in the domain name field of answer portion 23.
Next, DNS Relay Server 1a utilizes the prefix-converting means table of comparisons 160 of the IPv4 address search IPv4/IPv6 converting means information retaining section 16 that extracts, obtain the information of the IPv4/IPv6 converting means 102 corresponding, select the IPv4/IPv6 converting means 102 corresponding with this prefix with the prefix " 3ffe:2 ∷/96 " of the sender address of message D.
Then, DNS Relay Server 1a sends the IP packet K (displacement IPv6 address inquiry) of the inquiry displacement corresponding with " 192.168.0.2 " with the IPv6 address to IPv4/IPv6 converting means 102.
IPv4/IPv6 converting means 102 is retrieved the IPv6 address corresponding with " 192.168.0.2 " with reference to address mapping table, obtains corresponding IPv6 address " 3ffe:2 ∷ c0a8:2 ", sends to DNS Relay Server 1a and answers the IP packet L of displacement with the IP address.
" 2.0.168.192.in-addr.arpa " is substituted into generation
“[x3ffe00020000000000000000c0a80002/12].ip6.arpa”。Then, send the message D ' of the pointer of having revised the domain name field in the refer message to IPv6 terminal 602.
IPv6 terminal 602a receives the result of the message D ' that FQDN has been replaced, and the title with machine of IPv6 address " 3ffe:2 ∷ c0a8:2 " is identified as " hostX.v4.net ".
By above processing, the DNS backward process of the IPv4 address of IPv6 network ask finish.
In the 1st embodiment of above explanation, even under the situation that IPv4 network and IPv6 network couple together by a plurality of IPv4/IPv6 converting means, have reception to the DNS of the request of DNS Relay Server 1a at the IPv6 network side, this Relay Server 1a judges the prefix of sending to target of DNS request message and selects the IPv4/IPv6 converting means corresponding with prefix, the conversion of request IPv4 address and IPv6 address, by according to conversion the address DNS is asked, can in the network that connects by a plurality of IPv4/IPv6 converting means, carry out asking to the backward process of the IP address of DNS request.
Secondly, with reference to accompanying drawing the 2nd embodiment of the present invention is illustrated.
Figure 11 is the pie graph of communications network system of the 2nd embodiment that is provided with the DNS Relay Server of embodiments of the present invention.
Compare with the 1st embodiment, difference is to be connected with a plurality of IPv4/ IPv6 converting means 102 and 103 on IPv4 network 410.In addition, the formation identical with the network of the 1st embodiment paid identical symbol, omits its explanation.
IPv4/IPv6 converting means 103 is same with IPv4/IPv6 converting means 101,102, is to be used for the destination address of the IP packet that will send from the network that connects and sender address to transform to IPv6 or transform to the device of IPv4 from IPv6 from IPv4.
This IPv4/IPv6 converting means 102 is different with the scope of 103 pairing prefixes, is included in the conversion of the IP address in the corresponding prefix respectively.
Figure 12 is the calcspar of the formation of the DNS relay services apparatus 1b among expression the 2nd embodiment of the present invention.
Also have, the formation identical with the DNS Relay Server 1b of the 1st embodiment paid identical symbol, omits its explanation.
Shown in Figure 13 is the content of prefix-network numbering table of comparisons 170.
Prefix-network numbering the table of comparisons 170 is corresponding keep IPv6 prefix, be the network numbering of the identiflication number of being paid each network corresponding individually with prefix.
Specifically, prefix-network numbering table of comparisons 170 is made up of the zone 171 of record prefix and 172 in the zone of record network numbering.In addition, zone 171 is further by the zone 173 of the IPv6 address value of record 128 bits, formed with the go forward side by side zone 174 of line item of the part of representing wherein to represent prefix from the bit number of length of top.
Shown in Figure 14 is the content of network numbering-converting means table of comparisons 180.
Network numbering-converting means the table of comparisons 180 correspondences remain the identiflication number of being paid each network individually network numbering, accept the address of IPv4/IPv6 converting means of the address mapping of this network.
Specifically, network numbering-converting means table of comparisons 180 is made up of 182 in the zone of the information of the zone 181 of writing down network numbering, record IPv4/IPv6 converting means.In addition, IPv4/IPv6 converting means information area 182 is made up of the zone 183 of the IPv6 address of record IPv4/IPv6 converting means, 184 in the zone that the udp port of record IPv4/IPv6 converting means is numbered.
Next, the processing that the backward process of carrying out IPv4 terminal 412 by IPv6 terminal 602 is ask is illustrated.
Here, at first, following setting address and title in the formation of Figure 11.
The IPv4 address of 102 pairs of all machines that are connected with IPv4 network 410 of IPv4/IPv6 converting means generates the interim IPv6 address of additional prefix " 3ffe:2 ∷/96 ".Equally, the IPv4 address of 103 pairs of all machines that are connected with IPv4 network 410 of IPv4/IPv6 converting means generates the interim IPv6 address of additional prefix " 3ffe:3 ∷/96 ".
Have, IPv4/ IPv6 converting means 102 and 103 is logined in advance in the address mapping information of DNS Relay Server 1b again.
In the inside of DNS Relay Server 1b, make the prefix " 3ffe:2 ∷/96 " of IPv6 address reach " 3ffe:3 ∷/96 " map network numbering 1 simultaneously.In addition, to network numbering 1, make IPv4/ IPv6 converting means 102 and 103 corresponding with it, displacement transmits mutually with the request between of address.
At first, IPv6 terminal 602 message of title that inquiry had a machine of IPv6 address " 3ffe:2 ∷ c0a8:2 " sends to nearest dns server 601.Dns server 601 is given DNS Relay Server 1b this inquiry forwards in the time oneself can not finishing the title solution.
" [x3ffe00020000000000000000c0a80002/128 ] .ip6.arpa " extracts the IPv6 address " 3ffe:2 ∷ c0a8:2 " of inquiry person's appointment.
Next, DNS Relay Server 1b utilizes the prefix-network numbering table of comparisons 170 of the IPv6 address search IPv4/IPv6 converting means information retaining section 17 that extracts, and obtains the corresponding network numbering " 1 " of prefix " 3ffe:2 ∷/96 " with the IPv6 address of passing through this inquiry message inquiry.Then, utilize the network numbering that obtains, the retrieval network numbering-converting means table of comparisons 180 is obtained IPv4/IPv6 converting means 102 corresponding with network numbering " 1 " and 103 information, selects the IPv4/IPv6 converting means 102,103 corresponding with this prefix.
Then, DNS Relay Server 1b at first, IPv4/IPv converting means (for example, the IPv4/IPv6 converting means 102) in selected 2 IPv4/IPv6 converting means is sent the IP packet of the inquiry displacement corresponding with " 3ffe:2 ∷ c0a8:2 " with the IPv4 address.
The IPv4/IPv6 converting means 102 that receives IP packet (displacement IPv4 address inquiry) is with reference to address mapping table, retrieval and " 3ffe:2 ∷ c0a8:2 " corresponding IPv4 address, obtain " 192.168.0.2 " as corresponding IPv4 address, send to DNS Relay Server 1a and answer the IP packet J of displacement with the IP address.
" [x3ffe00020000000000000000c0a80002/128 ] .ip6.arpa " is substituted into the backward process of generation and askes with FQDN " 2.0.168.192.in-addr.arpa ", then to the dns server 411 inquiry message of FQDN part of inquiry content that sent conversion.
Conversion the inquiry message of FQDN part be sent to the way of IPv4 network 400 from IPv6 network 600, be transformed into the IPv4 packet at IPv4/IPv6 converting means 102 from the IPv6 packet, arrive dns server 411 then.
The dns server 411 that receives this message will be answered message into " hostX.v4.net " of the PTR record (domain name) of " 2.0.168.192.in-addr.arpa " as the answer to this message, send to DNS Relay Server 1b.
This answer message is being sent to the way of IPv6 network 600 from IPv4 network 400, is transformed into the IPv6 packet at IPv4/IPv6 converting means 102 from the IPv4 packet, arrives DNS Relay Server 1b then.This message is ask with FQDN " 2.0.168.192.in-addr.arpa " in the backward process that the domain name field of information office 22 stores IPv4, stores the pointer of the top of pointing to the character string consistent with the domain name field of information office 22 in the domain name field of answer portion 23.
Next, DNS Relay Server 1b utilizes the prefix-network numbering table of comparisons 170 of the IPv4 address search IPv4/IPv6 converting means information retaining section 17 extract, obtains the corresponding network numbering of prefix " 3ffe:2 ∷/96 " with the sender address of this answer message.Further, utilize the network numbering retrieval network numbering-converting means table of comparisons 180 obtain, obtain IPv4/IPv6 converting means 102 corresponding and 103 information, select the IPv4/IPv6 converting means 102 corresponding with this prefix with network numbering 1.
Then, DNS Relay Server 1b at first the IPv4/IPv6 converting means (for example the IPv4/IPv6 converting means 103) in resulting two IPv4/IPv6 converting means send the IP packet of the inquiry displacement usefulness IPv6 address corresponding with " 192.168.0.2 ".
IPv4/IPv6 converting means 103 is retrieved the IPv6 address corresponding with " 192.168.0.2 " with reference to address mapping table, still, owing to do not exist with " 192.168.0.2 " so corresponding IPv6 address sends false answer.
The IPv4/IPv6 converting means 102 that receives IP packet (displacement IPv6 address inquiry) is with reference to address mapping table, retrieve the IPv6 address corresponding with " 192.168.0.2 ", obtain " 3ffe:2 ∷ c0a8:2 " as corresponding IPv6 address, send to DNS Relay Server 1b then and answer the IP packet of displacement with the IP address.
By above processing, the backward process of the IPv4 address D NS of IPv6 network ask finish.
In the 2nd embodiment of above explanation, same with the 1st embodiment, in the network that connects by a plurality of IPv4/IPv6 converting means, also can carry out asking to the backward process of DNS request.Particularly, at consolidated network, possess with different prefixes under the situation of a plurality of IPv4/IPv6 converting means, also can be by carry out the backward process inquiry of DNS with reference to the numbering that stores each network and the network numbering-converting means correspondence table 180 of the corresponding relation of IPv4/IPv6 converting means.
Secondly, with reference to accompanying drawing the 3rd embodiment is illustrated.
Figure 15 is the pie graph of communications network system of the 3rd embodiment that is provided with the IPv4/IPv6 converting means of the DNS Relay Server that comprises embodiments of the invention
Figure 16 is the calcspar of the formation of the IPv4/IPv6 jockey 1c among signal the 3rd embodiment of the present invention.
This IPv4/IPv6 jockey 1c is made up of the DNS Relay Server unit [DNS proxy server blade] 32 of the function of the DNS relay services apparatus 1b that possesses the 2nd embodiment, Ipv4/Ipv6 converter unit [Ipv4/Ipv6 translatorblade] 31a～31n and the switch 33 that possess the function of Ipv4/Ipv6 converting means.
Ipv4/Ipv6 converter unit 31 is with Ipv4/Ipv6 converting means 103 or 103 identical functions of program behavior realization with the 2nd embodiment.In Ipv4/Ipv6 jockey 1c, a plurality of Ipv4/Ipv6 converter units 31 are installed, they are endowed separately Ipv4 address and Ipv6 address respectively.
In DNS Relay Server unit 32, with the DNS relay 1b identical functions of program behavior realization with the 2nd embodiment.
In addition, this each unit is the computer installation that is made of CPU, storage device and communicator.
Switch 33 between each unit and network according to the path of the address switchover packet of target.
Be assigned to Ipv4/Ipv6 converter unit 31a～31n or DNS Relay Server unit 32 from the IP packet of each network input by switch.
Also have,, omit its explanation here because the flow process of processing after this is identical with the 2nd embodiment.
As among the 3rd embodiment of above formation, except the effect of the 2nd embodiment, can also realize the tediously long formation of Ipv4/Ipv6 converting means 31a～31n by comprising an Ipv4/Ipv6 jockey 1c of DNS Relay Server 32.
Claims (20)
1. packet communication apparatus, the 2nd network that is to use the 1st agreement to carry out the 1st network of data packet communication and uses the 2nd agreement to carry out data packet communication couples together by address conversion device, the packet communication apparatus of the packet that the communication between above-mentioned the 1st network and above-mentioned the 2nd network of passing on is relevant; It is characterized in that:
Possess: keep existing with ... in the employed address in above-mentioned the 1st network part of network and the corresponding relation holding device of the corresponding relation of address conversion device; According to the address conversion device choice device that is included in the above-mentioned address conversion device of address choice in the packet that receives; From the converting means of above-mentioned selected address, obtain the displacement that is used for replacing the address that is included in the above-mentioned packet that the receives address acquisition device of address; Be included in the address displacement apparatus of the address in the above-mentioned reception packet with the address displacement with this obtained displacement.
2. packet communication apparatus as claimed in claim 1 is characterized in that: above-mentioned the 1st network is different with the agreement of the 3rd layer on above-mentioned the 2nd network, and above-mentioned address packet of being replaced is contained in the part more than the 4th layer of above-mentioned reception packet.
3. packet communication apparatus as claimed in claim 1 or 2 is characterized in that: above-mentioned corresponding relation holding device can with one of the part that depends on network of address in the being included in above-mentioned reception packet a plurality of address conversion devices of corresponding maintenance; Above-mentioned address acquisition device from be included in above-mentioned reception packet the corresponding above-mentioned a plurality of address conversion devices in address in select one, this selected address converting means is sent request, obtain above-mentioned displacement and use the address.
4. packet communication apparatus as claimed in claim 3, it is characterized in that: above-mentioned address acquisition device is to the result of the above-mentioned displacement of optional address conversion device request from above-mentioned a plurality of address conversion devices with the address, use the address if can not obtain above-mentioned displacement, just among above-mentioned a plurality of address conversion devices, select other address conversion device and ask above-mentioned displacement to use the address.
5. as claim 3 or 4 described packet communication apparatus, it is characterized in that: above-mentioned address acquisition device repeatedly to the above-mentioned displacement of above-mentioned selected address conversion device request with the address up to satisfy fixed condition.
6. packet communication apparatus as claimed in claim 5 is characterized in that: above-mentioned address acquisition device is used address with the address up to obtaining necessary displacement to the above-mentioned displacement of above-mentioned selected address conversion device request repeatedly.
7. packet communication apparatus as claimed in claim 5 is characterized in that: above-mentioned address acquisition device is used the address to whole above-mentioned displacements of address conversion device request corresponding with the network portion that depends on above-mentioned address repeatedly.
8. packet communication apparatus as claimed in claim 5 is characterized in that: above-mentioned address acquisition device preestablishes the request of the address of number of times repeatedly.
9. as any one described packet communication apparatus of claim 1 to 8, it is characterized in that: above-mentioned the 1st network is the IPv6 net, represents that the value of part of the network of above-mentioned address is the prefix of IPv6 address, and it is connected in the above-mentioned IP v6 net.
10. as any one described packet communication apparatus of claim 1 to 9, it is characterized in that: the displacement of above-mentioned address is so that appointed target is an object for the corresponding title in address of inquiry and communication terminal according to DNS Protocol; If above-mentioned address is the IPv4 address, above-mentioned address acquisition device is just obtained the IPv6 address and is used the address as displacement, if above-mentioned address is the IPv6 address, just obtains the IPv4 address and uses the address as displacement.
11. as any one described packet communication apparatus of claim 1 to 9, it is characterized in that: above-mentioned address acquisition device is being obtained above-mentioned displacement with under the situation of address, the character string that is included in the address in the above-mentioned reception packet or comprises the address is replaced as above-mentioned displacement with the address or comprise the character string of address, and is sent to the target [destination] of appointment.
12. as any one described packet communication apparatus of claim 1 to 9, it is characterized in that: above-mentioned address acquisition device is sent to above-mentioned reception packet former state the target of appointment obtaining above-mentioned displacement with under the situation of address.
13. packet communication apparatus as claimed in claim 1, it is characterized in that: above-mentioned address conversion device is selected above-mentioned address conversion device according to the sender's who receives packet address [source address], and above-mentioned address acquisition device is used the address to this selected address converting means request displacement.
14. packet communication apparatus as claimed in claim 10, it is characterized in that: possess: after receiving the title solution requested packets corresponding with the IPv4 address, in the time will carrying out solving request data package and being sent to dns server with the title of the displacement of address according to the above-mentioned displacement that obtains, the identiflication number that the title of IPv6 address and above-mentioned transmission that the above-mentioned title that receives is solved the sender of request data package the solves request data package identiflication number holding device in the title solution request data package that remains on this reception that is mapped; Above-mentioned address acquisition device is after receiving the packet of answering the title corresponding with the IPv6 address, just, the IPv4 address is used in this selected address converting means request displacement according to the above-mentioned address conversion device of IPv6 address choice corresponding with the identiflication number of this answer data bag.
1 5. packet communication apparatus as claimed in claim 10, it is characterized in that: above-mentioned address acquisition device is after receiving the title solution request data package corresponding with the IPv6 address, according to be contained in this packet in the corresponding above-mentioned address conversion device of IPv6 address choice of character string that solves of request title, the IPv6 address is used in this selected address converting means request displacement.
16. packet communication apparatus as claimed in claim 15, it is characterized in that: above-mentioned address acquisition device is behind the packet that receives the answer title corresponding with the IPv4 address, according to the sender's of this packet the above-mentioned address conversion device of IPv6 address choice, the IPv6 address is used in this selected address converting means request displacement.
17. communication means, be to use the 1st network of IPv6 and use the 2nd network of IPv4 to couple together by address conversion device, connect, keep the prefix and the reception of IPv6 address with above-mentioned IP v6 network and keep communication means that use, that between above-mentioned the 1st network and above-mentioned the 2nd network, transmit the relevant packet of communication in the packet communication apparatus of corresponding relation of address conversion device of this prefix, it is characterized in that: replace dns server to receive title solution request data package; After receiving above-mentioned title solution request data package, from above-mentioned maintained corresponding relation, select above-mentioned address conversion device according to the address that is included in this title solution request; From the converting means of above-mentioned selected address, obtain displacement and use the address; Use the address with this displacement that obtains, appointment is included in character string that above-mentioned title solves address in the request data package and inquiry title is replaced as and specifies the character string of above-mentioned displacement, and transmit this title and solve request data package with address and inquiry title.
18. communication means as claimed in claim 17, it is characterized in that: after receiving the title solution request data package corresponding with the IPv4 address, when the title of the displacement that will carry out carrying out with the address according to the above-mentioned displacement that obtains solves request data package and sends to dns server, the identiflication number that the title of IPv6 address and above-mentioned transmission that the above-mentioned title that receives is solved the sender of request data package solves request data package is mapped in the title solution request data package that remains on this reception, after receiving the packet of answering the title corresponding with the IPv6 address, according to the IPv6 address choice converting means corresponding, the IPv4 address is used in this selected address converting means request displacement with the identiflication number of this answer data bag.
19. communication means as claimed in claim 18, it is characterized in that: after receiving the title solution request data package corresponding with the IPv6 address, according to be included in this packet in the corresponding above-mentioned address conversion device of IPv6 address choice of character string that solves of request title, the IPv4 address is used in this selected address converting means request displacement.
20. communication means as claimed in claim 19, it is characterized in that: after receiving the packet of answering the title corresponding with the IPv4 address, according to the sender's of this packet the above-mentioned converting means of IPv6 address choice, the IPv6 address is used in this selected address converting means request displacement.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2003140386A JP4271988B2 (en) | 2003-05-19 | 2003-05-19 | Packet communication device |
| JP2003140386 | 2003-05-19 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1551583A true CN1551583A (en) | 2004-12-01 |
| CN100536444C CN100536444C (en) | 2009-09-02 |
Family
ID=33447391
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100008851A Expired - Fee Related CN100536444C (en) | 2003-05-19 | 2004-01-18 | Data packet commmunication device |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US7315543B2 (en) |
| JP (1) | JP4271988B2 (en) |
| CN (1) | CN100536444C (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102318320A (en) * | 2009-02-13 | 2012-01-11 | 高通股份有限公司 | High rate packet data (hrpd) idle state handout from femto access point to macro access network |
| CN109600454A (en) * | 2011-04-01 | 2019-04-09 | 西门子企业通讯有限责任两合公司 | Method for addressing message in a computer network |
Families Citing this family (136)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2005236824A (en) * | 2004-02-23 | 2005-09-02 | Yokogawa Electric Corp | IPv6/IPv4 TRANSLATOR |
| US8085741B2 (en) | 2004-03-10 | 2011-12-27 | Core Wireless Licensing S.A.R.L. | System and method for pushing content to a terminal utilizing a network-initiated data service technique |
| US7529852B2 (en) * | 2004-05-17 | 2009-05-05 | Cisco Technology, Inc. | Method and apparatus for handling IPv4 DNS PTR queries across IPv4 and IPv6 networks |
| FR2871013B1 (en) * | 2004-06-01 | 2007-02-23 | Alcatel Sa | ROUTING FOR DETECTION OF SERVERS WITHIN A COMMUNICATION NETWORK |
| US7443880B2 (en) * | 2004-06-25 | 2008-10-28 | Cisco Technology, Inc. | Arrangement for reaching IPv4 public network nodes by a node in a IPv4 private network via an IPv6 access network |
| US8145908B1 (en) | 2004-10-29 | 2012-03-27 | Akamai Technologies, Inc. | Web content defacement protection system |
| US20060126614A1 (en) * | 2004-12-09 | 2006-06-15 | International Business Machines Corporation | Automatic network configuration |
| US7573903B2 (en) * | 2005-01-13 | 2009-08-11 | Yokogawa Electric Corporation | IPv6/IPv4 translator |
| CN100454891C (en) * | 2005-02-02 | 2009-01-21 | 横河电机株式会社 | IPv6/IPv4 converter |
| CN100505684C (en) * | 2005-03-29 | 2009-06-24 | 国际商业机器公司 | Network system, flow equalization method, network monitoring device and host machine |
| US7436783B2 (en) * | 2005-04-04 | 2008-10-14 | Apple Inc. | Method and apparatus for detecting a router that improperly responds to ARP requests |
| US7639686B2 (en) * | 2005-04-07 | 2009-12-29 | Cisco Technology, Inc. | Access network clusterhead for providing local mobility management of a roaming IPv4 node |
| US7411967B2 (en) * | 2005-05-06 | 2008-08-12 | Cisco Technology, Inc. | Private network gateways interconnecting private networks via an access network |
| US7827169B2 (en) * | 2005-10-24 | 2010-11-02 | Sap Ag | Methods and systems for data processing |
| JP4639152B2 (en) * | 2006-01-20 | 2011-02-23 | 株式会社日立製作所 | Communications system |
| US7903585B2 (en) * | 2006-02-15 | 2011-03-08 | Cisco Technology, Inc. | Topology discovery of a private network |
| US8804759B2 (en) * | 2006-02-28 | 2014-08-12 | Hewlett-Packard Development Company, L.P. | Network name resolution into network address |
| US7889676B1 (en) * | 2006-04-13 | 2011-02-15 | Infoblox Inc. | Systems and methods for storing and retrieving data |
| FR2903263A1 (en) * | 2006-06-30 | 2008-01-04 | France Telecom | METHOD FOR ADDRESSING SERVICE ELEMENTS AND CALL TRANSMISSION BETWEEN HETEROGENEOUS NODES |
| CN101212393B (en) * | 2006-12-29 | 2010-10-13 | 华为技术有限公司 | Medium independent switching message transmission method, system, and device |
| US8171467B1 (en) * | 2007-07-03 | 2012-05-01 | Trend Micro Incorporated | Updating of malicious code patterns using public DNS servers |
| US20090037595A1 (en) * | 2007-07-31 | 2009-02-05 | Sprint Communications Company L.P. | Selecting and applying a communication version |
| CN101803343B (en) * | 2007-09-18 | 2014-02-12 | 惠普开发有限公司 | Identifying subnet address range from DNS information |
| JP5100414B2 (en) * | 2008-01-24 | 2012-12-19 | キヤノン株式会社 | Network device management apparatus and control method therefor, network system, and program |
| US8782278B2 (en) * | 2008-03-21 | 2014-07-15 | Qualcomm Incorporated | Address redirection for nodes with multiple internet protocol addresses in a wireless network |
| JP2009239864A (en) * | 2008-03-28 | 2009-10-15 | Toshiba Corp | Information receiver and method for receiving information |
| US8046480B2 (en) * | 2008-03-31 | 2011-10-25 | Amazon Technologies, Inc. | Embedding overlay virtual network addresses in underlying substrate network addresses |
| US9456054B2 (en) | 2008-05-16 | 2016-09-27 | Palo Alto Research Center Incorporated | Controlling the spread of interests and content in a content centric network |
| DE102008048872A1 (en) * | 2008-09-25 | 2010-04-08 | Siemens Ag Österreich | Method and device for bidirectional address translation in SIP-controlled data streams between IPv4 and IPv6 data terminals |
| US7924832B2 (en) * | 2008-11-13 | 2011-04-12 | Blue Coat Systems, Inc. | Facilitating transition of network operations from IP version 4 to IP version 6 |
| US8156249B2 (en) * | 2009-02-20 | 2012-04-10 | Microsoft Corporation | Using server type to obtain network address |
| US8699515B2 (en) * | 2009-07-21 | 2014-04-15 | Cisco Technology, Inc. | Limiting of network device resources responsive to IPv6 originating entity identification |
| US8234377B2 (en) * | 2009-07-22 | 2012-07-31 | Amazon Technologies, Inc. | Dynamically migrating computer networks |
| US8509244B2 (en) * | 2009-08-14 | 2013-08-13 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for providing host node awareness for multiple NAT64 environments |
| US8923293B2 (en) | 2009-10-21 | 2014-12-30 | Palo Alto Research Center Incorporated | Adaptive multi-interface use for content networking |
| EP2517438B1 (en) * | 2009-12-23 | 2016-11-30 | Citrix Systems Inc. | Systems and methods for managing ports for rtsp across cores in a multi-core system |
| US8825859B2 (en) * | 2009-12-23 | 2014-09-02 | Citrix Systems, Inc. | System and methods for mixed mode of IPv6 and IPv4 DNS of global server load balancing |
| US9098335B2 (en) | 2009-12-23 | 2015-08-04 | Citrix Systems, Inc. | Systems and methods for managing spillover limits in a multi-core system |
| US9054943B2 (en) * | 2009-12-23 | 2015-06-09 | Citrix Systems, Inc. | Systems and methods for mixed mode handling of IPv6 and IPv4 traffic by a virtual server |
| US8509185B2 (en) | 2010-02-26 | 2013-08-13 | Telefonaktiebolaget Lm Ericsson | Enabling IPV6 mobility with NAT64 |
| US20110271005A1 (en) * | 2010-04-30 | 2011-11-03 | Sonus Networks, Inc. | Load balancing among voip server groups |
| CN101917491A (en) * | 2010-05-20 | 2010-12-15 | 中兴通讯股份有限公司 | Method and terminal for improving domain name resolution efficiency |
| US8750297B2 (en) | 2010-05-20 | 2014-06-10 | Comcast Cable Communications, Llc | Ascertaining per-hop network characteristics |
| US9276901B2 (en) * | 2010-05-21 | 2016-03-01 | Brian Heder | Method, system, and apparatus for transitioning from IPv4 to IPv6 |
| US8504722B2 (en) * | 2010-06-14 | 2013-08-06 | Telefonaktiebolaget Lm Ericsson | Enhancing DS-lite with private IPV4 reachability |
| US8347100B1 (en) | 2010-07-14 | 2013-01-01 | F5 Networks, Inc. | Methods for DNSSEC proxying and deployment amelioration and systems thereof |
| US20120259998A1 (en) * | 2011-04-11 | 2012-10-11 | Matthew Kaufman | System and method for translating network addresses |
| US9680791B2 (en) | 2011-07-29 | 2017-06-13 | Fortinet, Inc. | Facilitating content accessibility via different communication formats |
| US20130103853A1 (en) * | 2011-07-29 | 2013-04-25 | 3Crowd Technologies, Inc. | Directing clients based on communication format |
| US8621038B2 (en) | 2011-09-27 | 2013-12-31 | Cloudflare, Inc. | Incompatible network gateway provisioned through DNS |
| US8438240B2 (en) * | 2011-09-27 | 2013-05-07 | Cloudflare, Inc. | Distributing transmission of requests across multiple IP addresses of a proxy server in a cloud-based proxy service |
| US8751686B2 (en) * | 2011-10-05 | 2014-06-10 | Cisco Technology, Inc. | Forwarding IPv6 packets based on shorter addresses derived from their IPv6 destination addresses |
| US8719450B2 (en) * | 2011-10-31 | 2014-05-06 | Cable Television Laboratories, Inc. | Internet protocol (IP) address translation |
| US10230687B1 (en) | 2011-11-16 | 2019-03-12 | Google Llc | Apparatus and method for correlating addresses of different Internet protocol versions |
| WO2013120074A1 (en) * | 2012-02-11 | 2013-08-15 | Vid Scale, Inc. | Method and apparatus for video aware hybrid automatic repeat request |
| US9008093B2 (en) * | 2012-03-12 | 2015-04-14 | Comcast Cable Communications, Llc | Stateless protocol translation |
| US9621495B1 (en) * | 2012-12-10 | 2017-04-11 | Jeffrey Brian Shumate | Anonymous messaging proxy |
| EP2928129B1 (en) * | 2012-12-18 | 2018-05-09 | Huawei Technologies Co., Ltd. | Method and network devices for determining an administrative domain in a virtual cluster |
| JP2014135592A (en) * | 2013-01-09 | 2014-07-24 | Sony Corp | Information processing device, information processing method, and information processing system |
| US9391951B2 (en) * | 2013-08-29 | 2016-07-12 | Alcatel Lucent | Communication network with distributed network address translation functionality |
| US10098051B2 (en) | 2014-01-22 | 2018-10-09 | Cisco Technology, Inc. | Gateways and routing in software-defined manets |
| US9954678B2 (en) | 2014-02-06 | 2018-04-24 | Cisco Technology, Inc. | Content-based transport security |
| US9836540B2 (en) | 2014-03-04 | 2017-12-05 | Cisco Technology, Inc. | System and method for direct storage access in a content-centric network |
| US9626413B2 (en) | 2014-03-10 | 2017-04-18 | Cisco Systems, Inc. | System and method for ranking content popularity in a content-centric network |
| US9716622B2 (en) | 2014-04-01 | 2017-07-25 | Cisco Technology, Inc. | System and method for dynamic name configuration in content-centric networks |
| US9473576B2 (en) | 2014-04-07 | 2016-10-18 | Palo Alto Research Center Incorporated | Service discovery using collection synchronization with exact names |
| US9992281B2 (en) | 2014-05-01 | 2018-06-05 | Cisco Technology, Inc. | Accountable content stores for information centric networks |
| CN104253877A (en) * | 2014-05-21 | 2014-12-31 | 四川长虹电器股份有限公司 | Device type and IP (Internet Protocol) address-based comprehensive naming method and system |
| US9609014B2 (en) | 2014-05-22 | 2017-03-28 | Cisco Systems, Inc. | Method and apparatus for preventing insertion of malicious content at a named data network router |
| US9699198B2 (en) | 2014-07-07 | 2017-07-04 | Cisco Technology, Inc. | System and method for parallel secure content bootstrapping in content-centric networks |
| US9621354B2 (en) | 2014-07-17 | 2017-04-11 | Cisco Systems, Inc. | Reconstructable content objects |
| US9590887B2 (en) | 2014-07-18 | 2017-03-07 | Cisco Systems, Inc. | Method and system for keeping interest alive in a content centric network |
| US9729616B2 (en) | 2014-07-18 | 2017-08-08 | Cisco Technology, Inc. | Reputation-based strategy for forwarding and responding to interests over a content centric network |
| US9882964B2 (en) | 2014-08-08 | 2018-01-30 | Cisco Technology, Inc. | Explicit strategy feedback in name-based forwarding |
| US9503365B2 (en) * | 2014-08-11 | 2016-11-22 | Palo Alto Research Center Incorporated | Reputation-based instruction processing over an information centric network |
| US9729662B2 (en) | 2014-08-11 | 2017-08-08 | Cisco Technology, Inc. | Probabilistic lazy-forwarding technique without validation in a content centric network |
| US9800637B2 (en) | 2014-08-19 | 2017-10-24 | Cisco Technology, Inc. | System and method for all-in-one content stream in content-centric networks |
| US10069933B2 (en) | 2014-10-23 | 2018-09-04 | Cisco Technology, Inc. | System and method for creating virtual interfaces based on network characteristics |
| US9590948B2 (en) | 2014-12-15 | 2017-03-07 | Cisco Systems, Inc. | CCN routing using hardware-assisted hash tables |
| US10237189B2 (en) | 2014-12-16 | 2019-03-19 | Cisco Technology, Inc. | System and method for distance-based interest forwarding |
| US10003520B2 (en) | 2014-12-22 | 2018-06-19 | Cisco Technology, Inc. | System and method for efficient name-based content routing using link-state information in information-centric networks |
| US9660825B2 (en) | 2014-12-24 | 2017-05-23 | Cisco Technology, Inc. | System and method for multi-source multicasting in content-centric networks |
| US9946743B2 (en) | 2015-01-12 | 2018-04-17 | Cisco Technology, Inc. | Order encoded manifests in a content centric network |
| US9954795B2 (en) | 2015-01-12 | 2018-04-24 | Cisco Technology, Inc. | Resource allocation using CCN manifests |
| US9916457B2 (en) | 2015-01-12 | 2018-03-13 | Cisco Technology, Inc. | Decoupled name security binding for CCN objects |
| US9832291B2 (en) | 2015-01-12 | 2017-11-28 | Cisco Technology, Inc. | Auto-configurable transport stack |
| US10333840B2 (en) | 2015-02-06 | 2019-06-25 | Cisco Technology, Inc. | System and method for on-demand content exchange with adaptive naming in information-centric networks |
| US10075401B2 (en) | 2015-03-18 | 2018-09-11 | Cisco Technology, Inc. | Pending interest table behavior |
| US10075402B2 (en) | 2015-06-24 | 2018-09-11 | Cisco Technology, Inc. | Flexible command and control in content centric networks |
| US10701038B2 (en) | 2015-07-27 | 2020-06-30 | Cisco Technology, Inc. | Content negotiation in a content centric network |
| US9986034B2 (en) | 2015-08-03 | 2018-05-29 | Cisco Technology, Inc. | Transferring state in content centric network stacks |
| US9832123B2 (en) | 2015-09-11 | 2017-11-28 | Cisco Technology, Inc. | Network named fragments in a content centric network |
| US11063981B2 (en) | 2015-09-11 | 2021-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Gateway, client device and methods for facilitating secure communication between a client device and an application server using redirect |
| US10355999B2 (en) | 2015-09-23 | 2019-07-16 | Cisco Technology, Inc. | Flow control with network named fragments |
| US9977809B2 (en) | 2015-09-24 | 2018-05-22 | Cisco Technology, Inc. | Information and data framework in a content centric network |
| US10313227B2 (en) | 2015-09-24 | 2019-06-04 | Cisco Technology, Inc. | System and method for eliminating undetected interest looping in information-centric networks |
| US10454820B2 (en) | 2015-09-29 | 2019-10-22 | Cisco Technology, Inc. | System and method for stateless information-centric networking |
| US10263965B2 (en) | 2015-10-16 | 2019-04-16 | Cisco Technology, Inc. | Encrypted CCNx |
| US9912776B2 (en) | 2015-12-02 | 2018-03-06 | Cisco Technology, Inc. | Explicit content deletion commands in a content centric network |
| US10097346B2 (en) | 2015-12-09 | 2018-10-09 | Cisco Technology, Inc. | Key catalogs in a content centric network |
| US10257271B2 (en) | 2016-01-11 | 2019-04-09 | Cisco Technology, Inc. | Chandra-Toueg consensus in a content centric network |
| US10797888B1 (en) | 2016-01-20 | 2020-10-06 | F5 Networks, Inc. | Methods for secured SCEP enrollment for client devices and devices thereof |
| US10305864B2 (en) | 2016-01-25 | 2019-05-28 | Cisco Technology, Inc. | Method and system for interest encryption in a content centric network |
| US10043016B2 (en) | 2016-02-29 | 2018-08-07 | Cisco Technology, Inc. | Method and system for name encryption agreement in a content centric network |
| US10742596B2 (en) | 2016-03-04 | 2020-08-11 | Cisco Technology, Inc. | Method and system for reducing a collision probability of hash-based names using a publisher identifier |
| US10003507B2 (en) | 2016-03-04 | 2018-06-19 | Cisco Technology, Inc. | Transport session state protocol |
| US10051071B2 (en) | 2016-03-04 | 2018-08-14 | Cisco Technology, Inc. | Method and system for collecting historical network information in a content centric network |
| US10264099B2 (en) | 2016-03-07 | 2019-04-16 | Cisco Technology, Inc. | Method and system for content closures in a content centric network |
| US10067948B2 (en) | 2016-03-18 | 2018-09-04 | Cisco Technology, Inc. | Data deduping in content centric networking manifests |
| US10091330B2 (en) | 2016-03-23 | 2018-10-02 | Cisco Technology, Inc. | Interest scheduling by an information and data framework in a content centric network |
| US10826868B2 (en) * | 2016-03-29 | 2020-11-03 | T-Mobile Usa, Inc. | NAT aware DNS |
| US10320760B2 (en) | 2016-04-01 | 2019-06-11 | Cisco Technology, Inc. | Method and system for mutating and caching content in a content centric network |
| US9930146B2 (en) | 2016-04-04 | 2018-03-27 | Cisco Technology, Inc. | System and method for compressing content centric networking messages |
| US10425503B2 (en) | 2016-04-07 | 2019-09-24 | Cisco Technology, Inc. | Shared pending interest table in a content centric network |
| US10063414B2 (en) | 2016-05-13 | 2018-08-28 | Cisco Technology, Inc. | Updating a transport stack in a content centric network |
| US10084764B2 (en) | 2016-05-13 | 2018-09-25 | Cisco Technology, Inc. | System for a secure encryption proxy in a content centric network |
| US10103989B2 (en) | 2016-06-13 | 2018-10-16 | Cisco Technology, Inc. | Content object return messages in a content centric network |
| US10305865B2 (en) | 2016-06-21 | 2019-05-28 | Cisco Technology, Inc. | Permutation-based content encryption with manifests in a content centric network |
| US10148572B2 (en) | 2016-06-27 | 2018-12-04 | Cisco Technology, Inc. | Method and system for interest groups in a content centric network |
| US10009266B2 (en) | 2016-07-05 | 2018-06-26 | Cisco Technology, Inc. | Method and system for reference counted pending interest tables in a content centric network |
| US9992097B2 (en) | 2016-07-11 | 2018-06-05 | Cisco Technology, Inc. | System and method for piggybacking routing information in interests in a content centric network |
| US10122624B2 (en) | 2016-07-25 | 2018-11-06 | Cisco Technology, Inc. | System and method for ephemeral entries in a forwarding information base in a content centric network |
| US10069729B2 (en) | 2016-08-08 | 2018-09-04 | Cisco Technology, Inc. | System and method for throttling traffic based on a forwarding information base in a content centric network |
| US10956412B2 (en) | 2016-08-09 | 2021-03-23 | Cisco Technology, Inc. | Method and system for conjunctive normal form attribute matching in a content centric network |
| US10142230B2 (en) * | 2016-08-15 | 2018-11-27 | Vonage Business Inc. | Method and apparatus for transmitting messages associated with internet protocol version 4 (IPv4) addresses on an internet protocol version 6 (IPv6) network |
| US10033642B2 (en) | 2016-09-19 | 2018-07-24 | Cisco Technology, Inc. | System and method for making optimal routing decisions based on device-specific parameters in a content centric network |
| US10212248B2 (en) | 2016-10-03 | 2019-02-19 | Cisco Technology, Inc. | Cache management on high availability routers in a content centric network |
| US10447805B2 (en) | 2016-10-10 | 2019-10-15 | Cisco Technology, Inc. | Distributed consensus in a content centric network |
| US10135948B2 (en) | 2016-10-31 | 2018-11-20 | Cisco Technology, Inc. | System and method for process migration in a content centric network |
| US10243851B2 (en) | 2016-11-21 | 2019-03-26 | Cisco Technology, Inc. | System and method for forwarder connection information in a content centric network |
| EP3462710B1 (en) * | 2017-09-29 | 2020-01-15 | Siemens Aktiengesellschaft | Method for providing a name service within an industrial automation system and switch |
| KR20210049335A (en) * | 2019-10-25 | 2021-05-06 | 삼성전자주식회사 | Method of translating ip packet for tethering service and communication system performing the same |
| US11496439B1 (en) * | 2021-03-23 | 2022-11-08 | Amazon Technologies, Inc. | Stateless high-capacity network address translation service |
| WO2023001383A1 (en) * | 2021-07-23 | 2023-01-26 | Huawei Cloud Computing Technologies Co., Ltd. | Proxy dns server and methods of running ipv4 applications in an ipv6 only environment |
| US11863515B2 (en) * | 2021-12-10 | 2024-01-02 | Cisco Technology, Inc. | Systems and methods for translating IPV6 packets for DIA in an SD-WAN environment |
| US20230216825A1 (en) * | 2021-12-31 | 2023-07-06 | T-Mobile Innovations Llc | Gateway based ip address translation in communication networks |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE69737645T2 (en) * | 1996-11-01 | 2007-11-22 | Hitachi, Ltd. | Communication method between an IPv4 terminal and an IPv6 terminal and IPv4-IPv6 conversion apparatus |
| US6493765B1 (en) * | 1999-03-23 | 2002-12-10 | Nortel Networks Limited | Domain name resolution in a network having multiple overlapping address domains |
| JP4186446B2 (en) | 2001-09-11 | 2008-11-26 | 株式会社日立製作所 | Address translation method |
| JP4349766B2 (en) | 2001-12-07 | 2009-10-21 | 株式会社日立製作所 | Address translation device |
| US7272148B2 (en) * | 2002-06-27 | 2007-09-18 | Hewlett-Packard Development Company, L.P. | Non-ALG approach for application layer session traversal of IPv6/IPv4 NAT-PT gateway |
-
2003
- 2003-05-19 JP JP2003140386A patent/JP4271988B2/en not_active Expired - Fee Related
-
2004
- 2004-01-16 US US10/758,211 patent/US7315543B2/en not_active Expired - Fee Related
- 2004-01-18 CN CNB2004100008851A patent/CN100536444C/en not_active Expired - Fee Related
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102318320A (en) * | 2009-02-13 | 2012-01-11 | 高通股份有限公司 | High rate packet data (hrpd) idle state handout from femto access point to macro access network |
| CN104967699A (en) * | 2009-02-13 | 2015-10-07 | 高通股份有限公司 | High rate packet data (HRPD) idle state handout from femto access point to macro access network |
| US9185607B2 (en) | 2009-02-13 | 2015-11-10 | Qualcomm Incorporated | High rate packet data (HRPD) idle state handout from femto access point to macro access network |
| CN109600454A (en) * | 2011-04-01 | 2019-04-09 | 西门子企业通讯有限责任两合公司 | Method for addressing message in a computer network |
Also Published As
| Publication number | Publication date |
|---|---|
| JP2004343620A (en) | 2004-12-02 |
| US7315543B2 (en) | 2008-01-01 |
| US20040233916A1 (en) | 2004-11-25 |
| CN100536444C (en) | 2009-09-02 |
| JP4271988B2 (en) | 2009-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1551583A (en) | Data packet commmunication device | |
| CN1423201A (en) | Address changing device, message treatment method and apparatus | |
| CN1214580C (en) | Data caching on the internet | |
| CN1503526A (en) | Address translator and method for management of address translation rules | |
| CN1251458C (en) | System for transmission/reception of E-mail with attached files | |
| CN1310152C (en) | Exchanging method and exchanging device | |
| CN1236583C (en) | System for selecting path between areas | |
| CN1574835A (en) | Ip address translator and packet transfer apparatus | |
| CN1661990A (en) | Protocol translator | |
| CN1487711A (en) | Network system, back agency, computer equipment, data processing method and program products | |
| CN1767435A (en) | Data communication method and system | |
| CN1925462A (en) | Cache system | |
| CN1864377A (en) | Mail distribution system, mail distribution method, and mail distribution program | |
| CN1520123A (en) | Answering method to address inquire and program and appts. thereof, and address notifying method, program and appts. | |
| CN1855825A (en) | Computer system | |
| CN1505429A (en) | Mobile terminal equipment and packet communication method between terminals | |
| CN1947106A (en) | Notification method, connection apparatus, communication method, and program | |
| CN1859332A (en) | System, device and method for synchronously processing e-mail using data | |
| CN1839592A (en) | Packet relay device | |
| CN1531263A (en) | Communication system, connector, communication method and identifying method | |
| CN1525709A (en) | Name resolution server and packet transfer device | |
| CN1450765A (en) | Servo load balance system, apparatus and content management apparatus | |
| CN101047662A (en) | Method and system for implementing multi-identity immediate message communication and present service of single account number | |
| CN1838642A (en) | Method and system for realizing ask-answer service using instantaneous message system | |
| CN1694459A (en) | Method for updating dynamic field name in IPv6 network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20060414 Address after: Tokyo, Japan, Japan Applicant after: Hitachi Communications Technology Co., Ltd. Address before: Tokyo, Japan, Japan Applicant before: Hitachi Ltd. Co-applicant before: Hitachi Communications Technology Co., Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: HITACHI CO., LTD. Free format text: FORMER OWNER: HITACHI COMMUNICATION TECHNOLOGIES LTD. Effective date: 20100323 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20100323 Address after: Tokyo, Japan, Japan Patentee after: Hitachi Ltd. Address before: Tokyo, Japan, Japan Patentee before: Hitachi Communications Technology Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090902 Termination date: 20180118 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |