WO2015149481A1 - 业务链路由方法及系统、及系统中的设备 - Google Patents

业务链路由方法及系统、及系统中的设备 Download PDF

Info

Publication number
WO2015149481A1
WO2015149481A1 PCT/CN2014/086062 CN2014086062W WO2015149481A1 WO 2015149481 A1 WO2015149481 A1 WO 2015149481A1 CN 2014086062 W CN2014086062 W CN 2014086062W WO 2015149481 A1 WO2015149481 A1 WO 2015149481A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
service
data packet
relay node
next hop
Prior art date
Application number
PCT/CN2014/086062
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 US15/300,964 priority Critical patent/US10305822B2/en
Priority to JP2016559847A priority patent/JP2017510208A/ja
Priority to EP18192031.5A priority patent/EP3425856A1/en
Priority to EP14888198.0A priority patent/EP3128701A4/en
Publication of WO2015149481A1 publication Critical patent/WO2015149481A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/55—Prevention, detection or correction of errors
    • H04L49/552—Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • 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/20—Hop count for routing purposes, e.g. TTL
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • 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/12—Shortest path evaluation
    • H04L45/127—Shortest path evaluation based on intermediate node capabilities
    • 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/74—Address processing for routing

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and system for a service link, and a device in the system.
  • the service links of the mobile value-added service network mainly include the two modes shown in Figure 1:
  • Mode 1 The service enablers are statically linked together, and the traffic needs to pass through all the service enablers in the service link.
  • the mobile gateway uses an Access Point Name (APN) to distinguish different service links.
  • API Access Point Name
  • Mode 2 All service enablers are connected to a centralized traffic routing controller. After each service enabler is processed, traffic is returned to the centralized controller to determine the next hop.
  • the networking topology between service enablers corresponding to each APN is relatively static, even fixedly connected into a service chain, adding or removing a service enabler, or simply changing the service chain.
  • the logic of the network will cause changes in the network topology. This brings many problems to the service deployment and management of the carrier.
  • the dependency of the network topology directly leads to the complexity of manual configuration.
  • the service enablers can only be deployed in the specified order. It cannot be changed (although many business enablers do not have a sequence of execution restrictions), which makes it difficult to adapt to flexible and rapid service deployment changes;
  • FIG. 1 which includes the following network element devices:
  • the traffic classification network element device is mainly responsible for performing service identification and service chain selection on the received data packet, and inserting a corresponding service chain label in the data packet. For details, refer to FIG. 2;
  • the service orchestration network element device is mainly responsible for orchestrating the order of the service nodes connected in series in the service chain;
  • the network control network element device is mainly responsible for maintaining and managing the network topology and service links of the mobile value-added service network
  • the switch is mainly responsible for receiving data packets and forwarding data packets according to the service link.
  • not all nodes of the mobile value-added service network support the service link. As shown in FIG. 3 and FIG. 4, in FIG. 3, the service node 2 does not support the service link mechanism, which may cause the service chain path 2 to fail. In Figure 4, Switch 2 does not support the service link mechanism, which also causes the service link to fail.
  • the traditional node for the mobile value-added service network in the related art does not support the problem that the service link is easily caused by the mechanism, and no effective solution has been proposed yet.
  • the present invention provides a method and system for a service link, and a device in the system to at least solve the above problems.
  • a method for a service link comprising: receiving, by a relay node, a first data packet forwarded by a switching node, where the first data packet is sent to an unsupported service link
  • the packet of the next hop node, the relay node has a binding relationship with the next hop node; the relay node determines that the type of the next hop node is a service node, and deletes the service chain identifier in the first data packet;
  • the node sends the first data packet with the service chain identifier removed to the switching node, so that the switching node forwards the first data packet with the service chain identifier deleted to the next hop node according to the binding relationship.
  • the relay node deletes the service chain identifier in the first data packet, and the relay node saves the correspondence between the address quintuple and the service chain identifier in the first data packet, where the address quintuple includes: Destination IP address, destination port, source IP address, source port, and protocol number; the relay node deletes the service chain identifier from the first data packet.
  • the relay node After the relay node sends the first data packet of the service chain identifier to the switching node, the relay node receives the second data packet forwarded by the switching node, where the second data packet is the next hop node.
  • the relay node adds the service chain identifier in the first data packet to the second data packet, including: the relay node acquires the address quintuple in the second data packet; and the relay node belongs to the corresponding relationship that has been saved.
  • the address quintuple in the second data packet is searched for the corresponding service chain identifier; if the search result is yes, the relay node adds the found service chain identifier to the second datagram.
  • the relay node determines that the address quintuple has been modified when the next hop node performs packet processing, and obtains the address in the first data packet from the next hop node.
  • the quintuple obtains the service chain identifier in the first data packet according to the corresponding relationship, and adds the obtained service chain identifier to the second data packet.
  • the binding relationship is an address tunnel binding relationship configured for the relay node and the next hop node in a manner that is configured in advance for the switching node or is sent by the network control node to the switching node.
  • the binding relationship is an address tunnel binding relationship set by the network control node for the relay node and the next hop node by changing the service link by means of information.
  • the switch node finds that the first data packet carries the service chain identifier, and the service link determines that the next hop node does not support the service link according to the service link;
  • the control node sends an event report;
  • the network control node allocates a relay node to the next hop node according to the network topology, where the relay node includes: a virtual machine, a service device, or an internal component of the network control node.
  • a service link system including: a service orchestration node, a network control node, a switching node, a service node, and a relay node, where the relay node includes: a first receiving The module is configured to receive the first data packet forwarded by the switching node, where the first data packet is sent to a next hop node that does not support the service link, and the relay node is bound to the next hop node.
  • the first processing module is configured to: after determining that the type of the next hop node is a service node, deleting the service chain identifier in the first data packet; the first sending module is configured to delete the first of the service chain identifier The data packet is sent to the switching node, so that the switching node forwards the first data packet with the service chain identifier deleted to the next hop node according to the binding relationship.
  • the first processing module includes: a saving unit, configured to save a correspondence between the address quintuple and the service chain identifier in the first data packet, where the address quintuple includes: a destination IP address, a destination port, and a source IP address. The address, the source port, and the protocol number; the deleting unit is configured to delete the service chain identifier from the first data packet.
  • the relay node further includes: a second receiving module, configured to receive the second data packet forwarded by the switching node, where the second data packet is a packet returned by the next hop node after the packet processing; the second processing module The second sending module is configured to forward the second data packet with the service chain identifier added to the switching node.
  • the second processing module includes: an obtaining unit, configured to obtain an address quintuple in the second data packet; and the searching unit is configured to search for the second data packet in the corresponding relationship set to which the saved correspondence belongs Whether the address quintuple has a corresponding service chain identifier; the first processing unit is configured to add the found service chain identifier to the second data packet when the search result of the search unit is YES, and the corresponding relationship In the collection
  • the second processing unit is configured to determine that the address quintuple has been modified when the next hop node performs packet processing, and the first data is obtained from the next hop node when the search result of the search unit is negative.
  • the address quintuple in the packet is obtained, and the service chain identifier in the first data packet is obtained according to the corresponding relationship, and the obtained service chain identifier is added to the second data packet.
  • the binding relationship is an address tunnel binding relationship configured for the relay node and the next hop node in a manner that is configured in advance for the switching node or is sent by the network control node to the switching node.
  • the binding relationship is an address tunnel binding relationship set by the network control node for the relay node and the next hop node by changing the service link by means of information.
  • the switching node includes: a determining module, configured to: discover that the first data packet carries a service chain identifier, and according to the service link, determine, by the information, that the next hop node does not support the service link; and the sending module is configured to send an event to the network control node.
  • the network control node includes: an allocation module, configured to allocate a relay node to the next hop node according to the network topology, where the relay node includes: a virtual machine, a service device, or an internal component of the network control node.
  • a method for service link comprising: receiving, by a first relay node, a data packet forwarded by a switching node, where the data packet is sent to an unsupported service link.
  • the first hop node has a binding relationship with the next hop node; the first relay node determines that the type of the next hop node is a switching node, and encapsulates the address information of the second relay node.
  • the second relay node has a binding relationship with the next hop node; the first relay node sends the data packet encapsulated with the address information to the second relay node, so that the second relay node After the node deletes the address information from the received data packet, the data packet that has deleted the address information is forwarded to the switching node that supports the service link.
  • the method includes: the first relay node receives the address information of the second relay node sent by the network control node.
  • the binding relationship is an address tunnel binding relationship configured for the first relay node, the second relay node, and the next hop node by using a pre-configured switch node or a network control node to send a notification to the switch node. .
  • the binding relationship is an address tunnel binding relationship set by the network control node for the first relay node, the second relay node, and the next hop node by changing the service link by means of information.
  • the method includes: the switching node discovers that the data packet carries the service chain identifier, and determines, according to the service link, that the next hop node does not support The service link is sent by; the switching node sends an event report to the network control node; the network control node according to the network topology A first relay node and a second relay node are allocated to the next hop node, where the second relay node refers to a relay node directly connected to the switching node supporting the service link.
  • the network control node When the second relay node does not belong to the network control node, the network control node sends an allocation request to the network control node that governs the second relay node to obtain the right to use the second relay node and the address of the second relay node. information.
  • a service link system including: a service orchestration node, a network control node, a switching node, a service node, a first relay node, and a second relay node
  • a relay node includes: a first receiving module, configured to receive a data packet forwarded by the switching node, where the data packet is sent to a next hop node that does not support the service link, and the first relay node
  • the first processing module is configured to determine the type of the next hop node as a switching node, and then encapsulate the address information of the second relay node in the data packet, where the second node
  • the second processing module is configured to send the data packet encapsulated with the address information to the second relay node, so that the second relay node deletes the received data packet. After the address information is forwarded, the data packet with the deleted address information is forwarded to the switching node supporting the service link.
  • the first relay node further includes: a second receiving module, configured to receive address information of the second relay node sent by the network control node.
  • the binding relationship is an address tunnel binding relationship configured for the first relay node, the second relay node, and the next hop node by using a pre-configured switch node or a network control node to send a notification to the switch node. .
  • the binding relationship is an address tunnel binding relationship set by the network control node for the first relay node, the second relay node, and the next hop node by changing the service link by means of information.
  • the switching node includes: a determining module, configured to: the service data identifier is carried in the discovery data packet, and the next hop node does not support the service link according to the service link; the first sending module is configured to send the event to the network control node.
  • the network control node includes: an allocation module, configured to allocate a first relay node and a second relay node to the next hop node according to the network topology, where the second relay node refers to an exchange with the support service link A relay node directly connected to a node.
  • the network control node further includes: a second sending module, configured to send an allocation request to the network control node that governs the second relay node to obtain the use of the second relay node when the second relay node does not belong to the network control node The right and the address information of the second relay node.
  • a second sending module configured to send an allocation request to the network control node that governs the second relay node to obtain the use of the second relay node when the second relay node does not belong to the network control node The right and the address information of the second relay node.
  • a service orchestration network element device including: a collection module, configured to collect service link capability information of all service nodes in a service chain; and a screening module, configured to be based on a service link The capability information is used to filter out a service node that does not support the service link capability; the notification module is configured to notify the network control network element device of the service node that does not support the service link by the capability, so that the network control network element device according to the network Topology, the port of the switching node that is connected to the service node that does not support the service routing capability is set to not support the service link state.
  • a network control network element device including: a collection module, configured to collect service link capability information of all switching nodes in a mobile value-added service network; and a screening module, configured to be based on the service
  • the link is configured by the capability information to filter out the switching node that does not support the service link capability.
  • the setting module is configured to set the port of the switching node connected to the switching node that does not support the service routing capability to not support the service chain according to the network topology. Routing status.
  • a switch including: a determining module, configured to determine that a next hop node does not support a service link capability if the next hop node fails to forward data or does not answer
  • the reporting module is configured to report, to the network control network element device, port state information that is set to indicate that the next hop node does not support the service link capability, so that the network control network element device determines the next hop according to the predetermined policy and the port state information.
  • the node does not support the service link capability;
  • the receiving module is configured to receive the response message returned by the network control network element device, wherein the response message is set to notify the switch that the port connected to the next hop node is set to not support the service link.
  • setting module set to set the switch port connected to the next hop node to not support the service link state according to the response message.
  • the present invention solves the problem that the traditional node of the mobile value-added service network does not support the service link by adding a relay node in the mobile value-added service network deployed by the operator and performing function expansion and definition on other nodes.
  • the problem that the service link is faulty is caused by the mechanism.
  • the next hop node is the service node, and the relay node is used to forward the data packet forwarded by the switching node to the next hop service node.
  • the next hop node is the switching node, and the relay node is used to forward the data packet forwarded by the switching node to the next hop switching node, thereby achieving the probability of improving the success of the service link.
  • the effect of the service link by the mechanism When the service link is not supported by the capability, the next hop node is the switching node, and the relay node is used to forward the data packet forwarded by the switching node to the next hop switching node, thereby achieving the probability of improving the success of the service link.
  • FIG. 1 is a schematic structural diagram of a service link of a mobile value-added service network according to the related art
  • FIG. 2 is a schematic diagram of inserting a service chain label in a data packet according to the related art
  • FIG. 3 is a schematic diagram of a service link when a service node does not support a service link by mechanism according to the related art
  • FIG. 4 is a schematic diagram of a service link when a switching node does not support a service link by mechanism according to the related art
  • FIG. 5 is a flowchart of a service link method according to Embodiment 1 of the present invention.
  • FIG. 6 is a structural block diagram of a service link system according to Embodiment 1 of the present invention.
  • FIG. 7 is a structural block diagram of a preferred service link system according to Embodiment 1 of the present invention.
  • FIG. 9 is a structural block diagram of a service link system according to Embodiment 2 of the present invention.
  • FIG. 10 is a structural block diagram of a preferred service link system according to Embodiment 2 of the present invention.
  • FIG. 11 is a structural block diagram of a service orchestration network element device according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a network control network element device according to an embodiment of the present invention.
  • FIG. 13 is a structural block diagram of a switch according to an embodiment of the present invention.
  • FIG. 14 is a block diagram showing the structure of a service link of a mobile value-added service network according to a preferred embodiment of the present invention.
  • 15 is a schematic diagram of packet processing in a case where a next hop node is a service node according to a preferred embodiment of the present invention.
  • FIG. 16 is a schematic diagram of packet processing in a case where a next hop node is a switching node according to a preferred embodiment of the present invention.
  • FIG. 17 is a flow chart of message processing in a case where a next hop node is a service node according to a preferred embodiment of the present invention.
  • next hop node is a switching node according to a preferred embodiment of the present invention.
  • FIG. 19 is a flow chart showing a first mode of setting a state of a switching node port in accordance with a preferred embodiment of the present invention.
  • 20 is a flow chart showing a second mode of setting a state of a switching node port in accordance with a preferred embodiment of the present invention.
  • 21 is a flow chart showing the third way of setting the state of a switching node port according to a preferred embodiment of the present invention.
  • FIG. 22 is a flowchart of processing for a cross-domain relay node in a scenario in which a switch does not support a service link according to a preferred embodiment of the present invention.
  • Embodiment 1 of the present invention provides a method for service link.
  • FIG. 5 is a flowchart of a service link according to a first embodiment of the present invention. As shown in FIG. 5, the method mainly includes the following steps (step S502-step S506):
  • Step S502 The relay node receives the first data packet forwarded by the switching node, where the first data packet is a packet sent to a next hop node that does not support the service link, and the relay node and the next hop node Have a binding relationship;
  • Step S504 After determining that the type of the next hop node is a service node, the relay node deletes the service chain identifier in the first data packet.
  • Step S506 The relay node sends the first data packet with the service chain identifier deleted to the switching node, so that the switching node forwards the first data packet with the service chain identifier deleted to the next hop node according to the binding relationship.
  • a method of adding a relay node in a mobile value-added service network that is traditionally deployed by an operator and performing function expansion and definition on other nodes may be performed without supporting the service link.
  • the relay node forwards the data packet forwarded by the switching node to the next hop service node, thereby improving the probability of success of the service link and improving the service link mechanism.
  • step S504 the relay node deletes the service chain identifier in the first data packet, which can be implemented in such a manner that the relay node first saves the address quintuple in the first data packet.
  • the address quintuple includes: a destination IP address, a destination port, a source IP address, a source port, and a protocol number; and the relay node deletes the service chain identifier from the first data packet.
  • the relay node may further receive the second data packet forwarded by the switching node, where the second data packet is the packet returned by the next hop node after the packet processing.
  • the relay node adds the service chain identifier in the first data packet to the second data packet; the relay node forwards the second data packet to which the service chain identifier is added to the switching node.
  • the relay node adds the service chain identifier in the first data packet to the second data packet, which can be implemented in the following manner: the relay node first obtains the address quintuple in the second data packet; The node searches for the corresponding service chain identifier of the address quintuple in the second data packet in the corresponding relationship set to which the saved correspondence belongs. If the search result is yes, the relay node finds the found The service chain identifier is added to the second data packet, and the corresponding relationship is deleted from the corresponding relationship set. If the search result is no, the relay node determines that the next hop node has modified the address quintuple when processing the packet. Obtaining the address quintuple in the first data packet from the next hop node, and obtaining the service chain identifier in the first data packet according to the corresponding relationship, and adding the obtained service chain identifier to the second data packet .
  • the binding relationship can be implemented in the following two manners: (1) the binding relationship is configured by using a pre-switching node or a notification by the network control node by sending a notification to the switching node.
  • the mode (2) binding relationship is an address tunnel binding relationship set by the network control node for the relay node and the next hop node by changing the service link by means of information.
  • the switch node may further include: the switching node discovers that the first data packet carries the service chain identifier, and the information is determined according to the service link. The hop node does not support the service link; the switch node sends the event report to the network control node; the network control node allocates the relay node to the next hop node according to the network topology, where the relay node includes: a virtual machine, a service device, or The internal components of the network control node.
  • the first embodiment of the present invention provides a service link system, which is configured to implement the service link provided by the first embodiment.
  • 6 is a structural block diagram of a service link system according to Embodiment 1 of the present invention. As shown in FIG. 6, the system mainly includes: a service orchestration node 10, a network control node 20, a switching node 30, a service node 40, and Following node 50.
  • the relay node 50 may further include: a first receiving module 51, configured to receive the first data packet forwarded by the switching node 30, where the first data packet is sent to the next hop of the unsupported service link
  • the packet of the node has a binding relationship between the relay node 50 and the next hop node.
  • the first processing module 52 is configured to delete the service chain identifier in the first data packet after determining that the type of the next hop node is a service node.
  • the first sending module 53 is configured to send the first data packet with the service chain identifier deleted to the switching node 30, so that the switching node 30 forwards the first data packet with the service chain identifier deleted according to the binding relationship. Next hop node.
  • FIG. 7 is a structural block diagram of a preferred service link system according to Embodiment 1 of the present invention.
  • the first processing module 52 includes: a saving unit 522, which is set to protect And storing a correspondence between the address quintuple and the service chain identifier in the first data packet, where the address quintuple includes: a destination IP address, a destination port, a source IP address, a source port, and a protocol number; and deleting the unit 524 , set to remove the service chain identifier from the first data packet.
  • the relay node 50 further includes: a second receiving module 54 configured to receive the second data packet forwarded by the switching node 30, wherein the second data packet is performed by the next hop node The packet returned by the packet processing; the second processing module 55 is configured to add a service chain identifier in the first data packet to the second data packet; and the second sending module 56 is configured to add the service chain identifier.
  • the second data message is forwarded to the switching node 30.
  • the second processing module 55 may include: an obtaining unit 552, which acquires an address quintuple in the second data packet; and a searching unit, configured to search for the second data in the corresponding relationship set to which the saved correspondence belongs Whether the address quintuple in the message has a corresponding service chain identifier; the first processing unit 554 is configured to add the found service chain identifier to the second data packet if the search result of the search unit is yes.
  • the second processing unit 556 is configured to: when the search result of the search unit is negative, determine that the address quintuple has been modified when the next hop node performs packet processing, The next hop node obtains the address quintuple in the first data packet, and obtains the service chain identifier in the first data packet according to the corresponding relationship, and adds the obtained service chain identifier to the second data packet.
  • the binding relationship can be implemented in the following two ways: mode (1) the binding relationship is configured in advance for the switching node 30 or by the network control node 20 by sending a notification to the switching node 30.
  • the mode (2) binding relationship is an address tunnel binding relationship set by the network control node 20 for the relay node 50 and the next hop node by changing the service link by means of information.
  • the switching node 30 includes: a determining module 32, configured to discover that the first data packet carries a service chain identifier, and according to the service link, it is determined by the information that the next hop node does not support the service link.
  • the sending module 34 is configured to send an event report to the network control node 20; the network control node 20 includes: an allocating module 22, configured to allocate a relay node 50 to the next hop node according to the network topology, wherein the relay node 50 may include : Internal components of a virtual machine, business device, or network control node.
  • Embodiment 2 of the present invention provides a service link method.
  • FIG. 8 is a flowchart of a service link according to a second embodiment of the present invention. As shown in FIG. 8, the method mainly includes the following steps (step S802-step S806):
  • Step S802 The first relay node receives the data packet forwarded by the switching node, where the data packet is sent to the next hop node that does not support the service link, and the first relay node and the next hop node Have a binding relationship;
  • Step S804 the first relay node determines that the type of the next hop node is a switching node, and encapsulates the address information of the second relay node in the data packet, where the second node has a binding relationship with the next hop node. ;
  • Step S806 the first relay node sends the data packet encapsulating the address information to the second relay node, so that the second relay node deletes the address information after deleting the address information from the received data packet.
  • the data packet is forwarded to the switching node that supports the service link.
  • the method of adding a relay node in the mobile value-added service network deployed by the operator and performing function expansion and definition on other nodes may be performed by not supporting the service link by the capability next hop node.
  • the relay node forwards the data packet forwarded by the switching node to the next hop switching node, thereby improving the probability of success of the service link and improving the service link mechanism.
  • the first relay node may receive address information of the second relay node sent by the network control node.
  • the method further includes: the switching node discovers that the data packet carries the service chain identifier, and the information is determined by the information according to the service link.
  • the one-hop node does not support the service link; the switching node sends an event report to the network control node; the network control node allocates the first relay node and the second relay node to the next hop node according to the network topology, wherein the second relay A node is a relay node that is directly connected to a switching node that supports a service link.
  • the binding relationship can be implemented in the following two manners: mode (1) the binding relationship is configured by using a pre-switching node or sending a notification to the switching node by the network control node. An address tunnel binding relationship configured by the first relay node, the second relay node, and the next hop node. (2) The binding relationship is an address tunnel binding relationship set by the network control node for the first relay node, the second relay node, and the next hop node by changing the service link by means of information.
  • the network control node may send an allocation request to the network control node that governs the second relay node to obtain the right to use the second relay node and the second Following the address information of the node.
  • the second embodiment of the present invention provides a service link by the system, which is configured to implement the service link provided by the second embodiment.
  • 9 is a structural block diagram of a service link system according to Embodiment 2 of the present invention.
  • the system mainly includes: a service orchestration node 10, a network control node 20, a switching node 30, a service node 40, and a first The relay node 52 and the second relay node 54, wherein the first relay node 52 includes: a first receiving module 522, configured to receive the data packet forwarded by the switching node 30, wherein the data packet is sent to the unsupported The packet of the next hop node of the service link, the first relay node 52 and the next hop node have a binding relationship; the first process After the module 524 is configured to determine that the type of the next hop node is a switching node, the address information of the second relay node 54 is encapsulated in a data packet, where the second relay node 54 has a binding with the next hop node.
  • the second processing module 526 is configured to send the data message encapsulating the address information to the second relay node 54, so that the second relay node 54 deletes the address information from the received data message, and then The data message with the address information deleted is forwarded to the switching node 30 supporting the service link.
  • the second embodiment of the present invention further provides a preferred service link system.
  • 10 is a structural block diagram of a preferred service link system according to Embodiment 2 of the present invention.
  • the first relay node 52 may further include: a second receiving module 528, configured to receive a network control node. 20 transmits the address information of the second relay node 54.
  • the binding relationship can be implemented in the following two ways: mode (1) the binding relationship is configured by using the switching node 30 in advance or by the network control node 20 by sending a notification to the switching node 30. An address tunnel binding relationship configured by the relay node 52, the second relay node 54, and the next hop node. (2) The binding relationship is an address tunnel binding relationship set by the network control node 20 for the first relay node 52, the second relay node 54, and the next hop node by changing the service link by means of information.
  • the switching node 30 includes: a determining module 32, configured to: the service data link identifier is carried in the discovery data packet, and the next hop node does not support the service link according to the service link;
  • a sending module 34 is configured to send an event report to the network control node 20;
  • the network control node 20 includes: an allocating module 22 configured to allocate the first relay node 52 and the second relay node 54 to the next hop node according to the network topology.
  • the second relay node 54 refers to a relay node directly connected to the switching node 30 supporting the service link.
  • the network control node 20 further includes: a second sending module 24 configured to send an allocation request to the network control node that governs the second relay node 54 when the second relay node 54 does not belong to the network control node 20 Obtaining the right to use the second relay node 54 and the address information of the second relay node.
  • a second sending module 24 configured to send an allocation request to the network control node that governs the second relay node 54 when the second relay node 54 does not belong to the network control node 20 Obtaining the right to use the second relay node 54 and the address information of the second relay node.
  • the embodiment of the invention further provides a service orchestration network element device.
  • 11 is a structural block diagram of a service orchestration network element device according to an embodiment of the present invention.
  • the service orchestration network element device may include: a collection module 10 configured to collect service links of all service nodes in a service chain. The capability information; the screening module 20 is configured to filter out the service node that does not support the service link by the capability information according to the service link; and the notification module 30 is configured to notify the service node that does not support the service link by the capability
  • the network controls the network element device, so that the network control network element device sets the port of the switching node connected to the service node that does not support the service routing capability to not support the service link state according to the network topology.
  • FIG. 12 is a structural block diagram of a network control network element device according to an embodiment of the present invention.
  • the network control network element device may include: a collection module 10 configured to collect services of all switching nodes in a mobile value-added service network.
  • the link is composed of the capability information;
  • the screening module 20 is configured to filter out the switching node that does not support the service link by the capability information according to the service link;
  • the setting module 30 is configured to perform the service routing capability according to the network topology.
  • the port of the switching node to which the switching node is connected is set to not support the service link by state.
  • the embodiment of the invention further provides a switch.
  • 13 is a structural block diagram of a switch according to an embodiment of the present invention. As shown in FIG. 13, the switch may include: a determining module 10 configured to determine the next if the next hop node fails to forward data or does not answer.
  • the hopping node does not support the service link capability;
  • the reporting module 20 is configured to report the port state information set to the network control network element device to indicate that the next hop node does not support the service link capability, so that the network control network element device is configured according to The predetermined policy and port state information determines that the next hop node does not support the service link by capability;
  • the receiving module 30 is configured to receive a response message returned by the network control network element device, wherein the response message is set to notify the switch that the next hop will be
  • the port connected to the node is set to not support the service link state;
  • the setting module 40 is configured to set the switch port connected to the next hop node to not support the service link state according to the response message.
  • the service link provided by the foregoing embodiment may be implemented by the method and system, the service orchestration network element device, the network control network element device, and/or the switch, and the traditional node of the mobile value-added service network in the related technology does not support the service link.
  • the problem of the failure of the service link is achieved by improving the probability of success of the service link by the success of the service link.
  • the service link provided by the foregoing embodiment is described and illustrated in detail by the method and system, the service orchestration network element device, the network control network element device, and/or the switch, with reference to FIG. 14 to FIG. 22 and the preferred embodiment.
  • FIG. 14 is a schematic structural diagram of a service link of a mobile value-added service network according to a preferred embodiment of the present invention.
  • the architecture mainly adds a relay node as compared with the background architecture (shown in FIG. 1).
  • the traffic classification network element is not involved in this preference.
  • the traffic classification network element is omitted in this architecture.
  • the architecture mainly includes:
  • the service orchestration network element device in addition to being responsible for orchestrating the order of the service nodes connected in the service chain, is also responsible for collecting the capability information of the service node (mainly including: whether the service link is supported by the capability), and transmitting the information to the network control.
  • Network element device in addition to being responsible for orchestrating the order of the service nodes connected in the service chain, is also responsible for collecting the capability information of the service node (mainly including: whether the service link is supported by the capability), and transmitting the information to the network control.
  • Network element device is also responsible for collecting the capability information of the service node (mainly including: whether the service link is supported by the capability), and transmitting the information to the network control.
  • the network control network element device in addition to being responsible for maintaining and managing the network topology and service links of the mobile value-added service network, is also responsible for assigning service nodes and switching nodes (switches) for which the service link is not supported. Following node
  • the switch node in addition to being responsible for receiving data packets and forwarding data packets according to the service link, also needs to have the ability to sense whether the next hop supports the service link. If not, the switch needs to be reported. Forwarding to the relay node assigned by the network control network element;
  • the relay node performs the corresponding operation according to the type of the next hop node notified by the network control network element, and specifically includes: (1) if the type of the next hop node is in the service node, the relay node will receive the datagram. After the address quintuple and the service chain identifier relationship carried in the file are saved, the service chain identifier in the data packet is deleted, and the data packet is forwarded to the next hop node by the switching node; the returned datagram is received. After the text, the relay node obtains the quintuple of the data packet, searches for the corresponding service chain identifier in the previously stored address quintuple and the service chain identifier relationship, and finds and adds the corresponding service chain identifier to the data.
  • the packet the stored correspondence between the quintuple and the service chain identifier is deleted, and the data packet is forwarded to the switching node.
  • the type of the next hop node is a switching node
  • the first relay node acquires the address information of the second relay node, and encapsulates the address information of the second relay node into the header of the data packet, by A switching node forwards the data packet to the second relay node, and the second relay node strips the address information of the second relay node encapsulated in the data packet, and forwards the data packet to the second switching node.
  • FIG. 15 is a schematic diagram of packet processing in a case where a next hop node is a service node according to a preferred embodiment of the present invention. As shown in FIG. 15 , after receiving a data packet, the switching node forwards the packet according to the service link. If the next hop node does not support the service link, the event is reported to the network control node (see step 1);
  • the network control selects the relay node serving the next hop node and informs the relay node of the type of the next hop node (Note: if the relay node only processes the service node, the network control network element device is not required to notify the next hop node Type), then, by modifying the switching node flow table, the relay node and the next hop service node are bound to the address tunnel, and the data packet carrying the service chain identifier sent to the service node is forwarded to the relay node, and the relay node The data packet that does not carry the service chain identifier is forwarded to the service node, and the data packet returned by the service node is forwarded to the relay node (see step 2);
  • the switching node forwards the data packet to the relay node, and the data packet carries the service chain identifier (see step 3);
  • the relay node receives the data packet and dynamically stores the correspondence between the quintuple and the service chain identifier.
  • the quintuple refers to the destination IP address, destination port, source IP address, and source port carried in the packet. , the protocol number, delete the field of the service chain identifier in the packet, and forward the packet to the switching node (see step 4);
  • the switching node determines that there is no service chain identifier in the received data packet, and forwards the data packet to the service node according to the binding relationship between the relay node and the service node (see step 5);
  • the service node After receiving the packet and processing it, the service node returns a data packet (see step 6);
  • the switching node returns the returned data packet to the relay node according to the binding relationship between the service node and the relay node (see step 7);
  • the relay node After receiving the data packet, the relay node first obtains the address quintuple (which may be simply referred to as a quintuple) in the data packet, and according to the relationship table between the quintuple and the service chain identifier saved by the quintuple. Searching for the corresponding service chain identifier, if found, adding the corresponding service chain identifier to the data packet, deleting the stored quintuple and service chain identifier correspondence record, and forwarding the packet to the switching node; If not found, the service node modifies the initial quintuple of the packet, for example, a NAT type service node.
  • the address quintuple which may be simply referred to as a quintuple
  • the relay node needs to obtain initial quintuple information from the service node, and according to the initial quintuple search relationship table, Obtaining the service chain identifier, inserting the service chain identifier field into the data packet, and then forwarding the packet to the switching node (see step 8);
  • the switching node is responsible for forwarding the message to the next hop.
  • FIG. 16 is a schematic diagram of packet processing in the case where a next hop node is a switching node according to a preferred embodiment of the present invention. As shown in FIG. 16, when a switching node receives a data packet and forwards the packet according to the service link, the packet is found. If the next hop node does not support the service link, the event is reported to the network control node (see step 1);
  • the network control network element device selects the first relay node (including the first relay node and the second relay node) serving the next hop node, and first acquires the second relay node address information, where the second relay node It refers to a relay node that can directly connect to the subsequent support service link by the switching node.
  • the acquisition method can be divided into two types: the first type, the second relay node belongs to the current network control network element device, and the network control network element
  • the device selects the second relay node according to the network topology and the switching node capability; second, the second relay node may not belong to the current network control network element device jurisdiction (referred to as the network control network device 1), and the network control network
  • the meta-device 1 needs to request the second relay node to be allocated to the network control network element device 2 (the network control network element device to which the second relay node belongs) (see FIG. 22 for details).
  • the network control network device 1 acquires the address information of the relay node 2 (ie, the second relay node) and transmits it to the relay node 1 (ie, the first relay node), and then makes the relay node 1 and the middle by modifying the switching node flow table. After the node 2 and the next hop service node perform the address tunnel binding, the data packet carrying the service chain identifier sent to the service node is forwarded to the relay node 1, and the relay node 1 sends the packet without the service chain identifier to the relay node. The service node and the data packet returned by the service node are forwarded to the relay node 1 (see step 2);
  • the switching node forwards the data packet to the first relay node, and the data packet carries the service chain identifier (see step 3);
  • the first relay node receives the data packet, encapsulates the address information of the second relay node before the packet, and forwards the packet to the switching node (see step 4);
  • the switching node forwards the data packet to the second relay node (see step 5);
  • the second relay node After receiving the data packet, the second relay node strips the address information of the local node, and delivers the packet to the switch supporting the service link (see step 6);
  • the switching node is responsible for forwarding the message to the corresponding service node.
  • FIG. 17 is a flowchart of packet processing in a case where a next hop node is a service node according to a preferred embodiment of the present invention. As shown in FIG. 17, the process includes the following steps:
  • the switching node receives the data packet, and finds that the service chain identifier is carried in the packet, and then the next hop node that is forwarded by the table-aware packet according to the service link does not support the service link.
  • S1702 The switching node sends an event report to the network control node device.
  • the network control node device allocates a relay node to the next hop node according to the network topology, where the relay node may be a virtual machine instance, or a service device, or a component inside the network control node;
  • the switching node knows that the relay node exists (for example, the network control node has informed the switching node, or the switching node has been statically configured with the relay node (including the built-in relay node)), the first three steps are Not required.
  • the network control node device changes the service link by the flow table, so that the relay node and the next hop service node perform address tunnel binding, and the data packet carrying the service chain identifier sent to the service node is forwarded to the relay node, where After the node forwards the data packet that does not carry the service chain identifier to the service node, the data packet returned by the service node is forwarded to the relay node.
  • S1705 The switching node forwards the data packet to the relay node according to the service link by using the flow table.
  • the S1706 After receiving the data packet, the S1706 dynamically saves the correspondence between the quintuple and the service chain identifier in the packet.
  • the quintuple refers to the destination IP address, destination port, and source IP address carried in the packet. , the source port, the protocol number, and then delete the service chain identifier field in the data packet, and forward the data packet to the switching node;
  • the switching node determines that there is no service chain identifier in the received data packet, and forwards the data packet to the service node according to the binding relationship between the relay node and the service node;
  • S1708-S1709 The service node returns a data packet after processing the received data packet, and the switching node returns the returned data packet to the relay node according to the binding relationship between the service node and the relay node;
  • the relay node After receiving the data packet, the relay node first obtains the quintuple in the data packet, and searches for the corresponding service chain identifier according to the quintuple's address quintuple and the service chain identifier relationship table. If it is found, the corresponding service chain identifier is added to the data packet, and the stored quintuple and service chain identifier correspondence record is deleted, and the data packet is forwarded to the switching node. If not found, the service node is modified. The initial quintuple of the packet (for example, a NAT type service node).
  • the relay node needs to obtain the initial quintuple information from the service node, and obtain the service chain identifier according to the initial quintuple search relationship table. Then, the service chain identification field is inserted into the data packet, and then the data packet is forwarded to the switching node, and the switching node forwards the packet to the next hop node.
  • FIG. 18 is a flow chart of packet processing in the case where the next hop node is a switching node according to a preferred embodiment of the present invention. As shown in FIG. 18, the process includes the following steps:
  • the switching node After receiving the data packet, the switching node forwards the packet according to the service link, and finds that the next hop node does not support the service link.
  • the network control node device selects a relay node serving the next hop node, and obtains the second relay node address information, where the second relay node is directly connected to the subsequent support service link by the switching node relay node.
  • the acquisition method can be divided into two types: the first type, the second relay node belongs to the network control node device, and the network control node device selects the second relay node according to the network topology and the switching node capability, the second type, the second The relay node may not belong to the network control node device, and the network control 1 needs to request the second relay node to be allocated to the network control 2 (see FIG. 22 for details);
  • the switching node knows the relay node (for example, the network control node has informed the switching node, or the switching node has been statically configured with the relay node (including the built-in relay node)), the foregoing three steps are not required. of.
  • the network control node device obtains the address information of the relay node 2 and transmits it to the relay node 1;
  • the relay node and the next hop service node are bound to the address tunnel, and the data packet carrying the service chain identifier sent to the service node is forwarded to the relay node, and the relay node does not carry
  • the data packet identified by the service chain is forwarded to the service node, and the data packet returned by the service node is forwarded to the relay node.
  • the switching node forwards the data packet to the relay node 1 (the data packet carries the service chain identifier at this time);
  • the relay node After receiving the data packet, the relay node encapsulates the address information of the second relay node before the data packet, and forwards the packet to the switching node.
  • S1808 The switching node forwards the data packet to the second relay node.
  • the S1809 and the second relay node strip the local node address information, and transmit the data packet to the switch supporting the service link, and the switching node is responsible for forwarding the data packet to the corresponding service node.
  • FIG. 19 is a flowchart of a first manner of setting a state of a switching node port according to a preferred embodiment of the present invention.
  • the first method is used to enable a switch to sense whether a next hop node supports a service link capability, as shown in FIG.
  • the process includes the following steps:
  • the service orchestration node collects the capabilities of each service node
  • S1902 Filter out which nodes do not support service routing, and notify the network control node;
  • S1903 The network control node sets, according to the network topology, a switch port that is connected to the service node that does not have the service link by the capability, and does not support the service link state.
  • the switch searches by the table according to the service link, the egress port is found.
  • the status is "Does not support the service link state"
  • the process shown in Figure 17/18 is triggered;
  • FIG. 20 is a flowchart of a second manner of setting a state of a switching node port according to a preferred embodiment of the present invention.
  • the second mode is used by the network control node to sense whether the next hop switch of the switching node supports the service link capability, as shown in FIG. 20 As shown, the process includes the following steps:
  • the network control node collects capability information of each switching node in the network, and filters out a switch that does not support the service link.
  • S2002 The network control node sets, according to the network topology, a switch port that is connected to the switching node that does not have the service link by the capability, and does not support the service link state.
  • FIG. 21 is a flowchart of a third manner of setting a state of a switching node port according to a preferred embodiment of the present invention.
  • the third mode is used by the switching node to sense whether the next hop supports the service link capability, as shown in FIG. Includes the following steps:
  • the switching node does not support the service link by the next hop when the data is forwarded (for example, the data transmission does not answer or the transmission fails);
  • S2102 The switching node reports the port status information to the network control node, and notifies the network control node that the next hop service link fails.
  • S2103 The network control node determines, according to the policy (for example, the number of failure thresholds), that the next hop reported by the switching node does not support the service link, and then returns a response message, informing the switching node to set the port to “not supporting the service link. status".
  • the policy for example, the number of failure thresholds
  • FIG. 22 is a flowchart of processing for a cross-domain relay node in a scenario where a switch does not support a service link according to a preferred embodiment of the present invention. As shown in FIG. 22, the process includes the following steps:
  • the service domain 1 network control node 1 receives the switching node to report the next hop does not support the service link, then assigns the relay node 1 of the domain first;
  • the network control node 2 of the domain 2 allocates the relay node 2;
  • the network control node 1 notifies the relay node 1 of the address information of the collected relay node 2.
  • each of the above modules can be implemented by hardware.
  • a processor includes the above modules, or each of the above modules is located in one processor.
  • a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • the present invention achieves the following technical effects: by adding a relay node in a mobile value-added service network that is traditionally deployed by an operator, and expanding and defining functions of other nodes,
  • the next hop node is the service node
  • the relay node is used to forward the data packet forwarded by the switching node to the next hop service node, and the service link is not supported by the capability next hop node.
  • the relay node is used to forward the data packet forwarded by the switching node to the next hop switching node, thereby achieving the effect of improving the probability of success of the service link and improving the mechanism of the service link.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the embodiment of the present invention provides a method and system for a service link, and a device in the system, which has the following beneficial effects: when the service link is not supported, the next hop node is a service node.
  • the relay node forwards the data packet forwarded by the switching node to the next hop service node.
  • the next hop node is the switching node, and the relay node forwards the data packet forwarded by the switching node to the data packet.
  • the next hop switching node achieves the effect of improving the probability of success of the service link and improving the service link by the mechanism.

Landscapes

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

Abstract

本发明公开了一种业务链路由方法及系统、及系统中的设备。其中，该业务链路由方法包括：中继节点接收交换节点转发的第一数据报文，其中，第一数据报文是发送给不支持业务链路由的下一跳节点的报文，中继节点与下一跳节点具有绑定关系；中继节点确定下一跳节点的类型为业务节点后，删除第一数据报文中的业务链标识；中继节点将删除了业务链标识的第一数据报文发送给交换节点，以使交换节点根据绑定关系将删除了业务链标识的第一数据报文转发给下一跳节点。通过本发明，达到了提高业务链路由成功的概率，健全业务链路由机制的效果。

Description

业务链路由方法及系统、及系统中的设备 技术领域
本发明涉及通信领域，具体而言，涉及一种业务链路由方法及系统、及系统中的设备。
背景技术
目前，运营商正在通过部署移动增值业务网络提高用户体验质量(Qualify of Experience，简称为QoE)的方式减少网络带宽压力，并提供增值业务。移动增值业务网络的业务链路主要包括图1所示的两种模式：
模式1：业务使能器静态链接在一起，流量需要经过业务链路中所有的业务使能器，通常移动网关使用接入点名称(Access Point Name，简称为APN)来区分不同的业务链路；
模式2：所有的业务使能器连接到一个集中的流量路由控制器，每个业务使能器处理完后，流量回到集中控制器来决定下一跳。
在模式1中，每个APN对应的业务使能器之间的组网拓扑是相对静态的，甚至是固定串接成一个业务链，加入或移除一个业务使能器，或者简单改变业务链的逻辑，都会导致网络拓扑的更改，这为运营商的业务部署和管理带来很多的问题，网络拓扑的依赖性直接导致人工配置的复杂性，导致业务使能器只能按照既定的顺序部署而无法更改(虽然很多业务使能器之间没有执行先后顺序的限制)，这样难以适应弹性、快速的服务部署变动；
在模式2中，资本支出(CAPital eXpenditure，简称为CAPX)是比较高的，所有的流量总是经过集中控制器来确定下一跳，导致和分组网关之间具有重复的功能。
为了解决上述问题，业界提出一种业务链路由方案，如图1所示，该方案中包含以下几个网元设备：
流分类网元设备，主要负责对接收的数据报文进行业务识别和业务链选择，并在数据报文中插入对应的业务链标签，具体请参照图2；
业务编排网元设备，主要负责对业务链串联的业务节点的顺序进行编排；
网络控制网元设备，主要负责对移动增值业务网络的网络拓扑和业务链路由表进行维护和管理；
交换机，主要负责接收数据报文，并根据业务链路由表转发数据报文。
但是，不是移动增值业务网络的所有节点都支持业务链路由，如图3和图4所示，在图3中，业务节点2不支持业务链路由机制，会导致业务链路径2路由失败，在图4中，交换机2不支持业务链路由机制，同样会导致业务链路由失败。
针对相关技术中移动增值业务网络的传统节点不支持业务链路由机制容易导致业务链路由失败的问题，目前尚未提出有效的解决方案。
发明内容
本发明提供了一种业务链路由方法及系统、及系统中的设备，以至少解决上述问题。
根据本发明的一个实施例，提供了一种业务链路由方法，包括：中继节点接收交换节点转发的第一数据报文，其中，第一数据报文是发送给不支持业务链路由的下一跳节点的报文，中继节点与下一跳节点具有绑定关系；中继节点确定下一跳节点的类型为业务节点后，删除第一数据报文中的业务链标识；中继节点将删除了业务链标识的第一数据报文发送给交换节点，以使交换节点根据绑定关系将删除了业务链标识的第一数据报文转发给下一跳节点。
中继节点删除第一数据报文中的业务链标识，包括：中继节点保存第一数据报文中的地址五元组和业务链标识之间的对应关系，其中，地址五元组包括：目的IP地址、目的端口、源IP地址、源端口以及协议号；中继节点从第一数据报文中删除业务链标识。
在中继节点将删除了业务链标识的第一数据报文发送给交换节点之后，包括：中继节点接收交换节点转发的第二数据报文，其中，第二数据报文是下一跳节点进行报文处理后返回的报文；中继节点为第二数据报文添加第一数据报文中的业务链标识；中继节点将添加了业务链标识的第二数据报文转发到交换节点。
中继节点为第二数据报文添加第一数据报文中的业务链标识，包括：中继节点获取第二数据报文中的地址五元组；中继节点在已经保存的对应关系所属的对应关系集合中，查找第二数据报文中的地址五元组是否存在相应的业务链标识；在查找结果为是的情况下，中继节点把查找到的业务链标识添加到第二数据报文中，从对应关系集 合中删除对应关系；在查找结果为否的情况下，中继节点确定下一跳节点进行报文处理时已经修改了地址五元组，从下一跳节点获取第一数据报文中的地址五元组，并根据对应关系获取第一数据报文中的业务链标识，将获取到的业务链标识添加到第二数据报文中。
绑定关系是采用预先为交换节点配置或者是由网络控制节点通过向交换节点发送通知的方式，为中继节点和下一跳节点配置的地址隧道绑定关系。
绑定关系是由网络控制节点通过更改业务链路由信息的方式为中继节点和下一跳节点设置的地址隧道绑定关系。
在网络控制节点更改业务链路由信息之前，包括：交换节点发现第一数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；交换节点向网络控制节点发送事件上报；网络控制节点根据网络拓扑为下一跳节点分配中继节点，其中，中继节点包括：虚拟机、业务设备、或网络控制节点的内部组件。
根据本发明的另一实施例，提供了一种业务链路由系统，包括：业务编排节点、网络控制节点、交换节点、业务节点、以及中继节点，其中，中继节点包括：第一接收模块，设置为接收交换节点转发的第一数据报文，其中，第一数据报文是发送给不支持业务链路由的下一跳节点的报文，中继节点与下一跳节点具有绑定关系；第一处理模块，设置为确定下一跳节点的类型为业务节点后，删除第一数据报文中的业务链标识；第一发送模块，设置为将删除了业务链标识的第一数据报文发送给交换节点，以使交换节点根据绑定关系将删除了业务链标识的第一数据报文转发给下一跳节点。
第一处理模块包括：保存单元，设置为保存第一数据报文中的地址五元组和业务链标识之间的对应关系，其中，地址五元组包括：目的IP地址、目的端口、源IP地址、源端口以及协议号；删除单元，设置为从第一数据报文中删除业务链标识。
中继节点还包括：第二接收模块，设置为接收交换节点转发的第二数据报文，其中，第二数据报文是下一跳节点进行报文处理后返回的报文；第二处理模块，设置为为第二数据报文添加第一数据报文中的业务链标识；第二发送模块，设置为将添加了业务链标识的第二数据报文转发到交换节点。
第二处理模块包括：获取单元，设置为获取第二数据报文中的地址五元组；查找单元，设置为在已经保存的对应关系所属的对应关系集合中，查找第二数据报文中的地址五元组是否存在相应的业务链标识；第一处理单元，设置为在查找单元的查找结果为是的情况下，把查找到的业务链标识添加到第二数据报文中，从对应关系集合中 删除对应关系；第二处理单元，设置为在查找单元的查找结果为否的情况下，确定下一跳节点进行报文处理时已经修改了地址五元组，从下一跳节点获取第一数据报文中的地址五元组，并根据对应关系获取第一数据报文中的业务链标识，将获取到的业务链标识添加到第二数据报文中。
绑定关系是以预先为交换节点配置的或者是由网络控制节点通过向交换节点发送通知的方式，为中继节点和下一跳节点配置的地址隧道绑定关系。
绑定关系是由网络控制节点通过更改业务链路由信息的方式为中继节点和下一跳节点设置的地址隧道绑定关系。
交换节点包括：确定模块，设置为发现第一数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；发送模块，设置为向网络控制节点发送事件上报；网络控制节点包括：分配模块，设置为根据网络拓扑为下一跳节点分配中继节点，其中，中继节点包括：虚拟机、业务设备、或网络控制节点的内部组件。
根据本发明的又一实施例，提供了一种业务链路由方法，包括：第一中继节点接收交换节点转发的数据报文，其中，数据报文是发送给不支持业务链路由的下一跳节点的报文，第一中继节点与下一跳节点具有绑定关系；第一中继节点确定下一跳节点的类型为交换节点后，将第二中继节点的地址信息封装在数据报文中，其中，第二中继节点与下一跳节点具有绑定关系；第一中继节点将封装了地址信息的数据报文发送给第二中继节点，以使第二中继节点从接收到的数据报文中删除地址信息后，将删除了地址信息的数据报文转发给支持业务链路由的交换节点。
在第一中继节点接收交换节点转发的数据报文之前，包括：第一中继节点接收由网络控制节点发送的第二中继节点的地址信息。
绑定关系是采用预先为交换节点配置的或者是由网络控制节点通过向交换节点发送通知的方式，为第一中继节点、第二中继节点及下一跳节点配置的地址隧道绑定关系。
绑定关系是由网络控制节点通过更改业务链路由信息的方式为第一中继节点、第二中继节点及下一跳节点设置的地址隧道绑定关系。
在第一中继节点接收由网络控制节点发送的第二中继节点的地址信息之前，包括：交换节点发现数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；交换节点向网络控制节点发送事件上报；网络控制节点根据网络拓扑 为下一跳节点分配第一中继节点和第二中继节点，其中，第二中继节点是指与支持业务链路由的交换节点直接相连的中继节点。
当第二中继节点不属于网络控制节点管辖时，网络控制节点向管辖第二中继节点的网络控制节点发送分配请求，以获得使用第二中继节点的权利和第二中继节点的地址信息。
根据本发明的又一实施例，提供了一种业务链路由系统，包括：业务编排节点、网络控制节点、交换节点、业务节点、第一中继节点以及第二中继节点，其中，第一中继节点包括：第一接收模块，设置为接收交换节点转发的数据报文，其中，数据报文是发送给不支持业务链路由的下一跳节点的报文，第一中继节点与下一跳节点具有绑定关系；第一处理模块，设置为确定下一跳节点的类型为交换节点后，将第二中继节点的地址信息封装在数据报文中，其中，第二节点与下一跳节点具有绑定关系；第二处理模块，设置为将封装了地址信息的数据报文发送给第二中继节点，以使第二中继节点从接收到的数据报文中删除地址信息后，将删除了地址信息的数据报文转发给支持业务链路由的交换节点。
第一中继节点还包括：第二接收模块，设置为接收由网络控制节点发送的第二中继节点的地址信息。
绑定关系是采用预先为交换节点配置的或者是由网络控制节点通过向交换节点发送通知的方式，为第一中继节点、第二中继节点及下一跳节点配置的地址隧道绑定关系。
绑定关系是由网络控制节点通过更改业务链路由信息的方式为第一中继节点、第二中继节点及下一跳节点设置的地址隧道绑定关系。
交换节点包括：确定模块，设置为发现数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；第一发送模块，设置为向网络控制节点发送事件上报；网络控制节点包括：分配模块，设置为根据网络拓扑为下一跳节点分配第一中继节点和第二中继节点，其中，第二中继节点是指与支持业务链路由的交换节点直接相连的中继节点。
网络控制节点还包括：第二发送模块，设置为当第二中继节点不属于网络控制节点管辖时，向管辖第二中继节点的网络控制节点发送分配请求，以获得使用第二中继节点的权利和第二中继节点的地址信息。
根据本发明的又一实施例，提供了一种业务编排网元设备，包括：收集模块，设置为收集业务链中所有业务节点的业务链路由能力信息；筛选模块，设置为根据业务链路由能力信息，筛选出不支持业务链路由能力的业务节点；通知模块，设置为将不支持业务链路由能力的业务节点通知给网络控制网元设备，以使网络控制网元设备根据网络拓扑，将与不支持业务路由能力的业务节点相连的交换节点的端口设置为不支持业务链路由状态。
根据本发明的还一实施例，提供了一种网络控制网元设备，包括：收集模块，设置为收集移动增值服务网络中所有交换节点的业务链路由能力信息；筛选模块，设置为根据业务链路由能力信息，筛选出不支持业务链路由能力的交换节点；设置模块，设置为根据网络拓扑，将与不支持业务路由能力的交换节点相连的交换节点的端口设置为不支持业务链路由状态。
根据本发明的还一实施例，提供了一种交换机，包括：确定模块，设置为在向下一跳节点转发数据失败或无应答的情况下，确定下一跳节点不支持业务链路由能力；上报模块，设置为向网络控制网元设备上报设置为指示下一跳节点不支持业务链路由能力的端口状态信息，以使网络控制网元设备根据预定策略和端口状态信息确定下一跳节点确实不支持业务链路由能力；接收模块，设置为接收网络控制网元设备返回的应答消息，其中，应答消息设置为通知交换机将与下一跳节点相连的端口设置为不支持业务链路由状态；设置模块，设置为根据应答消息，将与下一跳节点相连的交换机端口设置为不支持业务链路由状态。
通过本发明，采用在运营商传统部署的移动增值服务网络中增加设置中继节点，并对其它节点进行功能扩展和定义的方式，解决了相关技术中移动增值业务网络的传统节点不支持业务链路由机制容易导致业务链路由失败的问题，可以在不支持业务链路由能力下一跳节点是业务节点时，使用中继节点将交换节点转发的数据报文转发给下一跳业务节点，在不支持业务链路由能力下一跳节点是交换节点时，使用中继节点将交换节点转发的数据报文转发给下一跳交换节点，进而达到了提高业务链路由成功的概率，健全业务链路由机制的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的移动增值服务网络的业务链路由的架构示意图；
图2是根据相关技术的在数据报文中插入业务链标签的示意图；
图3是根据相关技术的业务节点不支持业务链路由机制时的业务链路由示意图；
图4是根据相关技术的交换节点不支持业务链路由机制时的业务链路由示意图；
图5是根据本发明实施例一的业务链路由方法流程图；
图6是根据本发明实施例一的业务链路由系统的结构框图；
图7是根据本发明实施例一的优选业务链路由系统的结构框图；
图8是根据本发明实施例二的业务链路由方法流程图；
图9是根据本发明实施例二的业务链路由系统的结构框图；
图10是根据本发明实施例二的优选业务链路由系统的结构框图；
图11是根据本发明实施例的业务编排网元设备的结构框图；
图12是根据本发明实施例的网络控制网元设备的结构框图；
图13是根据本发明实施例的交换机的结构框图；
图14是根据本发明优选实施例的移动增值服务网络的业务链路由的架构示意图；
图15是根据本发明优选实施例的下一跳节点为业务节点情况下的报文处理示意图；
图16是根据本发明优选实施例的下一跳节点为交换节点情况下的报文处理示意图；
图17是根据本发明优选实施例的下一跳节点为业务节点情况下的报文处理流程图；
图18是根据本发明优选实施例的下一跳节点为交换节点情况下的报文处理流程图；
图19是根据本发明优选实施例的设置交换节点端口状态的方式一的流程图；
图20是根据本发明优选实施例的设置交换节点端口状态的方式二的流程图；
图21是根据本发明优选实施例的设置交换节点端口状态的方式三的流程图；
图22是根据本发明优选实施例的交换机不支持业务链路场景下的针对跨域中继节点的处理流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明的实施例一提供了一种业务链路由方法。图5是根据本发明实施例一的业务链路由方法流程图，如图5所示，该方法主要包括以下步骤(步骤S502-步骤S506)：
步骤S502，中继节点接收交换节点转发的第一数据报文，其中，第一数据报文是发送给不支持业务链路由的下一跳节点的报文，中继节点与下一跳节点具有绑定关系；
步骤S504，中继节点确定下一跳节点的类型为业务节点后，删除第一数据报文中的业务链标识；
步骤S506，中继节点将删除了业务链标识的第一数据报文发送给交换节点，以使交换节点根据绑定关系将删除了业务链标识的第一数据报文转发给下一跳节点。
通过上述各个步骤，采用在运营商传统部署的移动增值服务网络中增加设置中继节点，并对其它节点进行功能扩展和定义的方式，可以在不支持业务链路由能力下一跳节点是业务节点时，使用中继节点将交换节点转发的数据报文转发给下一跳业务节点，从而提高了业务链路由成功的概率，健全了业务链路由机制。
在本实施例一中，在步骤S504，中继节点删除第一数据报文中的业务链标识，可以通过这样的方式来实现：中继节点先保存第一数据报文中的地址五元组和业务链标识之间的对应关系，其中，地址五元组包括：目的IP地址、目的端口、源IP地址、源端口以及协议号；中继节点再从第一数据报文中删除业务链标识。
在本实施例一中，在执行步骤S506之后，中继节点还可以接收交换节点转发的第二数据报文，其中，第二数据报文是下一跳节点进行报文处理后返回的报文；中继节点为第二数据报文添加第一数据报文中的业务链标识；中继节点将添加了业务链标识的第二数据报文转发到交换节点。
其中，中继节点为第二数据报文添加第一数据报文中的业务链标识，可以通过这样的方式来实现：中继节点先获取第二数据报文中的地址五元组；中继节点在已经保存的对应关系所属的对应关系集合中，查找第二数据报文中的地址五元组是否存在相应的业务链标识；在查找结果为是的情况下，中继节点把查找到的业务链标识添加到第二数据报文中，从对应关系集合中删除对应关系；在查找结果为否的情况下，中继节点确定下一跳节点进行报文处理时已经修改了地址五元组，从下一跳节点获取第一数据报文中的地址五元组，并根据对应关系获取第一数据报文中的业务链标识，将获取到的业务链标识添加到第二数据报文中。
在本实施例一中，绑定关系可以通过以下两种方式来实现：方式(1)绑定关系是采用预先为交换节点配置或者是由网络控制节点通过向交换节点发送通知的方式，为中继节点和下一跳节点配置的地址隧道绑定关系。方式(2)绑定关系是由网络控制节点通过更改业务链路由信息的方式为中继节点和下一跳节点设置的地址隧道绑定关系。
其中，在方式(2)的实施过程中，在网络控制节点更改业务链路由信息之前，还可以包括：交换节点发现第一数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；交换节点向网络控制节点发送事件上报；网络控制节点根据网络拓扑为下一跳节点分配中继节点，其中，中继节点包括：虚拟机、业务设备、或网络控制节点的内部组件。
本发明的实施例一提供了一种业务链路由系统，设置为实现实施例一提供的业务链路由方法。图6是根据本发明实施例一的业务链路由系统的结构框图，如图6所示，该系统主要包括：业务编排节点10、网络控制节点20、交换节点30、业务节点40、以及中继节点50。
其中，中继节点50可以进一步包括：第一接收模块51，设置为接收交换节点30转发的第一数据报文，其中，第一数据报文是发送给不支持业务链路由的下一跳节点的报文，中继节点50与下一跳节点具有绑定关系；第一处理模块52，设置为确定下一跳节点的类型为业务节点后，删除第一数据报文中的业务链标识；第一发送模块53，设置为将删除了业务链标识的第一数据报文发送给交换节点30，以使交换节点30根据绑定关系将删除了业务链标识的第一数据报文转发给下一跳节点。
在图6所示的业务链路由系统的基础上，本发明实施例一还提供了一种优选业务链路由系统。图7是根据本发明实施例一的优选业务链路由系统的结构框图，如图7所示，在该优选业务链路由系统中，第一处理模块52包括：保存单元522，设置为保 存第一数据报文中的地址五元组和业务链标识之间的对应关系，其中，地址五元组包括：目的IP地址、目的端口、源IP地址、源端口以及协议号；删除单元524，设置为从第一数据报文中删除业务链标识。
在该优选业务链路由系统中，中继节点50还包括：第二接收模块54，设置为接收交换节点30转发的第二数据报文，其中，第二数据报文是下一跳节点进行报文处理后返回的报文；第二处理模块55，设置为为第二数据报文添加第一数据报文中的业务链标识；第二发送模块56，设置为将添加了业务链标识的第二数据报文转发到交换节点30。
进一步地，第二处理模块55可以包括：获取单元552，获取第二数据报文中的地址五元组；查找单元，设置为在已经保存的对应关系所属的对应关系集合中，查找第二数据报文中的地址五元组是否存在相应的业务链标识；第一处理单元554，设置为在查找单元的查找结果为是的情况下，把查找到的业务链标识添加到第二数据报文中，从对应关系集合中删除对应关系；第二处理单元556，设置为在查找单元的查找结果为否的情况下，确定下一跳节点进行报文处理时已经修改了地址五元组，从下一跳节点获取第一数据报文中的地址五元组，并根据对应关系获取第一数据报文中的业务链标识，将获取到的业务链标识添加到第二数据报文中。
优选地，绑定关系可以通过以下两种方式来实现：方式(1)绑定关系是以预先为交换节点30配置的或者是由网络控制节点20通过向交换节点30发送通知的方式，为中继节点50和下一跳节点配置的地址隧道绑定关系。方式(2)绑定关系是由网络控制节点20通过更改业务链路由信息的方式为中继节点50和下一跳节点设置的地址隧道绑定关系。
在该优选业务链路由系统中，交换节点30包括：确定模块32，设置为发现第一数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；发送模块34，设置为向网络控制节点20发送事件上报；网络控制节点20包括：分配模块22，设置为根据网络拓扑为下一跳节点分配中继节点50，其中，中继节点50可以包括：虚拟机、业务设备、或网络控制节点的内部组件。
本发明实施例二提供了一种业务链路由方法。图8是根据本发明实施例二的业务链路由方法流程图，如图8所示，，该方法主要包括以下步骤(步骤S802-步骤S806)：
步骤S802，第一中继节点接收交换节点转发的数据报文，其中，数据报文是发送给不支持业务链路由的下一跳节点的报文，第一中继节点与下一跳节点具有绑定关系；
步骤S804，第一中继节点确定下一跳节点的类型为交换节点后，将第二中继节点的地址信息封装在数据报文中，其中，第二节点与下一跳节点具有绑定关系；
步骤S806，第一中继节点将封装了地址信息的数据报文发送给第二中继节点，以使第二中继节点从接收到的数据报文中删除地址信息后，将删除了地址信息的数据报文转发给支持业务链路由的交换节点。
通过上述各个步骤，采用在运营商传统部署的移动增值服务网络中增加设置中继节点，并对其它节点进行功能扩展和定义的方式，可以在不支持业务链路由能力下一跳节点是交换节点时，使用中继节点将交换节点转发的数据报文转发给下一跳交换节点，从而提高了业务链路由成功的概率，健全了业务链路由机制。
在本实施例二中，在执行步骤S802之前，第一中继节点可以接收由网络控制节点发送的第二中继节点的地址信息。
优选地，在第一中继节点接收由网络控制节点发送的第二中继节点的地址信息之前，还可以包括：交换节点发现数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；交换节点向网络控制节点发送事件上报；网络控制节点根据网络拓扑为下一跳节点分配第一中继节点和第二中继节点，其中，第二中继节点是指与支持业务链路由的交换节点直接相连的中继节点。
在本实施例二中，绑定关系可以通过以下两种方式来实现：方式(1)绑定关系是采用预先为交换节点配置的或者是由网络控制节点通过向交换节点发送通知的方式，为第一中继节点、第二中继节点及下一跳节点配置的地址隧道绑定关系。(2)绑定关系是由网络控制节点通过更改业务链路由信息的方式为第一中继节点、第二中继节点及下一跳节点设置的地址隧道绑定关系。
优选地，当第二中继节点不属于网络控制节点管辖时，网络控制节点可以向管辖第二中继节点的网络控制节点发送分配请求，以获得使用第二中继节点的权利和第二中继节点的地址信息。
本发明的实施例二提供了一种业务链路由系统，设置为实现实施例二提供的业务链路由方法。图9是根据本发明实施例二的业务链路由系统的结构框图，如图9所示，该系统主要包括：业务编排节点10、网络控制节点20、交换节点30、业务节点40、第一中继节点52以及第二中继节点54，其中，第一中继节点52包括：第一接收模块522，设置为接收交换节点30转发的数据报文，其中，数据报文是发送给不支持业务链路由的下一跳节点的报文，第一中继节点52与下一跳节点具有绑定关系；第一处理 模块524，设置为确定下一跳节点的类型为交换节点后，将第二中继节点54的地址信息封装在数据报文中，其中，第二中继节点54与下一跳节点具有绑定关系；第二处理模块526，设置为将封装了地址信息的数据报文发送给第二中继节点54，以使第二中继节点54从接收到的数据报文中删除地址信息后，将删除了地址信息的数据报文转发给支持业务链路由的交换节点30。
在图9所示的业务链路由系统的基础上，本发明实施例二还提供了一种优选业务链路由系统。图10是根据本发明实施例二的优选业务链路由系统的结构框图，如图10所示，第一中继节点52还可以进一步包括：第二接收模块528，设置为接收由网络控制节点20发送的第二中继节点54的地址信息。
优选地，绑定关系可以通过以下两种方式来实现：方式(1)绑定关系是采用预先为交换节点30配置的或者是由网络控制节点20通过向交换节点30发送通知的方式，为第一中继节点52、第二中继节点54及下一跳节点配置的地址隧道绑定关系。(2)绑定关系是由网络控制节点20通过更改业务链路由信息的方式为第一中继节点52、第二中继节点54及下一跳节点设置的地址隧道绑定关系。
在该优选业务链路由系统中，交换节点30包括：确定模块32，设置为发现数据报文中携带业务链标识，根据业务链路由信息确定下一跳节点不支持业务链路由；第一发送模块34，设置为向网络控制节点20发送事件上报；网络控制节点20包括：分配模块22，设置为根据网络拓扑为下一跳节点分配第一中继节点52和第二中继节点54，其中，第二中继节点54是指与支持业务链路由的交换节点30直接相连的中继节点。
优选地，网络控制节点20还进一步包括：第二发送模块24，设置为当第二中继节点54不属于网络控制节点20管辖时，向管辖第二中继节点54的网络控制节点发送分配请求，以获得使用第二中继节点54的权利和第二中继节点的地址信息。
本发明实施例还提供了一种业务编排网元设备。图11是根据本发明实施例的业务编排网元设备的结构框图，如图11所示，该业务编排网元设备可以包括：收集模块10，设置为收集业务链中所有业务节点的业务链路由能力信息；筛选模块20，设置为根据业务链路由能力信息，筛选出不支持业务链路由能力的业务节点；通知模块30，设置为将不支持业务链路由能力的业务节点通知给网络控制网元设备，以使网络控制网元设备根据网络拓扑，将与不支持业务路由能力的业务节点相连的交换节点的端口设置为不支持业务链路由状态。
本发明实施例还提供了一种网络控制网元设备。图12是根据本发明实施例的网络控制网元设备的结构框图，如图12所示，该网络控制网元设备可以包括：收集模块10，设置为收集移动增值服务网络中所有交换节点的业务链路由能力信息；筛选模块20，设置为根据业务链路由能力信息，筛选出不支持业务链路由能力的交换节点；设置模块30，设置为根据网络拓扑，将与不支持业务路由能力的交换节点相连的交换节点的端口设置为不支持业务链路由状态。
本发明实施例还提供了一种交换机。图13是根据本发明实施例的交换机的结构框图，如图13所示，该交换机可以包括：确定模块10，设置为在向下一跳节点转发数据失败或无应答的情况下，确定下一跳节点不支持业务链路由能力；上报模块20，设置为向网络控制网元设备上报设置为指示下一跳节点不支持业务链路由能力的端口状态信息，以使网络控制网元设备根据预定策略和端口状态信息确定下一跳节点确实不支持业务链路由能力；接收模块30，设置为接收网络控制网元设备返回的应答消息，其中，应答消息设置为通知交换机将与下一跳节点相连的端口设置为不支持业务链路由状态；设置模块40，设置为根据应答消息，将与下一跳节点相连的交换机端口设置为不支持业务链路由状态。
采用上述实施例提供的业务链路由方法及系统、业务编排网元设备、网络控制网元设备和/或交换机，可以解决相关技术中移动增值业务网络的传统节点不支持业务链路由机制容易导致业务链路由失败的问题，达到了提高业务链路由成功的概率，健全业务链路由机制的效果。
下面结合图14至图22以及优选实施例对上述实施例提供的业务链路由方法及系统、业务编排网元设备、网络控制网元设备和/或交换机进行更加详细的描述和说明。
优选实施例
图14是根据本发明优选实施例的移动增值服务网络的业务链路由的架构示意图，如图14所示，该架构与背景技术架构(图1所示)相比，主要增加一个中继节点网元，由于本优选不涉及到流分类网元，为了描述简明起见，在本架构中省略流分类网元，本架构主要：
业务编排网元设备，除了负责对业务链串联的业务节点的顺序进行编排，还需要负责收集业务节点的能力信息(主要包括：是否支持业务链路由能力)，并把这些信息传递给网络控制网元设备；
网络控制网元设备，除了负责对移动增值服务网络的网络拓扑和业务链路由表的维护和管理之外，还需要负责为不支持业务链路由的业务节点和交换节点(交换机)指派中继节点；
交换节点(交换机)，除了负责接收数据报文，并根据业务链路由表转发数据报文之外，还需要具备感知下一跳是否支持业务链路由的能力，如果不支持，需要把报文转发至网络控制网元所指派的中继节点；
中继节点，根据网络控制网元告知的下一跳节点的类型执行相应的操作，具体包括：(1)如果下一跳节点的类型为业务节点中，则中继节点将收到的数据报文中携带的地址五元组和业务链标识关系进行保存后，删除数据报文中的业务链标识，再将数据报文交由交换节点转发至下一跳节点；在收到返回的数据报文后，中继节点获取数据报文的五元组，在其之前保存的地址五元组和业务链标识关系中查找对应的业务链标识，查找到，把所对应的业务链标识添加至数据报文中，并删除所存储的五元组和业务链标识对应关系记录，转发数据报文至交换节点。(2)如果下一跳节点的类型为交换节点，第一中继节点获取第二中继节点的地址信息，并把第二中继节点的地址信息封装到数据报文的头部，由第一交换节点将数据报文转发至第二中继节点，由第二中继节点剥离数据报文中所封装的第二中继节点的地址信息，并将数据报文转发至第二交换节点。
图15是根据本发明优选实施例的下一跳节点为业务节点情况下的报文处理示意图，如图15所示，交换节点收到数据报文后根据业务链路由表转发报文时，发现下一跳节点不支持业务链路由，则向网络控制节点上报事件(参见步骤①)；
网络控制选择为下一跳节点服务的中继节点，并告知中继节点下一跳节点的类型(注，如果中继节点仅处理业务节点，则无需网络控制网元设备告知下一跳节点的类型)，然后通过修改交换节点流表，使中继节点与下一跳业务节点进行地址隧道绑定，将发向业务节点的携带业务链标识的数据报文转发至中继节点，中继节点将不携带业务链标识的数据报文转发至业务节点，业务节点返回的数据报文均转发至中继节点(参见步骤②)；
交换节点转发数据报文至中继节点，这时候数据报文携带业务链标识(参见步骤③)；
中继节点收到数据报文，动态保存报文中五元组与业务链标识之间的对应关系，其中五元组指报文中携带的目的IP地址，目的端口，源IP地址，源端口，协议号，删除报文中业务链标识的字段，把报文转发至交换节点(参见步骤④)；
交换节点判断收到的数据报文中无业务链标识，根据中继节点和业务节点的绑定关系，把数据报文转发至业务节点处理(参见步骤⑤)；
业务节点收到报文并处理完毕后返回数据报文(参见步骤⑥)；
交换节点根据业务节点和中继节点的绑定关系，把返回的数据报文返回给中继节点(参见步骤⑦)；
中继节点接收到数据报文后，首先获取数据报文中的地址五元组(可以简称为五元组)，并根据五元组在其保存的五元组与业务链标识的关系表中查找对应的业务链标识，如果查找到，把所对应的业务链标识添加至数据报文中，并删除所存储的五元组和业务链标识对应关系记录，转发所述报文至交换节点；如果没有找到，表明业务节点修改了报文的初始五元组，例如NAT类型业务节点，这时，中继节点需要向业务节点获取初始五元组信息，并根据初始五元组查找关系表，获取业务链标识，获取完同样把业务链标识字段插入到数据报文中，然后转发报文至交换节点(参见步骤8)；
交换节点负责把报文转发至下下跳。
图16是根据本发明优选实施例的下一跳节点为交换节点情况下的报文处理示意图，如图16所示，交换节点收到数据报文根据业务链路由表转发报文时，发现下一跳节点不支持业务链路由，则向网络控制节点上报事件(参见步骤①)；
网络控制网元设备选择为下一跳节点服务的第一中继节点(包括第一中继节点和第二中继节点)，首先获取第二中继节点地址信息，这里的第二中继节点是指可以直连后续支持业务链路由交换节点的中继节点，其获取方法可分两种：第一种，第二中继节点属于当前的网络控制网元设备管辖，则网络控制网元设备根据网络拓扑及交换节点能力，选择第二中继节点；第二种，第二中继节点可能不属于当前的网络控制网元设备管辖(称之为网络控制网设备1)，网络控制网元设备1需要向网络控制网元设备2(第二中继节点所属的网络控制网元设备)请求分配第二中继节点(详细见图22)。网络控制网设备1获取中继节点2(即第二中继节点)地址信息传递给中继节点1(即第一中继节点)，然后通过修改交换节点流表，使中继节点1和中继节点2与下一跳业务节点进行地址隧道绑定，发向业务节点的携带业务链标识的数据报文转发至中继节点1，中继节点1下发不携带业务链标识报文转发至业务节点，业务节点返回的数据报文均转发至中继节点1(参见步骤②)；
交换节点转发数据报文至第一中继节点，这时候数据报文携带业务链标识(参见步骤③)；
第一中继节点收到数据报文，在报文前封装第二中继节点地址信息，转发报文至交换节点(参见步骤④)；
交换节点转发数据报文至第二中继节点(参见步骤⑤)；
第二中继节点收到数据报文后，剥离本节点地址信息，把报文传递给支持业务链路由的交换机(参见步骤⑥)；
交换节点负责把报文转发至相应的业务节点。
图17是根据本发明优选实施例的下一跳节点为业务节点情况下的报文处理流程图，如图17所示，该流程包括以下步骤：。
S1701、交换节点收到数据报文，发现报文中携带业务链标识，然后根据业务链路由表感知报文转发的下一跳节点不支持业务链路由；
S1702、交换节点向网络控制节点设备发事件上报；
S1703、网络控制节点设备根据网络拓扑，为下一跳节点分配中继节点，该中继节点可以是一个虚拟机实例，或者是一个业务设备，或者网络控制节点内部的一个组件；
这里需要说明的是，如果交换节点已知中继节点存在(例如，网络控制节点已告知交换节点，或者交换节点已静态配置有中继节点(包括内置中继节点))，前三个步骤是不需要的。
S1704、网络控制节点设备更改业务链路由流表，使中继节点与下一跳业务节点进行地址隧道绑定，发向业务节点的携带业务链标识的数据报文转发至中继节点，中继节点将不携带业务链标识的数据报文转发至业务节点，业务节点返回的数据报文均转发至中继节点；
S1705、交换节点根据业务链路由流表，把数据报文转发至中继节点；
S1706、中继节点接收到数据报文后，动态保存报文中的五元组与业务链标识的对应关系(其中，五元组指报文中携带的目的IP地址，目的端口，源IP地址，源端口，协议号)，再删除数据报文中的业务链标识字段，把数据报文转发至交换节点；
S1707、交换节点确定接收收到的数据报文中没有业务链标识，根据中继节点与业务节点的绑定关系，把数据报文转发至业务节点进行处理；
S1708-S1709、业务节点对接收到数据报文进行处理完毕后返回数据报文，交换节点根据业务节点和中继节点的绑定关系，把返回的数据报文返回给中继节点；
S1710、中继节点收到数据报文后，首先获取数据报文中的五元组，并根据五元组在其保存的地址五元组和业务链标识关系表中查找对应的业务链标识，如果查找到，把所对应的业务链标识添加至数据报文中，并删除所存储的五元组和业务链标识对应关系记录，转发数据报文至交换节点，如果没有找到，表明业务节点修改了报文的初始五元组(例如，NAT类型业务节点)，这时，中继节点需要向业务节点获取初始五元组信息，并根据初始五元组查找关系表，获取业务链标识，获取后同样把业务链标识字段插入到数据报文中，然后转发数据报文至交换节点，有交换节点转发报文至下下跳节点。
图18是根据本发明优选实施例的下一跳节点为交换节点情况下的报文处理流程图，如图18所示，该流程包括以下步骤：
S1801、交换节点接收到数据报文后，根据业务链路由表转发报文时发现下一跳节点不支持业务链路由；
S1802、交换节点向网络控制节点设备上报事件步骤；
S1803、网络控制节点设备选择为下一跳节点服务的中继节点，获取第二中继节点地址信息，这里的第二中继节点是指可以直连后续支持业务链路由交换节点中继节点，其获取方法可分两种：第一种，第二中继节点属于网络控制节点设备管辖，网络控制节点设备根据网络拓扑及交换节点能力，选择第二中继节点，第二种，第二中继节点可能不属于网络控制节点设备管辖，网络控制1需要向网络控制2请求分配第二中继节点(详细见图22)；
这里需要说明的是，如果交换节点已知中继节点(如网络控制节点已告知交换节点，或者交换节点已静态配置有中继节点(包括内置中继节点))，前述三个步骤是不需要的。
S1804、网络控制节点设备获取中继节点2的地址信息并传递给中继节点1；
S1805、通过修改交换节点流表，使中继节点与下一跳业务节点进行地址隧道绑定，发向业务节点的携带业务链标识的数据报文转发至中继节点，中继节点将不携带业务链标识的数据报文转发至业务节点，业务节点返回的数据报文均转发至中继节点；
S1806、交换节点转发数据报文至中继节点1(此时数据报文携带业务链标识)；
S1807、中继节点接收到数据报文后，在数据报文前封装第二中继节点的地址信息，并转发报文至交换节点；
S1808、交换节点转发数据报文至第二中继节点；
S1809、第二中继节点接收到数据报文后，剥离本节点地址信息，并把数据报文传递给支持业务链路由的交换机，交换节点负责把数据报文转发至相应的业务节点。
图19是根据本发明优选实施例的设置交换节点端口状态的方式一的流程图，该方式一用于使交换机能够感知下一跳节点是否支持业务链路由能力，如图19所示，该流程包括以下步骤：
S1901、业务编排节点收集各业务节点的能力；
S1902、筛选出哪些节点不支持业务路由，并告知网络控制节点；
S1903、网络控制节点根据网络拓扑，把与不具备业务链路由能力的业务节点相连的交换机端口设置为“不支持业务链路由状态”，当交换机根据业务链路由表查找，发现出口端口状态为“不支持业务链路由状态”时，触发图17/18所示的流程；
S1904、网络控制节点返回上报业务节点能力信息应答。
图20是根据本发明优选实施例的设置交换节点端口状态的方式二的流程图，该方式二用于由网络控制节点感知交换节点的下一跳交换机是否支持业务链路由能力，如图20所示，该流程包括以下步骤：
S2001、网络控制节点收集网络中各交换节点的能力信息，筛选出不支持业务链路由的交换机；
S2002、网络控制节点根据网络拓扑，把与不具备业务链路由能力的交换节点相连的交换机端口设置为“不支持业务链路由状态”。
图21是根据本发明优选实施例的设置交换节点端口状态的方式三的流程图，该方式三用于由交换节点感知下一跳是否支持业务链路由能力，如图21所示，该流程包括以下步骤：
S2101、交换节点在数据转发时，感知下一跳不支持业务链路由(例如，数据发送无应答或发送失败)；
S2102、交换节点向网络控制节点上报端口状态信息，告知网络控制节点下一跳业务链路由失败；
S2103、网络控制节点根据策略(例如，失败次数门限)，确定交换节点上报的下一跳确实不支持业务链路由，则回应答消息，通知交换节点将端口设置为“不支持业务链路由状态”。
图22是根据本发明优选实施例的交换机不支持业务链路场景下的针对跨域中继节点的处理流程图，如图22所示，该流程包括以下步骤：
S2201、业务域1网络控制节点1收到交换节点上报下一跳不支持业务链路由，则先指派本域的中继节点1；
S2202、向域2的网络控制节点2请求分配中继节点；
S2203、域2的网络控制节点2分配中继节点2；
S2204、并告知中继节点1的信息(本步骤为可选步骤)；
S2205、返回请求应答，携带中继节点2地址信息；
S2206、网络控制节点1把收集的中继节点2的地址信息告知中继节点1。
需要说明的是，上述各个模块是可以通过硬件来实现的。例如：一种处理器，包括上述各个模块，或者，上述各个模块分别位于一个处理器中。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及优选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
从以上的描述中，可以看出，本发明实现了如下技术效果：采用在运营商传统部署的移动增值服务网络中增加设置中继节点，并对其它节点进行功能扩展和定义的方式，可以在不支持业务链路由能力下一跳节点是业务节点时，使用中继节点将交换节点转发的数据报文转发给下一跳业务节点，在不支持业务链路由能力下一跳节点是交换节点时，使用中继节点将交换节点转发的数据报文转发给下一跳交换节点，进而达到了提高业务链路由成功的概率，健全业务链路由机制的效果。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供了一种业务链路由方法及系统、及系统中的设备，具有以下有益效果：可以在不支持业务链路由能力下一跳节点是业务节点时，使用中继节点将交换节点转发的数据报文转发给下一跳业务节点，在不支持业务链路由能力下一跳节点是交换节点时，使用中继节点将交换节点转发的数据报文转发给下一跳交换节点，进而达到了提高业务链路由成功的概率，健全业务链路由机制的效果。

