CN107786462B - Message forwarding method and device - Google Patents
Message forwarding method and device Download PDFInfo
- Publication number
- CN107786462B CN107786462B CN201711051890.9A CN201711051890A CN107786462B CN 107786462 B CN107786462 B CN 107786462B CN 201711051890 A CN201711051890 A CN 201711051890A CN 107786462 B CN107786462 B CN 107786462B
- Authority
- CN
- China
- Prior art keywords
- nsh
- service chain
- node
- message
- flow classification
- 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
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Abstract
The application provides a message forwarding method and a message forwarding device. In the application, the flow classification node determines the service chain which needs to keep the specified information in the network service header NSH, when receiving the data message, if the data message matches the service chain, a first NSH is packaged for the data message and is sent to a first node of the service chain, the first NSH carries a reserved identification, the reservation identification is used to instruct the tail node of the service chain to reserve the specified information in the first NSH, and thus, when the tail node of the appointed service chain receives the data message and finishes the service processing to the data message, the specified information in the first NSH is retained based on a retained identity in the first NSH encapsulated by the data message, instead of clearing the whole NSH, the service chain attribute information is reserved as required, and the purposes that the operation and maintenance tool dynamically displays the service chain through which the data message passes and the service chain attribute information is transmitted across the data center and the like are met.
Description
Technical Field
The present application relates to network communication technologies, and in particular, to a method and an apparatus for forwarding a packet.
Background
In a multiple data center scenario, a separate controller may be deployed at each data center to independently manage the data center.
After a flow Classification (CF) node of a data center receives a data packet, if it is determined that the data packet matches a Service chain, the data packet is encapsulated with a Network Service Header (NSH) and then sent to a first node of the Service chain, where fig. 1 shows an NSH format. After receiving the data message encapsulated with the NSH, the service chain head node and the service chain intermediate node (the service processing node between the service chain head node and the service chain tail node) process the data message encapsulated with the NSH, and add service attribute information in the NSH according to service requirements, for example, add a Metadata Context field in the NSH, and add the service attribute information to the Metadata Context field. When the data packet encapsulated with the NSH reaches the tail node of the service chain, the tail node of the service chain deletes the NSH encapsulated with the data packet, and then forwards the data packet.
The deletion of the NSH encapsulated by the data packet by the service chain tail node in the data center causes the service chain attribute information carried by the NSH to be deleted, and cannot realize the service chain attribute information reservation as required in a specific application scenario, where the specific application scenario is, for example: the operation and maintenance tool needs to dynamically display a service chain through which the data message passes, and the service chain attribute information is transmitted across the data center.
Disclosure of Invention
The application provides a message forwarding method and a message forwarding device, so as to realize the service chain attribute information reservation as required.
The technical scheme provided by the application comprises the following steps:
a message forwarding method comprises the following steps:
the first flow classification node determines a service chain which needs to reserve the specified information in the network service header NSH;
the first flow classification node receives a data message;
and when the first flow classification node determines that the data message matches the service chain, encapsulating a first NSH for the data message and sending the first NSH to a first node of the service chain, wherein the first NSH carries a reserved identifier, and the reserved identifier is used for indicating a tail node of the service chain to reserve the specified information in the first NSH.
A message forwarding device applied to a flow classification node comprises:
the service chain unit is used for determining a service chain which needs to reserve the specified information in the network service header NSH;
and the forwarding unit is used for receiving a data message, and when the data message is determined to be matched with the service chain, encapsulating a first NSH for the data message and sending the first NSH to a head node of the service chain, wherein the first NSH carries a reserved identifier which is used for indicating a tail node of the service chain to reserve the specified information in the first NSH.
It can be seen from the above technical solutions that, in the present application, the stream classification node determines the service chain that needs to retain the specified information in the network service header NSH, and when receiving the data packet, if the data packet matches the service chain, a first NSH is packaged for the data message and is sent to a first node of the service chain, the first NSH carries a reserved identification, the reservation identification is used to instruct the tail node of the service chain to reserve the specified information in the first NSH, and thus, when the tail node of the appointed service chain receives the data message and finishes the service processing to the data message, the specified information in the first NSH is retained based on a retained identity in the first NSH encapsulated by the data message, instead of clearing the whole NSH, the service chain attribute information is reserved as required, and the purposes that the operation and maintenance tool dynamically displays the service chain through which the data message passes and the service chain attribute information is transmitted across the data center and the like are met.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a schematic diagram of the NSH format;
fig. 2 is a flowchart of a message transmission method provided in the present application;
FIG. 3 is a flowchart of setting a specific flag for a specific service chain according to the present application;
FIG. 4 is a schematic diagram of the NSH format provided herein;
FIG. 5 is a schematic diagram illustrating application networking according to an embodiment of the present application;
FIG. 6 is a schematic diagram of another NSH format provided herein;
FIG. 7 is a schematic diagram of another NSH format provided herein;
fig. 8 is a schematic structural diagram of the device provided in the present application.
Detailed Description
In order to satisfy the requirement of retaining the service chain attribute information as required in a specific application scene so as to realize the dynamic display of the service chain through which the data message passes, the transmission of the service chain attribute information across the data center and the like by the operation and maintenance tool, the application provides the method shown in fig. 2.
Referring to fig. 2, fig. 2 is a flowchart of a message transmission method provided in the present application. As shown in fig. 2, the process may include the following steps:
in step 201, the first flow classification node determines a service chain that needs to retain the specified information in the NSH.
Here, the first flow classification node refers to a flow classification node of any data center, and is for convenience of description only and is not intended to be limiting.
In an example, the first flow classification node may determine, by using the flow shown in fig. 3, a service chain that needs to retain the specified information in the NSH, which is described in the following description of the flow shown in fig. 3 and is not described herein again for the moment.
In another example, the first flow classification node may also designate one or more service chains as service chains that need to retain the designated information in NSH according to the user configuration.
Here, the way that the first flow classification node checks that the data packet matches the service chain is similar to the existing service chain matching way, for example, the service chain having the service chain matching information is found by using the port of the received data packet, the VLAN to which the port belongs, and the five-tuple of the data packet (source IP address, source port, destination IP address, destination port, and transport layer protocol) as the service chain matching information.
As one example, in the present application, the reservation in step 202 above identifies the designated reservation bit carried in the Base Header (Base Header) of the first NSH. Taking the last reserved bit of the Base Header designating the reserved bit as NSH, and the reserved flag as M as an example, the NSH format involved in the present application is improved compared to the NSH format shown in fig. 1, and is specifically shown in fig. 4.
As an embodiment, in the present application, the specifying information in the step 202 is: service chain attribute information. As an embodiment, the service chain attribute information may be information carried in a Metadata Context field of the first NSH.
Thus, the flow shown in fig. 2 is completed.
In the application, the stream classification node determines the service chain which needs to keep the specified information in the NSH, when the stream classification node receives the data message, if the data message matches the service chain, a first NSH is packaged for the data message and transmitted to a first node of the service chain, wherein the first NSH carries a reserved identifier, the reservation identification is used to instruct the tail node of the service chain to reserve the specified information in the first NSH, and thus, when the tail node of the service chain receives the data message and finishes the service processing of the data message, the specified information in the first NSH is reserved based on the reserved identification in the first NSH packaged by the data message, instead of clearing the whole NSH, the service chain attribute information is reserved as required, and the purposes that the operation and maintenance tool dynamically displays the service chain through which the data message passes and the service chain attribute information is transmitted across the data center and the like are met.
As an embodiment, in the present application, in order to facilitate distinguishing the service chain that needs to retain the specified information in the NSH, in the present application, a specified flag may be set for the service chain that needs to retain the specified information in the NSH to indicate that the service chain needs to retain the specified information in the NSH. For example, there are two service chains: the method comprises a service chain 1 and a service chain 2, wherein the service chain 1 is a service chain which needs to reserve specified information in NSH, and a specified mark such as cross-domain flag is set for the service chain 1.
To facilitate the first flow classification node to determine the service chain that needs to retain the information specified in NSH, in this application, as an embodiment, the following configuration may be made at the first flow classification node:
1) and configuring the address of the second flow classification node. Here, the second flow classification node is a flow classification node in a next data center (for short, a second data center) in which the service to be performed passes through the first data center where the first flow classification node is located, according to the service requirement.
2) And configuring a next class-forwarding detection function (next-forwarding detection) for the second data center.
Accordingly, in the present application, the following configuration also needs to be made for the second flow classification node: a cross-domain vas listening (cross-domain) function is configured.
Based on the above configuration, in this application, the service chain for which the first flow classification node determines that the specified information in the NSH needs to be retained in step 201 may include the flow shown in fig. 3.
Referring to fig. 3, fig. 3 is a flowchart for implementing step 201 provided by the present application. As shown in fig. 3, the process may include the following steps:
step 301, a first flow classification node sends a detection message to a second flow classification node, where the detection message carries matching information of a target service chain, and the first flow classification node and the second flow classification node are flow classification nodes of two different data centers.
In application, the first flow classification node associates a plurality of service chains, and based on this, when step 301 is executed, the first flow classification node sends, to an address of a second flow classification node configured locally, a detection packet corresponding to each service chain as a target service chain, where the detection packet corresponding to the service chain carries matching information of the target service chain.
It should be noted that, before step 301 is executed, it is required to ensure that the first flow classification node has started a configured service-chain detection function (next-forwarding test enable) for the second data center, otherwise, step 301 cannot be executed.
When a first flow classification node sends a detection message to an address of a second flow classification node configured locally, if a configured detection monitoring (cross-domain vass listening) function is started, the second flow classification node monitors the detection message sent by the first flow classification node, when the second flow classification node monitors the detection message, whether a service chain matched with service chain matching information carried by the detection message exists in all service chains associated with the second flow classification node or not is checked, if so, an acknowledgement message is returned to the first flow classification node, otherwise, the acknowledgement message is not returned. It should be noted that, when the second flow classification node detects that there is a service chain matching the service chain matching information carried in the detection packet, it means that the second flow classification node and the first flow classification node are associated with the same service chain, and the associated same service chain may be for the same service, such as a firewall service.
When the first flow classification node receives the acknowledgement packet returned by the second flow classification node, step 302 is executed.
Through the steps 301 and 302, the first flow classification node can dynamically determine the service chain which needs to retain the specified information in the NSH.
The flow shown in fig. 3 is completed.
As can be seen from the flow shown in fig. 3, in the present application, if a first flow classification node serving as a downstream flow classification node is associated with a same service chain as an upstream second flow classification node, the first flow classification node determines the service chain as a service chain that needs to retain the specified information in the NSH.
In this application, the encapsulating the first NSH for the data packet in step 202 may include:
step a1, if the data message does not encapsulate the NSH, encapsulating a first NSH for the data message; if the data message is encapsulated with NSH (marked as second NSH), extracting the specified information from the second NSH and removing the encapsulated second NSH of the data message, and encapsulating a first NSH for the data message, wherein the first NSH carries the specified information extracted from the second NSH.
With reference to the flow shown in fig. 3, in which the service chain requiring to retain the specified information in the NSH is determined, on the premise that the received data packet encapsulates the second NSH, the first flow classification node means that the service chain matched by the first flow classification node for the data packet in the first data center corresponds to the same service, such as a firewall service, as the service chain matched by the first flow classification node for the data packet corresponds to the service chain matched by the previous hop flow classification node for the data packet, for example, when the first flow classification node encapsulates the first NSH for the data packet, as described in step a1, the first flow classification node extracts the specified information, such as the service chain attribute information, from the second NSH of the data packet, and then removes the encapsulated second NSH of the data packet, and encapsulates the first NSH carries the specified information extracted from the second NSH. Thus, when each service node on the service chain matched by the first flow classification node for the data packet performs a service operation on the data packet, the specific information extracted from the second NSH, such as the service chain attribute information, carried by the data packet is used as a reference, so that some service operations that should be performed originally are determined to have been performed by the service node in the previous-hop data center due to the specific information extracted from the second NSH, and are omitted from being performed, thereby preventing unnecessary repeated operations from being performed repeatedly.
The method provided by the present application is described below with reference to a specific embodiment:
referring to fig. 5, fig. 5 is a diagram of application networking according to an embodiment of the present application. Fig. 5 shows two data centers: the system comprises a first data center and a second data center. The node 5_10 in the first data center is a stream classification node, and the node 5_20 in the second data center is a stream classification node.
If it is determined, according to the traffic demand, that traffic is to be transmitted from the first data center to the second data center, then for node 5_10, the following configuration is made:
(1): the address of node 5_20 is configured.
(2): and configuring a service chain detection function (next class-forward enable) for the second data center.
For node 5_20, the following configuration is made: a cross-domain vas listening (cross-domain) function is configured.
In fig. 5, the following service chains exist in the first data center:
service chain 1: node 5_11- > node 5_12- > node 5_13- > node 5_14- > node 5_ 15;
the following service chains exist in the second data center:
and (3) service chain 2: node 5_21- > node 5_22- > node 5_23- > node 5_24- > node 5_ 25.
In fig. 5, both the service chain 1 and the service chain 2 have the same service chain matching information for the same service, such as firewall service.
Based on the processes provided in the present application and shown in fig. 2 and 3, then,
the node 5_10 starts a next class-forwarding test (next-class-forward-enable) function configured for the second data center, and sends a detection packet to the node 5_ 20. And detecting the service chain matching information of the service chain 1 carried by the message.
After receiving the detection message, the node 5_20 finds that the service chain matching information of the service chain 1 carried by the detection message is matched with the service chain 2, and returns a confirmation message to the node 5_ 10.
When receiving the acknowledgement packet returned by the node 5_20, the node 5_10 determines that the service chain 1 is a service chain that needs to retain the specified information in the NSH, and may set a specified flag for the service chain 1 to indicate that the service chain 1 is a service chain that needs to retain the specified information in the NSH.
Then, the node 5_10 receives the data packet, if the data packet received at this time is denoted as a packet a.
And the node 5_10 finds the service chain with the service chain matching information being the same as the message characteristic information according to the message characteristic information of the message a, and determines the found service chain as the service chain matched with the message a. The message characteristic information here is, for example, the port on which the message a is received, the VLAN to which the port belongs, and the five-tuple (source IP address, source port, destination IP address, destination port, and transport layer protocol) of the message a.
If the node 5_10 determines that the service chain matched with the message a is the service chain 1, as described above, and the service chain 1 has set the designated flag, the node 5_10 encapsulates the NSH for the message a, where the format of the NSH is as shown in fig. 4. In NSH, the last reserved bit of the BaseHeader is a reserved flag (taking M as an example), and the reserved flag is used to instruct the tail node of the service chain 1 to reserve the specified information in NSH. For convenience of description, the message a encapsulating the NSH is denoted as a message b.
The node 5_10 transmits the message b to the first node of the service chain 1, i.e. the node 5_ 11.
After receiving the message b, the node 5_11 performs service processing on the message b, and after the processing is completed, a Metadata Context (Metadata Context) field is extended and added in the NSH packaged by the message b so as to carry service attribute information of the service node. The processing from the node 5_12 to the node 5_14 is similar to the node 5_11, and is not described again here.
When the tail node of the service chain 1, i.e., the node 5_15, receives the message b, the service processing is performed on the message b, and after the processing is completed, the service chain attribute information carried in the NSH, such as the information in the Metadata Context field, is reserved based on the last reserved bit of the Base Header in the NSH encapsulated by the message b as a reserved identifier, where the format of the NSH at this time is shown in fig. 6. For convenience of description, the message b encapsulated with the format of fig. 6 is referred to as a message c.
The node 5_15 transmits the message c to the second data center.
When the flow classification node, i.e., the node 5_20, in the second data center receives the packet c, the service chain is first matched according to the packet feature information of the packet c, where the packet feature information includes, for example, a port that receives the packet c, a VLAN to which the port belongs, and a five-tuple (a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol) of the packet c.
If the node 5_20 is the service chain 2 for the service chain matched with the message c, the node 5_20 extracts the service chain attribute information from the NSH encapsulated by the message c (at this time, the format of the NSH encapsulated by the message c is shown in fig. 6), and the service chain attribute information is specifically information carried by the Metadata Context field 1 shown in fig. 6. Then, the node 5_20 clears the NSH shown in fig. 6 encapsulated by the message c, and encapsulates the NSH for the message c again, where the extracted attribute information of the service chain 1 is carried in the encapsulated NSH, which is specifically shown in fig. 7. In fig. 7, the extracted attribute information of the service chain 1 is carried in the Metadata Context field 1, and the Metadata Context field 1 shown in fig. 7 is used for carrying the attribute information of the service chain 2.
In one example, after the node 5_20 returns the acknowledgement message to the node 5_10, the second data center may delete the service chain 2 due to the service requirement. Based on this special case, the node 5_20 may not match the service chain for the packet c, and when the node 5_20 does not match the service chain for the packet c, in this application, as an embodiment, the node 5_20 clears the NSH encapsulated by the packet c and forwards the data packet normally.
Thus, the description of the embodiments of the present application is completed.
The method provided by the present application is described above, and the device provided by the present application is described below:
referring to fig. 8, fig. 8 is a diagram illustrating the structure of the apparatus according to the present invention. The apparatus is applied to a stream classification node, as shown in fig. 8, and includes:
a service chain unit 810, configured to determine a service chain that needs to retain the specified information in the network service header NSH;
a forwarding unit 820, configured to receive a data packet, and when it is determined that the data packet matches the service chain, encapsulate a first NSH for the data packet and send the data packet to a head node of the service chain, where the first NSH carries a reservation identifier, and the reservation identifier is used to indicate a tail node of the service chain to reserve specified information in the first NSH.
For an embodiment, the determining, by the service chaining unit 810, a service chain that needs to retain the specified information in the network service header NSH includes:
sending a detection message to flow classification nodes in other data centers, wherein the detection message carries matching information of a target service chain;
when receiving the confirmation message returned by the other flow classification nodes, determining the target service chain as a service chain needing to reserve the specified information in the network service header NSH; and the confirmation message is returned when the other flow classification nodes determine that the service chain matched with the matching information of the target service chain exists locally.
As an embodiment, the encapsulating, by the forwarding unit 820, the first NSH for the data packet includes:
if the data message is not encapsulated with the NSH, encapsulating a first NSH for the data message;
if the data message is encapsulated with the second NSH, extracting the specified information from the second NSH and removing the encapsulated second NSH of the data message, and encapsulating the first NSH for the data message, wherein the specified information extracted from the second NSH is carried in the first NSH.
As an embodiment, the specifying information is: service chain attribute information.
As one embodiment, the reservation identification is carried in a designated reservation bit in a base header of the first NSH.
Thus, the description of the structure of the apparatus shown in fig. 8 is completed.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A message forwarding method is characterized by comprising the following steps:
the first flow classification node determines a service chain which needs to reserve the specified information in the network service header NSH;
the first flow classification node receives a data message;
and when the first flow classification node determines that the data message matches the service chain, encapsulating a first NSH for the data message and sending the first NSH to a first node of the service chain, wherein the first NSH carries a reserved identifier, and the reserved identifier is used for indicating a tail node of the service chain to reserve the specified information in the first NSH.
2. The method according to claim 1, wherein the determining, by the first flow classification node, the traffic chain that needs to retain the specified information in the network service header NSH comprises:
a first flow classification node sends a detection message to a second flow classification node, wherein the detection message carries matching information of a target service chain, and the first flow classification node and the second flow classification node are flow classification nodes of two different data centers;
when the first flow classification node receives a confirmation message returned by the second flow classification node, determining the target service chain as a service chain needing to reserve the specified information in the NSH; and the confirmation message is returned to the first flow classification node when the second flow classification node determines that the service chain matched with the matching information of the target service chain exists locally.
3. The method according to claim 1, wherein the designation information is: service chain attribute information.
4. The method of claim 1, wherein the reservation identification is carried in a designated reservation bit in a Base Header of the first NSH.
5. The method according to any of claims 1 to 4, wherein encapsulating the first NSH for the data message comprises:
if the data message is not encapsulated with the NSH, encapsulating a first NSH for the data message;
if the data message is encapsulated with the second NSH, extracting the specified information from the second NSH and removing the encapsulated second NSH of the data message, and encapsulating the first NSH for the data message, wherein the specified information extracted from the second NSH is carried in the first NSH.
6. A message forwarding apparatus, which is applied to a flow classification node, comprising:
the service chain unit is used for determining a service chain which needs to reserve the specified information in the network service header NSH;
and the forwarding unit is used for receiving a data message, and when the data message is determined to be matched with the service chain, encapsulating a first NSH for the data message and sending the first NSH to a head node of the service chain, wherein the first NSH carries a reserved identifier which is used for indicating a tail node of the service chain to reserve the specified information in the first NSH.
7. The apparatus of claim 6, wherein the traffic chain unit determining the traffic chain requiring the retention of the specific information in the network service header NSH comprises:
sending a detection message to flow classification nodes in other data centers, wherein the detection message carries matching information of a target service chain;
when receiving the confirmation message returned by the other flow classification nodes, determining the target service chain as a service chain needing to reserve the specified information in the network service header NSH; and the confirmation message is returned when the other flow classification nodes determine that the service chain matched with the matching information of the target service chain exists locally.
8. The apparatus of claim 6, wherein the forwarding unit encapsulating the first NSH for the data packet comprises:
if the data message is not encapsulated with the NSH, encapsulating a first NSH for the data message;
if the data message is encapsulated with the second NSH, extracting the specified information from the second NSH and removing the encapsulated second NSH of the data message, and encapsulating the first NSH for the data message, wherein the specified information extracted from the second NSH is carried in the first NSH.
9. The apparatus according to any one of claims 7 to 8, wherein the designation information is: service chain attribute information.
10. The apparatus of any of claims 6 to 8, wherein the reservation identification is carried in a designated reservation bit in a Base Header of the first NSH.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711051890.9A CN107786462B (en) | 2017-10-30 | 2017-10-30 | Message forwarding method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711051890.9A CN107786462B (en) | 2017-10-30 | 2017-10-30 | Message forwarding method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107786462A CN107786462A (en) | 2018-03-09 |
| CN107786462B true CN107786462B (en) | 2020-05-12 |
Family
ID=61432469
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711051890.9A Active CN107786462B (en) | 2017-10-30 | 2017-10-30 | Message forwarding method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107786462B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111200609B (en) * | 2020-01-02 | 2022-08-12 | 苏州盛科通信股份有限公司 | INT Metadata data processing method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105099919A (en) * | 2014-05-15 | 2015-11-25 | 华为技术有限公司 | Message processing method and apparatus |
| CN105207909A (en) * | 2014-06-24 | 2015-12-30 | 华为技术有限公司 | Method for transmitting information and network apparatus |
| CN105681198A (en) * | 2014-11-21 | 2016-06-15 | 华为技术有限公司 | Business chain processing method, device and system |
| US9537752B2 (en) * | 2014-07-14 | 2017-01-03 | Cisco Technology, Inc. | Encoding inter-domain shared service paths |
| CN107204866A (en) * | 2016-03-18 | 2017-09-26 | 上海有云信息技术有限公司 | The implementation method of multi-tenant service chaining transmission is solved based on VXLAN technologies |
-
2017
- 2017-10-30 CN CN201711051890.9A patent/CN107786462B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105099919A (en) * | 2014-05-15 | 2015-11-25 | 华为技术有限公司 | Message processing method and apparatus |
| CN105207909A (en) * | 2014-06-24 | 2015-12-30 | 华为技术有限公司 | Method for transmitting information and network apparatus |
| US9537752B2 (en) * | 2014-07-14 | 2017-01-03 | Cisco Technology, Inc. | Encoding inter-domain shared service paths |
| CN105681198A (en) * | 2014-11-21 | 2016-06-15 | 华为技术有限公司 | Business chain processing method, device and system |
| CN107204866A (en) * | 2016-03-18 | 2017-09-26 | 上海有云信息技术有限公司 | The implementation method of multi-tenant service chaining transmission is solved based on VXLAN technologies |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107786462A (en) | 2018-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106878065B (en) | Configuration method and device of distributed aggregation system | |
| CN103748835B (en) | The dynamic renewal of label switched path | |
| US8169984B2 (en) | Communication system, radio lan base station control device, and radio lan base station device | |
| US8130775B2 (en) | Mechanism for protecting a pseudo-wire | |
| CN109088821B (en) | Message transmission method, service chain system and computer readable storage medium | |
| WO2018054397A1 (en) | Service function chain detection path method and device | |
| CN101848171B (en) | Data transmission method based on GRE tunnel, device and system | |
| CN103312611B (en) | Message processing method, device label processing method and equipment | |
| WO2017054576A1 (en) | Unicast tunnel building method, apparatus and system | |
| CN102404197A (en) | Data path processing information included in the pseudowire layer of packets | |
| WO2016161937A1 (en) | Method, device, and system for identifying traffic flow | |
| EP3113425B1 (en) | Encapsulation method for service routing packet, service forwarding entity and control plane | |
| US8792350B2 (en) | Network relay system, network relay device, and congested state notifying method | |
| CN107872332A (en) | The detection method and relevant apparatus of a kind of message forwarding path | |
| CN114503526A (en) | Method and apparatus for routing and bearer mapping configuration | |
| CN102984175B (en) | A kind of without IP monitoring frontend and a kind of agent apparatus | |
| CN108259297B (en) | Message processing method and device | |
| CN105515816A (en) | Processing method and apparatus for detection level information | |
| CN108075991B (en) | Message forwarding method and device | |
| CN103368844A (en) | Message processing method and label switching router in MPLS network | |
| CN115297493A (en) | SRv6 network slice configuration management method and system | |
| CN107786462B (en) | Message forwarding method and device | |
| US20120224488A1 (en) | Method of connectivity monitoring by subscriber line terminating apparatus | |
| CN108259442B (en) | Slow protocol message processing method and related device | |
| CN106878202B (en) | Message processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |