WO2021121086A1 - 一种流量调度方法、电子设备及存储介质 - Google Patents

一种流量调度方法、电子设备及存储介质 Download PDF

Info

Publication number
WO2021121086A1
WO2021121086A1 PCT/CN2020/134650 CN2020134650W WO2021121086A1 WO 2021121086 A1 WO2021121086 A1 WO 2021121086A1 CN 2020134650 W CN2020134650 W CN 2020134650W WO 2021121086 A1 WO2021121086 A1 WO 2021121086A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling
traffic
service
queue
service traffic
Prior art date
Application number
PCT/CN2020/134650
Other languages
English (en)
French (fr)
Inventor
任坤
潘康
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20903344.8A priority Critical patent/EP4072085A4/en
Publication of WO2021121086A1 publication Critical patent/WO2021121086A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
    • H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/60—Queue scheduling implementing hierarchical scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a traffic scheduling method, electronic device, and storage medium.
  • Multi-queue technology can be used to implement rich hierarchical quality of service (HQoS) functions, such as traffic rate limiting, congestion avoidance, traffic shaping, queue scheduling, etc., based on multi-level queue technology to achieve hierarchical scheduling, not only distinguishes Users also distinguish between services and traffic, which can not only provide refined service quality assurance, but also save network operation and maintenance costs as a whole.
  • HQoS rich hierarchical quality of service
  • the inventor of this application found that the current HQoS policy is used to schedule traffic. If the HQoS policy is configured on the sub-interfaces, the HQoS policies of each sub-interface are independent of each other, and can only be used for the internal service traffic of each user. It is not possible to schedule and limit the rate of service traffic at the port level. If the HQoS policy is configured on the port, a total scheduling and speed limit will be performed on all service traffic on the port, but it cannot take into account the scheduling and speed limit of the user's internal service traffic.
  • the purpose of the embodiments of the present application is to provide a traffic scheduling method, electronic equipment, and storage medium.
  • the embodiment of the present application provides a traffic scheduling method, including: obtaining the service traffic received by the data receiving port; according to a preset first scheduling strategy, scheduling the service traffic for the first time; wherein , The first scheduling strategy is a user-level scheduling strategy; forwards the service traffic after the first scheduling to the data receiving port; according to the preset second scheduling strategy, the service traffic is scheduled for the second time; among them, the second
  • the scheduling policy is a port-level scheduling policy; the service traffic after the second scheduling is sent through the data sending port.
  • the embodiment of the present application also provides an electronic device, including: a memory communicatively connected with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are The at least one processor executes, so that the at least one processor can execute the above-mentioned traffic scheduling method.
  • the embodiment of the present application also provides a computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor, the above-mentioned traffic scheduling method is implemented.
  • Fig. 1 is a flowchart of a traffic scheduling method according to the first embodiment of the present application
  • Fig. 2 is a flowchart of a traffic scheduling method according to the second embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a traffic scheduling system according to the second embodiment of the present application.
  • Fig. 4 is a flowchart of a traffic scheduling method according to the third embodiment of the present application.
  • Fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application.
  • the purpose of the embodiments of the present application is to provide a traffic scheduling method, electronic equipment, and storage medium, so that in a multi-service scenario where the HQoS function is applied, user-level and port-level scheduling and rate limiting of service traffic are performed at the same time.
  • the first embodiment of the application relates to a traffic scheduling method.
  • This embodiment is applied to network communication equipment and is implemented based on the HQoS multi-level quality of service function.
  • the service traffic received by the data receiving port is acquired;
  • the first scheduling strategy is set to schedule business traffic for the first time;
  • the first scheduling strategy is a user-level scheduling strategy;
  • the business traffic after the first scheduling is forwarded to the data receiving port; according to the preset first scheduling strategy
  • the second scheduling strategy is to schedule the business traffic for the second time;
  • the second scheduling strategy is a port-level scheduling strategy; the business traffic after the second scheduling is sent through the data sending port.
  • the traffic scheduling method in this embodiment is shown in Figure 1, and includes:
  • Step 101 According to a preset first scheduling policy, perform the first scheduling of service traffic.
  • the first scheduling strategy is a user-level scheduling strategy.
  • the data receiving port is the downstream switching side interface of the network communication device.
  • the network communication equipment receives the business traffic sent from the backplane switching network through the downstream switch side interface, analyzes the business traffic, and obtains the forwarding priority of the business traffic during traffic scheduling.
  • the first scheduling strategy is a user-level traffic scheduling strategy.
  • the attributes of business traffic include users and services.
  • the first scheduling strategy can either schedule the service flow according to the priority of the user to which the service flow belongs, or schedule the service flow according to the priority of the specific service to which the service flow belongs. In the scenario where the HQoS function is applied, different service flows will pass through different sub-interfaces. If the first scheduling policy is bound to the sub-interfaces, each sub-interface can only schedule service flows passing through the sub-interface.
  • Step 102 Forward the service traffic after the first scheduling to the data receiving port.
  • the service traffic is forwarded to the uplink side interface through the loopback port inside the device, and then sent to the downlink switching side interface through the uplink side interface, and then through the downlink switching side
  • the interface receives service traffic again.
  • Step 103 Perform a second scheduling on the service traffic after the first scheduling according to the preset second scheduling strategy.
  • the second scheduling policy is a port-level traffic scheduling policy, which can be bound to the parent interface. Since all business traffic needs to pass through the parent interface, according to the second scheduling strategy, all business traffic that needs to pass through the port can be scheduled as a whole. In the first scheduling, the business traffic has been differentiated according to the priority of users or services. On the basis of, ensure the scheduling and speed limit of port-level traffic.
  • Step 104 Forward the service traffic after the second scheduling to the data sending port.
  • the data sending port is the downstream line side interface. After the service traffic is scheduled for the second time, the service traffic that has completed the entire scheduling process is directly forwarded to the data sending port, and the traffic is sent to the line side through the data sending port equipment.
  • the two scheduling of business traffic mainly implements user-based (can be distinguished by VLAN (virtual local area network)) traffic rate limiting and internal priority scheduling; the second scheduling does not Care about specific user VLAN and other information, and only perform rate limiting and priority scheduling on all service traffic on the port.
  • VLAN virtual local area network
  • the network communication device in this embodiment obtains the service flow, it first schedules the service flow based on the user-level scheduling strategy, and then adjusts the service flow after the first dispatch.
  • the service traffic is scheduled for the second time based on the port-level scheduling strategy, so as to realize the second enqueue of the service traffic, so that when the service traffic is managed by the multi-level quality of service HQoS function, the user-level and the port can be realized at the same time.
  • Level of traffic scheduling and rate limiting are examples of traffic scheduling and rate limiting.
  • the second embodiment of the present application relates to a traffic scheduling method.
  • this embodiment it is specifically explained how to schedule service traffic for the first time according to the first scheduling policy and how to schedule the traffic for the first time according to the second scheduling policy.
  • the traffic is scheduled for the second time.
  • the traffic scheduling method in this embodiment is shown in Figure 2 and includes:
  • Step 201 Obtain the service traffic received by the data receiving port.
  • Step 202 Search whether there is a first scheduling queue corresponding to the sub-interface identifier of the service traffic in the preset first mapping relationship. If there is a first scheduling queue corresponding to the sub-interface identifier of the service traffic in the preset first mapping relationship, perform step 203; if there is no corresponding sub-interface identifier of the service traffic in the preset first mapping relationship For the first scheduling queue of, step 205 is executed.
  • Step 203 Add the service traffic to the first scheduling queue corresponding to the sub-interface identifier of the service traffic in the first mapping relationship.
  • Step 204 Send the service flow according to the priority of the first scheduling queue to which the service flow is added.
  • the interface has three ways to bind HQoS scheduling policies, including:
  • Binding to the interface in multiple-level mode This method of binding informs that the traffic needs to be enqueued twice.
  • the child interface is bound to the HQoS scheduling policy in the multiple-level mode
  • the parent interface is bound to the HQoS scheduling policy in the overwrite mode.
  • the service traffic uses the sub-interface identifier to find the corresponding first scheduling queue in the first mapping relationship, and completes the first scheduling through the sub-interface, where the first mapping relationship is the mapping relationship between the user to which the service belongs and the queue identifier.
  • Stored in the ACL table access control list
  • look up the corresponding second dispatch queue in the ACL table with the parent interface identifier and complete the second dispatch through the parent interface.
  • the first scheduling policy is pre-configured, and the device binds the first scheduling policy to the sub-interface according to the preset configuration, and then attaches queues to each sub-interface according to the first scheduling policy, and each queue is All have different priorities, and the priority is determined according to the pre-configured first scheduling strategy.
  • the service traffic in the queue with the higher priority will be forwarded first.
  • the sub-interface when the service traffic is first scheduled, the sub-interface will write the second scheduling mark to the service traffic, and the service traffic will be added to the queue attached to the internal loopback port. After the service traffic is scheduled for the first time, it will be forwarded to the downstream switch side interface through the loopback port.
  • the first mapping relationship in this embodiment is the mapping relationship between the sub-interface identifier and the first scheduling queue, and the first mapping relationship is stored in the access control rule ACL table.
  • step 205 If the first scheduling queue corresponding to the sub-interface identifier does not exist in the ACL table, skip the first scheduling of the service traffic and directly perform the second scheduling, go to step 205, in the preset second mapping relationship Find out whether there is a sub-interface identifier related to business traffic.
  • Step 205 Find in the preset second mapping relationship whether there is a second scheduling policy corresponding to the parent interface identifier of the service traffic. If there is a second scheduling queue corresponding to the sub-interface identifier of the service traffic in the preset second mapping relationship, step 206 is executed; if there is no second scheduling queue corresponding to the sub-interface identifier of the service traffic in the preset second mapping relationship For the second scheduling queue of, then step 208 is executed.
  • Step 206 Add the service traffic to the second scheduling queue corresponding to the parent interface identifier of the service traffic in the second mapping relationship.
  • the second mapping relationship in this embodiment is the mapping relationship between the parent interface identifier and the second scheduling queue, and the second mapping relationship is also stored in the access control rule ACL table.
  • the parent interface through which the service traffic passes is determined according to the scheduling tree under the pre-configured second scheduling policy, and then the second mapping relationship corresponding to the parent interface identifier in the ACL table is found according to the second mapping relationship.
  • the dispatch queue if a second dispatch queue corresponding to the parent interface identifier is found in the ACL table, the service traffic is added to the second dispatch queue.
  • step 208 is executed to add the service traffic
  • the default queue according to the priority of the default queue, schedules the service traffic that has not completed ACL rule matching for the second time.
  • Step 207 Send the service flow according to the priority of the second scheduling queue to which the service flow is added.
  • the parent interface binds the HQoS scheduling policy in the overwrite mode, searches the corresponding second scheduling queue in the ACL table with the parent interface identifier, and completes the second scheduling through the parent interface.
  • the pre-configured second scheduling policy is bound to the parent interface (bind the HQoS scheduling policy in overwrite mode), and the network communication device attaches queues to each sub-interface according to the bound second scheduling policy.
  • Each queue has a different priority. In actual operation, when there are multiple service traffic on the same interface, the service traffic in the queue with the higher priority will be forwarded first. After the service flow is scheduled for the second time, it is sent out through the downlink side to complete the entire scheduling process of the service flow.
  • Fig. 3 the structure of the traffic scheduling system in this embodiment is shown in Fig. 3, including:
  • the network processor NP Network Process
  • the network processor NP is used to parse the traffic received by the downstream switching side interface, and find the queue identifier that has a mapping relationship with the interface identifier of the service traffic in the ACL table according to the interface identifier of the service traffic, and then The parsed service traffic is forwarded to the traffic manager TM1, and related information such as queue identification is also sent to the traffic manager TM1.
  • TM1 forwards the service flow to the uplink side interface through the loopback port
  • NP is also used to forward the service flow to the downlink switch side interface in a transparent transmission mode.
  • the forwarding path during the first scheduling of service traffic is represented by a solid arrow in the figure
  • the forwarding path during the second scheduling of service traffic is represented by a dashed arrow in the figure.
  • the traffic manager TM1 is used to add the service traffic analyzed by NP to the corresponding queue according to the queue identifier sent by the NP, and then assign different priorities to each queue according to the preset HQoS strategy, according to the priority of each queue To complete the scheduling of business traffic and speed limit.
  • the service traffic is directly added to the corresponding queue attached to the TM loopback port LP according to the queue identifier. After the first scheduling, it is forwarded to the uplink side interface through the LP, and then The NP is transparently transmitted to the downstream switch side interface, and the second scheduling of traffic starts. After the second scheduling is completed, the service traffic is forwarded from the downlink line side interface through the logical port P2.
  • the NP after the NP receives the service flow from the downstream switching side interface for the first time and analyzes the service flow, if the sub-interface identification of the service flow is not found in the preset ACL table, it has the same identity as the sub-interface identification.
  • the queue identifier of the mapping relationship continues to search for the queue identifier that has a mapping relationship with the parent interface identifier in the preset ACL table according to the parent interface identifier of the service traffic. If the queue identifier that has a mapping relationship with the parent interface identifier is not found in the preset ACL table based on the parent interface identifier of the service traffic, NP will send the default queue information to TM1, and then TM1 will add the service traffic to the default queue. Forward business traffic according to the priority of the default queue, and complete the scheduling of business traffic.
  • the third embodiment of the present application relates to a traffic scheduling method.
  • the third embodiment is roughly the same as the second embodiment.
  • the main difference is: in the second embodiment, when the service traffic is scheduled for the first time, the first mapping relationship is searched according to the sub-interface identifier of the service traffic.
  • the first scheduling queue corresponding to the sub-interface identifier; when the traffic is scheduled for the second time, the second scheduling queue corresponding to the parent interface identifier is searched in the second mapping relationship according to the parent interface identifier of the service traffic.
  • the first scheduling queue corresponding to the interface identifier is searched in the first mapping relationship according to the interface identifier of the service flow, where the interface identifier of the service flow is It is the combination of the sub-interface identifier and the parent interface identifier; when the traffic is scheduled for the second time, the second scheduling queue corresponding to the IP priority field is searched in the second mapping relationship according to the IP priority field of the service traffic.
  • the traffic scheduling method in the third embodiment of the present application is shown in FIG. 4 and includes:
  • Step 401 Obtain the service traffic received by the data receiving port.
  • Step 402 Find in the preset first mapping relationship whether there is a first scheduling policy corresponding to the interface identifier of the service traffic, where the interface identifier is a combination of the sub-interface identifier of the service traffic and the parent interface identifier. If there is a first scheduling queue corresponding to the interface identifier of the service traffic in the preset first mapping relationship, step 403 is executed; if there is no first scheduling queue corresponding to the interface identifier of the service traffic in the preset first mapping relationship For a dispatch queue, step 405 is executed.
  • Step 403 Add the service traffic to the first scheduling queue corresponding to the interface identifier of the service traffic in the first mapping relationship.
  • Step 404 Send the service flow according to the priority of the first scheduling queue to which the service flow is added.
  • the first mapping relationship stored in the ACL table in this embodiment is the mapping relationship between the sub-interface identifier of the service traffic and the combination with the parent interface identifier and the first scheduling queue.
  • the first scheduling policy is bound to the HQoS policy of the parent interface in a multiple-level mode, and the HQoS policy distinguishes the priority of service traffic based on user information.
  • Steps 402 to 404 are similar to steps 202 to 204 in the second embodiment of the present application, and other implementation details have been specifically described in the second embodiment of the present application, and will not be repeated here.
  • Step 405 Search for a second scheduling queue corresponding to the IP priority field of the service traffic in the preset second mapping relationship.
  • QoS-template (8 phb scheduling and rate limiting based on ports) scheduling and rate limiting strategies are pre-bound on the parent interface. This strategy is based on the IP priority field in the service traffic packet. The priority of business traffic is distinguished. Therefore, in this embodiment, the second mapping relationship is the mapping relationship between the IP priority field and the second scheduling queue, and the second mapping relationship is stored in the outbound port table. After analyzing the service flow, it is necessary to obtain the IP priority field in the service flow, and then look up the second dispatch queue corresponding to the service flow in the outbound port table according to the IP priority field. Since all traffic needs to be forwarded from the logical outbound port through the parent interface, this policy binding method can implement port-level traffic scheduling.
  • NP parses the service traffic, it queries the corresponding queue ID in the outbound port table according to the IP priority field, and then forwards the service traffic and the corresponding queue ID to the traffic manager TM1 at the same time, and then TM1 will The service traffic is added to the corresponding queue, and the service traffic is forwarded according to the priority of the queue, and the port-level traffic scheduling is completed.
  • the first scheduling of service traffic includes: according to the sub-interface identifier of the service traffic, and the first mapping relationship between the preset sub-interface identifier and the first scheduling queue, the service The sub-interface of the traffic added to the service traffic identifies the corresponding first dispatch queue in the first mapping relationship; the service traffic is sent according to the priority of the first dispatch queue to which the service traffic joins.
  • the user-level scheduling strategy is selected based on the sub-interface identification of the service flow access to schedule the service flow for the first time.
  • the second scheduling of service traffic includes: according to the parent interface identifier of the service traffic, and the second mapping relationship between the preset parent interface identifier and the second scheduling queue, the service The parent interface of the traffic added to the service traffic identifies the second scheduling queue corresponding to the second mapping relationship; the service traffic is sent according to the priority of the second scheduling queue to which the service traffic is added. It realizes that the port-level scheduling strategy is selected based on the identifier of the parent interface to which the service traffic is accessed to schedule the service traffic after the second enqueue.
  • the first scheduling of the service flow includes: adding the service flow according to the interface identification of the service flow and the first mapping relationship between the preset interface identification and the first dispatch queue
  • the interface identifier of the service traffic corresponds to the first dispatch queue in the first mapping relationship
  • the interface identifier of the service traffic is a combination of the sub-interface identifier and the parent interface identifier
  • the service is sent according to the priority of the first dispatch queue to which the service traffic joins flow. It is realized that the user-level scheduling strategy is selected based on the combination of the sub-interface for service traffic access and the identifier of the parent interface to schedule the service traffic for the first time.
  • the second scheduling of service traffic includes: according to the Internet Protocol IP priority field of the service traffic, and the second mapping relationship between the IP priority field and the second scheduling queue, the The service flow is added to the second scheduling queue corresponding to the IP priority field of the service flow in the second mapping relationship; the service flow is sent according to the priority of the second scheduling queue to which the service flow is added.
  • the port-level scheduling strategy is selected based on the IP priority field of the service traffic to schedule the service traffic after the second enqueue.
  • the fourth embodiment of the present application relates to a server. As shown in FIG. 5, it includes at least one processor 501; and a memory 502 communicatively connected with at least one processor 501; The instructions executed by 501 are executed by at least one processor 501, so that the at least one processor 501 can execute the traffic scheduling method of any one of the first to third embodiments.
  • the memory 502 and the processor 501 are connected in a bus manner.
  • the bus may include any number of interconnected buses and bridges, and the bus connects one or more various circuits of the processor 501 and the memory 502 together.
  • the bus can also connect various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all well-known in the art, and therefore, no further description will be given herein.
  • the bus interface provides an interface between the bus and the transceiver.
  • the transceiver may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on the transmission medium.
  • the data processed by the processor 501 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 501.
  • the processor 501 is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 502 may be used to store data used by the processor 501 when performing operations.
  • the fifth embodiment of the present application relates to a computer-readable storage medium that stores a computer program.
  • the computer program is executed by the processor, the above method embodiment is realized.
  • the program is stored in a storage medium and includes several instructions to enable a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) that executes all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

本申请实施例涉及通信技术领域，公开了一种流量调度方法、电子设备及存储介质。本申请中，所述方法包括：获取数据接收端口接收到的业务流量；根据预设的第一调度策略，对业务流量进行第一次调度；其中，第一调度策略为用户级的调度策略；将经过第一次调度后的业务流量转发至数据接收端口；根据预设的第二调度策略，对业务流量进行第二次调度；其中，第二调度策略为端口级的调度策略；将第二次调度后的业务流量通过数据发送端口进行发送。

Description

一种流量调度方法、电子设备及存储介质
相关申请的交叉引用
本申请基于申请号为201911291974.9、申请日为2019年12月16日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及通信技术领域，特别涉及一种流量调度方法、电子设备及存储介质。
背景技术
目前随着用户规模的扩大，业务种类的增多，要求网络通讯设备不仅能够进一步细化区分业务流量，而且还能够对多用户、多业务、多种流量等传输对象进行统一管理和分层调度。多队列技术可以用于实现丰富的多层级服务质量HQoS(Hierarchical Quality of Service)功能，例如流量限速、拥塞避免、流量整形、队列调度等，基于多级队列技术实现层次化调度，不仅区分了用户，也区分了业务和流量，既能够提供精细化的服务质量保证，又能够从整体上节约网络运行维护成本。
然而，本申请的发明人发现：以目前的HQoS策略对流量进行调度，若HQoS策略配置在子接口，则每个子接口的HQoS策略是相互独立，只能单独对每个用户内部的业务流量而不能对端口级的业务流量进行调度和限速。若HQoS策略配置在端口上，则会对端口上所有的业务流量进行一个总的调度和限速，但不能兼顾用户内部的业务流量的调度和限速。
发明内容
本申请实施方式的目的在于提供一种流量调度方法、电子设备及存储介质。
为解决上述技术问题，本申请的实施方式提供了一种流量调度方法，包括：获取数据接收端口接收到的业务流量；根据预设的第一调度策略，对业务流量进行第一次调度；其中，第一调度策略为用户级的调度策略；将经过第一次调度后的业务流量转发至数据接收端口；根据预设的第二调度策略，对业务流量进行第二次调度；其中，第二调度策略为端口级的调度策略；将第二次调度后的业务流量通过数据发送端口进行发送。
本申请的实施方式还提供了一种电子设备，包括：与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如上述的流量调度方法。
本申请的实施方式还提供了一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现如上述的流量调度方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定。
图1是根据本申请第一实施方式中流量调度方法的流程图；
图2是根据本申请第二实施方式中流量调度方法的流程图；
图3是根据本申请第二实施方式中流量调度系统的结构示意图；
图4是根据本申请第三实施方式中流量调度方法的流程图；
图5是根据本申请第四实施方式中电子设备的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施方式进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施方式中，为了使读者更好地理解本申请而提出了许多技术细节。 但是，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
本申请实施方式的目的在于提供一种流量调度方法、电子设备及存储介质，使得在应用HQoS功能的多业务场景下，同时对业务流量进行用户级和端口级的调度和限速。
本申请的第一实施方式涉及一种流量调度方法，本实施例应用于网络通讯设备，基于HQoS多层级服务质量功能实现，在本实施例中，获取数据接收端口接收到的业务流量；根据预设的第一调度策略，对业务流量进行第一次调度；其中，第一调度策略为用户级的调度策略；将经过第一次调度后的业务流量转发至数据接收端口；根据预设的第二调度策略，对业务流量进行第二次调度；其中，第二调度策略为端口级的调度策略；将第二次调度后的业务流量通过数据发送端口进行发送。
下面结合附图对本实施方式的流量调度方法的实现细节进行具体的说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。
本实施方式中的流量调度方法如图1所示，包括：
步骤101，根据预设的第一调度策略，对业务流量进行第一次调度。其中，第一调度策略为用户级的调度策略。
在一些情形下，在本实施方式中数据接收端口为网络通讯设备的下行交换侧接口。网络通讯设备通过下行交换侧接口接收来自背板交换网发送过来的业务流量，对业务流量进行解析，获取业务流量在流量调度时的转发优先级。
第一调度策略为基于用户级的流量调度策略。业务流量具有的属性包括用户和业务。第一调度策略既可以根据业务流量所属用户的优先级来对业务流量进行调度，也可以根据业务流量所属的具体业务的优先级来对业务流量进行调度。在应用HQoS功能的场景下，不同的业务流量会经过不同的子接口，若第一调度策略绑定于子接口，则每一个子接口只能对经过该子接口的业务流量进行调度。
步骤102，将经过第一次调度后的业务流量转发至数据接收端口。
在一些情形下，在对业务流量进行第一次调度后，通过设备内部的环回端 口将业务流量转发至上行线路侧接口，然后通过上行线路侧接口发送至下行交换侧接口，通过下行交换侧接口再次接收业务流量。
步骤103，根据预设的第二调度策略，对经第一次调度后的业务流量进行第二次调度。
在一些情形下，第二调度策略为基于端口级的流量调度策略，可绑定于父接口上。由于所有的业务流量均需要通过父接口，因此根据第二调度策略可以对所有需经过端口的业务流量进行整体的调度，在第一次调度已经根据用户或业务的优先级对业务流量进行了区分的基础上，保证端口级别流量的调度和限速。
步骤104，将第二次调度后的业务流量转发至数据发送端口。
在一些情形下，数据发送端口为下行线路侧接口，对业务流量进行第二次调度后，直接将已经完成整个调度过程的业务流量转发至数据发送端口，通过数据发送端口将流量发往线路侧设备。
在一个例子中，对业务流量进行的两次调度，第一次调度主要实现基于用户(可以通过VLAN(虚拟局域网)进行区分)的流量限速和内部优先级的调度；第二次调度则不关心具体用户VLAN等信息，只对端口上的所有业务流量进行限速和优先级调度。
与现有技术相比，本实施方式中的网络通讯设备在获取到业务流量后，首先以基于用户级的调度策略对业务流量进行第一次调度，然后将经过第一次调度后的业务流量以基于端口级的调度策略对业务流量进行第二次调度，从而实现业务流量的二次入队，使得在利用多层级服务质量HQoS功能来对业务流量进行管理时，能够同时实现用户级和端口级的流量调度和限速。
本申请的第二实施方式涉及一种流量调度方法，本实施方式中，具体说明了如何根据第一调度策略对业务流量进行第一次调度以及如何根据第二调度策略对经第一次调度的流量进行第二次调度。
本实施方式中的流量调度方法如图2所示，包括：
步骤201，获取数据接收端口接收到的业务流量。
步骤202，在预设的第一映射关系中查找是否存在与业务流量的子接口标 识对应的第一调度队列。若在预设的第一映射关系中存在与业务流量的子接口标识对应的第一调度队列，则执行步骤203；若在预设的第一映射关系中不存在与业务流量的子接口标识对应的第一调度队列，则执行步骤205。
步骤203，将业务流量加入业务流量的子接口标识在第一映射关系中对应的第一调度队列。
步骤204，根据业务流量加入的第一调度队列的优先级发送业务流量。
在一些情形下，接口有三种绑定HQoS调度策略的方式，包括：
(1)直接绑定到接口，这种绑定方式只对经过该接口的流量做HQoS；
(2)以overwrite模式绑定到父接口，这种方式绑定的HQoS策略既对父接口的流量做HQoS，也对所有父接口对应的子接口流量做HQoS；
(3)以multiple-level模式绑定到接口，这种方式绑定是告知流量需要进行二次入队。
在本实施方式中，子接口以multiple-level模式绑定HQoS调度策略，父接口以overwrite模式绑定HQoS调度策略。其中，业务流量以子接口标识在第一映射关系中中查找对应的第一调度队列，通过子接口完成第一次调度，其中第一映射关系为业务所属用户与队列标识之间的映射关系，保存在ACL表(访问控制列表)中；以父接口标识在ACL表中查找对应的第二调度队列，通过父接口完成第二次调度。
在一些情形下，预先配置第一调度策略，设备根据预先设定的配置将第一调度策略绑定在子接口上，然后根据第一调度策略在各个子接口上挂接队列，其中每一个队列都具有不同的优先级，优先级根据预先配置的第一调度策略来确定。实际运行中，当同一个接口上存在多个业务流量时，会优先转发优先级较高的队列中的业务流量。在这种配置方式下，在对业务流量进行第一调度时，子接口会向业务流量写入二次调度的标记，业务流量会被加入到挂接在内部环回端口上的队列中，当业务流量完成第一次调度后，会通过环回端口转发至下行交换侧接口。
在一些情形下，本实施方式中的第一映射关系为子接口标识与第一调度队列之间的映射关系，第一映射关系保存在访问控制规则ACL表中。对接收到的业务流量进行解析后，首先根据预先所配置第一调度策略下的调度树来确定业务流量通过的子接口，然后根据第一映射关系找到子接口标识在ACL表中所对 应的第一调度队列，如果在ACL表中查找到存在与子接口标识对应的第一调度队列，将业务流量加入第一调度队列。如果在ACL表中不存在到与子接口标识对应的第一调度队列，则跳过对业务流量的第一次调度直接进行第二次调度，执行步骤205，在预设的第二映射关系中查找是否存在与业务流量的子接口标识。
步骤205，在预设的第二映射关系中查找是否存在与业务流量的父接口标识对应的第二调度策略。若在预设的第二映射关系中存在与业务流量的子接口标识对应的第二调度队列，则执行步骤206；若在预设的第二映射关系中不存在与业务流量的子接口标识对应的第二调度队列，则执行步骤208。
步骤206，将业务流量加入业务流量的父接口标识在第二映射关系中对应的第二调度队列。
在一些情形下，本实施方式中的第二映射关系为父接口标识与第二调度队列之间的映射关系，第二映射关系同样保存在访问控制规则ACL表中。当第二次接收到业务流量后，根据预先所配置第二调度策略下的调度树来确定业务流量通过的父接口，然后根据第二映射关系找到父接口标识在ACL表中所对应的第二调度队列，如果在ACL表中查找到存在与父接口标识对应的第二调度队列，将业务流量加入第二调度队列。如果在ACL表中不存在与子接口标识对应的第二调度队列，意味着并没有在预先配置的调度策略中设置业务流量用户属性或业务属性的优先级，则执行步骤208，将业务流量加入默认队列，根据默认队列的优先级来对未完成ACL规则匹配的业务流量进行第二次调度。
步骤207，根据业务流量加入的第二调度队列的优先级发送业务流量。
在一些情形下，在本实施方式中父接口以overwrite模式绑定HQoS调度策略，以父接口标识在ACL表中查找对应的第二调度队列，通过父接口完成第二次调度。在这种配置方式下父接口上绑定预先配置好的第二调度策略(以overwrite模式绑定HQoS调度策略)，网络通讯设备根据绑定的第二调度策略在各个子接口上挂接队列，每一个队列都具有不同的优先级，在实际运行中，当同一个接口上存在多个业务流量时，会优先转发优先级较高的队列中的业务流量。在业务流量经过第二次调度以后，通过下行线路侧发送出去，完成业务流量的整个调度过程。
在一个例子中，本实施方式中的流量调度系统结构如图3所示，包括：
网络处理器NP(Network Process)，用于对下行交换侧接口所接收到的流量进行解析，并根据业务流量的接口标识在ACL表中查找与业务流量的接口标识具有映射关系的队列标识，然后将解析后的业务流量转发给流量管理器TM 1，同时也将队列标识等相关信息发送至流量管理器TM 1。在业务流量完成第一次调度后，TM1通过环回端口将业务流量转发至上行线路侧接口，NP还用于以透传方式将业务流量转发至下行交换侧接口。其中，业务流量第一次调度过程中的转发路径在图中以实线箭头表示，业务流量第二次调度过程中的转发路径在图中以虚线箭头表示。
流量管理器TM1，用于根据NP发送的队列标识将经过NP解析的业务流量加入到相应的队列中，然后根据预设的HQoS策略，为各队列分配不同的优先级，根据各队列的优先级来完成对业务流量的调度以及限速。在第一次流量调度的过程中，业务流量直接根据队列标识加入到挂接在TM环回端口LP上的相应队列中，经过第一次调度后通过LP转发至上行线路侧接口，然后再由NP透传至下行交换侧接口，开始流量的第二次调度。完成第二次调度后，将业务流量通过逻辑端口P2从下行线路侧接口转发出去。
在一个例子中，在NP第一次从下行交换侧接口接收到业务流量并对业务流量进行解析后，若根据业务流量的子接口标识在预设的ACL表中没有查找到与子接口标识具有映射关系的队列标识，则继续根据业务流量的父接口标识在预设的ACL表中查找与父接口标识具有映射关系的队列标识。若根据业务流量的父接口标识在预设的ACL表中没有查找到与父接口标识具有映射关系的队列标识，NP则会将默认队列信息发送至TM1，然后TM1将业务流量加入默认队列中，根据默认队列的优先级来转发业务流量，完成对业务流量的调度。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请第三实施方式涉及一种流量调度方法。第三实施方式与第二实施方式大致相同，主要区别之处在于：在第二实施方式中，在对业务流量进行第一次调度时，根据业务流量的子接口标识在第一映射关系中查找与子接口标识对 应的第一调度队列；在对流量进行第二次调度时，根据业务流量的父接口标识在第二映射关系中查找与父接口标识对应的第二调度队列。而在本申请第三实施方式中，在对业务流量进行第一次调度时，根据业务流量的接口标识在第一映射关系中查找与接口标识对应的第一调度队列，其中业务流量的接口标识为子接口标识与父接口标识的组合；在对流量进行第二次调度时，根据业务流量的IP优先级字段在第二映射关系查找与IP优先级字段对应的第二调度队列。
本申请第三实施方式中的流量调度方法如图4所示，包括：
步骤401，获取数据接收端口接收到的业务流量。
步骤402，在预设的第一映射关系中查找是否存在与业务流量的接口标识对应的第一调度策略，其中，接口标识为业务流量的子接口标识与父接口标识的组合。若在预设的第一映射关系中存在与业务流量的接口标识对应的第一调度队列，则执行步骤403；若在预设的第一映射关系中不存在与业务流量的接口标识对应的第一调度队列，则执行步骤405。
步骤403，将业务流量加入业务流量的接口标识在第一映射关系中对应的第一调度队列。
步骤404，根据业务流量加入的第一调度队列的优先级发送业务流量。
在一些情形下，本实施方式中的ACL表中所保存的第一映射关系为业务流量的子接口标识和与父接口标识的组合与第一调度队列之间的映射关系。第一调度策略以multiple-level模式绑定于父接口的HQoS策略，该HQoS策略基于用户信息来对业务流量的优先级进行区分。步骤402至步骤404与本申请第二实施方式中的步骤202至步骤204相似，其他实施细节已在本申请第二实施方式中进行了具体的说明，在此不再赘述。
步骤405，在预设的第二映射关系中查找与业务流量的IP优先级字段对应的第二调度队列。
在一些情形下，预先在父接口上绑定了QoS-template(基于端口的8个phb调度和限速)调度和限速策略，这种策略基于业务流量报文中的IP优先级字段来对业务流量的优先级进行区分。因此在本实施方式中，第二映射关系为IP优先级字段与第二调度队列之间的映射关系，第二映射关系保存在出向端口表中。在对业务流量进行解析后，需要获取到业务流量中的IP优先级字段，然后根据IP优先级字段在出向端口表中查找业务流量所对应的第二调度队列。由于所有 的流量均需要通过父接口来从逻辑出向端口转发出去，因此这种策略绑定方式可以实现基于端口级的流量调度。
在一个例子中，NP对业务流量进行解析后，根据IP优先级字段在出向端口表中查询到对应的队列标识，然后将业务流量与对应的队列标识同时转发给流量管理器TM1，然后TM1将业务流量加入至相应的队列中，根据队列的优先级来转发业务流量，完成基于端口级的流量调度。
由于第二实施方式与本实施方式可以相互替换，因此第二实施方式中提到的相关技术细节在本实施方式中依然有效，在第二实施方式中所能达到的技术效果在本实施方式中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第二实施方式中。
另外，根据预设的第一调度策略，对业务流量进行第一次调度，包括：根据业务流量的子接口标识，以及预设的子接口标识与第一调度队列的第一映射关系，将业务流量加入业务流量的子接口标识在第一映射关系中对应的第一调度队列；根据业务流量加入的第一调度队列的优先级发送业务流量。实现以业务流量接入的子接口标识为依据选择用户级的调度策略来对业务流量进行第一次调度。
另外，根据预设的第二调度策略，对业务流量进行第二次调度，包括：根据业务流量的父接口标识，以及预设的父接口标识与第二调度队列的第二映射关系，将业务流量加入所述业务流量的父接口标识在第二映射关系中对应的第二调度队列；根据业务流量加入的第二调度队列的优先级发送业务流量。实现以业务流量接入的父接口的标识为依据选择端口级的调度策略来对业务流量进行二次入队后的调度。
另外，根据预设的第一调度策略，对业务流量进行第一次调度，包括：根据业务流量的接口标识，以及预设的接口标识与第一调度队列的第一映射关系，将业务流量加入业务流量的接口标识在第一映射关系中对应的第一调度队列；其中，业务流量的接口标识为子接口标识与父接口标识的组合；根据业务流量加入的第一调度队列的优先级发送业务流量。实现以业务流量接入的子接口与父接口标识的组合为依据选择用户级的调度策略来对业务流量进行第一次调度。
另外，根据预设的第二调度策略，对业务流量进行第二次调度，包括：根 据业务流量的互联网协议IP优先级字段，以及IP优先级字段与第二调度队列的第二映射关系，将业务流量加入业务流量的IP优先级字段在第二映射关系中对应的第二调度队列；根据业务流量加入的第二调度队列的优先级发送业务流量。实现以业务流量的IP优先级字段为依据选择端口级的调度策略来对业务流量进行二次入队后的调度。
本申请第四实施方式涉及一种服务器，如图5所示，包括至少一个处理器501；以及，与至少一个处理器501通信连接的存储器502；其中，存储器502存储有可被至少一个处理器501执行的指令，指令被至少一个处理器501执行，以使至少一个处理器501能够执行第一至第三实施方式中任一实施方式的流量调度方法。
其中，存储器502和处理器501采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器501和存储器502的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器501处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器501。
处理器501负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器502可以被用于存储处理器501在执行操作时所使用的数据。
本申请第五实施方式涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的 介质。
本领域的普通技术人员可以理解，上述各实施方式是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (10)

  1. 一种流量调度方法，包括：
    根据预设的第一调度策略，对业务流量进行第一次调度；其中，所述第一调度策略为用户级的调度策略；
    将经过所述第一次调度后的所述业务流量转发至数据接收端口；
    根据预设的第二调度策略，对经所述第一次调度后的所述业务流量进行第二次调度；其中，所述第二调度策略为端口级的调度策略；
    将所述第二次调度后的业务流量通过数据发送端口进行发送。
  2. 根据权利要求1所述的流量调度方法，其中，
    所述根据预设的第一调度策略，对所述业务流量进行第一次调度，包括：
    根据所述业务流量的子接口标识，以及预设的子接口标识与第一调度队列的第一映射关系，在所述第一映射关系中查找与所述业务流量的子接口标识对应的第一调度队列；以及
    将所述业务流量加入查找到的所述对应的第一调度队列；
    所述将经过所述第一次调度后的所述业务流量转发至所述数据接收端口，包括：根据所述业务流量加入的第一调度队列的优先级发送所述业务流量至所述数据接收端口。
  3. 根据权利要求2所述的流量调度方法，其中，
    所述根据预设的第二调度策略，对所述业务流量进行第二次调度，包括：
    根据所述业务流量的父接口标识，以及预设的父接口标识与第二调度队列的第二映射关系，在所述第二映射关系中查找与所述业务流量的父接口标识对应的第二调度队列；以及
    将所述业务流量加入查找到的所述对应的第二调度队列；
    所述将所述第二次调度后的业务流量通过数据发送端口进行发送，包括：根据所述业务流量加入的第二调度队列的优先级通过数据发送端 口发送所述业务流量。
  4. 根据权利要求3所述的流量调度方法，其中，
    在所述第一映射关系中查找与所述业务流量的子接口标识对应的第一调度队列之后，还包括：若在所述第一映射关系中未查找到与所述业务流量的子接口标识对应的第一调度队列，则执行所述根据预设的第二调度策略，对所述业务流量进行第二次调度；
    在所述第二映射关系中查找与所述业务流量的父接口标识对应的第二调度队列之后，还包括：若在所述第二映射关系中未查找到与所述业务流量的父接口标识对应的第二调度队列，则将所述业务流量加入预设队列；
    所述将所述第二次调度后的业务流量通过数据端口进行发送，包括：根据所述业务流量加入的预设队列的优先级通过数据发送端口发送所述业务流量。
  5. 根据权利要求1所述的流量调度方法，其中，
    所述根据预设的第一调度策略，对所述业务流量进行第一次调度，包括：
    根据所述业务流量的接口标识，以及预设的接口标识与第一调度队列的第一映射关系，在所述第一映射关系中查找与所述业务流量的接口标识对应的第一调度队列；以及
    将所述业务流量加入查找到的所述对应的第一调度队列；其中，所述业务流量的接口标识为子接口标识与父接口标识的组合；
    所述将经过所述第一次调度后的所属业务流量转发至所述数据接收端口，包括：根据所述业务流量加入的第一调度队列的优先级发送所述业务流量至所述数据接收端口。
  6. 根据权利要求5所述的流量调度方法，其中，
    所述根据预设的第二调度策略，对所述业务流量进行第二次调度，包括：根据所述业务流量的互联网协议IP优先级字段，以及IP优先级字 段与第二调度队列的第二映射关系，在所述第二映射关系中查找与所述业务流量的IP优先级字段对应的第二调度队列；
    所述将所述第二次调度后的业务流量通过数据发送端口进行发送，包括：根据所述业务流量加入的第二调度队列的优先级通过数据发送端口发送所述业务流量。
  7. 根据权利要求3所述的流量调度方法，其中，
    在所述第一映射关系中查找与所述业务流量的接口标识对应的第一调度队列之后，还包括：若在所述第一映射关系中未查找到与所述业务流量的接口标识对应的第一调度队列，则执行所述根据预设的第二调度策略，对所述业务流量进行第二次调度；
    所述将所述第二次调度后的业务流量通过数据发送端口进行发送，包括：根据所述业务流量加入的预设队列的优先级通过数据发送端口发送所述业务流量。
  8. 根据权利要求1至7中任一项所述的流量调度方法，其中，所述数据接收端口为下行交换侧接口；所述数据发送端口为下行线路侧接口；
    所述将经过所述第一次调度后的所述业务流量转发至所述数据接收端口，包括：
    将所述经过第一次调度后的所述业务流量通过环回端口转发至上行线路侧接口；以及
    将所述经过第一次调度后的所述业务流量从所述上行线路侧接口以透传方式转发至所述下行交换侧接口。
  9. 一种电子设备，包括：至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至8中任一项所述的流量调度方法。
  10. 一种计算机可读存储介质，存储有计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1至8中任一项所述的流量调度方法。
