CN1275443C - Method for realizing distributed application tier conversion gate-link in network processor - Google Patents

Method for realizing distributed application tier conversion gate-link in network processor Download PDF

Info

Publication number
CN1275443C
CN1275443C CNB2003101010680A CN200310101068A CN1275443C CN 1275443 C CN1275443 C CN 1275443C CN B2003101010680 A CNB2003101010680 A CN B2003101010680A CN 200310101068 A CN200310101068 A CN 200310101068A CN 1275443 C CN1275443 C CN 1275443C
Authority
CN
China
Prior art keywords
packet
bag
protocol
ipv4
ipv6
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.)
Expired - Fee Related
Application number
CNB2003101010680A
Other languages
Chinese (zh)
Other versions
CN1529481A (en
Inventor
孙红兵
李忠诚
殷昭印
石晶林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Institute of Computing Technology of CAS
Original Assignee
Institute of Computing Technology of CAS
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Institute of Computing Technology of CAS filed Critical Institute of Computing Technology of CAS
Priority to CNB2003101010680A priority Critical patent/CN1275443C/en
Publication of CN1529481A publication Critical patent/CN1529481A/en
Application granted granted Critical
Publication of CN1275443C publication Critical patent/CN1275443C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

The present invention relates to a method of a domain name service (DNS) conversion gateway and a file transfer protocol (FTP) conversion gateway in the technical field of computer network communication. The method comprises the following steps: step 1: a receive port receives a data pack; step 2: an address and a protocol of the received data pack are converted on a micro engine; step 3: a port number of the protocol is checked to find out a domain name service pack or an FTP command pack, a data pack is structured by a taking along technique, and the structured data pack is sent ot a Strong ARM to be processed; step 4: Strong ARM processes calls a module of the DNS conversion gateway to process the DNS pack and calls a module of the FTP conversion gateway to process the FTP command pack; step 5: the data pack processed by the conversion module of an application layer gateway is sent to a transmission queue to be transmitted. The realization of the method on a network processor platform is tested, and the result proves that NAT-PT implemented by the method can process mutual accesses between an IPv4 network and an IPv6 in real time.

Description

The inner method that realizes Distributed Application layer transfer gateway of network processing unit
Technical field
The present invention relates to the computer network communication technology field, the inner method that realizes distribution applications layer transfer gateway of particularly a kind of network processing unit, be a kind of on network processor platform, be raising IPv4 (Internet Protocol Version 4) and IPv6 (Internet Protocol Version 6) protocol conversion performance, realize a kind of method of Distributed Application layer conversion process in the sheet.
Background technology
The IPv6 agreement is the Next Generation Internet network agreement that replaces the IPv4 agreement, and it has many new characteristics and function.But IPv6 with now on the internet IPv4 agreement of extensive use incompatible, for example address size, package head format difference or the like will be so IPv4 will be a long-term process to the IPv6 transition.How realizing seamlessly transitting in this process is the problem that adopts the people of IPv6 agreement at first to face.On behalf of mechanism, the typical case who realizes IPv4 and IPv6 intercommunication be at present: NAT-PT (Network addresstransition-Protocol translation, address transition-protocol translation mechanism) and TRT (TransportRelay transition, transport relay translating mechanism).
NAT-PT carries out header and semantic translation between IPv4 grouping and IPv6 grouping when doing the IPv4/IPv6 address transition.Be applicable to the communication between pure IPv4 website and the pure IPv6 website.For the upper-layer protocol of some embedded address informations, as domain name service and file transfer protocol (FTP), NAT-PT needs and application layer gateway cooperated finished translation.The concrete regulation of NAT-PT can be referring to RFC2766.RFC 2766 has stipulated how to realize address translation and has had the node in following two networks of situation of domain name service transfer gateway support how to realize communication.Application layer conversion gateway (Applicationlevel gateway) is meant the gateway that carries out conversion process in application layer.The ALG conversion that current most of IPv4/IPv6 switch technology all will relate to comprises: domain name service transfer gateway and file transfer protocol (FTP) transfer gateway etc.If there is not the support of domain name service transfer gateway, NAT-PT can only realize initiating by IPv6 with IPv4 between communicate by letter, otherwise bag will be dropped.The TRT technology is a kind of switch technology of carrying out relaying in transport layer.If its realization does not have the support of application layer conversion gateway can only realize the communication that IPv6 initiates yet.For the order that contains the IP address in the PORT even load of using in the file transfer protocol (FTP), also must translate when passing through the network of two kinds of employing different IP agreements the IP address in the load.
The relevant regulations of domain name service transfer gateway is seen RFC2694, and this standard mainly is that the function of domain name service transfer gateway is stipulated.UDP (User Datagram Protoco (UDP)) is adopted in common domain name service transport layer again, and file transfer protocol (FTP) adopts TCP (transmission control protocol) in transport layer.How to realize that application layer conversion gateway people have different opinions.Some advocate application layer conversion gateway and the NAT-PT realization that combines, and influence the performance of whole NAT-PT for fear of the realization of application layer conversion but also there are groups of people to think, suggestion is done an independently acting server operation to the application layer conversion gateway.
NAT-PT can carry out software programming and realize just as other network equipments on general processor, also can realize with application-specific integrated circuit (ASIC) (ASIC) chip hardware.The benefit that software programming realizes is to implement fairly simplely, and also relatively flexibly, carry out more easily in the new capital of upgrading more.Its shortcoming is exactly that efficient is lower, when network speed is slow, can also bear, but seem unable to do what one wishes for data traffic huge on the backbone network, can constitute network bottleneck.On the contrary, realize with dedicated IC chip, can reach very high performance, still, implement more complexly, and the development time is long.Because dedicated IC chip can not be programmed,, be difficult to upgrading so in a single day just realize not malleable.By comparative analysis, the implementation of processor Network Based has just shown the superiority that it is huge.
IXP1200 series is the core product of the employing IXA framework of Intel Company's release, it structurally is divided into control and two planes of data, control plane is a StrongARM processor, mainly be that responsible maintain system information and Coordination Treatment are partly worked, datum plane is then by a plurality of risc processors---and micro engine (MicroEngine) and other specialized hardwares are formed, be responsible for the microcode and the order that utilize datum plane to issue, directly network data.Its basic structure is: a dominant frequency reaches as high as the micro engine able to programme (each micro engine comprises 4 hardware threads again) of the processing core StrongARM of 232M hertz, 6 risc architectures, one 64 IX Bus (dominant frequency reaches as high as 85MHz), 32 SRAM interface unit (operating frequency is half of core frequency), 64 sdram interface unit (operating frequency is half of core frequency), one 32 pci bus interface unit (dominant frequency reaches as high as the 66M hertz).
Summary of the invention
The object of the present invention is to provide a kind of raising conversion performance that on network processor platform, is, in the inner method that realizes the conversion of Distributed Application layer transfer gateway of network processing unit.This time this method that proposes mainly is rationally to utilize the multiprocessor of network processing unit hardware platform, the characteristic of hardware multithreading, and application layer protocols such as domain name service and file transfer are carried out distributed conversion process.Micro engine is responsible for receiving packet and the packet of receiving is carried out preliminary treatment in network layer in the network processing unit.Need carry out packet that application layer conversion handles delivers on the StrongARM by the data channel between micro engine and StrongARM and handles.StrongARM judges that according to port numbers what receive is which kind of application layer data bag determines to call application corresponding layer processing module.In order to realize the ALG conversion process on the StrongARM, when sending on the StrongARM, adopts packet piggy mechanism, for the conversion of application layer is submitted necessary information.The piggy mechanism here refers to a kind of a kind of technology of transmitting information, promptly in the back of the normal packet that transmits incidentally this packet through information such as the source address before address transition, source port, destination address, destination interfaces.We to this method the realization on Intel IXP1200 network processor platform test, the result proves the application layer conversion gateway binding data aspect address translation feature of realizing with this method, the exchanging visit of process IP v4 network and IPv6 network real-time and efficiently, the service of support has comprised: WWW, TELNET, email, DNS, FTP.Piggy mechanism in this invention provides a kind of effective communication mode for communicating by letter between StrongARM and micro engine.
Technical scheme of the present invention:
A kind of domain name service transfer gateway of processor platform Network Based and file transfer protocol (FTP) transfer gateway implementation method, by the packet that needs the ALG conversion process is carried out distributed treatment, to guarantee the conversion performance of whole NAT-PT system, it is characterized in that concrete steps are as follows:
Step 1: receiving port receives packet;
Step 2: on micro engine, the packet that receives is carried out address and protocol conversion;
Step 3: check protocol port number, discovery is domain name service bag or file transfer protocol (FTP) order bag, adopts piggy mechanism, the construction data bag, and send StrongARM to handle the posttectonic packet;
Step 4:StrongARM calls domain name service transfer gateway resume module to the domain name service bag, and file transfer protocol (FTP) order bag is called file transfer protocol (FTP) transfer gateway resume module;
Step 5: it is to be sent that the packet after the ALG module processing is delivered to transmit queue etc.
Wherein the step 2 pair packet that receives at first carries out the IP address transition, comprises the conversion of packet header protocol format, and execution in step 3 then.
Wherein step 3 adopts piggy mechanism, the source address, source port, the destination address that need when incidentally carrying out the ALG conversion process on the StrongARM.
Wherein step 3 will judge whether bag is domain name service bag and file transfer protocol (FTP) order bag according to the port numbers of transport layer, if these two kinds of bags are then delivered on the StrongARM nuclear by the data channel between micro engine and StrongARM and handled.
Wherein step 4 will be domain name service bag or file transfer protocol (FTP) order bag according to the type of the bag of receiving, judge whether to call domain name service transfer gateway processing module, or file transfer protocol (FTP) transfer gateway processing module.
In the equipment of implementing IPv4 and IPv6 conversion, need the bag of application layer conversion gateway processes not only need carry out address and package head format conversion usually at the IP layer, also to translate the load that contains the IP address.If NAT and application layer conversion gateway are integrated in the same system, and unreasonable design uniform distribution load will constitute bottleneck to the conversion performance of whole system.This method is exactly that conversion of IP layer and application layer conversion gateway function are being integrated under the prerequisite of same system, utilize the characteristics of network processing unit and both can ensure the NAT-PT performance, the implementation method of performance application layer transfer gateway can be provided again at the characteristic Design of network traffics is a kind of.The main thought of this method is exactly that the bag that needs carry out the application layer conversion gateway processes is carried out distributed treatment.To need the bag of application layer conversion gateway processes at first to carry out the NAT conversion through the micro engine of network processing unit, the conversion micro engine can judge whether that needs send the control aspect to handle according to the source and destination port of bag, handles if then deliver on the strong ARM by the passage between micro engine and strong ARM.The conversion micro engine continues to handle other packet.Most of network packet do not need the processing through the application layer conversion gateway, only need carry out NAT conversion and packet header protocol translation on micro engine, directly send by sending micro engine then.The hardware HASH that network processing unit provides has ensured that micro engine searches the speed of NAT table clause, and these can reach linear speed basically through the packet of NAT conversion process.For the packet that needs the application layer conversion gateway processes, the processing in packet header realizes on micro engine that also strong ARM is responsible for the load of bag is analyzed and changed.
Description of drawings
Fig. 1 is the UDP bag flow path switch figure from IPv6 to IPv4 of the present invention.
Fig. 2 is the UDP bag flow path switch figure from IPv4 to IPv6 of the present invention.
Fig. 3 is the TCP bag flow path switch figure from IPv6 to IPv4 of the present invention.
Fig. 4 is the TCP bag flow path switch figure from IPv4 to IPv6 of the present invention.
To be TCP when conversion bag of the present invention from IPv6 to IPv4 deliver to packet format figure on the StrongArm through micro engine to Fig. 5.
Among Fig. 1, after microcode handling procedure on the step s1 micro engine is received a UDP message bag from the IPv6 network port, at first step s2 looks into the NAT table according to the IPv6 address, get corresponding IPv4 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv4 protocol format in packet header, step s3 microcode handling procedure judges according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s4 microcode handling procedure can continue the processing of this packet, calculate the verification of UDP, then it is sent by the IPv4 port; Otherwise this packet of step s5 will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, usually the UDP bag of delivering on the StrongArm all is the domain name service packet, handle so application layer usually all can step s6 after receiving such packet be called domain service protocol conversion process module, the domain service protocol conversion process is finished after the corresponding protocol conversion process and can step s7 to be recomputated a pseudo-verification and and packet sent from the IPv4 network port.
Among Fig. 2, after microcode handling procedure on the step s8 micro engine is received a UDP message bag from the IPv4 network port, at first step s9 looks into the NAT table according to the IPv4 address, get corresponding IPv6 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv6 protocol format in packet header, step s 10 microcode handling procedures judge according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s11 microcode handling procedure can continue the processing of this packet, calculate the verification of UDP, then it is sent by the IPv6 port, otherwise this packet of step s12 will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, usually the UDP bag of delivering on the StrongArm all is the domain name service packet, finishes after the corresponding protocol conversion process and can step s14 to recomputate a pseudo-verification and and packet sent from the IPv6 network port so application layer usually all can invocation step s13 domain service protocol conversion process module after receiving such packet be handled the domain service protocol conversion process.
Among Fig. 3, after microcode handling procedure on the step s15 micro engine is received a tcp data bag from the IPv6 network port, at first step s16 looks into the NAT table according to the IPv6 address, get corresponding IPv4 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv4 protocol format in packet header, step s17 microcode handling procedure judges according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s18 microcode handling procedure can continue the processing of this packet, calculate a pseudo-verification and calculate a pseudo-verification, then it is sent by the IPv4 port; Otherwise step s19 micro engine will be according to the packet format of describing among Fig. 5, structure contains the packet of IPv4 source address, destination address, source port, this special data package will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, application layer usually all can step s20 after receiving such packet be called file transfer protocol (FTP) conversion process module and is handled, and the file transfer protocol (FTP) conversion process is finished after the corresponding protocol conversion process and can step s21 to be recomputated a pseudo-verification and and packet sent from the IPv4 network port.
Among Fig. 4, after microcode handling procedure on the step s22 micro engine is received a tcp data bag from the IPv4 network port, at first step s23 looks into the NAT table according to the IPv4 address, get corresponding IPv6 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv6 protocol format in packet header, step s24 microcode handling procedure judges according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s25 microcode handling procedure can continue the processing of this packet, calculate a pseudo-verification, then it is sent by the IPv6 port; Otherwise this packet of step s26 will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, usually the TCP bag of delivering on the StrongArm all is a file transfer protocol (FTP) order bag, handle so application layer usually all can step s27 after receiving such packet be called file transfer protocol (FTP) conversion process module, the file transfer protocol (FTP) conversion process is finished after the corresponding protocol conversion process and can step s28 to be recomputated a pseudo-verification and and packet sent from the IPv6 network port.
Among Fig. 5, the packet format of description has only when packet and adopts Transmission Control Protocol in transport layer, and bag is the packet format that just can use when converting IPv4 to from IPv6.The bag that micro engine is given StrongArm has passed through packet header address format conversion, and in the process of tcp data bag conversion, need to use the IPv4 source address, destination address and source port, therefore the present invention has creatively designed this kind packet format here, and a kind of effective mode of intelligence transmission is provided between micro engine and StrongArm.
Embodiment
Intel IXP1200 network processing unit is at independently integrated six risc processors (MicroEngine) and a StrongARM processor on the chip.Usually need packet, not only will carry out payload content analysis and conversion, also will write down the state of load through the application layer conversion gateway processes.It is infeasible that the complexity of these processing need to have determined the packet of application layer conversion gateway processes all to be placed on to be handled on the micro engine.
By the network flow quantitative analysis is found, domain name service packet, file transfer protocol (FTP) order bag account for that the ratio of data packet flow is not very big on the whole Internet under the normal condition, and pass the flow that transfer gateway requires to carry out ALG data converted bag being optimized aspect the system design of IPv6 network to reduce as far as possible.Has only file transfer protocol (FTP) order bag for the file transfer protocol (FTP) application need through ALG conversion.Usually file transfer protocol (FTP) order bag just set up file transfer protocol (FTP) connect with the situation that finishes to be connected under just generation.Therefore these packets are put into just to handle on the StrongARM and can satisfy common network demand for services fully.So we have done following design to the packet that needs ALG to handle:
In the format conversion that realizes on the micro engine between packet header address transition and different agreement.The initialization of address mapping table and search by micro engine and handle.Usually the design of NAT table is several thousand clauses and subclauses at least, can realize tabling look-up with hardware HASH on micro engine, and the speed of tabling look-up can be secure.Domain name service bag and file transfer protocol (FTP) order bag have been undertaken delivering to upward processing of StrongARM after the preliminary conversion by the conversion micro engine.
The control aspect receives behind the packet payload content of bag translated, and recomputate a pseudo-verification and.Usually only the query type need be translated for the domain name service request package.The domain name service response packet has then comprised one or more IP address in resource record, the ALG conversion program of control aspect need be translated these IP addresses.When the domain name service response packet be from the IPv4 network to the IPv6 network, in the resource record usually record be the node IP address that is arranged in the IPv4 network with domain name record.For a kind of easy method of the bag of this record is exactly just to distribute to the prefix of IPv4 network when directly front, IPv4 address being added system initialization.When the domain name service response packet from the IPv6 network to the IPv4 network, to searching the static NAT mapping table of safeguarding by the control aspect in the resource record IP address translation time.If the clauses and subclauses of this IPv6 address correspondence not in the static NAT mapping table, the way of acquiescence are to sew most before with the IPv6 address preceding 96 to remove.Domain name service processing data packets flow process is referring to Fig. 1.What show among Fig. 1 is the flow process that the UDP message bag from IPv6 to IPv4 is handled.The flow process that UDP message bag from IPv4 to IPv6 is handled is seen Fig. 2.Both differences are that from IPv6 to IPv4 with what search be different NAT tables from IPv4 to IPv6.
When the application layer conversion gateway program is delivered to the file transfer protocol (FTP) order bag of control aspect in processing, also need sometimes the IP address in its load is translated, method is with the processing of domain name services package.These orders that contain the IP address comprise: PASV and EPASV, PORT and EPORT order.Because file transfer protocol (FTP) order bag is the packet that adopts Transmission Control Protocol, will cause loaded length to change after the packet payload content is changed.After packet was changed through NAT-PT, the bag Sequence and Acknowledgment Number at two ends also needed to change, so also should there be suitable mechanism to write down this variation of bag Sequence and Acknowledgment Number in the ALG modular converter of handling TCP.In realization, we need some through the data message before the address transition.According to design, when delivering on the StrongARM, micro engine need piggyback Useful Information to these bags, for the time standby of ALG module processing in the bag back.Concrete data packet format is referring to Fig. 5.File transfer protocol (FTP) order bag handling process is referring to Fig. 3.What Fig. 3 showed is the process that bag is handled from IPv6 to IPv4, and the flow process that bag is handled from IPv4 to IPv6 is seen Fig. 4.Both differences are that from IPv6 to IPv4 with what search be different NAT tables from IPv4 to IPv6, and the TCP from IPv6 to IPv4 bag delivers to StrongArm on through micro engine and will adopt the packet format of describing among Fig. 5, and the TCP from IPv4 to IPv6 wraps and do not need to adopt this special packet format.
We have realized this method on Intel IXP1200 network processor platform.Micro engine is responsible for receiving packet and the packet of receiving is carried out preliminary treatment in the network processing unit.Need carry out packet that application layer conversion handles delivers on the StrongARM by the data channel between micro engine and StrongARM and handles.StrongARM judges that according to port numbers what receive is which kind of application layer data bag determines to call application corresponding layer processing module.In order to realize the ALG conversion process on the StrongARM, when sending on the StrongARM, adopts packet special information transmission technique, for the conversion of application layer is submitted necessary information.We to this method the realization on network processor platform test, the result proves the NAT-PT that realizes with this method exchanging visit of process IP v4 network and IPv6 network in real time.

Claims (9)

1. the domain name service transfer gateway of a processor platform Network Based and file transfer protocol (FTP) transfer gateway method, by the packet that needs the ALG conversion process is carried out distributed treatment, to guarantee the conversion performance of whole NAT-PT system, it is characterized in that concrete steps are as follows:
Step 1: receiving port receives packet;
Step 2: on micro engine, the packet that receives is carried out address and protocol conversion;
Step 3: check protocol port number, discovery is domain name service bag or file transfer protocol (FTP) order bag, adopt piggy mechanism, the construction data bag, behind former packet, piggyback ALG and handle source address, source port, the destination address that wraps before the conversion that needs, and send StrongARM to handle posttectonic packet;
Step 4:StrongARM calls domain name service transfer gateway resume module to the domain name service bag, file transfer protocol (FTP) order bag is called file transfer protocol (FTP) transfer gateway resume module, for domain name service bag and file transfer protocol (FTP) bag, transfer gateway will carry out IPv4-to the IP address that comprises in the packet content〉IPv6 or IPv6-the conversion of IPv4, and recomputate a pseudo-verification and;
Step 5: it is to be sent that the packet after the ALG module processing is delivered to transmit queue etc.
2. the domain name service transfer gateway of processor platform Network Based according to claim 1 and file transfer protocol (FTP) transfer gateway method, it is characterized in that wherein the step 2 pair packet that receives at first carries out the IP address transition, comprise the conversion of packet header protocol format, execution in step 3 then.
3. the domain name service transfer gateway of processor platform Network Based according to claim 1 and file transfer protocol (FTP) transfer gateway method, it is characterized in that, wherein step 3 will judge whether bag is domain name service bag and file transfer protocol (FTP) order bag according to the port numbers of transport layer, if these two kinds of bags are then delivered on the StrongARM nuclear by the data channel between micro engine and StrongARM and are handled.
4. the domain name service transfer gateway of processor platform Network Based according to claim 1 and file transfer protocol (FTP) transfer gateway method, it is characterized in that, wherein step 4 will be domain name service bag or file transfer protocol (FTP) order bag according to the type of the bag of receiving, judge whether to call domain name service transfer gateway processing module, or file transfer protocol (FTP) transfer gateway processing module.
5. the domain name service transfer gateway of processor platform Network Based according to claim 1 and file transfer protocol (FTP) transfer gateway method is characterized in that, comprising:
UDP bag conversion from IPv6 to IPv4;
UDP bag conversion from IPv4 to IPv6;
TCP bag conversion from IPv6 to IPv4;
TCP bag conversion from IPv4 to IPv6.
6. the domain name service transfer gateway of processor platform Network Based according to claim 5 and file transfer protocol (FTP) transfer gateway method is characterized in that, the UDP bag conversion from IPv6 to IPv4 comprises:
After microcode handling procedure on the step s1 micro engine is received a UDP message bag from the IPv6 network port, step s2 looks into the NAT table according to the IPv6 address, get corresponding IPv4 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv4 protocol format in packet header, step s3 microcode handling procedure judges according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s4 microcode handling procedure can continue the processing of this packet, calculate the verification of UDP, then it is sent by the IPv4 port; Otherwise this packet of step s5 will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, usually the UDP bag of delivering on the StrongArm all is the domain name service packet, handle so application layer usually all can step s6 after receiving such packet be called domain service protocol conversion process module, the domain service protocol conversion process is finished after the corresponding protocol conversion process and can step s7 to be recomputated a pseudo-verification and and packet sent from the IPv4 network port.
7. the domain name service transfer gateway of processor platform Network Based according to claim 5 and file transfer protocol (FTP) transfer gateway method is characterized in that, the UDP bag conversion from IPv4 to IPv6; Comprise:
After microcode handling procedure on the step s8 micro engine is received a UDP message bag from the IPv4 network port, step s9 looks into the NAT table according to the IPv4 address, get corresponding IPv6 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv6 protocol format in packet header, step s10 microcode handling procedure judges according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s11 microcode handling procedure can continue the processing of this packet, calculate the verification of UDP, then it is sent by the IPv6 port, otherwise this packet of step s12 will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, usually the UDP bag of delivering on the StrongArm all is the domain name service packet, finishes after the corresponding protocol conversion process and can step s14 to recomputate a pseudo-verification and and packet sent from the IPv6 network port so application layer usually all can invocation step s13 domain service protocol conversion process module after receiving such packet be handled the domain service protocol conversion process.
8. the domain name service transfer gateway of processor platform Network Based according to claim 5 and file transfer protocol (FTP) transfer gateway method is characterized in that, the TCP bag conversion from IPv6 to IPv4; Comprise:
After microcode handling procedure on the step s15 micro engine is received a tcp data bag from the IPv6 network port, step s16 looks into the NAT table according to the IPv6 address, get corresponding IPv4 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv4 protocol format in packet header, step s17 microcode handling procedure judges according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s18 microcode handling procedure can continue the processing of this packet, calculate a pseudo-verification and calculate a pseudo-verification, then it is sent by the IPv4 port; Otherwise step s19 micro engine will be according to the packet format of describing, structure contains the packet of IPv4 source address, destination address, source port, this special data package will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, application layer usually all can step s20 after receiving such packet be called file transfer protocol (FTP) conversion process module and is handled, and the file transfer protocol (FTP) conversion process is finished after the corresponding protocol conversion process and can step s21 to be recomputated a pseudo-verification and and packet sent from the IPv4 network port.
9. the domain name service transfer gateway of processor platform Network Based according to claim 5 and file transfer protocol (FTP) transfer gateway method is characterized in that, the TCP bag conversion from IPv4 to IPv6 comprises:
After microcode handling procedure on the step s22 micro engine is received a tcp data bag from the IPv4 network port, step s23 looks into the NAT table according to the IPv4 address, get corresponding IPv6 address and carry out corresponding address transition, address and protocol conversion are carried out according to the IPv6 protocol format in packet header, step s24 microcode handling procedure judges according to the service port number of transport layer whether this packet belongs to the needs application layer and carry out data converted then, if not, step s25 microcode handling procedure can continue the processing of this packet, calculate a pseudo-verification, then it is sent by the IPv6 port; Otherwise this packet of step s26 will be delivered on the StrongArm by the passage between micro engine and the StrongArm and handle, usually the TCP bag of delivering on the StrongArm all is a file transfer protocol (FTP) order bag, handle so application layer usually all can step s27 after receiving such packet be called file transfer protocol (FTP) conversion process module, the file transfer protocol (FTP) conversion process is finished after the corresponding protocol conversion process and can step s28 to be recomputated a pseudo-verification and packet is sent from the IPv6 network port.
CNB2003101010680A 2003-10-14 2003-10-14 Method for realizing distributed application tier conversion gate-link in network processor Expired - Fee Related CN1275443C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2003101010680A CN1275443C (en) 2003-10-14 2003-10-14 Method for realizing distributed application tier conversion gate-link in network processor

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2003101010680A CN1275443C (en) 2003-10-14 2003-10-14 Method for realizing distributed application tier conversion gate-link in network processor

Publications (2)

Publication Number Publication Date
CN1529481A CN1529481A (en) 2004-09-15
CN1275443C true CN1275443C (en) 2006-09-13

Family

ID=34304165

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2003101010680A Expired - Fee Related CN1275443C (en) 2003-10-14 2003-10-14 Method for realizing distributed application tier conversion gate-link in network processor

Country Status (1)

Country Link
CN (1) CN1275443C (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102925241B (en) * 2012-11-27 2014-05-21 中国环境科学研究院 Method and device for preparing household garbage derived fuel
CN106059817A (en) * 2016-06-18 2016-10-26 青岛中云数据信息科技有限公司 General wireless data management system

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100380897C (en) * 2004-11-16 2008-04-09 北京北方烽火科技有限公司 Telecommunicating method for microengine and strongArm nuclear
CN101087296B (en) * 2006-06-08 2011-06-15 上海亿人通信终端有限公司 Method for utilizing network processor to translate the IPv4/IPv6 network protocol
CN101136910B (en) * 2006-08-30 2010-09-29 中国电信股份有限公司 Network address and protocol translating equipment and application layer gateway equipment
CN101136852B (en) * 2007-06-01 2010-05-19 武汉虹旭信息技术有限责任公司 Deep pack processing method of microengine
CN101325580B (en) * 2007-06-15 2012-01-25 上海亿人通信终端有限公司 Method for implementing FTP application-layer gateway based on NAT-PT
CN101938384A (en) * 2010-08-31 2011-01-05 中山大学 Common gateway testing method in digital home interactive service
US11195213B2 (en) * 2010-09-01 2021-12-07 Apixio, Inc. Method of optimizing patient-related outcomes
US11694239B2 (en) 2010-09-01 2023-07-04 Apixio, Inc. Method of optimizing patient-related outcomes
KR102610823B1 (en) * 2017-11-27 2023-12-07 삼성전자주식회사 Communication system and method for network address translation
CN115242890A (en) * 2022-06-14 2022-10-25 深圳市老狗科技有限公司 Microcode-based general industrial protocol conversion method
CN116614315B (en) * 2023-07-19 2023-10-27 国家计算机网络与信息安全管理中心江西分中心 IPv6 security protection method for realizing application cloud security hosting

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102925241B (en) * 2012-11-27 2014-05-21 中国环境科学研究院 Method and device for preparing household garbage derived fuel
CN106059817A (en) * 2016-06-18 2016-10-26 青岛中云数据信息科技有限公司 General wireless data management system

Also Published As

Publication number Publication date
CN1529481A (en) 2004-09-15

Similar Documents

Publication Publication Date Title
US6704786B1 (en) Network and end-host efficiency for web communication
Spatscheck et al. Optimizing TCP forwarder performance
CN1232080C (en) Method of providing internal service apparatus in network for saving IP address
CN1275443C (en) Method for realizing distributed application tier conversion gate-link in network processor
CN101296238B (en) Method and equipment for remaining persistency of security socket layer conversation
US7653075B2 (en) Processing communication flows in asymmetrically routed networks
US8447802B2 (en) Address manipulation to provide for the use of network tools even when transaction acceleration is in use over a network
US7298745B2 (en) Method and apparatus to manage packet fragmentation with address translation
BRPI0616627A2 (en) equipment, system, and method for client-server communication
CN1708959A (en) Method, router or switch for software and hardware packet flow forwarding
US7290050B1 (en) Transparent load balancer for network connections
CN1507734A (en) Generic external proxy
US8601139B2 (en) Multiple core session initiation protocol (SIP)
CN1493140A (en) Method and apparatus to permit data transmission to transverse firewalls
Natarajan et al. SCTP: An innovative transport layer protocol for the web
US8892745B2 (en) Redirection of a request for information
CN1272724C (en) No.7 layer load equalization method based on socket butt joint in kernel
CN103368872A (en) Data packet forwarding system and method
US20030167338A1 (en) System and method to provide PPPoE connectivity to non-PPPoE clients
WO2003105006A1 (en) Load balancing with direct terminal response
CN1764172A (en) Multimedia communication proxy system and method capable of crossing network address conversion and firewall
US8509235B2 (en) Layer-2 packet return in proxy-router communication protocol environments
CN1816003A (en) Telecommunication method and apparatus of dissimilar chain protocol
CN101621528B (en) Conversation system based on Ethernet switch cluster management and method for realizing conversation passage
CN1476206A (en) Method of breakthrough NAT using dual tunnel mechanism

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
EE01 Entry into force of recordation of patent licensing contract

Assignee: Beijing Zhongke Jingshang Technology Co., Ltd.

Assignor: Institute of Computing Technology, Chinese Academy of Sciences

Contract record no.: 2011110000143

Denomination of invention: Method for realizing distributed application tier conversion gate-link in network processor

Granted publication date: 20060913

License type: Exclusive License

Open date: 20040915

Record date: 20110823

EC01 Cancellation of recordation of patent licensing contract

Assignee: Beijing Zhongke Polytron Technologies Inc

Assignor: Institute of Computing Technology, Chinese Academy of Sciences

Contract record no.: 2011110000143

Date of cancellation: 20181212

EC01 Cancellation of recordation of patent licensing contract
EM01 Change of recordation of patent licensing contract

Change date: 20181212

Contract record no.: 2011110000143

Assignee after: Beijing Zhongke Polytron Technologies Inc

Assignee before: Beijing Zhongke Jingshang Technology Co., Ltd.

EM01 Change of recordation of patent licensing contract
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20060913

Termination date: 20191014