Claims (29)

  1. 一种业务链路由方法，包括：
    中继节点接收交换节点转发的第一数据报文，其中，所述第一数据报文是发送给不支持业务链路由的下一跳节点的报文，所述中继节点与所述下一跳节点具有绑定关系；
    所述中继节点确定所述下一跳节点的类型为业务节点后，删除所述第一数据报文中的业务链标识；
    所述中继节点将删除了业务链标识的第一数据报文发送给所述交换节点，以使所述交换节点根据所述绑定关系将删除了所述业务链标识的第一数据报文转发给所述下一跳节点。
  2. 根据权利要求1所述的方法，其中，所述中继节点删除所述第一数据报文中的业务链标识，包括：
    所述中继节点保存所述第一数据报文中的地址五元组和所述业务链标识之间的对应关系，其中，所述地址五元组包括：目的IP地址、目的端口、源IP地址、源端口以及协议号；
    所述中继节点从所述第一数据报文中删除所述业务链标识。
  3. 根据权利要求2所述的方法，其中，在所述中继节点将删除了业务链标识的第一数据报文发送给所述交换节点之后，包括：
    所述中继节点接收所述交换节点转发的第二数据报文，其中，所述第二数据报文是所述下一跳节点进行报文处理后返回的报文；
    所述中继节点为所述第二数据报文添加所述第一数据报文中的业务链标识；
    所述中继节点将添加了业务链标识的第二数据报文转发到所述交换节点。
  4. 根据权利要求3所述的方法，其中，所述中继节点为所述第二数据报文添加所述第一数据报文中的业务链标识，包括：
    所述中继节点获取所述第二数据报文中的地址五元组；
    所述中继节点在已经保存的所述对应关系所属的对应关系集合中，查找所述第二数据报文中的地址五元组是否存在相应的业务链标识；
    在查找结果为是的情况下，所述中继节点把查找到的业务链标识添加到所述第二数据报文中，从所述对应关系集合中删除所述对应关系；
    在查找结果为否的情况下，所述中继节点确定所述下一跳节点进行报文处理时已经修改了地址五元组，从所述下一跳节点获取所述第一数据报文中的地址五元组，并根据所述对应关系获取所述第一数据报文中的业务链标识，将获取到的业务链标识添加到所述第二数据报文中。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述绑定关系是采用预先为交换节点配置或者是由网络控制节点通过向交换节点发送通知的方式，为所述中继节点和所述下一跳节点配置的地址隧道绑定关系。
  6. 根据权利要求1至4中任一项所述的方法，其中，所述绑定关系是由网络控制节点通过更改业务链路由信息的方式为所述中继节点和所述下一跳节点设置的地址隧道绑定关系。
  7. 根据权利要求6所述的方法，其中，在所述网络控制节点更改所述业务链路由信息之前，包括：
    所述交换节点发现所述第一数据报文中携带业务链标识，根据所述业务链路由信息确定所述下一跳节点不支持业务链路由；
    所述交换节点向所述网络控制节点发送事件上报；
    所述网络控制节点根据网络拓扑为所述下一跳节点分配中继节点，其中，所述中继节点包括：虚拟机、业务设备、或网络控制节点的内部组件。
  8. 一种业务链路由系统，包括：业务编排节点、网络控制节点、交换节点、业务节点、以及中继节点，所述中继节点包括：
    第一接收模块，设置为接收所述交换节点转发的第一数据报文，其中，所述第一数据报文是发送给不支持业务链路由的下一跳节点的报文，所述中继节点与所述下一跳节点具有绑定关系；
    第一处理模块，设置为确定所述下一跳节点的类型为业务节点后，删除所述第一数据报文中的业务链标识；
    第一发送模块，设置为将删除了业务链标识的第一数据报文发送给所述交换节点，以使所述交换节点根据所述绑定关系将删除了所述业务链标识的第一数据报文转发给所述下一跳节点。
  9. 根据权利要求8所述的系统，其中，所述第一处理模块包括：
    保存单元，设置为保存所述第一数据报文中的地址五元组和所述业务链标识之间的对应关系，其中，所述地址五元组包括：目的IP地址、目的端口、源IP地址、源端口以及协议号；
    删除单元，设置为从所述第一数据报文中删除所述业务链标识。
  10. 根据权利要求9所述的系统，其中，所述中继节点还包括：
    第二接收模块，设置为接收所述交换节点转发的第二数据报文，其中，所述第二数据报文是所述下一跳节点进行报文处理后返回的报文；
    第二处理模块，设置为为所述第二数据报文添加所述第一数据报文中的业务链标识；
    第二发送模块，设置为将添加了业务链标识的第二数据报文转发到所述交换节点。
  11. 根据权利要求10所述的系统，其中，所述第二处理模块包括：
    获取单元，获取所述第二数据报文中的地址五元组；
    查找单元，设置为在已经保存的所述对应关系所属的对应关系集合中，查找所述第二数据报文中的地址五元组是否存在相应的业务链标识；
    第一处理单元，设置为在所述查找单元的查找结果为是的情况下，把查找到的业务链标识添加到所述第二数据报文中，从所述对应关系集合中删除所述对应关系；
    第二处理单元，设置为在所述查找单元的查找结果为否的情况下，确定所述下一跳节点进行报文处理时已经修改了地址五元组，从所述下一跳节点获取所述第一数据报文中的地址五元组，并根据所述对应关系获取所述第一数据报文中的业务链标识，将获取到的业务链标识添加到所述第二数据报文中。
  12. 根据权利要求8至11中任一项所述的系统，其中，所述绑定关系是以预先为交换节点配置的或者是由网络控制节点通过向交换节点发送通知的方式，为所述中继节点和所述下一跳节点配置的地址隧道绑定关系。
  13. 根据权利要求8至11中任一项所述的系统，其中，所述绑定关系是由网络控制节点通过更改业务链路由信息的方式为所述中继节点和所述下一跳节点设置的地址隧道绑定关系。
  14. 根据权利要求13所述的系统，其中，
    所述交换节点包括：
    确定模块，设置为发现所述第一数据报文中携带业务链标识，根据所述业务链路由信息确定所述下一跳节点不支持业务链路由；发送模块，设置为向所述网络控制节点发送事件上报；
    所述网络控制节点包括：
    分配模块，设置为根据网络拓扑为所述下一跳节点分配中继节点，其中，所述中继节点包括：虚拟机、业务设备、或网络控制节点的内部组件。
  15. 一种业务链路由方法，包括：
    第一中继节点接收交换节点转发的数据报文，其中，所述数据报文是发送给不支持业务链路由的下一跳节点的报文，所述第一中继节点与所述下一跳节点具有绑定关系；
    所述第一中继节点确定所述下一跳节点的类型为交换节点后，将第二中继节点的地址信息封装在所述数据报文中，其中，所述第二中继节点与所述下一跳节点具有绑定关系；
    所述第一中继节点将封装了地址信息的数据报文发送给所述第二中继节点，以使所述第二中继节点从接收到的数据报文中删除所述地址信息后，将删除了所述地址信息的数据报文转发给支持业务链路由的交换节点。
  16. 根据权利要求15所述的系统，其中，在第一中继节点接收交换节点转发的数据报文之前，包括：
    所述第一中继节点接收由网络控制节点发送的所述第二中继节点的地址信息。
  17. 根据权利要求15或16所述的方法，其中，所述绑定关系是采用预先为交换节点配置的或者是由网络控制节点通过向交换节点发送通知的方式，为所述第一中继节点、所述第二中继节点及所述下一跳节点配置的地址隧道绑定关系。
  18. 根据权利要求15或16所述的方法，其中，所述绑定关系是由网络控制节点通过更改业务链路由信息的方式为所述第一中继节点、所述第二中继节点及所述下一跳节点设置的地址隧道绑定关系。
  19. 根据权利要求18所述的方法，其中，在所述第一中继节点接收由网络控制节点发送的所述第二中继节点的地址信息之前，包括：
    所述交换节点发现所述数据报文中携带业务链标识，根据所述业务链路由信息确定所述下一跳节点不支持业务链路由；
    所述交换节点向所述网络控制节点发送事件上报；
    所述网络控制节点根据网络拓扑为所述下一跳节点分配所述第一中继节点和所述第二中继节点，其中，第二中继节点是指与支持业务链路由的交换节点直接相连的中继节点。
  20. 根据权利要求19所述的方法，其中，当所述第二中继节点不属于所述网络控制节点管辖时，所述网络控制节点向管辖所述第二中继节点的网络控制节点发送分配请求，以获得使用所述第二中继节点的权利和所述第二中继节点的地址信息。
  21. 一种业务链路由系统，包括：业务编排节点、网络控制节点、交换节点、业务节点、第一中继节点以及第二中继节点，所述第一中继节点包括：
    第一接收模块，设置为接收交换节点转发的数据报文，其中，所述数据报文是发送给不支持业务链路由的下一跳节点的报文，所述第一中继节点与所述下一跳节点具有绑定关系；
    第一处理模块，设置为确定所述下一跳节点的类型为交换节点后，将第二中继节点的地址信息封装在所述数据报文中，其中，所述第二中继节点与所述下一跳节点具有绑定关系；
    第二处理模块，设置为将封装了地址信息的数据报文发送给所述第二中继节点，以使所述第二中继节点从接收到的数据报文中删除所述地址信息后，将删除了所述地址信息的数据报文转发给支持业务链路由的交换节点。
  22. 根据权利要求21所述的系统，其中，所述第一中继节点还包括：
    第二接收模块，设置为接收由网络控制节点发送的所述第二中继节点的地址信息。
  23. 根据权利要求21或22所述的系统，其中，所述绑定关系是采用预先为交换节点配置的或者是由网络控制节点通过向交换节点发送通知的方式，为所述第一中继节点、所述第二中继节点及所述下一跳节点配置的地址隧道绑定关系。
  24. 根据权利要求21或22所述的系统，其中，所述绑定关系是由网络控制节点通过更改业务链路由信息的方式为所述第一中继节点、所述第二中继节点及所述下一跳节点设置的地址隧道绑定关系。
  25. 根据权利要求24所述的系统，其中，
    所述交换节点包括：
    确定模块，设置为发现所述数据报文中携带业务链标识，根据所述业务链路由信息确定所述下一跳节点不支持业务链路由；第一发送模块，设置为向所述网络控制节点发送事件上报；
    所述网络控制节点包括：
    分配模块，设置为根据网络拓扑为所述下一跳节点分配所述第一中继节点和所述第二中继节点，其中，第二中继节点是指与支持业务链路由的交换节点直接相连的中继节点。
  26. 根据权利要求25所述的系统，其中，所述网络控制节点还包括：
    第二发送模块，设置为当所述第二中继节点不属于所述网络控制节点管辖时，向管辖所述第二中继节点的网络控制节点发送分配请求，以获得使用所述第二中继节点的权利和所述第二中继节点的地址信息。
  27. 一种业务编排网元设备，包括：
    收集模块，设置为收集业务链中所有业务节点的业务链路由能力信息；
    筛选模块，设置为根据所述业务链路由能力信息，筛选出不支持业务链路由能力的业务节点；
    通知模块，设置为将所述不支持业务链路由能力的业务节点通知给网络控制网元设备，以使所述网络控制网元设备根据网络拓扑，将与所述不支持业务路由能力的业务节点相连的交换节点的端口设置为不支持业务链路由状态。
  28. 一种网络控制网元设备，包括：
    收集模块，设置为收集移动增值服务网络中所有交换节点的业务链路由能力信息；
    筛选模块，设置为根据所述业务链路由能力信息，筛选出不支持业务链路由能力的交换节点；
    设置模块，设置为根据网络拓扑，将与所述不支持业务路由能力的交换节点相连的交换节点的端口设置为不支持业务链路由状态。
  29. 一种交换机，包括：
    确定模块，设置为在向下一跳节点转发数据失败或无应答的情况下，确定所述下一跳节点不支持业务链路由能力；
    上报模块，设置为向网络控制网元设备上报设置为指示所述下一跳节点不支持业务链路由能力的端口状态信息，以使所述网络控制网元设备根据预定策略和所述端口状态信息确定所述下一跳节点确实不支持业务链路由能力；
    接收模块，设置为接收所述网络控制网元设备返回的应答消息，其中，所述应答消息设置为通知所述交换机将与所述下一跳节点相连的端口设置为不支持业务链路由状态；
    设置模块，设置为根据所述应答消息，将与所述下一跳节点相连的交换机端口设置为不支持业务链路由状态。
