WO2015101066A1

WO2015101066A1 - Method and node for establishing quality of service reservation

Info

Publication number: WO2015101066A1
Application number: PCT/CN2014/086343
Authority: WO
Inventors: 梁旭东
Original assignee: 华为技术有限公司
Priority date: 2013-12-31
Filing date: 2014-09-12
Publication date: 2015-07-09
Also published as: CN104753823B; CN104753823A

Abstract

A method for establishing quality of service (QoS) reservation includes that: a first node obtains a first protocol message, the first protocol message includes a first flow definition domain, a first QoS requirement domain and a first forwarding header information domain, and is used for establishing QoS reservation for a service flow, and the first transfer header information domain is used for indicating the forwarding path of the service flow; the first node determines the flow according to the first flow definition domain; the first node extracts a first QoS requirement information in the first QoS requirement domain; the first node generates a binding relationship between the flow and the first QoS requirement information. In the method, the flow and the QoS requirement information are determined by the protocol message, and further the binding relationship between the flow and the QoS requirement information is generated, so that the QoS reservation can be established for the service flow; the QoS reservation can be established hop by hop for the service flow due to the hop-by-hop forwarding of the protocol message, and thus the QoS of the service flow can be ensured, and the reservation can be adapted to all kinds of networks.

Description

Method and node for establishing service quality reservation

This application claims priority to Chinese Patent Application No. 201310750102.0, filed on December 31, 2013, and entitled "Method and Node for Establishing Service Quality Reservation", the entire contents of which are incorporated herein by reference. In the application.

Technical field

Embodiments of the present invention relate to the field of communications, and, more particularly, to a method and a node for establishing a quality of service reservation.

Background technique

The switching device in the network forwards the packet based on the packet information. When the outbound interface is congested, the switching device will ensure the high-priority service and discard the packets of other services that cannot be guaranteed. In this way, the switching device cannot guarantee the quality of service (QoS) of certain services. The Integrated Service (IS) proposed by the Internet Engineering Task Force (IETF) is an end-to-end flow-based QoS technology that implements QoS guarantees in a resource reservation manner. The Resource Reservation Protocol (RSVP) is the core signaling protocol in the IS.

However, RSVP is designed for the Internet Protocol (IP) network. RSVP packets can only be reserved along the service path on devices in the IP network. Multi-Protocol Label Switching (Multi-Protocol Label Switching) is not available. Resource reservation in the MPLS) network. In this way, the RSVP packet cannot be used to establish resource reservation for the MPLS network hop by hop. In other words, RSVP can only be applied to IP networks, but not to other network types.

Summary of the invention

Embodiments of the present invention provide a method and a node for establishing a quality of service reservation.

The first aspect provides a method for establishing a QoS reservation, where the first node obtains a first protocol packet, where the first protocol packet includes a first flow definition domain, a first quality of service QoS requirement domain, and a first a forwarding header information field, the first protocol packet is used to establish a QoS reservation for the service flow, the first forwarding header information field is used to indicate a service flow forwarding path, and the first node is defined according to the first flow a domain determining flow and a traffic classification rule, where the traffic classification rule is used for performing traffic classification on subsequent service packets to determine that the subsequent service packet belongs to the flow; Extracting the first QoS requirement information in the first QoS requirement domain; the first node generates a binding relationship, where the binding relationship is a binding relationship between the flow and the first QoS requirement information .

With reference to the first aspect, in a first possible implementation, the method further includes: the first node generates a second protocol packet according to the first protocol packet, where the second protocol packet includes a second flow definition a first QoS requirement domain and a second forwarding header information field; the first node sends the second protocol packet to the second node, and the second node is configured according to the first forwarding header The domain performs a lookup of the next hop node determined by the table, and the second protocol packet is used by the second node to establish a QoS reservation for the service flow, where the second flow definition domain is based on the The first flow definition domain is generated based on the first flow definition domain and the first forwarding header information domain, and the second forwarding header information domain is generated based on the first forwarding header information domain.

With reference to the first aspect, or the first possible implementation manner of the first aspect, in a second possible implementation, the method further includes: the first node receiving a third protocol packet, where the third protocol packet includes a second QoS requirement domain; the first node extracts second QoS requirement information in the second QoS requirement domain; when the first node cannot meet the second QoS requirement information, the first node sends The alarm message is used to indicate that the first node fails to establish a QoS reservation.

In conjunction with the first possible implementation of the first aspect, or the second possible implementation of the first aspect, in a third possible implementation, the second flow domain includes at least one of the following: a source network The range of the protocol IP address, the range of the destination IP address, the protocol identifier ID, the range of the port number, the range of the source media access control MAC address, and the range of the destination MAC address, where the second forwarding header information field includes the destination IP address; Or the second forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the second forwarding header information field includes a source IP address, a destination IP address, a source port, a destination port, and a protocol ID; Or the second forwarding header information field includes a destination MAC address; or the second forwarding header information field includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, when the network where the first node is located belongs to a multi-protocol label switching MPLS network, the second flow domain further includes The MPLS label, the second forwarding header information field further includes the MPLS label, where the MPLS label is determined by the first node according to the first forwarding header information field and searching for a label forwarding table.

With reference to the third possible implementation of the first aspect, in a fifth possible implementation, when the first node forwards the second protocol packet by using a universal routing encapsulation GRE tunnel, the second flow The definition field further includes a GRE IP header, and the second forwarding header information field further includes the GRE IP header, where the GRE IP header is determined by the first node according to the first forwarding header information field, and a routing table is searched. of.

With the third possible implementation of the first aspect, in a sixth possible implementation, when the first node forwards the second protocol packet by using a MAC tunnel, the second flow domain is further Including a MAC in MAC header, the second forwarding header information field further includes the MAC in MAC header, where the MAC in MAC header is the first node, according to the first forwarding header information field, searching for a first MAC forwarding Published by the confirmed.

With reference to the third possible implementation manner of the first aspect, in a seventh possible implementation, when the first node forwards the second protocol packet by using a virtual scalable local area network (VXLAN tunnel), the second The flow domain further includes a VXLAN header, the second forwarding header information field further includes the VXLAN header, and the VXLAN header is configured by the first node to search for a second MAC forwarding table according to the first forwarding header information field. definite.

With reference to the first aspect, or any one of the foregoing possible implementation manners, in the eighth possible implementation manner, the first protocol packet further includes a queue ID and a layering level, the queue ID and the layering level And configured to establish a hierarchical queue for the service flow, and further perform scheduling deployment for the hierarchical queue.

With reference to the first aspect, or any one of the foregoing possible implementation manners, in the ninth possible implementation manner, the first protocol packet further includes an information domain, where the information domain includes monitoring information for establishing a QoS reservation.

With reference to the first aspect, or any one of the foregoing possible implementation manners, in a tenth possible implementation manner, the method further includes: when no service uses the binding relationship within a preset time period, the first node Delete the binding relationship.

The second aspect provides a method for establishing a QoS reservation, where the method includes: a first node generates a binding relationship and a protocol packet, where the binding relationship is a binding relationship between the flow and the QoS requirement information, where The protocol packet includes a flow definition domain, a QoS quality requirement domain, and a forwarding header information domain, where the protocol packet is used to establish a QoS reservation for the service flow, and the flow definition domain is used to indicate the flow of the service flow. The QoS requirement field is used to indicate the QoS requirement information, and the forwarding header information field is used to indicate a service flow forwarding path; the first node sends the protocol packet to the first according to the forwarding header information field. A second node, where the second node is a next hop node indicated by the forwarding header information field.

With reference to the second aspect, in a first possible implementation manner, the first node generates a protocol packet, where the first node receives at least one first protocol packet, and the first node is configured according to a convergence policy. And combining the at least one first protocol packet to generate the protocol packet.

With reference to the second aspect, or the first possible implementation manner of the second aspect, in a second possible implementation manner, the flow definition domain includes at least one of the following: a source network protocol IP address range, a destination IP address The range of the protocol identifier ID, the range of the port number, the range of the source media access control MAC address, and the range of the destination MAC address, the forwarding header information field includes the destination IP address; or the forwarding header information field includes the source IP address. Address, destination IP address And the protocol ID; or the forwarding header information field includes a source IP address, a destination IP address, a source port, a destination port, and a protocol ID; or the forwarding header information field includes a destination MAC address; or the forwarding header The information domain includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

With reference to the second possible implementation manner of the second aspect, in a third possible implementation manner, when the network where the first node is located belongs to a multi-protocol label switching MPLS network, the flow definition domain further includes an MPLS label. The forwarding header information field further includes the MPLS label.

With reference to the second possible implementation of the second aspect, in a fourth possible implementation, when the first node forwards the protocol packet by using a universal routing encapsulation GRE tunnel, the flow definition domain further includes The GRE IP header, the forwarding header information field further includes the GRE IP header.

With reference to the second possible implementation of the second aspect, in a fifth possible implementation, when the first node forwards the protocol packet by using a MAC tunnel, the flow definition domain further includes a MAC in MAC Header, the forwarding header information field further includes the MAC in MAC header.

With reference to the second possible implementation of the second aspect, in a sixth possible implementation, when the first node forwards the protocol packet by using a virtual scalable local area network (VXLAN tunnel), the flow definition domain is further Including a VXLAN header, the forwarding header information field further includes the VXLAN header.

With reference to the second aspect, or any one of the foregoing possible implementation manners, in a seventh possible implementation manner, the protocol packet further includes a queue ID and a layering level, where the queue ID and the layering level are used. A hierarchical queue is established for the service flow, and the hierarchical queue is further scheduled for deployment.

With reference to the second aspect, or any one of the foregoing possible implementation manners, in the eighth possible implementation manner, the protocol packet further includes an information domain, where the information domain includes monitoring information for establishing a QoS reservation.

With reference to the second aspect, or any one of the foregoing possible implementation manners, in the ninth possible implementation manner, the method further includes: when no service uses the binding relationship within a preset time period, the first node Delete the binding relationship.

A third aspect provides a node, including: an acquiring unit, configured to acquire a first protocol packet, where the first protocol packet includes a first flow definition domain, a first quality of service QoS requirement domain, and first forwarding header information. The first protocol packet is used to establish a QoS reservation for the service flow, the first forwarding header information field is used to indicate a service flow forwarding path, and the determining unit is configured to obtain, according to the acquiring unit, the first The first flow domain in a protocol packet determines a flow and a traffic classification rule, where the traffic classification rule is used to perform traffic classification on the subsequent service packet to determine that the subsequent service packet belongs to the flow; Extracting the first QoS requirement information in the first QoS requirement domain in the first protocol packet obtained by the acquiring unit; the first generating unit is configured to generate a binding relationship, where the binding The relationship is a binding relationship between the flow determined by the determining unit and the first QoS requirement information extracted by the extracting unit.

With reference to the third aspect, in a first possible implementation, the method further includes: a second generating unit, configured to generate a second protocol packet according to the first protocol packet acquired by the acquiring unit, where the second The protocol packet includes a second flow definition domain, the first QoS requirement domain, and a second forwarding header information domain, and a sending unit, configured to send the second protocol packet to another node, where the other node is Determining, by the second forwarding header, the next hop node determined by the first forwarding header information field, where the second protocol packet is used by the second node to establish a QoS reservation for the service flow, where the The second flow definition domain is generated based on the first flow definition domain or based on the first flow definition domain and the first forwarding header information domain, and the second forwarding header information domain is based on the first forwarding header information. Domain generated.

With the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, the acquiring unit is further configured to receive a third protocol packet, where the third protocol packet includes a second QoS requirement domain; the extracting unit is further configured to extract second QoS requirement information in the second QoS requirement domain in the third protocol packet obtained by the acquiring unit; And when the node cannot meet the second QoS requirement information extracted by the extracting unit, sending an alarm message, where the alarm message is used to indicate that the node fails to establish a QoS reservation.

With reference to the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, in a third possible implementation manner, the second flow domain includes at least one of the following: a source network The range of the protocol IP address, the range of the destination IP address, the protocol identifier ID, the range of the port number, the range of the source media access control MAC address, and the range of the destination MAC address, where the second forwarding header information field includes the destination IP address; Or the second forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the second forwarding header information field includes a source IP address, a destination IP address, a source port, a destination port, and a protocol ID; Or the second forwarding header information field includes a destination MAC address; or the second forwarding header information field includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, when the network where the first node is located belongs to a multi-protocol label switching MPLS network, the second flow domain further includes The MPLS label, the second forwarding header information field further includes the MPLS label, where the MPLS label is determined by the first node according to the first forwarding header information field and searching for a label forwarding table.

With reference to the third possible implementation manner of the third aspect, in a fifth possible implementation, when the first node forwards the second protocol packet by using a universal routing encapsulation GRE tunnel, the second flow The definition domain also includes The GRE IP header, the second forwarding header information field further includes the GRE IP header, where the GRE IP header is determined by the first node according to the first forwarding header information field and searching for a routing table.

With the third possible implementation of the third aspect, in a sixth possible implementation, when the first node forwards the second protocol packet by using a MAC tunnel, the second flow domain is further Including a MAC in MAC header, the second forwarding header information field further includes the MAC in MAC header, where the MAC in MAC header is the first node, according to the first forwarding header information field, searching for a first MAC forwarding Published by the confirmed.

With reference to the third possible implementation manner of the third aspect, in a seventh possible implementation, when the first node forwards the second protocol packet by using a virtual scalable local area network VXLAN tunnel, the second The flow domain further includes a VXLAN header, the second forwarding header information field further includes the VXLAN header, and the VXLAN header is configured by the first node to search for a second MAC forwarding table according to the first forwarding header information field. definite.

With reference to any one of the possible implementation manners of the foregoing third aspect, in the eighth possible implementation, the first protocol packet further includes a queue ID and a layering level, the queue ID and the layering level And configured to establish a hierarchical queue for the service flow, and further perform scheduling deployment for the hierarchical queue.

With reference to the third aspect, or any one of the foregoing possible implementation manners, in the ninth possible implementation manner, the first protocol packet further includes an information domain, where the information domain includes monitoring information for establishing a QoS reservation.

With reference to the third aspect, or any one of the foregoing possible implementation manners, in the tenth possible implementation, the deleting unit is further configured to: when no service is generated by using the first generating unit in a preset time period When the binding relationship is described, the binding relationship is deleted.

In a fourth aspect, a node is provided, including: a generating unit, configured to generate a binding relationship and a protocol packet, where the binding relationship is a binding relationship between the flow and the QoS requirement information, The protocol packet includes a flow definition domain, a QoS quality requirement domain, and a forwarding header information domain, where the protocol packet is used to establish a QoS reservation for the service flow, and the flow definition domain is used to indicate the flow of the service flow. The QoS requirement field is used to indicate the QoS requirement information, the forwarding header information field is used to indicate a service flow forwarding path, and the sending unit is configured to: according to the forwarding header information field, the protocol generated by the generating unit The message is sent to another node, which is the next hop node indicated by the forwarding header information field.

With reference to the fourth aspect, in a first possible implementation, the generating unit includes: a receiving subunit, configured to receive at least one first protocol packet; and a first generating subunit, configured to use, according to a convergence policy, The at least one first protocol packet is merged to generate the protocol packet, and the second generation subunit is configured to generate the binding relationship.

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, in a second possible implementation, the flow definition domain includes at least one of the following: a range of a source network protocol IP address, and a destination IP address. Scope, The protocol identifier ID, the range of the port number, the range of the source media access control MAC address, and the range of the destination MAC address, where the forwarding header information field includes the destination IP address; or the forwarding header information field includes the source IP address and the destination. The IP address and the protocol ID; or the forwarding header information field includes a source IP address, a destination IP address, a source port, a destination port, and a protocol ID; or the forwarding header information field includes a destination MAC address; or, the forwarding The header information field includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

With reference to the second possible implementation manner of the fourth aspect, in a third possible implementation manner, when the network where the first node is located belongs to a multi-protocol label switching MPLS network, the flow definition domain further includes an MPLS label. The forwarding header information field further includes the MPLS label.

With the second possible implementation of the fourth aspect, in a fourth possible implementation, when the first node forwards the protocol packet by using a universal routing encapsulation GRE tunnel, the flow definition domain further includes The GRE IP header, the forwarding header information field further includes the GRE IP header.

With reference to the second possible implementation manner of the fourth aspect, in a fifth possible implementation manner, when the first node forwards the protocol packet by using a MAC tunnel, the flow definition domain further includes a MAC in MAC Header, the forwarding header information field further includes the MAC in MAC header.

With reference to the second possible implementation of the fourth aspect, in a sixth possible implementation, when the first node forwards the protocol packet by using a virtual scalable local area network (VXLAN tunnel), the flow definition domain is further Including a VXLAN header, the forwarding header information field further includes the VXLAN header.

With reference to the fourth aspect, or any one of the foregoing possible implementation manners, in a seventh possible implementation manner, the protocol packet further includes a queue ID and a layering level, where the queue ID and the layering level are used. A hierarchical queue is established for the service flow, and the hierarchical queue is further scheduled for deployment.

With reference to the fourth aspect, or any one of the foregoing possible implementation manners, in the eighth possible implementation manner, the protocol packet further includes an information domain, where the information domain includes monitoring information for establishing a QoS reservation.

With reference to the fourth aspect, or any one of the foregoing possible implementation manners, in a ninth possible implementation, the deleting unit is further configured to: when no service uses the binding relationship within a preset time period, Delete the binding relationship.

The embodiment of the present invention determines the flow and the QoS requirement information by using the protocol packet, and further generates a binding relationship between the flow and the QoS requirement information, and can establish a QoS reservation for the service flow, and the hop-by-hop forwarding of the protocol packet can be a service. The QoS reservation is established hop by hop, thereby ensuring the QoS of the service flow, and the reservation can be adapted to various network types.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only some of the present invention. For the embodiments, other drawings may be obtained from those skilled in the art without any inventive labor.

1 is a flow chart of a method of establishing a quality of service reservation in accordance with an embodiment of the present invention.

2 is a flow chart of a method of establishing a quality of service reservation in accordance with another embodiment of the present invention.

3 is a flow chart of a method of establishing a quality of service reservation in accordance with another embodiment of the present invention.

4 is a block diagram of a node in accordance with one embodiment of the present invention.

Figure 5 is a block diagram of a node in accordance with another embodiment of the present invention.

Figure 6 is a block diagram of a node in accordance with another embodiment of the present invention.

Figure 7 is a block diagram of a node in accordance with another embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly described in conjunction with the drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

RSVP is designed for IP and works only on IP networks. In order to perform resource reservation along the service path, the destination address of the RSVP path (PATH) message needs to be consistent with the destination address of the service flow, and the RSVP packet is sent to the router control plane to complete resource reservation by using each hop. Although this design can meet the granularity defined by IP flow, it cannot reserve resources hop by hop in the MPLS network. Because the routers in the MPLS network are forwarded based on the MPLS label, the scenario of the MPLS virtual private network (VPN) does not have the routing table information of the user. Therefore, the destination address of the RSVP packet cannot be traversed through the network. Resource reservation.

In addition, the flow is defined in RSVP as a combination of an IP address, an agreement identifier (Identity, ID), and a port number. This definition has limitations and RSVP cannot manage and control the flow definition.

Furthermore, RSVP is a fairly complex protocol that defines the soft state of the protocol, which is maintained by a timed refresh. When resource reservation is performed for a large number of service flows, the RSVP control plane needs to maintain a large amount of information, and periodically refresh the reserved resources in the network through the PATH and the reservation (RESerVation, RESV) messages, and the resource reservation for the timeout is also required. The previous resource reservation is cleared by signaling to the end. Such complicated operations consume a large amount of central processing unit (CPU) resources, which in turn makes RSVP specifications very limited. system.

Moreover, the RSVP needs to determine whether the resource reservation is successful. That is to say, the RSVP needs to reserve and confirm the bidirectional RSVP packet transmission, which causes a large overhead and consumes a large amount of CPU resources.

Moreover, resource reservation by RSVP only considers bandwidth resources, and does not consider resources such as Committed Access Rate (CAR).

On the other hand, Resource Reservation Protocol-Traffic Engineering (RSVP-TE) can establish resource reservation for MPLS networks, but RSVP-TE cannot establish resource pre-requisites for other network types except MPLS networks. The process of establishing a resource reservation with RSVP-TE is coupled with the process of establishing a traffic flow forwarding path. In this way, the time sequence of the resource reservation and the deployment of the service flow forwarding path is inflexible, and the requirements for the establishment of the service flow forwarding path are also increased. As a result, different service flows need different forwarding labels. Resource reservation based on the stream.

1 is a flow chart of a method of establishing a quality of service reservation in accordance with an embodiment of the present invention. The method shown in FIG. 1 is performed after the service flow forwarding path is established, and the method includes:

101. The first node obtains a first protocol packet, where the first protocol packet includes a first flow definition domain, a first QoS requirement domain, and a first forwarding header information domain, where the first protocol packet is used to establish a QoS for the service flow. Reserved, the first forwarding header information field is used to indicate a service flow forwarding path.

102. The first node determines, according to the first flow domain, a flow and a traffic classification rule, where the traffic classification rule is used to perform traffic classification on the subsequent service packet to determine that the subsequent service packet belongs to the flow.

103. The first node extracts first QoS requirement information in the first QoS requirement domain.

104. The first node generates a binding relationship, where the binding relationship is a binding relationship between the flow and the first QoS requirement information.

It should be noted that, in the embodiment of the present invention, establishing a QoS reservation not only establishes a resource reservation of a bandwidth resource, but also establishes a reservation of a resource such as a CAR. In the embodiment of the present invention, reservations of resources such as bandwidth resources and CARs are collectively referred to as QoS reservations.

In the embodiment of the present invention, the process of establishing the QoS reservation is performed after the service flow forwarding path is established, so that complete decoupling between the service quality reservation establishment of the service flow and the establishment of the service flow forwarding path is implemented. That is to say, in the process of establishing a service flow forwarding path, there is no process of establishing a service quality resource at the same time. That After the service flow forwarding path is established, normal service flow forwarding can be performed. However, since the service quality reservation is not established, the established service flow forwarding path does not necessarily guarantee the service quality of the service flow.

In the embodiment of the present invention, in order to guarantee the service quality of the service flow, after the service flow forwarding path is established, the QoS reservation is established hop by hop. Each hop of the service flow forwarding path may be referred to as a node.

In the embodiment of the present invention, the node may be a forwarding device, for example, may be a switch, or may be a router, or a device with a switching function, or a device with a routing function. In addition, the node may be a Provider Edge (PE) device in the network, or may be a Provider (P) device, or may be a Customer Edge (CE) device, in the embodiment of the present invention. This is not limited.

In the embodiment of the present invention, the first node in FIG. 1 may be an intermediate node in a service flow forwarding path, or may be a last node of a service flow forwarding path.

Optionally, as an embodiment, the first node may receive the first protocol packet from the third node, where the third node may be a previous hop node of the first node in the service flow forwarding path.

Optionally, in the embodiment of the present invention, the first protocol packet may be generated by the third node according to the service requirement, and the first node obtains the first protocol packet from the third node. The third node may be a host that initiates a service flow service quality application, or may also be a PE device that initiates a service flow service quality application. At this time, it can be understood that the third node is the first node of the service flow forwarding path, and the first node is the next hop node of the third node. That is, the first node is the next hop node of the first node of the service flow forwarding path.

Optionally, as an embodiment, the first protocol packet may be in the form of a Quality of Service Reservation (QoS RESV) message. That is, the first node may receive a QoS RESV message including a first flow definition domain, a first QoS requirement domain, and a first forwarding header information domain. Optionally, the form of the first protocol packet may also be other types of messages, which is not limited by the embodiment of the present invention.

Optionally, the QoS RESV message may further carry an information domain. The information field includes monitoring information when the first protocol packet establishes a QoS reservation. The monitoring information may include one or more of whether the bandwidth reservation is completed, whether there is a queue congestion packet loss, a path information for establishing a QoS reservation, and a service flow packet statistics. And optionally, the QoS RESV message may further include a plurality of optional domains, where the multiple optional domains are available for the indication information related to the first protocol packet. The invention is not limited thereto.

In this way, the number of mandatory domains in the QoS RESV message can be made smaller, which facilitates the processing of the QoS RESV message. For example, the QoS RESV message can be processed at the hardware level, such as processing the QoS RESV message directly at the forwarding plane without being sent to the control plane. Moreover, the transmission frequency of the QoS RESV message can be reduced, and processed by the control entity at the control plane, thereby saving resources.

Optionally, as another embodiment, in the embodiment of the present invention, the information domain may be carried in a quality of service information (QoS INFO) message. The first node may acquire the QoS INFO message while acquiring the QoS RESV message, or the QoS INFO message may be different from the period of the QoS RESV message. The information field may include monitoring information for establishing a QoS reservation for the first protocol message. The monitoring information may include one or more of whether the bandwidth reservation is completed, whether there is a queue congestion packet loss, a path information for establishing a QoS reservation, and a service flow packet statistics.

That is to say, the first protocol message exists in the form of a QoS RESV message, which may be any of the following situations:

(1) The QoS RESV message may include only the first flow definition domain, the first QoS requirement domain, and the first forwarding header information domain, where the first flow definition domain, the first QoS requirement domain, and the first forwarding header information domain may be referred to as 3 Required fields; or,

(2) The QoS RESV message may include a first flow definition domain, a first QoS requirement domain, a first forwarding header information domain, and an information domain, where the information domain is an optional domain; or

(3) The QoS RESV message and the QoS INFO message are simultaneously used to establish a QoS reservation. The QoS RESV message includes a first flow definition domain, a first QoS requirement domain, and a first forwarding header information domain, and the QoS INFO message includes an information domain. The invention is not limited thereto.

In the embodiment of the present invention, the first flow definition domain may include the first partial first flow definition domain, where the first partial first flow definition domain may include at least one of the following: a range of the source IP address, a range of the destination IP address, a protocol ID, and a port number. The range, the range of source MAC addresses, and the range of destination MAC addresses. And, the first part of the first flow definition domain may be generated by the first node of the service flow forwarding path. The first node may be a host that initiates a service flow service quality application, or may be a PE device that initiates a service flow service quality application.

Specifically, the range of addresses may be the prefix of the address. For example, the range of the source IP address may be the prefix of the source IP address, the range of the destination IP address may be the prefix of the destination IP address, the range of the source MAC address may be the prefix of the source MAC address, and the range of the destination MAC address may be the destination MAC address. The prefix of the address.

Optionally, the first flow definition domain may further include a second partial first flow definition domain, where the second partial first flow definition domain may include one or more of the following: an MPLS label, a GRE IP header, a MAC in MAC header, and a virtual The Virtual Extensible Local Area Network (VXLAN) header is not limited in this embodiment of the present invention. For example, if the first node receives the first protocol packet from the third node, and the third node is in the MPLS network, the second part of the first flow definition domain may include an MPLS label generated by the third node. It should be noted that the MPLS label can be single layer or multiple layers. For example, if the first node receives the first protocol packet from the third node, and the third node forwards the first protocol packet through the GRE tunnel, the second part of the first flow definition domain may include a GRE IP header. For example, if the first node receives the first protocol packet from the third node, and the third node passes The MAC tunnel forwards the first protocol packet, and the second part of the first stream definition domain may include a MAC in MAC header. For example, if the first node receives the first protocol packet from the third node, and the third node forwards the first protocol packet through the VXLAN tunnel, the second part of the first flow definition domain may include a VXLAN header.

It can be understood that the second part of the first stream definition domain is dynamically added or modified by the node in the process of establishing the QoS reservation. In this way, the embodiment of the present invention expands the scope of the stream definition, improves the classification ability of the stream definition, and can support more fields of the stream classification. And, you can manage and control the flow definition.

In the embodiment of the present invention, the first QoS requirement field includes the first QoS requirement information, which is used to indicate the QoS requirement of the service flow, and the first QoS requirement information may be carried in a certain format in the first protocol packet. For example, the first QoS requirement information may include a QoS queue, and the QoS queue may be one or more of the following parameters: a queue scheduling manner, a queue priority, and a bandwidth of the queue. The first QoS requirement information may also include other QoS parameters, such as CAR, coloring, and setting, which are not limited by the present invention.

The first QoS requirement domain may be determined by the first node according to the QoS requirement information of the service flow, or may be pre-configured in the first node, which is not limited by the present invention. The first node may be a host that initiates a service flow service quality application, or may also be a PE device that initiates a service flow service quality application.

In the embodiment of the present invention, the first forwarding header information field includes a first part of the first forwarding header information field. The first part of the first forwarding header information field may include a destination IP address; or the first part of the first forwarding header information field may include a source IP address, a destination IP address, and a protocol ID; or, the first part of the first forwarding header information field may be The source IP address, the destination IP address, the source port, the destination port, and the protocol ID are included; or the first part of the first forwarding header information field may include the destination MAC address; or the first part of the first forwarding header information field may include the source IP address, Destination IP address, source MAC address, and destination MAC address. And, the first part of the first forwarding header information field may be generated by the first node. The first node may be a host that initiates a service flow service quality application, or may also be a PE device that initiates a service flow service quality application. The source IP address can be the source IP address of the service flow, the destination IP address can be the destination IP address of the service flow, the source MAC address can be the source MAC address of the service flow, and the destination MAC address can be the destination MAC address of the service flow.

It can be understood that the first part of the first forwarding header information field belongs to the category of the first part of the first stream defining domain. Specifically, the source IP address in the first part of the first forwarding header information field is one of the ranges belonging to the source IP address in the first part of the first stream definition domain. The destination IP address in the first part of the first forwarding header information field is one of the ranges belonging to the destination IP address in the first part of the first stream definition domain. The source MAC address in the first part of the first forwarding header information field is one of the ranges belonging to the source MAC address in the first part of the first stream definition domain. The destination MAC address of the first part of the first forwarding header information field belongs to the destination MAC address of the first part of the first stream definition domain. One of the ranges.

Optionally, the first forwarding header information field may further include a second part of the first forwarding header information field. The second part of the first forwarding header information field may include one or more of the following: an MPLS label, a GRE IP header, a MAC in MAC header, and a VXLAN header, which are not limited in this embodiment of the present invention. For example, if the first node receives the first protocol packet from the third node, and the third node is in the MPLS network, the second part of the first forwarding header information field may include an MPLS label generated by the third node. It should be noted that the MPLS label can be single layer or multiple layers. For example, if the first node receives the first protocol packet from the third node, and the third node forwards the first protocol packet through the GRE tunnel, the second part of the first forwarding header information field may include a GRE IP header. For example, if the first node receives the first protocol packet from the third node, and the third node forwards the first protocol packet through the MAC tunnel, the second part of the first forwarding header information field may include a MAC in MAC header. . For example, if the first node receives the first protocol packet from the third node, and the third node forwards the first protocol packet through the VXLAN tunnel, the second portion of the first forwarding header information field may include a VXLAN header.

It can be understood that the second part of the first forwarding header information field is dynamically added or modified by the node in the process of establishing the QoS reservation. In this way, the first protocol packet defined in the embodiment of the present invention can be applied to various network types, such as an IP network, an MPLS network, or a hybrid network of IP and MPLS, or can also be applied to a cross-domain network.

Thus, in the embodiment of the present invention, the first forwarding header information field is used to guide the first protocol packet to be forwarded along the service flow forwarding path. The first forwarding header information field includes the service flow forwarding path information that is consistent with the forwarding path of the service flow, and can ensure that the first protocol packet is forwarded along the service flow forwarding path, so that each node of the service flow forwarding path can be The first protocol packet establishes a QoS reservation for the service flow. Moreover, each node may update the second part of the first forwarding header information field, and forward the updated protocol message to the next hop node in the service flow forwarding path.

In the embodiment of the present invention, the flow in step 102 is defined according to the first flow definition domain. And the flow classification rule can be used to perform traffic classification on the subsequent service packets to determine that the subsequent service packets belong to the flow. The same stream has the same QoS processing.

Specifically, the flow classification rule is generated by the first node according to the first flow definition domain. After the QoS reservation is established for the service flow in the embodiment of the present invention, when the subsequent service packet passes the first node, the first node may perform traffic classification on the subsequent service packet according to the traffic classification rule, and determine the subsequent service report. Whether the text belongs to the stream. When the first node can determine that the subsequent service message belongs to the flow, the same QoS processing procedure corresponding to the flow can be performed.

In the embodiment of the present invention, the first node may determine the flow according to the first part of the first flow definition domain, and may also determine the flow together with the second partial first flow definition domain and the first partial first flow definition domain, which is not limited by the present invention.

Optionally, the first node may define a range of IP addresses and/or a range of MAC addresses according to the first flow. Determine the flow. Optionally, the first node may also determine the flow together with the range of the IP address in the first flow definition domain, together with the MPLS label, and the like. This embodiment of the present invention does not limit this.

Specifically, in different VPNs of the same network, there may be the same IP address, and the flow cannot be uniquely determined only according to the range of the IP address. Therefore, it is necessary to combine other information with the range of IP addresses to determine the flow. The other information mentioned herein may be an MPLS label, or may be a GRE IP header, or may be a MAC in MAC header, or may be a VXLAN header, or the like, or may be other identifiers for distinguishing different network types. This is not limited.

Optionally, in the embodiment of the present invention, the first QoS requirement information extracted in step 103 may be a QoS queue.

In the embodiment of the present invention, the binding relationship is established in step 104, and the first node is considered to establish a QoS reservation for the service flow. Optionally, the binding relationship may be a binding relationship between the flow and the QoS queue.

Optionally, as an embodiment, when the first node is an intermediate node of the service flow forwarding path, after the binding relationship is established, the first node generates a second protocol packet according to the first protocol packet, where the second protocol is generated. The message includes a second flow definition domain, a first QoS requirement domain, and a second forwarding header information domain. Further, the first node sends the second protocol packet to the second node according to the second forwarding header information field, where the second node is the next hop node determined according to the first forwarding header information field. The second flow definition domain is generated based on the first flow definition domain or based on the first flow definition domain and the first forwarding header information domain. The second forwarding header information field is generated based on the first forwarding header information field. The second protocol packet is used by the second node to establish a QoS reservation for the service flow according to the second protocol packet.

Specifically, the second flow definition domain may include a first partial second flow definition domain and a second partial second flow definition domain. And the first part of the second stream defining domain is the same as the first part of the first stream defining domain, and the second part of the second stream defining domain is different from the second part of the first stream defining domain.

It can be understood that, if the first stream definition domain does not include the second part of the first stream domain, the second stream domain may be generated after the first node adds the second part of the second stream domain to the first stream domain. . If the first flow definition domain includes the second partial first flow definition domain, the second flow definition domain may be that the first node replaces the second partial first flow domain in the first flow definition domain with the second partial second flow domain Generated.

Here, the second partial second flow definition domain may include at least one of the following: an MPLS label, a GRE IP header, a MAC in MAC header, and a VXLAN header.

For example, when the first node is in the MPLS network, the second part of the second flow definition domain may include an MPLS label, and the MPLS label is determined by the first node according to the first forwarding header information field lookup label forwarding table. It should be noted that the MPLS label can be single layer or multiple layers. For example, when the first node forwards the first protocol packet through the GRE tunnel, then the second part of the second flow definition domain may include a GRE IP header, where the GRE IP header is the first node according to the first forwarding The header information field is determined by the routing table. When the first node forwards the first protocol packet through the MAC tunnel, the second part of the second flow definition domain may include a MAC in MAC header, where the MAC in MAC header is the first node searches according to the first forwarding header information field. Determined by the first MAC forwarding table. For example, when the first node forwards the first protocol packet through the VXLAN tunnel, the second portion of the second flow definition domain may include a VXLAN header, where the VXLAN header is the first node searches for the second according to the first forwarding header information field. Determined by the MAC forwarding table.

Optionally, the second forwarding header information field includes a destination IP address; or the second forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the second forwarding header information field includes a source IP address, a destination IP address, a source port, a destination port, and a protocol ID; or the second forwarding header information field includes a destination MAC address; or the second forwarding header information field includes a source IP address and a destination IP address. Source MAC address and destination MAC address.

Specifically, the second forwarding header information field includes a first partial second forwarding header information field and a second partial second forwarding header information domain, and the first partial second forwarding header information domain is the same as the first partial first forwarding header information domain, The two-part second forwarding header information field is different from the second partial first forwarding header information field.

It can be understood that, if the first forwarding header information field does not include the second part of the first forwarding header information field, the second forwarding header information field may be that the first node adds the second part to the second forwarding header information field. Generated after forwarding the header information field. If the first forwarding header information field includes the second partial first forwarding header information field, the second forwarding header information field may be that the first node replaces the second partial first forwarding header information field in the first forwarding header information field with The second part is generated after the second forwarding header information field. The second part of the second forwarding header information field is used to indicate the next hop information of the first node.

Here, the second partial second forwarding header information field may include at least one of the following: an MPLS label, a GRE IP header, a MAC in MAC header, and a VXLAN header.

For example, when the first node is in the MPLS network, the second part of the second forwarding header information field may include an MPLS label, and the MPLS label is determined by the first node according to the first forwarding header information field lookup label forwarding table. It should be noted that the MPLS label can be single layer or multiple layers. For example, when the first node forwards the first protocol packet through the GRE tunnel, the second part of the second forwarding header information field may include a GRE IP header, where the GRE IP header is the first node according to the first forwarding header information field. Look up the routing table to determine. When the first node forwards the first protocol packet through the MAC tunnel, the second part of the second forwarding header information field may include a MAC in MAC header, where the MAC in MAC header is the first node according to the first forwarding header information field. Find the first MAC forwarding table to determine. For example, when the first node forwards the first protocol packet through the VXLAN tunnel, the second portion of the second forwarding header information field may include a VXLAN header, where the VXLAN header is the first node searches according to the first forwarding header information field. Two MAC forwarding tables are determined.

It should be noted that, in the embodiment of the present invention, if the network where each hop node of the service flow forwarding path is located is an IP network, or the network where each hop node of the service flow forwarding path is located is a MAC network, the first definition is The domain includes only the first part of the first stream definition domain, and the first forwarding header information field includes only the first part of the first forwarding header information field. And, the second stream definition domain is the same as the first stream definition domain.

Optionally, as an embodiment, the method shown in FIG. 1 may further include: the first node receives a third protocol packet, where the third protocol packet is used to establish a QoS reservation for the second service flow, where the third The protocol message includes a second QoS requirement field. The first node extracts second QoS requirement information in the second QoS requirement domain. When the first node cannot meet the second QoS requirement information, the first node sends an alarm message, where the alarm message is used to indicate that the first node fails to establish a QoS reservation for the second service flow. Then, the first node generates a fourth protocol packet according to the third protocol packet, and sends the fourth protocol packet to the next hop node of the first node, so that the next hop node is configured according to the fourth protocol. The message establishes a QoS reservation.

Specifically, the first node may send an alarm message to the network management, and further complete the QoS reservation at the first node by performing a human intervention by the network management. Or the network management further reduces the bandwidth of the QoS of the second service flow, etc., to establish a QoS reservation at the first node. Alternatively, other operations may be performed by the network management system, which is not limited by the present invention.

Optionally, as another embodiment, after the binding relationship is established in step 104, when no binding service is used by the service within the preset time period, the first node deletes the binding relationship. For example, a timer can be set at the first node, and the value of the timer can be pre-configured. When no service flow passes through the first node in the time period set by the timer, or no related protocol packet passes through the first node, the first node may delete the binding relationship, that is, the first node. Release the established QoS reservation.

In this way, if there is no longer a QoS requirement for the service flow, or for other service flows reconstructed by the forwarding path, as long as the service flow is stopped or the protocol packet is stopped, the corresponding QoS reservation can be used after a preset time period. freed. After that, QoS reservations can be established for other service flows, which can guarantee the resource utilization of the nodes.

Optionally, as an embodiment, in the embodiment of the present invention, the first protocol packet may further include a queue ID, and the first node may allocate a layering level to the service flow according to the queue ID and the first QoS requirement information. The queue ID and the hierarchization level can then be used to establish a hierarchical queue for the traffic flow and further deploy the deployment for the hierarchical queue.

Optionally, in another embodiment, in the embodiment of the present invention, the first protocol packet may further include a queue ID and a layering level corresponding to the queue ID. The queue ID and the layering level can be used to establish a hierarchical queue for the service flow and further deploy the deployment for the hierarchical queue. This hierarchical level can be used as an optional domain for QoS RESV messages.

Specifically, if the first QoS requirement domain includes a queue, the first node may establish a hierarchical relationship between the parent queue of the queue and the higher-level ancestor queue while generating the binding relationship between the flow and the queue in step 104. After receiving the multiple protocol packets, the first node may top-down the protocol packets with the same queue ID as the hierarchical level of the first protocol packet in the multiple protocol packets. , programmed into the hierarchical queue established above. In this way, the service packet is first scheduled in the lowest-level queue, then scheduled in the parent queue, and then scheduled from the bottom up, and finally to the top-level queue for scheduling, and the multiple scheduling is completed to achieve hierarchical bandwidth allocation. The bandwidth and priority of the parent queue may be carried in the protocol packet, may be the superposition of the sub-queue bandwidth, or may be configured through the node.

In this way, the hierarchical relationship of the queue is organized by the establishment process of the QoS reservation, that is, the combination of QoS scheduling and hierarchical scheduling is realized.

In the embodiment of the present invention, the scheduling deployment of the hierarchical queue is a method for deploying QoS in the network. For example, the network first allocates resources for different user groups, so that the user groups reach a certain resource ratio relationship; secondly, allocate resources or schedule relationships for different users within a user group, which can be scheduled according to priority, or It can be scheduled according to proportions, so that users within the user group can obtain resource ratios; finally, resources are allocated for different service flows of one user, and the resource ratio between different service flows is achieved. This way of resource allocation is hierarchical and is achieved through a hierarchical relationship of queues.

In the embodiment of the present invention, the QoS reservation is established on each node of the service flow forwarding path by forwarding the protocol packet hop by hop, and an end to end (E2E) QoS reservation can be established. And in the process of establishing the reservation, there is no need to make a reservation confirmation by using an additional message, so that on the one hand, the soft state is simplified, and on the other hand, the QoS reservation of a larger E2E can be supported.

2 is a flow chart of a method of establishing a quality of service reservation in accordance with another embodiment of the present invention. The method shown in FIG. 2 is performed after the service flow forwarding path is established, and the method includes:

201. The first node generates a binding relationship and a protocol packet, where the binding relationship is a binding relationship between the flow and the QoS requirement information, where the protocol packet includes a flow definition domain, a QoS requirement domain, and a forwarding header information domain. The protocol packet is used to establish a QoS reservation for the service flow, where the flow definition field is used to indicate the flow of the service flow, the QoS requirement domain is used to indicate the QoS requirement information, and the forwarding header information field is used to indicate the service flow forwarding path. .

202. The first node sends the protocol packet to the second node according to the forwarding header information field, where the second node is the next hop node indicated by the forwarding header information field.

Optionally, in the embodiment of the present invention, the first node may be a first node of the service flow forwarding path. The first node may be a host that initiates a service flow service quality application, or may be a PE device that initiates a service flow service quality application.

Optionally, in the embodiment of the present invention, in step 201, the first node generates a binding relationship, and the first node is considered to establish a QoS reservation for the service flow. The binding relationship is a binding relationship between the flow and the QoS requirement information. The flow and the QoS requirement information may be pre-configured according to the service requirements of the service flow. This embodiment of the present invention does not limit this.

Specifically, in step 201, the first node may generate a protocol packet according to the service requirement. The protocol packet includes a flow domain, a QoS requirement domain, and a forwarding header information domain.

The flow definition domain may include a first partial flow definition domain. The first partial flow definition domain includes at least one of the following: a range of a source IP address, a range of a destination IP address, a protocol ID, a range of a port number, a range of a source MAC address, and a range of a destination MAC address. Specifically, the range of addresses may be the prefix of the address. For example, the range of the source IP address may be the prefix of the source IP address, the range of the destination IP address may be the prefix of the destination IP address, the range of the source MAC address may be the prefix of the source MAC address, and the range of the destination MAC address may be the destination MAC address. The prefix of the address.

Optionally, the flow definition domain may further include a second partial flow definition domain. The second partial flow definition domain may be one or more of the following: an MPLS label, a GRE IP header, a MAC in MAC header, and a VXLAN header.

For example, when the first node is in the MPLS network, the second partial flow definition domain may include an MPLS label. It should be noted that the MPLS label can be single layer or multiple layers. For example, when the first node forwards the protocol packet through the GRE tunnel, then the second partial flow definition domain may include a GRE IP header. When the first node forwards the protocol packet through the MAC tunnel, then the second partial flow definition domain may include a MAC in MAC header. For example, when the first node forwards the protocol message through the VXLAN tunnel, then the second partial flow definition domain may include a VXLAN header.

It should be noted that the second partial flow definition domain may also be other identifiers for distinguishing different network types, which is not limited by the embodiment of the present invention.

Optionally, the QoS requirement field includes QoS requirement information, which is used to indicate a QoS requirement of the service flow, and the QoS requirement information may be carried in a certain format in the protocol packet. For example, the QoS requirement information may include a QoS queue, and the QoS queue may be one or more of the following parameters: a queue scheduling manner, a queue priority, and a bandwidth of the queue. Optionally, the QoS requirement information may also include other QoS parameters, such as CAR, coloring, and setting, which are not limited by the present invention.

Optionally, the forwarding header information field includes a destination IP address; or the forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the forwarding header information field includes a source IP address and a destination IP address. Address, source port, destination port, and protocol ID; or, the forwarding header information field includes a destination MAC address; or, the The originating information field includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

Optionally, the forwarding header information field may include a first partial forwarding header information field. The first part of the forwarding header information field may include a destination IP address; or the first part of the forwarding header information field may include a source IP address, a destination IP address, and a protocol ID; or the first partial forwarding header information field may include a source IP address, The destination IP address, the source port, the destination port, and the protocol ID; or the first part of the forwarding header information field may include the destination MAC address; or the first part of the forwarding header information field may include the source IP address, the destination IP address, the source MAC address, and the destination. MAC address. The source IP address can be the source IP address of the service flow, the destination IP address can be the destination IP address of the service flow, the source MAC address can be the source MAC address of the service flow, and the destination MAC address can be the destination MAC address of the service flow.

Optionally, the forwarding header information field further includes a second part forwarding header information field. The second partial forwarding header information field includes one or more of the following: an MPLS label, a GRE IP header, a MAC in MAC header, and a VXLAN header.

For example, when the first node is in the MPLS network, the second partial forwarding header information field may include an MPLS label. It should be noted that the MPLS label can be single layer or multiple layers. For example, when the first node forwards the protocol packet through the GRE tunnel, then the second partial forwarding header information field may include a GRE IP header. When the first node forwards the protocol packet through the MAC tunnel, then the second partial forwarding header information field may include a MAC in MAC header. For example, when the first node forwards the protocol message through the VXLAN tunnel, then the second partial forwarding header information field may include a VXLAN header.

It should be noted that the second part of the forwarding header information field may also be other identifiers for distinguishing different network types, which is not limited by the present invention.

Optionally, as an embodiment, the protocol message may be in the form of a QoS RESV message. Optionally, the protocol packet may also be other types of messages, which is not limited by the disclosure.

The QoS RESV message may also carry an information domain. The information field includes monitoring information when the protocol packet establishes a QoS reservation. The monitoring information may include one or more of whether the bandwidth reservation is completed, whether there is a queue congestion packet loss, a path information for establishing a QoS reservation, and a service flow packet statistics. This information field is an optional field for this QoS RESV message. And optionally, the QoS RESV message may further include a plurality of optional domains, where the multiple optional domains are available for the indication information related to the first protocol packet. The invention is not limited thereto.

Optionally, in another embodiment, in the embodiment of the present invention, the information domain may be carried in a QoS INFO message, and the first node may generate the QoS INFO message while generating the QoS RESV message. The information field can include The protocol packet is used to establish monitoring information for QoS reservation. The monitoring information may include one or more of whether the bandwidth reservation is completed, whether there is a queue congestion packet loss, a path information for establishing a QoS reservation, and a service flow packet statistics.

That is, the protocol message may be in any of the following cases in the form of a QoS RESV message:

(1) The QoS RESV message may include only the flow definition domain, the QoS requirement domain, and the forwarding header information domain, and may be referred to as three mandatory domains; or

(2) The QoS RESV message may include a flow definition domain, a QoS requirement domain, a forwarding header information domain, and an information domain, where the information domain is an optional domain; or

(3) The QoS RESV message and the QoS INFO message are simultaneously used to establish a QoS reservation. The QoS RESV message includes a flow definition domain, a QoS requirement domain, and a forwarding header information domain, and the QoS INFO message includes an information domain. The invention is not limited thereto.

Optionally, as another embodiment, the protocol packet may further include a queue ID and a layering level corresponding to the queue ID, where the queue ID and the layering level are used to establish a hierarchical queue for the service flow, and further The hierarchical queue is scheduled for deployment. Also, this level of hierarchy can also be used as an optional domain for QoS RESV messages.

Optionally, in the embodiment of the present invention, the first node may be an intermediate node in the service flow forwarding path.

Specifically, before the step 201, the method further includes: the first node receiving the at least one first protocol packet, where each of the at least one first protocol packet includes the first flow definition domain, the first QoS The demand domain and the first forwarding header information domain.

Here, at least one first protocol message may be received by the first node from different directions, and different directions may refer to different nodes. The at least one first protocol message may be belonging to a different user.

Correspondingly, in step 201, the first node generates a protocol packet, and the first node combines the at least one first protocol packet according to the convergence policy to generate a protocol packet. An aggregation policy is a policy for combining multiple protocol packets into one protocol packet.

The convergence policy includes a first convergence policy and a second convergence policy. The first convergence policy can be used to determine that at least one first protocol packet can be aggregated. The second convergence policy can be used to aggregate at least one first protocol packet into the protocol packet. Here, the second aggregation policy may include a flow definition aggregation policy, a QoS requirement aggregation policy, and a forwarding header information aggregation policy.

First, the first node determines, according to the first convergence policy, that the at least one first protocol packet can be aggregated.

For example, the first aggregation policy may be that the first forwarding header information field of each first protocol packet of the at least one first protocol packet is the same.

Optionally, each first protocol packet of the at least one first protocol packet further includes an aggregation ID field. at this time, The first aggregation policy may be that the convergence ID field of each first protocol packet of the at least one first protocol packet is the same. Optionally, the first aggregation policy may be that the convergence ID field of each first protocol packet of the at least one first protocol packet is the same.

It should be noted that the convergence ID field of each first protocol message of the at least one first protocol message may be determined when each of the first protocol messages is generated. For example, it may be determined according to a traffic flow forwarding path or according to QoS requirements. Optionally, the aggregation ID field of each first protocol packet of the at least one first protocol packet may be pre-configured by the user when generating each of the first protocol packets. The invention is not limited thereto.

Optionally, when the form of the at least one first protocol message is a QoS RESV message, the aggregation ID field may be one of the optional domains of the QoS RESV message.

Then, the first node merges the at least one first protocol packet into a protocol packet according to the second convergence policy. Specifically, the flow definition convergence policy is configured to enable the first node to merge each first flow definition domain of each first protocol packet in the at least one first protocol packet into a flow definition domain. The QoS requirement aggregation policy is configured to enable the first node to merge each of the first QoS requirement domains of each of the at least one first protocol packet into a QoS requirement domain. The forwarding header information aggregation policy is configured to enable the first node to merge each of the first forwarding header information fields of each of the at least one first protocol packet into a forwarding header information domain.

Specifically, the flow definition aggregation policy may be a union of each first flow definition domain of each first protocol packet in the at least one first protocol packet as a flow definition domain.

For example, when each of the first flow definition fields of each of the at least one first protocol message is the same, the flow definition field may be each of the at least one first protocol message. Each first stream definition field of the message.

For example, when each of the first flow definition domains has a part of each other, the flow definition domain may define a union of the domains for each of the first flows.

Optionally, the flow definition aggregation policy may be to generate the flow definition domain in other manners.

For example, assume that at least one first protocol message is three first protocol messages. The flow definition convergence policy may be that the first flow definition fields of the two first protocol packets of the three first protocol packets are intersected, and then the third first protocol of the three first protocol packets is obtained. The first flow definition field of the packet is taken as a union, and then the flow definition domain is generated.

Specifically, the QoS requirement aggregation policy may be: adding the bandwidth in each first QoS requirement domain of each of the at least one first protocol packet as the bandwidth information included in the QoS requirement domain. Optionally, it is also possible to multiply the pre-set convergence ratio after the bandwidth is added as the bandwidth information included in the QoS requirement domain. And taking the other demand information except the bandwidth in each of the first QoS demand domains as the QoS requirement Demand information in the domain other than bandwidth.

Optionally, the QoS requirement aggregation policy may be: setting a convergence ratio for a part of the first protocol packet in the at least one first protocol packet, where each part of the first protocol packet is in the first QoS requirement domain The bandwidth is multiplied by the convergence ratio, and is added to the bandwidth of each of the first QoS request domains in the first protocol packet except the first protocol packet in the at least one first protocol packet. Bandwidth information contained in the QoS requirement domain. And the other required information except the bandwidth in each of the first QoS requirement domains is intersected as the other demand information except the bandwidth in the QoS demand domain.

Specifically, each of the at least one first protocol packet may include a convergence ID field. When the value in the convergence ID field of one of the first protocol packets satisfies the preset matching algorithm, the convergence ratio operation is performed on the first protocol packet. For example, the convergence code can be pre-configured, and the value in the convergence ID field is compared with the convergence code. When the result of the AND operation is zero, it is determined that the first protocol message can perform the convergence ratio operation.

It should be noted that the first node may determine and execute the convergence ratio operation together in the process of determining whether aggregation can be performed according to the first aggregation policy, so that statistical multiplexing can be embodied.

Optionally, the QoS requirement aggregation policy may be: weighting and summing bandwidths in each of the first QoS requirement domains of each of the at least one first protocol packet, as included in the QoS requirement domain. Bandwidth information; the other pieces of demand information other than the bandwidth in each of the first QoS demand domains are intersected as other demand information except the bandwidth in the QoS demand domain.

Generally, the multiple service flows corresponding to the at least one first protocol packet are not concurrently concurrent, that is, the probability that all the service flows corresponding to the at least one first protocol packet reach the first node at the same time is relatively small. Set a certain weight, and also guarantee the QoS of each service flow. Even when one or more of the at least one first protocol packet arrives at the first node at the same time, the first node does not reach the maximum bandwidth at the same time because the multiple service flows corresponding to the at least one first protocol packet The QoS of the one or several first protocol messages can still be guaranteed.

For example, it is assumed that at least one first protocol packet is two first protocol packets, and the bandwidth requirements of the two first protocol packets are 10M and 20M, respectively. Then, the bandwidth requirement of the QoS requirement domain of the generated protocol packet may be 30M, that is, 10M and 20M are summed.

Optionally, the bandwidth requirement of the QoS requirement domain of the generated protocol packet may also be γ×(10+20)M, where γ is a convergence ratio, and 0≤γ≤1.

Optionally, if the value in the aggregation ID field of the first protocol packet with the bandwidth requirement of 10 M meets the preset matching algorithm, the bandwidth requirement of the QoS requirement domain of the generated protocol packet may also be (λ×10+). 20) M, where λ is a convergence ratio, and 0 ≤ λ ≤ 1.

Optionally, the bandwidth requirement of the QoS requirement domain of the generated protocol packet may also be (α×10+β×20)M, where α and β are weights, and 0≤α≤1 and 0≤β≤1 . α and β are pre-configured.

Specifically, the forwarding header information aggregation policy may be: after each first forwarding header information field of each first protocol packet in the at least one first protocol packet is reserved or replaced or partially replaced, and then generated and forwarded. Header information field.

For example, when each of the first forwarding header information fields of each of the at least one first protocol packet is the same, the forwarding header information field may be each of the at least one first protocol packet. Each of the first forwarding header information fields of the first protocol message.

For example, if each of the first forwarding header information fields of each of the at least one first protocol packet is different from each other, each of the at least one first protocol packet is the first protocol packet. The destination IP address of each of the first forwarding header information fields belongs to the same enterprise network. Then, the forwarding header information field may be generated by partially replacing each of the first forwarding header information fields of each of the at least one first protocol packet. In this manner, the aggregated protocol packet can be forwarded to the PE device of the enterprise network, and then the PE device of the enterprise network can split the aggregated protocol packet and forward it to other devices in the enterprise network.

In this way, the first node aggregates multiple protocol packets into one protocol packet, and only needs to establish a QoS reservation for a protocol packet after the aggregation, so as to guarantee the QoS of multiple protocol packets. The resource occupation on the first node can be saved.

For example, if the at least one first protocol packet belongs to a different user, the protocol message after the aggregation belongs to a user group, that is, the aggregation improves the granularity of the stream.

It should be noted that, in the embodiment of the present invention, the convergence policy may be pre-configured. Optionally, the aggregation policy may be recompiled in the aggregation process, which is not limited by the disclosure.

In this way, in step 201, the first node generates a protocol packet according to the convergence policy, and the protocol packet includes a flow definition domain, a QoS requirement domain, and a forwarding header information domain.

For example, when the first node is in the MPLS network, the second partial flow definition domain may include an MPLS label. For example, when the first node forwards the protocol packet through the GRE tunnel, then the second partial flow definition domain may include a GRE IP header. When the first node forwards the protocol packet through the MAC tunnel, then the second partial flow definition domain may include a MAC in MAC header. For example, when the first node forwards the protocol message through the VXLAN tunnel, then the second partial flow definition domain may include a VXLAN header.

The QoS requirement field includes QoS requirement information, which is used to indicate the QoS requirement of the service flow, and the QoS requirement information may be carried in a certain format in the protocol packet. For example, the QoS requirement information may include a QoS queue, and the QoS queue may be one or more of the following parameters: a queue scheduling manner, a queue priority, and a bandwidth of the queue. The QoS requirement information may also include other QoS parameters, such as CAR, coloring, and setting, which are not limited by the present invention.

The forwarding header information field may include a first part forwarding header information field. The first part of the forwarding header information field may include a destination IP address; or the first part of the forwarding header information field may include a source IP address, a destination IP address, and a protocol ID; or the first partial forwarding header information field may include a source IP address, The destination IP address, the source port, the destination port, and the protocol ID; or the first part of the forwarding header information field may include the destination MAC address; or the first part of the forwarding header information field may include the source IP address, the destination IP address, the source MAC address, and the destination. MAC address. The source IP address can be the source IP address of the service flow, the destination IP address can be the destination IP address of the service flow, the source MAC address can be the source MAC address of the service flow, and the destination MAC address can be the destination MAC address of the service flow.

For example, when the first node is in the MPLS network, the second partial forwarding header information field may include an MPLS label. For example, when the first node forwards the protocol packet through the GRE tunnel, then the second partial forwarding header information field may include a GRE IP header. When the first node forwards the protocol packet through the MAC tunnel, then the second partial forwarding header information field may include a MAC in MAC header. For example, when the first node forwards the protocol message through the VXLAN tunnel, then the second partial forwarding header information field may include a VXLAN header.

Optionally, as another embodiment, the protocol packet may further include a queue ID and a layering level, where the queue ID and the layering level are used to establish a hierarchical queue for the service flow, and further perform the hierarchical queue Schedule deployment.

Optionally, as an embodiment, the protocol message may be in the form of a QoS RESV message. At this time, the flow definition domain, the QoS requirement domain, and the forwarding header information domain are three mandatory domains of the QoS RESV message. Optionally, the protocol packet may also be other types of messages, which is not limited by the disclosure.

The QoS RESV message may also carry an information domain. At this point, the information field is an optional field for the QoS RESV message. The information field includes monitoring information when the protocol packet establishes a QoS reservation. The monitoring information may include one or more of whether the bandwidth reservation is completed, whether there is a queue congestion packet loss, a path information for establishing a QoS reservation, and a service flow packet statistics. And optionally, the QoS RESV message may further include a plurality of optional domains, where the multiple optional domains are available for the indication information related to the first protocol packet. This embodiment of the present invention does not limit this.

Optionally, in another embodiment, in the embodiment of the present invention, the information domain may be carried in a QoS INFO message, and the first node may generate the QoS INFO message while generating the QoS RESV message. The information field may include monitoring information for establishing a QoS reservation for the protocol message. The monitoring information may include one or more of whether the bandwidth reservation is completed, whether there is a queue congestion packet loss, a path information for establishing a QoS reservation, and a service flow packet statistics.

That is to say, the protocol message exists in the form of a QoS RESV message, which may be any of the following situations:

(2) The QoS RESV message may include a flow definition domain, a QoS requirement domain, a forwarding header information domain, and an information domain; or

(3) The QoS RESV message and the QoS INFO message are simultaneously used to establish a QoS reservation. The QoS RESV message includes a flow definition domain, a QoS requirement domain, and a forwarding header information domain, and the QoS INFO message includes an information domain. This embodiment of the present invention does not limit this.

Thus, in step 201, the first node generates a binding relationship, that is, establishes a QoS reservation for the service flow.

Further, in step 202, the first node sends the protocol packet generated in step 201 to the second node, so that the second node can establish a QoS reservation for the service flow according to the protocol packet.

Optionally, as another embodiment, after the binding relationship is established in step 201, when no binding service is used by the service within the preset time period, the first node deletes the binding relationship. For example, a timer can be set at the first node, and the value of the timer can be pre-configured. When no service flow passes through the first node in the time period set by the timer, or no related protocol packet passes through the first node, the first node may delete the binding relationship, that is, the first node. Release the established QoS reservation.

In this way, if there are no more QoS requirements for the traffic flow, or other traffic flows reconstructed for the forwarding path, If the service flow is stopped or the protocol packet is stopped, the corresponding QoS reservation can be released after a preset period of time. After that, QoS reservations can be established for other service flows, which can guarantee the resource utilization of the nodes.

3 is a flow chart of a method of establishing a quality of service reservation in accordance with another embodiment of the present invention. The method shown in Figure 3 includes:

306. The node 301 generates a binding relationship and a first protocol packet. The binding relationship is a binding relationship between the flow and the first QoS requirement information. The first protocol packet includes a first flow definition domain, a first QoS requirement domain, and a first forwarding header information domain. The first protocol packet is used to establish a QoS reservation for the service flow, where the first flow definition domain is used to indicate the flow of the service flow, and the first QoS requirement domain is used to indicate the first QoS requirement information, the first forwarding The header information field is used to indicate the service forwarding path.

Specifically, the node 301 may be a host that initiates a service flow service quality application, or may also be a PE device that initiates a service flow service quality application. Moreover, the forwarding path of the service flow has been established before step 305, and the service flow forwarding path reaches the node 304 via the node 302 and the node 303 in sequence.

The node 301 generates a binding relationship, that is, establishes a QoS reservation for the service flow.

The purpose of the first protocol packet generated by the node 301 is to establish a QoS reservation hop by hop for the service flow. Assuming that the network in which the node 301 is located is an IP network, it is assumed that the network in which the node 302, the node 303, and the node 304 are located is an MPLS network.

For example, the first flow definition domain includes a range of a source IP address, a range of a destination IP address, a protocol ID, a range of a port number, a range of a source MAC address, and a range of a destination MAC address; the first QoS requirement domain includes a queue; the first forwarding The header information field includes a source IP address, a destination IP address, a source MAC address, a destination MAC address, and a protocol ID.

307. The node 301 sends the first protocol packet to the node 302.

Specifically, the node 301 sends the first protocol packet to the node 302 according to the first forwarding header information field.

308. The node 302 determines, according to the first flow domain, a flow and a traffic classification rule, where the traffic classification rule is used to perform traffic classification on the subsequent service packets to determine that the subsequent service packets belong to the flow.

Step 308 is similar to step 102 in FIG. 1. To avoid repetition, details are not described herein again.

309. The node 302 extracts first QoS requirement information in the first QoS requirement domain.

Specifically, the first QoS requirement information may be a queue.

310. Node 302 generates a binding relationship. The binding relationship is a binding relationship between the flow and the first QoS requirement information.

Specifically, the binding relationship may be a binding relationship between the flow and the queue. Thus, node 302 establishes a QoS reservation for the traffic flow.

311. The node 302 generates a second protocol packet according to the first protocol packet. The second protocol packet includes a second flow definition domain, a first QoS requirement domain, and a second forwarding header information domain.

Optionally, the second flow definition domain includes a range of the source IP address, a range of the destination IP address, a protocol ID, a range of the port number, a range of the source MAC address, a range of the destination MAC address, and the first MPLS label. It can be understood that the second flow definition domain includes a first partial second flow definition domain and a second partial second flow definition domain, wherein the first partial second flow definition domain includes a range of a source IP address, a range of a destination IP address, a protocol ID, The range of the port number, the range of the source MAC address, and the range of the destination MAC address. The second part of the second stream definition field includes the first MPLS label. It can also be understood that the second flow definition domain is generated after adding the first MPLS label on the basis of the first flow definition domain.

Optionally, the second forwarding header information field includes a source IP address, a destination IP address, a source MAC address, a destination MAC address, a protocol ID, and a first MPLS label. It can be understood that the second forwarding header information field includes a first part of the second forwarding header information field and a second part of the second forwarding header information field, where the first part of the second forwarding header information field includes a source IP address, a destination IP address, and a source MAC address. The destination MAC address and the protocol ID, and the second part of the second forwarding header information field includes the first MPLS label. It can also be understood that the second forwarding header information field is generated after the first MPLS label is added on the basis of the first forwarding header information field.

The first MPLS label may be determined by the node 302 according to the first forwarding header information field and searching for the first label forwarding table stored on the node 302.

312. The node 302 sends the second protocol message to the node 303.

Specifically, the node 302 sends the second protocol packet to the node 303 according to the second forwarding header information field.

313. The node 303 determines, according to the second flow domain, a flow and a traffic classification rule, where the traffic classification rule is used to perform traffic classification on the subsequent service packet to determine that the subsequent service packet belongs to the flow.

Specifically, the node 303 may combine the first partial second flow definition domain and the second partial second flow definition domain to determine the flow together.

Step 313 is similar to step 102 in FIG. 1. To avoid repetition, details are not described herein again.

314. The node 303 extracts first QoS requirement information in the first QoS requirement domain.

Specifically, the first QoS requirement information may be a queue.

315. The node 303 fails to generate a binding relationship.

Specifically, the node 303 does not successfully generate a binding relationship between the flow and the first QoS requirement information. The reason for the failure may be that the node 303 cannot meet the bandwidth requirement in the first QoS requirement information, and may be other reasons. The present invention does not limit this.

316. The node 303 sends an alarm message, where the alarm message is used to indicate that the node 303 fails to establish a QoS reservation.

Specifically, the alarm message can be sent to the network management.

Optionally, the network management may perform human intervention after receiving the alarm message, and establish a binding on the node 303. Relationship to complete the QoS reservation establishment at node 303.

317. The node 303 generates a third protocol packet. The third protocol packet includes a third flow definition domain, a first QoS requirement domain, and a third forwarding header information domain.

Optionally, the third flow definition domain includes a range of the source IP address, a range of the destination IP address, a protocol ID, a range of the port number, a range of the source MAC address, a range of the destination MAC address, and a second MPLS label. It can be understood that the third stream definition domain includes a first part third stream definition domain and a second part third stream definition domain, wherein the first part third stream definition domain includes a range of source IP addresses, a range of destination IP addresses, a protocol ID, The range of the port number, the range of the source MAC address, and the range of the destination MAC address. The second part of the third stream definition field includes the second MPLS label. It can also be understood that the third stream definition domain is generated after the first MPLS label is replaced with the second MPLS label on the basis of the second stream definition domain.

Optionally, the third forwarding header information field includes a destination IP address; or the third forwarding header information domain includes a source IP address, a destination IP address, and a protocol ID; or the third forwarding header information field includes a source IP address, a destination IP address, a source port, a destination port, and a protocol ID; or the third forwarding header information field includes a destination MAC address; or the third forwarding header information field includes a source IP address and a destination IP address. Source MAC address and destination MAC address.

Optionally, the third forwarding header information field includes a source IP address, a destination IP address, a source MAC address, a destination MAC address, a protocol ID, and a second MPLS label. It can be understood that the third forwarding header information field includes a first partial third forwarding header information field and a second partial third forwarding header information domain, wherein the first partial third forwarding header information domain includes a source IP address, a destination IP address, and a source MAC address. The destination MAC address and the protocol ID, and the second part of the third forwarding header information field includes the second MPLS label. It can also be understood that the third forwarding header information field is generated after the first MPLS label is replaced with the second MPLS label based on the second forwarding header information field.

The second MPLS label may be determined by the node 303 searching for the second label forwarding table stored on the node 303 according to the second forwarding header information field.

318. The node 303 sends the third protocol message to the node 304.

Specifically, the node 303 sends the third protocol packet to the node 304 according to the third forwarding header information field.

319. The node 304 determines, according to the third flow domain, a flow and a traffic classification rule, where the traffic classification rule is used to perform traffic classification on the subsequent service packets to determine that the subsequent service packets belong to the flow.

Step 319 is similar to step 313. To avoid repetition, details are not described herein again.

320. The node 304 extracts first QoS requirement information in the first QoS requirement domain.

Specifically, the first QoS requirement information may be a queue.

The node 304 generates a binding relationship. The binding relationship is a binding relationship between the flow and the first QoS requirement information.

Specifically, the binding relationship may be a binding relationship between the flow and the queue. Thus, node 304 establishes a QoS reservation for the traffic flow.

In the embodiment of the present invention, after the binding relationship is established on each node of the node 301 to the node 304, the QoS reservation of the E2E of the node 301 to the node 304 is completed.

It should be noted that FIG. 3 is only one embodiment of the present invention. The present invention does not limit the number of nodes and the type of network in which the nodes are located. Other embodiments that are extended by those skilled in the art based on the embodiments of the present invention still fall within the scope of the present invention.

4 is a block diagram of a node in accordance with one embodiment of the present invention. The node 400 shown in FIG. 4 includes an acquisition unit 401, a determination unit 402, an extraction unit 403, and a first generation unit 404.

The obtaining unit 401 is configured to obtain a first protocol packet, where the first protocol packet includes a first flow definition domain, a first QoS requirement domain, and a first forwarding header information domain. The first protocol packet is used to establish a QoS reservation for the service flow, and the first forwarding header information field is used to indicate the service forwarding path. The determining unit 402 is configured to determine a flow and a traffic classification rule according to the first flow definition field in the first protocol packet obtained by the obtaining unit 401, where the traffic classification rule is used to perform traffic classification on the subsequent service packet to determine that the subsequent service packet belongs to The stream. The extracting unit 403 is configured to extract first QoS requirement information in the first QoS requirement domain in the first protocol packet obtained by the obtaining unit 401. The first generating unit 404 is configured to generate a binding relationship, where the binding relationship is a binding relationship between the flow determined by the determining unit 402 and the first QoS requirement information extracted by the extracting unit 403.

Optionally, as an embodiment, the node 400 shown in FIG. 4 may further include a second generating unit 405 and a sending unit 406.

The second generating unit 405 is configured to generate a second protocol packet according to the first protocol packet that is obtained by the obtaining unit 401, where the second protocol packet includes a second flow definition domain, a first QoS requirement domain, and a second forwarding header information domain. . The sending unit 406 is configured to send the second protocol packet to another node, where the other node is a next hop node determined by performing a table lookup according to the first forwarding header information field, where the second protocol packet is used by The other node establishes a QoS reservation for the traffic flow. The second flow definition domain is generated based on the first flow definition domain or based on the first flow definition domain and the first forwarding header information domain. The second forwarding header information field is generated based on the first forwarding header information field.

Optionally, in another embodiment, the obtaining unit 401 is further configured to receive a third protocol packet, where the third protocol packet includes a second QoS requirement domain. The extracting unit 403 is further configured to extract second QoS requirement information in the second QoS requirement domain in the third protocol packet obtained by the obtaining unit 401. The sending unit 406 is further configured to: when the node 400 fails to meet the second QoS requirement information extracted by the extracting unit 403, send an alert message, where the alert message is used to indicate that the node 400 fails to establish a QoS reservation.

Optionally, as an embodiment, the first flow definition field in the first protocol packet acquired by the obtaining unit 401 may include at least one of the following: a range of the source IP address, a range of the destination IP address, a protocol ID, and a port number. The range, the range of source MAC addresses, and the range of destination MAC addresses. The second forwarding header information field may include a destination IP address; or the second forwarding header information field may include a source IP address, a destination IP address, and a protocol ID; or the second forwarding header information field may include a source IP address and a destination IP address. The source port, the destination port, and the protocol ID; or the second forwarding header information field may include the destination MAC address; or the second forwarding header information field may include a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

Optionally, as another embodiment, when the network where the node 400 is located belongs to the MPLS network, the second flow definition domain further includes an MPLS label, and the second forwarding header information field further includes the MPLS label, where the MPLS label is the node 400 according to the node 400. The first forwarding header information field is determined by the label forwarding table.

Optionally, as another embodiment, when the node 400 forwards the second protocol packet through the GRE tunnel, the second flow definition domain further includes a GRE IP header, and the second forwarding header information domain further includes the GRE IP header, the GRE The IP header is determined by the node 400 according to the first forwarding header information field, and the routing table is determined.

Optionally, in another embodiment, when the node 400 forwards the second protocol packet by using the MAC tunnel, the second flow definition domain further includes a MAC in MAC header, and the second forwarding header information domain further includes the MAC in MAC header. The MAC in MAC header is determined by the node 400 according to the first forwarding header information field to look up the first MAC forwarding table.

Optionally, as another embodiment, when the node 400 forwards the second protocol packet through the VXLAN tunnel, the second flow definition domain further includes a VXLAN header, and the second forwarding header information domain further includes the VXLAN header, where the VXLAN header is The node 400 searches for the second MAC forwarding table according to the first forwarding header information field.

Optionally, in another embodiment, the first protocol packet acquired by the obtaining unit 401 may further include a queue ID and a layering level, where the queue ID and the layering level are used to establish a hierarchical queue for the service flow, and Further scheduling and deploying the hierarchical queue.

Optionally, as another embodiment, the first protocol packet acquired by the obtaining unit 401 may further include an information domain. The information field includes monitoring information for establishing a QoS reservation.

Optionally, as another embodiment, the node 400 may further include a deleting unit, configured to delete the binding relationship when no service uses the binding relationship generated by the first generating unit 404 within a preset time period.

Figure 5 is a block diagram of a node in accordance with another embodiment of the present invention. The node 500 shown in FIG. 5 includes a generating unit 501 and a transmitting unit 502.

The generating unit 501 is configured to generate a binding relationship and a protocol packet, where the binding relationship is a binding relationship between the flow and the QoS requirement information. The protocol message includes a flow definition domain, a quality of service QoS requirement domain, and a forwarding header information domain. The protocol message is used to establish a QoS reservation for the service flow, where the flow definition field is used to indicate the flow of the service flow, the QoS requirement domain is used to indicate the QoS requirement information, and the forwarding header information field is used to indicate the service flow. Send path. The sending unit 502 is configured to send, according to the forwarding header information field, the protocol packet generated by the first generating unit 501 to another node, where the other node is a next hop node indicated by the forwarding header information field.

Optionally, as an embodiment, the generating unit 501 may include: a receiving subunit 503, a first generating subunit 504, and a second generating subunit 505. The receiving subunit 503 can be configured to receive at least one first protocol message. The first generating sub-unit 504 is configured to combine the at least one first protocol packet received by the receiving sub-unit 503 to generate a protocol packet according to the convergence policy. The second generation subunit 505 is configured to generate the binding relationship.

Optionally, as another embodiment, the flow definition field in the protocol packet generated by the generating unit 501 may include at least one of the following: a range of the source IP address, a range of the destination IP address, a protocol ID, and a range of the port number. The range of the source MAC address and the range of the destination MAC address. The forwarding header information field may include a destination IP address; or the forwarding header information field may include a source IP address, a destination IP address, and a protocol ID; or the forwarding header information field may include a source IP address, a destination IP address, a source port, and a destination port. And the protocol ID; or, the forwarding header information field may include a destination MAC address; or, the forwarding header information field may include a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

Optionally, as another embodiment, when the network where the node 500 is located belongs to the MPLS network, the flow definition domain further includes an MPLS label, and the forwarding header information field further includes the MPLS label.

Optionally, as another embodiment, when the node 500 forwards the protocol packet through the GRE tunnel, the flow definition domain further includes a GRE IP header, and the forwarding header information domain further includes the GRE IP header.

Optionally, as another embodiment, when the node 500 forwards the protocol packet through the MAC tunnel, the flow definition domain further includes a MAC in MAC header, and the forwarding header information domain further includes the MAC in MAC header.

Optionally, as another embodiment, when the node 500 forwards the protocol packet through the VXLAN tunnel, the flow definition domain further includes a VXLAN header, and the forwarding header information domain further includes the VXLAN header.

Optionally, as another embodiment, the protocol packet generated by the generating unit 501 may further include a queue ID and a layering level, where the layer ID and the layering level are used to establish a hierarchical queue for the service flow, and further Schedule deployment for this hierarchical queue.

Optionally, as another embodiment, the protocol packet generated by the generating unit 501 may further include an information domain, where the information domain includes monitoring information for establishing a QoS reservation.

Optionally, as another embodiment, the node 500 may further include a deleting unit, configured to delete the binding relationship when there is no binding relationship generated by the service using generating unit 501 within a preset time period.

Figure 6 is a block diagram of a node in accordance with another embodiment of the present invention. The node 600 shown in FIG. 6 includes a processor 601, a memory 602, a receiving circuit 603, and a transmitting circuit 604.

The receiving circuit 603 is configured to obtain a first protocol packet, where the first protocol packet includes a first flow definition domain, a first QoS requirement domain, and a first forwarding header information domain. The first protocol packet is used to establish a QoS reservation for the service flow, and the first forwarding header information field is used to indicate the service flow forwarding path. The processor 601 is configured to determine a flow and a traffic classification rule according to the first flow definition field in the first protocol packet that is received by the receiving circuit 603, where the traffic classification rule is used to perform traffic classification on the subsequent service packet to determine that the subsequent service packet belongs to Extracting the first QoS requirement information in the first QoS requirement domain in the first protocol packet obtained by the receiving circuit 603; and generating a binding relationship, where the binding relationship is between the flow and the first QoS requirement information Binding relationship.

The various components in node 600 are coupled together by a bus system 605, which in addition to the data bus includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 605 in FIG.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 601 or implemented by the processor 601. Processor 601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 601 or an instruction in a form of software. The processor 601 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programmable logic device, discrete gate or transistor logic Pieces, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read only memory or an electrically erasable programmable memory, a register, etc. In the storage medium. The storage medium is located in the memory 602, and the processor 601 reads the information in the memory 602 and completes the steps of the above method in combination with its hardware.

Optionally, as an embodiment, the processor 601 is further configured to generate a second protocol packet according to the first protocol packet that is obtained by the receiving circuit 603, where the second protocol packet includes a second flow definition domain and a first QoS requirement. Domain and second forwarding header information field. The sending circuit 604 can be configured to send the second protocol packet to another node, where the other node is a next hop node determined by performing a lookup table according to the first forwarding header information field, where the second protocol packet is used by The other node establishes a QoS reservation for the traffic flow. The second flow definition domain is generated based on the first flow definition domain or based on the first flow definition domain and the first forwarding header information domain. The second forwarding header information field is generated based on the first forwarding header information field.

Optionally, as another embodiment, the receiving circuit 603 is further configured to receive a third protocol packet, where the third protocol packet includes a second QoS requirement field. The processor 601 is further configured to extract second QoS requirement information in the second QoS requirement domain in the third protocol packet obtained by the receiving circuit 603. When the node 600 is unable to meet the second QoS requirement information, the sending circuit 604 is further configured to send an alarm message, where the alarm message is used to indicate that the node 600 fails to establish a QoS reservation.

Optionally, as an embodiment, the first flow definition field in the first protocol packet acquired by the receiving circuit 603 may include at least one of the following: a range of the source IP address, a range of the destination IP address, a protocol ID, and a port number. The range, the range of source MAC addresses, and the range of destination MAC addresses. The second forwarding header information field may include a destination IP address; or the second forwarding header information field may include a source IP address, a destination IP address, and a protocol ID; or the second forwarding header information field may include a source IP address and a destination IP address. The source port, the destination port, and the protocol ID; or the second forwarding header information field may include the destination MAC address; or the second forwarding header information field may include a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

Optionally, as another embodiment, when the network where the node 600 is located belongs to the MPLS network, the second flow definition domain further includes an MPLS label, and the second forwarding header information field further includes the MPLS label, where the MPLS label is the node 600 according to the node 600. The first forwarding header information field is determined by the label forwarding table.

Optionally, as another embodiment, when the node 600 forwards the second protocol packet through the GRE tunnel, the second flow definition domain further includes a GRE IP header, and the second forwarding header information domain further includes the GRE IP header, the GRE IP header is a node 600 is determined by searching the routing table according to the first forwarding header information field.

Optionally, in another embodiment, when the node 600 forwards the second protocol packet by using the MAC tunnel, the second flow definition domain further includes a MAC in MAC header, and the second forwarding header information domain further includes the MAC in MAC header. The MAC in MAC header is determined by the node 600 according to the first forwarding header information field to find the first MAC forwarding table.

Optionally, in another embodiment, when the node 600 forwards the second protocol packet through the VXLAN tunnel, the second flow definition domain further includes a VXLAN header, and the second forwarding header information domain further includes the VXLAN header, where the VXLAN header is The node 600 searches for the second MAC forwarding table according to the first forwarding header information field.

Optionally, in another embodiment, the first protocol packet acquired by the receiving circuit 603 may further include a queue ID and a layering level, where the queue ID and the layering level are used to establish a hierarchical queue for the service flow, and Further scheduling and deploying the hierarchical queue.

Optionally, as another embodiment, the first protocol packet acquired by the receiving circuit 603 may further include an information domain, where the information domain includes monitoring information for establishing a QoS reservation.

Optionally, as another embodiment, the node 600 may further include a deleting unit, configured to: when no service uses the binding relationship within a preset time period, the processor 601 is further configured to delete the binding relationship.

The node 600 can implement the various processes implemented by the first node in the embodiment of FIG. 1. To avoid repetition, details are not described herein again.

Figure 7 is a block diagram of a node in accordance with another embodiment of the present invention. The node 700 shown in FIG. 7 includes a processor 701, a memory 702, a receiving circuit 703, and a transmitting circuit 704.

The processor 701 is configured to generate a binding relationship and a protocol packet, where the binding relationship is a binding relationship between the flow and the QoS requirement information. The protocol message includes a flow definition domain, a quality of service QoS requirement domain, and a forwarding header information domain. The protocol message is used to establish a QoS reservation for the service flow, where the flow definition field is used to indicate the flow of the service flow, the QoS requirement domain is used to indicate the QoS requirement information, and the forwarding header information field is used to indicate the service flow. Send path. The sending circuit 704 is configured to send, according to the forwarding header information field, the protocol packet generated by the processor 701 to another node, where the other node is the next hop node indicated by the forwarding header information field.

The various components in node 700 are coupled together by a bus system 705, which in addition to the data bus includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 705 in FIG.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 701 or implemented by the processor 701. Processor 701 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 701 or an instruction in a form of software. The processor 701 described above may be a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software modules can be located in RAM, flash memory, ROM, programmable read only memory, or electrically erasable programmable memory, registers, and the like, which are well established in the art. The storage medium is located in the memory 702, and the processor 701 reads the information in the memory 702 and completes the steps of the above method in combination with its hardware.

Optionally, as an embodiment, the receiving circuit 703 is configured to receive at least one first protocol message. The processor 701 is configured to combine the at least one first protocol packet received by the receiving subunit 504 to generate a protocol packet according to the convergence policy.

Optionally, as another embodiment, the flow definition field in the protocol packet generated by the processor 701 may include at least one of the following: a range of the source IP address, a range of the destination IP address, a protocol ID, and a range of the port number. The range of the source MAC address and the range of the destination MAC address. The forwarding header information field may include a destination IP address; or the forwarding header information field may include a source IP address, a destination IP address, and a protocol ID; or the forwarding header information field may include a source IP address, a destination IP address, a source port, and a destination port. And the protocol ID; or, the forwarding header information field may include a destination MAC address; or, the forwarding header information field may include a source IP address, a destination IP address, a source MAC address, and a destination MAC address.

Optionally, as another embodiment, when the network where the node 700 is located belongs to the MPLS network, the flow definition domain further includes an MPLS label, and the forwarding header information field further includes the MPLS label.

Optionally, as another embodiment, when the node 700 forwards the protocol packet through the GRE tunnel, the flow definition domain further includes a GRE IP header, and the forwarding header information domain further includes the GRE IP header.

Optionally, as another embodiment, when the node 700 forwards the protocol packet through the MAC tunnel, the flow definition domain further includes a MAC in MAC header, and the forwarding header information domain further includes the MAC in MAC header.

Optionally, as another embodiment, when the node 700 forwards the protocol packet through the VXLAN tunnel, the flow definition domain further includes a VXLAN header, and the forwarding header information domain further includes the VXLAN header.

Optionally, as another embodiment, the protocol packet generated by the processor 701 may further include a queue ID and a layering level, where the layer ID and the layering level are used to establish a hierarchical queue for the service flow, and further For this level The queue is scheduled for deployment.

Optionally, as another embodiment, the protocol packet generated by the processor 701 may further include an information domain, where the information domain includes monitoring information for establishing a QoS reservation.

Optionally, as another embodiment, the processor 701 is further configured to delete the binding relationship when no service uses the binding relationship generated by the processor 701 within a preset time period.

The node 700 can implement the processes implemented by the first node in the embodiment of FIG. 2. To avoid repetition, details are not described herein again.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including Several instructions to make a computer device (can It is a personal computer, server, or network device, etc.) that performs all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

A method for establishing a quality of service reservation, characterized in that it comprises:

The first node obtains a first protocol packet, where the first protocol packet includes a first flow definition domain, a first quality of service QoS requirement domain, and a first forwarding header information domain, where the first protocol packet is used as a service flow. Establishing a QoS reservation, where the first forwarding header information field is used to indicate a service flow forwarding path;

Determining, by the first node, the flow and the traffic classification rule according to the first flow definition domain, where the traffic classification rule is used to perform traffic classification on the subsequent service packet to determine that the subsequent service packet belongs to the flow;

The first node extracts first QoS requirement information in the first QoS requirement domain;

The first node generates a binding relationship, where the binding relationship is a binding relationship between the flow and the first QoS requirement information.
The method of claim 1 further comprising:

The first node generates a second protocol packet according to the first protocol packet, where the second protocol packet includes a second flow definition domain, the first QoS requirement domain, and a second forwarding header information domain.

Sending, by the first node, the second protocol packet to the second node, where the second node is a next hop node determined by performing a table lookup according to the first forwarding header information field, the second protocol The message is used by the second node to establish a QoS reservation for the service flow,

The second flow definition domain is generated based on the first flow definition domain or based on the first flow definition domain and the first forwarding header information domain, and the second forwarding header information domain is based on the The first forwarding header information field is generated.
The method according to claim 1 or 2, further comprising:

The first node receives a third protocol packet, where the third protocol packet includes a second QoS requirement field;

The first node extracts second QoS requirement information in the second QoS requirement domain;

When the first node cannot meet the second QoS requirement information, the first node sends an alarm message, where the alarm message is used to indicate that the first node fails to establish a QoS reservation.
The method according to any one of claims 2 to 3, wherein the second flow definition domain comprises at least one of the following: a range of a source network protocol IP address, a range of a destination IP address, a protocol identification ID, and a port. The range of the number, the range of the source media access control MAC address, and the range of the destination MAC address,

The second forwarding header information field includes a destination IP address; or the second forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the second forwarding header information field includes a source IP address, Destination IP address, a source port, a destination port, and a protocol ID; or the second forwarding header information field includes a destination MAC address; or the second forwarding header information field includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address. .
The method according to claim 4, wherein when the network in which the first node is located belongs to a multi-protocol label switching MPLS network, the second flow definition domain further includes an MPLS label, and the second forwarding header information The domain further includes the MPLS label, where the MPLS label is determined by the first node according to the first forwarding header information field and searching for a label forwarding table.
The method according to claim 4, wherein when the first node forwards the second protocol packet by using a universal routing encapsulation GRE tunnel, the second flow defining domain further includes a GRE IP header, where The second forwarding header information field further includes the GRE IP header, where the GRE IP header is determined by the first node according to the first forwarding header information field and searching for a routing table.
The method according to claim 4, wherein when the first node forwards the second protocol packet through a MAC tunnel, the second flow definition domain further includes a MAC in MAC header, and the second The forwarding header information field further includes the MAC in MAC header, where the MAC in MAC header is determined by the first node searching for the first MAC forwarding table according to the first forwarding header information field.
The method according to claim 4, wherein when the first node forwards the second protocol packet through a virtual scalable local area network (VXLAN tunnel), the second flow definition domain further includes a VXLAN header, The second forwarding header information field further includes the VXLAN header, where the VXLAN header is determined by the first node searching for the second MAC forwarding table according to the first forwarding header information field.
The method according to any one of claims 1 to 8, wherein the first protocol message further comprises a queue ID and a layering level, and the queue ID and the layering level are used for the service The flow establishes a hierarchical queue and further performs scheduling deployment for the hierarchical queue.
The method according to any one of claims 1 to 9, wherein the first protocol message further comprises an information domain, and the information domain comprises monitoring information for establishing a QoS reservation.
The method according to any one of claims 1 to 10, further comprising:

When no service uses the binding relationship within a preset time period, the first node deletes the binding relationship.
A method for establishing a quality of service reservation, characterized in that it comprises:

The first node generates a binding relationship and a protocol packet, where the binding relationship is a binding relationship between the flow and the QoS requirement information, where the protocol packet includes a flow definition domain, a quality of service QoS requirement domain, and a forwarding header information domain. The agreement And the QoS requirement domain is used to indicate the QoS requirement information, and the forwarding header information field is used to indicate a service. Stream forwarding path;

The first node sends the protocol packet to the second node according to the forwarding header information field, where the second node is a next hop node indicated by the forwarding header information field.
The method according to claim 12, wherein the first node generates a protocol message, including:

The first node receives at least one first protocol packet;

The first node combines the at least one first protocol packet to generate the protocol packet according to the convergence policy.
The method according to claim 12 or 13, wherein the flow definition domain comprises at least one of the following: a range of source network protocol IP addresses, a range of destination IP addresses, a protocol identification ID, a range of port numbers, and a source. Media access control MAC address range and destination MAC address range,

The forwarding header information field includes a destination IP address; or the forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the forwarding header information field includes a source IP address, a destination IP address, and a source port. And the destination port and the protocol ID; or the forwarding header information field includes a destination MAC address; or the forwarding header information field includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address.
The method according to claim 14, wherein when the network in which the first node is located belongs to a multi-protocol label switching MPLS network, the flow definition domain further includes an MPLS label, and the forwarding header information field further includes a Said MPLS label.
The method according to claim 14, wherein when the first node forwards the protocol packet by using a universal routing encapsulation GRE tunnel, the flow definition domain further includes a GRE IP header, and the forwarding header information domain Also included is the GRE IP header.
The method according to claim 14, wherein when the first node forwards the protocol packet through a MAC tunnel, the flow definition domain further includes a MAC in MAC header, and the forwarding header information domain further includes The MAC in MAC header.
The method according to claim 14, wherein when the first node forwards the protocol packet through a virtual scalable local area network VXLAN tunnel, the flow definition domain further includes a VXLAN header, and the forwarding header information domain Also included is the VXLAN header.
The method according to any one of claims 12 to 18, wherein the protocol message further comprises a queue ID and a layering level, wherein the queue ID and the layering level are used to establish the service flow. Hierarchical queues and further scheduling deployment for the hierarchical queues.
The method according to any one of claims 12 to 19, wherein the protocol message further comprises an information domain, and the information domain comprises monitoring information for establishing a QoS reservation.
The method according to any one of claims 12 to 20, further comprising:

When no service uses the binding relationship within a preset time period, the first node deletes the binding relationship.
A node, wherein the node comprises:

An acquiring unit, configured to obtain a first protocol packet, where the first protocol packet includes a first flow definition domain, a first quality of service QoS requirement domain, and a first forwarding header information domain, where the first protocol packet is used as The service flow establishes a QoS reservation, and the first forwarding header information field is used to indicate a service flow forwarding path;

a determining unit, configured to determine a flow and a traffic classification rule according to the first flow definition domain in the first protocol packet obtained by the acquiring unit, where the traffic classification rule is used to perform traffic classification on a subsequent service packet to determine The subsequent service message belongs to the flow;

An extracting unit, configured to extract first QoS requirement information in the first QoS requirement domain in the first protocol packet obtained by the acquiring unit;

a first generating unit, configured to generate a binding relationship, where the binding relationship is a binding relationship between the flow determined by the determining unit and the first QoS requirement information extracted by the extracting unit.
The node according to claim 22, further comprising:

a second generating unit, configured to generate a second protocol packet according to the first protocol packet obtained by the acquiring unit, where the second protocol packet includes a second flow definition domain, the first QoS requirement domain, and Second forwarding header information field;

a sending unit, configured to send the second protocol packet to another node, where the other node is a next hop node determined by performing a table lookup according to the first forwarding header information field, the second protocol The message is used by the another node to establish a QoS reservation for the service flow,

The second flow definition domain is generated based on the first flow definition domain or based on the first flow definition domain and the first forwarding header information domain, and the second forwarding header information domain is based on the The first forwarding header information field is generated.
A node according to claim 22 or 23, characterized in that

The acquiring unit is further configured to receive a third protocol packet, where the third protocol packet includes a second QoS requirement field;

The extracting unit is further configured to extract second QoS requirement information in the second QoS requirement domain in the third protocol packet obtained by the acquiring unit;

The sending unit is further configured to: when the node fails to meet the second QoS requirement information extracted by the extracting unit, send an alarm message, where the alarm message is used to indicate that the node fails to establish a QoS reservation.
The node according to any one of claims 23 to 24, wherein the second flow definition domain comprises at least one of the following: a range of a source network protocol IP address, a range of a destination IP address, a protocol identification ID, and a port. The range of the number, the range of the source media access control MAC address, and the range of the destination MAC address,

The second forwarding header information field includes: a destination IP address; or the second forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the second forwarding header information field includes a source IP address. The destination IP address, the source port, the destination port, and the protocol ID; or the second forwarding header information field includes a destination MAC address; or the second forwarding header information field includes a source IP address, a destination IP address, and a source MAC address. Address and destination MAC address.
The node according to claim 25, wherein when the network in which the first node is located belongs to a multi-protocol label switching MPLS network, the second flow definition domain further includes an MPLS label, and the second forwarding header information The domain further includes the MPLS label, where the MPLS label is determined by the first node according to the first forwarding header information field and searching for a label forwarding table.
The node according to claim 25, wherein when the first node forwards the second protocol packet by using a universal routing encapsulation GRE tunnel, the second flow definition domain further includes a GRE IP header, The second forwarding header information field further includes the GRE IP header, where the GRE IP header is determined by the first node according to the first forwarding header information field and searching for a routing table.
The node according to claim 25, wherein when the first node forwards the second protocol packet through a MAC tunnel, the second flow definition domain further includes a MAC in MAC header, and the second The forwarding header information field further includes the MAC in MAC header, where the MAC in MAC header is determined by the first node searching for the first MAC forwarding table according to the first forwarding header information field.
The node according to claim 25, wherein when the first node forwards the second protocol packet through a virtual scalable local area network VXLAN tunnel, the second flow definition domain further includes a VXLAN header, The second forwarding header information field further includes the VXLAN header, where the VXLAN header is determined by the first node searching for the second MAC forwarding table according to the first forwarding header information field.
The node according to any one of claims 22 to 29, wherein the first protocol message further includes a queue ID and a layering level, and the queue ID and the layering level are used for the service The flow establishes a hierarchical queue and further performs scheduling deployment for the hierarchical queue.
The node according to any one of claims 22 to 30, wherein the first protocol message further comprises an information domain, and the information domain comprises monitoring information for establishing a QoS reservation.
The node according to any one of claims 22 to 31, further comprising a deleting unit, configured to: when there is no service in the preset time period, use the binding relationship generated by the first generating unit When the binding relationship is deleted.
A node, wherein the node comprises:

a generating unit, configured to generate a binding relationship and a protocol packet, where the binding relationship is a binding relationship between the flow and the QoS requirement information, where the protocol packet includes a flow definition domain, a quality of service QoS requirement domain, and a forwarding header An information field, the protocol message is used to establish a QoS reservation for the service flow, the flow definition domain is used to indicate a flow of the service flow, and the QoS requirement domain is used to indicate the QoS requirement information, and the forwarding The header information field is used to indicate a service flow forwarding path.

a sending unit, configured to send, according to the forwarding header information field, the protocol packet generated by the generating unit to another node, where the another node is a next hop node indicated by the forwarding header information field .
The node according to claim 33, wherein the generating unit comprises:

a receiving subunit, configured to receive at least one first protocol packet;

a first generating subunit, configured to combine the at least one first protocol packet to generate the protocol packet according to a convergence policy;

The second generation subunit is configured to generate the binding relationship.
The node according to claim 33 or 34, wherein the flow definition domain comprises at least one of the following: a range of a source network protocol IP address, a range of a destination IP address, a protocol identification ID, a range of a port number, and a source. Media access control MAC address range and destination MAC address range,

The forwarding header information field includes a destination IP address; or the forwarding header information field includes a source IP address, a destination IP address, and a protocol ID; or the forwarding header information field includes a source IP address, a destination IP address, and a source port. And the destination port and the protocol ID; or the forwarding header information field includes a destination MAC address; or the forwarding header information field includes a source IP address, a destination IP address, a source MAC address, and a destination MAC address.
The node according to claim 35, wherein when the network in which the first node is located belongs to a multi-protocol label switching MPLS network, the flow definition domain further includes an MPLS label, and the forwarding header information field further includes a Said MPLS label.
The node according to any one of claims 35 to 35, wherein when the first node forwards the protocol packet by using a universal routing encapsulation GRE tunnel, the flow definition domain further includes a GRE IP header, and the forwarding The header information field also includes the GRE IP header.
The node according to claim 35, wherein when the first node forwards the protocol packet through a MAC tunnel, the flow definition domain further includes a MAC in MAC header, and the forwarding header information domain further includes The MAC in MAC header.
The node according to claim 35, wherein when the first node forwards the protocol packet through a virtual scalable local area network VXLAN tunnel, the flow definition domain further includes a VXLAN header, and the forwarding header information domain Also included is the VXLAN header.
The node according to any one of claims 33 to 39, wherein the protocol message further includes a queue ID and a layering level, and the queue ID and the layering level are used to establish the service flow. Hierarchical queues and further scheduling deployment for the hierarchical queues.
The node according to any one of claims 33 to 40, wherein the protocol message further comprises an information domain, and the information domain comprises monitoring information for establishing a QoS reservation.
The node according to any one of claims 33 to 41, further comprising a deleting unit, configured to delete the binding relationship when no binding relationship is used by a service within a preset time period .