WO2017050085A1 - 一种报文处理的方法、设备和系统 - Google Patents

一种报文处理的方法、设备和系统 Download PDF

Info

Publication number
WO2017050085A1
WO2017050085A1 PCT/CN2016/096572 CN2016096572W WO2017050085A1 WO 2017050085 A1 WO2017050085 A1 WO 2017050085A1 CN 2016096572 W CN2016096572 W CN 2016096572W WO 2017050085 A1 WO2017050085 A1 WO 2017050085A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
packet
label
fec
controller
Prior art date
Application number
PCT/CN2016/096572
Other languages
English (en)
French (fr)
Inventor
庄顺万
李振斌
陈双龙
陈国义
车佳
吴楠
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16847967.3A priority Critical patent/EP3343846B1/en
Priority to ES16847967T priority patent/ES2793312T3/es
Publication of WO2017050085A1 publication Critical patent/WO2017050085A1/zh
Priority to US15/926,872 priority patent/US10680942B2/en
Priority to US16/879,100 priority patent/US11218408B2/en
Priority to US17/536,507 priority patent/US11909633B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a packet processing method, device, and system.
  • the packet needs to be forwarded from the source node to the destination node along the forwarding path, thereby completing the forwarding of the data packet and realizing the data transmission.
  • the source node is also called an ingress node
  • the destination node is also called an egress node.
  • MPLS Multi-Protocol Label Switch
  • IP Internet Protocol
  • MPLS MPLS mechanism
  • segmentation routing Segment Routing
  • LSP Label Switch Path
  • FEC Forwarding Equivalence Class
  • Some forwarding nodes perform static configuration. These forwarding nodes can process packets corresponding to FEC according to the statically configured service processing mode.
  • the service processing mode of each FEC needs to be configured to different forwarding nodes. This will cause a large number of forwarding nodes in the network to be statically configured, resulting in configuration and maintenance of the network environment.
  • the work of business processing is too complicated. As a result, various business processes in the network environment are difficult to implement flexibly.
  • the technical problem to be solved by the embodiments of the present invention is to provide a method and a device for processing a packet to solve the technical problem that the network configuration and maintenance are complicated due to the static configuration of the forwarding node to implement the service processing.
  • an embodiment of the present invention provides a system for processing a message, where the system includes:
  • a controller configured to allocate a service label to a service processing manner of the forwarding equivalent FEC, establish a mapping relationship between the service label and the service processing manner, and send the service label to a source node corresponding to the FEC, And sending the mapping relationship to the destination node corresponding to the FEC;
  • the source node is configured to receive the service label corresponding to the FEC sent by the controller, receive a first packet corresponding to the FEC, and insert the service label in the first packet. Obtaining a second packet, and sending the second packet to a destination node corresponding to the FEC;
  • the destination node is configured to receive the mapping relationship sent by the controller, receive a second packet sent by the source node corresponding to the FEC, and pop the second packet according to the mapping relationship. Deriving the service tag to obtain the first message;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the controller sends the service label to the source node, including:
  • the controller binds the service label to routing information corresponding to the FEC
  • the controller sends the routing information bound to the service tag to the source node.
  • the controller sends the mapping relationship to the destination node, including:
  • the controller inserts the service label and the service processing mode into network layer reachability information corresponding to the FEC, to form the service label and the service processing manner in the network layer reachability information. Mapping relationship between
  • the service processing mode is load balancing processing on the packet, where the network device is an intermediate node on a forwarding path from the source node to the destination node, and the service label is the second The inner label in the label stack of the message.
  • an embodiment of the present invention provides a packet processing method, where the method includes:
  • the controller allocates a service label for forwarding a service processing manner of the equivalent class FEC, and establishes a mapping relationship between the service label and the service processing manner;
  • the controller sends the service label corresponding to the FEC to a source node corresponding to the FEC, to indicate that the source node inserts the service label in a first packet corresponding to the FEC, and obtains a second report.
  • the controller sends the mapping relationship to the destination node corresponding to the FEC, to instruct the destination node to pop the service label from the second packet according to the mapping relationship, to obtain the first packet. ;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the controller sends the service label corresponding to the FEC to a source node corresponding to the FEC, to indicate that the source node inserts the service label in a first packet corresponding to the FEC, Get the second message, including:
  • the controller binds the service label to routing information corresponding to the FEC
  • the controller sends the routing information that is bound to the service label to the source node, to indicate that the source node inserts the service label in the first packet, to obtain the second packet. .
  • the controller sends the mapping relationship to the destination node that is corresponding to the FEC, to indicate that the destination node pops the service label from the second packet according to the mapping relationship, to obtain the first
  • the message includes:
  • the controller inserts the service label and the service processing mode into network layer reachability information corresponding to the FEC, to form the service label and the service processing manner in the network layer reachability information. Mapping relationship between
  • an embodiment of the present invention provides another method for processing a message, where the method includes:
  • the source node receives the service label corresponding to the forwarding equivalence class FEC sent by the controller, where the service label is allocated by the controller for the service processing mode of the FEC, and the source node is corresponding to the Source node of the FEC;
  • the source node receives the first packet corresponding to the FEC, inserts the service label in the first packet, and obtains a second packet;
  • the source node sends the second packet to the destination node corresponding to the FEC, to indicate that the destination node corresponding to the FEC is from the second according to the mapping relationship between the service label and the service processing mode.
  • the service tag is popped up in the packet, and the first packet is obtained; the mapping relationship is established by the controller and sent to the destination node;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the source node receives the service label of the corresponding FEC sent by the controller, including:
  • the source node receives routing information of a corresponding FEC sent by the controller
  • the source node acquires the service label bound to the routing information.
  • the embodiment of the present invention provides another method for processing a packet, where the method includes:
  • the destination node receives a mapping relationship between the service label sent by the controller and the service processing mode, where the service label is allocated by the controller for forwarding the service class of the equivalence class FEC, and the destination node is a corresponding node. Describe the destination node of the FEC;
  • the destination node of the destination node pops the service label from the second packet according to the mapping relationship, to obtain the first packet;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the destination node receives a mapping relationship between the service label and the service processing manner, including:
  • the destination node obtains the service label and the service processing manner from the network layer reachability information, to obtain a mapping relationship between the service label and the service processing manner.
  • an embodiment of the present invention provides a controller, where the controller includes:
  • An allocation module configured to allocate a service label for a service processing manner of forwarding an equivalent class FEC
  • a first sending module configured to send, by the source node corresponding to the FEC, the service label corresponding to the FEC, to indicate that the source node inserts the service label in a first packet corresponding to the FEC, to obtain a Second message;
  • a second sending module configured to send the mapping relationship to the destination node corresponding to the FEC, to indicate that the destination node pops the service label from the second packet according to the mapping relationship, to obtain a first report.
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the first sending module includes:
  • a binding submodule configured to bind the service label to routing information corresponding to the FEC
  • a first sending submodule configured to send, to the source node, the routing information that is bound to the service label, to indicate that the source node inserts the service label in the first packet, to obtain the Second message.
  • the second sending module includes:
  • Inserting a sub-module configured to insert the service label and the service processing manner into network layer reachability information corresponding to the FEC, to form the service label and the service processing in the network layer reachability information
  • a second sending submodule configured to send the network layer reachability information to the destination node, to indicate that the destination node pops the service label from the second packet according to the mapping relationship, to obtain a first Message.
  • an embodiment of the present invention provides a source node device, where the device includes:
  • a first receiving module configured to receive, by the controller, a service label corresponding to the forwarding equivalent type FEC, where the service label is allocated by the controller for service processing of the FEC, and the source node is corresponding to the FEC Source node
  • a second receiving module configured to receive a first packet corresponding to the FEC
  • An insertion module configured to insert the service tag in the first packet to obtain a second packet
  • a first sending module configured to send the second packet to a destination node corresponding to the FEC, to And indicating that the destination node corresponding to the FEC pops the service label from the second packet according to the mapping relationship between the service label and the service processing manner, to obtain a first packet;
  • the mapping relationship is The controller is established and sent to the destination node;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • an embodiment of the present invention provides a destination node device, where the device includes:
  • a first receiving module configured to receive a mapping relationship between a service tag sent by the controller and a service processing mode, where the service tag is allocated by the controller to forward the service class of the equivalent class FEC,
  • the destination node is a destination node corresponding to the FEC;
  • a second receiving module configured to receive a second packet sent by the source node corresponding to the FEC, where the second packet is that the source node inserts the service label in a first packet corresponding to the FEC owned;
  • a pop-up module configured to pop the service label from the second packet according to the mapping relationship, to obtain a first packet
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the embodiment of the invention has at least the following advantages:
  • the service label is allocated by the controller, the service label is sent to the source node, and the mapping relationship between the service label and the service processing mode is sent to the destination node, and the source node can be implemented without static configuration.
  • a service tag is inserted into the packet, and the destination node can be configured to pop the service label from the packet. Therefore, in the process of forwarding the packet from the source node to the destination node, the network device can perform the service label pair according to the packet.
  • the service is processed by the packet. It can be seen that the packet processing can be implemented in the process of packet forwarding without static configuration of the forwarding node. This greatly reduces the number of devices that need to be statically configured, and simplifies the configuration for the network environment.
  • Maintaining the processing of business processes enables various business processes in the network environment to be flexibly implemented.
  • the service tag is allocated by the controller, the service tag is sent to the source node, and the mapping relationship is sent to the destination node, so that the packet carries the service tag used to carry multiple different service processing requirements in the forwarding process.
  • Make each business label flexible A variety of combinations are inserted into the packet to flexibly process the packet according to a combination of various service processing modes, so that the MPLS label can be more flexibly applied to an application scenario with multiple service requirements.
  • FIG. 1 is a schematic diagram of a system framework involved in an application scenario according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a system for processing a message according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a format of network layer reachability information according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a format of a network layer reachability information field according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a packet label according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart diagram of a method for processing a packet according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart diagram of another method for processing a packet according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart diagram of still another method for processing a packet according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart diagram of still another method for processing a packet according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart diagram of a controller for processing a message according to an embodiment of the present invention.
  • FIG. 11 is a schematic flowchart of a source node device for processing a packet according to an embodiment of the present disclosure
  • FIG. 12 is a schematic flowchart of a destination node device for processing a packet according to an embodiment of the present disclosure
  • FIG. 13 is a schematic structural diagram of a controller according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a source node device according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a destination node device according to an embodiment of the present invention.
  • the inventor has found that in order to enable the network environment to process the packet, it is considered that the network environment usually has many FECs, and the packets corresponding to different FECs need to be processed according to different service processing manners. Therefore, the network device The device needs to perform the service processing on the packet. For this reason, the indication information for identifying the service processing mode can be added to the packet in the process of forwarding the packet, so that the network device can determine the pair by reading the indication information. The message is processed in accordance with the corresponding business. In order to enable the packet to have the indication information in the forwarding process, the packet needs to be added to the source node on the forwarding path, and the indication information is popped up at the destination node on the forwarding path.
  • the source node and the destination node corresponding to the FEC need to be statically configured, so that the source node can add indication information to the message corresponding to the FEC, and enable the destination node to respond to the FEC.
  • the message pops up with instructions.
  • a large number of forwarding nodes may exist between the source node and the destination node corresponding to the FEC. Therefore, in the prior art, in order to implement service processing in the network environment, a large number of forwarding nodes need to be statically configured, which results in The network configuration and maintenance work is too complicated, which makes it difficult to implement business processing flexibly.
  • FIG. 1 is a schematic diagram of an application network scenario according to an embodiment of the present invention, where the network scenario includes a controller 101, a forwarding node 102, and a forwarding node 103.
  • the controller 101 can be a controller to separate the control and forwarding network architecture
  • the forwarding node 102 and the forwarding node 103 can be a forwarding node in the control forwarding separate network architecture.
  • the forwarding node 102 is the source node
  • the forwarding node 103 is the destination node.
  • FIG. 1 is a schematic diagram of an application network scenario according to an embodiment of the present invention, where the network scenario includes a controller 101, a forwarding node 102, and a forwarding node 103.
  • the controller 101 can be a controller to separate the control and forwarding network architecture
  • the forwarding node 102 and the forwarding node 103 can be a forwarding node in the control forwarding separate network architecture.
  • the forwarding node 102 is the source node
  • the controller 101 may allocate a service tag to the service processing mode of the FEC, establish a mapping relationship between the service tag and the service processing mode, and the controller 101 may forward the node 102 to the forwarding node 102.
  • the corresponding service tag is sent, and the mapping relationship is sent to the forwarding node 103.
  • the forwarding node 102 can insert the service tag received by the controller 101 into the first packet. And obtaining the second packet, and sending the second packet to the forwarding node 103; when receiving the second packet, the forwarding node 103 may obtain the second packet according to the mapping relationship received from the controller 101.
  • the service packet is popped up to obtain the first packet; in the forwarding process of the second packet from the forwarding node 102 to the forwarding node 103, a network configuration for performing service processing on the second packet is required.
  • the second packet can be processed according to the service processing mode selected by the service label in the second packet.
  • the forwarding path of the FEC-compliant packet from the forwarding node 102 to the forwarding node 103 may not pass through any intermediate node, and may also pass through one or more intermediate nodes, which is not limited in this embodiment of the present invention. .
  • FIG. 2 is a schematic diagram of a message processing system according to an embodiment of the present invention.
  • the system includes:
  • the controller 201 is configured to allocate a service label to the service processing mode of the corresponding FEC, establish a mapping relationship between the service label and the service processing mode, and send a corresponding to the FEC to the source node 202 corresponding to the FEC. Describe the service label, and send the mapping relationship to the destination node 203 corresponding to the FEC;
  • the source node 202 is configured to receive the service label corresponding to the FEC sent by the controller 201, receive a first packet corresponding to the FEC, and insert the service label in the first packet. Obtaining a second packet, and sending the second packet to the destination node 203 corresponding to the FEC;
  • the destination node 203 is configured to receive the mapping relationship sent by the controller 201, receive a second packet sent by the source node 202 corresponding to the FEC, and use the second report according to the mapping relationship.
  • the service label is popped up to obtain the first packet;
  • the service tag is configured to indicate, in the process of forwarding the second packet from the source node 202 to the destination node 203, the network device that needs to perform service processing on the second packet according to the The service processing manner processes the second packet.
  • the controller 201 can be configured to configure a corresponding service processing manner for the FEC. Specifically, the controller 201 may allocate the FEC for identifying the service according to a service processing manner that needs to be performed in response to the FEC packet. The service tag of the processing mode, and establishes a mapping relationship between the service tag and the service processing mode. Then, the controller 201 can send the service label to the source node 202 corresponding to the FEC, so that the source node 202 can save the service label and the FEC, and the controller 201 can send the mapping relationship to the corresponding node. The destination node 203 of the FEC, so that the destination node 203 holds the mapping relationship.
  • the source node 202 when receiving the first packet corresponding to the FEC, the source node 202 may insert the service label into the first packet to obtain the second report. And sending the second message to the destination node 203.
  • the destination node 203 may identify the service label inserted in the second packet according to the mapping relationship, and pop the service label from the second packet to obtain the service packet.
  • the first packet thereby completing the forwarding process of the first packet in the network environment.
  • the network device that needs to perform service processing on the second packet in the forwarding process of the second packet from the source node 202 to the destination node 203 may read the service label in the second packet. Determining that the second packet corresponds to the service processing manner, so that the second packet can be processed according to the service processing manner.
  • the controller 201 may not limit the execution order between the two sending actions for the service label issuing action and the mapping action.
  • the controller 201 can send a service label to the source node 202 and a mapping relationship to the destination node 203.
  • the controller 201 may also send a mapping relationship to the destination node 203 and then send a service label to the source node 202.
  • the FEC in this embodiment may be an FEC formed by classifying packets in any manner.
  • the FEC may classify the packets by using the IP address prefix of the destination address, that is, the packets corresponding to the same FEC have the same IP address prefix destination address.
  • the controller 201 may bind the service label to the source node 202 by binding the IP label to the source node 202, and the source node 202 may And storing the IP address prefix, so that the source node 202 can identify the destination address of the packet when receiving the packet, and if the destination address of the packet has the IP address prefix, the source node 202 can be in the packet. Insert the service tag saved corresponding to the IP address prefix.
  • the controller 201 may send a routing letter corresponding to the FEC to the source node 202.
  • the interest is realized.
  • the controller 201 binds the service label to routing information corresponding to the FEC; the controller 201 sends the routing information to the source node 202.
  • the binding of the service label corresponding to the FEC to the routing information of the FEC may be implemented by extending the Border Gateway Protocol (BGP).
  • the routing information corresponding to the FEC may be carried in the Network Layer Reachability Information (NLRI) of the BGP, and the service label corresponding to the FEC may be bound as a BGP attribute to the NLRI carrying the routing information.
  • the controller 201 can send the routing information and the service label corresponding to the FEC to the source node 202 by sending the network layer reachability information to the source node 202.
  • NLRI Network Layer Reachability Information
  • the controller 201 in order to implement the mapping between the service tag and the service processing mode, can be carried in the NLRI of the BGP, and the controller 201 is sent to the destination node 203.
  • the NLRI is sent to implement the mapping relationship.
  • the controller 201 inserts the service label and the service processing manner into an NLRI corresponding to the FEC, to form a mapping relationship between the service label and the service processing manner in the NLRI.
  • the controller 201 transmits the NLRI to the destination node 203.
  • the Multi-Protocol Reachable NLRI (MP_Reach_NLRI) is obtained by extending the BGP, and the MP_Reach_NLRI can be used to carry the mapping relationship. among them,
  • the address family Identifier is an address family identifier field, which is used to carry an address family identifier of a network protocol, such as an IPv4 (Internet Protocol Version 4) identifier or an IPv6 (Internet Protocol Version 4) identifier;
  • the Subsequent Address Family is a sub-address family identifier field, which is used to carry the NLRI type flag information.
  • a flag information may be added, where the flag information is used to indicate that the NLRI includes Have the mapping relationship;
  • the Network Address of Next Hop is a next hop network address field, which is used to carry the address of the next forwarding node of the route;
  • the Network Layer Reachability Information is a network layer reachability information field.
  • the field can be used to carry the mapping relationship.
  • the NLRI field may implement the bearer of the mapping relationship by using the format shown in FIG. 4, where
  • the NLRI Type is an NLRI type field, which is used to carry the type of the service label.
  • the type of the service label can be used to indicate the service processing mode corresponding to the service label.
  • the service label type is Entropy label, that is, the service label belongs to the entropy.
  • the service processing mode corresponding to the label and the entropy label may be a load sharing service.
  • NLRI Length is an NLRI length field, which is used to carry information indicating the length of the NLRI field;
  • the SID/Label/Index is a service identifier field, and the field can be used to carry a Service Identifier (SID), a Service Label (Label), or an Index (Index).
  • SID Service Identifier
  • Label Service Label
  • Index Index
  • the Type Specific Value is a type-specific value field, which is used to carry the description information of the service processing mode.
  • the service tag can be inserted into the SID/Label/Index field, and the service processing mode can be inserted into the Type Specific Value field, so that the MP_Reach_NLRI can carry the service tag and the service processing manner.
  • the relationship between the mappings and the controller 201 sends the MP_Reach_NLRI to the destination node 203.
  • the destination node 203 reads the service tag and the service processing mode in the MP_Reach_NLRI, and determines that the service tag is used to identify the relationship. Business processing methods.
  • the service processing manner may include: performing load sharing processing on the packet, source identification processing of the service flow, or packet dyeing processing.
  • the source identification processing of the service flow is mainly used in the operation, management, and maintenance (OAM) process of a service such as a Layer 3 Virtual Protocol Network (L3VPN). Identification.
  • the dyeing process is mainly used for dyeing the business flow by the OAM process.
  • the service tag assigned to the load sharing process belongs to an Entropy Label
  • the service tag assigned to the source identification process belongs to the source label (Source Label)
  • the service tag assigned to the dyeing process belongs to a color label (Color Label).
  • the processing may be performed by the controller 201, some of the service processing may be performed by the destination node 203, and some of the service processing may be performed by intermediate nodes on the packet forwarding path.
  • the intermediate node is responsible for performing load sharing processing on the packet
  • the controller 201 is responsible for performing source identification processing on the packet
  • the destination node 203 is responsible for dyeing the packet.
  • the intermediate node in order to implement a service processing manner, may be configured to obtain an entropy label of the second packet according to a preset manner. And performing load sharing processing on the second packet according to the entropy label, where the entropy label is a service label used to indicate load sharing processing, and the second packet may be used by the source node 202 to use the entropy label as an inner label. Inserted into the first packet, that is, the entropy label may be an inner label of the second packet.
  • the intermediate node may not need to identify the service processing manner represented by each service label, but only needs to identify the entropy label in the second packet. Therefore, the intermediate node The entropy label can be identified from the second packet according to its own preset manner, without the mapping relationship between the service label and the service processing mode established by the controller. Therefore, the controller 201 does not need to deliver the service to the intermediate node.
  • the mapping between labels and business processing methods For example, the preset manner of the intermediate node itself may be that the last label in the label stack of the second packet is identified as an entropy label.
  • the source node 202 may perform the entropy label according to the preset manner of the intermediate node.
  • the preset manner of the intermediate node itself may be that the label following the entropy label identifier in the second packet is identified as an entropy label.
  • the source node 202 may follow the preset manner of the intermediate node.
  • the entropy tag identifier is inserted in the tag stack immediately before the entropy tag.
  • the controller 201 may also send a mapping relationship between the service label and the service processing mode to the intermediate node, and the intermediate node may also identify the entropy label from the second packet according to the mapping relationship sent by the controller. This example does not limit this.
  • the controller 201 may determine, according to the mapping relationship, that the second packet corresponds to the service processing manner, and The second packet is processed according to the service processing manner. Specifically, in the forwarding process of the second packet from the source node 202 to the destination node 203, the controller 201 may capture the second packet by using one or some forwarding nodes that the second packet passes. Two messages are processed for business. Considering that controller 201 is usually responsible for multiple industries In this case, the controller 201 needs to be able to identify the service processing mode indicated by each service tag. To this end, the controller 201 can assign the service tag and the service processing mode when assigning the service tag to the service processing mode.
  • the mapping relationship between the two is saved.
  • the service processing mode indicated by the service label in the second packet can be determined according to the saved mapping relationship, so that the determined service can be determined according to the saved mapping relationship.
  • the processing mode processes the second packet.
  • the destination node may determine, according to the service label in the mapping relationship, that the second packet corresponds to the service processing mode, and according to The service processing manner processes the second packet. It is considered that the destination node is usually responsible for a plurality of service processing modes. In this case, the destination node 203 needs to be able to identify the service processing mode indicated by each service tag. To this end, the service tag sent by the controller 201 to the destination node 203. The destination node may save the mapping relationship with the service processing mode. When the destination node 203 receives the second packet, the destination node 203 may determine the service label in the second packet according to the mapping relationship.
  • the service processing mode is displayed, so that the second packet can be processed according to the determined service processing manner, and the service label in the second packet can be identified, so that the service label is popped from the second packet.
  • the first packet is obtained, so that the destination node 203 can perform subsequent processing on the packet, for example, the obtained first packet is further forwarded along other forwarding paths.
  • the network device may perform different service processing modes on the same packet.
  • the controller 201 may allocate different service labels for different service processing modes of the same FEC, and may correspond to the same FEC.
  • the multiple service tags are sent to the source node 202 corresponding to the FEC, and the source node 202 can insert multiple service tags corresponding to the FEC into the message corresponding to the FEC, so that the packet needs to be in the network.
  • the network device that performs service processing processes the packet according to each service processing mode. Therefore, in the process of packet forwarding, by inserting multiple service labels in the same packet, you can flexibly select a combination of service processing modes for the packet. For example, in the example of the message label shown in FIG. 5, an entropy tag, a QoS tag, a guide tag, a VPN prefix tag, a VPN tag, a dye tag, and a source tag are inserted in the message.
  • the processing corresponding to these service processing modes may be performed by a plurality of different network devices.
  • the message can be processed only in accordance with the business processing mode that it is responsible for.
  • the destination node 203 needs to process the second packet in accordance with the service processing mode in its own right, and also needs to pop all the service labels in the second packet to obtain the first packet, so as to facilitate the subsequent processing.
  • the normal processing of the first message is the case where multiple service tags are inserted in the same packet.
  • the source node 201 inserts the first service label, the second service label, and the third service label into the first packet to obtain the second packet, where the first service label indicates that the intermediate node is responsible for
  • the second service tag indicates a second service processing mode that the controller 201 is responsible for
  • the third service tag indicates a third service processing mode that the destination node 203 is responsible for.
  • the second packet is sent from the source node 202 to the destination.
  • the intermediate node can identify the first service label in the second packet and process the second packet according to the first service processing manner, and the controller 201 can identify the second packet in the second packet.
  • the second service label processes the second packet according to the second service processing manner
  • the destination node 203 can identify the third service label in the second packet and process the second packet according to the third service processing manner, and
  • the destination node 203 can identify all three service labels in the second packet, and pops the three service labels from the second packet to obtain the first packet. Complete the process of forwarding the first message.
  • any mechanism may be used to forward a packet with a service label, such as an IP routing mechanism, an MPLS forwarding mechanism, and a segment routing mechanism.
  • the packet is forwarded through the LSP label.
  • the LSP label and the service label of the packet can form the packet together.
  • the controller 201 may be further configured to send, to the source node 202, a next hop address corresponding to the FEC, to instruct the source node 202 to obtain an LSP label corresponding to the next hop address, and according to The LSP label performs forwarding processing on the second packet.
  • the LSP label may be an outer label
  • the service label may be an inner label.
  • the next hop address corresponding to the FEC indicates an address of a destination node corresponding to the FEC.
  • the controller 201 can allocate a service label for the service processing mode of the FEC, and establish a mapping relationship between the service label and the service processing mode.
  • the controller 201 sends the service tag to the source node 202 corresponding to the FEC, so that the source node 202 can insert the service tag in the message corresponding to the FEC, and on the other hand, the controller 201 can correspond to the FEC.
  • the mapping relationship is sent, so that the destination node 203 can pop the service label from the packet corresponding to the FEC according to the mapping relationship, where the service label is used to identify the service processing manner, and is used for During the forwarding process of the packet, the network device that needs to perform service processing on the packet processes the packet according to the service processing manner.
  • the service tag is allocated by the controller 201, the service tag is sent to the source node 202, and the mapping relationship between the service tag and the service processing mode is sent to the destination node 203.
  • the source corresponding to the FEC is corresponding.
  • the node 202 can be configured to insert the service label corresponding to the FEC in the packet corresponding to the FEC, and the destination node 203 corresponding to the FEC can be configured to pop the service label from the message corresponding to the FEC.
  • the packet corresponding to the FEC can be matched with the service label of the FEC in the forwarding process to implement the service processing of the packet by using the service label. Therefore, for each FEC in the network, only the controller 201 needs to be configured.
  • the service processing of the packets corresponding to each FEC can be implemented without statically configuring the source node 202 and the destination node 203 corresponding to each FEC, which greatly reduces the number of devices that need to be statically configured, and simplifies configuring and maintaining service processing for the network environment. work. Further, since the configuration and maintenance work of the service processing in the network is simplified, various service processing modes can be easily and flexibly configured for each FEC, so that various service processing in the network environment can be flexibly implemented.
  • FIG. 6 is a schematic flowchart of a method for processing a packet according to an embodiment of the present invention. The method includes:
  • Step 601 The controller allocates a service label to the service processing mode of the FEC, and establishes a mapping relationship between the service label and the service processing manner.
  • Step 602 The controller sends the service label corresponding to the FEC to a source node corresponding to the FEC, to indicate that the source node inserts the service label in a first packet corresponding to the FEC, to obtain Second message;
  • Step 603 The controller sends the mapping relationship to the destination node corresponding to the FEC, to instruct the destination node to pop the service label from the second packet according to the mapping relationship, to obtain the first a message;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet
  • the second packet is processed according to the service processing manner.
  • step 602 and step 603 are performed is not limited.
  • step 602 can include:
  • the controller binds the service label to the routing information corresponding to the FEC; the controller sends the routing information bound to the service label to the source node, to indicate the source node Inserting the service tag in the first packet to obtain the second packet.
  • step 603 can include, for example:
  • the controller inserts the service label and the service processing mode into network layer reachability information corresponding to the FEC, to form the service label and the service processing manner in the network layer reachability information.
  • the mapping relationship between the network layer and the destination node is sent to the destination node to indicate that the destination node pops the service label from the second packet according to the mapping relationship, and obtains a The first message is described.
  • the embodiment may further include: determining, by the controller, that the second packet corresponds to the service processing manner according to the service label, and the controller processing according to the service The method is configured to process the second packet, where the service processing mode is not load sharing processing.
  • the embodiment may further include: the controller sending, to the source node, a next hop address corresponding to the FEC, to instruct the source node to acquire a label switched path LSP corresponding to the next hop address. And performing the forwarding process on the second packet according to the LSP label, where the LSP label is an outer label and the service label is an inner label in the label stack of the second packet.
  • mapping relationship between the service label and the service processing mode and the content of the service label in the embodiment of the present invention can be referred to the embodiment shown in FIG. 2 .
  • the service tag is allocated by the controller, the service tag is sent to the source node, and the mapping relationship between the service tag and the service processing mode is sent to the destination node.
  • the controller For each FEC in the network, only You need to configure the controller to perform service processing on the packets corresponding to each FEC, without statically configuring the source and destination nodes corresponding to each FEC. This greatly reduces the number of devices that need to be statically configured, and simplifies configuration for the network environment. Maintenance business Rational work.
  • FIG. 7 is a schematic flowchart diagram of another method for processing a message according to an embodiment of the present invention.
  • the method includes:
  • Step 701 The source node receives the service label of the corresponding FEC sent by the controller, where the service label is allocated by the controller for the service processing mode of the FEC, and the source node is a source node corresponding to the FEC.
  • Step 702 The source node receives the first packet corresponding to the FEC, inserts the service label in the first packet, and obtains a second packet.
  • Step 703 The source node sends the second packet to the destination node corresponding to the FEC, to indicate that the destination node corresponding to the FEC is based on the mapping relationship between the service label and the service processing mode.
  • the service packet is popped up in the second packet, and the first packet is obtained; the mapping relationship is established by the controller and sent to the destination node;
  • the service label is configured to indicate, in the process of forwarding the second packet from the source node to the destination node, a network device that needs to perform service processing on the second packet according to the service.
  • the processing manner processes the second packet.
  • the step 701 may include: the source node receiving the routing information of the corresponding FEC sent by the controller; and the source node acquiring the service label bound to the routing information.
  • the embodiment may further include: receiving, by the source node, a next hop address corresponding to the FEC sent by the controller, and acquiring a label switched path LSP label corresponding to the next hop address as a corresponding location The LSP label of the FEC; the second packet is forwarded according to the LSP label; wherein, in the label stack of the second packet, the tunnel label is an outer label, and the service label is For the inner label.
  • mapping relationship between the service label and the service processing mode and the content of the service label in the embodiment of the present invention can be referred to the embodiment shown in FIG. 2 .
  • various embodiments of the method for performing the method in the source node in the embodiment of the present invention may be referred to the detailed description of the embodiment shown in FIG. 2, and details are not described herein again.
  • the source node receives, from the controller, a service label corresponding to the service processing mode of the FEC, where the service label is allocated by the controller for the service processing mode of the FEC.
  • the source node inserts the service label in the message corresponding to the FEC. Therefore, for each FEC in the network, the service corresponding to each FEC packet can be processed without statically configuring the source node corresponding to each FEC. This greatly reduces the number of devices that need to be statically configured, simplifying the task of configuring and maintaining business processes for the network environment.
  • FIG. 8 is a schematic flowchart diagram of another method for processing a packet according to an embodiment of the present invention.
  • the method includes:
  • Step 801 The destination node receives a mapping relationship between the service label sent by the controller and the service processing mode, where the service label is allocated by the controller for the service processing mode of the FEC, and the destination node is corresponding to the The destination node of the FEC;
  • Step 802 The destination node receives a second packet sent by the source node corresponding to the FEC, where the second packet is that the source node inserts the service label in a first packet corresponding to the FEC. owned;
  • Step 803 The destination node pops the service label from the second packet according to the mapping relationship, to obtain the first packet.
  • the service label is configured to indicate, in the process of forwarding the second packet from the source node to the destination node, a network device that needs to perform service processing on the second packet according to the service.
  • the processing manner processes the second packet.
  • the step 801 may include: the destination node receives network layer reachability information corresponding to the FEC sent by the controller; and the destination node obtains the service label from the network layer reachability information
  • the service processing manner is to obtain a mapping relationship between the service label and the service processing manner.
  • the embodiment may further include: determining that the second packet corresponds to the service processing manner according to the service label, and the destination node processing according to the service according to the mapping relationship; The method processes the second packet.
  • mapping relationship between the service label and the service processing mode and the content of the service label in the embodiment of the present invention can be referred to the embodiment shown in FIG. 2 .
  • specific implementation manners of the method for performing the method in the embodiment of the present invention reference may be made to the detailed description of the system embodiment shown in FIG. 2, and details are not described herein again.
  • the destination node receives the service label sent by the controller and the The mapping between the service processing modes, the correspondence between the service label and the service label processing mode is pre-established by the controller, and the destination node can pop the service label from the message corresponding to the FEC through the mapping relationship.
  • the destination node For each FEC in the network, it is possible to perform service processing on packets corresponding to each FEC without statically configuring the destination node corresponding to each FEC, which greatly reduces the number of devices that need to be statically configured, and simplifies configuration for the network environment. Maintain business processing work.
  • the FEC is used as the target FEC in the network environment, and the controller sends the next hop address and the service label of the corresponding target FEC to the source node of the corresponding target FEC, and delivers the message to the destination node of the corresponding target FEC.
  • the service processing mode corresponding to the target FEC includes a first service processing mode, a second service processing mode, and a third service processing mode.
  • the first service processing mode is performed by the controller, and the second service processing mode is performed by the middle of the corresponding target FEC.
  • the section is responsible for the third service processing mode is responsible for the destination node corresponding to the target FEC.
  • FIG. 9 is a schematic flowchart diagram of another method for processing a message according to an embodiment of the present invention.
  • the embodiment of the present invention can be applied to the above exemplary application scenario, and the method includes the following steps:
  • Step 901 The controller allocates a service label for the service processing mode of the target FEC.
  • the controller may allocate a first service label for the first service processing mode of the target FEC, may allocate a second service label for the second service processing manner of the target FEC, and may allocate the third service processing manner for the target FEC.
  • Three business labels may be used.
  • Step 902 The controller establishes a mapping relationship between the service label and the service processing mode.
  • the controller may establish a mapping relationship between the first service label and the first service processing as the first mapping relationship, and establish a mapping relationship between the second service label and the second service processing as the second mapping relationship, and A mapping relationship between the third service tag and the third service process may be established as the third mapping relationship.
  • Step 903 The controller generates a first NLRI of the corresponding target FEC according to the next hop address of the corresponding target FEC and the service label, and sends the first NLRI to the source node of the corresponding target FEC.
  • next hop address may be inserted into the NLRI field of the first network layer reachability information as the routing information of the corresponding target FEC, and the first service label, the second service label, and the third service label may be bound as the BGP attribute. On an NLRI.
  • the next hop address corresponds to the address of the destination node of the target FEC.
  • Step 904 The source node searches for an LSP label according to the next hop address, and saves both the LSP label and the service label corresponding to the target FEC.
  • the label saved by the source node corresponding to the target FEC includes an LSP label, a first service label, a second service label, and a third service label.
  • Step 905 The controller generates a second NLRI according to the mapping relationship between the service label and the service processing mode, and delivers the second NLRI to the destination node of the corresponding target FEC.
  • the controller may form three second NLRI information corresponding to the foregoing three mapping relationships and send the same to the destination node.
  • a second NLRI the SID/Label/Index field is inserted with the first service tag, and the Type Specific Value field is inserted with the first service processing mode.
  • the SID/Label/Index field is inserted with the second service tag, and the Type Specific Value field is inserted with the second service processing mode.
  • the SID/Label/Index field is inserted with a third service tag, and the Type Specific Value field is inserted with a third service processing mode.
  • Step 906 The destination node saves the received mapping relationship.
  • the mapping relationship saved by the destination node includes the foregoing first mapping relationship, second mapping relationship, and third mapping relationship.
  • Step 907 When the source node receives the first packet corresponding to the target FEC, insert the LSP label and the service label into the first packet to obtain the second packet.
  • the label stack of the second packet includes an LSP label, a first service label, a second service label, and a third service label.
  • the LSP label is an outer label
  • the first service label, the second service label, and the third service label are inner label.
  • Step 908 The source node forwards the second packet according to the LSP label.
  • Step 909 When the intermediate node receives the second packet, the controller captures the second packet by using the intermediate node.
  • the intermediate node may be any intermediate node on the forwarding path of the second packet.
  • the intermediate node may send the second packet in response to the controller's scratch orientation controller, that is, perform this step 909, and on the other hand, the intermediate node may identify the second packet.
  • the service tag in the packet performs service processing on the second packet, that is, performs the subsequent step 911.
  • Step 910 The controller identifies the service label in the second packet according to the mapping relationship, and responds to the first service label, and processes the second packet according to the first service processing manner.
  • the controller may identify the first service label in the second packet according to the first mapping relationship that is established in advance, and determine that the first service label indicates the first service processing manner, so that the first service processing may be performed.
  • the method processes the second packet.
  • the controller may identify the second service label and the third service label in the second packet according to the pre-established second mapping relationship and the third mapping relationship.
  • the second service processing mode indicated by the second service label and the service processing manner indicated by the third service label do not need to be executed by the controller. Therefore, the controller may not need to respond to the indication of the second service label and the third service label. Perform the action.
  • Step 911 When the intermediate node receives the second packet, the intermediate node identifies the second service label in the second packet according to the fixed configuration, and performs the second packet according to the second service processing manner indicated by the second service label. deal with.
  • the second service processing mode is load sharing processing
  • the second service label is an entropy label.
  • the intermediate node can find the entropy label from the second packet according to the fixed configuration. Then, the intermediate node can process the entropy label and perform load sharing processing on the second packet according to the processing result of the entropy label.
  • Step 912 The intermediate node forwards the second packet according to the LSP label.
  • Step 913 The destination node receives the second packet, and identifies the service label in the second packet according to the mapping relationship.
  • the destination node may identify the first service label, the second service label, and the third service label from the second packet according to the first mapping relationship, the second mapping relationship, and the third mapping relationship that are saved in advance.
  • Step 914 The destination node processes the second packet according to the third service processing manner.
  • the destination node may determine, according to the third mapping relationship that is established in advance, that the third service label indicates the third service processing manner, so that the second service processing manner may be used to perform the second The message is processed.
  • Step 915 The destination node pops the service label from the second packet to obtain the first packet.
  • the destination node pops all the service labels in the second packet from the second packet, that is, the destination node uses the first service label, the second service label, and the third service label in the second packet. Both pop up from the second message.
  • FIG. 10 is a schematic structural diagram of a controller according to an embodiment of the present invention.
  • the controller 1000 includes:
  • the allocating module 1001 is configured to allocate a service label for the service processing mode of the FEC;
  • the establishing module 1002 is configured to establish a mapping relationship between the service tag and the service processing mode.
  • the first sending module 1003 is configured to send the service label corresponding to the FEC to the source node corresponding to the FEC, to indicate that the source node inserts the service label in the first packet corresponding to the FEC, to obtain Second message;
  • the second sending module 1004 is configured to send the mapping relationship to the destination node that is corresponding to the FEC, to indicate that the destination node pops the service label from the second packet according to the mapping relationship, to obtain the first Message
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the distribution module 1001 can allocate a service label, and the establishing module 1002 can establish a mapping relationship between the service label allocated by the distribution module 1001 and its service processing mode.
  • a sending module 1003 The service label allocated by the distribution module 1001 can be delivered to the source node, and the second sending module 1004 can deliver the mapping relationship established by the establishing module 1002 to the destination node.
  • the first sending module 1003 may include a binding submodule and a first sending submodule, where the binding submodule is configured to bind the service label to the routing information corresponding to the FEC; a sending submodule, configured to send the routing information that is bound to the service label to the source node, to indicate that the source node inserts the service label in the first packet, to obtain the second Message.
  • the second sending module 1004 may include an insertion sub-module and a second sending sub-module.
  • the inserting sub-module is configured to insert the service label and the service processing manner into a network layer corresponding to the FEC.
  • the mapping relationship between the service label and the service processing mode is formed in the network layer reachability information, and the second sending submodule is configured to send the network layer reachable to the destination node.
  • the information is sent to the destination node to pop the service label from the second packet according to the mapping relationship, to obtain a first packet.
  • the controller 1000 may further include a determining module and a service processing module, where the determining module is configured to determine, according to the service label, that the second packet corresponds to the service processing manner according to the mapping relationship;
  • the service processing module is configured to process the second packet according to the service processing manner.
  • the controller 1000 may further include: a third sending module, configured to send, to the source node, a next hop address corresponding to the FEC, to instruct the source node to acquire a label corresponding to the next hop address Exchanging the path LSP label and forwarding the second packet according to the LSP label; wherein, in the label stack of the second packet, the LSP label is an outer label, and the service label is Layer label.
  • a third sending module configured to send, to the source node, a next hop address corresponding to the FEC, to instruct the source node to acquire a label corresponding to the next hop address Exchanging the path LSP label and forwarding the second packet according to the LSP label; wherein, in the label stack of the second packet, the LSP label is an outer label, and the service label is Layer label.
  • controller 1000 in this embodiment corresponds to the controller 201 in the foregoing embodiment shown in FIG. 2 .
  • controller 1000 in this embodiment corresponds to the controller 201 in the foregoing embodiment shown in FIG. 2 .
  • specific implementations of the controller 1000 in this embodiment refer to the detailed description of the foregoing embodiment shown in FIG. 2, and details are not described herein again.
  • the controller 1000 allocates the service label, sends the service label to the source node, and delivers the mapping relationship between the service label and the service processing mode to the destination node.
  • the controller 1000 can be configured to process the packets corresponding to each FEC without statically configuring the source node and the destination node corresponding to each FEC. This greatly reduces the number of devices that need to be statically configured, and simplifies the network environment. Match Set up and maintain business processing work.
  • FIG. 11 is a schematic structural diagram of a source node device 1100 according to an embodiment of the present invention.
  • the source node device 1100 includes:
  • the first receiving module 1101 is configured to receive a service label of a corresponding FEC sent by the controller, where the service label is allocated by the controller for service processing of the FEC, and the source node is a source node corresponding to the FEC. ;
  • the second receiving module 1102 is configured to receive a first packet corresponding to the FEC.
  • the insertion module 1103 is configured to insert the service tag in the first packet to obtain a second packet.
  • the first sending module 1104 is configured to send the second packet to the destination node corresponding to the FEC, to indicate that the destination node corresponding to the FEC is based on a mapping relationship between the service label and the service processing mode.
  • the service label is popped up in the second packet, and the first packet is obtained; the mapping relationship is established by the controller and sent to the destination node;
  • the service label is used to indicate, according to the service, that the network device that needs to perform service processing on the second packet is in the process of forwarding the second packet from the source node 1100 to the destination node.
  • the processing manner processes the second packet.
  • the first receiving module 1101 can receive the service label of the corresponding FEC from the controller, and the second receiving module 1102 can receive the first packet corresponding to the FEC, and the first inserting module 1103
  • the first packet sent by the first receiving module 1101 can be inserted into the first packet received by the second receiving module 1102 to obtain the second packet, and the first sending module 1104 can send the inserting module 1103 to the destination node corresponding to the FEC.
  • the second message obtained.
  • the first receiving module 1101 may include, for example, a first receiving submodule and a first acquiring submodule, where the first receiving submodule is configured to receive routing information of the corresponding FEC sent by the controller; a submodule, configured to obtain the service tag bound to the information.
  • the source node device 1100 may further include: a third receiving module, configured to receive a next hop address corresponding to the FEC sent by the controller, and an acquiring module, configured to acquire, corresponding to the next hop address
  • the label switching path LSP label is used as an LSP label corresponding to the FEC; the second packet is forwarded according to the LSP label; wherein, the second packet is In the label stack of the text, the LSP label is an outer label, and the service label is an inner label.
  • the source node device 1100 in this embodiment corresponds to the source node 202 in the foregoing embodiment shown in FIG. 2.
  • the specific implementations of the source node device 1100 in this embodiment refer to the detailed description of the foregoing embodiment shown in FIG. 2, and details are not described herein again.
  • the source node device 1100 can implement the insertion of the service label in the packet by receiving the service label from the controller. For each FEC in the network, it is not necessary to statically configure the source node device 1100 corresponding to each FEC. The service processing of the packets corresponding to each FEC can be implemented. This greatly reduces the number of devices that need to be statically configured, and simplifies the configuration and maintenance of service processing for the network environment.
  • FIG. 12 is a schematic structural diagram of a destination node device 1200 according to the present invention.
  • the device 1200 includes:
  • the first receiving module 1201 is configured to receive a mapping relationship between a service tag sent by the controller and a service processing mode, where the service tag is allocated by the controller to forward the service class of the equivalent class FEC. Determining the destination node as a destination node corresponding to the FEC;
  • the second receiving module 1202 is configured to receive a second packet that is sent by the source node that is corresponding to the FEC, where the second packet is that the source node inserts the service label in the first packet corresponding to the FEC. Obtained
  • the pop-up module 1203 is configured to: eject the service label from the second packet according to the mapping relationship, to obtain a first packet;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the first receiving module 1201 may receive a mapping relationship between the service tag and the service processing mode, and the second receiving module 1202 may receive the second tag inserted with the service tag.
  • the message ejecting module 1203 may identify the service tag from the second packet received by the second receiving module 1202 according to the mapping relationship received by the first receiving module 1201, and pop the service tag from the second packet.
  • the first receiving module 1201 may include a second receiving submodule and a second acquiring submodule, where the second receiving submodule is configured to receive the corresponding FEC sent by the controller.
  • Network layer reachability information a second obtaining submodule, configured to obtain the service tag and the service processing mode from the second network layer reachability information, to obtain the service tag and the service processing manner The mapping relationship between them.
  • the destination node device 1200 may further include a determining module and a service processing module, where the determining module is configured to determine, according to the service label, the second packet corresponding to the service processing manner according to the mapping relationship.
  • the service processing module is configured to process the second packet according to the service processing manner.
  • the destination node device 1200 in this embodiment corresponds to the destination node 203 in the foregoing embodiment shown in FIG. 2 .
  • the specific implementations of the destination node device 1200 in this embodiment refer to the detailed description of the foregoing embodiment shown in FIG. 2, and details are not described herein again.
  • the destination node device 1200 can perform the mapping between the service label and the service processing mode to obtain the pop-up service label from the packet.
  • the destination node device 1200 corresponding to each FEC can perform service processing on the packets corresponding to the FECs, which greatly reduces the number of devices that need to be statically configured, and simplifies the work of configuring and maintaining service processing for the network environment.
  • FIG. 13 is a schematic structural diagram of a controller according to an embodiment of the present invention.
  • the controller 1300 includes a processor 1301, a memory 1302, a network interface 1303, and a bus system 1304.
  • the bus system 1304 is for coupling together various hardware components of the controller 1300.
  • the network interface 1303 is configured to implement a communication connection between the controller 1300 and at least one other network element, and may use an Internet, a wide area network, a local network, a metropolitan area network, or the like.
  • the memory 1302 is configured to store program instructions and data.
  • the processor 1301 is configured to read instructions and data stored in the memory 1302, and perform the following operations:
  • the processor 1301 allocates a service label for forwarding a service processing manner of an equivalent class FEC, and establishes a mapping relationship between the service label and the service processing manner;
  • the processor 1301 sends the service label corresponding to the FEC to a source node corresponding to the FEC, to instruct the source node to insert the service in a first packet corresponding to the FEC. Label, get the second message;
  • the processor 1301 sends the mapping relationship to the destination node corresponding to the FEC, to instruct the destination node to pop the service label from the second packet according to the mapping relationship, to obtain the first report.
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the processor 1301 is configured to send the service label corresponding to the FEC to a source node corresponding to the FEC, to indicate that the source node inserts the first packet in the first packet corresponding to the FEC.
  • the service tag which gets the second message, for example, can do the following:
  • the processor 1301 binds the service label to routing information corresponding to the FEC;
  • the processor 1301 sends the routing information that is bound to the service label to the source node, to indicate that the source node inserts the service label in the first packet, and obtains the second packet. Text.
  • the processor 1301 is configured to send the mapping relationship to the destination node that is corresponding to the FEC, to indicate that the destination node pops the service label from the second packet according to the mapping relationship,
  • the processor 1301 is configured to send the mapping relationship to the destination node that is corresponding to the FEC, to indicate that the destination node pops the service label from the second packet according to the mapping relationship
  • the processor 1301 inserts the service label and the service processing mode into the network layer reachability information corresponding to the FEC, to form the service label and the service processing manner in the network layer reachability information. Mapping relationship between
  • the processor 1301 sends the network layer reachability information to the destination node, to instruct the destination node to pop the service label from the second packet according to the mapping relationship, to obtain the first report. Text.
  • processor 1301 can also perform the following operations, for example:
  • the processor 1301 determines, according to the mapping relationship, that the second packet corresponds to the service processing mode according to the service label.
  • the processor 1301 processes the second packet according to the service processing manner
  • the service processing does not perform load balancing processing on the packet, and the network device is the controller.
  • processor 1301 can also perform the following operations, for example:
  • the processor 1301 sends, to the source node, a label switched path LSP label corresponding to the FEC, to instruct the source node to forward the second packet according to the LSP label;
  • the LSP label is an outer label
  • the service label is an inner label
  • controller 1300 in this embodiment corresponds to the controller 201 in the foregoing embodiment shown in FIG. 2 .
  • the specific implementations of the controller 1300 in this embodiment refer to the detailed description of the foregoing embodiment shown in FIG. 2, and details are not described herein again.
  • FIG. 14 is a schematic structural diagram of a source node device according to an embodiment of the present invention.
  • the source node device 1400 in this embodiment may include, for example, a processor 1401, a memory 1402, a network interface 1403, and a bus system 1404.
  • the bus system 1404 is configured to couple the various hardware components of the forwarding node 1400 together.
  • the network interface 1403 is configured to implement a communication connection between the forwarding node 1400 and at least one other network element, and may use an Internet, a wide area network, a local network, a metropolitan area network, or the like.
  • the memory 1402 is configured to store program instructions and data.
  • the processor 1401 is configured to read instructions and data stored in the memory 1402, and perform the following operations:
  • the processor 1401 receives a service label corresponding to the forwarding equivalent type FEC sent by the controller, where the service label is allocated by the controller for the service processing mode of the FEC, and the source node device 1400 is corresponding to the Source node of the FEC;
  • the processor 1401 receives the first packet corresponding to the FEC, and inserts the service label into the first packet to obtain a second packet.
  • the processor 1401 sends the second packet to the destination node corresponding to the FEC, to indicate that the destination node corresponding to the FEC is in accordance with the mapping relationship between the service label and the service processing mode.
  • the service label is popped up in the second packet, and the first packet is obtained; the mapping relationship is established by the controller and sent to the destination node;
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the processor 1401 may perform the following operations, for example:
  • the processor 1401 receives routing information of a corresponding FEC sent by the controller;
  • the processor 1401 acquires the service tag bound to the routing information.
  • processor 1401 can also perform the following operations, for example:
  • the processor 1401 receives a label switched path LSP label corresponding to the FEC sent by the controller;
  • the second packet is forwarded according to the LSP label
  • the tunnel label is an outer label
  • the service label is an inner label
  • the source node device 1400 in this embodiment corresponds to the source node 202 in the foregoing embodiment shown in FIG. 2 .
  • the specific implementations of the source node device 1400 in this embodiment refer to the detailed description of the foregoing embodiment shown in FIG. 2, and details are not described herein again.
  • the destination node device 1500 may include, for example, a processor 1501, a memory 1502, a network interface 1503, and a bus system 1504.
  • the bus system 1504 is for coupling together various hardware components of the forwarding node 1500.
  • the network interface 1503 is configured to implement a communication connection between the forwarding node 1500 and at least one other network element, and may use an Internet, a wide area network, a local network, a metropolitan area network, or the like.
  • the memory 1502 is configured to store program instructions and data.
  • the processor 1501 is configured to read instructions and data stored in the memory 1502, and perform the following operations:
  • the processor 1501 receives a mapping relationship between a service tag sent by the controller and a service processing mode, where the service tag is allocated by the controller for forwarding the service class of the equivalence class FEC, and the destination node
  • the device 1500 is a destination node corresponding to the FEC;
  • the processor 1501 receives a second packet that is sent by the source node corresponding to the FEC, where the second packet is obtained by inserting the service label in the first packet corresponding to the FEC. ;
  • the processor 1501 pops up the industry from the second packet according to the mapping relationship. Obtaining the first message
  • the service tag is configured to: in the process of forwarding the second packet from the source node to the destination node, instructing a network device that needs to perform service processing on the second packet according to the service processing The method processes the second packet.
  • the processor 1501 may perform the following operations, for example:
  • the processor 1501 receives network layer reachability information corresponding to the FEC sent by the controller;
  • the processor 1501 obtains the service label and the service processing manner from the network layer reachability information to obtain a mapping relationship between the service label and the service processing manner.
  • processor 1501 can also perform the following operations, for example:
  • the processor 1501 determines, according to the mapping relationship, that the second packet corresponds to the service processing mode according to the service label.
  • the processor 1501 processes the second packet according to the service processing manner
  • the service processing mode is not load balancing processing on the packet, and the network device is the destination node.
  • the destination node device 1500 in this embodiment corresponds to the destination node 203 in the foregoing embodiment shown in FIG. 2 .
  • the specific implementations of the destination node device 1500 in this embodiment refer to the detailed description of the foregoing embodiment shown in FIG. 2, and details are not described herein again.
  • the first message mentioned in the embodiment of the present invention and the “first” in the first sending module are only used for name identification, and do not represent the first in the order. The same rules apply to "second”, “third” and “fourth”.
  • the processor in the embodiment of the present invention may be an integrated circuit chip with signal processing capability.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • These instructions may be implemented and controlled by a processor therein for performing the methods disclosed in the embodiments of the present invention.
  • the processor may also be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit, or an off-the-shelf programmable Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.
  • DSP digital signal processing
  • FPGA off-the-shelf programmable Field Programmable Gate Array
  • the above general-purpose processor may be a microprocessor or the processor may be any conventional processor, decoder or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • bus system may include a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus systems in Figures 8 and 9.

Landscapes

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

Abstract

本发明实施例公开了一种报文处理的方法、设备和系统。该系统包括：控制器，用于为FEC的业务处理方式分配业务标签，建立业务标签与业务处理方式之间的映射关系，向源节点发送业务标签，并向目的节点发送映射关系；源节点，用于接收控制器发送的业务标签，接收第一报文，在所述第一报文中插入业务标签而得到第二报文，并向目的节点发送第二报文；目的节点，用于接收控制器发送的映射关系，接收源节点发送的第二报文，并根据映射关系从第二报文中弹出业务标签而得到第一报文；其中，业务标签用于在第二报文从源节点到目的节点的转发过程中，指示需要对第二报文进行业务处理的网络设备按照业务处理方式对第二报文进行处理。

Description

一种报文处理的方法、设备和系统
本申请要求于2015年9月22日提交中国专利局、申请号为201510608874.X、发明名称为“一种报文处理的方法、设备和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，特别是涉及一种报文处理的方法、设备和系统。
背景技术
在网络环境中，报文需要沿着转发路径从源节点转发到目的节点，从而完成数据包的转发，实现数据传输。其中，源节点也称入节点(Ingress Node)，目的节点也称出节点(Egress Node)。对于支持多协议标签交换(Multiple Protocol Label Switch，简称MPLS)的网络环境，可以选择不同的机制来实现报文转发，如互联网协议(Internet Protocol，简称IP)路由机制、MPLS机制、分段路由(Segment Routing，简称SR)机制等。在MPLS机制、分段路由机制等报文转发机制中，转发路径也称标签交换路径(Label Switch Path，简称LSP)。
在网络转发报文的过程中，有时需要对报文进行一些业务处理。例如，当报文的转发路径上某转发节点有多条链路可以选择时，为了实现该转发节点上负载均衡，该转发节点需要根据各链路的负载情况来选择链路转发该报文。
现有技术中，对于一转发等价类(Forwarding Equivalence Class，简称FEC)，为了在对应该FEC的报文的转发过程中实现对该报文进行业务处理，需要对该FEC的转发路径上的一些转发节点进行静态配置，这些转发节点就可以根据静态配置的业务处理方式对对应该FEC的报文进行处理。但是，由于网络环境中存在大量的FEC，而每一FEC的业务处理方式需要配置到不同的转发节点，这就会使得网络中大量的转发节点都需要进行静态配置，导致为网络环境配置和维护业务处理的工作过于复杂， 从而造成网络环境中的各种业务处理难以灵活地实现。
发明内容
本发明实施例所要解决的技术问题是，提供一种报文处理的方法和设备，以解决现有技术中由于通过静态配置转发节点来实现业务处理而导致网络配置和维护复杂的技术问题。
第一方面，本发明实施例提供了一种报文处理的系统，所述系统包括：
控制器，用于为转发等价类FEC的业务处理方式分配业务标签，建立所述业务标签与所述业务处理方式之间的映射关系，向对应所述FEC的源节点发送所述业务标签，并向对应所述FEC的目的节点发送所述映射关系；
所述源节点，用于接收所述控制器发送的对应所述FEC的所述业务标签，接收对应所述FEC的第一报文，并在所述第一报文中插入所述业务标签而得到第二报文，向对应所述FEC的目的节点发送所述第二报文；
所述目的节点，用于接收所述控制器发送的所述映射关系，接收对应所述FEC的源节点发送的第二报文，并根据所述映射关系从所述第二报文中弹出所述业务标签而得到所述第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述控制器向所述源节点发送所述业务标签，包括：
所述控制器将所述业务标签绑定在对应所述FEC的路由信息上；
所述控制器向所述源节点发送绑定有所述业务标签的所述路由信息。
可选的，所述控制器向所述目的节点发送所述映射关系，包括：
所述控制器将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；
向所述目的节点发送所述网络层可达信息。
可选的，所述业务处理方式为对报文进行负载分担处理，所述网络设备为从所述源节点到所述目的节点的转发路径上的中间节点，所述业务标签为所述第二报文的标签栈中的内层标签。
第二方面，本发明实施例提供了一种报文处理的方法，所述方法包括：
控制器为转发等价类FEC的业务处理方式分配业务标签，并建立所述业务标签与所述业务处理方式之间的映射关系；
所述控制器向对应所述FEC的源节点发送对应所述FEC的所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文；
所述控制器向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述控制器向对应所述FEC的源节点发送对应所述FEC的所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文，包括：
所述控制器将所述业务标签绑定在对应所述FEC的路由信息上；
所述控制器向所述源节点发送绑定有所述业务标签的所述路由信息，以指示所述源节点在所述第一报文中插入所述业务标签，得到所述第二报文。
可选的，所述控制器向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文，包括：
所述控制器将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；
所述控制器向所述目的节点发送所述网络层可达信息，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文。
第三方面，本发明实施例提供了另一种报文处理的方法，所述方法包括：
源节点接收控制器发送的对应转发等价类FEC的业务标签，所述业务标签是所述控制器为所述FEC的业务处理方式分配的，所述源节点为对应所述 FEC的源节点；
所述源节点接收对应所述FEC的第一报文，在所述第一报文中插入所述业务标签，得到第二报文；
所述源节点向对应所述FEC的目的节点发送所述第二报文，以指示对应所述FEC的目的节点根据所述业务标签与所述业务处理方式之间的映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；所述映射关系是所述控制器建立并发送给所述目的节点的；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述源节点接收控制器发送的对应FEC的业务标签，包括：
所述源节点接收所述控制器发送的对应FEC的路由信息；
所述源节点获取所述路由信息信息上绑定的所述业务标签。
第四方面，本发明实施例提供了又一种报文处理的方法，所述方法包括：
目的节点接收控制器发送的业务标签与业务处理方式之间的映射关系，所述业务标签是所述控制器为转发等价类FEC的所述业务处理方式分配的，所述目的节点为对应所述FEC的目的节点；
所述目的节点接收对应所述FEC的源节点发送的第二报文，所述第二报文是所述源节点在对应所述FEC的第一报文中插入所述业务标签而得到的；
所述目的节点所述目的节点根据所述映射关系，从所述第二报文中弹出所述业务标签，得到所述第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述目的节点接收业务标签与业务处理方式之间的映射关系，包括：
所述目的节点接收所述控制器发送的对应所述FEC的网络层可达信息；
所述目的节点从所述网络层可达信息中获取所述业务标签与所述业务处理方式，以得到所述业务标签与所述业务处理方式之间的映射关系。
第五方面，本发明实施例提供了一种控制器，所述控制器包括：
分配模块，用于为转发等价类FEC的业务处理方式分配业务标签；
建立模块，用于建立所述业务标签与所述业务处理方式之间的映射关系；
第一发送模块，用于向对应所述FEC的源节点发送对应所述FEC所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文；
第二发送模块，用于向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述第一发送模块包括：
绑定子模块，用于将所述业务标签绑定在对应所述FEC的路由信息上；
第一发送子模块，用于向所述源节点发送绑定有所述业务标签的所述路由信息，以指示所述源节点在所述第一报文中插入所述业务标签，得到所述第二报文。
可选的，所述第二发送模块包括：
插入子模块，用于将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；
第二发送子模块，用于向所述目的节点发送所述网络层可达信息，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文。
第六方面，本发明实施例提供了一种源节点设备，所述设备包括：
第一接收模块，用于接收控制器发送的对应转发等价类FEC的业务标签，所述业务标签是所述控制器为所述FEC的业务处理分配的，所述源节点为对应所述FEC的源节点；
第二接收模块，用于接收对应所述FEC的第一报文；
插入模块，用于在所述第一报文中插入所述业务标签，得到第二报文；
第一发送模块，用于向对应所述FEC的目的节点发送所述第二报文，以 指示对应所述FEC的目的节点根据所述业务标签与所述业务处理方式之间的映射关系从所述第二报文中弹出所述业务标签，得到第一报文；所述映射关系是所述控制器建立并发送给所述目的节点的；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
第七方面，本发明实施例提供了一种目的节点设备，所述设备包括：
第一接收模块，用于接收控制器发送的业务标签与业务处理方式之间的映射关系，所述业务标签是所述控制器为转发等价类FEC的所述业务处理方式分配的，所述目的节点为对应所述FEC的目的节点；
第二接收模块，用于接收对应所述FEC的源节点发送的第二报文，所述第二报文是所述源节点在对应所述FEC的第一报文中插入所述业务标签而得到的；
弹出模块，用于根据所述映射关系，从所述第二报文中弹出所述业务标签，得到第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
与现有技术相比，本发明实施例至少具有以下优点：
采用本发明实施例的技术方案，通过控制器分配业务标签、向源节点下发业务标签并向目的节点下发业务标签与业务处理方式之间的映射关系，源节点无需静态配置就可以实现在报文中插入业务标签，目的节点无需静态配置就可以实现从报文中弹出业务标签，这样，在报文从源节点到目的节点转发的过程中，网络设备可以就根据报文中业务标签对报文进行业务处理，由此可见，无需静态配置转发节点就可以在报文转发的过程中实现对报文的业务处理，从而大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处理的工作，使得网络环境中的各种业务处理能够灵活地实现。此外，通过控制器分配业务标签、向源节点下发业务标签并向目的节点下发映射关系，可以使得报文在转发过程中携带用来承载多种不同的业务处理需求的业务标签，这就使得各业务标签可以灵活地 形成各种组合插入到报文中，以灵活地按照各种业务处理方式的组合对报文进行处理，从而使得MPLS标签能够更加灵活地适用于具有多业务需求的应用场景。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，还可以根据这些附图获得其他的附图。
图1为本发明实施例中一应用场景所涉及的系统框架示意图；
图2为本发明实施例中一种报文处理的系统的结构示意图；
图3为本发明实施例中一种网络层可达信息的格式示意图；
图4为本发明实施例中一种网络层可达信息字段的格式示意图；
图5为本发明实施例中一种报文标签的示意图；
图6为本发明实施例中一种报文处理的方法的流程示意图；
图7为本发明实施例中另一种报文处理的方法的流程示意图；
图8为本发明实施例中又一种报文处理的方法的流程示意图；
图9为本发明实施例中又一种报文处理的方法的流程示意图；
图10为本发明实施例中一种报文处理的控制器的流程示意图；
图11为本发明实施例中一种报文处理的源节点设备的流程示意图；
图12为本发明实施例中一种报文处理的目的节点设备的流程示意图；
图13为本发明实施例中一种控制器的结构示意图；
图14为本发明实施例中一种源节点设备的结构示意图；
图15为本发明实施例中一种目的节点设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明中的方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描 述，显然，所描述的实施例仅是本发明一部分实施例，而不是全部的实施例。
发明人经过研究发现，为了使网络环境能够实现对报文的业务处理，考虑到网络环境中通常具有许多FEC，而对应不同FEC的报文需要按照不同的业务处理方式进行处理，因此，网络设备需要有针对性的对报文进行业务处理，为此，在报文转发的过程中可以为报文添加用于标识业务处理方式的指示信息，这样，网络设备可以通过读取该指示信息确定对该报文进行相应的业务处理。而为了使得报文在转发过程中具有该指示信息，就需要报文在转发路径上的源节点处添加该指示信息，并在转发路径上的目的节点处弹出该指示信息。因此，现有技术中，对于一个FEC，需要静态配置对应该FEC的源节点和目的节点，以使得源节点能够对对应该FEC的报文添加指示信息，并使得目的节点能够对对应该FEC的报文弹出指示信息。但是，在实际网络中，FEC对应的源节点和目的节点之间可能存在大量的转发节点，因此，现有技术为了在网络环境中实现业务处理就需要对大量的转发节点进行静态配置，这导致了网络配置和维护工作过于复杂，从而造成业务处理难以灵活地实现。
参考图1，图1为本发明实施方式的应用网络场景示意图，其中，该网络场景包括：控制器(controller)101、转发节点102和转发节点103。该控制器101可以为到控制与转发分离网络架构的控制器，该转发节点102和转发节点103可以为控制转发分离网络架构中的转发节点。其中，对于一个FEC来说，对应该FEC的转发路径上，转发节点102为源节点，转发节点103为目的节点。在图1所示的网络场景中，控制器101可以为该FEC的业务处理方式分配业务标签，建立该业务标签与该业务处理方式之间的映射关系，并且，控制器101可以向转发节点102发送对应该业务标签，并向转发节点103发送该映射关系；转发节点102在接收到对应该FEC的第一报文时，可以将该从控制器101接收到的业务标签插入该第一报文中而得到第二报文，并向转发节点103发送该第二报文；转发节点103在接收到该第二报文时，可以根据从控制器101接收的该映射关系从该第二报文中弹出该业务标签而得到该第一报文；在第二报文从转发节点102到转发节点103的转发过程中，需要对该第二报文进行业务处理的网络设 备，可以根据该第二报文中业务标签选择对应的业务处理方式对第二报文进行处理。
上述应用场景中，对应该FEC的报文从转发节点102到转发节点103的转发路径上，可以不经过任何中间节点，也可以经过一个或多个中间节点，本发明实施例对此不做限定。
需要注意的是，上述应用场景仅是为了便于理解本发明的原理而示出，本发明的实施方式在此方面不受任何限制。本发明的实施方式可以应用于适用的任何场景。
下面结合附图，通过实施例来详细说明本发明中报文处理的方法、相关设备和系统的实现方式。
参见图2，图2为本发明实施例提供的一种报文处理系统的示意图。在本实施例中，所述系统包括：
控制器201，用于为对应FEC的业务处理方式分配业务标签，建立所述业务标签与所述业务处理方式之间的映射关系，向对应所述FEC的源节点202发送对应所述FEC的所述业务标签，并向对应所述FEC的目的节点203发送所述映射关系；
所述源节点202，用于接收所述控制器201发送的对应所述FEC的所述业务标签，接收对应所述FEC的第一报文，在所述第一报文中插入所述业务标签而得到第二报文，并向对应所述FEC的目的节点203发送所述第二报文；
所述目的节点203，用于接收所述控制器201发送的所述映射关系，接收对应所述FEC的源节点202发送的第二报文，并根据所述映射关系，从所述第二报文中弹出所述业务标签而得到所述第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点202到所述目的节点203的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
在本实施例中，对于网络环境中的任意一个FEC，可以通过控制器201来为该FEC配置相应的业务处理方式。具体地，控制器201可以按照对应该FEC的报文需要执行的业务处理方式，为该FEC分配用于标识该业务 处理方式的业务标签，并建立该业务标签与该业务处理方式之间的映射关系。然后，控制器201可以将该业务标签下发到对应该FEC的源节点202，以便源节点202可以将该业务标签与该FEC保存，并且，控制器201可以将该映射关系下发到对应该FEC的目的节点203，以便目的节点203保存该映射关系。在源节点202保存有对应该FEC的业务标签的情况下，当接收到对应该FEC的第一报文时，源节点202可以将该业务标签插入到该第一报文中而得到第二报文，并向目的节点203发送该第二报文。当目的节点203接收到该第二报文时，目的节点203可以根据该映射关系识别出该第二报文中插入的该业务标签，并将该业务标签从该第二报文中弹出，得到第一报文，从而完成第一报文在网络环境中的转发过程。其中，在该第二报文从源节点202到目的节点203的转发过程中，需要对该第二报文进行业务处理的网络设备，通过读取该第二报文中的该业务标签，可以确定该第二报文对应的是该业务处理方式，从而可以按照该业务处理方式对该第二报文进行处理。
本实施例中，控制器201对于业务标签的下发动作和对于映射关系的下发动作，这两个下发动作之间可以是不限定执行顺序的。例如，控制器201可以同时向源节点202下发业务标签和向目的节点203下发映射关系。又如，控制器201还可以先向目的节点203下发映射关系而后向源节点202下发业务标签。
本实施例中的FEC，可以是采用任意一种方式对分组进行归类而形成的FEC。例如，FEC可以采用目的地址的IP地址前缀对分组进行归类，即，对应于同一FEC的报文具有相同IP地址前缀的目的地址。在这种情况下，在控制器201为FEC的业务处理方式分配业务标签时，控制器201可以将该业务标签与该IP地址前缀绑定向源节点202发送，源节点202可以将该业务标签与该IP地址前缀保存，这样，源节点202接收到报文时可以识别该报文的目的地址，如果识别出该报文的目的地址具有该IP地址前缀，源节点202可以在该报文中插入与该IP地址前缀对应保存的该业务标签。
在具体实施方式中，为了实现控制器201向源节点202下发对应FEC的业务标签，可以通过控制器201向源节点202下发对应该FEC的路由信 息来实现。具体地，所述控制器201将所述业务标签绑定在对应所述FEC的路由信息上；所述控制器201向所述源节点202发送所述路由信息。其中，在对应FEC的路由信息上绑定对应该FEC的业务标签，可以是通过扩展边界网关协议(Border Gateway Protocol，简称BGP)来实现的。具体地，对应该FEC的路由信息可以承载在BGP的网络层可达信息(Network Layer Reachability Information，简称NLRI)中，对应该FEC的业务标签可以作为BGP属性绑定在承载有该路由信息的NLRI中，这样，控制器201通过向源节点202下发该网络层可达信息，就可以实现向源节点202下发对应该FEC的路由信息及业务标签。
在具体实施方式中，为了实现控制器201向目的节点203下发业务标签与业务处理方式之间的映射关系，可以将该映射关系承载在BGP的NLRI中，通过控制器201向目的节点203下发该NLRI实现该映射关系的下发。具体地，所述控制器201将所述业务标签与所述业务处理方式插入对应所述FEC的NLRI中，以在所述NLRI中形成所述业务标签与所述业务处理方式之间的映射关系；所述控制器201向所述目的节点203发送所述NLRI。
为了实现在NLRI中承载所述映射关系，通过扩展BGP得到如图3所示的多协议可达NLRI(Multiprotocol Reachable NLRI，简称MP_Reach_NLRI)，该MP_Reach_NLRI即可用于承载所述映射关系。其中，
Address Family Identifier为地址族标识字段，该字段用于携带网络协议的地址族标识，如IPv4(Internet Protocol Version 4)的标识或IPv6(Internet Protocol Version 4)的标识；
Subsequent Address Family为子地址族标识字段，该字段用于携带NLRI类型的标志信息，对于表示NLRI承载有所述映射关系的NLRI类型，可以新增一个标志信息，该标志信息用于表示该NLRI包含有所述映射关系；
两个Reserved均为保留字段；
Network Address of Next Hop为下一跳网络地址字段，该字段用于携带路由的下一转发节点的地址；
Network Layer Reachability Information为网络层可达信息字段，对于承载有所述映射关系的NLRI来说，该字段可以用于携带该映射关系。
NLRI字段可以采用图4所示的格式来实现对所述映射关系的承载，其中，
NLRI Type为NLRI类型字段，该字段用于携带业务标签的类型，业务标签的类型可以用于表示该业务标签对应的业务处理方式，例如，业务标签的类型为Entropy label，即该业务标签属于熵标签，熵标签对应的业务处理方式可以是负载分担业务；
NLRI Length为NLRI长度字段，该字段用于携带表示NLRI字段长度的信息；
SID/Label/Index为业务标识字段，该字段可以用于携带业务识别码(Service Identifier，简称SID)、业务标签(Label)或索引(Index)；
Type Specific Value为类型具体值字段，该字段用于携带业务处理方式的描述信息。
可见，在图4所示的NLRI字段格式中，业务标签可以插入到SID/Label/Index字段，业务处理方式可以插入到Type Specific Value字段，因此即可实现MP_Reach_NLRI承载该业务标签与该业务处理方式之间的映射关系，而控制器201将该MP_Reach_NLRI下发到目的节点203，目的节点203读取到该MP_Reach_NLRI中具有该业务标签与该业务处理方式，就可以确定该业务标签是用于标识该业务处理方式的。
在具体实施方式中，，该业务处理方式可以包括：对报文进行负载分担处理、业务流的源识别处理或报文染色处理等。所述业务流的源识别处理主要用在三层虚拟专用网(Layer 3Virtual Protocol Network，简称L3VPN)等业务的操作、管理和维护(Operation Administration and Maintenance，简称OAM)过程中对业务流的源进行识别。所述染色处理，主要用于OAM过程对业务流进行染色。其中，分配给负载分担处理的业务标签属于熵标签(Entropy Label)，分配给源识别处理的业务标签属于源标签(Source Label)，分配给染色处理的业务标签属于染色标签(Color Label)。
对于需要从源节点202到目的节点203进行转发的报文来说，有些业 务处理可以是由控制器201执行，有些业务处理可以是由目的节点203执行，有些业务处理可以是由该报文转发路径上的中间节点执行。例如，中间节点负责对报文进行负载分担处理，由控制器201负责对报文进行源识别处理，目的节点203负责对报文进行染色处理。
在具体实施方式中，对于由中间节点执行的负载分担处理，为了实现负载分担处理这样一种业务处理方式，中间节点可以用于，按照预先设定的方式获得该第二报文的熵标签，并根据该熵标签对第二报文进行负载分担处理，其中，该熵标签为用于指示负载分担处理的业务标签，该第二报文可以是由源节点202将该熵标签作为内层标签插入到第一报文而形成的，即，该熵标签可以是第二报文的内层标签。考虑到中间节点通常仅负责负载分担处理这一种业务处理，中间节点可以无需识别各业务标签所表示的业务处理方式，而仅需要在第二报文中识别到该熵标签，因此，中间节点可以根据其自身预先设定的方式从第二报文中识别熵标签，而无需根据控制器建立的业务标签与业务处理方式之间的映射关系，因此，控制器201无需向中间节点下发业务标签与业务处理方式之间的映射关系。例如，中间节点自身的预先设定方式可以是将第二报文的标签栈中最后一个标签识别为熵标签，此时，源节点202可以按照中间节点的这种预先设定方式，将熵标签插入为第二报文的标签栈中最后一个标签。又如，中间节点自身的预先设定方式也可以是将第二报文中熵标签标识后面的标签识别为熵标签，此时，源节点202可以按照中间节点的这种预先设定方式，在将熵标签插入第一报文时，在标签栈中紧邻该熵标签之前插入熵标签标识。当然，控制器201也可以向中间节点下发业务标签与业务处理方式之间的映射关系，中间节点也可以是根据控制器下发的该映射关系从第二报文中识别熵标签，本实施例对此不作限定。
在具体实施方式中，对于由控制器201执行的业务处理方式的情况，控制器201可以基于所述映射关系，根据所述业务标签，确定所述第二报文对应所述业务处理方式，并按照所述业务处理方式对所述第二报文进行处理。具体地，在第二报文从源节点202到目的节点203的转发过程中，控制器201可以通过第二报文经过的某个或某些转发节点抓取到第二报文，以便对第二报文进行业务处理。考虑到控制器201通常要负责多种业 务处理方式，在这种情况下控制器201需要能够识别各业务标签所表示的业务处理方式，为此，控制器201在为业务处理方式分配业务标签时，可以将业务标签与业务处理方式之间的映射关系保存下来，当控制器201抓取到第二报文时，可以根据保存的映射关系确定第二报文中的业务标签所表示的业务处理方式，从而就可以按照确定出的业务处理方式对第二报文进行处理。
在具体实施方式中，对于由目的节点203执行的业务处理方式的情况，目的节点可以基于所述映射关系中的所述业务标签，确定所述第二报文对应所述业务处理方式，并按照所述业务处理方式对所述第二报文进行处理。考虑到目的节点通常要负责多种业务处理方式，在这种情况下目的节点203需要能够识别各业务标签所表示的业务处理方式，为此，对于控制器201向目的节点203下发的业务标签与业务处理方式之间的映射关系，目的节点可以将该映射关系保存下来，当目的节点203接收到第二报文时，根据该映射关系，一方面可以确定第二报文中的业务标签所表示的业务处理方式，从而可以按照确定出的业务处理方式对第二报文进行处理，另一方面可以识别出第二报文中的业务标签，从而将业务标签从第二报文中弹出，得到该第一报文，以便于目的节点203对报文的后续处理，例如，将得到的该第一报文继续沿着其他转发路径进行转发。
在具体实施方式中，网络设备可能对同一报文可以进行多种不同的业务处理方式，此时，控制器201可以为同一FEC的不同业务处理方式分配不同的业务标签，并可以将对应同一FEC的多个业务标签都下发到对应该FEC的源节点202，源节点202可以将对应该FEC的多个业务标签都插入到对应该FEC的报文中，从而使得网络中需要对该报文进行业务处理的网络设备，按照各个业务处理方式对报文进行处理。由此可见，在报文转发的过程中，通过在同一报文中插入多个业务标签，可以灵活地为报文选择业务处理方式的组合。例如，图5示出的报文标签示例中，在该报文中插入有熵标签、QoS标签、导向标签、VPN前缀标签、VPN标签、染色标签和源标签。
对于在同一报文中插入多个业务标签的情况，对应这些业务处理方式的处理可能由多个不同的网络设备执行。在这种情况下，每一个网络设备， 可以仅按照其自身负责的业务处理方式对该报文进行处理。当然，目的节点203除了按照其自身负责的业务处理方式对第二报文进行处理之外，还需要将第二报文中的所有业务标签弹出，从而得到第一报文，以便于后续对该第一报文的正常处理。作为一种示例，假设源节点201在第一报文中同时插入了第一业务标签、第二业务标签和第三业务标签而得到了第二报文，第一业务标签表示中间节点负责的第一业务处理方式，第二业务标签表示控制器201负责的第二业务处理方式，第三业务标签表示目的节点203负责的第三业务处理方式，那么，在第二报文从源节点202到目的节点203的转发过程中，中间节点可以识别出第二报文中的第一业务标签并按照第一业务处理方式对第二报文进行处理，控制器201可以识别出第二报文中的第二业务标签并按照第二业务处理方式对第二报文进行处理，目的节点203可以识别出第二报文中的第三业务标签并按照第三业务处理方式对第二报文进行处理，并且，目的节点203可以识别出第二报文中的全部三个业务标签，并将这三个业务标签从第二报文中弹出，从而得到第一报文，完成第一报文的转发过程。
在具体实施方式中，可以采用任意一种机制来转发具有业务标签的报文，如IP路由机制、MPLS转发机制、分段路由机制等。其中，在采用MPLS转发机制或分段路由机制时，报文是通过LSP标签来进行转发，此时，在报文转发的过程中，该报文的LSP标签与业务标签可以共同形成该报文的标签栈。具体地，所述控制器201还可以用于，向所述源节点202发送对应所述FEC的下一跳地址，以指示所述源节点202获取所述下一跳地址对应的LSP标签并按照所述LSP标签对所述第二报文进行转发处理。其中，在所述第二报文的标签栈中，所述LSP标签可以为外层标签，所述业务标签可以为内层标签。其中，对应所述FEC的下一跳地址表示对应所述FEC的目的节点的地址。
通过本实施例的技术方案，在转发节点支持MPLS的网络中，可以由控制器201为FEC的业务处理方式分配业务标签，并建立业务标签与业务处理方式之间的映射关系，一方面，该控制器201向对应该FEC的源节点202发送该业务标签，从而该源节点202可以在对应该该FEC的报文中插入该业务标签，另一方面，该控制器201可以向对应该FEC的目的节点 203发送的该映射关系，从而该目的节点203可以根据该映射关系从对应该FEC的报文中弹出该业务标签，其中，该业务标签即是用于标识该业务处理方式的指示信息，用于在该报文的转发过程中指示需要对该报文进行业务处理的网络设备按照该业务处理方式对该报文进行处理。由此可见，通过控制器201分配业务标签、向源节点202下发业务标签并向目的节点203下发业务标签与业务处理方式之间的映射关系，对于一FEC来说，对应该FEC的源节点202无需静态配置就可以实现在对应FEC的报文中插入对应该FEC的业务标签，对应该FEC的目的节点203无需静态配置就可以实现从对应该FEC的报文中弹出该业务标签，从而使得对应该FEC的报文能够在转发过程中具有对应该FEC的业务标签，以通过业务标签实现对报文的业务处理，因此，对于网络中的各FEC来说，仅需配置控制器201就可以实现对对应各FEC的报文进行业务处理，而无需静态配置对应各FEC的源节点202和目的节点203，这大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处理的工作。进一步而言，由于业务处理在网络中的配置和维护工作简化，各种业务处理方式可以较为容易地、灵活地配置给各FEC，从而使得网络环境中的各种业务处理能够灵活地实现。
参见图6，图6为本发明实施例提供的一种报文处理的方法流程示意图。所述方法包括：
步骤601、控制器为FEC的业务处理方式分配业务标签，并建立所述业务标签与所述业务处理方式之间的映射关系；
步骤602、所述控制器向对应所述FEC的源节点发送对应所述FEC的所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文；
步骤603、所述控制器向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；
其中，所述业务标签，用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按 照所述业务处理方式对所述第二报文进行处理。
本实施例中，步骤602和步骤603两者执行的先后顺序是不限定的。
可选的，步骤602可以包括：
所述控制器将所述业务标签绑定在对应所述FEC的路由信息上；所述控制器向所述源节点发送绑定有所述业务标签的所述路由信息，以指示所述源节点在所述第一报文中插入所述业务标签，得到所述第二报文。
可选的，步骤603例如可以包括：
所述控制器将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；所述控制器向所述目的节点发送所述网络层可达信息，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文。
可选的，本实施例还可以包括：所述控制器基于所述映射关系，根据所述业务标签，确定所述第二报文对应所述业务处理方式；所述控制器按照所述业务处理方式对所述第二报文进行处理，其中，所述业务处理方式不为负载分担处理。
可选的，本实施例还可以包括：所述控制器向所述源节点发送对应所述FEC的下一跳地址，以指示所述源节点获取所述下一跳地址对应的标签交换路径LSP标签并根据所述LSP标签对所述第二报文进行转发处理；其中，在所述第二报文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
需要说明的是，本发明实施例中的业务标签与业务处理方式之间的映射关系以及业务标签的内容，可以参见图2所示实施例。另外，本发明实施例中控制器执行方法步骤的各种具体实施方式，也可以参见图2所示实施例的详细介绍，此处不再赘述。
通过本实施例的技术方案，通过控制器分配业务标签、向源节点下发业务标签并向目的节点下发业务标签与业务处理方式之间的映射关系，对于网络中的各FEC来说，仅需配置控制器就可以实现对对应各FEC的报文进行业务处理，而无需静态配置对应各FEC的源节点和目的节点，这大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处 理的工作。
参见图7，图7为本发明实施例提供了另一种报文处理的方法流程示意图。所述方法包括：
步骤701、源节点接收控制器发送的对应FEC的业务标签，所述业务标签是所述控制器为所述FEC的业务处理方式分配的，所述源节点为对应所述FEC的源节点；
步骤702、所述源节点接收对应所述FEC的第一报文，在所述第一报文中插入所述业务标签，得到第二报文；
步骤703、所述源节点向对应所述FEC的目的节点发送所述第二报文，以指示对应所述FEC的目的节点根据所述业务标签与所述业务处理方式之间的映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；所述映射关系是所述控制器建立并发送给所述目的节点的；
其中，所述业务标签，用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，步骤701可以包括：所述源节点接收所述控制器发送的对应FEC的路由信息；所述源节点获取所述路由信息信息上绑定的所述业务标签。
可选的，本实施例还可以包括：所述源节点接收所述控制器发送的对应所述FEC的下一跳地址，并获取所述下一跳地址对应的标签交换路径LSP标签作为对应所述FEC的LSP标签；所述第二报文是根据所述LSP标签进行转发处理的；其中，在所述第二报文的标签栈中，所述隧道标签为外层标签，所述业务标签为内层标签。
需要说明的是，本发明实施例中的业务标签与业务处理方式之间的映射关系以及业务标签的内容，可以参见图2所示实施例。另外，本发明实施例中该源节点执行方法步骤的各种具体实施方式，可以参见图2所示实施例的详细介绍，本实施例在此不再赘述。
通过本实施例的技术方案，源节点从控制器接收对应FEC的业务处理方式的业务标签来，该业务标签是控制器为该FEC的业务处理方式分配 的，该源节点在对应该FEC的报文中插入该业务标签，因此，对于网络中的各FEC来说，无需静态配置对应各FEC的源节点就可以实现对应各FEC的报文进行业务处理，这大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处理的工作。
参见图8，图8为本发明实施例提供了又一种报文处理的方法流程示意图。所述方法包括：
步骤801、目的节点接收控制器发送的业务标签与业务处理方式之间的映射关系，所述业务标签是所述控制器为FEC的所述业务处理方式分配的，所述目的节点为对应所述FEC的目的节点；
步骤802、所述目的节点接收对应所述FEC的源节点发送的第二报文，所述第二报文是所述源节点在对应所述FEC的第一报文中插入所述业务标签而得到的；
步骤803、所述目的节点根据所述映射关系，从所述第二报文中弹出所述业务标签，得到所述第一报文；
其中，所述业务标签，用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，步骤801可以包括：所述目的节点接收所述控制器发送的对应所述FEC的网络层可达信息；所述目的节点从所述网络层可达信息中获取所述业务标签与所述业务处理方式，以得到所述业务标签与所述业务处理方式之间的映射关系。
可选的，本实施例还可以包括：所述目的节点基于所述映射关系，根据所述业务标签，确定所述第二报文对应所述业务处理方式；所述目的节点按照所述业务处理方式对所述第二报文进行处理。
需要说明的是，本发明实施例中的业务标签与业务处理方式之间的映射关系以及业务标签的内容，可以参见图2所示实施例。另外，本实发明施例中该目的节点执行方法步骤的各种具体实施方式，可以参见前述图2所示的系统实施例的详细介绍，本实施例在此不再赘述。
通过本实施例的技术方案，目的节点接收控制器发送的业务标签与该 业务处理方式之间的映射关系，该业务标签和该业务标签处理方式之间的对应关系为控制器预先建立的，该目的节点通过该映射关系可以从对应该FEC的报文中弹出该业务标签，对于网络中的各FEC来说，无需静态配置对应各FEC的目的节点就可以对对应各FEC的报文进行业务处理，这大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处理的工作。
为了使得本领域技术人员更清楚地理解本发明的具体应用方式，下面以一个示例性的应用场景对本发明实施例进行介绍。在该应用场景中，以网络环境中任意一个FEC作为目标FEC，控制器向对应目标FEC的源节点下发对应目标FEC的下一跳地址和业务标签，并向对应目标FEC的目的节点下发业务标签与业务处理方式之间的映射关系，以便在对应目标FEC的报文能够根据下一跳地址对应的LSP标签以及业务标签进行转发处理和业务处理。其中，该目标FEC对应的业务处理方式包括第一业务处理方式、第二业务处理方式和第三业务处理方式，第一业务处理方式由控制器负责，第二业务处理方式由对应目标FEC的中间节来负责，第三业务处理方式由对应目标FEC的目的节点负责。需要说明的是，该应用场景仅是本发明实施例的一个示例，本发明实施例不限定于该应用场景。
参见图9，图9为本发明实施例提供了又一报文处理的方法流程示意图。本发明实施例可以应用到上述示例性的应用场景，所述方法包括以下步骤：
步骤901、控制器为目标FEC的业务处理方式分配业务标签。
具体地，控制器可以为目标FEC的第一业务处理方式分配第一业务标签，可以为目标FEC的第二业务处理方式分配第二业务标签，并可以为目标FEC的第三业务处理方式分配第三业务标签。
步骤902、控制器建立业务标签与业务处理方式之间的映射关系。
具体地，控制器可以建立第一业务标签与第一业务处理之间的映射关系作为第一映射关系，可以建立第二业务标签与第二业务处理之间的映射关系作为第二映射关系，并可以建立第三业务标签与第三业务处理之间的映射关系作为第三映射关系。
步骤903、控制器根据对应目标FEC的下一跳地址和业务标签生成对应目标FEC的第一NLRI并向对应目标FEC的源节点下发。
具体地，下一跳地址可以作为对应目标FEC的路由信息插入到第一网络层可达信息的NLRI字段，第一业务标签、第二业务标签和第三业务标签可以作为BGP属性绑定在第一NLRI上。其中，下一跳地址对应目标FEC的目的节点的地址。
步骤904、源节点根据下一跳地址查找LSP标签，并将LSP标签和业务标签均与目标FEC对应保存。
其中，源节点对应目标FEC保存的标签包括LSP标签、第一业务标签、第二业务标签和第三业务标签。
步骤905、控制器根据业务标签与业务处理方式之间的映射关系生成第二NLRI并向对应目标FEC的目的节点下发。
具体地，控制器可以对应前述三个映射关系形成三个第二NLRI息并均下发给目的节点。在一个第二NLRI中，SID/Label/Index字段插入有第一业务标签，Type Specific Value字段插入有第一业务处理方式。在另一个第二NLRI中，SID/Label/Index字段插入有第二业务标签，Type Specific Value字段插入有第二业务处理方式。在又一个第二NLRI中，SID/Label/Index字段插入有第三业务标签，Type Specific Value字段插入有第三业务处理方式。
步骤906、目的节点保存接收到的映射关系。
其中，目的节点保存的映射关系包括前述的第一映射关系、第二映射关系和第三映射关系。
步骤907、当源节点接收到对应目标FEC的第一报文时，在第一报文中插入LSP标签和业务标签而得到第二报文。
具体地，在第二报文的标签栈中包括有LSP标签、第一业务标签、第二业务标签和第三业务标签。其中，LSP标签为外层标签，第一业务标签、第二业务标签和第三业务标签为内层标签。
步骤908、源节点根据LSP标签对第二报文进行转发处理。
步骤909、当中间节点接收到第二报文时，控制器通过中间节点抓取第二报文。
其中，中间节点可以是第二报文的转发路径上的任意一个中间节点。
此外，当中间节点接收到第二报文时，一方面中间节点可以响应于控制器的抓取向控制器发送该第二报文，即执行本步骤909，另一方面中间节点可以识别第二报文中的业务标签对第二报文进行业务处理，即执行后续的步骤911。
步骤910、控制器根据映射关系识别第二报文中的业务标签，并响应于识别到第一业务标签，按照第一业务处理方式对第二报文进行处理。
其中，控制器可以根据预先建立的第一映射关系，可以识别出第二报文中的第一业务标签并确定第一业务标签表示的是第一业务处理方式，从而就可以按照第一业务处理方式对第二报文进行处理。
可以理解的是，除了第一业务标签之外，控制器也可以根据预先建立的第二映射关系和第三映射关系识别出第二报文中的第二业务标签和第三业务标签，但是，第二业务标签所表示的第二业务处理方式和第三业务标签所表示的业务处理方式均不需要由控制器来执行，因此，控制器可以无需响应第二业务标签和第三业务标签的指示执行动作。
步骤911、当中间节点接收到第二报文时，中间节点根据固定配置识别第二报文中的第二业务标签并按照第二业务标签所表示的第二业务处理方式对第二报文进行处理。
具体地，第二业务处理方式为负载分担处理，第二业务标签为熵标签。中间节点根据固定配置可以从第二报文中查找到熵标签，然后，中间节点可以处理熵标签并按照熵标签的处理结果对第二报文进行负载分担处理。
步骤912、中间节点根据LSP标签对第二报文进行转发处理。
步骤913、目的节点接收第二报文，并根据映射关系识别第二报文中的业务标签。
具体地，目的节点根据预先保存的第一映射关系、第二映射关系和第三映关系，可以从第二报文中识别出第一业务标签、第二业务标签和第三业务标签。
步骤914、目的节点按照第三业务处理方式对第二报文进行处理。
具体地，目的节点可以根据预先建立的第三映射关系确定第三业务标签表示的是第三业务处理方式，从而就可以按照第三业务处理方式对第二 报文进行处理。
步骤915、目的节点从第二报文中弹出业务标签，得到第一报文。
具体地，目的节点将第二报文中的所有业务标签都从第二报文中弹出，也即，目的节点将第二报文中的第一业务标签、第二业务标签和第三业务标签都从第二报文中弹出。
通过本实施例的技术方案，对于网络环境中的各FEC来说，仅需配置控制器就可以实现对对应各FEC的报文进行业务处理，而无需静态配置对应各FEC的源节点和目的节点，这大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处理的工作。进一步而言，由于业务处理在网络环境中的配置和维护工作十分简便，各种业务处理方式可以较为容易地、灵活地配置给各FEC，从而使得网络环境中的各种业务处理能够灵活地实现。
参见图10，图10为本发明实施例提供了一种控制器的结构示意图。所述控制器1000包括：
分配模块1001，用于为FEC的业务处理方式分配业务标签；
建立模块1002，用于建立所述业务标签与所述业务处理方式之间的映射关系；
第一发送模块1003，用于向对应所述FEC的源节点发送对应所述FEC所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文；
第二发送模块1004，用于向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
具体实现时，在控制器1000中，针对FEC的业务处理方式，分配模块1001可以为其分配业务标签，建立模块1002可以建立分配模块1001分配的业务标签与其业务处理方式之间的映射关系，第一发送模块1003 可以将分配模块1001分配的业务标签向源节点下发，第二发送模块1004可以将建立模块1002建立的映射关系向目的节点下发。
可选的，第一发送模块1003可以包括绑定子模块和第一发送子模块；其中，绑定子模块，用于将所述业务标签绑定在对应所述FEC的路由信息上；第一发送子模块，用于向所述源节点发送绑定有所述业务标签的所述路由信息，以指示所述源节点在所述第一报文中插入所述业务标签，得到所述第二报文。
可选的，第二发送模块1004可以包括插入子模块和第二发送子模块；其中，插入子模块，用于将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；第二发送子模块，用于向所述目的节点发送所述网络层可达信息，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文。
可选的，控制器1000还可以包括确定模块和业务处理模块；其中，确定模块，用于基于所述映射关系，根据所述业务标签，确定所述第二报文对应所述业务处理方式；业务处理模块，用于按照所述业务处理方式对所述第二报文进行处理。
可选的，控制器1000还可以包括：第三发送模块，用于向所述源节点发送对应所述FEC的下一跳地址，以指示所述源节点获取所述下一跳地址对应的标签交换路径LSP标签并根据所述LSP标签对所述第二报文进行转发处理；其中，在所述第二报文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
需要说明的是，本实施例中控制器1000对应于前述图2所示的实施例中的控制器201。本实施例中控制器1000的各种具体实施方式，可以参见前述图2所示的实施例的详细介绍，本实施例在此不再赘述。
通过本实施例的技术方案，通过控制器1000分配业务标签、向源节点下发业务标签并向目的节点下发业务标签与业务处理方式之间的映射关系，对于网络中的各FEC来说，仅需配置控制器1000就可以实现对对应各FEC的报文进行业务处理，而无需静态配置对应各FEC的源节点和目的节点，这大大减少了需要静态配置的设备数量，简化了为网络环境配 置和维护业务处理的工作。
参见图11，图11为本发明实施例提供了一种源节点设备1100的结构示意图。所述源节点设备1100包括：
第一接收模块1101，用于接收控制器发送的对应FEC的业务标签，所述业务标签是所述控制器为所述FEC的业务处理分配的，所述源节点为对应所述FEC的源节点；
第二接收模块1102，用于接收对应所述FEC的第一报文；
插入模块1103，用于在所述第一报文中插入所述业务标签，得到第二报文；
第一发送模块1104，用于向对应所述FEC的目的节点发送所述第二报文，以指示对应所述FEC的目的节点根据所述业务标签与所述业务处理方式之间的映射关系从所述第二报文中弹出所述业务标签，得到第一报文；所述映射关系是所述控制器建立并发送给所述目的节点的；
其中，所述业务标签用于在所述第二报文从所述源节点1100到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
具体实现时，在源节点设备1100中，第一接收模块1101可以从控制器接收到对应FEC的业务标签，第二接收模块1102可以接收到对应该FEC的第一报文，第一插入模块1103可以在第二接收模块1102接收到的第一报文中插入第一接收模块1101接收到的业务标签而得到第二报文，第一发送模块1104可以向对应该FEC的目的节点发送插入模块1103得到的第二报文。
可选的，第一接收模块1101例如可以包括第一接收子模块和第一获取子模块，其中，第一接收子模块，用于接收所述控制器发送的对应FEC的路由信息；第一获取子模块，用于获取所述信息上绑定的所述业务标签。
可选的，源节点设备1100还可以包括：第三接收模块，用于接收所述控制器发送的对应所述FEC的下一跳地址；获取模块，用于获取所述下一跳地址对应的标签交换路径LSP标签作为对应所述FEC的LSP标签；所述第二报文是根据所述LSP标签进行转发处理的；其中，在所述第二报 文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
需要说明的是，本实施例中源节点设备1100对应于前述图2所示的实施例中的源节点202。本实施例中源节点设备1100的各种具体实施方式，可以参见前述图2所示的实施例的详细介绍，本实施例在此不再赘述。
通过本实施例的技术方案，源节点设备1100可以通过从控制器接收业务标签来实现在报文中插入业务标签，对于网络中的各FEC来说，无需静态配置对应各FEC的源节点设备1100就可以实现对应各FEC的报文进行业务处理，这大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处理的工作。
参见图12，图12为本发明提供了一种目的节点设备1200的结构示意图。所述设备1200包括：
第一接收模块1201，用于接收控制器发送的业务标签与业务处理方式之间的映射关系，所述业务标签是所述控制器为转发等价类FEC的所述业务处理方式分配的，所述目的节点为对应所述FEC的目的节点；
第二接收模块1202，用于接收对应所述FEC的源节点发送的第二报文，所述第二报文是所述源节点在对应所述FEC的第一报文中插入所述业务标签而得到的；
弹出模块1203，用于根据所述映射关系，从所述第二报文中弹出所述业务标签，得到第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
具体实现时，在目的节点设备1200中，第一接收模块1201可以从控制器接收到业务标签与业务处理方式之间的映射关系，第二接收模块1202可以接收到插入有该业务标签的第二报文，弹出模块1203可以根据第一接收模块1201接收到的映射关系，从第二接收模块1202接收到的第二报文中识别出该业务标签并从第二报文中弹出该业务标签。
可选的，第一接收模块1201可以包括第二接收子模块和第二获取子模块；其中，第二接收子模块，用于接收所述控制器发送的对应所述FEC 的网络层可达信息；第二获取子模块，用于从所述第二网络层可达信息中获取所述业务标签与所述业务处理方式，以得到所述业务标签与所述业务处理方式之间的映射关系。
可选的，目的节点设备1200还可以包括确定模块和业务处理模块；其中，确定模块，用于基于所述映射关系，根据所述业务标签，确定所述第二报文对应所述业务处理方式；业务处理模块，用于按照所述业务处理方式对所述第二报文进行处理。
需要说明的是，本实施例中目的节点设备1200对应于前述图2所示的实施例中的目的节点203。本实施例中目的节点设备1200的各种具体实施方式，可以参见前述图2所示的实施例的详细介绍，本实施例在此不再赘述。
通过本实施例的技术方案，目的节点设备1200可以通过从控制器接收业务标签与业务处理方式之间的映射关系来实现从报文中弹出业务标签，对于网络中的各FEC来说，无需静态配置对应各FEC的目的节点设备1200就可以对对应各FEC的报文进行业务处理，这大大减少了需要静态配置的设备数量，简化了为网络环境配置和维护业务处理的工作。
参见图13，图13为本发明实施例中一种控制器的结构示意图。在本实施例中，控制器1300包括：处理器1301、存储器1302、网络接口1303、总线系统1304。
所述总线系统1304，用于将控制器1300的各个硬件组件耦合在一起。
所述网络接口1303，用于实现控制器1300与至少一个其它网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等方式。
所述存储器1302，用于存储程序指令和数据。
所述处理器1301，用于读取存储器1302中存储的指令和数据，执行以下操作：
所述处理器1301为转发等价类FEC的业务处理方式分配业务标签，并建立所述业务标签与所述业务处理方式之间的映射关系；
所述处理器1301向对应所述FEC的源节点发送对应所述FEC的所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务 标签，得到第二报文；
所述处理器1301向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述处理器1301为了实现向对应所述FEC的源节点发送对应所述FEC的所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文，例如可以执行以下操作：
所述处理器1301将所述业务标签绑定在对应所述FEC的路由信息上；
所述处理器1301向所述源节点发送绑定有所述业务标签的所述路由信息，以指示所述源节点在所述第一报文中插入所述业务标签，得到所述第二报文。
可选的，所述处理器1301为了实现向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文，例如可以执行以下操作：
所述处理器1301将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；
所述处理器1301向所述目的节点发送所述网络层可达信息，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文。
可选的，所述处理器1301例如还可以执行以下操作：
所述处理器1301基于所述映射关系，根据所述业务标签，确定所述第二报文对应所述业务处理方式；
所述处理器1301按照所述业务处理方式对所述第二报文进行处理；
其中，所述业务处理不为对所述报文进行负载分担处理，所述网络设备为所述控制器。
可选的，所述处理器1301例如还可以执行以下操作：
所述处理器1301向所述源节点发送对应所述FEC的标签交换路径LSP标签，以指示所述源节点根据所述LSP标签对所述第二报文进行转发处理；
其中，在所述第二报文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
需要说明的是，本实施例中控制器1300对应于前述图2所示的实施例中的控制器201。本实施例中控制器1300的各种具体实施方式，可以参见前述图2所示的实施例的详细介绍，本实施例在此不再赘述。
参见图14，图14为本发明实施例提供了一种源节点设备的结构示意图。在本实施例中所述源节点设备1400例如可以包括：处理器1401、存储器1402、网络接口1403、总线系统1404。
所述总线系统1404，用于将转发节点1400的各个硬件组件耦合在一起。
所述网络接口1403，用于实现转发节点1400与至少一个其它网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等方式。
所述存储器1402，用于存储程序指令和数据。
所述处理器1401，用于读取存储器1402中存储的指令和数据，执行以下操作：
所述处理器1401接收控制器发送的对应转发等价类FEC的业务标签，所述业务标签是所述控制器为所述FEC的业务处理方式分配的，所述源节点设备1400为对应所述FEC的源节点；
所述处理器1401接收对应所述FEC的第一报文，在所述第一报文中插入所述业务标签，得到第二报文；
所述处理器1401向对应所述FEC的目的节点发送所述第二报文，以指示对应所述FEC的目的节点根据所述业务标签与所述业务处理方式之间的映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；所述映射关系是所述控制器建立并发送给所述目的节点的；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述处理器1401为了实现接收控制器发送的对应FEC的业务标签，例如可以执行以下操作：
所述处理器1401接收所述控制器发送的对应FEC的路由信息；
所述处理器1401获取所述路由信息信息上绑定的所述业务标签。
可选的，所述处理器1401例如还可以执行以下操作：
所述处理器1401接收所述控制器发送的对应所述FEC的标签交换路径LSP标签；
所述第二报文是根据所述LSP标签进行转发处理的；
其中，在所述第二报文的标签栈中，所述隧道标签为外层标签，所述业务标签为内层标签。
需要说明的是，本实施例中源节点设备1400对应于前述图2所示的实施例中的源节点202。本实施例中源节点设备1400的各种具体实施方式，可以参见前述图2所示的实施例的详细介绍，本实施例在此不再赘述。
参见图15，本发明实施例提供了一种目的节点设备的结构示意图。本实施例中，所述目的节点设备1500例如可以包括：处理器1501、存储器1502、网络接口1503、总线系统1504。
所述总线系统1504，用于将转发节点1500的各个硬件组件耦合在一起。
所述网络接口1503，用于实现转发节点1500与至少一个其它网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等方式。
所述存储器1502，用于存储程序指令和数据。
所述处理器1501，用于读取存储器1502中存储的指令和数据，执行以下操作：
所述处理器1501接收控制器发送的业务标签与业务处理方式之间的映射关系，所述业务标签是所述控制器为转发等价类FEC的所述业务处理方式分配的，所述目的节点设备1500为对应所述FEC的目的节点；
所述处理器1501接收对应所述FEC的源节点发送的第二报文，所述第二报文是所述源节点在对应所述FEC的第一报文中插入所述业务标签而得到的；
所述处理器1501根据所述映射关系，从所述第二报文中弹出所述业 务标签，得到所述第一报文；
其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
可选的，所述处理器1501为了实现接收业务标签与业务处理方式之间的映射关系，例如可以执行以下操作：
所述处理器1501接收所述控制器发送的对应所述FEC的网络层可达信息；
所述处理器1501从所述网络层可达信息中获取所述业务标签与所述业务处理方式，以得到所述业务标签与所述业务处理方式之间的映射关系。
可选的，所述处理器1501例如还可以执行以下操作：
所述处理器1501基于所述映射关系，根据所述业务标签，确定所述第二报文对应所述业务处理方式；
所述处理器1501按照所述业务处理方式对所述第二报文进行处理；
其中，所述业务处理方式不为对报文进行负载分担处理，所述网络设备为所述目的节点。
需要说明的是，本实施例中目的节点设备1500对应于前述图2所示的实施例中的目的节点203。本实施例中目的节点设备1500的各种具体实施方式，可以参见前述图2所示的实施例的详细介绍，本实施例在此不再赘述。
本发明实施例中提到的第一报文和第一发送模块中的“第一”只是用来做名字标识，并不代表顺序上的第一。该规则同样适用于“第二”、“第三”和“第四”。
需要说明的是，本发明实施例中的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。这些指令可以通过其中的处理器以配合实现及控制，用于执行本发明实施例揭示的方法。上述处理器还可以是通用处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(application specific integrated circuit)、现成可编 程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
其中，上述通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器，解码器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。
另外，需要说明的是，总线系统除了包括数据总线之外，还可包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图8、9中将各种总线都标为总线系统。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到上述实施例方法中的全部或部分步骤可借助软件加通用硬件平台的方式来实现。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者诸如媒体网关等网络通信设备)执行本发明各个实施例或者实施例的某些部分所述的方法。
需要说明的是，本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于方法实施例和设备实施例而言，由于其基本相似于系统实施例，所以描述得比较简单，相关之处参见系统实施例的部分说明即可。以上所描述的设备及系统实施例仅仅是示意性的，其中作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅是本发明的优选实施方式，并非用于限定本发明的保护范围。应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本发明的保护范围。

