CN106453204B - Method and device for processing data message - Google Patents
Method and device for processing data message Download PDFInfo
- Publication number
- CN106453204B CN106453204B CN201510483930.1A CN201510483930A CN106453204B CN 106453204 B CN106453204 B CN 106453204B CN 201510483930 A CN201510483930 A CN 201510483930A CN 106453204 B CN106453204 B CN 106453204B
- Authority
- CN
- China
- Prior art keywords
- context data
- header
- data
- message
- enhanced
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a method and a device for processing data messages, wherein the method comprises the following steps: obtaining an enhanced context data header type; encapsulating the enhanced context data header type in a network service header, and encapsulating the network service header in a data message; and sending the data message along a service forwarding path. The invention can further increase the type identification of the context data head in the SFC network so as to enhance the further identification of the context data head on the node supporting the service chain.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and an apparatus for processing data packets.
Background
At present, a Service Function Chain (SFC) technology is proposed, that is, all services are integrated, a Service overlay layer is virtualized, a Service topology is formed, and decoupling is performed on the Service overlay layer, which is no longer limited by an underlying network structure, and a framework is shown in fig. 1. It can be seen that the SFC technique includes the following components: a Classifier (Classifier), a Service Function Forwarder (SFF for short), a Service Function (SF for short), and a Network Service Header Proxy (NSH Proxy for short). The Classifier is responsible for classifying the flow, and according to the classification result, the flow is encapsulated with a Network Service Header (NSH), that is, a subsequent Service function path of the message is determined on the Classifier, and further the encapsulation and forwarding of an overlay layer are performed, the message is forwarded to a next-hop SFF by an overlay technology, the SFF receives the message, decapsulates the overlay layer, analyzes the received message carrying the NSH message Header, and forwards the message to a corresponding SF for processing according to the information in the NSH Header; the SF is responsible for carrying out corresponding service function processing on the received message, and after the processing is finished, the head of the NSH message is further updated and the updated message is forwarded to the SFF which forwards the message to the SF; the SFF further searches the corresponding transmission layer package according to the information in the NSH message, performs overlay package on the NSH message, and forwards the message to the next-hop SFF. The NSH Proxy mainly represents SFF, and interacts with SF which does not sense NSH message header. For example, for an overlay technology using IPv4-GRE (Generic Routing Encapsulation), the format of a complete packet sent from the Classifier is shown in fig. 2, i.e., an NSH header, an IPv4-GRE header, and an L2 header are encapsulated on the outer layer of an original packet (original packet).
From the control plane, the classification rules and the service function chain definition of the SFC and the NSH are issued by the SFC controller or configured locally; from the data plane packaging point of view, the whole NSH of the Service function chain and related to the Service is shown in fig. 3, and includes a Base Header (Base Header), a Service Path Header (Service Path Header), a Context Header (Context Header), and variable length optional Context data; wherein, the basic header mainly identifies version number, length, context data type and next protocol number; the Service Path head is most core, and identifies the Service function Path information of the whole Service function chain, wherein the Service Path information comprises a Service Path identifier (Service Path ID) and a Service Index (Service Index), the Service Path identifier is issued globally, and the node confirms which Service function chain the current message should be forwarded to and which Service function to process according to the Service Path identifier and the Service Index; a Mandatory Context Header (directory Context Header) is used to carry Context information that must be carried, and an Optional Variable Length Context Headers (Optional Variable Length Context Headers) is used to carry Context information that can be carried optionally. The context information refers to information shared between the classifier and the service function SF, between SFs, and between the service function SFs and the service function forwarder SFFs, and information to be transferred.
Currently, in the SFC working group of IETF (Internet Engineering Task Force), the definition of the context header includes two types: an MD Type (Metadata Type) 1 (optional support), at this time, an NSH packet header must carry a mandatory context data header of 4 bytes in addition to an optional variable length context data header, and a packet format is shown in fig. 3; the other is MD Type (Metadata Type) ═ 2 (optional support), at this time, the NSH packet header does not need to carry a 4-byte mandatory context data header, and the packet format is shown in fig. 4; whether MD Type is 1 or MD Type is 2, wherein the context data format selectable in variable length is shown in fig. 5.
Further, in the current IETF SFC working group, when MD Type is 1, an extended definition is made for a mandatory context data header that must carry 4 bytes. There are two main extension definitions: one is a mandatory context data header extension definition for a data center scenario, as shown in FIG. 6; one is a mandatory context header extension definition for mobile scenarios, as shown in FIG. 7. However, when a node receives an NSH packet carrying a context header, it is unknown how to parse the context header, and is it necessary to use the context header as context data of a data center scene, as context data of a mobile scene, or as context data in another scene? If the analysis is wrong, the context data information cannot be read correctly, and the service processing fails.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method and an apparatus for processing a data packet, so as to enhance the identification degree of the context packet header type.
In order to solve the above technical problem, the present invention provides a method for processing a data packet, which is applied to a node supporting a service function chain, and comprises:
obtaining an enhanced context data header type;
encapsulating the enhanced context data header type in a network service header, and encapsulating the network service header in a data message;
and sending the data message along a service forwarding path.
Further, the method also has the following characteristics: the enhanced context data header type includes any one of:
a context data header of a data center scene, a context data header of a mobile scene, and a context data header of a broadband network scene.
Further, the method also has the following characteristics:
the enhanced context header type is configured according to a network deployment situation and/or context header data information.
Further, the method also has the following characteristics:
the enhanced context data header type is configured locally or issued by the centralized controller.
Further, the method also has the following characteristics:
the data message is composed of original data and a network service header, or composed of original data, a network service header and a superposed network message header.
In order to solve the above problem, the present invention further provides a device for processing a data packet, which is applied to a node supporting a service function chain, and includes:
an obtaining module, configured to obtain an enhanced context header type; the enhanced context data header type includes any one of: a context data head of a data center scene, a context data head of a mobile scene and a context data head of a broadband network scene;
the encapsulation module is used for encapsulating the enhanced context data header type in a network service header and encapsulating the network service header in a data message, wherein the data message consists of original data and the network service header or consists of the original data, the network service header and a superposed network message header;
and the sending module is used for sending the data message along a service forwarding path.
Further, the device also has the following characteristics: further comprising:
a configuration module for configuring the enhanced context data header type according to a network deployment situation and/or context data header data information.
Further, the device also has the following characteristics:
the obtaining module is further configured to obtain the type of the enhanced context data header that is locally configured or issued by the centralized controller.
In order to solve the above problem, the present invention further provides a method for processing a data packet, which is applied to a node supporting a service function chain, and includes:
receiving a data message carrying a network service header;
analyzing the enhanced context data type in the network service header;
and reading the context data information in the data message according to the enhanced context data type.
Further, the method also has the following characteristics: after reading the context data information in the data message according to the enhanced context data type, the method further comprises:
and if the context data information needs to be updated, updating the context data information and/or the enhanced context data type.
Further, the method also has the following characteristics:
after receiving the data packet carrying the network service header, the method further includes: analyzing the service forwarding path information in the data message;
after reading the context data information in the data message according to the enhanced context data type, the method further comprises:
and forwarding the data message or the updated data message according to the service forwarding path information.
In order to solve the above problem, the present invention further provides a device for processing a data packet, which is applied to a node supporting a service function chain, and includes:
a receiving module, configured to receive a data packet carrying a network service header;
the analysis module is used for analyzing the enhanced context data type in the network service header;
and the processing module is used for reading the context data information in the data message according to the enhanced context data type.
Further, the device also has the following characteristics: further comprising:
and the updating module is used for updating the context data information and/or the enhanced context data type if the context data information needs to be updated.
Further, the device also has the following characteristics:
the analysis module is further configured to analyze service forwarding path information in the data packet;
the processing module is further configured to forward the data packet or the updated data packet according to the service forwarding path information.
In summary, the present invention provides a method and an apparatus for processing a data packet, in which a context data header type identifier is further added in the SFC network, so as to enhance further identification of a context data header on a node supporting a service chain.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
FIG. 1 is a schematic diagram of an SFC technology architecture;
FIG. 2 is a schematic diagram of a complete message structure sent from a Classifier component under SFC technology;
fig. 3 is a schematic diagram of a network service packet header NSH with data plane encapsulated MD-type 1 in SFC technology;
fig. 4 is a schematic diagram of a network service packet header NSH of MD-type 2 encapsulated in a data plane in SFC technology;
FIG. 5 is a diagram of an alternative variable length context data header structure in NSH;
FIG. 6 is a diagram of a mandatory context data header extension definition for a data center scenario;
FIG. 7 is a diagram of a mandatory context data header extension definition for a mobile scenario;
fig. 8 is a flowchart of a method for processing a data packet at a sending node side according to an embodiment of the present invention;
fig. 9 is a flowchart of a method for processing a data packet at a receiving node side according to an embodiment of the present invention;
fig. 10 is a diagram illustrating a message reference format of an enhanced context header type in NSH according to an embodiment of the present invention;
fig. 11 is a schematic diagram of processing a data packet in a data center-based scenario according to a first embodiment of the present invention;
fig. 12 is a schematic diagram of processing a data packet in a mobile scenario according to a second embodiment of the present invention;
FIG. 13 is a diagram of updating enhanced context header types at an intermediate node according to a third embodiment of the present invention;
fig. 14 is a schematic diagram of an apparatus for processing a data packet at a transmitting side according to an embodiment of the present invention;
fig. 15 is a schematic diagram of an apparatus for processing a data packet at a receiving side according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
Fig. 8 is a flowchart of a method for processing a data packet at a sending node side according to an embodiment of the present invention, and as shown in fig. 8, the method is applied to a node supporting a service function chain, and includes:
and step 13, sending the data message along a service forwarding path.
Further, the enhanced context data header type includes any one of: the context data head of the data center scene, the context data head of the mobile scene and the context data head of the broadband network scene.
Further, the enhanced context header type is configured according to a network deployment situation and/or context header data information, and may be configured locally; or the system can be issued by a centralized controller;
furthermore, the data message is composed of original data and a network service header, or composed of original data, a network service header and a superimposed network message header; overlay network headers referring to fig. 2, the part in front of the NSH is the overlay network header.
Fig. 9 is a flowchart of a method for processing a data packet at a receiving node side according to an embodiment of the present invention, where as shown in fig. 9, the method includes:
step 21, receiving a data message carrying a network service header;
and step 23, reading the context information carried in the context data header according to the enhanced context data type.
Further, the receiving node may update the context data information and/or the enhanced context data header type according to the actual deployment situation.
As shown in fig. 10, it is a message reference format based on the NSH extended enhanced context data header type field in the embodiment of the present invention; wherein, E-MD-ty identifies Enhanced MD-type, namely Enhanced context data header type field; the present reference format reserves 4 bits of the 8 bits of MD-type for the present invention.
The first embodiment is as follows:
as shown in fig. 11, the service function chain SFC1 inside the data center is SF2- > SF 5; wherein SF1 and SF2 are connected to SFF1/TOR (Top-of-Rack) 1, SF3 is connected to SFF2/TOR2, SF4 and SF5 are connected to SFF3/TOR 3; that is, the service forwarding path experienced by the service function chain is SFP 1: SFF1- > SF2> SFF3- > SF 5.
When the message arrives at the gateway device of the data center, the gateway device, as a Classifier in the service function chain technology, classifies the message, and finds that the message is forwarded by a corresponding service chain SFC1, that is, the corresponding service forwarding path is SFP1, the forwarding flow of the message is as follows:
step 101: classifying and finding by the Classiier node, acquiring an enhanced context data header type, wherein the flow needs to enter a data center for processing, so that the related information of a service forwarding path and context data header information belonging to a data center scene are acquired to form an NSH header, the NSH header is encapsulated in an original data message, and the NSH header is forwarded to a next hop node TOR1/SFF1 according to the service forwarding path;
step 102: after receiving the message, the TOR1/SFF1 analyzes and reads the service forwarding path information and the enhanced context data type in the message, correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the TOR1/SFF1 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information (for example, interpreting the first 16bits of the mandatory context data header as D/F/Source Node ID/Source Interface ID); after the use, if the context data information needs to be updated, updating; if not, not updating the context data information; the TOR1/SFF1 forwards the message to the corresponding SF2 for processing according to the service forwarding path information;
step 103: after receiving the message, the SF2 correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SF2 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and carrying out corresponding Service processing (for example, reading the fourth 16bits of the mandatory context data header as an A/Service Tag), and updating if the context data related information needs to be updated after the processing is finished; if not, not updating the context data related information; then the message is forwarded to the TOR1/SFF 1;
step 104: after receiving the message, the SFF1 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the TOR1/SFF1 node exists; if yes, correctly reading and using the context data information according to the enhanced context data type field, and updating if the context data information needs to be updated after the context data information is used; if not, not updating the context data information; the TOR1/SFF1 forwards the message to the next hop TOR3/SFF3 for processing according to the service forwarding path information;
step 105: after receiving the message, the TOR3/SFF3 analyzes and reads the service forwarding path information and the enhanced context data type in the message, correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the TOR3/SFF3 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information (for example, interpreting the first 16bits of the mandatory context data header as D/F/Source Node ID/Source Interface ID); after the use, if the context data information needs to be updated, updating; if not, not updating the context data information; the TOR3/SFF3 forwards the message to the corresponding SF5 for processing according to the service forwarding path information;
step 106: after receiving the message, the SF5 correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SF5 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and carrying out corresponding Service processing (for example, reading the fourth 16bits of the mandatory context data header as an A/Service Tag), and updating if the context data related information needs to be updated after the processing is finished; if not, not updating the context data related information; then the message is forwarded to the TOR3/SFF 3;
step 107: after receiving the message, the TOR3/SFF3 analyzes and reads the service forwarding path information and the enhanced context data type in the message, correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the TOR3/SFF3 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information, stripping the NSH header after using the context data information, and forwarding the message according to the destination IP address in the original message.
Example two:
as shown in fig. 12, the service function chain SFC2 in the mobile scenario is SF2- > SF 5; wherein SF1 and SF2 are connected to SFF1, SF3 is connected to SFF2, and SF4 and SF5 are connected to SFF 3; that is, the service forwarding path experienced by the service function chain is SFP 2: SFF1- > SF2> SFF3- > SF 5.
When the packet arrives at a mobile network gateway device (P-GW), the gateway device, as a Classifier in the service function chain technology, classifies the packet, and finds that the packet is forwarded by a corresponding service chain SFC2, that is, the corresponding service forwarding path is SFP2, the packet forwarding process is as follows:
step 201: classifying and finding by the Classiier node, acquiring the type of an enhanced context data header, wherein the flow needs to enter a mobile network data center for processing, acquiring relevant information of a service forwarding path and context data header information belonging to a mobile scene to form an NSH header, encapsulating the NSH header in an original data message, and forwarding the NSH header to a next hop node SFF1 according to the service forwarding path;
step 202: after receiving the message, the SFF1 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SFF1 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information (for example, interpreting the first 16bits of the mandatory context data header as a Flow Cookie); after the use, if the context data information needs to be updated, updating; if not, not updating the context data information; the SFF1 forwards the message to the corresponding SF2 for processing according to the service forwarding path information;
step 203: after receiving the message, the SF2 correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SF2 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and carrying out corresponding service processing (for example, reading the second 16bits of the mandatory context data header to be TenTy/Tenant ID), and updating if the context data related information needs to be updated after the processing is finished; if not, not updating the context data related information; then forwarding the message to SFF 1;
step 204: after receiving the message, the SFF1 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SFF1 node exists; if yes, correctly reading and using the context data information according to the enhanced context data type field, and updating if the context data information needs to be updated after the context data information is used; if not, not updating the context data information; the SFF1 forwards the message to the next-hop SFF3 for processing according to the service forwarding path information;
step 205: after receiving the message, the SFF3 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SFF3 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information (for example, interpreting the first 16bits of the mandatory context data header as a Flow Cookie); after the use, if the context data information needs to be updated, updating; if not, not updating the context data information; the SFF3 forwards the message to the corresponding SF5 for processing according to the service forwarding path information;
step 206: after receiving the message, the SF5 correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SF5 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and carrying out corresponding service processing (for example, reading the second 16bits of the mandatory context data header to be TenTy/Tenant ID), and updating if the context data related information needs to be updated after the processing is finished; if not, not updating the context data related information; then forwarding the message to SFF 3;
step 207: after receiving the message, the SFF3 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SFF3 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information, stripping the NSH header after using the context data information, and forwarding the message according to the destination IP address in the original message.
Example three:
as shown in fig. 13, for data traffic that needs to go through the broadband network and then enter the data center, the service function chain SFC3 is SF2- > SF3- > SF 5; wherein SF1 and SF2 are connected to SFF1 and are broadband network domain, SF3 is connected to SFF2, and SF4 and SF5 are connected to SFF3 and are data center network domain; that is, the service forwarding path experienced by the service function chain is SFP 3: SFF1- > SF2- > SFF2- > SF3- > SFF3- > SF 5. On SFF2, reclassification will occur, and the subsequent new traffic forwarding path is SFP 4: SFF1- > SF2- > SFF2- > SF3- > SFF3- > SF 4;
when the message arrives at a broadband network device (BNG), the gateway device, as a Classifier in the service function chain technology, classifies the message, and finds that the message is forwarded by a corresponding service chain SFC3, that is, the corresponding service forwarding path is SFP3, the forwarding flow of the message is as follows:
step 301: classifying and finding by the Classiier node, acquiring the type of an enhanced context data header, wherein the flow needs to enter a broadband network for processing, acquiring relevant information of a service forwarding path and context data header information belonging to a broadband network scene to form an NSH header, encapsulating the NSH header in an original data message, and forwarding the NSH header to a next hop node SFF1 according to the service forwarding path;
step 302: after receiving the message, the SFF1 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field to judge whether the context data information required by the SFF1 node exists in the broadband network scene; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information; after the use, if the context data information needs to be updated, updating; if not, not updating the context data information; the SFF1 forwards the message to the corresponding SF2 for processing according to the service forwarding path information;
step 303: after receiving the message, the SF2 correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SF2 node exists in the broadband network scene; if yes, correctly reading the context data information according to the enhanced context data type field and processing the corresponding service, and if the context data related information needs to be updated after the processing is finished, updating; if not, not updating the context data related information; then forwarding the message to SFF 1;
step 304: after receiving the message, the SFF1 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SFF1 node exists; if yes, correctly reading and using the context data information according to the enhanced context data type field, and updating if the context data information needs to be updated after the context data information is used; if not, not updating the context data information; the SFF1 forwards the message to the next-hop SFF2 for processing according to the service forwarding path information;
step 305: after receiving the message, the SFF2 reclassifies the message, acquires the service forwarding path information SFP4 again, and creates an NSH header by the enhanced type of the context data header and the context data header information belonging to the data center scenario, encapsulates the NSH header in the original data message, and forwards the NSH header to the next hop node SF3 according to the service forwarding path;
step 306: after receiving the message, the SF3 correctly analyzes the context data information in the message to determine whether the context data information required by the SF2 node exists in the data center scene according to the received enhanced context data type field; if yes, correctly reading the context data information according to the enhanced context data type field and processing the corresponding service, and if the context data related information needs to be updated after the processing is finished, updating; if not, not updating the context data related information; then forwarding the message to SFF 2;
step 307: after receiving the message, the SFF2 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SFF2 node exists; if yes, correctly reading and using the context data information according to the enhanced context data type field, and updating if the context data information needs to be updated after the context data information is used; if not, not updating the context data information; the SFF2 forwards the message to the next-hop SFF3 for processing according to the service forwarding path information;
step 308: after receiving the message, the SFF3 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and judges whether the context data information required by the SFF3 node exists or not in the data center scene according to the enhanced context data type field; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information; after the use, if the context data information needs to be updated, updating; if not, not updating the context data information; the SFF3 forwards the message to the corresponding SF5 for processing according to the service forwarding path information;
step 309: after receiving the message, the SF5 correctly analyzes the context data information in the message to determine whether the context data information required by the SF5 node exists in the data center scene according to the received enhanced context data type field; if yes, correctly reading the context data information according to the enhanced context data type field and processing the corresponding service, and if the context data related information needs to be updated after the processing is finished, updating; if not, not updating the context data related information; then forwarding the message to SFF 3;
step 310: after receiving the data message, the SFF3 analyzes and reads the service forwarding path information and the enhanced context data type in the message, and correctly analyzes the context data information in the message according to the enhanced context data type field, and judges whether the context data information required by the SFF3 node exists; if yes, correctly reading the context data information according to the enhanced context data type field and using the context data information, stripping the NSH header after using the context data information, and forwarding the message according to the destination IP address in the original message.
Example four:
when the enhanced context data header type is not identified on the intermediate node, the field is ignored; furthermore, the intermediate node deciphers the context data header information according to a certain rule.
Fig. 14 is a schematic diagram of an apparatus for processing a data packet at a sending side according to an embodiment of the present invention, and as shown in fig. 14, the apparatus of this embodiment is applied to a node supporting a service function chain, and includes:
an obtaining module, configured to obtain an enhanced context header type; the enhanced context data header type includes any one of: a context data head of a data center scene, a context data head of a mobile scene and a context data head of a broadband network scene;
the encapsulation module is used for encapsulating the enhanced context data header type in a network service header and encapsulating the network service header in a data message;
and the sending module is used for sending the data message along a service forwarding path.
The data message is composed of original data and a network service header, or composed of original data, a network service header and a superimposed network message header.
In a preferred embodiment, the method may further include:
a configuration module for configuring the enhanced context data header type according to a network deployment situation and/or context data header data information.
In a preferred embodiment, the obtaining module is further configured to obtain the type of the enhanced context data header configured locally or sent by the centralized controller.
Fig. 15 is a schematic diagram of a device for processing a data packet at a receiving side according to an embodiment of the present invention, and as shown in fig. 15, the device of this embodiment is applied to a node supporting a service function chain, and may include:
a receiving module, configured to receive a data packet carrying a network service header;
the analysis module is used for analyzing the enhanced context data type in the network service header;
and the processing module is used for reading the context data information in the data message according to the enhanced context data type.
In a preferred embodiment, the apparatus may further include:
and the updating module is used for updating the context data information and/or the enhanced context data type if the context data information needs to be updated.
In a preferred embodiment, the parsing module is further configured to parse service forwarding path information in the data packet;
the processing module is further configured to forward the data packet or the updated data packet according to the service forwarding path information.
It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module/unit in the above embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present invention is not limited to any specific form of combination of hardware and software.
The foregoing is only a preferred embodiment of the present invention, and naturally there are many other embodiments of the present invention, and those skilled in the art can make various corresponding changes and modifications according to the present invention without departing from the spirit and the essence of the present invention, and these corresponding changes and modifications should fall within the scope of the appended claims.
Claims (13)
1. A method for processing data message, which is applied to a node supporting a service function chain, comprises:
obtaining an enhanced context data header type;
encapsulating the enhanced context data header type in a network service header, and encapsulating the network service header in a data message;
sending the data message along a service forwarding path;
the enhanced context data header type includes any one of:
a context data header of a data center scene, a context data header of a mobile scene, and a context data header of a broadband network scene.
2. The method of claim 1, wherein:
the enhanced context header type is configured according to a network deployment situation and/or context header data information.
3. The method of claim 1, wherein:
the enhanced context data header type is configured locally or issued by the centralized controller.
4. The method of claim 1, wherein:
the data message is composed of original data and a network service header, or composed of original data, a network service header and a superposed network message header.
5. An apparatus for processing data packets, applied to a node supporting a service function chain, comprising:
an obtaining module, configured to obtain an enhanced context header type; the enhanced context data header type includes any one of: a context data head of a data center scene, a context data head of a mobile scene and a context data head of a broadband network scene;
the encapsulation module is used for encapsulating the enhanced context data header type in a network service header and encapsulating the network service header in a data message, wherein the data message consists of original data and the network service header or consists of the original data, the network service header and a superposed network message header;
and the sending module is used for sending the data message along a service forwarding path.
6. The apparatus of claim 5, wherein: further comprising:
a configuration module for configuring the enhanced context data header type according to a network deployment situation and/or context data header data information.
7. The apparatus of claim 5 or 6, wherein:
the obtaining module is further configured to obtain the type of the enhanced context data header that is locally configured or issued by the centralized controller.
8. A method for processing data message, which is applied to a node supporting a service function chain, comprises:
receiving a data message carrying a network service header;
analyzing the enhanced context data type in the network service header;
reading the context data information in the data message according to the enhanced context data type;
the enhanced context data header type includes any one of:
a context data header of a data center scene, a context data header of a mobile scene, and a context data header of a broadband network scene.
9. The method of claim 8, wherein: after reading the context data information in the data message according to the enhanced context data type, the method further comprises:
and if the context data information needs to be updated, updating the context data information and/or the enhanced context data type.
10. The method of claim 8 or 9, wherein:
after receiving the data packet carrying the network service header, the method further includes: analyzing the service forwarding path information in the data message;
after reading the context data information in the data message according to the enhanced context data type, the method further comprises:
and forwarding the data message or the updated data message according to the service forwarding path information.
11. An apparatus for processing data packets, applied to a node supporting a service function chain, comprising:
a receiving module, configured to receive a data packet carrying a network service header;
the analysis module is used for analyzing the enhanced context data type in the network service header;
the processing module is used for reading the context data information in the data message according to the enhanced context data type;
the enhanced context data header type includes any one of:
a context data header of a data center scene, a context data header of a mobile scene, and a context data header of a broadband network scene.
12. The apparatus of claim 11, wherein: further comprising:
and the updating module is used for updating the context data information and/or the enhanced context data type if the context data information needs to be updated.
13. The apparatus of claim 11 or 12, wherein:
the analysis module is further configured to analyze service forwarding path information in the data packet;
the processing module is further configured to forward the data packet or the updated data packet according to the service forwarding path information.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510483930.1A CN106453204B (en) | 2015-08-07 | 2015-08-07 | Method and device for processing data message |
| PCT/CN2016/080538 WO2017024818A1 (en) | 2015-08-07 | 2016-04-28 | Method and device for processing data message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510483930.1A CN106453204B (en) | 2015-08-07 | 2015-08-07 | Method and device for processing data message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106453204A CN106453204A (en) | 2017-02-22 |
| CN106453204B true CN106453204B (en) | 2020-11-17 |
Family
ID=57983894
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510483930.1A Active CN106453204B (en) | 2015-08-07 | 2015-08-07 | Method and device for processing data message |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106453204B (en) |
| WO (1) | WO2017024818A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108574638B (en) * | 2017-03-14 | 2020-10-16 | 华为技术有限公司 | Method and equipment for forwarding data message |
| CN111857945A (en) * | 2019-04-30 | 2020-10-30 | 中兴通讯股份有限公司 | Data packet transmission method, data packet management method, data packet transmission device, data packet management device, data packet forwarding device and storage medium |
| CN112491729A (en) * | 2020-09-22 | 2021-03-12 | 中兴通讯股份有限公司 | Data processing method and device, storage medium and electronic device |
| CN115460145A (en) * | 2022-08-15 | 2022-12-09 | 阿里云计算有限公司 | Forwarding rule issuing method, intelligent network card and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104639414A (en) * | 2015-01-30 | 2015-05-20 | 杭州华三通信技术有限公司 | Message transmitting method and message transmitting equipment |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101299766A (en) * | 2008-06-19 | 2008-11-05 | 中兴通讯股份有限公司 | Method for processing locating information format |
| US9917745B2 (en) * | 2013-09-27 | 2018-03-13 | Futurewei Technologies, Inc. | Validation of chained network services |
| US9319324B2 (en) * | 2013-12-06 | 2016-04-19 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system of service placement for service chaining |
| US9825856B2 (en) * | 2014-01-06 | 2017-11-21 | Futurewei Technologies, Inc. | Service function chaining in a packet network |
-
2015
- 2015-08-07 CN CN201510483930.1A patent/CN106453204B/en active Active
-
2016
- 2016-04-28 WO PCT/CN2016/080538 patent/WO2017024818A1/en active Application Filing
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104639414A (en) * | 2015-01-30 | 2015-05-20 | 杭州华三通信技术有限公司 | Message transmitting method and message transmitting equipment |
Non-Patent Citations (1)
| Title |
|---|
| "VLAN service Function Chaining draft-dolson-sfc-vlan-00";David Dolson;《IETF》;20140214;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017024818A1 (en) | 2017-02-16 |
| CN106453204A (en) | 2017-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106330714B (en) | Method and device for realizing service function chain | |
| US9832130B2 (en) | Data packet routing method and device | |
| US8284785B2 (en) | System and method for direct communications between FCoE devices | |
| CN105577413A (en) | OAM (Operation, Administration and Management) message processing method and device | |
| CN106453204B (en) | Method and device for processing data message | |
| CN107786437B (en) | Message forwarding method and device | |
| US20180198643A1 (en) | Packet transmission method and apparatus | |
| KR101477012B1 (en) | Method, apparatus, system and computer-readable recording medium for sdn switching | |
| JP4330520B2 (en) | Communication device | |
| WO2015184771A1 (en) | Method and node device for operation, administration, and maintenance of service function chaining | |
| CN105515816B (en) | Processing method and device for detecting hierarchical information | |
| US10165092B2 (en) | Using a network service header to manage a network-as-a-system | |
| US20070041355A1 (en) | Network physical connection inference for IP tunnels | |
| CN109379241A (en) | A kind of routing information determines method and device | |
| CN112087381B (en) | Method and device for realizing service function processing | |
| CN109039903B (en) | Route determining method, device and machine-readable storage medium | |
| US7978728B2 (en) | Network clustering for improving connection management and re-routing capabilities | |
| CN103986637B (en) | A kind of error message processing method and tunnel device | |
| CN111147379A (en) | Data transmission method, system and related equipment | |
| WO2015154393A1 (en) | Method and apparatus for processing service node ability, service classifier and service controller | |
| CN114301993A (en) | Data transmission method, device, terminal equipment and storage medium | |
| US20210119696A1 (en) | Satellite network acceleration and optimization | |
| US9918217B1 (en) | Fast roaming across a network fabric | |
| US10476784B2 (en) | Underlay overlay correlation for visibility and debugging | |
| CN117749567A (en) | Data message forwarding method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |