[go: up one dir, main page]

WO2013059991A1 - Procédé et système de traitement de message de données, dispositif de transfert de message - Google Patents

Procédé et système de traitement de message de données, dispositif de transfert de message Download PDF

Info

Publication number
WO2013059991A1
WO2013059991A1 PCT/CN2011/081287 CN2011081287W WO2013059991A1 WO 2013059991 A1 WO2013059991 A1 WO 2013059991A1 CN 2011081287 W CN2011081287 W CN 2011081287W WO 2013059991 A1 WO2013059991 A1 WO 2013059991A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
ipv6
flow table
packet
content
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.)
Ceased
Application number
PCT/CN2011/081287
Other languages
English (en)
Chinese (zh)
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.)
Tsinghua University
Huawei Technologies Co Ltd
Original Assignee
Tsinghua University
Huawei Technologies Co Ltd
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 Tsinghua University, Huawei Technologies Co Ltd filed Critical Tsinghua University
Priority to CN201180002343.6A priority Critical patent/CN103181129B/zh
Priority to PCT/CN2011/081287 priority patent/WO2013059991A1/fr
Publication of WO2013059991A1 publication Critical patent/WO2013059991A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a data packet processing method and system, and a packet forwarding device. Background technique
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • OpenFlow OpenFlow
  • the OpenFlow Switch converts the packet forwarding process that was originally controlled by the switch/router into an OpenFlow switch and control server (Controller). ) to complete together, thus achieving the separation of data forwarding and routing control.
  • the control server can control the flow table in the OpenFlow switch through pre-defined interface operations to control data forwarding.
  • the switch can obtain the flow table entry that matches the data packet by querying the flow table, and the operation that needs to be performed on the data packet can be determined according to the flow table entry, and the operation can be, for example, forwarding. Go to the destination port, drop, report to the control server, and so on.
  • Embodiments of the present invention provide a data packet processing method and system, and a packet forwarding device.
  • the embodiment of the invention provides a data packet processing method, including: Determining, according to the link layer data type field included in the data packet, whether the data packet is an IPv6 packet;
  • the data packet is an IPv6 packet
  • the content of the field in the IPv6 packet is matched with the content of the field that is required to be matched in the IPv6 flow table that is sent by the control server, and the IPv6 flow table includes the following. Said at least one field:
  • Message entry field metadata field, link layer source address field, link layer destination address field, link layer data type field, virtual local area network identification field, virtual local area network priority field, MPLS label field, MPLS traffic type field, IPv6 source address field, IPv6 destination address field, IPv6 traffic type field, IPv6 next header field, IPv6 flow label field, transport layer source port or ICMP type field, transport layer destination port or ICMP code field;
  • IPv6 text is processed correspondingly according to the matching result.
  • the embodiment of the invention provides a packet forwarding device, which includes:
  • a determining module configured to determine, according to a link layer data type field included in the data packet, whether the data packet is an IPv6 packet;
  • a matching module configured to: if the data packet is an IPv6 packet, match the field content in the IPv6 packet with a field content that needs to be matched in an IPv6 flow table that is sent by the control server in advance, the IPv6
  • the flow table contains at least one of the following fields:
  • Message entry field metadata field, link layer source address field, link layer destination address field, link layer data type field, virtual local area network identification field, virtual local area network priority field, MPLS label field, MPLS traffic type field, IPv6 source address field, IPv6 destination address field, IPv6 traffic type field, IPv6 next header field, IPv6 flow label field, transport layer source port or ICMP type field, transport layer destination port or ICMP code field;
  • the processing module is configured to perform corresponding processing on the IPv6 packet according to the matching result.
  • the embodiment of the present invention further provides a data packet processing system, including a control server and at least one packet forwarding device, wherein the packet forwarding device uses the packet forwarding device.
  • the IPv6 flow table structure supporting the IPv6 packet is pre-defined in the control server of the OpenFlow system architecture, and the IPv6 flow table is delivered to the packet forwarding device of the OpenFlow system architecture.
  • the packet forwarding device may determine, according to the link layer data type field included in the data packet, whether the data packet is an IPv6 packet, and if it is an IPv6 packet, the packet forwarding device Can be in the field contained in the IPv6 message The content matches the content of the field in the stored IPv6 flow table, and the IPv6 packet is processed according to the matching result. Therefore, the embodiment of the present invention can enable the packet forwarding device of the OpenFlow system architecture to support IPv6 packets, and expand the OpenFlow system architecture.
  • Embodiment 1 is a flowchart of Embodiment 1 of a data packet processing method according to the present invention
  • Embodiment 2 is a flowchart of Embodiment 2 of a data packet processing method according to the present invention
  • Embodiment 3 is a flowchart of Embodiment 3 of a data packet processing method according to the present invention.
  • Embodiment 4 is a schematic structural diagram of Embodiment 1 of a packet forwarding device according to the present invention.
  • FIG. 5 is a schematic structural diagram of Embodiment 2 of a packet forwarding device according to the present invention.
  • FIG. 6 is a schematic structural diagram of an embodiment of a data packet processing system according to the present invention. detailed description
  • the flow table in the OpenFlow system architecture only supports IPv4 packets, but does not support IPv6 packets, and cannot identify and match related fields in the header of IPv6 packets. Therefore, the OpenFlow system architecture cannot be completed. Network programming control based on IPv64 transmission.
  • the flow table is extended in the OpenFlow system architecture, and an IPv6 flow table supporting the IPv6 packet is added to support the identification and matching of the IPv6 packet.
  • IPv6 flow table in the embodiment of the present invention is removed.
  • IPv4 related fields in the existing OpenFlow flow table namely IPv4 source address, IPv4 destination address, IPv4 protocol type (IPv4 Protocol Type) and IPv4 monthly service type field (IPv4 ToS), newly added IPv6 source address
  • IPv6 destination address field, the IPv6 traffic type field, the IPv6 next header field, and the IPv6 flow label field are five fields, thereby forming an IPv6 flow table containing 16 fields.
  • the embodiment of the present invention may further add a Hop-by-Hop Header Options field and a routing header of the Routing Header in the IPv6 flow table.
  • the (Routing Type) field, the Segment Left field, the Type Specific Data field, and the Options Options field of the Destination Options Header form an IPv6 stream containing 21 fields. table.
  • the complete IPv6 flow table may include the following 21 fields: an Ingress Port field, a Metadata field, a link layer source address (Ether Src) field, and a link layer destination. Address (Ether Dst) field, link layer data type (Ether Type) field, virtual local area network (VLAN) identifier (Vlan ID) field, virtual local area network priority (Vlan Priority) field, multi-protocol Multi-Protocol Label Switching (hereinafter referred to as MPLS) label (MPLS Label) field, MPLS Traffic Class field, IPv6 source address (IPv6 Src) field, IPv6 destination address (IPv6 Dst) field, IPv6 The IPv6 Traffic Class field, the IPv6 Next Header field, the IPv6 Flow Label field, the transport layer source port, or the Internet Protocol Message Protocol (ICMP).
  • ICMP Internet Protocol Message Protocol
  • TCP/UDP/SCTP Src Port/ICMP Type TCP/UDP/SCTP Src Port/ICMP Type
  • Transport destination port or ICMP code TCP/UDP/SCTP Dst Port/ICMP Code
  • Hop-by-Hop Header option Options
  • Routing header Routing Header
  • the (Routing Type) field the Segment Left field, the Type Specific Data field, and the Options Options field of the Destination Options Header.
  • the field length of the IPv6 source address field may be 256 bits, which may include a 128-bit IPv6 source address mask field and a 128-bit source address field. When the IPv6 source address field matches, the IPv6 source address mask field may be selectively matched. . IPv6 destination address field The field length can be 256 bits, which can contain a 128-bit IPv6 destination address mask field. When the IPv6 destination address field matches, the IPv6 destination address mask field can be selectively matched. Both the IPv6 Traffic Class field and the IPv6 Next Header field can be 8 bits.
  • the length of the IPv6 Flow Label field can be 32 bits. Only the lower 20 bits are used as valid storage bits, and the upper 12 bits are all zero.
  • the TCP/UDP/SCTP Src Port represents the transport layer source port
  • the ICMP Type represents the ICMP type
  • the field is either Indicates the source port of the transport layer, which indicates the ICMP type. If the field indicates the transport layer source port or ICMP type, it is characterized by the specific content of the field. It is similar to the port of the transport layer or the ICMP code TCP/UDP/SCTP Dst Port/ICMP Code field, and will not be described here.
  • control server does not need a packet forwarding device, such as a switch or a router, to receive all the fields in the received IPv6 packet. Matches with the above 16 fields or 21 fields.
  • control server can send the following two forms of IPv6 flow table to the packet forwarding device:
  • the control server delivers a complete IPv6 flow table.
  • the complete IPv6 flow table includes the above 16 fields or 21 fields. In these fields, the content of one or a few fields may be matched by the corresponding field in the IPv6 packet received by the packet forwarding device, and the remaining fields are matched. You can indicate that no matching is required by setting it to "empty" or "any".
  • Form 2 The control server delivers an incomplete IPv6 flow table.
  • control server only needs to send the fields that need to match the IPv6 data, that is, only the entries in the IPv6 flow table are sent, and the other fields that do not need to be matched need not be sent. .
  • the fields in the IPv6 flow table entries to be delivered may be in the form of a type-length-value. Said.
  • the IPv6 flow table delivered by the above two methods is included in the required
  • the matching field is matched to the corresponding operation (Instruction).
  • the packet forwarding device may perform a preset operation, for example, discarding the IPv6 packet, or sending the IPv6 packet to the controller server to request the control server to the IPv6.
  • the text is processed.
  • IPv6 flow table may be used as an independent flow table, and the IPv6 flow table does not include the IPv4 flow table.
  • the control server can only send the IPv6 flow table to the packet forwarding device, and if the packet forwarding device needs to support the IPv6 packet, And the IPv4 dual-stack operation, the control server needs to send the IPv4 flow table to the packet forwarding device, and the IPv6 flow table is sent to the packet forwarding device.
  • the IPv6 flow table stored in the packet forwarding device and The IPv4 flow table needs to be distinguished by the respective flow table type values of the IPv6 flow table and the IPv4 flow table.
  • Embodiment 1 is a flowchart of Embodiment 1 of a data packet processing method according to the present invention. As shown in FIG. 1, the method in this embodiment includes:
  • Step 101 Determine, according to the link layer data type field included in the data packet, whether the data packet is an IPv6 packet.
  • a packet forwarding device in the OpenFlow system architecture can receive data packets, which can be either IPv4 packets or IPv6 packets.
  • the two packets can pass data packets.
  • the link layer data type field contained in the Ether Type representation.
  • the data packet is an IPv4 packet. If the Ether Type is 0x86DD, the data packet is an IPv6 packet.
  • Step 102 If the data packet is an IPv6 packet, match the content of the field in the IPv6 packet with the content of the field that needs to be matched in the IPv6 flow table that is sent by the control server in advance.
  • the IPv6 flow table may include at least one of the following fields:
  • Ingress Port Metadata, Ether Src, Ether Dst, Ether Type, Vlan ID, Vlan Priority, MPLS Label, MPLS Traffic Class, IPv6 Src, IPv6 Dst, IPv6 Traffic Class, IPv6 Next Header, IPv6 Flow Label, TCP/UDP/SCTP Src Port/ICMP Type, TCP/UDP/SCTP Dst Port/ICMP Code, Hop-by-Hop Header Options, Routing Type, Segment Left, Type Specific Data, and Destination Options Header Options.
  • the Controller in the OpenFlow system architecture may send the IPv6 flow table to the switch controlled by the IPv6 flow table in advance.
  • the switch may send the two forms of the IPv6 flow table to the switch. It can be understood by those skilled in the art that the Controller can issue different IPv6 flow tables for different switches controlled by the controller.
  • the switch in the OpenFlow system architecture may extract the content of the field from the IPv6 packet, and then extract the content of the field with the field content that needs to be matched in the pre-stored IPv6 flow table. Make a match.
  • the switch can extract all the contents of the field included in the IPv6 packet, and only match the content of the field to be matched with the entry in the IPv6 flow table, or extract only the required matching.
  • the content of the field matches the entry in the IPv6 flow table.
  • the switch may extract the packet entry field, the link layer source address field, the link layer destination address field, and the link in the data packet before determining whether the received data packet is an IPv6 packet.
  • the content of the layer data type field is similar to the process of IPv4 in the OpenFlow system architecture, and is not described here.
  • the switch can extract the IPv6 source address field, the IPv6 destination address field, the IPv6 traffic type field, the IPv6 next header field, the IPv6 flow label field, and the transport layer source in the IPv6 packet.
  • the port or ICMP type field, the transport layer destination port, or the ICMP code field is the switch's IP packet for extract IPv6 packet.
  • the option field of the hop-by-hop extension header and the route type field of the route extension header may also be extracted in the IPv6 extension header. , the remaining slice field, the type specification data field, and the option field of the destination option header.
  • the switch may first apply the extracted field content to generate a flow table matching structure, and then generate the data.
  • the formed flow table matching structure matches the content of the field that needs to be matched in the IPv6 flow table.
  • Step 103 Perform corresponding processing on the IPv6 packet according to the matching result.
  • the IPv6 4 message can be processed according to the matching result.
  • the switch can perform an IPv6 flow table corresponding to the processing operation of the IPv6 packet.
  • the Instruction can include:
  • the operation of the next-level IPv6 flow table is associated with the IPv6 packet forwarding operation.
  • IPv6 packet for example, add the IPv6 source address, IPv6 destination address, IPv6 Traffic Class, and IPv6 Flow Table settings.
  • the switch can perform the preset operation to process the IPv6 packet, for example, discarding the IPv6 text or sending the IPv6 ⁇ message to the Controller.
  • the IPv6 flow table structure supporting the IPv6 packet is pre-defined in the control server of the OpenFlow system architecture, and the IPv6 flow table is delivered to the packet forwarding device of the OpenFlow system architecture.
  • the packet forwarding device may determine, according to the link layer data type field included in the data packet, whether the data packet is an IPv6 packet, and if it is an IPv6 packet, the packet forwarding device The content of the field included in the IPv6 packet may be matched with the content of the field in the stored IPv6 flow table, and the IPv6 packet is processed according to the matching result. Therefore, this embodiment can enable the packet forwarding device of the OpenFlow system architecture to support IPv6 packets, and expand the OpenFlow system architecture.
  • the IPv4 packet is already supported in the existing OpenFlow system architecture.
  • the OpenFlow system architecture can support IPv6 packets. Therefore, for the Swtich in the OpenFlow system architecture. It is said that if it needs to support IPv6 packets and IPv4 packets, it needs to perform double-stack operation on IPv6 packets and IPv4 packets.
  • the IPv4 flow table and the IPv6 flow table can be delivered to the switch by the controller in advance. . The dual stack operation will be described in detail below using an embodiment.
  • Embodiment 2 is a flowchart of Embodiment 2 of a data packet processing method according to the present invention. As shown in FIG. 2, the method in this embodiment may include:
  • Step 201 Receive a data packet.
  • Step 202 Initialize content of a message entry field, a link layer source address field, a link layer destination address field, and a link layer data type field in the flow table matching structure.
  • the initialization operation may be an Ingress Port field, a link layer source address (Ether Src) field, a link layer destination address (Ether Dst) field, and a link layer in the flow table matching structure.
  • the Ether Type field is initialized to the corresponding value in the data, and the initial value of the remaining fields in the flow table matching structure can be set to zero.
  • Step 203 Whether the next header is Vlan, if yes, execute step 204, otherwise step 206 is performed. Whether it is Vlan. For example, if the content of the Ether Type is 0x8100 or 0x88a8, the next header is Vlan.
  • Step 204 Extract the Vlan ID and Vlan Priority fields, and continue processing using the Ether Type after the last Vlan header.
  • Step 207 When using Ether Type for processing, use the Ether Type after the last Vlan header.
  • Step 205 Skip the remaining Vlan headers and perform step 206.
  • Step 206 Whether the switch supports MPLS. If yes, go to step 207. Otherwise, go to step 210.
  • this step is an optional step. If the switch supports MPLS by default, the next step can be omitted.
  • Step 207 Whether the next header is an MPLS shim header, if yes, go to step 208; otherwise, go to step 210.
  • the switch can determine whether the next 4-head is MPLS by determining the content of the Ether Type. For example, if the content of the Ether Type is 0x8848 or 0x8847, the next one is MPLS.
  • Step 209 Skip the remaining MPLS headers and perform step 214.
  • the default processing mode of the switch is to ignore the first MPLS label and then skip all the remaining MPLS labels and process the MPLS payload packet header.
  • Step 210 Whether the next header is an IPv6 header, if yes, go to step 211, otherwise go to step 212.
  • the switch can determine whether the next header is an IPv6 header by determining the content of the Ether Type. For example, if the content of the Ether Type is 0x86DD, the next header is the IPv6 header.
  • Step 211 Perform IPv6 packet processing, and perform step 214.
  • the IPv6 packet can be processed by using the method described in the foregoing Embodiment 1, and details are not described herein.
  • Step 212 Whether the next header is an IPv4 header, if yes, step 213 is performed, otherwise it ends.
  • the switch determines that the next header is not an IPv6 header, it can further determine whether the header is an IPv4 header. Specifically, the switch can also determine whether the next header is an IPv4 header by determining the content of the Ether Type. For example, if the content of the Ether Type is 0x0800, the header is an IPv4 header.
  • Step 213 Perform: ⁇ 4 "3 ⁇ 4" processing, and perform step 214.
  • the sequence between the foregoing steps 210 to 211 and the steps 212 to 213 may be reversed, that is, whether the IPv4 packet is determined first, and then it is determined whether the packet is an IPv6 packet, or the foregoing step 210 and step 212 may be performed in combination. That is, the switch can determine whether the data packet is an IPv4 packet or an IPv6 packet by using the value of the Ether Type.
  • Step 214 Determine a flow table to be used according to the flow table type value identification, and use the extracted related field to perform a flow table query.
  • the related fields that are extracted may be filled in the corresponding fields of the flow table matching structure, and then the switch may identify the flow table to be used according to the value of the flow table type. If the data packet is an IPv6 packet, The switch can match the flow table matching structure with the IPv6 flow table for flow table query. If the data packet is an IPv4 packet, the switch can match the flow table matching structure with IPv4. The flow table performs flow table query matching.
  • the flow table type value is defined in the IPv6 flow table, and the flow table type value is different from the flow table type value of the IPv4 flow table, so that the IPv6 flow table and the IPv4 flow table can be distinguished by the flow table type value.
  • Flow table is defined in the IPv6 flow table, and the flow table type value is different from the flow table type value of the IPv4 flow table, so that the IPv6 flow table and the IPv4 flow table can be distinguished by the flow table type value.
  • the present embodiment further describes the dual-stack operation of IPv4 4 and IPv6 messages in a detailed manner, and is compatible with the existing OpenFlow system architecture.
  • step 211 The process of performing IPv6 packet processing in step 211 in the embodiment shown in FIG. 2 is described in detail below by using a more specific embodiment.
  • FIG. 3 is a flowchart of Embodiment 3 of a data packet processing method according to the present invention. As shown in FIG. 3, the method in this embodiment may include:
  • Step 301 Extract an IPv6 source address, a destination address, a Traffic Class, a Next header, and a Flow label.
  • Step 302 Whether the next header is an IPv6 extension header, if yes, step 303 is performed, otherwise step 309 is performed.
  • Step 303 Whether the next header is a Hop-by-Hop header, if yes, step 304 is performed; otherwise, step 305 is performed.
  • the Switch can determine whether the next header is a Hop-by-Hop header by determining whether the IP v6 Next Header is equal to zero.
  • Step 304 Extract the Options field of the Hop-by-Hop Header, and perform step 302.
  • Step 305 Whether the next header is a Routing Header extension header, if yes, executing step 306, otherwise performing step 307.
  • the switch can determine whether the next header is a Routing Header extension header by determining whether the IPv6 Next Header is equal to 43.
  • Step 306 Extract the Routing Type, Segment Left, and Type Specific Data fields of the IPv6 routing extension header, and perform step 302.
  • Step 307 Whether the next header is a Destination Options Header extension header, if yes, go to step 308; otherwise, go to step 302.
  • the switch can determine if the next header is a Destination Options Header extension by determining if the IPv6 Next Header is equal to 60.
  • Step 308 extract the options field of the Destination Options Header, and execute the step Step 302.
  • Step 309 Whether the IPv6 Next Header is equal to 6, 17 or 132, if yes, go to step 310, otherwise go to step 311.
  • Step 310 Extract the TCP/UDP/SCTP Src Port/Dst Port, and go to step 313. If the IPv6 Next Header is equal to 6, extract the TCP Src Port/Dst Port if IPv6 Next
  • the UDP Src Port/Dst Port is extracted. If the IPv6 Next Header is equal to 132, the SCTP Src Port/Dst Port is extracted.
  • Step 311 Whether the IP Next Header is equal to 58, if yes, execute step 312, otherwise step 313 is performed.
  • Step 312 Extract the ICMP Type and Code, and perform step 313.
  • Step 313 Perform an flow table query by using the extracted field.
  • the foregoing embodiment of the present invention can enable the packet forwarding device of the OpenFlow system architecture to support the IPv6 packet. Moreover, the technical solution of the embodiment of the present invention can support the dual stack operation and expand the OpenFlow system architecture.
  • the device in this embodiment may include: a determining module 11, a matching module 12, and a processing module 13, where the determining module 11 is configured to Determining, according to the link layer data type field included in the data packet, whether the data packet is an IPv6 packet, and the matching module 12, configured to: if the data packet is an IPv6 packet, the IPv6 packet The content of the field matches the content of the field that needs to be matched in the IPv6 flow table that is sent by the control server.
  • the IPv6 flow table includes at least one of the following fields: a message entry field, a metadata field, and a link layer source.
  • link layer destination address field link layer data type field, virtual local area network identification field, virtual local area network priority field, MPLS label field, MPLS traffic type field, IPv6 source address field, IPv6 destination address field, IPv6 traffic type Field, IPv6 Next Header Field, IPv6 Flow Label Field, Transport Layer Source Port or ICMP Type Field, Transport Layer
  • the processing module 13 is configured to perform corresponding processing on the IPv6 packet according to the matching result.
  • the processing module 13 may be specifically configured to: if the matching is successful, perform the processing operation corresponding to the IPv6 flow table on the IPv6 packet; if the matching is unsuccessful, discard the IPv6 packet. Or sending the IPv6 packet to the control server.
  • the packet forwarding device in this embodiment may be a switch in an OpenFlow system architecture or Router.
  • the packet forwarding device of this embodiment may be used to implement the technical solution of the method embodiment shown in FIG. 1.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • the device in this embodiment may further include: an extraction module 14 for determining a module, based on the device shown in FIG. Determining, before determining whether the data packet is an IPv6 packet, extracting, in the data packet, a content of a message entry field, a link layer source address field, a link layer destination address field, and a link layer data type field; After the determining module determines that the data packet is an IPv6 packet, extracting an IPv6 source address field, an IPv6 destination address field, an IPv6 traffic type field, an IPv6 next header field, and an IPv6 flow label field in the IPv6 packet.
  • a matching module 12 specifically configured to: use the content of the field extracted by the extraction module and the IPv6 flow table Field contents need to match to match.
  • the matching module 12 may include: a generating unit 121 and a matching unit 122, where the generating unit 121 is configured to generate the flow table matching structure by using the field content extracted by the extracting module 14; the matching unit 122 is configured to use the matching table
  • the matching structure matches the content of the field that needs to match in the IPv6 flow table.
  • the device in this embodiment may further include: a flow table identification module 15 configured to use the flow table included in the IPv6 flow table before the matching module performs matching
  • the type value identifies the IPv6 flow table from the IPv6 flow table and the IPv4 flow table.
  • the device of this embodiment may further include: a flow table storage module 16, configured to receive an IPv6 flow table sent by the control server, where each field in the IPv6 flow table includes a type, a length, and a value of the field.
  • a flow table storage module 16 configured to receive an IPv6 flow table sent by the control server, where each field in the IPv6 flow table includes a type, a length, and a value of the field.
  • the device in this embodiment can be used to implement the technical solution of the method embodiment shown in FIG. 2 or FIG. 3, and the implementation principle is similar, and details are not described herein again.
  • FIG. 6 is a schematic structural diagram of an embodiment of a data packet processing system according to the present invention.
  • the system in this embodiment may be an OpenFlow system architecture.
  • the system includes: a control server 1 and at least one packet.
  • the text forwarding device 2, in the present embodiment, two message forwarding devices are shown.
  • the packet forwarding device 2 in this embodiment may adopt the structure shown in FIG. 4 or FIG.
  • the technical solution described in any one of FIG. 1 to FIG. 3 is specifically implemented, and the implementation principle is similar, and details are not described herein again.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé et un système de traitement de message de données ainsi qu'un dispositif de transfert de message. Dans un mode de réalisation de la présente invention, une table de flux IPv6 prenant en charge un message IPv6 est définie à l'avance dans un contrôleur d'une architecture de système OpenFlow, et la table de flux IPv6 est fournie à un dispositif de transfert de message de l'architecture du système OpenFlow. Après avoir reçu le message de données, le dispositif de transfert de message détermine si le message de données est un message IPv6 selon un champ de type de données de couche de liaison compris dans le message de données, et si le message de données est le message IPv6, le dispositif de transfert de message met en correspondance le contenu de champ compris dans le message IPv6 avec un contenu de champ dans la table de flux IPv6 stockée et effectue un traitement du message IPv6 selon le résultat de la mise en correspondance. Par conséquent, le mode de réalisation de la présente invention permet au dispositif de transfert de message de l'architecture du système OpenFlow de prendre en charge un message IPv6, étendant ainsi l'architecture du système OpenFlow.
PCT/CN2011/081287 2011-10-25 2011-10-25 Procédé et système de traitement de message de données, dispositif de transfert de message Ceased WO2013059991A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180002343.6A CN103181129B (zh) 2011-10-25 2011-10-25 数据报文处理方法和系统、报文转发设备
PCT/CN2011/081287 WO2013059991A1 (fr) 2011-10-25 2011-10-25 Procédé et système de traitement de message de données, dispositif de transfert de message

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/081287 WO2013059991A1 (fr) 2011-10-25 2011-10-25 Procédé et système de traitement de message de données, dispositif de transfert de message

Publications (1)

Publication Number Publication Date
WO2013059991A1 true WO2013059991A1 (fr) 2013-05-02

Family

ID=48167046

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/081287 Ceased WO2013059991A1 (fr) 2011-10-25 2011-10-25 Procédé et système de traitement de message de données, dispositif de transfert de message

Country Status (2)

Country Link
CN (1) CN103181129B (fr)
WO (1) WO2013059991A1 (fr)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348716A (zh) * 2013-07-23 2015-02-11 杭州华三通信技术有限公司 一种报文处理方法及设备
CN104426762A (zh) * 2013-08-30 2015-03-18 中兴通讯股份有限公司 一种传输、接收元数据的方法、开放流逻辑交换机
CN104734963A (zh) * 2015-03-24 2015-06-24 电子科技大学 一种基于SDN的IPv4和IPv6网络互连方法
CN106656720A (zh) * 2016-10-31 2017-05-10 上海斐讯数据通信技术有限公司 一种基于SDN的IPv4向IPv6过渡的方法及系统
CN112995062A (zh) * 2021-02-07 2021-06-18 中国银联股份有限公司 一种数据传输方法及装置
CN113347090A (zh) * 2020-02-18 2021-09-03 华为技术有限公司 报文处理方法、转发设备以及报文处理系统
CN113595931A (zh) * 2021-07-08 2021-11-02 杭州海康威视数字技术股份有限公司 一种报文处理方法、装置、设备及存储介质
CN113949519A (zh) * 2020-06-29 2022-01-18 中国电信股份有限公司 用于实现用户身份保真的方法和系统
CN114205415A (zh) * 2020-09-17 2022-03-18 深圳市中兴微电子技术有限公司 报文修改方法、装置、计算机设备、介质
CN114553757A (zh) * 2022-01-29 2022-05-27 阿里巴巴（中国）有限公司 基于可编程交换机的协议报文处理方法、装置和设备
CN115412512A (zh) * 2022-10-31 2022-11-29 浙江九州云信息科技有限公司 一种基于IPv6的多云跨网互通方法及装置
CN117336251A (zh) * 2023-11-30 2024-01-02 上海鉴智其迹科技有限公司 一种车载数据的交互方法、装置、电子设备及存储介质
CN118573601A (zh) * 2024-07-29 2024-08-30 广州通则康威科技股份有限公司 基于icmp的dnat连通性测试方法、装置及设备

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103841189B (zh) * 2014-02-28 2018-09-28 上海斐讯数据通信技术有限公司 控制云计算中心服务器之间数据通信的方法
TWI720113B (zh) 2017-01-20 2021-03-01 香港商阿里巴巴集團服務有限公司 一種電文處理方法和裝置
CN106878308B (zh) * 2017-02-21 2020-06-19 浪潮集团有限公司 一种icmp报文匹配系统及方法
CN108881195A (zh) * 2018-06-07 2018-11-23 蒋云 基于云环境的数据安全共享方法和装置
CN109088769B (zh) * 2018-08-18 2021-05-07 国网山西省电力公司信息通信分公司 一种诊断mpls-vpn数据报文的装置
CN109117182B (zh) * 2018-08-29 2022-03-08 赛尔网络有限公司 基于源码支持IPv6程度的检测方法、设备、系统及介质
CN111343088B (zh) * 2020-02-21 2021-01-29 清华大学 一种报文传输方法及装置、终端、存储介质
CN111950000B (zh) * 2020-07-30 2022-10-21 新华三技术有限公司 一种接入访问控制方法及设备
CN116684358B (zh) * 2023-07-31 2023-12-12 之江实验室 一种可编程网元设备的流表管理系统及方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011030889A1 (fr) * 2009-09-14 2011-03-17 日本電気株式会社 Système de communication, nœud de transmission, serveur de gestion de chemin, procédé de communication et programme
EP2355423A1 (fr) * 2010-01-29 2011-08-10 Deutsche Telekom AG Système et procédé de routage de paquets de données sur un réseau de protocole Internet

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009042919A2 (fr) * 2007-09-26 2009-04-02 Nicira Networks Système d'exploitation de réseau pour la gestion et la sécurisation des réseaux

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011030889A1 (fr) * 2009-09-14 2011-03-17 日本電気株式会社 Système de communication, nœud de transmission, serveur de gestion de chemin, procédé de communication et programme
EP2355423A1 (fr) * 2010-01-29 2011-08-10 Deutsche Telekom AG Système et procédé de routage de paquets de données sur un réseau de protocole Internet

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZHILIANG, WANG ET AL., THINKING ABOUT EXTENSIBILITY AND SCALABILITY IN OPENFLOW NETWORKING (CANS 2011), 9 August 2011 (2011-08-09), pages 8, 12 - 14 *

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348716B (zh) * 2013-07-23 2018-03-23 新华三技术有限公司 一种报文处理方法及设备
CN104348716A (zh) * 2013-07-23 2015-02-11 杭州华三通信技术有限公司 一种报文处理方法及设备
CN104426762A (zh) * 2013-08-30 2015-03-18 中兴通讯股份有限公司 一种传输、接收元数据的方法、开放流逻辑交换机
CN104734963A (zh) * 2015-03-24 2015-06-24 电子科技大学 一种基于SDN的IPv4和IPv6网络互连方法
CN104734963B (zh) * 2015-03-24 2018-07-13 电子科技大学 一种基于SDN的IPv4和IPv6网络互连方法
CN106656720A (zh) * 2016-10-31 2017-05-10 上海斐讯数据通信技术有限公司 一种基于SDN的IPv4向IPv6过渡的方法及系统
CN113347090B (zh) * 2020-02-18 2023-06-20 华为技术有限公司 报文处理方法、转发设备以及报文处理系统
CN113347090A (zh) * 2020-02-18 2021-09-03 华为技术有限公司 报文处理方法、转发设备以及报文处理系统
CN113949519A (zh) * 2020-06-29 2022-01-18 中国电信股份有限公司 用于实现用户身份保真的方法和系统
CN114205415A (zh) * 2020-09-17 2022-03-18 深圳市中兴微电子技术有限公司 报文修改方法、装置、计算机设备、介质
CN112995062A (zh) * 2021-02-07 2021-06-18 中国银联股份有限公司 一种数据传输方法及装置
CN112995062B (zh) * 2021-02-07 2023-07-07 中国银联股份有限公司 一种数据传输方法及装置
CN113595931A (zh) * 2021-07-08 2021-11-02 杭州海康威视数字技术股份有限公司 一种报文处理方法、装置、设备及存储介质
CN113595931B (zh) * 2021-07-08 2024-01-16 杭州海康威视数字技术股份有限公司 一种报文处理方法、装置、设备及存储介质
CN114553757A (zh) * 2022-01-29 2022-05-27 阿里巴巴（中国）有限公司 基于可编程交换机的协议报文处理方法、装置和设备
CN115412512A (zh) * 2022-10-31 2022-11-29 浙江九州云信息科技有限公司 一种基于IPv6的多云跨网互通方法及装置
CN115412512B (zh) * 2022-10-31 2023-03-24 浙江九州云信息科技有限公司 一种基于IPv6的多云跨网互通方法及装置
CN117336251A (zh) * 2023-11-30 2024-01-02 上海鉴智其迹科技有限公司 一种车载数据的交互方法、装置、电子设备及存储介质
CN117336251B (zh) * 2023-11-30 2024-02-23 上海鉴智其迹科技有限公司 一种车载数据的交互方法、装置、电子设备及存储介质
CN118573601A (zh) * 2024-07-29 2024-08-30 广州通则康威科技股份有限公司 基于icmp的dnat连通性测试方法、装置及设备

Also Published As

Publication number Publication date
CN103181129A (zh) 2013-06-26
CN103181129B (zh) 2015-09-30

Similar Documents

Publication Publication Date Title
WO2013059991A1 (fr) Procédé et système de traitement de message de données, dispositif de transfert de message
CN109756425B (zh) 组播转发方法、装置以及bfr
US9954779B2 (en) Method, apparatus, and system for supporting flexible lookup keys in software-defined networks
Kempf et al. Moving the mobile evolved packet core to the cloud
CN103718520B (zh) 处理数据报文的方法、装置及系统
CN114422432B (zh) 基于可靠传输层的可靠覆盖
CN103430149B (zh) 虚拟机迁移通知方法和系统
US20160043943A1 (en) Application wire
CN104125191B (zh) 基于以太网的点对点协议的处理方法、设备和系统
WO2014008820A1 (fr) Procédé, dispositif et système de traitement de service
WO2013113171A1 (fr) Système, dispositif et procédé d'identification de flux
CN107046506B (zh) 一种报文处理方法、流分类器和业务功能实例
WO2011103781A2 (fr) Procédé, dispositif pour la mise en oeuvre de la séparation d'identificateur et de localisateur et procédé d'encapsulation de données
WO2010006528A1 (fr) Procédé, dispositif et système d'établissement de pseudo-circuit
WO2015143802A1 (fr) Procédé et dispositif de gestion de chaîne de fonctions de service
WO2016000513A1 (fr) Procédé et dispositif pour mettre à jour une manière de traitement d'un paquet de flux de services
WO2013086897A1 (fr) Procédé de génération d'entrées, procédé de réception de messages, et dispositif et système correspondants
US20170155582A1 (en) Method and Apparatus for Processing Modified Packet
WO2011160517A1 (fr) Procédé et système de commutation de tunnel pour services de commutation multiprotocole par étiquette
WO2017198131A1 (fr) Procédé et système de redirection de flux de données, et dispositif de réseau et dispositif de commande
CN104158752A (zh) 业务流量的处理方法和装置
WO2014198217A1 (fr) Procédé et système de traitement de tunnel, équipement de plan de commande et équipement de plan d'expédition
WO2014149888A1 (fr) Étiquettes universelles en interconnexion de réseaux
WO2011103759A1 (fr) Procédé pour l'établissement d'un chemin à commutation d'étiquettes bidirectionnel associé, et système pour sa mise en œuvre
CN104734949A (zh) 一种实现流表配置的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11874552

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11874552

Country of ref document: EP

Kind code of ref document: A1