Claims (23)

  1. 一种报文处理的系统，其特征在于，所述系统包括：
    控制器，用于为转发等价类FEC的业务处理方式分配业务标签，建立所述业务标签与所述业务处理方式之间的映射关系，向对应所述FEC的源节点发送所述业务标签，并向对应所述FEC的目的节点发送所述映射关系；
    所述源节点，用于接收所述控制器发送的对应所述FEC的所述业务标签，接收对应所述FEC的第一报文，并在所述第一报文中插入所述业务标签而得到第二报文，向对应所述FEC的目的节点发送所述第二报文；
    所述目的节点，用于接收所述控制器发送的所述映射关系，接收对应所述FEC的源节点发送的第二报文，并根据所述映射关系从所述第二报文中弹出所述业务标签而得到所述第一报文；
    其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
  2. 根据权利要求1所述的系统，其特征在于，所述控制器向所述源节点发送所述业务标签，包括：
    所述控制器将所述业务标签绑定在对应所述FEC的路由信息上；
    所述控制器向所述源节点发送绑定有所述业务标签的所述路由信息。
  3. 根据权利要求1所述的系统，其特征在于，所述控制器向所述目的节点发送所述映射关系，包括：
    所述控制器将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；
    向所述目的节点发送所述网络层可达信息。
  4. 根据权利要求1所述的系统，其特征在于，所述业务处理方式为对报文进行负载分担处理，所述网络设备为从所述源节点到所述目的节点的转发路径 上的中间节点，所述业务标签为所述第二报文的标签栈中的内层标签。
  5. 根据权利要求1～4任意一项所述的系统，其特征在于，
    所述控制器，还用于向所述源节点发送对应所述FEC的下一跳地址，以指示所述源节点获取所述下一跳地址对应的标签交换路径LSP标签并按照所述LSP标签对所述第二报文进行转发处理；
    其中，在所述第二报文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
  6. 一种报文处理的方法，其特征在于，所述方法包括：
    控制器为转发等价类FEC的业务处理方式分配业务标签，并建立所述业务标签与所述业务处理方式之间的映射关系；
    所述控制器向对应所述FEC的源节点发送对应所述FEC的所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文；
    所述控制器向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；
    其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
  7. 根据权利要求6所述的方法，其特征在于，
    所述控制器向对应所述FEC的源节点发送对应所述FEC的所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文，包括：
    所述控制器将所述业务标签绑定在对应所述FEC的路由信息上；
    所述控制器向所述源节点发送绑定有所述业务标签的所述路由信息，以指示所述源节点在所述第一报文中插入所述业务标签，得到所述第二报文。
  8. 根据权利要求6所述的方法，其特征在于，
    所述控制器向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文，包括：
    所述控制器将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；
    所述控制器向所述目的节点发送所述网络层可达信息，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文。
  9. 根据权利要求6～8任意一项所述的方法，其特征在于，还包括：
    所述控制器向所述源节点发送对应所述FEC的下一跳地址，以指示所述源节点获取所述下一跳地址对应的标签交换路径LSP标签并根据所述LSP标签对所述第二报文进行转发处理；
    其中，在所述第二报文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
  10. 一种报文处理的方法，其特征在于，所述方法包括：
    源节点接收控制器发送的对应转发等价类FEC的业务标签，所述业务标签是所述控制器为所述FEC的业务处理方式分配的，所述源节点为对应所述FEC的源节点；
    所述源节点接收对应所述FEC的第一报文，在所述第一报文中插入所述业务标签，得到第二报文；
    所述源节点向对应所述FEC的目的节点发送所述第二报文，以指示对应所述FEC的目的节点根据所述业务标签与所述业务处理方式之间的映射关系从所述第二报文中弹出所述业务标签，得到所述第一报文；所述映射关系是所述控制器建立并发送给所述目的节点的；
    其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
  11. 根据权利要求10所述的方法，其特征在于，所述源节点接收控制器发送的对应FEC的业务标签，包括：
    所述源节点接收所述控制器发送的对应FEC的路由信息；
    所述源节点获取所述路由信息信息上绑定的所述业务标签。
  12. 根据权利要求10或11所述的方法，其特征在于，还包括：
    所述源节点接收所述控制器发送的对应所述FEC的下一跳地址，并获取所述下一跳地址对应的标签交换路径LSP标签作为对应所述FEC的LSP标签；
    所述第二报文是根据所述LSP标签进行转发处理的；
    其中，在所述第二报文的标签栈中，所述隧道标签为外层标签，所述业务标签为内层标签。
  13. 一种报文处理的方法，其特征在于，所述方法包括：
    目的节点接收控制器发送的业务标签与业务处理方式之间的映射关系，所述业务标签是所述控制器为转发等价类FEC的所述业务处理方式分配的，所述目的节点为对应所述FEC的目的节点；
    所述目的节点接收对应所述FEC的源节点发送的第二报文，所述第二报文是所述源节点在对应所述FEC的第一报文中插入所述业务标签而得到的；
    所述目的节点所述目的节点根据所述映射关系，从所述第二报文中弹出所述业务标签，得到所述第一报文；
    其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
  14. 根据权利要求13所述的方法，其特征在于，所述目的节点接收业务标签与业务处理方式之间的映射关系，包括：
    所述目的节点接收所述控制器发送的对应所述FEC的网络层可达信息；
    所述目的节点从所述网络层可达信息中获取所述业务标签与所述业务处理方式，以得到所述业务标签与所述业务处理方式之间的映射关系。
  15. 一种控制器，其特征在于，所述控制器包括：
    分配模块，用于为转发等价类FEC的业务处理方式分配业务标签；
    建立模块，用于建立所述业务标签与所述业务处理方式之间的映射关系；
    第一发送模块，用于向对应所述FEC的源节点发送对应所述FEC所述业务标签，以指示所述源节点在对应所述FEC的第一报文中插入所述业务标签，得到第二报文；
    第二发送模块，用于向对应所述FEC的目的节点发送所述映射关系，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文；
    其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
  16. 根据权利要求14所述的控制器，其特征在于，所述第一发送模块包括：
    绑定子模块，用于将所述业务标签绑定在对应所述FEC的路由信息上；
    第一发送子模块，用于向所述源节点发送绑定有所述业务标签的所述路由信息，以指示所述源节点在所述第一报文中插入所述业务标签，得到所述第二报文。
  17. 根据权利要求15所述的控制器，其特征在于，所述第二发送模块包括：
    插入子模块，用于将所述业务标签与所述业务处理方式插入对应所述FEC的网络层可达信息中，以在所述网络层可达信息中形成所述业务标签与所述业务处理方式之间的映射关系；
    第二发送子模块，用于向所述目的节点发送所述网络层可达信息，以指示所述目的节点根据所述映射关系从所述第二报文中弹出所述业务标签，得到第一报文。
  18. 根据权利要求15～17任意一项所述的控制器，其特征在于，还包括：
    第三发送模块，用于向所述源节点发送对应所述FEC的下一跳地址，以指示所述源节点获取所述下一跳地址对应的标签交换路径LSP标签并根据所述 LSP标签对所述第二报文进行转发处理；
    其中，在所述第二报文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
  19. 一种源节点设备，其特征在于，所述设备包括：
    第一接收模块，用于接收控制器发送的对应转发等价类FEC的业务标签，所述业务标签是所述控制器为所述FEC的业务处理分配的，所述源节点为对应所述FEC的源节点；
    第二接收模块，用于接收对应所述FEC的第一报文；
    插入模块，用于在所述第一报文中插入所述业务标签，得到第二报文；
    第一发送模块，用于向对应所述FEC的目的节点发送所述第二报文，以指示对应所述FEC的目的节点根据所述业务标签与所述业务处理方式之间的映射关系从所述第二报文中弹出所述业务标签，得到第一报文；所述映射关系是所述控制器建立并发送给所述目的节点的；
    其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
  20. 根据权利要求19所述的设备，其特征在于，所述第一接收模块包括：
    第一接收子模块，用于接收所述控制器发送的对应FEC的路由信息；
    第一获取子模块，用于获取所述路由信息上绑定的所述业务标签。
  21. 根据权利要求19或20所述的设备，其特征在于，还包括：
    第三接收模块，用于接收所述控制器发送的对应所述FEC的下一跳地址；
    获取模块，用于获取所述下一跳地址对应的标签交换路径LSP标签作为对应所述FEC的LSP标签；
    所述第二报文是根据所述LSP标签进行转发处理的；
    其中，在所述第二报文的标签栈中，所述LSP标签为外层标签，所述业务标签为内层标签。
  22. 一种目的节点设备，其特征在于，所述设备包括：
    第一接收模块，用于接收控制器发送的业务标签与业务处理方式之间的映射关系，所述业务标签是所述控制器为转发等价类FEC的所述业务处理方式分配的，所述目的节点为对应所述FEC的目的节点；
    第二接收模块，用于接收对应所述FEC的源节点发送的第二报文，所述第二报文是所述源节点在对应所述FEC的第一报文中插入所述业务标签而得到的；
    弹出模块，用于根据所述映射关系，从所述第二报文中弹出所述业务标签，得到第一报文；
    其中，所述业务标签用于在所述第二报文从所述源节点到所述目的节点的转发过程中，指示需要对所述第二报文进行业务处理的网络设备按照所述业务处理方式对所述第二报文进行处理。
  23. 根据权利要求22所述设备，其特征在于，所述第一接收模块包括：
    第一接收子模块，用于接收所述控制器发送的对应所述FEC的网络层可达信息；
    第一获取子模块，用于从所述第二网络层可达信息中获取所述业务标签与所述业务处理方式，已得到所述业务标签与所述业务处理方式之间的映射关系。