PCT/CN2020/134650 2019-12-16 2020-12-08 一种流量调度方法、电子设备及存储介质 WO2021121086A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20903344.8A EP4072085A4 (en) 2019-12-16 2020-12-08 Traffic scheduling method, electronic device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911291974.9 2019-12-16
CN201911291974.9A CN112995056B (zh) 2019-12-16 2019-12-16 一种流量调度方法、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2021121086A1 true WO2021121086A1 (zh) 2021-06-24

Family

ID=76343106

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/134650 WO2021121086A1 (zh) 2019-12-16 2020-12-08 一种流量调度方法、电子设备及存储介质

Country Status (3)

Country Link
EP (1) EP4072085A4 (zh)
CN (1) CN112995056B (zh)
WO (1) WO2021121086A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114598647A (zh) * 2022-01-30 2022-06-07 阿里巴巴（中国）有限公司 数据处理方法、系统和存储介质
WO2023092769A1 (zh) * 2021-11-26 2023-06-01 中电信数智科技有限公司 一种网络流量调度综合判定方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2950490A1 (en) * 2013-01-28 2015-12-02 ZTE Corporation Hierarchical service quality scheduling method and apparatus
CN107306232A (zh) * 2016-04-22 2017-10-31 华为技术有限公司 网络设备、控制器、队列管理方法及流量管理芯片
CN107483361A (zh) * 2016-06-08 2017-12-15 中兴通讯股份有限公司 一种调度模型构建方法和装置
CN107872403A (zh) * 2017-11-10 2018-04-03 西安电子科技大学 一种实现层次化QoS的五级队列调度装置及方法
WO2018188487A1 (zh) * 2017-04-12 2018-10-18 中兴通讯股份有限公司 一种HQoS资源调度方法、设备和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348750B (zh) * 2013-07-31 2019-07-26 中兴通讯股份有限公司 OpenFlow网络中QoS的实现方法及装置
CN104348751B (zh) * 2013-07-31 2019-03-12 中兴通讯股份有限公司 虚拟输出队列授权管理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2950490A1 (en) * 2013-01-28 2015-12-02 ZTE Corporation Hierarchical service quality scheduling method and apparatus
CN107306232A (zh) * 2016-04-22 2017-10-31 华为技术有限公司 网络设备、控制器、队列管理方法及流量管理芯片
CN107483361A (zh) * 2016-06-08 2017-12-15 中兴通讯股份有限公司 一种调度模型构建方法和装置
WO2018188487A1 (zh) * 2017-04-12 2018-10-18 中兴通讯股份有限公司 一种HQoS资源调度方法、设备和系统
CN107872403A (zh) * 2017-11-10 2018-04-03 西安电子科技大学 一种实现层次化QoS的五级队列调度装置及方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023092769A1 (zh) * 2021-11-26 2023-06-01 中电信数智科技有限公司 一种网络流量调度综合判定方法及系统
CN114598647A (zh) * 2022-01-30 2022-06-07 阿里巴巴（中国）有限公司 数据处理方法、系统和存储介质

Also Published As

Publication number Publication date
EP4072085A1 (en) 2022-10-12
EP4072085A4 (en) 2023-06-28
CN112995056B (zh) 2023-09-15
CN112995056A (zh) 2021-06-18

Similar Documents

Publication Publication Date Title
US10003540B2 (en) Flow forwarding method, device, and system
US8705363B2 (en) Packet scheduling method and apparatus
EP2926513B1 (en) Packet prioritization in a software-defined network implementing openflow
US6892309B2 (en) Controlling usage of network resources by a user at the user's entry point to a communications network based on an identity of the user
EP2541866A1 (en) Management schemes for filter sets
Tsuzaki et al. Reactive configuration updating for intent-based networking
US20030152067A1 (en) Controlling concurrent usage of network resources by multiple users at an entry point to a communications network based on identities of the users
EP2362589B1 (en) Priority and source aware packet memory reservation and flow control
WO2015074453A1 (zh) 数据流转发路由的控制方法及装置
WO2021121086A1 (zh) 一种流量调度方法、电子设备及存储介质
CN112583636B (zh) 一种政务网络切片的构造方法、电子设备和存储介质
US7855972B2 (en) Creating, modifying and storing service abstractions and role abstractions representing one or more packet rules
CN106453138A (zh) 一种报文处理方法和装置
WO2021098425A1 (zh) 配置业务的服务质量策略方法、装置和计算设备
WO2021057436A1 (zh) 带宽限速的方法及装置
RU2602333C2 (ru) Сетевая система, способ обработки пакетов и носитель записи
US9137030B1 (en) Multicast queueing in a network switch
WO2020248996A1 (zh) QoS处理及控制方法及网络接口控制器
Ghanwani et al. A framework for integrated services over shared and switched IEEE 802 LAN technologies
WO2016150020A1 (zh) 基于调度流标识的报文调度方法和装置
CN102377645B (zh) 交换芯片及其实现方法
WO2017211161A1 (zh) 基于软件定义网络的资源管理方法及装置
CN109274601A (zh) 服务质量调度方法及装置
CN112838992B (zh) 报文调度方法及网络设备
WO2021174236A2 (en) In-band signaling for latency guarantee service (lgs)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20903344

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020903344

Country of ref document: EP

Effective date: 20220718