CN113452555A

CN113452555A - Service quality guarantee method and device

Info

Publication number: CN113452555A
Application number: CN202110690876.3A
Authority: CN
Inventors: 王建
Original assignee: New H3C Big Data Technologies Co Ltd
Current assignee: New H3C Big Data Technologies Co Ltd
Priority date: 2021-06-22
Filing date: 2021-06-22
Publication date: 2021-09-28
Anticipated expiration: 2041-06-22
Also published as: CN113452555B

Abstract

The present specification provides a method and an apparatus for guaranteeing quality of service, where the method includes: configuring an interconnection port corresponding to a newly added direct connection link between network devices as a trusted port, configuring a non-interconnection port as a non-trusted port, and issuing a QoS policy to an access device, thereby avoiding the situation that a user forges a high-priority message for forwarding under the condition that the network topology is changed. Meanwhile, in the method provided by the present specification, a Qos policy is only issued to the access device, when the packet matches the Qos policy, the priority information is carried in the packet, and the packet is sent to the Leaf device through the interconnection port.

Description

Service quality guarantee method and device

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for guaranteeing quality of service.

Background

In a campus network scenario, a common networking environment is formed by three layers, which are: a Spine layer, a Leaf layer and an Access layer, wherein the specific networking diagram refers to a networking diagram 1. The Spine is usually used as a core layer and used as data forwarding, the Leaf device is used as a convergence layer and is responsible for wired user authentication and wired/wireless user data forwarding control and policy control, and the Access device layer is used as an Access layer and mainly used as Access devices for directly connecting wired users and wireless APs (Access points, wireless Access nodes).

As the size of the campus increases, if the traffic is not guaranteed in the network, critical user traffic may be dropped by the switch, so that Quality of Service (QoS) needs to be used to guarantee the Quality of the feature traffic.

The actual service flow used in the current network of the user is much, and if the user manually or uses the traditional network management to ensure the flow, the operation is troublesome.

Disclosure of Invention

In order to overcome the problems in the related art, the present specification provides a method and an apparatus for guaranteeing quality of service.

According to a first aspect of embodiments herein, there is provided a quality of service assurance method, the method including:

acquiring a topological relation between network devices;

if the obtained topological relation changes compared with the last obtained topological relation, configuring an interconnection port corresponding to a newly added direct connection link between network equipment as a trusted port, and configuring a non-interconnection port as an untrusted port, wherein the non-interconnection port is a port which is not connected with the network equipment or a port which is connected with a user terminal;

and sending the QoS strategy to the access equipment, wherein the QoS strategy specifies the priority information of the service guarantee carried by the flow.

Optionally, the method further includes:

and if the managed network equipment is determined to be unreachable, not updating the topological relation.

Optionally, the method further includes:

the range of network devices that perform acquisition of the topological relationship between the network devices is specified.

Optionally, the method further includes:

determining whether an aggregation port exists;

if the aggregation port exists, acquiring a member port of the aggregation port;

and determining whether the topological relation obtained this time and the last obtained topological relation change or not according to the member port.

Optionally, the priority information is a differentiated services code point DSCP.

According to a second aspect of embodiments herein, there is provided a quality of service assurance apparatus, the apparatus comprising: the device comprises an acquisition module, a topology updating module and a distribution module;

the acquisition module is used for acquiring a topological relation between network devices;

the topology updating module is used for determining whether the obtained topology relation changes compared with the last obtained topology relation, if so, the issuing module configures an interconnection port corresponding to a newly added direct connection link between network devices as a trusted port, and configures a non-interconnection port as an untrusted port, wherein the non-interconnection port is a port which is not connected with the network devices or a port which is connected with a user terminal;

the issuing module is further configured to issue a QoS policy to the access device, where the QoS policy specifies priority information of service guarantees carried by traffic.

Optionally, the topology updating module is further configured to not update the topology relationship if it is determined that the managed network device is not reachable.

Optionally, the apparatus further comprises: and the receiving module is used for appointing the range of the network equipment for acquiring the topological relation among the network equipment.

Optionally, the topology updating module is further configured to determine whether an aggregation port exists; if the aggregation port exists, acquiring a member port of the aggregation port; and determining whether the topological relation obtained this time and the last obtained topological relation change or not according to the member port.

The technical scheme provided by the embodiment of the specification can have the following beneficial effects: configuring an interconnection port corresponding to a direct link between network equipment as a trust port, configuring a non-interconnection port as a non-trust port, and further issuing a Qos policy to access equipment, so as to avoid the situation that a user forges a high-priority message for forwarding under the condition that network topology is changed, and meanwhile, only issuing the Qos policy to the access equipment, carrying priority information in the message after the message is matched with the Qos policy, and uploading the message to Leaf equipment through the interconnection port.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.

FIG. 1 is a schematic diagram of a network architecture provided herein;

fig. 2 is a schematic flowchart of a method for guaranteeing quality of service according to an embodiment of the present disclosure;

FIG. 3 is a flowchart illustrating a method for guaranteeing quality of service according to another embodiment of the present disclosure;

FIG. 4 is a schematic flow chart diagram illustrating a method for providing quality of service assurance in accordance with yet another embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of a quality of service assurance device provided in an embodiment of the present specification;

fig. 6 is a schematic structural diagram of a controller provided in the present specification.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.

In the related art, quality assurance for service traffic can be achieved by the following means:

a user performs the same QoS service provisioning for a certain service flow on each network device, and when each service flow performs QoS provisioning configuration independently, many ACLs (Access Control Lists ) need to be occupied, but this way is likely to conflict with PBR (Policy Based Routing). And for the scene that the network topology changes, the configuration of re-issuing the Qos policy for the interface with the changed network topology is also complex.

Example one

In the method, an interconnection port corresponding to a newly added direct connection link between network devices is configured as a trusted port, a non-interconnection port is configured as an untrusted port, and a Qos policy is issued to an access device, so that a situation that a user forges a high-priority message and forwards the high-priority message when a network topology is changed is avoided. Meanwhile, in the method provided by the present specification, a Qos policy is only issued to the access device, when the packet matches the Qos policy, the priority information is carried in the packet, and the packet is sent to the Leaf device through the interconnection port.

The service quality assurance method provided in this specification may be applied to an SDN (Software Defined Network) controller or Network management Software, and a physical entity installed in the Network management Software is not limited.

Fig. 2 is a schematic flow diagram of a method for guaranteeing quality of service provided in this embodiment, where the method is described by taking network management software as an example, as shown in fig. 2, the method includes:

step 201, acquiring a topological relation between network devices.

The network management software may periodically obtain Link Layer Discovery Protocol (LLDP) information stored in the network device. The LLDP information includes information of a network device directly connected to the network device, and may include, for example, any one or more of an MAC address of the network device, a type of the network device (switch, router), whether the network device is online, information of a port that receives an LLDP message, and information of a port that a previous hop device sends an LLDP message. Whether the network device is online or not may be determined by sending a heartbeat message to the network device, and the like, and the specific way of determining that the network device is online is not limited in this embodiment.

And obtaining the connection relationship, namely the topological relationship, among all the network devices managed by the network management software according to the obtained LLDP information.

Of course, the contents included in the LLDP information may be drawn and stored in the network management software by an administrator directly in advance when the network device is wired.

Any implementation manner in the prior art may be adopted for the network management software to obtain the network topology relationship, and details are not described in this embodiment.

Step 203, if the obtained topological relation changes compared with the last obtained topological relation, configuring an interconnection port corresponding to a newly added direct connection link between the network devices as a trusted port, and configuring a non-interconnection port as an untrusted port, where the non-interconnection port is a port not connected with the network device or a port connected with the user terminal.

Taking the network architecture shown in fig. 1 as an example, if there is no other network device between the spin and the leaf1, a direct link is between the spin and the leaf1, then a port on the leaf1 connected to the spin and a port on the spin connected to the leaf1 are all interconnect ports; if no other network device exists between the Access1 and the leaf1, the two are directly connected, then the Access1 and the leaf1 are directly connected, and then a port on the leaf1 connected with the Access1 and a port on the Access1 connected with the leaf1 are all internet ports.

Of course, the terminal may be directly connected to the access device, or the terminal may also be directly connected to the access device through the AP, generally, the AP is controlled by the access controller AC, and therefore, the direct link mentioned in this embodiment may be a direct link involved between the access device and the spine.

Referring to fig. 1, the access2 is directly connected to the terminal, and the port on the access2 directly connected to the terminal is the port connected to the user terminal, that is, the non-interconnect port. Alternatively, if the other ports on the access2 are not connected to any network device except the port connected to the terminal on the access2, then the other ports on the access2 that are not connected to any network device are also non-interconnect ports. If only access1 and access2 are hung down on leaf1, then the other ports on leaf1 are non-direct ports.

Referring to fig. 1, for example, if the Access device Access1 is deleted, or the Access device Access1 changes from being directly connected to the leaf1 to being directly connected to the leaf2, this may result in a change in the topology.

In the case that the access device access1 is deleted, the port connected to the access1 in the previous leaf1 becomes a non-interconnect port, and the non-interconnect port is configured as an untrusted port.

For the Access device Access1, the Access device Access1 is changed from direct connection with the leaf1 to direct connection with the leaf2, then the port on the leaf2 connected with the moved Access1 and the port on the Access1 connected with the leaf2 are direct connection ports, and at this time, the port on the Access1 connected with the leaf2 is configured as a trusted port.

Step 205, issuing a QoS policy to the access device, where the QoS policy specifies priority information of service guarantees carried by traffic.

The important change in this embodiment is that the QoS policy is issued to the access device, and the QoS policy specifies the priority information of the service guarantee carried by the matched traffic. Therefore, the QoS policy does not need to be issued to other devices (e.g., leaf devices, spine devices, AP devices) outside the access device in a large amount as in the related art. The method provided by this embodiment can reduce the number of Qos policies issued to other devices (e.g., leaf devices, spine devices, and AP devices).

That is, after the access device receives the message, if the source address or/and the destination address of the message matches the Qos policy, the message carries priority information specified by the Qos policy.

Because the interconnection port of the leaf of the network device directly connected with the access device is configured as a trust port, the message can be forwarded with corresponding priority by directly utilizing the priority information carried by the received message.

For the non-interconnected port, because the port is configured as the untrusted port, the port can be ensured not to be forged by the user and the high-priority message can not be forwarded.

Specifically, the corresponding port can be configured as a trusted port by issuing configuration of a priority trust mode through the corresponding port, and the message is allowed to carry priority information under the condition of configuring the priority trust mode. And if the port is configured as an untrusted port, the message is not allowed to carry the priority information.

Example two

On the basis of the foregoing embodiments, this embodiment further provides a quality of service guarantee method, and fig. 3 shows a flowchart of the method, and as shown in fig. 3, the method includes:

step 201, acquiring a topological relation between network devices;

step 202, if it is determined that the managed network device is not reachable, topology updating is not performed.

Step 201, step 203, and step 205 are similar to the implementation manner of the above embodiment, and are not described in detail in this embodiment.

For step 202, in an implementation manner, the network topology relationship carries information about whether the network device is currently reachable, for example, the LLDP information carries information about reachability of the network device.

In another implementation manner, the Network management software may determine the reachability of the Network device through a Network Configuration Protocol (netconf), an openflow Protocol, or the like. The purpose of determining the reachability is that, in the network, there may be a case where some network devices are currently disconnected instantaneously, and at this time, the network devices may not be able to communicate with the network management software, and if such a case occurs, the current network topology relationship is not updated, that is, the relationship of the network topology obtained last time is still adopted for the network device. It should be noted that the unreachable is that the network device is still under the management of the network management software, and thus is in a different state from the state in which the network device is deleted (i.e., not managed by the network management software).

For the embodiments shown in fig. 2 and fig. 3, in an optional case, the functions of step 201 and step 203 may also be performed for a specific network range (for example, setting an IP network segment range of a network device), in an example, a switch in a software form may be set on the visual interface, and when the switch is turned on, the steps of step 201 and step 203 are triggered to be performed. Step 205 may be automatically triggered and executed by the switch, or may be configured by the user.

The method provided in this embodiment may also be applied to a case where an aggregation port exists, and fig. 4 shows a flowchart of a quality of service guarantee method applied to an architecture of the aggregation port, as shown in fig. 4, the method includes:

step 401, acquiring a topological relation between network devices;

step 402, determining whether an aggregation port exists;

step 403, if an aggregation port exists, acquiring a member port of the aggregation port;

step 404, determining whether the obtained topological relation changes with the last obtained topological relation according to the member port;

step 405, if the obtained topological relation changes compared with the last obtained topological relation, configuring an interconnection port corresponding to a newly added direct connection link between the network devices as a trusted port, and configuring a non-interconnection port as an untrusted port, where the non-interconnection port is a port not connected with the network device or a port connected with the user terminal.

Step 406, sending the QoS policy to the access device, where the QoS policy specifies priority information of service guarantee carried by the traffic.

Steps

401, 405, and 406 are similar to

steps

201, 204, and 205 in the above embodiment, and this embodiment is not described in detail again. The

steps

402 and 404 in this embodiment can also be combined with the embodiment shown in fig. 3.

For steps 402-404, the steps can be executed after acquiring the topological relation between the network devices. Of course, before step 401, the information that the aggregation port exists between all network devices managed by the network management software may also be acquired, and the information of the member port of the aggregation port may also be determined. And then determining direct links between the member ports according to the information of the member ports.

The priority information in the embodiments in this specification may be DSCP (Differentiated Services Code Point), or may be IP priority.

EXAMPLE III

Corresponding to the quality of service assurance method provided in the foregoing embodiment, a quality of service assurance device is provided in this embodiment, and is configured to perform the method described in any one of the foregoing embodiments. Fig. 5 is a schematic structural diagram of a quality of service guarantee device provided in this embodiment, and as shown in fig. 5, the device includes: an acquisition module 501, a topology updating module 502 and a distribution module 503;

the acquiring module 501 is configured to acquire a topological relation between network devices;

the topology updating module 502 is configured to determine whether the obtained topology relationship changes compared with the last obtained topology relationship, and if the obtained topology relationship changes, the issuing module 503 configures an interconnection port corresponding to a newly added direct-connected link between network devices as a trusted port and configures a non-interconnection port as an untrusted port, where the non-interconnection port is a port which is not connected to a network device or a port which is connected to a user terminal;

the issuing module 503 is further configured to issue a QoS policy to the access device, where the QoS policy specifies priority information of service guarantees carried by traffic.

Optionally, the topology updating module 502 is further configured to not update the topology relationship if it is determined that the managed network device is not reachable.

Optionally, the apparatus may further include: a receiving module (not shown in the figure) for specifying a range of the network device performing the acquisition of the topological relation between the network devices.

Optionally, the topology updating module 502 may be further configured to determine whether an aggregation port exists; if the aggregation port exists, acquiring a member port of the aggregation port; and determining whether the topological relation obtained this time and the last obtained topological relation change or not according to the member port.

The present disclosure further provides a controller 60, and fig. 6 is a schematic structural diagram of a controller according to another embodiment of the present disclosure, as shown in fig. 6, the controller 60 includes a processor 601 and a memory 602,

the memory 602 is configured to store program instructions, the processor 601 is configured to call the program instructions stored in the memory, and when the processor 601 executes the program instructions stored in the memory 602, the processor is configured to perform any one of the methods provided in the first embodiment or the second embodiment. Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.

In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, functional modules in the embodiments of the present disclosure may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solution of the present disclosure or portions thereof that contribute to the prior art in essence can be embodied in the form of a software product, which is stored in a readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present disclosure. And the aforementioned readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Claims

1. A method for guaranteeing quality of service, comprising:

acquiring a topological relation between network devices;

2. The method of claim 1, further comprising:

3. The method of claim 2, further comprising:

4. The method of claim 1, further comprising:

determining whether an aggregation port exists;

5. The method according to any of claims 1-4, wherein the priority information is a differentiated services code point, DSCP.

6. A quality of service assurance apparatus, characterized in that the apparatus comprises: the device comprises an acquisition module, a topology updating module and a distribution module;

7. The apparatus of claim 6, wherein the topology update module is further configured to not perform topology relationship update if it is determined that the managed network device is not reachable.

8. The apparatus of claim 6, further comprising: and the receiving module is used for appointing the range of the network equipment for acquiring the topological relation among the network equipment.

9. The apparatus of claim 6, wherein the topology update module is further configured to determine whether an aggregation port exists; if the aggregation port exists, acquiring a member port of the aggregation port; and determining whether the topological relation obtained this time and the last obtained topological relation change or not according to the member port.

10. The apparatus according to any of claims 6-9, wherein the priority information is a differentiated services code point, DSCP.