PCT/CN2016/096572 2015-09-22 2016-08-24 一种报文处理的方法、设备和系统 WO2017050085A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP16847967.3A EP3343846B1 (en) 2015-09-22 2016-08-24 Method, device and system for processing packet
ES16847967T ES2793312T3 (es) 2015-09-22 2016-08-24 Método, dispositivo y sistema de procesamiento de paquetes
US15/926,872 US10680942B2 (en) 2015-09-22 2018-03-20 Packet processing method, device, and system
US16/879,100 US11218408B2 (en) 2015-09-22 2020-05-20 Packet processing method, device, and system
US17/536,507 US11909633B2 (en) 2015-09-22 2021-11-29 Packet processing method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510608874.X 2015-09-22
CN201510608874.XA CN106549871B (zh) 2015-09-22 2015-09-22 一种报文处理的方法、设备和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/926,872 Continuation US10680942B2 (en) 2015-09-22 2018-03-20 Packet processing method, device, and system

Publications (1)

Publication Number Publication Date
WO2017050085A1 true WO2017050085A1 (zh) 2017-03-30

Family

ID=58364215

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/096572 WO2017050085A1 (zh) 2015-09-22 2016-08-24 一种报文处理的方法、设备和系统

Country Status (5)

Country Link
US (3) US10680942B2 (zh)
EP (1) EP3343846B1 (zh)
CN (2) CN106549871B (zh)
ES (1) ES2793312T3 (zh)
WO (1) WO2017050085A1 (zh)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106549871B (zh) * 2015-09-22 2020-09-08 华为技术有限公司 一种报文处理的方法、设备和系统
CN106936713B (zh) 2015-12-30 2020-02-21 华为技术有限公司 一种标签管理方法，数据流处理方法及设备
CN113839871A (zh) 2017-09-25 2021-12-24 华为技术有限公司 一种报文转发的方法及网络设备
CN109861924B (zh) * 2017-11-30 2022-06-21 中兴通讯股份有限公司 报文的发送、处理方法及装置，pe节点，节点
CN110224935B (zh) 2018-03-02 2020-10-23 华为技术有限公司 一种处理组播数据报文的方法及装置
CN112491687B (zh) * 2018-03-29 2022-04-12 华为技术有限公司 一种处理报文的方法及装置
CN110855459B (zh) * 2018-08-20 2021-07-09 华为技术有限公司 网络配置方法、装置及系统
CN110086718A (zh) * 2019-05-13 2019-08-02 和记奥普泰通信技术有限公司 一种基于分组化mpls的vll快速实现方法
CN112152924A (zh) * 2019-06-29 2020-12-29 华为技术有限公司 一种在数据中心网络中转发报文的方法及相关装置
CN112217724A (zh) * 2019-07-11 2021-01-12 中兴通讯股份有限公司 路由管理方法、装置、网络设备和可读存储介质
CN112468396B (zh) * 2019-09-06 2022-05-31 华为技术有限公司 主机网络性能需求可编程化的方法、设备和系统
CN110932895B (zh) * 2019-11-26 2022-07-15 中国联合网络通信集团有限公司 一种网络切片的报文转发方法和装置
CN116113006A (zh) * 2021-11-10 2023-05-12 华为技术有限公司 一种处理报文的系统、方法和网络装置
CN116805930A (zh) * 2022-03-16 2023-09-26 中兴通讯股份有限公司 Bgp路由的发送方法、装置、存储介质及电子装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090122801A1 (en) * 2006-06-16 2009-05-14 Huawei Technologies Co., Ltd. Ethernet switching and forwarding method, system and apparatus
CN102143030A (zh) * 2011-01-07 2011-08-03 华为数字技术有限公司 一种发送转发信息的方法及设备
WO2013185715A1 (zh) * 2012-09-18 2013-12-19 中兴通讯股份有限公司 一种实现虚拟网络的方法和虚拟网络
CN104243362A (zh) * 2013-06-24 2014-12-24 杭州华三通信技术有限公司 一种报文转发方法和装置

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7359377B1 (en) * 2001-06-19 2008-04-15 Juniper Networks, Inc. Graceful restart for use in nodes employing label switched path signaling protocols
US7463591B1 (en) * 2001-06-25 2008-12-09 Juniper Networks, Inc. Detecting data plane liveliness of a label-switched path
US7702810B1 (en) * 2003-02-03 2010-04-20 Juniper Networks, Inc. Detecting a label-switched path outage using adjacency information
US7397795B2 (en) * 2003-02-24 2008-07-08 Intel California Method and system for label-based packet forwarding among multiple forwarding elements
US7174427B2 (en) * 2003-12-05 2007-02-06 Intel Corporation Device and method for handling MPLS labels
CN100334857C (zh) * 2004-09-27 2007-08-29 华为技术有限公司 一种环网及其业务实现方法
US7639674B2 (en) * 2004-10-25 2009-12-29 Alcatel Lucent Internal load balancing in a data switch using distributed network processing
CN101741709B (zh) * 2008-11-06 2012-08-22 华为技术有限公司 建立标签交换路径的方法、系统及网络节点
US9246801B1 (en) * 2008-12-12 2016-01-26 Juniper Networks, Inc. Transmitting packet label contexts within computer networks
US7948986B1 (en) * 2009-02-02 2011-05-24 Juniper Networks, Inc. Applying services within MPLS networks
US8902766B2 (en) * 2010-09-20 2014-12-02 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus to improve LDP convergence using hierarchical label stacking
WO2012145886A1 (zh) * 2011-04-25 2012-11-01 华为技术有限公司 一种基于标签的测量方法，装置和系统
WO2012106919A1 (zh) 2011-07-22 2012-08-16 华为技术有限公司 一种三层虚拟专有网路由控制方法、装置及系统
US9049142B1 (en) * 2011-09-20 2015-06-02 Cisco Technology, Inc. Method and apparatus to enable protection for selective traffic in an MPLS network
US9300584B1 (en) * 2012-03-27 2016-03-29 Cisco Technology, Inc. Expanded quality of service processing of multiprotocol label switching (MPLS) packets
KR20130126822A (ko) * 2012-04-27 2013-11-21 한국전자통신연구원 다중 프로토콜 레이블 스위칭-전송 프로파일 네트워크에서의 패킷 처리방법 및 그 장치
US9088519B2 (en) * 2012-06-15 2015-07-21 Juniper Networks, Inc. Allocating and distributing labels for packet encapsulation
CN103516610B (zh) * 2012-06-18 2017-12-15 华为技术有限公司 业务处理方法、设备和系统
US9094337B2 (en) * 2012-12-21 2015-07-28 Cieno Corporation Source identification preservation in multiprotocol label switching networks
US9042369B2 (en) * 2013-03-13 2015-05-26 Alcatel Lucent System and method for reflecting FEC route information
CN103269315B (zh) * 2013-04-27 2016-03-30 华为技术有限公司 标签分配方法、装置、系统和网络设备
CN104243311B (zh) * 2013-06-08 2018-05-25 华为技术有限公司 报文处理的方法及路由器
CN103354520B (zh) * 2013-07-02 2016-11-23 华为技术有限公司 一种标签处理的方法及装置
US9210089B2 (en) * 2013-10-21 2015-12-08 Cisco Technology, Inc. LSP ping/trace over MPLS networks using entropy labels
US9344357B2 (en) * 2014-01-24 2016-05-17 Cisco Technology, Inc. Label-switched path aggregation
US9253084B2 (en) * 2014-02-24 2016-02-02 Juniper Networks, Inc. Neighbor-label distribution with label distribution protocol
US9525622B2 (en) * 2014-03-17 2016-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Label stack encoding and processing to enable OAM procedures for service segments in segment routed (SR) networks
US9369379B2 (en) * 2014-09-30 2016-06-14 Alcatel Lucent System and method providing secured contexts in MPLS LFIB
CN105634940B (zh) * 2014-10-27 2020-06-16 中兴通讯股份有限公司 Sr信息获取方法及建立段路由网络的方法
US9781030B1 (en) * 2015-03-31 2017-10-03 Juniper Networks, Inc. Fast re-route protection using GRE over MPLS
CN106549871B (zh) * 2015-09-22 2020-09-08 华为技术有限公司 一种报文处理的方法、设备和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090122801A1 (en) * 2006-06-16 2009-05-14 Huawei Technologies Co., Ltd. Ethernet switching and forwarding method, system and apparatus
CN102143030A (zh) * 2011-01-07 2011-08-03 华为数字技术有限公司 一种发送转发信息的方法及设备
WO2013185715A1 (zh) * 2012-09-18 2013-12-19 中兴通讯股份有限公司 一种实现虚拟网络的方法和虚拟网络
CN104243362A (zh) * 2013-06-24 2014-12-24 杭州华三通信技术有限公司 一种报文转发方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3343846A4 *

Also Published As

Publication number Publication date
CN106549871A (zh) 2017-03-29
US20180212872A1 (en) 2018-07-26
US11909633B2 (en) 2024-02-20
US10680942B2 (en) 2020-06-09
ES2793312T3 (es) 2020-11-13
EP3343846B1 (en) 2020-03-25
CN106549871B (zh) 2020-09-08
EP3343846A4 (en) 2018-07-18
EP3343846A1 (en) 2018-07-04
CN112087386B (zh) 2024-01-02
US11218408B2 (en) 2022-01-04
US20220086086A1 (en) 2022-03-17
CN112087386A (zh) 2020-12-15
US20200287825A1 (en) 2020-09-10

Similar Documents

Publication Publication Date Title
WO2017050085A1 (zh) 一种报文处理的方法、设备和系统
US11570285B2 (en) Packet processing method, network node, and system
US10164838B2 (en) Seamless segment routing
JP6479169B2 (ja) 目的受信機を識別するパケットに依拠したマルチキャストアーキテクチャにおける分散的選択による、ツリー属性の自動化された判定及び受信機識別子の割り当て
EP4102785A1 (en) Message processing method and apparatus, and network device and storage medium
US11233732B2 (en) Label management method, data stream processing method, and device
CN112019433B (zh) 一种报文转发方法和装置
WO2019165888A1 (zh) 一种利用统一sr标签栈进行报文处理的方法及装置
WO2022237291A1 (zh) 报文传输方法、装置、相关设备及存储介质
US11943148B2 (en) Traffic flow processing method and apparatus
US11271873B2 (en) Operating a service provider network node
WO2021057530A1 (zh) 确定路由前缀与分段标识间映射关系的方法、装置及系统
CN111181855B (zh) 一种组播的方法及路由设备
WO2016119461A1 (zh) 一种建立bgp lsp隧道的方法及网络设备
US9853881B2 (en) Autonomous system border router (ASBR) advertising routes with a same forwarding label
WO2022170877A1 (zh) 报文转发方法、设备及系统
CN115118544A (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: 16847967

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016847967

Country of ref document: EP