PCT/CN2014/086062 2014-04-04 2014-09-05 业务链路由方法及系统、及系统中的设备 WO2015149481A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US15/300,964 US10305822B2 (en) 2014-04-04 2014-09-05 Service chain routing method and system, and equipment in system
JP2016559847A JP2017510208A (ja) 2014-04-04 2014-09-05 サービスチェインルーティング方法とシステム及びシステムにおける機器
EP18192031.5A EP3425856A1 (en) 2014-04-04 2014-09-05 Service chain routing method and system
EP14888198.0A EP3128701A4 (en) 2014-04-04 2014-09-05 Method and system for service chain routing and device in system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410136043.2 2014-04-04
CN201410136043.2A CN104980348A (zh) 2014-04-04 2014-04-04 业务链路由方法及系统、及系统中的设备

Publications (1)

Publication Number Publication Date
WO2015149481A1 true WO2015149481A1 (zh) 2015-10-08

Family

ID=54239359

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/086062 WO2015149481A1 (zh) 2014-04-04 2014-09-05 业务链路由方法及系统、及系统中的设备

Country Status (5)

Country Link
US (1) US10305822B2 (zh)
EP (2) EP3425856A1 (zh)
JP (1) JP2017510208A (zh)
CN (1) CN104980348A (zh)
WO (1) WO2015149481A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017147601A (ja) * 2016-02-17 2017-08-24 日本電信電話株式会社 通信装置および通信方法
CN110516915A (zh) * 2019-08-02 2019-11-29 阿里巴巴集团控股有限公司 业务节点训练、评估方法、装置及电子设备
CN115242885A (zh) * 2022-07-15 2022-10-25 天翼云科技有限公司 云数据中心系统、数据报文传输方法、设备和介质

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9225638B2 (en) 2013-05-09 2015-12-29 Vmware, Inc. Method and system for service switching using service tags
US9531590B2 (en) 2014-09-30 2016-12-27 Nicira, Inc. Load balancing across a group of load balancers
US10021213B2 (en) * 2015-02-09 2018-07-10 Google Llc Systems and methods for adaptive cloning of mobile devices
US10805181B2 (en) 2017-10-29 2020-10-13 Nicira, Inc. Service operation chaining
US10805192B2 (en) 2018-03-27 2020-10-13 Nicira, Inc. Detecting failure of layer 2 service using broadcast messages
US11595250B2 (en) 2018-09-02 2023-02-28 Vmware, Inc. Service insertion at logical network gateway
US11288088B2 (en) 2019-02-22 2022-03-29 Vmware, Inc. Service control plane messaging in service data plane
US11140218B2 (en) * 2019-10-30 2021-10-05 Vmware, Inc. Distributed service chain across multiple clouds
US11659061B2 (en) 2020-01-20 2023-05-23 Vmware, Inc. Method of adjusting service function chains to improve network performance
US11368387B2 (en) 2020-04-06 2022-06-21 Vmware, Inc. Using router as service node through logical service plane
US11611625B2 (en) 2020-12-15 2023-03-21 Vmware, Inc. Providing stateful services in a scalable manner for machines executing on host computers
US11734043B2 (en) 2020-12-15 2023-08-22 Vmware, Inc. Providing stateful services in a scalable manner for machines executing on host computers
CN113328956B (zh) * 2021-06-07 2022-07-01 新华三技术有限公司 一种报文处理方法及装置
CN114900458B (zh) * 2022-03-22 2024-01-09 阿里云计算有限公司 报文转发方法、设备、介质及产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360042A (zh) * 2007-08-01 2009-02-04 中国电信股份有限公司 可运营p2p网络应用路由系统及其路由实现方法
JP4630360B2 (ja) * 2008-08-21 2011-02-09 日本電信電話株式会社 通信システムおよび通信方法
CN102238059A (zh) * 2010-04-20 2011-11-09 中兴通讯股份有限公司 数据报文处理方法、系统及接入服务节点
CN102571856A (zh) * 2010-12-17 2012-07-11 中国移动通信集团公司 一种中转节点的选择方法、设备和系统

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020110087A1 (en) 2001-02-14 2002-08-15 David Zelig Efficient setup of label-switched connections
US7821930B2 (en) 2005-09-12 2010-10-26 Microsoft Corporation Fault-tolerant communications in routed networks
US20070109991A1 (en) * 2005-11-14 2007-05-17 Broadcom Corporation, A California Corporation Access point supporting direct and indirect downstream delivery based on communication characteristics
US20070242675A1 (en) * 2006-04-13 2007-10-18 David Romrell Dual scheduling for efficient network traffic management
US7830883B1 (en) * 2006-12-19 2010-11-09 World Wide Packets, Inc. Modifying duplicate packets to have different transport formats
US8078664B2 (en) * 2008-01-07 2011-12-13 Computer Associates Think, Inc. Evaluation of current capacity levels of resources in a distributed computing system
US8180896B2 (en) * 2008-08-06 2012-05-15 Edgecast Networks, Inc. Global load balancing on a content delivery network
US7860100B2 (en) * 2008-10-01 2010-12-28 Cisco Technology, Inc. Service path selection in a service network
US8526435B2 (en) * 2010-03-19 2013-09-03 Telefonaktiebolaget L M Ericsson (Publ) Packet node for applying service path routing at the MAC layer
CN107483345B (zh) * 2012-07-11 2020-09-11 华为技术有限公司 业务处理方法、设备及系统
US8989192B2 (en) * 2012-08-15 2015-03-24 Futurewei Technologies, Inc. Method and system for creating software defined ordered service patterns in a communications network
US9036476B2 (en) * 2012-09-28 2015-05-19 Juniper Networks, Inc. Maintaining load balancing after service application with a network device
US9258243B2 (en) * 2013-05-10 2016-02-09 Cisco Technology, Inc. Symmetric service chain binding
EP2993836B1 (en) * 2013-06-14 2020-02-19 Huawei Technologies Co., Ltd. Method and device for routing data message
US9203765B2 (en) * 2013-08-30 2015-12-01 Cisco Technology, Inc. Flow based network service insertion using a service chain identifier
US9385950B2 (en) * 2013-10-14 2016-07-05 Cisco Technology, Inc. Configurable service proxy local identifier mapping
EP3063923B1 (en) * 2013-10-29 2019-10-16 Telefonaktiebolaget LM Ericsson (publ) Control of a chain of services
US9467382B2 (en) * 2014-02-03 2016-10-11 Cisco Technology, Inc. Elastic service chains
US9967175B2 (en) * 2014-02-14 2018-05-08 Futurewei Technologies, Inc. Restoring service functions after changing a service chain instance path

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360042A (zh) * 2007-08-01 2009-02-04 中国电信股份有限公司 可运营p2p网络应用路由系统及其路由实现方法
JP4630360B2 (ja) * 2008-08-21 2011-02-09 日本電信電話株式会社 通信システムおよび通信方法
CN102238059A (zh) * 2010-04-20 2011-11-09 中兴通讯股份有限公司 数据报文处理方法、系统及接入服务节点
CN102571856A (zh) * 2010-12-17 2012-07-11 中国移动通信集团公司 一种中转节点的选择方法、设备和系统

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017147601A (ja) * 2016-02-17 2017-08-24 日本電信電話株式会社 通信装置および通信方法
CN110516915A (zh) * 2019-08-02 2019-11-29 阿里巴巴集团控股有限公司 业务节点训练、评估方法、装置及电子设备
CN115242885A (zh) * 2022-07-15 2022-10-25 天翼云科技有限公司 云数据中心系统、数据报文传输方法、设备和介质
CN115242885B (zh) * 2022-07-15 2023-10-13 天翼云科技有限公司 云数据中心系统、数据报文传输方法、设备和介质

Also Published As

Publication number Publication date
EP3425856A1 (en) 2019-01-09
US10305822B2 (en) 2019-05-28
US20170034080A1 (en) 2017-02-02
EP3128701A1 (en) 2017-02-08
JP2017510208A (ja) 2017-04-06
CN104980348A (zh) 2015-10-14
EP3128701A4 (en) 2017-10-11

Similar Documents

Publication Publication Date Title
WO2015149481A1 (zh) 业务链路由方法及系统、及系统中的设备
US10715634B2 (en) System and method for creating virtual interfaces based on network characteristics
US10750387B2 (en) Configuration of rules in a network visibility system
US10348571B2 (en) Methods and apparatus for accessing dynamic routing information from networks coupled to a wide area network (WAN) to determine optimized end-to-end routing paths
US20210160181A1 (en) Architecture for a network visibility system
US10057126B2 (en) Configuration of a network visibility system
US10530688B2 (en) Configuration of load-sharing components of a network visibility router in a network visibility system
CN109660442B (zh) Overlay网络中组播复制的方法及装置
CN107483345B (zh) 业务处理方法、设备及系统
CN113497754B (zh) 转发路径建立方法、装置以及计算机可读存储介质
WO2021093465A1 (zh) 发送报文、接收报文以进行oam的方法、装置及系统
US20060268853A1 (en) Methods and apparatus for distributing label information
US20230067091A1 (en) Method and device for segment routing service processing, routing equipment, and storage medium
US20180139099A1 (en) Virtualized Networking Application and Infrastructure
CN105337746A (zh) 一种组播数据的传输方法和装置
CN103188153B (zh) 一种广播网链路上bfd报文发送方法和设备
EP3503484A1 (en) Message transmission method, device and network system
CN106230730B (zh) 一种组播传输方法和装置
CN111865805B (zh) 一种组播gre报文处理方法及系统
CN106559838B (zh) 业务处理优化方法及装置
CN113364683A (zh) 一种路由发送方法及设备
JP6593886B2 (ja) 高速アップロードシステム及びその再送制御方法並びにプログラム
CN105721313B (zh) 数据传输方法及相关设备
CN103139084A (zh) 分布式通信设备中主控卡获取组播流量方法和装置
JP6007599B2 (ja) 通信システム、中継装置、中継方法、及び中継プログラム

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: 14888198

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016559847

Country of ref document: JP

Kind code of ref document: A

REEP Request for entry into the european phase

Ref document number: 2014888198

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15300964

Country of ref document: US

Ref document number: 2014888198

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE