WO2017107814A1 - 一种传播QoS策略的方法、装置及系统 - Google Patents

一种传播QoS策略的方法、装置及系统 Download PDF

Info

Publication number
WO2017107814A1
WO2017107814A1 PCT/CN2016/109682 CN2016109682W WO2017107814A1 WO 2017107814 A1 WO2017107814 A1 WO 2017107814A1 CN 2016109682 W CN2016109682 W CN 2016109682W WO 2017107814 A1 WO2017107814 A1 WO 2017107814A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
bgp
network device
policy
route
Prior art date
Application number
PCT/CN2016/109682
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 华为技术有限公司
Publication of WO2017107814A1 publication Critical patent/WO2017107814A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • 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/302—Route determination based on requested QoS

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, device, and system for propagating a quality of service (QoS) policy.
  • QoS quality of service
  • Border Gateway Protocol is a dynamic routing protocol used between autonomous systems (ASs).
  • ASs autonomous systems
  • QoS Quality of Service
  • QPPB Border Gateway Protocol
  • the QoS Policy Propagation Through the Border Gateway Protocol (QPPB) technology can be used to classify routes by BGP route senders by setting BGP attributes. This simplifies the policy modification of route receivers.
  • the BGP routing policy can meet the requirements.
  • the implementation mechanism of the QPPB is as follows:
  • the BGP route can carry the route attribute in the notification process.
  • the BGP route matches the routing policy and sets different BGP route attributes for the different routing information.
  • the BGP routing attributes include the AS path and the community attribute.
  • the BGP route attribute is used as the identifier of the BGP route classification.
  • the receiving end matches the BGP route attribute through the ingress routing policy, matches the routing policy based on the route attribute information, sets the QoS parameters for the received BGP route, and delivers the BGP route and the associated QoS parameters to the BGP route.
  • Forward Information Base FIB
  • the data packets sent to the destination network segment can use different QoS policies according to the QoS parameters such as the Internet Protocol (IP) priority, the QoS local identifier, and the traffic behavior name obtained from the FIB.
  • IP Internet Protocol
  • the QoS local identifier the QoS local identifier
  • the traffic behavior name obtained from the FIB.
  • the BGP FlowSpec (BGP FlowSpec) delivers the traffic policy to the BGP FlowSpec peer by passing the BGP FlowSpec route.
  • the traffic control action is applied to the traffic that meets the filtering conditions.
  • the BGP FlowSpec peer After receiving the BGP FlowSpec route, the BGP FlowSpec peer converts the preferred BGP FlowSpec route to the forwarding plane's traffic control policy, thereby limiting the Denial of Service (DoS)/Distributed Denial Service (Distributed Denial). Of service, DDoS) Traffic from the attack source.
  • DoS Denial of Service
  • DDoS Distributed Denial Service
  • the inventor has found that the existing QPPB has the following problems: When the QoS policy needs to be changed, it is necessary to implement a pre-change of the QoS policy at the receiving end, especially when there are multiple receiving ends, and multiple receiving ends are required. Implementing the pre-change of the QoS policy separately increases the configuration of the QPPB, which is prone to errors and is not conducive to post-maintenance.
  • the embodiments of the present application provide a method, a device, and a system for propagating a QoS policy, so as to solve the problem that a large amount of QPPB configuration is required to implement a pre-change of a QoS policy for multiple receivers when implementing QPPB. It is easy to make mistakes and is not conducive to the problems of later maintenance.
  • a method for propagating a QoS policy comprising:
  • first information includes one or more of the following: an AS number list, a community list;
  • the first information is carried in the BGP route attribute information
  • the sending the first information and the first QoS policy to the first network device includes: sending the information to the first network device BGP Update Message, the BGP update message includes the BGP route attribute information and the first QoS policy.
  • the BGP update message carries No-Advertise; the foregoing is configured to the first network
  • the step of transmitting the first information and the first QoS policy further includes: sending the BGP update message to a second network device in the AS.
  • the BGP update message carries a route filtering identifier, where the route filtering identifier is used to indicate that the BGP update message carries the BGP route attribute information and the first QoS policy.
  • the step of sending the first information and the first QoS policy to the first network device includes: sending a BGP FlowSpec Update Message to the first network device, where The BGP FlowSpec update message includes the first information and the first QoS policy.
  • the BGP FlowSpec update message carries No-Advertise; the step of sending the first information and the first QoS policy to the first network device further includes: sending to a second network in the AS The device sends the BGP FlowSpec update message.
  • a method for propagating a QoS policy comprising:
  • the first network device in the AS sends a BGP route to the policy centralized control device
  • the first network device receives first information from the policy centralized control device and a first QoS policy corresponding to the first information, where the first information is generated according to the BGP route, and the first information includes One or more of the following: an AS number list, a community list, the first QoS policy is generated according to the first information, and the first QoS policy includes a route filtering action;
  • the first network device forwards the first information and the first QoS policy to a second network device.
  • the first information is carried in the BGP route attribute information
  • the step of the first network device receiving the first information from the policy centralized control device and the first QoS policy includes: the first network The device receives a BGP update message from the policy centralized control device, where the BGP update message includes the BGP route attribute information and the first QoS policy; the first network device forwards the first to the second network device
  • the information and the first QoS policy step include the first network device forwarding the BGP update message to the second network device.
  • the step of the first network device receiving the first information from the policy centralized control device and the first QoS policy includes: the first network device receiving a BGP FlowSpec update from the policy centralized control device a message, the BGP FlowSpec update message includes the first information and the first QoS policy; and the step of the first network device forwarding the first information and the first QoS policy to the second network device includes: The first network device forwards the BGP FlowSpec update message to the second network device.
  • a method for propagating a QoS policy comprising:
  • the second network device receives the BGP route from the first network device in the AS;
  • the second network device receives first information and a first QoS policy corresponding to the first information, where the first information and the first QoS policy are from a first network device or a centralized policy control in the AS
  • the first information is generated according to the BGP route, and the first information includes one or more of the following: an AS number list, a community list, and the first QoS policy is generated according to the first information, where
  • the first QoS policy includes a route filtering action;
  • the second network device searches for the BGP routing entry that matches the first information in the BGP route.
  • the second network device applies the route filtering action to the FIB entry sent by the BGP routing entry.
  • the first information is carried in the BGP route attribute information; the second network device receives a BGP update message from the first network device, where the BGP update message includes the BGP route attribute information and the Determining a first QoS policy; or the second network device receiving a BGP update message from the policy centralized control device, the BGP update message including the BGP route attribute information, the first QoS policy, and No-Advertise .
  • the second network device receives a BGP FlowSpec update message from the first network device, where the BGP FlowSpec update message includes the first information and the first QoS policy; or, the second The network device receives a BGP FlowSpec update message from the policy centralized control device, where the BGP FlowSpec update message includes the first information, The first QoS policy and No-Advertise.
  • the second network device is configured with the undo local-install command, indicating that the local installation is not performed, specifically indicating that the second network device does not perform the first QoS policy.
  • the first information is carried in a BGP FlowSpec; and optionally, the first information is carried in a network layer reachability information (NLRI) of the BGP FlowSpec; The first information is carried in a medium route filtering component of the NLRI.
  • NLRI network layer reachability information
  • the BGP FlowSpec update message carries a route filtering identifier, where the route filtering identifier is used to indicate that the BGP FlowSpec update message carries the first information and the first QoS policy.
  • the BGP FlowSpec includes a traffic filtering action, where the traffic filtering action includes a specified action, and the specified action carries the route filtering identifier; and optionally, the traffic filtering action carries the route filtering action.
  • a policy centralized control device having a function of implementing the behavior of the policy centralized control device in the above method.
  • the functions may be implemented based on hardware, or may be implemented based on hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a first network device having a function of implementing behavior of a first network device in the foregoing method.
  • the functions may be implemented based on hardware, or may be implemented based on hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the first network device may include a sending unit and a receiving unit to implement the functions of the first network device in the foregoing method, and may also implement the functions of the first network device in the foregoing method by using other functional modules.
  • a second network device having a function of implementing a behavior of the second network device in the foregoing method.
  • the function can be implemented based on hardware or Perform the corresponding software implementation based on hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the second network device may include a sending unit and a receiving unit to implement the functions of the second network device in the foregoing method, and may also implement the functions of the second network device in the foregoing method by using other functional modules.
  • a network system includes a policy centralized control device, a first network device, and a second network device, where the policy centralized control device is the policy centralized control device according to the fourth aspect.
  • the first network device is the first network device according to the fifth aspect
  • the second network device is the second network device according to the sixth aspect.
  • a computer storage medium for storing a program, code or instruction used by the above-mentioned policy centralized control device, and the processor or the hardware device can complete the policy concentration in the above aspect when executing the program, code or instruction.
  • the function or step of the control device is provided for storing a program, code or instruction used by the above-mentioned policy centralized control device, and the processor or the hardware device can complete the policy concentration in the above aspect when executing the program, code or instruction.
  • a computer storage medium for storing a program, code or instruction used by the first network device, and the processor or the hardware device can perform the first of the above aspects when executing the program, code or instruction.
  • the function or step of a network device is provided for storing a program, code or instruction used by the first network device, and the processor or the hardware device can perform the first of the above aspects when executing the program, code or instruction.
  • a computer storage medium for storing a program, code or instruction used by the second network device, and the second network in the foregoing aspect can be completed when the computer or the hardware device executes the program, code or instruction.
  • the function or step of the device is provided.
  • the route filtering action includes at least one of the following actions: re-marking the Internet Protocol IP priority (Remark IP-precedence), re-marking the service type tos (Remark tos), re-marking the experimental bit of the multi-protocol label switching MPLS exp (Remark MPLS-exp) and re-marking the df of the IP (Remark IP-df).
  • the first information is generated according to the received BGP route from the first network device in the AS, where the first information includes one or more of the following: an AS number list, a community list; Generating, by the first information, a first QoS policy corresponding to the first information, where the first QoS policy includes a route filtering action; and sending the first to the first network device Information and the first QoS policy. Therefore, the automatic deployment of the QPPB is implemented, and the pre-change of the QoS policy is not required to be performed on multiple receiving ends respectively, the work of planning the routing classification rule and the configuration of the ingress policy at the transmitting end is omitted, and the matching of the QoS local identifier and the receiving end are omitted.
  • the popular name work simplifies the configuration of QPPB and reduces maintenance difficulty.
  • FIG. 1 is a schematic structural diagram of a cross-AS networking
  • FIG. 2 is a flowchart of a method for propagating a QoS policy according to an embodiment of the present application
  • FIG. 3 is a schematic structural diagram of a first scenario according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a second scenario according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a method for propagating a QoS policy performed by a first network device according to an embodiment of the present application
  • FIG. 6 is a flowchart of a method for propagating a QoS policy performed by a second network device according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of a format of a traffic action extended community attribute according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a policy centralized control apparatus according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a first network device according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a second network device according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of hardware of a policy centralized control apparatus according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of hardware of a first network device according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of hardware of a second network device according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a network system according to an embodiment of the present invention.
  • the embodiment of the present invention provides a method, a device, and a system for propagating a QoS policy, so as to solve the problem that when the QPPB is implemented, the configuration of the QPPB needs to be changed in advance, and the configuration of the QPPB is large and error-prone, which is disadvantageous to the later stage. Maintenance issues.
  • FIG. 1 is a schematic structural diagram of an AS network across an autonomous system.
  • the deployment process of the QPPB is exemplarily described below according to the networking shown in FIG. 1.
  • the network includes ASs AS1 and AS2, where AS1 and AS2 are different autonomous systems.
  • AS2 can be a national backbone network
  • AS1 can be a provincial backbone network.
  • AS2 may include one or more third network devices. It is assumed in the present embodiment that there are two third network devices CR21 and CR22 in AS2.
  • the third network device may be a router or a switch having a Layer 3 function.
  • the third network devices CR21 and CR22 can function as a core router (CR).
  • AS1 may include: a first network device and a second network device.
  • the first network device may be configured with one or more devices, and the second network device may be configured with one or more devices.
  • two first network devices CR11 and CR12 and four second network devices BR111, BR121, BR112, and BR122 are assumed.
  • the first network device may be a router or a switch having a Layer 3 function.
  • the second network device may be a router or a switch having a Layer 3 function.
  • the first network devices CR11 and CR12 can function as CRs; the second network devices BR111, BR121, BR112, and BR122 can function as border routers (BRs).
  • the third network device CR21 communicates with the second network devices BR111 and BR112 via the first network device CR11, and the third network device CR22 communicates with the second network via the first network device CR12.
  • the devices BR121 and BR122 communicate.
  • the first network device CR11 is in communication with the first network device CR12.
  • the second network device BR111 is in communication with the second network device BR121, and the second network device BR112 is in communication with the second network device BR122. It should be understood that the number of devices and the manner of connection of the arrangement shown in FIG. 1 are merely exemplary and should not be construed as limiting.
  • the third network devices CR21 and CR22 have the same role and function in the networking; the first network devices CR11 and CR12 have the same role and function in the networking; the second network devices BR111, BR121, BR112 and BR122 Have the same role and function.
  • the third network device CR21 communicates with the second network device BR111 via the first network device CR11 as an example for description.
  • BGP is deployed on the first network device, the second network device, and the third network device.
  • the BGP route sent by CR21 passes through CR11 and reaches BR111.
  • the QPPB is deployed in the networking shown in Figure 1, that is, the QoS policy is propagated through BGP.
  • the CR11 receives the BGP route from the CR21, and the BGP route can carry the route attribute.
  • the CR11 classifies the BGP route according to the first ingress routing policy, where the first ingress routing policy includes a pre-planned classification rule.
  • This classification rule can be saved on CR11 or on a third party device.
  • the classification rules are set according to actual needs. For example, the classification rule is set as a community attribute, or the classification rule is set as an AS path, or the classification rule is set as a prefix list.
  • the CR11 obtains the AS path information in the BGP route sent by the CR21, sets the value of the community attribute of the BGP route according to the AS path information, and the CR11 records the value of the community attribute in the list of values of the community attribute.
  • the CR11 obtains the community attribute information in the BGP route sent by the CR21, and sets the value of the community attribute of the BGP route according to the community attribute information.
  • the CR11 obtains the AS path information and the community attribute information in the BGP route sent by the CR21, and sets a value of the community attribute of the BGP route according to the AS path information and the community attribute information.
  • CR11 classifies the value of the community attribute as the classification label of the BGP route, and classifies the BGP routes that subsequently reach CR11.
  • the value of the community attribute can be automatically learned. For example, CR11 obtains another BGP route sent by CR21, and finds that the group cannot be used. If the value of the body attribute classifies another BGP route, CR11 sets the value of the community attribute of another BGP route according to the above method, and adds the value of the community attribute of another BGP route to the list of values of the community attribute. . CR11 sends the configured classification rules to BR111.
  • the CR11 can also classify the received BGP routes by using other identifiers, for example, one or more of the AS paths and prefix lists carried by the BGP routes sent by the CR21 to classify the received BGP routes.
  • the AS path is composed of an AS number list, and the AS number list may include an AS_SET (AS set) or an AS_SEQUENSE (AS sequence), and the AS_SET or AS_SEQUENSE may include multiple AS numbers. Where AS_SET represents an unordered list of numbers and AS_SEQUENSE represents an ordered list of numbers.
  • AS path: 10 20 30 70 100 300 200 represents the AS path from operator 1, where 10, 20, 30, 70, 100, 300, 200 are respectively different AS numbers, and these AS numbers are included in AS_SET or AS_SEQUENSE Among them, a list of AS numbers is formed.
  • the BR 111 receives the BGP route forwarded by the CR11, obtains the BGP route attribute in the BGP route, and determines whether a QoS policy corresponding to the BGP route attribute exists in the second ingress routing policy. If there is a QoS policy corresponding to the BGP route attribute, the QoS policy is applied to the BGP route on the BR111.
  • the BGP route attribute is attribute information configured by the route sending end (for example, CR21) according to different operators for BGP routing when sending BGP routes.
  • CR11 delivers the configured classification rule to BR111.
  • the BR 111 obtains the community attribute from the CR 11 and matches the list of values of the community attribute with the QoS policy preset in the BR 111.
  • the specific matching method is as follows: the value of the community attribute and the QoS policy are pre-set in the BR 111.
  • the value 1 of the community attribute corresponds to the QoS policy
  • the value 2 of the community attribute corresponds to the value of the Qos policy 2
  • the value of the community attribute corresponds to n.
  • QoS policy n where n is an integer greater than one.
  • the list of values of the community attribute obtained by the BR 111 from the CR11 includes the value 1 of the community attribute and the value 2 of the community attribute. Therefore, the BR 111 sets the value 1 of the community attribute to the QoS policy 1 and the value 2 of the community attribute corresponds to the QoS policy 2 as the second. Ingress routing policy.
  • the BR 111 receives the BGP route forwarded by the CR11, and if it determines that the BGP route corresponds to the value of the community attribute, the BGP routing configuration QoS policy 1.
  • the BR 111 determines the QoS local identifier corresponding to the community attribute in the QoS policy, and then finds the corresponding traffic behavior name by using the QoS local identifier, where the popularity name identifies the action that needs to be performed.
  • the BR111 sends the BGP route and the associated QoS local identifier and the traffic behavior name to the FIB table, and performs corresponding actions on the BGP route by matching the QoS local identifier and the traffic behavior name.
  • the CR21 sets the routing attribute by the route classification, and the BR111 sets the QoS policy according to the routing attribute of the destination network segment, instead of sending the QoS policy in the BGP route.
  • FIG. 2 is a flowchart of a method for propagating a QoS policy according to an embodiment of the present application. As shown in FIG. 2, in conjunction with FIG. 1 and FIG. 3, the method includes:
  • the policy centralized control device generates first information according to the received BGP route from the first network device in the AS, where the first information includes one or more of the following: an AS number list, a community list;
  • the policy centralized control device generates a first QoS policy corresponding to the first information according to the first information, where the first QoS policy includes a route filtering action.
  • the policy centralized control apparatus sends the first information and the first QoS policy to the first network device.
  • a QPPB is deployed in AS1, and AS1 includes CR11, which may be a router or a switch having a Layer 3 function.
  • CR11 acts as the sender of BGP routes during QPPB implementation.
  • the BGP route may be generated by the CR11, or may be generated by other network devices, and then forwarded through the CR11.
  • the other network devices may be located in AS1, for example, other network devices are core routers located in AS1.
  • the other network devices may also be located outside of AS1, such as shown in FIG. 1, which is CR21 in AS2.
  • FIG. 3 is a schematic structural diagram of a first scenario according to an embodiment of the present application.
  • the networking scenario shown in FIG. 3 differs from the networking scenario shown in FIG. 1 in that a policy centralized control device is added, and the policy centralized control device communicates with the first network devices CR11 and CR12, respectively.
  • CR11 receives BGP routes from AS2 and forwards the BGP routes.
  • Centralized control of the strategy The device receives the BGP route from CR11.
  • the policy centralized control device is located in AS1, or the policy centralized control device is located outside of AS1, or the policy centralized control device is integrated on CR11.
  • the policy centralized control device generates first information according to the received BGP route, where the first information includes an AS number list and/or a community list. The first information is used as an identifier of the BGP route classification.
  • the process of generating, by the policy centralized control device, the first information according to the received BGP route may be performed as follows.
  • the BGP route received by the policy centralized control device carries an AS path and a community attribute, that is, each BGP route carries a corresponding AS path and a community attribute.
  • AS path: 10 20 30 70 100 300 200 means that the BGP route comes from carrier 1
  • AS path: 40 60 80 90 400 500 600 represents that the BGP route comes from carrier 2.
  • the specific value and number of the AS number of the AS path can be determined according to the actual application.
  • Community:10:1 20:1 200:200 300:300 means that the BGP route comes from carrier 1
  • Community:30:1 40:1 100:100 400:400 represents the BGP route from carrier 2
  • the value and quantity of the community attribute can be determined according to the actual application.
  • the first information is obtained by directly extracting the value of the AS number and the community attribute of the AS path that the BGP route carries. For example, for AS path: 10 20 30 70 100 300 200, "20 70" can be extracted as the AS number list in the first information to identify the BGP route to the operator 1; for example, for the Community: 10: 1 20:1 200:200 300:300, you can extract "10:1 20:1" as the list of groups in the first message.
  • part or all of the AS number of the AS path may be extracted as the AS number list in the first information.
  • part or all of the value of the community attribute may be extracted as the community list in the first information.
  • the AS number list may be used as the first information; or only the community list may be used as the first information; or the AS number list and the community list may be common in order to make the matching rule more accurate. As the first information.
  • the centralized control device can be obtained directly in the BGP route.
  • the AS number list and the community list eliminate the need to plan route classification rules and configure entry policies on the sender side.
  • the policy centralized control device is preset with a QoS policy set, and the QoS policy set may be directly set in the policy centralized control device in advance, or may be preset in the CR11, and then the CR11
  • the QoS policy set is sent to the policy centralized control device.
  • the QoS policy set includes all predefined route filtering actions, such as re-marking IP priority and the like.
  • the route filtering action may include one action or multiple actions.
  • the policy centralized control device configures a corresponding QoS policy for the first information by using a preset rule. For example, it is assumed that there are 20 route filtering actions in the QoS policy set preset by the policy centralized control device.
  • the policy centralized control device uses the community list as the first information.
  • the policy centralized control device can obtain Community 10:1 according to the information extracted by the BGP route (for example, the BGP route from the operator 1 is represented). According to the preset rule, it is desirable to perform five kinds of route filtering actions on the BGP route from the operator 1.
  • the policy centralized control device may find corresponding five route filtering actions in the QoS policy set according to Community 10:1, and form the five route filtering actions into a QoS policy corresponding to the Community 10:1.
  • the policy centralized control device may carry the first information and the first QoS policy by using a BGP Update Message, or carry the BGP FlowSpec Update Message
  • the information and the first QoS policy; or the first information and the first QoS policy are carried by other protocol messages.
  • the CR21 sets the routing attribute through the route classification, and the BR 111 sets the QoS policy according to the routing attribute of the destination network segment, instead of sending the QoS policy in the BGP route.
  • the method for propagating a QoS policy implements automatic deployment of QPPB by adding a centralized control device.
  • the centralized configuration of the QoS policy is completed in the centralized control device, and then the QoS policy is propagated to the receiving end, and the receiving end implements the route filtering action of the QoS policy.
  • No need The pre-change of the QoS policy is implemented on multiple receiving ends, which eliminates the need to plan the routing classification rules and the configuration of the ingress policy at the transmitting end, and eliminates the work of matching the QoS local identifier and the popular name on the receiving end, simplifying the QPPB. Configuration, reducing maintenance difficulty.
  • the route filtering action includes at least one of the following actions: Remark IP-precedence, remarking service type tos (Remark tos), re-marking multi-protocol label switching MPLS experimental bit exp (Remark MPLS-exp) and re-marked IP df (Remark IP-df).
  • Remark IP-precedence is used to re-mark the priority of IP packets.
  • Remark tos is used to re-mark the tos value of the IP packet. Tos takes 8 bits in the IP header. You can apply the policy to the probe packet or the Committed Access Rate (CAR) feature.
  • Remark MPLS-exp is used to re-mark the exp field value of MPLS packets.
  • Exp Extra Use
  • CoS Class
  • the Remark IP-df is used to re-mark the value of the df field of the IP packet.
  • the df (Don't Fragment) indicates that the packet fragmentation is not allowed.
  • the route filtering action may include one or more of the above actions. The non-limiting embodiment only enumerates four commonly used route filtering actions, and may also add other route filtering actions during the implementation process.
  • the first information is carried in the BGP routing attribute information
  • the step of the policy centralized control device sending the first information and the first QoS policy to the first network device includes: the policy concentration
  • the control device sends a BGP update message to the first network device, where the BGP update message includes the BGP route attribute information and the first QoS policy.
  • the first information is carried in the BGP route attribute information, that is, the BGP route attribute information includes one of the following: an AS number list, a community list, and an AS number list and a community list.
  • the BGP route attribute information is carried in a BGP update message.
  • the policy centralized control device may send a BGP update message to the CR11, where the BGP update message carries the BGP route attribute information and the first QoS policy.
  • the BGP update message carries No-Advertise
  • the policy centralized control device further sends the BGP update message to the second network device in the AS.
  • FIG. 4 is a schematic structural diagram of a second scenario according to an embodiment of the present application.
  • the networking scenario shown in FIG. 4 is different from the networking scenario shown in FIG. 3 in that the policy centralized control device further communicates with the second network devices BR111, BR121, BR112, and BR122 in the AS1, respectively.
  • BR111 is used as the receiving end in the implementation process of QPPB.
  • the policy centralized control device also sends the BGP update message to the BR 111 in the AS1.
  • the BGP update message carries No-Advertise, and No-Advertise indicates that the routing information with the attribute is not advertised to any BGP neighbor.
  • the CR11 receives the BGP update message from the policy centralized control device. Since the BGP update message carries No-Advertise, the CR11 will not forward the BGP update message to the BR 111. Therefore, the BR 111 receives only the BGP update message from the policy centralized control device. The purpose of this setting is that the BR 111 receives the BGP update message directly from the policy centralized control device, thereby saving the communication bandwidth between the CR11 and the BR 111.
  • the BGP update message carries a route filtering identifier, where the route filtering identifier is used to indicate that the BGP update message carries the BGP route attribute information and the first QoS policy.
  • the BGP update message may carry a route filtering identifier, and the route filtering identifier may be implemented by adding a field in a BGP update message or using a bit of an existing field.
  • the route filtering identifier is valid, the BGP routing attribute information and the first QoS policy carried in the BGP update message are used to filter the route.
  • the route filtering identifier is invalid, it indicates that the BGP update message is a regular BGP update message. The purpose of this setting is to effectively improve the efficiency of operation.
  • the first information is carried in a BGP FlowSpec.
  • the first information is carried in a network layer reachability information (NLRI) of the BGP FlowSpec.
  • NLRI network layer reachability information
  • the first information is carried in a middle route filtering component of the NLRI.
  • BGP FlowSpec currently supports 12 component types, see Table 1.
  • the first column of Table 1 is the type of component (Type)
  • the second column is the component for the fourth edition Internet Protocol (Internet Protocol version 4, IPv4)
  • the third column is for the sixth edition Internet Protocol (Internet Protocol). Version 6, IPv6) components.
  • These components can be encapsulated into the NLRI of the BGP FlowSpec update message. When the logical condition of the component in the NLRI is met, the corresponding action carried in the BGP FlowSpec update message is performed.
  • the NLRI may include one, or more, or all of the components shown in Table 1.
  • This application can extend the component types in the BGP FlowSpec. Add a route filtering component to the component type of BGP FlowSpec, as shown in Table 2.
  • the first column of Table 2 is the type of component (Type), and the second column is the route filtering component.
  • the route filtering component can be applied to both IPv4 and IPv6.
  • the manner shown in Table 2 is based on the 12 component types currently supported by the BGP FlowSpec, and a route filtering component is added, and the route filtering component can be encapsulated into the NLRI.
  • the route filtering component may not be extended based on the original 12 component types, but may be encapsulated in the NLRI as a separate component.
  • the route filtering component may also be directly carried in the BGP FlowSpec update message without being encapsulated in the NLRI.
  • the step that the policy centralized control device sends the first information and the first QoS policy to the first network device includes: the policy centralized control device sends a BGP FlowSpec update to the first network device The message, the BGP FlowSpec update message includes the first information and the first QoS policy.
  • the first information is carried in the NLRI, that is, the NLRI includes one of the following: an AS number list, a community list, and an AS number list and a community list.
  • the NLRI is carried in a BGP FlowSpec update message.
  • the policy centralized control device may send a BGP FlowSpec update message to the CR11, where the BGP FlowSpec update message carries the first information and the first QoS policy.
  • the BGP FlowSpec update message carries No-Advertise
  • the policy centralized control device further sends the BGP FlowSpec update message to the second network device in the AS.
  • the policy centralized control device also communicates with the second network devices BR111, BR121, BR112, and BR122 in the AS1, respectively.
  • BR111 is used as the receiving end in the implementation process of QPPB.
  • the policy centralized control device also sends the BGP FlowSpec update message to the BR 111 in the AS1.
  • the BGP FlowSpec update message carries No-Advertise, and No-Advertise indicates that the routing information with the attribute is not advertised to any BGP neighbor.
  • the CR11 receives the BGP FlowSpec update message from the policy centralized control device.
  • the CR11 Since the BGP FlowSpec update message carries No-Advertise, the CR11 will not forward the BGP FlowSpec update message to the BR 111. Therefore, the BR 111 receives only the BGP FlowSpec update message from the policy centralized control device. The purpose of this setting is that the BR 111 receives the BGP FlowSpec update message directly from the policy centralized control device, thereby saving communication bandwidth between CR11 and BR111.
  • the BGP FlowSpec update message carries a route filtering identifier, where the route filtering identifier is used to indicate that the BGP FlowSpec update message carries the first information and the first QoS policy.
  • the BGP FlowSpec update message may carry a route filtering identifier, and the route filtering identifier may be implemented by adding a field in the BGP FlowSpec update message or using one bit of an existing field.
  • the route filtering identifier is valid, the first information carried in the BGP FlowSpec update message and the first QoS policy are used to filter the path. by.
  • the route filtering identifier is invalid, it indicates that the BGP FlowSpec update message is a conventional BGP FlowSpec update message for traffic filtering.
  • the purpose of this setting is to distinguish whether the BGP FlowSpec update message is used for filtering routes or for traffic filtering by using the route filtering identifier, which can effectively improve the running efficiency.
  • the BGP FlowSpec includes a traffic filtering action, where the traffic filtering action includes a specific action, and the specified action carries the route filtering identifier.
  • the BGP FlowSpec includes a traffic filtering action, and the traffic filtering action carries the route filtering action.
  • the BGP FlowSpec includes a traffic filtering action, as shown in Table 3.
  • the first column in Table 3 is the type of traffic filtering action (Type); the second column is the identifier of the traffic filtering action, specifically the extended community attribute; the third column is the actual action, that is, the traffic filtering action.
  • the traffic filtering action can be encapsulated into the BGP FlowSpec update message. When the logical condition of the component in the NLRI is met, the corresponding traffic filtering action is performed.
  • the traffic filtering action may include one, or multiple, or all of those shown in Table 3.
  • This application can extend the traffic filtering action in the BGP FlowSpec and add route filtering actions, as shown in Table 4.
  • the first column of Table 4 is the type of route filtering action (Type); the second column is the identifier of the route filtering action, specifically the extended community attribute; the third column is the actual action, that is, the route filtering action.
  • the route filtering action can be applied to IPv4 or to IPv6. TBD3, TBD4, etc. in the first column of Table 4 are used to indicate: To be defined, which can be defined by a standard organization.
  • the four commonly used route filtering actions are defined in Table 4. Non-limiting, other route filtering actions can also be defined.
  • the set flow rate and the labeled DSCP value in Table 3 can be used as a route filtering action.
  • the method shown in Table 4 is based on the traffic filtering action currently supported by the BGP FlowSpec, and the route filtering action is added.
  • the route filtering action can be encapsulated into the BGP FlowSpec update message.
  • the route filtering action may not be extended on the basis of the original traffic filtering action, but may be directly carried into the BGP FlowSpec update message as an independent route filtering action.
  • the advantage of this setting is that the existing traffic filtering action is extended, and the route filtering action is added without changing the structure of the BGP FlowSpec.
  • the extended community attribute shown in Table 3 includes a traffic-action, and the actual action indicated by the traffic action is a specific action.
  • the flow action expansion The exhibition community attribute consists of 6 bytes.
  • the S bit (46th bit) means “sampling", that is, when the S bit is enabled, it indicates flow sampling, and records the log.
  • the T bit (bit 47) represents the "terminating action", ie when the bit is set, the traffic filtering engine should use the subsequent filtering rules (defined in the sequencing procedure). If not set, the traffic filtering rules after the application of this rule stop matching.
  • the Q bit (the 45th bit) is defined to indicate that the BGP FlowSpec update message carries the first information and the first QoS policy for filtering a route. When the Q bit is set, the BGP FlowSpec update message carries the first information and the first QoS policy for filtering the route.
  • the automatic deployment of the QPPB is implemented by adding a centralized control device of the policy, and the pre-change of the QoS policy is not required to be performed on multiple receiving ends respectively, and the work of planning the routing classification rule and setting the entry policy at the transmitting end is omitted.
  • the work of matching the QoS local identifier and the traffic behavior name on the receiving end is omitted, the configuration of the QPPB is simplified, and the maintenance difficulty is reduced.
  • FIG. 5 is a flowchart of a method for propagating a QoS policy performed by a first network device according to an embodiment of the present application. This embodiment of the present application describes a method for propagating a QoS policy from the perspective of the first network device. As shown in FIG. 5, the first network device performs the following steps:
  • the first network device in the AS sends a BGP route to the policy centralized control device.
  • the first network device receives first information from the policy centralized control device and a first QoS policy corresponding to the first information, where the first information is generated according to the BGP route, where the first The information includes one or more of the following: an AS number list, a community list, the first QoS policy is generated according to the first information, and the first QoS policy includes a route filtering action;
  • the first network device forwards the first information and the first QoS policy to the second network device.
  • the first network device is included in the AS.
  • the second network device may be located within the AS or may be located outside of the AS, for example, the second network device is located at the third AS.
  • the second network device is in communication with the first network device and receives a BGP route from the first network device.
  • QPPB is deployed in AS1, and the AS1 includes CR11 and CR11. It can be a router or a switch with three layers of functionality.
  • CR11 acts as the sender of BGP routes during QPPB implementation.
  • the BGP route may be generated by CR11, or may be generated by other network devices, and then forwarded through CR11.
  • the other network devices may be located in AS1, for example, other network devices are core routers located in AS1.
  • the other network devices may also be located outside of AS1, such as shown in FIG. 3, which is CR21 in AS2.
  • the CR 11 communicates with the policy centralized control device, and sends the BGP route to the policy centralized control device.
  • the CR 11 receives the first information from the policy centralized control device and the first QoS policy.
  • the first information and the first QoS policy may be carried in a BGP update message, a BGP FlowSpec update message, or other protocol packets.
  • CR11 forwards the first information and the first QoS policy to the BR 111 in the AS1.
  • the BR111 can be a router or a switch with three layers of functionality.
  • the first information and the first QoS policy may be carried in a BGP update message, a BGP FlowSpec update message, or other protocol packets.
  • the CR11 is configured with the undo local-install command, indicating that the local installation is not performed. Specifically, the CR11 does not perform the first QoS policy according to the first information, and the CR11 only uses the first information and the first QoS.
  • the policy is forwarded.
  • the undo local-install command is an existing configuration command. The detailed execution process is not mentioned here.
  • CR11 communicates with the policy centralized control device.
  • CR11 receives the BGP route from AS2 and forwards the BGP route to the policy centralized control device.
  • the policy centralized control device generates first information according to the BGP route, and matches the QoS policy according to the first information.
  • the first information and the first QoS policy are then sent to CR11.
  • the CR 11 communicates with the BR 111 to forward the first information and the first QoS policy to the BR 111.
  • the route filtering action includes at least one of the following actions: re-marking the IP priority, re-marking the tos, re-marking the exp of the MPLS, and re-marking the df of the IP.
  • the first information is carried in the BGP route attribute information
  • the step of the first network device receiving the first information from the policy centralized control device and the first QoS policy includes: the first network The device receives a BGP update message from the policy centralized control device, where the BGP update message includes the BGP route attribute information and the first QoS policy; the first network device forwards the first to the second network device
  • the information and the first QoS policy step include the first network device forwarding the BGP update message to the second network device.
  • the first information and the first QoS policy may be carried in the BGP update message, and sent by the policy centralized control device to the CR11.
  • the CR 11 receives the BGP update message and forwards the BGP update message to the BR 111.
  • the first information is carried in the BGP FlowSpec; further optionally, the first information is carried in an NLRI of the BGP FlowSpec; and further optionally, the first information is carried in the NLRI's medium route filtering component.
  • the step of the first network device receiving the first information from the policy centralized control device and the first QoS policy includes: the first network device receiving a BGP FlowSpec update from the policy centralized control device a message that the BGP FlowSpec update message includes the first information and the QoS policy; and the step of the first network device forwarding the first information and the first QoS policy to the second network device includes: A network device forwards the BGP FlowSpec update message to the second network device.
  • the first information and the first QoS policy may be carried in the BGP FlowSpec update message, and sent by the policy centralized control apparatus to the CR11.
  • the CR11 receives the BGP FlowSpec update message and forwards the BGP FlowSpec update message to the BR 111.
  • the first network device receives the first information and the first QoS policy, and forwards the first information and the first QoS policy to the second network device. Therefore, the first network device does not need to configure an ingress policy, and the work of planning a route classification rule on the first network device is omitted.
  • FIG. 6 is a flowchart of a method for propagating a QoS policy performed by a second network device according to an embodiment of the present application.
  • This embodiment of the present application is a method for propagating a QoS policy from the perspective of a second network device. As shown in FIG. 6, the second network device performs the following steps:
  • the second network device receives a BGP route from the first network device in the AS.
  • the second network device receives first information and a first QoS policy corresponding to the first information, where the first information and the first QoS policy are from a first network device or policy in the AS.
  • the centralized control device the first information is generated according to the BGP route, and the first information includes one or more of the following: an AS number list, a community list, where the first QoS policy is generated according to the first information.
  • the first QoS policy includes a route filtering action;
  • the second network device searches for, in the BGP route, a BGP routing entry that matches the first information.
  • the second network device applies the route filtering action to the FIB entry sent by the BGP routing entry.
  • the first network device is included in the AS.
  • the second network device may be located within the AS or may be located outside of the AS, for example, the second network device is located at the third AS.
  • the second network device is in communication with the first network device and receives a BGP route from the first network device.
  • the BGP route may be generated by the first network device, or may be generated by another network device, and then forwarded by the first network device.
  • the other network device may be located in the AS or outside the AS. For example, the other network device is located in the second AS.
  • the second network device receives a BGP route from the first network device, and then applies a QoS policy to the BGP route.
  • the first QoS policy is generated by the policy centralized control device according to the first information, and the first information is generated according to the BGP route.
  • the first QoS policy includes a route filtering action.
  • the second network device receives the first information and the first QoS policy.
  • the first information and the first QoS policy may be sent by the policy centralized control device to the first network device, and then forwarded by the first network device to the second network device; or by the policy concentration
  • the control device sends directly to the second network device.
  • the BR 111 searches for the BGP routing entry matching the first information in the BGP route according to the first information.
  • the BGP route can be carried in the BGP update message and sent by the CR11 to the second network device.
  • the BGP route carries identification information, such as an AS path and a community attribute.
  • the BGP route may include one BGP routing entry or multiple BGP routing entries. Therefore, each BGP routing entry has its own identification information.
  • the first information includes the AS number list and the community list. Therefore, the BGP routing entry in the BGP route can be searched according to the first information.
  • a BGP route includes multiple BGP routing entries. Some BGP routing entries are from carrier 1.
  • the BGP routing entry identifier can be AS path: 10 20 30 70 100 300 200. Some BGP routes are available.
  • the entry of the BGP routing entry can be AS path: 40 60 80 90 400 500 600.
  • the AS number list information of the first information is AS path: 20 70.
  • searching all the BGP routing entries in the BGP route that identify the AS path: 20 70 can be determined, and the BGP route from the carrier 1 is formed.
  • the BR 111 may apply the first QoS policy corresponding to the first information to the FIB entry delivered by the BGP routing entry set from the operator 1.
  • the BR 111 receives the first information and the first QoS policy, and the BR 111 receives the BGP route from the CR11 in the AS1 without synchronization. For example, if the BR 111 first receives all the BGP routes, and then receives the first information and the first QoS policy, the BR 111 performs the first QoS on all the received BGP routes according to the first information. Strategy. It is also assumed that when the BR 111 first receives a part of the BGP route, the first information and the first QoS policy reach the second network device of the BR 111, and the second network device of the BR 111 performs the real-time follow-up according to the first information.
  • the BGP route to the second network device implements the first QoS policy, and then implements the first QoS policy for the first information and the part of the BGP route received before the QoS policy arrives. It is also assumed that the second network device of the BR 111 first receives the first information and the first QoS policy, and the second network device of the BR 111 according to the first The first QoS policy is implemented in real time for the BGP route that subsequently arrives at the second network device of the BR 111.
  • the route filtering action includes at least one of the following actions: re-marking the Internet Protocol IP priority, re-marking the service type tos, re-marking the experimental bit bit exp of the Multi-Protocol Label Switching MPLS, and re-marking the df of the IP.
  • the route filtering action includes at least one of the following actions: re-marking the Internet Protocol IP priority, re-marking the service type tos, re-marking the experimental bit bit exp of the Multi-Protocol Label Switching MPLS, and re-marking the df of the IP.
  • the first information is carried in the BGP route attribute information; the second network device receives a BGP update message from the first network device, where the BGP update message includes the BGP route attribute information and the Determining a first QoS policy; or the second network device receiving a BGP update message from the policy centralized control device, the BGP update message including the BGP route attribute information, the first QoS policy, and No-Advertise .
  • the BGP update message includes the BGP route attribute information and the Determining a first QoS policy
  • the second network device receiving a BGP update message from the policy centralized control device, the BGP update message including the BGP route attribute information, the first QoS policy, and No-Advertise .
  • the first information is carried in the BGP FlowSpec; further optionally, the first information is carried in an NLRI of the BGP FlowSpec; and further optionally, the first information is carried in the NLRI's medium route filtering component.
  • the second network device receives a BGP FlowSpec update message from the first network device, where the BGP FlowSpec update message includes the first information and the first QoS policy; or, the second The network device receives a BGP FlowSpec update message from the policy centralized control device, the BGP FlowSpec update message including the first information, the first QoS policy, and No-Advertise.
  • the BGP FlowSpec update message includes the first information and the first QoS policy
  • No-Advertise No-Advertise.
  • the BGP FlowSpec includes a traffic filtering action, and the traffic filtering action carries the route filtering action.
  • the traffic filtering action carries the route filtering action.
  • the second network device is configured with the undo local-install command, indicating that the local installation is not performed, specifically indicating that the second network device does not perform the first QoS policy.
  • a portion of the second network device may be selected to perform the The first QoS policy.
  • FIG. 8 is a schematic structural diagram of a policy centralized control apparatus 800 according to an embodiment of the present invention.
  • the policy centralized control device shown in FIG. 8 can perform the corresponding steps performed by the policy centralized control device in the method of the above embodiment.
  • the policy centralized control apparatus 800 includes a receiving unit 802, a generating unit 804, and a transmitting unit 806, where:
  • the receiving unit 802 is configured to generate first information according to the received BGP route from the first network device in the AS, where the first information includes one or more of the following: an AS number list, a community list;
  • the generating unit 804 is configured to generate, according to the first information, a first QoS policy corresponding to the first information, where the first QoS policy includes a route filtering action;
  • the sending unit 806 is configured to send the first information and the first QoS policy to the first network device.
  • the first information is carried in the BGP route attribute information, where the sending unit is configured to send a BGP update message to the first network device, where the BGP update message includes the BGP route attribute information and The first QoS policy.
  • the BGP update message carries a No-Advertise; the sending unit is further configured to send the BGP update message to a second network device in the AS.
  • the BGP update message carries a route filtering identifier, where the route filtering identifier is used to indicate that the BGP update message carries the BGP route attribute information and the first QoS policy.
  • the first information is carried in the BGP FlowSpec; further optionally, the first information is carried in an NLRI of the BGP FlowSpec; and further optionally, the first information is carried in the NLRI's medium route filtering component.
  • the sending unit is specifically configured to send a BGP FlowSpec update message to the first network device, where the BGP FlowSpec update message includes the first information and the first QoS policy.
  • the BGP FlowSpec update message carries a No-Advertise; the sending unit is further configured to send the BGP FlowSpec update message to a second network device in the AS.
  • the BGP FlowSpec update message carries a route filtering identifier, where the route filtering identifier is used to indicate that the BGP FlowSpec update message carries the first information and the first QoS policy.
  • the BGP FlowSpec includes a traffic filtering action, where the traffic filtering action includes a specified action, and the specified action carries the route filtering identifier.
  • the BGP FlowSpec includes a traffic filtering action, and the traffic filtering action carries the route filtering action.
  • the policy centralized control device shown in FIG. 8 can perform the corresponding steps performed by the policy centralized control device in the method of the above embodiment. Therefore, it is not necessary to separately implement pre-change of the QoS policy for multiple receiving ends, and the work of planning the routing classification rule and configuring the ingress policy at the transmitting end is omitted, and the work of matching the QoS local identifier and the popular name on the receiving end is omitted. Simplify the configuration of QPPB and reduce maintenance difficulty.
  • FIG. 11 is a schematic structural diagram of hardware of a policy centralized control apparatus 1100 according to an embodiment of the present invention.
  • the policy centralized control device shown in FIG. 11 can perform the corresponding steps performed by the policy centralized control device in the method of the above embodiment.
  • the policy centralized control device 1100 includes a processor 1101, a memory 1102, an interface 1103, and a bus 1104.
  • the interface 1103 can be implemented by using a wireless or wired method, and specifically, for example, a network card or the like.
  • the processor 1101, the memory 1102, and the interface 1103 are connected by a bus 1104.
  • the interface 1103 may specifically include a transmitter and a receiver, configured to send and receive information between the policy centralized control device and the first network device in the foregoing embodiment, or used for centralized policy control.
  • the device transmits and receives information to and from the first network device and the second network device in the foregoing embodiment.
  • the interface 1103 is used to support processes S202 and S206 in FIG.
  • the processor 1101 is configured to perform the steps performed by the policy centralized control device of FIG. 2.
  • the processor 1101 is configured to support the process S204 of FIG.
  • the memory 1102 is configured to store programs, codes, or instructions. When the processor or the hardware device executes the programs, codes, or instructions, the functions of any of the policy centralized control devices of FIG. 2 to FIG. 6 or any of the strategies of FIGS. 2-6 can be completed. The steps performed by the control device.
  • Figure 11 only shows a simplified design of the centralized control device.
  • the policy centralized control device may include any number of interfaces, processors, memories, etc., and all of the policy centralized control devices that can implement the present invention are within the scope of the present invention.
  • FIG. 9 is a schematic structural diagram of a first network device 900 according to an embodiment of the present invention.
  • the first network device shown in FIG. 9 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device 900 is located in an AS, and includes a sending unit 902 and a receiving unit 904, where:
  • the sending unit 902 is configured to send a BGP route to the policy centralized control device.
  • the receiving unit 904 is configured to receive first information from the policy centralized control device and a first QoS policy corresponding to the first information, where the first information is generated according to the BGP route, where the first The information includes one or more of the following: an AS number list, a community list, the first QoS policy is generated according to the first information, and the first QoS policy includes a route filtering action;
  • the sending unit 902 is further configured to forward the first information and the first QoS policy to the second network device.
  • the first information is carried in the BGP route attribute information
  • the receiving unit 904 is configured to receive a BGP update message from the policy centralized control device, where the BGP update message includes the BGP route attribute.
  • the sending unit 902 is specifically configured to forward the BGP update message to the second network device.
  • the first information is carried in the BGP FlowSpec; further optionally, the first information is carried in an NLRI of the BGP FlowSpec; and further optionally, the first information is carried in the NLRI's medium route filtering component.
  • the receiving unit 904 is specifically configured to receive a BGP FlowSpec update message from the policy centralized control device, where the BGP FlowSpec update message includes the first information and the first QoS policy;
  • the unit 902 is specifically configured to forward the BGP FlowSpec update message to the second network device.
  • the first network device shown in FIG. 9 can perform the corresponding steps performed by the first network device in the method of the above embodiment. Therefore, the first network device does not need to configure an ingress policy, and the work of planning a route classification rule on the first network device is omitted.
  • FIG. 12 is a schematic structural diagram of hardware of a first network device 1200 according to an embodiment of the present invention.
  • the first network device shown in FIG. 12 can perform the corresponding steps performed by the first network device in the method of the above embodiment.
  • the first network device 1200 includes a processor 1201, a memory 1202, an interface 1203, and a bus 1204.
  • the interface 1203 can be implemented in a wireless or wired manner, and specifically, may be, for example, a network card or the like.
  • the processor 1201, the memory 1202, and the interface 1203 are connected by a bus 1204.
  • the interface 1203 may specifically include a transmitter and a receiver, configured to send and receive information between the first network device and the policy centralized control device and the second network device in the foregoing embodiment.
  • the interface 1203 is used to support the processes S502, S504, and S506 in FIG.
  • the processor 1201 is configured to perform the processes of FIG. 5 relating to the first network device and/or other processes for the techniques described herein.
  • the memory 1202 is configured to store programs, codes or instructions of the first network device, and when the processor or the hardware device executes the programs, codes or instructions, the functions of any of the first network devices of FIG. 2 to FIG. 6 or FIG. 2 to FIG. 6 may be completed. The step performed by any of the first network devices Step.
  • Figure 12 only shows a simplified design of the first network device.
  • the first network device may include any number of interfaces, processors, memories, etc., and all of the first network devices that can implement the present invention are within the scope of the present invention.
  • FIG. 10 is a schematic structural diagram of a second network device 1000 according to an embodiment of the present invention.
  • the second network device shown in FIG. 10 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the second network device 1000 includes a receiving unit 1002, a searching unit 1004, and an application unit 1006, where:
  • the receiving unit 1002 is configured to receive a BGP route from a first network device in the AS.
  • the receiving unit 1002 is further configured to receive first information and a first QoS policy corresponding to the first information, where the first information and the first QoS policy are from a first network device in the AS or The policy centralized control device, the first information is generated according to the BGP route, and the first information includes one or more of the following: an AS number list, a community list, and the first QoS policy is based on the first information Generating, the first QoS policy includes a route filtering action;
  • the searching unit 1004 is configured to search, in the BGP route, a BGP routing entry that matches the first information.
  • the application unit 1006 is configured to apply the route filtering action to the FIB entry sent by the BGP routing entry.
  • the first information is carried in the BGP route attribute information
  • the receiving unit 1002 is configured to receive a BGP update message from the first network device, where the BGP update message includes the BGP route attribute information. And the first QoS policy; or the receiving unit 1002, configured to receive a BGP update message from the policy centralized control device, where the BGP update message includes the BGP route attribute information, the first QoS policy And No-Advertise.
  • the first information is carried in the BGP FlowSpec; further optionally, the first information is carried in an NLRI of the BGP FlowSpec; and further optionally, the first information is carried in the NLRI's medium route filtering component.
  • the receiving unit 1002 is configured to receive a BGP FlowSpec update message from the first network device, where the BGP FlowSpec update message includes the first information and the first QoS policy; or The receiving unit 1002 is configured to receive a BGP FlowSpec update message from the policy centralized control device, where the BGP FlowSpec update message includes the first information, the first QoS policy, and No-Advertise.
  • the BGP FlowSpec includes a traffic filtering action, and the traffic filtering action carries the route filtering action.
  • the second network device shown in FIG. 10 can perform the corresponding steps performed by the second network device in the method of the above embodiment. Therefore, there is no need to configure a QoS policy on the receiving end. When there are multiple receiving ends, it is not necessary to separately implement pre-change of the QoS policy for multiple receiving ends. Moreover, the work of matching the QoS local identifier and the popular name on the receiving end is omitted, the configuration of the QPPB is simplified, and the maintenance difficulty is reduced.
  • FIG. 13 is a schematic structural diagram of hardware of a second network device 1300 according to an embodiment of the present invention.
  • the second network device shown in FIG. 13 can perform the corresponding steps performed by the second network device in the method of the above embodiment.
  • the second network device 1300 includes a processor 1301, a memory 1302, an interface 1303, and a bus 1304.
  • the interface 1303 can be implemented by using a wireless or wired manner, and specifically, for example, a network card or the like.
  • the processor 1301, the memory 1302, and the interface 1303 are connected by a bus 1304.
  • the interface 1303 may specifically include a receiver, configured to send and receive information between the second network device and the first network device in the foregoing embodiment, or used in the second network device and the first in the foregoing embodiment.
  • the network device and the centralized control device of the policy send and receive information.
  • the interface 1303 is used to support processes S602 and S604 in FIG.
  • the processor 1301 is configured to perform the processing of the second network device in FIG. 6 and/or other processes for the techniques described herein.
  • the processor 1301 is used to support processes S606 and S608 in FIG.
  • the memory 1302 is configured to store programs, codes, or instructions of the second network device, and when the processor or the hardware device executes the programs, codes, or instructions, the second network device of any one of FIGS. 2-6 may be completed. The function or the steps performed by any of the second network devices of Figures 2-6.
  • Figure 13 only shows a simplified design of the second network device.
  • the second network device may include any number of interfaces, processors, memories, etc., and all second network devices that can implement the present invention are within the scope of the present invention.
  • the embodiment of the present invention further provides a network system 1400.
  • the network system may include the policy centralized control device provided by the foregoing embodiment corresponding to FIG. 8 or FIG. 11 , the first network device provided by the embodiment corresponding to FIG. 9 or FIG. 12 , and the embodiment corresponding to FIG. 10 or FIG. 13 .
  • Second network device The dotted line shown in FIG. 14 indicates that: the policy centralized control device sends information to the second network device, or the second network device receives information from the policy centralized control device, where the information may be the first Information and a first QoS policy corresponding to the first information.
  • the policy centralized control device, the first network device, and the second network device are not described herein again.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the user equipment.
  • the processor and the storage medium may also reside as discrete components in the user equipment.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • the computer readable medium includes a computer storage medium and a communication medium, wherein the communication medium includes a computer program that facilitates transmission from one location to another Any medium of the order.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Abstract

一种传播QoS策略的方法、装置及系统。该方法包括，根据接收到的来自AS中的第一网络设备的BGP路由生成第一信息，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表；根据所述第一信息生成与所述第一信息对应的第一QoS策略，所述第一QoS策略包括路由过滤动作；向所述第一网络设备发送所述第一信息和所述第一QoS策略。从而，无需对多个接收端分别实施QoS策略的预先变更，省去了在发送端规划路由分类规则和配置入口策略的工作，省去了在接收端匹配QoS局部标识和流行为名称的工作，简化QPPB的配置，降低维护难度。

Description

一种传播QoS策略的方法、装置及系统
本申请要求于2015年12月24日提交中国专利局、申请号为201510988407.4、发明名称为“一种传播QoS策略的方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种传播服务质量(Quality of service，QoS)策略的方法、装置及系统。
背景技术
边界网关协议(Border Gateway Protocol，BGP)是一种用于自治系统(Autonomous System，AS)之间的动态路由协议。在复杂组网环境中，为了满足QoS等需求，通常需要执行大量的复杂流分类，由于无法按照AS、团体属性(Community attribute)等聚类信息对报文分类，配置修改的工作量非常大甚至难以实施。而应用通过BGP传播QoS策略(QoS Policy Propagation Through the Border Gateway Protocol，QPPB)技术可以由BGP路由发送者通过设置BGP属性预先对路由进行分类，这样就可以简化路由接收者的策略修改，只需要配置BGP路由策略就可以满足需求。
QPPB的实现机制具体为：BGP路由在通告过程中可以携带路由属性，BGP路由的发送端在向接收端发送路由时，先匹配路由策略，为发送的不同路由信息设置不同的BGP路由属性，所述BGP路由属性包括自治系统路径(AS path)、团体属性等，BGP路由属性作为BGP路由分类的标识。接收端在接收到路由后，通过入口路由策略匹配BGP路由属性，基于路由属性信息，匹配路由策略，为接收到的BGP路由设置QoS参数，并将BGP路由及相关联的QoS参数一起下发到转发信息库(Forward Information Base，FIB)；对分类后的数据流配置QoS策略。这样，在数据转发过程中，对发送到目的网段的数据包可以依据从FIB中获取的互联网协议(Internet Protocol，IP)优先级、QoS局部标识和流行为名称等QoS参数使用不同的QoS策略，从而实现QPPB的实施。
边界网关协议流规则(BGP Flow Specification，BGP FlowSpec)通过传递BGP FlowSpec路由将流量策略传递给BGP FlowSpec对等体(peer)，对符合过滤条件的流量应用流量控制动作。BGP FlowSpec对等体收到BGP FlowSpec路由后，会将优选的BGP FlowSpec路由转换为转发平面的流量控制策略，以此来限制发起拒绝服务(Denial of service，DoS)/分布式拒绝服务(Distributed Denial of service，DDoS)攻击源的流量。
在实际应用中，发明人发现现有的QPPB存在以下问题：当QoS策略需要改变时，需要在接收端实施QoS策略的预先变更，特别是当具有多个接收端时，需要对多个接收端分别实施QoS策略的预先变更，增加了QPPB的配置量，容易出错，不利于后期维护。
发明内容
有鉴于此，本申请实施例提供了一种传播QoS策略的方法、装置及系统，以解决当实施QPPB时，需要对多个接收端分别实施QoS策略的预先变更而造成的QPPB的配置量大，容易出错，不利于后期维护的问题。
本申请实施例提供的技术方案如下。
第一方面，提供了一种传播QoS策略的方法，所述方法包括：
根据接收到的来自AS中的第一网络设备的BGP路由生成第一信息，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表；
根据所述第一信息生成与所述第一信息对应的第一QoS策略，所述第一QoS策略包括路由过滤动作；
向所述第一网络设备发送所述第一信息和所述第一QoS策略。
可选的，所述第一信息携带在BGP路由属性信息中；所述向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤包括：向所述第一网络设备发送BGP更新消息(BGP Update Message)，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略。
可选的，所述BGP更新消息携带No-Advertise；所述向所述第一网络设 备发送所述第一信息和所述第一QoS策略步骤还包括：向所述AS中的第二网络设备发送所述BGP更新消息。
可选的，所述BGP更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP更新消息中携带了所述BGP路由属性信息和所述第一QoS策略。
可选的，所述向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤包括：向所述第一网络设备发送BGP FlowSpec更新消息(BGP FlowSpec Update Message)，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略。
可选的，所述BGP FlowSpec更新消息携带No-Advertise；所述向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤还包括：向所述AS中的第二网络设备发送所述BGP FlowSpec更新消息。
第二方面，提供了一种传播QoS策略的方法，所述方法包括：
AS中的第一网络设备向策略集中控制装置发送BGP路由；
所述第一网络设备接收来自所述策略集中控制装置的第一信息和与所述第一信息对应的第一QoS策略，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略。
可选的，所述第一信息携带在BGP路由属性信息中，所述第一网络设备接收来自所述策略集中控制装置的第一信息和所述第一QoS策略步骤包括：所述第一网络设备接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略步骤包括：所述第一网络设备向所述第二网络设备转发所述BGP更新消息。
可选的，所述第一网络设备接收来自所述策略集中控制装置的第一信息和所述第一QoS策略步骤包括：所述第一网络设备接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略步骤包括：所述第一网络设备向所述第二网络设备转发所述BGP FlowSpec更新消息。
第三方面，提供了一种传播QoS策略的方法，所述方法包括：
第二网络设备接收来自AS中的第一网络设备的BGP路由；
所述第二网络设备接收第一信息和与所述第一信息对应的第一QoS策略，所述第一信息和所述第一QoS策略来自所述AS中的第一网络设备或策略集中控制装置，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
所述第二网络设备在所述BGP路由中查找与所述第一信息匹配的BGP路由表项；
所述第二网络设备将所述路由过滤动作应用在所述BGP路由表项下发的FIB表项中。
可选的，所述第一信息携带在BGP路由属性信息中；所述第二网络设备接收来自所述第一网络设备的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；或者，所述第二网络设备接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息、所述第一QoS策略和No-Advertise。
可选的，所述第二网络设备接收来自所述第一网络设备的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；或者，所述第二网络设备接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息、 所述第一QoS策略和No-Advertise。
可选的，所述第二网络设备配置有undo local-install命令，表示不执行本地安装，具体的表示所述第二网络设备不执行所述第一QoS策略。
在第一方面、第二方面和第三方面及其可能的实现方式中：
可选的，所述第一信息携带在BGP FlowSpec中；进一步可选的，所述第一信息携带在所述BGP FlowSpec的网络层可达信息(network layer reachability information,NLRI)中；进一步可选的，所述第一信息携带在所述NLRI的中路由过滤组件中。
可选的，所述BGP FlowSpec更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP FlowSpec更新消息中携带了所述第一信息和所述第一QoS策略。
可选的，所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作包括指定的动作，所述指定的动作携带所述路由过滤标识；进一步可选的，所述流量过滤动作携带所述路由过滤动作。
第四方面，提供了一种策略集中控制装置，所述策略集中控制装置具有实现上述方法中策略集中控制装置行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，提供了一种第一网络设备，所述第一网络设备具有实现上述方法中第一网络设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述第一网络设备可以包括发送单元和接收单元以实现上述方法中第一网络设备的功能，也可以通过其他功能模块来实现上述方法中第一网络设备的功能。
第六方面，提供了一种第二网络设备，所述第二网络设备具有实现上述方法中第二网络设备行为的功能。所述功能可以基于硬件实现，也可以 基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述第二网络设备可以包括发送单元和接收单元以实现上述方法中第二网络设备的功能，也可以通过其他功能模块来实现上述方法中第二网络设备的功能。
第七方面，提供了一种网络系统，所述网络系统包括策略集中控制装置、第一网络设备和第二网络设备，所述策略集中控制装置为第四方面所述的策略集中控制装置，所述第一网络设备为第五方面所述的第一网络设备，所述第二网络设备为第六方面所述的第二网络设备。
第八方面，提供了一种计算机存储介质，用于储存为上述策略集中控制装置所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述方面中策略集中控制装置的功能或步骤。
第九方面，提供了一种计算机存储介质，用于储存为上述第一网络设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述方面中第一网络设备的功能或步骤。
第十方面，提供了一种计算机存储介质，用于储存为上述第二网络设备所用的程序、代码或指令，当计算机或硬件设备执行这些程序、代码或指令时可以完成上述方面中第二网络设备的功能或步骤。
基于上述第一方面至第十方面可能的实现方式中，可选的，所述路由过滤动作包括下列动作的至少一个：重新标记互联网协议IP优先级(Remark IP-precedence)、重新标记服务类型tos(Remark tos)、重新标记多协议标记交换MPLS的实验比特位exp(Remark MPLS-exp)和重新标记IP的df(Remark IP-df)。
通过本申请实施方式，根据接收到的来自AS中的第一网络设备的BGP路由生成第一信息，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表；根据所述第一信息生成与所述第一信息对应的第一QoS策略，所述第一QoS策略包括路由过滤动作；向所述第一网络设备发送所述第一 信息和所述第一QoS策略。从而，实现QPPB的自动化部署，无需对多个接收端分别实施QoS策略的预先变更，省去了在发送端规划路由分类规则和配置入口策略的工作，省去了在接收端匹配QoS局部标识和流行为名称的工作，简化QPPB的配置，降低维护难度。
附图说明
图1为跨AS组网的结构示意图；
图2为本申请实施例的传播QoS策略的方法的流程图；
图3为本申请实施例的第一场景结构示意图；
图4为本申请实施例的第二场景结构示意图；
图5为本申请实施例的第一网络设备执行的传播QoS策略的方法的流程图；
图6为本申请实施例的第二网络设备执行的传播QoS策略的方法的流程图；
图7为本申请实施例的流量动作扩展团体属性的格式示意图；
图8为本发明实施例的策略集中控制装置的结构示意图；
图9为本发明实施例的第一网络设备的结构示意图；
图10为本发明实施例的第二网络设备的结构示意图；
图11为本发明实施例的策略集中控制装置的硬件结构示意图；
图12为本发明实施例的第一网络设备的硬件结构示意图；
图13为本发明实施例的第二网络设备的硬件结构示意图；
图14为本发明实施例的网络系统的结构示意图。
具体实施方式
本申请实施例提供了一种传播QoS策略的方法、装置及系统，以解决当实施QPPB时，需要预先变更多个接收端QoS策略而造成的QPPB的配置量大，容易出错，不利于后期维护的问题。
下面通过具体实施例，分别进行详细的说明。
为使得本申请的发明目的、特征、优点能更加的明显和易懂，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述，显然下面所描述的实施例仅仅是本申请一部分实施例，而非全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书及附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”不是排他的。例如包括了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，还可以包括没有列出的步骤或单元。
图1为跨自治系统AS组网的结构示意图。以下根据图1所示的组网示例性的说明QPPB的部署过程。如图1所示，该组网包括自治系统AS1和AS2，其中AS1和AS2为不同的自治系统。例如，AS2可以是国家骨干网，AS1可以是省骨干网。AS2可以包括一台或多台第三网络设备。在本实施例中假定为AS2中有两台第三网络设备CR21和CR22。所述第三网络设备可以是路由器或具有三层功能的交换机。在图1所示的组网中，第三网络设备CR21和CR22可以充当核心路由器(core router，CR)。
AS1可以包括：第一网络设备和第二网络设备。其中，所述第一网络设备可以设置一台或多台，所述第二网络设备可以设置一台或多台。在本实施例中假定为两台第一网络设备CR11和CR12和四台第二网络设备BR111、BR121、BR112和BR122。所述第一网络设备可以是路由器或具有三层功能的交换机。所述第二网络设备可以是路由器或具有三层功能的交换机。在图1所示的组网中，第一网络设备CR11和CR12可以充当CR；第二网络设备BR111、BR121、BR112和BR122可以充当边界路由器(border router，BR)。
如图1所示，第三网络设备CR21经由第一网络设备CR11与第二网络设备BR111和BR112通信，第三网络设备CR22经由第一网络设备CR12与第二网络 设备BR121和BR122通信。可选的，第一网络设备CR11与第一网络设备CR12通信。可选的，第二网络设备BR111与第二网络设备BR121通信，第二网络设备BR112与第二网络设备BR122通信。应当理解，图1所示的设置的设备数量及连接方式仅是示例性的，不应成为本申请的限制。
应当理解，第三网络设备CR21和CR22在组网中具有相同的作用和功能；第一网络设备CR11和CR12在组网中具有相同的作用和功能；第二网络设备BR111、BR121、BR112和BR122具有相同的作用和功能。为了便于理解，在下面的各个实施例描述中，以第三网络设备CR21经由第一网络设备CR11与第二网络设备BR111通信为例进行说明。
举例说明，第一网络设备、第二网络设备和第三网络设备上均部署有BGP，如图1所示，CR21发出的BGP路由，经过CR11，到达BR111。在图1所示的组网中部署QPPB，即通过BGP传播QoS策略。CR11接收来自CR21的BGP路由，在所述BGP路由中可以携带路由属性。CR11在从CR21接收所述BGP路由时，根据第一入口路由策略，对该BGP路由分类，所述第一入口路由策略包括预先规划的分类规则。该分类规则可以保存在CR11上或第三方设备上。所述分类规则根据实际需要进行设定。例如，设定所述分类规则为团体属性，或设定所述分类规则为AS路径，或设定所述分类规则为前缀列表。
以设定所述分类规则为团体属性为例。CR11获取CR21发送的BGP路由中的AS路径信息，根据该AS路径信息设置该BGP路由的团体属性的值，并且CR11将该团体属性的值记录到团体属性的值的列表中。可选的，CR11获取CR21发送的BGP路由中的团体属性信息，根据该团体属性信息设置该BGP路由的团体属性的值。可选地，CR11获取CR21发送的BGP路由中的AS路径信息和团体属性信息，设置根据该AS路径信息和该团体属性信息设置该BGP路由的团体属性的值。这样，CR11将该团体属性的值作为BGP路由的分类标记，对后续到达CR11的BGP路由进行分类。其中，所述团体属性的值可以自动的进行学习，例如，CR11获取CR21发送的另一BGP路由，发现无法使用所述团 体属性的值对另一BGP路由进行分类标记，则CR11将按照上述方法设置另一BGP路由的团体属性的值，并将另一BGP路由的团体属性的值添加到团体属性的值的列表中。CR11将配置好的分类规则下发给BR111。
当然，CR11也可以通过其他标识对接收到的BGP路由分类，例如通过CR21发送的BGP路由携带的AS路径、前缀列表等中的一个或多个对收到的BGP路由分类。其中，AS路径是由AS号码列表(AS number list)构成的，AS号码列表可以包括AS_SET(AS集合)或AS_SEQUENSE(AS序列)，AS_SET或AS_SEQUENSE可以包括多个AS号码。其中AS_SET表示无序的号码列表，AS_SEQUENSE表示有序的号码列表。例如，AS path：10 20 30 70 100 300 200代表来自运营商1的AS路径，其中10，20，30，70，100，300，200分别为不同的AS号码，这些AS号码包括在AS_SET或AS_SEQUENSE中，构成了AS号码列表。
BR111接收CR11转发的所述BGP路由，获取该BGP路由中的BGP路由属性，确定第二入口路由策略中是否存在对应该BGP路由属性的QoS策略。如果存在对应该BGP路由属性的QoS策略，在BR111上对该BGP路由应用QoS策略。所述BGP路由属性是由路由发送端(比如，CR21)在发送BGP路由时，根据不同的运营商为BGP路由配置的属性信息。
如前述，CR11将配置好的分类规则下发给BR111。以团体属性作为分类规则为例。BR111获得来自CR11的团体属性，将团体属性的值的列表与BR111中预先设置的QoS策略进行匹配。具体匹配方法是：BR111中预先设置有团体属性的值与QoS策略对应关系，例如“团体属性的值1对应QoS策略1、团体属性的值2对应Qos策略2···团体属性的值n对应QoS策略n”，其中n为大于1的整数。BR111从CR11获取的团体属性的值的列表中包括团体属性的值1和团体属性的值2，因此BR111将团体属性的值1对应QoS策略1和团体属性的值2对应QoS策略2作为第二入口路由策略。BR111接收CR11转发的所述BGP路由，如果判断所述BGP路由对应团体属性的值1，则为所述 BGP路由配置QoS策略1。然后，BR111确定QoS策略中与团体属性对应的QoS局部标识，再通过所述QoS局部标识找到对应的流行为名称，所述流行为名称标识了需要执行的动作。BR111将BGP路由及相关联的QoS局部标识和流行为名称一起下发到FIB表，通过匹配QoS局部标识和流行为名称对BGP路由实施相应的动作。
因此，上述QPPB的实施过程，CR21通过路由分类设置路由属性，BR111根据目的网段的路由属性设置QoS策略，不是在BGP路由中发送QoS策略。
图2为本申请实施例的传播QoS策略的方法的流程图。如图2所示，结合图1和图3，该方法包括：
S202，策略集中控制装置根据接收到的来自AS中的第一网络设备的BGP路由生成第一信息，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表；
S204，所述策略集中控制装置根据所述第一信息生成与所述第一信息对应的第一QoS策略，所述第一QoS策略包括路由过滤动作；
S206，所述策略集中控制装置向所述第一网络设备发送所述第一信息和所述第一QoS策略。
举例说明，例如参照图1，在AS1中部署QPPB，AS1中包括CR11，CR11可以是路由器或具有三层功能的交换机。CR11在QPPB实施过程中，作为BGP路由的发送端。所述BGP路由可以由所述CR11生成，也可以由其他网络设备生成，再经由CR11转发。所述其他网络设备可以位于AS1中，例如其他网络设备是位于AS1中的核心路由器。所述其他网络设备也可以位于AS1之外，例如图1所示，所述其他网络设备是AS2中的CR21。
举例说明，图3为本申请实施例的第一场景结构示意图。图3所示的组网场景与图1所示的组网场景的区别在于：增设策略集中控制装置，所述策略集中控制装置分别与第一网络设备CR11和CR12通信。例如对于CR11，CR11从AS2接收BGP路由，并对所述BGP路由进行转发。所述策略集中控 制装置接收来自CR11的所述BGP路由。可选择的，所述策略集中控制装置位于AS1中，或者所述策略集中控制装置位于AS1之外，或者将所述策略集中控制装置集成在CR11上。所述策略集中控制装置根据接收到的所述BGP路由生成第一信息，所述第一信息包括AS号码列表/或团体列表。所述第一信息作为所述BGP路由分类的标识。
举例说明，所述策略集中控制装置根据接收到的所述BGP路由生成第一信息的过程可以按照如下方式进行。所述策略集中控制装置接收到的所述BGP路由中携带有AS路径和团体属性，也就是说，每一条BGP路由均带有相应的AS路径和团体属性。例如，AS path：10 20 30 70 100 300 200代表该条BGP路由来自运营商1，AS path：40 60 80 90 400 500 600代表该条BGP路由来自运营商2。其中AS路径(AS path)的AS号码的具体数值和数量可以根据实际应用确定。又例如，Community：10:1 20:1 200:200 300:300代表该条BGP路由来自运营商1，Community：30:1 40:1 100:100 400:400代表该条BGP路由来自运营商2。其中团体属性(Community)的值和数量可以根据实际应用确定。通过直接提取BGP路由携带AS路径的AS号码和团体属性的值得到所述第一信息。例如，对于AS path：10 20 30 70 100 300 200，可以提取其中的“20 70”作为第一信息中的AS号码列表，用于标识BGP路由来运营商1；又例如，对于Community：10:1 20:1 200:200 300:300，可以提取“10:1 20:1”作为第一信息中的团体列表。
可选的，可以提取AS路径的AS号码的部分或全部作为第一信息中的AS号码列表，同样的，可以提取团体属性的值的部分或全部作为第一信息中的团体列表。
在实际应用中，可选的，可以仅将AS号码列表作为所述第一信息；或者仅将团体列表作为所述第一信息；或者为了使匹配规则更加准确，将AS号码列表和团体列表共同作为所述第一信息。
因此，相对于现有技术，策略集中控制装置可以直接在BGP路由中获得 AS号码列表和团体列表，省去了在发送端规划路由分类规则和配置入口策略的工作。
在实施例中，所述策略集中控制装置预先设置有QoS策略集合，所述QoS策略集合可以预先在所述策略集中控制装置中直接设置，也可以现在CR11中预先设置，再由CR11将所述QoS策略集合发送到所述策略集中控制装置中。所述QoS策略集合包括预先定义的全部路由过滤动作，所述路由过滤动作例如是重新标记IP优先级等。所述路由过滤动作可以包括一个动作或多个动作。所述策略集中控制装置通过预设的规则为第一信息配置相应的QoS策略。举例说明，假设所述策略集中控制装置预先设置的QoS策略集合中有20种路由过滤动作。所述策略集中控制装置将团体列表作为第一信息。所述策略集中控制装置根据BGP路由的信息提取可以得到Community 10:1(例如：代表该条BGP路由来自运营商1)。根据预设的规则希望对来自运营商1的BGP路由执行5种路由过滤动作。所述策略集中控制装置可以根据Community 10:1，在QoS策略集合中找到相应的5种路由过滤动作，并将这5种路由过滤动作组成与Community 10:1相对应的QoS策略。
在实施例中，所述策略集中控制装置完成QoS策略的配置之后，将向所述第一网络设备发送第一信息和第一QoS策略。可选的，所述策略集中控制装置可以通过BGP更新消息(BGP Update Message)携带所述第一信息和所述第一QoS策略；或者通过BGP FlowSpec更新消息(BGP FlowSpec Update Message)携带所述第一信息和所述第一QoS策略；或者通过其他协议报文携带所述第一信息和所述第一QoS策略。
现有技术中，CR21通过路由分类设置路由属性，BR111根据目的网段的路由属性设置QoS策略，不是在BGP路由中发送QoS策略。
本实施例提供的传播QoS策略的方法，通过增设策略集中控制装置，实现QPPB的自动化部署。在策略集中控制装置中完成QoS策略的集中配置，再将QoS策略传播到接收端，由接收端实施QoS策略的路由过滤动作。无需 对多个接收端分别实施QoS策略的预先变更，省去了在发送端规划路由分类规则和配置入口策略的工作，省去了在接收端匹配QoS局部标识和流行为名称的工作，简化QPPB的配置，降低维护难度。
可选的，所述路由过滤动作包括下列动作的至少一个：重新标记IP优先级(Remark IP-precedence)、重新标记服务类型tos(Remark tos)、重新标记多协议标记交换MPLS的实验比特位exp(Remark MPLS-exp)和重新标记IP的df(Remark IP-df)。
其中，Remark IP-precedence用于重新标记IP报文的优先级。Remark tos用于重新标记IP报文的tos值，tos在IP头中占8个比特位，通过配置tos值，可以对探测报文应用策略路由或者CAR(Committed Access Rate)等特性。Remark MPLS-exp用于重新标记MPLS报文的exp域值，exp(Experimental Use)是MPLS协议结构中定义的试用字段，在MPLS报文头中占3个比特位，现在通常用做CoS(Class of Service，服务等级)，即exp是用来设置MPLS报文的服务等级的。Remark IP-df用于重新标记IP报文的df字段的值，df(Don't Fragment)表示不允许报文分片。所述路由过滤动作可以包括上述动作中的一个或多个。非限制性的，本实施例只列举出常用的4种路由过滤动作，实施过程中也可以加入其他的路由过滤动作。
可选的，所述第一信息携带在BGP路由属性信息中；所述策略集中控制装置向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤包括：所述策略集中控制装置向所述第一网络设备发送BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略。
举例说明，所述第一信息携带在BGP路由属性信息中，即所述BGP路由属性信息包括以下中的一个：AS号码列表、团体列表、以及AS号码列表和团体列表。所述BGP路由属性信息携带在BGP更新消息中。所述策略集中控制装置可以向CR11发送BGP更新消息，所述BGP更新消息中携带有所述BGP路由属性信息和所述第一QoS策略。
可选的，所述BGP更新消息携带No-Advertise，所述策略集中控制装置还向所述AS中的第二网络设备发送所述BGP更新消息。
举例说明，图4为本申请实施例的第二场景结构示意图。图4所示的组网场景与图3所示的组网场景的区别在于：所述策略集中控制装置还分别与所述AS1中的第二网络设备BR111、BR121、BR112和BR122通信。以BR111为例，BR111作为QPPB实施过程中的接收端。所述策略集中控制装置还向所述AS1中的BR111发送所述BGP更新消息。所述BGP更新消息携带No-Advertise，No-Advertise表示带有该属性的路由信息不通告给任何BGP相邻体。CR11收到来自所述策略集中控制装置的所述BGP更新消息，由于所述BGP更新消息携带有No-Advertise，CR11将不向BR111转发所述BGP更新消息。因此，BR111只接收到来自所述策略集中控制装置的所述BGP更新消息。这样设置的目的是，BR111直接从策略集中控制装置接收BGP更新消息，从而节省CR11和BR111之间的通信带宽。
可选的，所述BGP更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP更新消息中携带了所述BGP路由属性信息和所述第一QoS策略。
举例说明，所述BGP更新消息可以携带路由过滤标识，所述路由过滤标识可以通过在BGP更新消息新增字段或使用已有字段的一个比特位实现。当所述路由过滤标识有效时，说明所述BGP更新消息中携带的所述BGP路由属性信息和所述第一QoS策略用于过滤路由。当所述路由过滤标识无效时，说明所述BGP更新消息是常规的BGP更新消息。这样设置的目的是，可以有效提高运行的效率。
可选的，所述第一信息携带在BGP FlowSpec中。
可选的，所述第一信息携带在所述BGP FlowSpec的网络层可达信息(network layer reachability information,NLRI)中。
可选的，所述第一信息携带在所述NLRI的中路由过滤组件中。
举例说明，BGP FlowSpec目前支持12种组件类型，参见表1。表1的第一栏是组件的类型(Type)，第二栏是用于第四版互联网协议(Internet Protocol version 4，IPv4)的组件，第三栏是用于第六版互联网协议(Internet Protocol version 6，IPv6)的组件。这些组件可以被封装到BGP FlowSpec更新消息的NLRI中。当满足所述NLRI中组件的逻辑条件时，执行BGP FlowSpec更新消息中携带的相应动作。所述NLRI可以包括表1中所示组件中的一个，或者多个，或者全部。
表1
Figure PCTCN2016109682-appb-000001
Figure PCTCN2016109682-appb-000002
本申请可以对BGP FlowSpec中的组件类型进行扩展。在BGP FlowSpec的组件类型中增加路由过滤组件，如表2所示。表2的第一栏是组件的类型(Type)，第二栏是路由过滤组件。所述路由过滤组件可以应用于IPv4，也可以应用于IPv6。表2的第一栏中的TBD1和TBD2用于表示：待定义(To be defined)，可以由标准组织定义。例如，延续BGP FlowSpec原有的类型数值，TBD1＝13，TBD2＝14。表2中定义出了常用的两种组件，非限定性的，也可以定义其他的组件。
表2
Figure PCTCN2016109682-appb-000003
表2所示的方式是在BGP FlowSpec目前支持的12种组件类型基础上进行扩展，增加路由过滤组件，所述路由过滤组件可以封装到所述NLRI中。作为可选的方案，所述路由过滤组件可以不在原有的12种组件类型基础上进行扩展，而是作为独立的组件，封装在所述NLRI中。作为可选的方案，所述路由过滤组件还可以直接携带到BGP FlowSpec更新消息中，而不封装在所述NLRI中。
可选的，所述策略集中控制装置向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤包括：所述策略集中控制装置向所述第一网络设备发送BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略。
举例说明，所述第一信息携带在NLRI中，即所述NLRI包括以下中的一个：AS号码列表、团体列表、以及AS号码列表和团体列表。所述NLRI携带于BGP FlowSpec更新消息中。所述策略集中控制装置可以向CR11发送BGP FlowSpec更新消息，所述BGP FlowSpec更新消息中携带有所述第一信息和所述第一QoS策略。
可选的，所述BGP FlowSpec更新消息携带No-Advertise，所述策略集中控制装置还向所述AS中的第二网络设备发送所述BGP FlowSpec更新消息。
举例说明，如图4所示，所述策略集中控制装置还分别与所述AS1中的第二网络设备BR111、BR121、BR112和BR122通信。以BR111为例，BR111作为QPPB实施过程中的接收端。所述策略集中控制装置还向所述AS1中的BR111发送所述BGP FlowSpec更新消息。所述BGP FlowSpec更新消息携带No-Advertise，No-Advertise表示带有该属性的路由信息不通告给任何BGP相邻体。CR11收到来自所述策略集中控制装置的所述BGP FlowSpec更新消息，由于所述BGP FlowSpec更新消息携带有No-Advertise，CR11将不向BR111转发所述BGP FlowSpec更新消息。因此，BR111只接收到来自所述策略集中控制装置的所述BGP FlowSpec更新消息。这样设置的目的是，BR111直接从策略集中控制装置接收BGP FlowSpec更新消息，从而节省CR11和BR111之间的通信带宽。
可选的，所述BGP FlowSpec更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP FlowSpec更新消息中携带了所述第一信息和所述第一QoS策略。
举例说明，所述BGP FlowSpec更新消息可以携带路由过滤标识，所述路由过滤标识可以通过在BGP FlowSpec更新消息新增字段或使用已有字段的一个比特位实现。当所述路由过滤标识有效时，说明所述BGP FlowSpec更新消息中携带的所述第一信息和所述第一QoS策略用于过滤路 由。当所述路由过滤标识无效时，说明所述BGP FlowSpec更新消息是常规的用于流量过滤的BGP FlowSpec更新消息。这样设置的目的是，可以通过路由过滤标识区分BGP FlowSpec更新消息是用于过滤路由，还是用于流量过滤，可以有效提高运行的效率。
可选的，所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作包括指定的动作(specific action)，所述指定的动作携带所述路由过滤标识。
可选的，所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。
举例说明，所述BGP FlowSpec包括流量过滤动作，如表3所示。表3中的第一栏是流量过滤动作的类型(Type)；第二栏是流量过滤动作的标识，具体是扩展团体属性；第三栏是实际的动作，即流量过滤动作。流量过滤动作可以封装到BGP FlowSpec更新消息中，当满足NLRI中组件的逻辑条件时，执行相应的流量过滤动作。所述流量过滤动作可以包括表3中所示的一个，或者多个，或者全部。
表3
Figure PCTCN2016109682-appb-000004
本申请可以对BGP FlowSpec中的流量过滤动作进行扩展，增加路由过滤动作，如表4所示。表4的第一栏是路由过滤动作的类型(Type)；第二栏是路由过滤动作的标识，具体是扩展团体属性；第三栏是实际的动作，即路由过滤动作。所述路由过滤动作可以应用于IPv4，也可以应用于IPv6。表4的第一栏中的TBD3、TBD4等用于表示：待定义(To be defined)，可以由标准组织定义。表4中定义出了常用的四种路由过滤动作，非限定性的，也可以定义其他的路由过滤动作。另外，表3中的设定流量速率和标记DSCP值可以用作路由过滤动作。
表4
Figure PCTCN2016109682-appb-000005
表4所示的方式是在BGP FlowSpec目前支持的流量过滤动作基础上进行扩展，增加路由过滤动作，所述路由过滤动作可以封装到BGP FlowSpec更新消息中。当满足NLRI中用于路由过滤组件的逻辑条件时，执行相应的路由过滤动作。作为可选的方案，所述路由过滤动作可以不在原有的流量过滤动作基础上进行扩展，而是作为独立的路由过滤动作，直接携带到BGP FlowSpec更新消息中。这样设置的好处在于，对现有的流量过滤动作进行扩展，增加路由过滤动作，无需改变BGP FlowSpec的结构。
如表3所示的扩展团体属性中包括流量动作(traffic-action)，流量动作所指示的实际的动作是指定的动作(specific action)。所述流量动作扩 展团体属性包括6个字节。其中，S比特位(第46比特位)表示“采样”，即当S比特位使能时，表示流量采样，并记录日志。T比特位(第47比特位)表示“终结动作”，即当该比特被置位，流量过滤引擎应该使用后继的过滤规则(排序规程中定义的)。如果没有置位，当本规则应用之后的流量过滤规则停止匹配。如图7所示，定义Q比特位(第45比特位)，用于指示所述BGP FlowSpec更新消息中携带了用于过滤路由的所述第一信息和所述第一QoS策略。当Q比特位置位时，表示所述BGP FlowSpec更新消息中携带了用于过滤路由的所述第一信息和所述第一QoS策略。
通过实施例的方案，通过增设策略集中控制装置，实现QPPB的自动化部署，无需对多个接收端分别实施QoS策略的预先变更，省去了在发送端规划路由分类规则和设置入口策略的工作，省去了在接收端匹配QoS局部标识和流行为名称的工作，简化QPPB的配置，降低维护难度。
图5为本申请实施例的第一网络设备执行的传播QoS策略的方法的流程图。本申请该实施例是从第一网络设备的角度，对传播QoS策略的方法进行说明。如图5所示，所述第一网络设备执行以下步骤：
S502，AS中的第一网络设备向策略集中控制装置发送BGP路由；
S504，所述第一网络设备接收来自所述策略集中控制装置的第一信息和与所述第一信息对应的第一QoS策略，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
S506，所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略。
在实施例中，AS中包括第一网络设备。第二网络设备可以位于AS之内，也可以位于AS之外，例如，所述第二网络设备位于第三AS。所述第二网络设备与所述第一网络设备通信，接收来自所述第一网络设备的BGP路由。
举例说明，参照图3，在AS1中部署QPPB，所述AS1中包括CR11，CR11 可以是路由器或具有三层功能的交换机。CR11在QPPB实施过程中，作为BGP路由的发送端。所述BGP路由可以由CR11生成，也可以由其他网络设备生成，再经由CR11转发。所述其他网络设备可以位于AS1中，例如其他网络设备是位于AS1中的核心路由器。所述其他网络设备也可以位于AS1之外，例如图3所示，所述其他网络设备是AS2中的CR21。CR11与所述策略集中控制装置通信，向所述策略集中控制装置发送所述BGP路由。
在实施例中，CR11接收来自所述策略集中控制装置的第一信息和所述第一QoS策略。可选的，所述第一信息和所述第一QoS策略可以携带在BGP更新消息、BGP FlowSpec更新消息或其他协议报文中。所述第一信息的生成过程和根据所述第一信息生成所述第一QoS策略的过程参见图2对应实施例的相应描述，此处不再进行赘述。
举例说明，参照图3，CR11向所述AS1中的BR111转发所述第一信息和所述第一QoS策略。BR111可以是路由器或具有三层功能的交换机。可选的，所述第一信息和所述第一QoS策略可以携带在BGP更新消息、BGP FlowSpec更新消息或其他协议报文中。CR11配置有undo local-install命令，表示不执行本地安装，具体的表示CR11不根据所述第一信息执行所述第一QoS策略，所述CR11只对所述第一信息和所述第一QoS策略进行转发。所述undo local-install命令是现有的配置命令，具体的执行过程不再进行赘述。
举例说明，参见图3，CR11与所述策略集中控制装置通信。CR11从AS2接收BGP路由，并将所述BGP路由转发到所述策略集中控制装置。所述策略集中控制装置根据所述BGP路由生成第一信息，并根据所述第一信息匹配QoS策略。然后，将所述第一信息和所述第一QoS策略发送到CR11。CR11与BR111通信，从而将所述第一信息和所述第一QoS策略转发到BR111。
可选的，所述路由过滤动作包括下列动作的至少一个：重新标记IP优先级、重新标记tos、重新标记MPLS的exp和重新标记IP的df。对上述参数的解释和作用参见图2对应实施例的相应描述，此处不进行赘述。
可选的，所述第一信息携带在BGP路由属性信息中，所述第一网络设备接收来自所述策略集中控制装置的第一信息和所述第一QoS策略步骤包括：所述第一网络设备接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略步骤包括：所述第一网络设备向所述第二网络设备转发所述BGP更新消息。
举例说明，结合前述图2对应实施例的相应描述，所述第一信息和所述第一QoS策略可以携带在所述BGP更新消息中，由所述策略集中控制装置发送到CR11。CR11接收到所述BGP更新消息，并将所述BGP更新消息转发到BR111。
可选的，所述第一信息携带在BGP FlowSpec中；进一步可选的，所述第一信息携带在所述BGP FlowSpec的NLRI中；再进一步可选的，所述第一信息携带在所述NLRI的中路由过滤组件中。
可选的，所述第一网络设备接收来自所述策略集中控制装置的第一信息和所述第一QoS策略步骤包括：所述第一网络设备接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述QoS策略；所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略步骤包括：所述第一网络设备向所述第二网络设备转发所述BGP FlowSpec更新消息。
举例说明，结合前述图2对应实施例的相应描述，所述第一信息和所述第一QoS策略可以携带在所述BGP FlowSpec更新消息中，由所述策略集中控制装置发送到所述CR11。CR11接收到所述BGP FlowSpec更新消息，并将所述BGP FlowSpec更新消息转发到BR111。
通过实施例的方案，第一网络设备收到第一信息和第一QoS策略，并将所述第一信息和所述第一QoS策略转发到第二网络设备。从而所述第一网络设备无需配置入口策略，省去了在所述第一网络设备上规划路由分类规则的工作。
图6为本申请实施例的第二网络设备执行的传播QoS策略的方法的流程图。本申请该实施例是从第二网络设备的角度，对传播QoS策略的方法进行说明。如图6所示，所述第二网络设备执行以下步骤：
S602，第二网络设备接收来自AS中的第一网络设备的BGP路由；
S604，所述第二网络设备接收第一信息和与所述第一信息对应的第一QoS策略，所述第一信息和所述第一QoS策略来自所述AS中的第一网络设备或策略集中控制装置，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
S606，所述第二网络设备在所述BGP路由中查找与所述第一信息匹配的BGP路由表项；
S608，所述第二网络设备将所述路由过滤动作应用在所述BGP路由表项下发的FIB表项中。
在实施例中，AS中包括第一网络设备。第二网络设备可以位于AS之内，也可以位于AS之外，例如，所述第二网络设备位于第三AS。所述第二网络设备与所述第一网络设备通信，接收来自所述第一网络设备的BGP路由。所述BGP路由可以由所述第一网络设备生成，也可以由其他网络设备生成，再经由所述第一网络设备转发。所述其他网络设备可以位于AS中，也可以位于AS之外，例如，所述其他网络设备位于第二AS。所述第二网络设备接收来自所述第一网络设备的BGP路由，然后对所述BGP路由应用QoS策略。
所述第一QoS策略由策略集中控制装置根据第一信息生成，所述第一信息根据所述BGP路由生成。所述第一QoS策略包括路由过滤动作。所述第二网络设备接收所述第一信息和所述第一QoS策略。所述第一信息和所述第一QoS策略可以由所述策略集中控制装置发送到所述第一网络设备，再由第一网络设备转发给所述第二网络设备；或者由所述策略集中控制装置直接发送给所述第二网络设备。具体实施过程参见图2-图5对应实施例的相应描 述。
举例说明，参见图3，BR111根据所述第一信息在所述BGP路由中查找与所述第一信息匹配的BGP路由表项。例如，可以通过以下方式实现：所述BGP路由可以携带在BGP更新消息中，由CR11发送到所述第二网络设备。所述BGP路由携带有标识信息，例如AS路径和团体属性。而且，所述BGP路由可以包括一条BGP路由表项或多条BGP路由表项。因此，每一条BGP路由表项都具有属于自己的标识信息。所述第一信息包括了AS号码列表和团体列表，因此可以根据所述第一信息查找所述BGP路由中的BGP路由表项。举例来讲，BGP路由中包括多条BGP路由表项，有的BGP路由表项来自运营商1，则BGP路由表项的标识可以是AS path：10 20 30 70 100 300 200；有的BGP路由表项来自运营商2，则BGP路由表项的标识可以是AS path：40 60 80 90 400 500 600。所述第一信息的AS号码列表信息是AS path：20 70，通过查找，可以将BGP路由中所有标识了AS path：20 70的BGP路由表项确定出来，形成了来自运营商1的BGP路由表项集合。BR111可以将所述第一信息对应的第一QoS策略应用在来自运营商1的BGP路由表项集合下发的FIB表项上。
BR111接收所述第一信息和所述第一QoS策略，以及BR111接收来自所述AS1中的CR11的BGP路由不需要进行同步。举例来讲，假设BR111先接收到全部BGP路由，再接收到所述第一信息和所述第一QoS策略，则BR111根据所述第一信息对接收到的全部BGP路由实施所述第一QoS策略。又假设BR111先接收到部分BGP路由时，所述第一信息和所述第一QoS策略到达BR111所述第二网络设备，则BR111所述第二网络设备根据所述第一信息实时的对后续到达所述第二网络设备的BGP路由实施所述第一QoS策略，然后再对所述第一信息和所述QoS策略到达之前接收到的那部分BGP路由实施所述第一QoS策略。又假设BR111所述第二网络设备先接收到所述第一信息和所述第一QoS策略，则BR111所述第二网络设备根据所述第一信 息实时的对后续到达BR111所述第二网络设备的BGP路由实施所述第一QoS策略。
可选的，所述路由过滤动作包括下列动作的至少一个：重新标记互联网协议IP优先级、重新标记服务类型tos、重新标记多协议标记交换MPLS的实验比特位exp和重新标记IP的df。具体解释参见图2对应实施例的相应描述。
可选的，所述第一信息携带在BGP路由属性信息中；所述第二网络设备接收来自所述第一网络设备的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；或者，所述第二网络设备接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息、所述第一QoS策略和No-Advertise。具体解释参见图2-图5对应实施例的相应描述。
可选的，所述第一信息携带在BGP FlowSpec中；进一步可选的，所述第一信息携带在所述BGP FlowSpec的NLRI中；再进一步可选的，所述第一信息携带在所述NLRI的中路由过滤组件中。
可选的，所述第二网络设备接收来自所述第一网络设备的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；或者，所述第二网络设备接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息、所述第一QoS策略和No-Advertise。具体解释参见图2-图5对应实施例的相应描述。
可选的，所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。具体解释参见图2对应实施例的相应描述。
可选的，所述第二网络设备配置有undo local-install命令，表示不执行本地安装，具体的表示所述第二网络设备不执行所述第一QoS策略。如此这样，在存在多个第二网络设备的场景中，可以选择部分第二网络设备执行所述 第一QoS策略。
通过实施例的方案，无需在接收端上配置QoS策略，当具有多个接收端时，无需对多个接收端分别实施QoS策略的预先变更。而且省去了在接收端匹配QoS局部标识和流行为名称的工作，简化QPPB的配置，降低维护难度。
图8为本发明实施例的策略集中控制装置800的结构示意图。图8所示的策略集中控制装置可以执行上述实施例的方法中策略集中控制装置执行的相应步骤。如图8所示，所述策略集中控制装置800包括接收单元802，生成单元804和发送单元806，其中：
所述接收单元802，用于根据接收到的来自AS中的第一网络设备的BGP路由生成第一信息，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表；
所述生成单元804，用于根据所述第一信息生成与所述第一信息对应的第一QoS策略，所述第一QoS策略包括路由过滤动作；
所述发送单元806，用于向所述第一网络设备发送所述第一信息和所述第一QoS策略。
可选的，所述第一信息携带在BGP路由属性信息中；所述发送单元，具体用于向所述第一网络设备发送BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略。
可选的，所述BGP更新消息携带No-Advertise；所述发送单元，还用于向所述AS中的第二网络设备发送所述BGP更新消息。
可选的，所述BGP更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP更新消息中携带了所述BGP路由属性信息和所述第一QoS策略。
可选的，所述第一信息携带在BGP FlowSpec中；进一步可选的，所述第一信息携带在所述BGP FlowSpec的NLRI中；再进一步可选的，所述第一信息携带在所述NLRI的中路由过滤组件中。
可选的，所述发送单元，具体用于向所述第一网络设备发送BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略。
可选的，所述BGP FlowSpec更新消息携带No-Advertise；所述发送单元，还用于向所述AS中的第二网络设备发送所述BGP FlowSpec更新消息。
可选的，所述BGP FlowSpec更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP FlowSpec更新消息中携带了所述第一信息和所述第一QoS策略。
可选的，所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作包括指定的动作，所述指定的动作携带所述路由过滤标识。
可选的，所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。
图8所示的策略集中控制装置可以执行上述实施例的方法中策略集中控制装置执行的相应步骤。从而，无需对多个接收端分别实施QoS策略的预先变更，省去了在发送端规划路由分类规则和配置入口策略的工作，省去了在接收端匹配QoS局部标识和流行为名称的工作，简化QPPB的配置，降低维护难度。
图11为本发明实施例的策略集中控制装置1100的硬件结构示意图。图11所示的策略集中控制装置可以执行上述实施例的方法中策略集中控制装置执行的相应步骤。
如图11所示，所述策略集中控制装置1100包括处理器1101、存储器1102、接口1103和总线1104，其中接口1103可以通过无线或有线的方式实现，具体来讲可以是例如网卡等元件，上述处理器1101、存储器1102和接口1103通过总线1104连接。
所述接口1103具体可以包括发送器和接收器，用于策略集中控制装置与上述实施例中的所述第一网络设备之间收发信息；或者用于策略集中控 制装置与上述实施例中的所述第一网络设备及所述第二网络设备之间收发信息。作为举例，所述接口1103用于支持图2中的过程S202和S206。所述处理器1101用于执行图2中策略集中控制装置所执行的步骤。作为举例，所述处理器1101用于支持图2中的过程S204。存储器1102用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成图2～6中任一策略集中控制装置的功能或图2～6中任一策略集中控制装置所执行的步骤。
可以理解的是，图11仅仅示出了策略集中控制装置的简化设计。在实际应用中，策略集中控制装置可以包含任意数量的接口，处理器，存储器等，而所有可以实现本发明的策略集中控制装置都在本发明的保护范围之内。
图9为本发明实施例的第一网络设备900的结构示意图。图9所示的第一网络设备可以执行上述实施例的方法中第一网络设备执行的相应步骤。如图9所示，所述第一网络设备900位于AS，中包括发送单元902和接收单元904，其中：
所述发送单元902，用于向策略集中控制装置发送BGP路由；
所述接收单元904，用于接收来自所述策略集中控制装置的第一信息和与所述第一信息对应的第一QoS策略，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
所述发送单元902，还用于向第二网络设备转发所述第一信息和所述第一QoS策略。
可选的，所述第一信息携带在BGP路由属性信息中；所述接收单元904，具体用于接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；
所述发送单元902，具体用于向所述第二网络设备转发所述BGP更新消息。
可选的，所述第一信息携带在BGP FlowSpec中；进一步可选的，所述第一信息携带在所述BGP FlowSpec的NLRI中；再进一步可选的，所述第一信息携带在所述NLRI的中路由过滤组件中。
可选的，所述接收单元904，具体用于接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；所述发送单元902，具体用于向所述第二网络设备转发所述BGP FlowSpec更新消息。
图9所示的第一网络设备可以执行上述实施例的方法中第一网络设备执行的相应步骤。从而，所述第一网络设备无需配置入口策略，省去了在所述第一网络设备上规划路由分类规则的工作。
图12为本发明实施例的第一网络设备1200的硬件结构示意图。图12所示的第一网络设备可以执行上述实施例的方法中第一网络设备执行的相应步骤。
如图12所示，所述第一网络设备1200包括处理器1201、存储器1202、接口1203和总线1204，其中接口1203可以通过无线或有线的方式实现，具体来讲可以是例如网卡等元件，上述处理器1201、存储器1202和接口1203通过总线1204连接。
所述接口1203具体可以包括发送器和接收器，用于第一网络设备与上述实施例中的所述策略集中控制装置和所述第二网络设备之间收发信息。作为举例，所述接口1203用于支持图5中的过程S502、S504和S506。所述处理器1201用于执行图5中涉及第一网络设备的处理过程和/或用于本申请所描述的技术的其他过程。存储器1202用于存储第一网络设备的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成图2～6中任一第一网络设备的功能或图2～6中任一第一网络设备所执行的步 骤。
可以理解的是，图12仅仅示出了第一网络设备的简化设计。在实际应用中，第一网络设备可以包含任意数量的接口，处理器，存储器等，而所有可以实现本发明的第一网络设备都在本发明的保护范围之内。
图10为本发明实施例的第二网络设备1000的结构示意图。图10所示的第二网络设备可以执行上述实施例的方法中第二网络设备执行的相应步骤。如图10所示，所述第二网络设备1000包括接收单元1002，查找单元1004和应用单元1006，其中：
所述接收单元1002，用于接收来自AS中的第一网络设备的BGP路由；
所述接收单元1002，还用于接收第一信息和与所述第一信息对应的第一QoS策略，所述第一信息和所述第一QoS策略来自所述AS中的第一网络设备或策略集中控制装置，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
所述查找单元1004，用于在所述BGP路由中查找与所述第一信息匹配的BGP路由表项；
所述应用单元1006，用于将所述路由过滤动作应用在所述BGP路由表项下发的FIB表项中。
可选的，所述第一信息携带在BGP路由属性信息中；所述接收单元1002，用于接收来自所述第一网络设备的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；或者，所述接收单元1002，用于接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息、所述第一QoS策略和No-Advertise。
可选的，所述第一信息携带在BGP FlowSpec中；进一步可选的，所述第一信息携带在所述BGP FlowSpec的NLRI中；再进一步可选的，所述第一信息携带在所述NLRI的中路由过滤组件中。
可选的，所述接收单元1002，用于接收来自所述第一网络设备的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；或者，所述接收单元1002，用于接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息、所述第一QoS策略和No-Advertise。
可选的，所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。
图10所示的第二网络设备可以执行上述实施例的方法中第二网络设备执行的相应步骤。从而，无需在接收端上配置QoS策略，当具有多个接收端时，无需对多个接收端分别实施QoS策略的预先变更。而且省去了在接收端匹配QoS局部标识和流行为名称的工作，简化QPPB的配置，降低维护难度。
图13为本发明实施例的第二网络设备1300的硬件结构示意图。图13所示的第二网络设备可以执行上述实施例的方法中第二网络设备执行的相应步骤。
如图13所示，所述第二网络设备1300包括处理器1301、存储器1302、接口1303和总线1304，其中接口1303可以通过无线或有线的方式实现，具体来讲可以是例如网卡等元件，上述处理器1301、存储器1302和接口1303通过总线1304连接。
所述接口1303具体可以包括接收器，用于第二网络设备与上述实施例中的所述第一网络设备之间收发信息；或者用于第二网络设备与上述实施例中的所述第一网络设备及所述策略集中控制装置之间收发信息。作为举例，所述接口1303用于支持图6中的过程S602和S604。所述处理器1301用于执行图6中涉及第二网络设备的处理过程和/或用于本申请所描述的技术的其他过程。作为举例，所述处理器1301用于支持图6中的过程S606和S608。存储器1302用于存储第二网络设备的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成图2～6中任一第二网络设备的 功能或图2～6中任一第二网络设备所执行的步骤。
可以理解的是，图13仅仅示出了第二网络设备的简化设计。在实际应用中，第二网络设备可以包含任意数量的接口，处理器，存储器等，而所有可以实现本发明的第二网络设备都在本发明的保护范围之内。
另外，如图14所示，本发明实施例还提供了一种网络系统1400。所述网络系统可以包括前述图8或图11对应的实施例提供的策略集中控制装置、图9或图12对应的实施例提供的第一网络设备和图10或图13对应的实施例提供的第二网络设备。其中图14所示的虚线表示：可选的，策略集中控制装置向第二网络设备发送信息，或者理解为，第二网络设备接收来自策略集中控制装置的信息，其中所述信息可以是第一信息和与所述第一信息对应的第一QoS策略。在此不再对策略集中控制装置、第一网络设备和第二网络设备进行赘述。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程 序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (51)

  1. 一种传播服务质量QoS策略的方法，其特征在于，所述方法包括：
    根据接收到的来自自治系统AS中的第一网络设备的边界网关协议BGP路由生成第一信息，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表；
    根据所述第一信息生成与所述第一信息对应的第一QoS策略，所述第一QoS策略包括路由过滤动作；
    向所述第一网络设备发送所述第一信息和所述第一QoS策略。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一信息携带在BGP路由属性信息中；所述向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤包括：
    向所述第一网络设备发送BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略。
  3. 根据权利要求2所述的方法，其特征在于，
    所述BGP更新消息携带No-Advertise；所述向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤还包括：
    向所述AS中的第二网络设备发送所述BGP更新消息。
  4. 根据权利要求2或3所述的方法，其特征在于，
    所述BGP更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP更新消息中携带了所述BGP路由属性信息和所述第一QoS策略。
  5. 根据权利要求1所述的方法，其特征在于，
    所述第一信息携带在边界网关协议流规则BGP FlowSpec中。
  6. 根据权利要求5所述的方法，其特征在于，
    所述第一信息携带在所述BGP FlowSpec的网络层可达信息NLRI中。
  7. 根据权利要求6所述的方法，其特征在于，
    所述第一信息携带在所述NLRI的中路由过滤组件中。
  8. 根据权利要求5至7任一项所述的方法，其特征在于，
    所述向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤包括：
    向所述第一网络设备发送BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略。
  9. 根据权利要求8所述的方法，其特征在于，
    所述BGP FlowSpec更新消息携带No-Advertise；所述向所述第一网络设备发送所述第一信息和所述第一QoS策略步骤还包括：向所述AS中的第二网络设备发送所述BGP FlowSpec更新消息。
  10. 根据权利要求8或9所述的方法，其特征在于，
    所述BGP FlowSpec更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP FlowSpec更新消息中携带了所述第一信息和所述第一QoS策略。
  11. 根据权利要求10所述的方法，其特征在于，
    所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作包括指定的动作，所述指定的动作携带所述路由过滤标识。
  12. 根据权利要求5至11任一项所述的方法，其特征在于，
    所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。
  13. 一种传播服务质量QoS策略的方法，其特征在于，所述方法包括：
    自治系统AS中的第一网络设备向策略集中控制装置发送边界网关协议BGP路由；
    所述第一网络设备接收来自所述策略集中控制装置的第一信息和与所述第一信息对应的第一QoS策略，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
    所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略。
  14. 根据权利要求13所述的方法，其特征在于，
    所述第一信息携带在BGP路由属性信息中，所述第一网络设备接收来自所述策略集中控制装置的第一信息和所述第一QoS策略步骤包括：
    所述第一网络设备接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；
    所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略步骤包括：
    所述第一网络设备向所述第二网络设备转发所述BGP更新消息。
  15. 根据权利要求13所述的方法，其特征在于，
    所述第一信息携带在边界网关协议流规则BGP FlowSpec中。
  16. 根据权利要求15所述的方法，其特征在于，
    所述第一信息携带在所述BGP FlowSpec的网络层可达信息NLRI中。
  17. 根据权利要求16所述的方法，其特征在于，
    所述第一信息携带在所述NLRI的中路由过滤组件中。
  18. 根据权利要求15至17任一项所述的方法，其特征在于，
    所述第一网络设备接收来自所述策略集中控制装置的第一信息和所述第一QoS策略步骤包括：
    所述第一网络设备接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；
    所述第一网络设备向第二网络设备转发所述第一信息和所述第一QoS策略步骤包括：
    所述第一网络设备向所述第二网络设备转发所述BGP FlowSpec更新消息。
  19. 一种传播服务质量QoS策略的方法，其特征在于，所述方法包括：
    第二网络设备接收来自自治系统AS中的第一网络设备的边界网关协议BGP路由；
    所述第二网络设备接收第一信息和与所述第一信息对应的第一QoS策略，所述第一信息和所述第一QoS策略来自所述AS中的第一网络设备或策略集中控制装置，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
    所述第二网络设备在所述BGP路由中查找与所述第一信息匹配的BGP路由表项；
    所述第二网络设备将所述路由过滤动作应用在所述BGP路由表项下发的转发信息库FIB表项中。
  20. 根据权利要求19所述的方法，其特征在于，
    所述第一信息携带在BGP路由属性信息中；
    所述第二网络设备接收来自所述第一网络设备的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；或者，
    所述第二网络设备接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息、所述第一QoS策略和No-Advertise。
  21. 根据权利要求19所述的方法，其特征在于，
    所述第一信息携带在边界网关协议流规则BGP FlowSpec中。
  22. 根据权利要求21所述的方法，其特征在于，
    所述第一信息携带在所述BGP FlowSpec的网络层可达信息NLRI中。
  23. 根据权利要求22所述的方法，其特征在于，
    所述第一信息携带在所述NLRI的中路由过滤组件中。
  24. 根据权利要求21至23任一项所述的方法，其特征在于，
    所述第二网络设备接收来自所述第一网络设备的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；或者，
    所述第二网络设备接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息、所述第一QoS策略和No-Advertise。
  25. 根据权利要求21至24任一项所述的方法，其特征在于，
    所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。
  26. 一种策略集中控制装置，其特征在于，包括：
    接收单元，用于根据接收到的来自自治系统AS中的第一网络设备的边界网关协议BGP路由生成第一信息，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表；
    生成单元，用于根据所述第一信息生成与所述第一信息对应的第一QoS策略，所述第一QoS策略包括路由过滤动作；
    发送单元，用于向所述第一网络设备发送所述第一信息和所述第一QoS策略。
  27. 根据权利要求26所述的策略集中控制装置，其特征在于，
    所述第一信息携带在BGP路由属性信息中；所述发送单元，具体用于向所述第一网络设备发送BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略。
  28. 根据权利要求27所述的策略集中控制装置，其特征在于，
    所述BGP更新消息携带No-Advertise；所述发送单元，还用于向所述AS中的第二网络设备发送所述BGP更新消息。
  29. 根据权利要求27或28所述的策略集中控制装置，其特征在于，
    所述BGP更新消息携带路由过滤标识，所述路由过滤标识用于指示所 述BGP更新消息中携带了所述BGP路由属性信息和所述第一QoS策略。
  30. 根据权利要求26所述的策略集中控制装置，其特征在于，
    所述第一信息携带在边界网关协议流规则BGP FlowSpec中。
  31. 根据权利要求30所述的策略集中控制装置，其特征在于，
    所述第一信息携带在所述BGP FlowSpec的网络层可达信息NLRI中。
  32. 根据权利要求31所述的策略集中控制装置，其特征在于，
    所述第一信息携带在所述NLRI的中路由过滤组件中。
  33. 根据权利要求30至32任一项所述的策略集中控制装置，其特征在于，
    所述发送单元，具体用于向所述第一网络设备发送BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略。
  34. 根据权利要求33所述的策略集中控制装置，其特征在于，
    所述BGP FlowSpec更新消息携带No-Advertise；所述发送单元，还用于向所述AS中的第二网络设备发送所述BGP FlowSpec更新消息。
  35. 根据权利要求33或34所述的策略集中控制装置，其特征在于
    所述BGP FlowSpec更新消息携带路由过滤标识，所述路由过滤标识用于指示所述BGP FlowSpec更新消息中携带了所述第一信息和所述第一QoS策略。
  36. 根据权利要求35所述的策略集中控制装置，其特征在于，
    所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作包括指定的动作，所述指定的动作携带所述路由过滤标识。
  37. 根据权利要求30至36任一项所述的策略集中控制装置，其特征在于，
    所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。
  38. 一种第一网络设备，所述第一网络设备位于自治系统AS中，其特 征在于，包括：
    发送单元，用于向策略集中控制装置发送边界网关协议BGP路由；
    接收单元，用于接收来自所述策略集中控制装置的第一信息和与所述第一信息对应的第一QoS策略，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
    所述发送单元，还用于向第二网络设备转发所述第一信息和所述第一QoS策略。
  39. 根据权利要求38所述的第一网络设备，其特征在于，
    所述第一信息携带在BGP路由属性信息中；
    所述接收单元，具体用于接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；
    所述发送单元，具体用于向所述第二网络设备转发所述BGP更新消息。
  40. 根据权利要求38所述的第一网络设备，其特征在于，
    所述第一信息携带在边界网关协议流规则BGP FlowSpec中。
  41. 根据权利要求40所述的第一网络设备，其特征在于，
    所述第一信息携带在所述BGP FlowSpec的网络层可达信息NLRI中。
  42. 根据权利要求41所述的第一网络设备，其特征在于，
    所述第一信息携带在所述NLRI的中路由过滤组件中。
  43. 根据权利要求40至42任一项所述的方法，其特征在于，
    所述接收单元，具体用于接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；
    所述发送单元，具体用于向所述第二网络设备转发所述BGP FlowSpec更新消息。
  44. 一种第二网络设备，其特征在于，包括：
    接收单元，用于接收来自自治系统AS中的第一网络设备的边界网关协议BGP路由；
    所述接收单元，还用于接收第一信息和与所述第一信息对应的第一QoS策略，所述第一信息和所述第一QoS策略来自所述AS中的第一网络设备或策略集中控制装置，所述第一信息根据所述BGP路由生成，所述第一信息包括以下中的一个或多个：AS号码列表、团体列表，所述第一QoS策略根据所述第一信息生成，所述第一QoS策略包括路由过滤动作；
    查找单元，用于在所述BGP路由中查找与所述第一信息匹配的BGP路由表项；
    应用单元，用于将所述路由过滤动作应用在所述BGP路由表项下发的转发信息库FIB表项中。
  45. 根据权利要求44所述的第二网络设备，其特征在于，
    所述第一信息携带在BGP路由属性信息中；
    所述接收单元，用于接收来自所述第一网络设备的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息和所述第一QoS策略；或者，
    所述接收单元，用于接收来自所述策略集中控制装置的BGP更新消息，所述BGP更新消息包括所述BGP路由属性信息、所述第一QoS策略和No-Advertise。
  46. 根据权利要求44所述的第二网络设备，其特征在于，
    所述第一信息携带在边界网关协议流规则BGP FlowSpec中。
  47. 根据权利要求46所述的第二网络设备，其特征在于，
    所述第一信息携带在所述BGP FlowSpec的网络层可达信息NLRI中。
  48. 根据权利要求47所述的第二网络设备，其特征在于，
    所述第一信息携带在所述NLRI的中路由过滤组件中。
  49. 根据权利要求46至48任一项所述的第二网络设备，其特征在于，
    所述接收单元，用于接收来自所述第一网络设备的BGP FlowSpec更新 消息，所述BGP FlowSpec更新消息包括所述第一信息和所述第一QoS策略；或者，
    所述接收单元，用于接收来自所述策略集中控制装置的BGP FlowSpec更新消息，所述BGP FlowSpec更新消息包括所述第一信息、所述第一QoS策略和No-Advertise。
  50. 根据权利要求46至49任一项所述的第二网络设备，其特征在于，
    所述BGP FlowSpec包括流量过滤动作，所述流量过滤动作携带所述路由过滤动作。
  51. 一种网络系统，其特征在于，所述网络系统包括策略集中控制装置、第一网络设备和第二网络设备，所述策略集中控制装置为权利要求26至37所述的任一策略集中控制装置，所述第一网络设备为权利要求38至43所述的任一第一网络设备，所述第二网络设备为权利要求44至49所述的任一第二网络设备。
PCT/CN2016/109682 2015-12-24 2016-12-13 一种传播QoS策略的方法、装置及系统 WO2017107814A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510988407.4 2015-12-24
CN201510988407.4A CN106921572B (zh) 2015-12-24 2015-12-24 一种传播QoS策略的方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2017107814A1 true WO2017107814A1 (zh) 2017-06-29

Family

ID=59089103

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/109682 WO2017107814A1 (zh) 2015-12-24 2016-12-13 一种传播QoS策略的方法、装置及系统

Country Status (2)

Country Link
CN (1) CN106921572B (zh)
WO (1) WO2017107814A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113259243A (zh) * 2021-04-26 2021-08-13 深圳市奇虎智能科技有限公司 路由器的自动应用拦截方法、系统、存储介质及计算机设备
EP3806401A4 (en) * 2018-07-10 2021-08-18 Huawei Technologies Co., Ltd. METHOD OF SENDING AND RECEIVING MESSAGES, DEVICE AND SYSTEM
CN113872861A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 一种生成表项的方法、发送报文的方法及设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391561B (zh) * 2017-08-10 2022-09-30 中国电信股份有限公司 动态双向保障方法和系统
CN108737150B (zh) * 2017-09-28 2019-07-05 新华三信息安全技术有限公司 承诺访问速率管理方法、业务板及主控板
CN113438159B (zh) * 2020-03-23 2023-04-18 华为技术有限公司 分段路由策略的传输方法及装置、网络传输系统
CN111726290B (zh) * 2020-07-23 2021-12-17 迈普通信技术股份有限公司 路由控制方法、装置、边界网关及可读存储介质
CN112532519B (zh) * 2020-12-21 2022-07-22 安徽皖通邮电股份有限公司 一种采用BGP Flow Specification控制数据流量行为的方法
CN115051951B (zh) * 2021-02-26 2024-04-19 中国电信股份有限公司 业务流调度方法、集中控制器以及存储介质
CN114143085B (zh) * 2021-11-30 2023-08-01 中国人民解放军国防科技大学 一种基于自编码器的bgp团体属性异常检测方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060164995A1 (en) * 2005-01-27 2006-07-27 Martin Djernaes Method and apparatus for context-based prefix updates in border gateway protocol
CN1852239A (zh) * 2005-10-12 2006-10-25 华为技术有限公司 一种通过边界网关协议实施路由策略的方法
CN101047651A (zh) * 2007-04-23 2007-10-03 杭州华为三康技术有限公司 设置ip优先级的方法、系统和设备
CN101471880A (zh) * 2007-12-27 2009-07-01 华为技术有限公司 数据处理方法与系统、路由装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902391B (zh) * 2010-03-15 2013-01-16 杭州华三通信技术有限公司 基于智能的静态路由进行报文转发的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060164995A1 (en) * 2005-01-27 2006-07-27 Martin Djernaes Method and apparatus for context-based prefix updates in border gateway protocol
CN1852239A (zh) * 2005-10-12 2006-10-25 华为技术有限公司 一种通过边界网关协议实施路由策略的方法
CN101047651A (zh) * 2007-04-23 2007-10-03 杭州华为三康技术有限公司 设置ip优先级的方法、系统和设备
CN101471880A (zh) * 2007-12-27 2009-07-01 华为技术有限公司 数据处理方法与系统、路由装置

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3806401A4 (en) * 2018-07-10 2021-08-18 Huawei Technologies Co., Ltd. METHOD OF SENDING AND RECEIVING MESSAGES, DEVICE AND SYSTEM
US11895021B2 (en) 2018-07-10 2024-02-06 Huawei Technologies Co., Ltd. Message sending and receiving method, apparatus, and system
CN113872861A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 一种生成表项的方法、发送报文的方法及设备
CN113872861B (zh) * 2020-06-30 2023-07-18 华为技术有限公司 一种生成表项的方法、发送报文的方法及设备
CN113259243A (zh) * 2021-04-26 2021-08-13 深圳市奇虎智能科技有限公司 路由器的自动应用拦截方法、系统、存储介质及计算机设备

Also Published As

Publication number Publication date
CN106921572A (zh) 2017-07-04
CN106921572B (zh) 2019-10-15

Similar Documents

Publication Publication Date Title
WO2017107814A1 (zh) 一种传播QoS策略的方法、装置及系统
USRE49485E1 (en) Overlay management protocol for secure routing based on an overlay network
US10270843B2 (en) Chaining service zones by way of route re-origination
US9954779B2 (en) Method, apparatus, and system for supporting flexible lookup keys in software-defined networks
EP3213480B1 (en) Content filtering for information centric networks
US8949413B2 (en) Filter selection and resuse
EP3402141B1 (en) Virtual private network (vpn) service optimization method and device
WO2016197344A1 (zh) 实现业务链接的方法、设备及系统
US10397066B2 (en) Content filtering for information centric networks
WO2018000443A1 (zh) 基于业务功能链sfc的报文转发方法、装置和系统
KR101473783B1 (ko) 터널링을 이용한 다이나믹 서비스 체이닝 제어 방법 및 장치
WO2015109821A1 (zh) 一种管理业务链的方法、系统及装置
EP2632088B1 (en) Method and device for storing and sending mac address entry
EP3151510A2 (en) Mac (l2) level authentication, security and policy control
CN108429680B (zh) 一种基于虚拟私有云的路由配置方法、系统、介质及设备
CN109714274B (zh) 一种获取对应关系的方法和路由设备
WO2015014187A1 (zh) 一种支持多租户的数据转发方法和装置
CN106789725B (zh) 一种实现流量重定向的方法、装置和系统
WO2017198131A1 (zh) 用于重定向数据流的方法和系统、网络设备和控制设备
CN107786439B (zh) 跨域路由方法、控制器、系统及路由方法和域内路由器
CN114422415A (zh) 在分段路由中的出口节点处理流
JP6592421B2 (ja) ルーティングシステムおよびルーティング方法
CN115118544B (zh) 通信方法及设备、通信系统
CN110958185A (zh) 基于业务的QoS配置方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16877625

Country of ref document: EP

Kind code of ref document: A1