CN111756647B - HQoS service transmission method, device and system - Google Patents
HQoS service transmission method, device and system Download PDFInfo
- Publication number
- CN111756647B CN111756647B CN201910255967.7A CN201910255967A CN111756647B CN 111756647 B CN111756647 B CN 111756647B CN 201910255967 A CN201910255967 A CN 201910255967A CN 111756647 B CN111756647 B CN 111756647B
- Authority
- CN
- China
- Prior art keywords
- service
- hqos
- management engine
- flow management
- sub
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
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/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- 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/2416—Real-time traffic
Abstract
The embodiment of the application provides a method, a device and a system for transmitting HQoS (quality of service) service. The method comprises the following steps: when the processing capacity of the first flow management engine for processing the first qos traffic does not meet the requirements of the first qos traffic; forwarding a first HQoS sub-service included in the first HQoS service to a second flow management engine for processing a second HQoS service for processing; the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service. The application solves the problems of traffic congestion and unbalanced resource allocation of the traffic management engine caused by unbalanced resource allocation of the traffic management engine. The application obtains higher HQoS service processing capability and simultaneously avoids the problem that a flow management engine is idle.
Description
Technical Field
The present application relates to the field of communications, and in particular, to a method, an apparatus, and a system for transmitting an HQoS service.
Background
With the expansion of the scale of users and the increase of service types, network communication equipment is required to be capable of further refining and distinguishing service traffic, and uniformly managing and hierarchically scheduling transmission objects such as multiple users, multiple services, multiple traffic and the like. Multi-queue techniques may be used to achieve rich layered quality of service (Hierarchical Quality of Service, abbreviated as HQoS), such as traffic limiting, congestion avoidance, traffic shaping, queue scheduling, etc., where queue capacity is an important indicator of providing fine-grained user traffic services.
A general network processor (Network Processor, abbreviated as a network processor) integrates a dedicated traffic management engine (Traffic Management, abbreviated as a traffic management engine), and fig. 1 lists a traditional architecture diagram for qos traffic transmission, including a line side interface, a network processor, a traffic management engine, and a switch side interface, where the line side interface interfaces with an external panel port of a single board, the switch side interface interfaces with an internal backplane switching network, and two mutually independent traffic management engines are built in to implement an ingress qos traffic processing function and an egress qos traffic processing function respectively. The specific service flow forwarding process is described as follows:
the user's HQoS business flow is received from the line side interface, then the network processor carries on the up-going analysis process, for the HQoS business which needs to be done up-going, the access control list rule is searched and matched, the network processor carries the information such as the flow queue number after up-going process, and transmits to the up-going flow management engine, the up-going flow management engine carries on the enqueue process according to the flow queue number, and the up-going flow management engine caches and dispatches the message to realize the up-going HQoS business, then the up-going flow management engine searches the port mapping table according to the logic port which the flow queue is hung, the actual outlet interface is the exchange side interface, the dequeue operation is completed.
In general, the two engines of the uplink flow management engine and the downlink flow management engine may be designed completely symmetrically, the number of resources such as queues and schedulers is the same, the supported HQoS service capacity is the same, the traditional HQoS service allocates the hardware resources of the flow management engine completely according to the direction of the HQoS service, the uplink flow management engine is completely applied to the incoming HQoS service, the downlink flow management engine is completely applied to the outgoing HQoS service, the incoming and outgoing HQoS services are respectively deployed on different flow management engine engines, and the mutual independence and the mutual influence are avoided.
In the practical application scenario, the demands of users for the ingress and egress qos services are likely to be different, the users may deploy a large number of ingress qos services on the switch-side interface, while only a small number of ingress qos services are deployed on the line-side interface, and the large number of ingress qos services may consume all resources on the downstream traffic management engine, so that the users cannot continue to deploy the egress qos services on the egress port, and the resources of the upstream traffic management engine are also abundant. This traditional qos traffic transmission scheme of symmetrical design limits the flexibility of the user.
Disclosure of Invention
The application provides a method and a device for service transmission, which at least solve the problem of unbalanced resource allocation of a flow management engine.
According to an aspect of an embodiment of the present application, there is provided a method for transmitting an HQoS service, including: and when the processing capacity of a first flow management engine for processing the first HQoS service does not meet the requirement of the first HQoS service, forwarding a first HQoS sub-service included in the first HQoS service to a second flow management engine for processing a second HQoS service for processing, wherein the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first service.
Optionally, forwarding the first qos sub-service included in the first qos service to a second flow management engine for processing the second qos service for processing, including: the network processor forwards the first HQoS sub-service to the second flow management engine according to access control information, wherein the access control information indicates that a target flow management engine of the first HQoS sub-service is the second flow management engine.
Optionally, forwarding the first qos sub-service included in the first qos service to a second flow management engine for processing the second qos service for processing, and further including: after the second flow management engine receives the first HQoS sub-service, the first HQoS sub-service is accessed into a first flow queue corresponding to the first flow queue identifier for processing according to the first flow queue identifier carried on the first HQoS sub-service, wherein the first flow queue identifier is encapsulated on the first HQoS sub-service by a network processor according to access control information, and the access control information indicates that a target flow queue of the first HQoS sub-service is the first flow queue.
Optionally, the second flow management engine outputs the processed first qos sub-service to an egress interface of the first service, including: the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first service from a first logic port in the second flow management engine according to port mapping information, wherein the port mapping information indicates that the output interface mapped by the first logic port is the output interface of the first service.
Optionally, the output interface of the first qos service has a hardware channel connected to the first flow management engine, and also has a hardware channel connected to the second flow management engine.
According to another aspect of an embodiment of the present application, there is provided an apparatus for transmitting qos traffic, including a first traffic engine for processing first qos traffic, and a second traffic management engine for processing second qos traffic, wherein: when the processing capacity of the first flow management engine does not meet the requirement of the first service, the second flow management engine receives and processes a first HQoS sub-service included in the first HQoS service; the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first service.
Optionally, the second flow management engine receives and processes a first qos sub-service included in the first qos service, including: the first HQoS sub-service is forwarded by the network processor according to access control information, wherein the access control information indicates that a target traffic management engine of the first HQoS sub-service is the second traffic management engine.
Optionally, the second flow management engine receives and processes a first qos sub-service included in the first qos service, and further includes: after the second flow management engine receives the first HQoS sub-service, the first HQoS sub-service is accessed into a first flow queue corresponding to the first flow queue identifier for processing according to the first flow queue identifier carried on the first HQoS sub-service, wherein the first flow queue identifier is encapsulated on the first HQoS sub-service by a network processor according to access control information, and the access control information indicates that a target flow queue of the first HQoS sub-service is the first flow queue.
Optionally, the second flow management engine outputs the processed first qos sub-service to an egress interface of the first qos service, wherein: the second flow management engine outputs the processed first HQoS sub-service from a first logic port in the second flow management engine to an output interface of the first HQoS service according to port mapping information, wherein the port mapping information indicates that the output interface mapped by the first logic port is the output interface of the first HQoS service.
According to another aspect of an embodiment of the present application, there is provided a system for qos traffic transmission, including a first flow management engine, a second flow management engine, wherein: when the processing capability of the first flow management engine for processing the first qos traffic does not meet the requirement of the first qos traffic, the network processor forwards the first qos sub-traffic to the second flow management engine according to access control information, wherein the access control information indicates that the target flow management engine of the first qos sub-traffic is the second flow management engine; the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service.
According to the application, when the residual resources of the first flow management engine are insufficient, the two flow management engines borrow each other's hardware resources, so that the effect of flexibly calling the flow management engines is achieved, and higher service processing capacity is realized.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
fig. 1 is a schematic structural diagram of a conventional HQoS service transmission apparatus;
fig. 2 is a schematic structural diagram of an HQoS traffic transmission system according to an embodiment of the present application;
fig. 3 is a flowchart of a method for transmitting an HQoS service according to an embodiment of the present application;
Detailed Description
Starting from the current common HQoS service transmission method, the uplink and downlink traffic management engines have the same data processing capacity, but because of the difference of the uplink and downlink traffic, one traffic management engine is overloaded, and the other traffic management engine is idle. According to the embodiment of the application, the proper flow management engine is reasonably called according to the actual downlink flow, so that the service transmission capacity is improved, and the flow management engine resource is more reasonably utilized.
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.
The embodiment provides a method for transmitting HQoS service, which comprises the following steps: and when the processing capacity of the first flow management engine for processing the first HQoS service does not meet the requirement of the first HQoS service, forwarding the first HQoS sub-service included in the first HQoS service to a second flow management engine for processing the second HQoS service for processing, wherein the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first service.
According to the embodiment, when the residual resources of the first flow management engine are insufficient, the two flow management engines borrow each other's hardware resources, so that the effect of flexibly calling the flow management engines is achieved, and higher service processing capacity is realized.
Optionally, forwarding the first qos sub-service included in the first qos service to a second flow management engine for processing the second qos service for processing, including: the network processor forwards the first HQoS sub-service to the second flow management engine according to the access control information, wherein the access control information indicates that the target flow management engine of the first HQoS sub-service is the second flow management engine.
Optionally, forwarding the first qos sub-service included in the first qos service to a second flow management engine for processing the second qos service for processing, and further including: after receiving the first HQoS sub-service, the second flow management engine accesses the first HQoS sub-service into a first flow queue corresponding to the first flow queue identifier for processing according to the first flow queue identifier carried on the first HQoS sub-service, wherein the first flow queue identifier is packaged on the first HQoS sub-service by the network processor according to access control information, and the access control information indicates that a target flow queue of the first HQoS sub-service is the first flow queue.
Optionally, the second flow management engine outputs the processed first qos sub-traffic to an egress interface of the first traffic, including: the second flow management engine outputs the processed first HQoS sub-service from the first logic port in the second flow management engine to the outlet interface of the first service according to the port mapping information, wherein the port mapping information indicates that the outlet interface mapped by the first logic port is the outlet interface of the first service.
Optionally, the egress interface of the first qos traffic has a hardware channel connected to the first flow management engine and also has a hardware channel connected to the second flow management engine.
The embodiment provides an apparatus for transmitting HQoS traffic, including a first traffic engine for processing first HQoS traffic, and a second traffic management engine for processing second HQoS traffic, where: when the processing capacity of the first flow management engine does not meet the requirement of the first service, the second flow management engine receives and processes the first HQoS sub-service included in the first HQoS service; the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first service.
Optionally, the second flow management engine receives and processes a first qos sub-service included in the first qos service, including: the first HQoS sub-service is forwarded by the network processor according to access control information, wherein the access control information indicates that a target traffic management engine of the first HQoS sub-service is a second traffic management engine.
Optionally, the second flow management engine receives and processes a first qos sub-service included in the first qos service, and further includes: after receiving the first HQoS sub-service, the second flow management engine accesses the first HQoS sub-service into a first flow queue corresponding to the first flow queue identifier for processing according to the first flow queue identifier carried on the first HQoS sub-service, wherein the first flow queue identifier is packaged on the first HQoS sub-service by the network processor according to access control information, and the access control information indicates that a target flow queue of the first HQoS sub-service is the first flow queue.
Optionally, the second flow management engine outputs the processed first qos sub-traffic to an egress interface of the first qos traffic, wherein: the second flow management engine outputs the processed first HQoS sub-service from the first logic port in the second flow management engine to the output interface of the first HQoS service according to the port mapping information, wherein the port mapping information indicates that the output interface mapped by the first logic port is the output interface of the first HQoS service.
The embodiment provides a system for transmitting HQoS service, which comprises a first flow management engine and a second flow management engine, wherein: when the processing capacity of the first flow management engine for processing the first HQoS service does not meet the requirement of the first HQoS service, the network processor forwards the first HQoS sub-service to the second flow management engine according to the access control information, wherein the access control information indicates that the target flow management engine of the first HQoS sub-service is the second flow management engine; the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service.
The application will be described in detail below with reference to the drawings in connection with specific embodiments. The embodiment provides a system for transmitting an HQoS service, fig. 2 is a schematic structural diagram of the HQoS service transmission system according to the embodiment of the present application, and as shown in fig. 2, the system operates as follows:
the flow of the upstream qos traffic (corresponding to the second qos traffic in the above embodiment) and the downstream qos traffic (corresponding to the first qos traffic in the above embodiment) analysis processing is different for the network processor NP. For the network processor, the difference between the HQoS services is not perceived, but the HQoS services are enqueued, processed and output according to the flow queue mark carried by the HQoS services.
When the resources of TM0 (corresponding to the first flow management engine in the above embodiment) do not meet the requirements of the downlink qos service, the remaining resources of TM1 (corresponding to the second flow management engine in the above embodiment) are enough to support the requirements of the uplink qos service, and the remaining resources of TM1 are enough to meet the resources to be borrowed by the downlink qos service, at this time, TM0 borrows all the hardware resources required by the downlink qos service to TM1 (corresponding to the flow management engine in the above embodiment), including a logical port, a scheduler, a shaper, and a queue.
The NP (corresponding to the network processor in the above embodiment) encapsulates the QID (corresponding to the flow queue identification in the above embodiment) into the downstream sub-traffic according to the access control list ACL information and forwards it to TM1. The first qos sub-service applies to an unused logical port P1 and a queue Q1 on TM1, TM1 hangs the queue Q1 on the logical port P1, and then maps the logical port P1 to the line side interface A2 through a mapping relationship between the logical port P1 and the line side interface A2 (corresponding to the first qos service egress interface in the above embodiment). After the TM1 processes the downlink qos service, the downlink qos service is output to the line side interface A2 through the logical port P1.
Further explaining the access control information, the access control information comprises borrowable TM number information, stream queue number and corresponding relation between the two, the access control information is used for the NP to search and match with the HQoS service stream, and the forwarding destination address of the HQoS traffic is identified.
As will be further explained with respect to the mapping relationship,
the embodiment of the application also provides a method for configuring the HQoS service transmission, which comprises the following steps:
s101: configuring downstream HQoS traffic (corresponding to the first HQoS traffic in the above embodiment) on the line-side outgoing interface (corresponding to the first HQoS traffic outgoing interface in the above embodiment);
s102, a network processor analyzes a downlink HQoS flow classification rule and analyzes the number of resources such as flow queues and the like required by downlink HQoS service configuration;
s103: checking whether the current TM0 (equivalent to the first flow management engine in the above embodiment) remaining resources satisfy the resources required for the downlink qos service, satisfying the transition S104, failing to satisfy the transition S107;
s104: using TM0 resource to complete the hanging configuration of the downlink HQoS service queue;
s105: mapping a logic port hung on a TM0 queue to a line side-out interface;
s106: writing the downlink HQoS flow classification rule and the TM0 flow queue into an access control information list, and turning to S111;
s107: checking whether the current TM1 (equivalent to the second flow management engine in the above embodiment) remaining resources satisfy the resources required for the downlink qos service, satisfying the transition S108, and failing to satisfy the transition S111;
s108: using TM1 resources to complete the hooking configuration of the downlink qos service queue (which is equivalent to that after the second flow management engine in the above embodiment receives the first qos sub-service, the second flow management engine accesses the first qos sub-service into the first flow queue corresponding to the first flow queue identifier according to the first flow queue identifier carried on the first qos sub-service to process the first qos sub-service);
s109: mapping a logic port hung on a TM1 queue to a line side-out interface;
s110: writing the downlink HQoS flow classification rule and the TM1 flow queue into an access control information list, and turning to S111;
and S111, completing configuration.
The embodiment discloses a service configuration method for processing HQoS service by a downlink flow management engine by using an uplink flow management engine, which has the effect of fully utilizing the resources of the flow management engine to process the service, improves the processing efficiency of the HQoS service and avoids possible blockage in the processing of the HQoS service.
In summary, the foregoing embodiments and preferred embodiments of the present application provide a method for transmitting an HQoS service, which can achieve higher service processing capability, effectively avoid service blocking, and simultaneously can more reasonably utilize resources of a traffic management engine.
It will be apparent to those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, or they may alternatively be implemented in program code executable by computing devices, such that they may be stored in a memory device for execution by the computing devices, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.
The above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (8)
1. A method for transmitting HQoS service is characterized in that:
when the processing capacity of a first flow management engine for processing first HQoS service does not meet the requirement of the first HQoS service, forwarding a first HQoS sub-service included in the first HQoS service to a second flow management engine for processing second HQoS service for processing, wherein the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service; the first flow management engine is a downlink flow management engine, and the second flow management engine is an uplink flow management engine;
wherein forwarding the first qos sub-service included in the first qos service to a second flow management engine for processing the second qos service for processing, includes:
the network processor forwards the first HQoS sub-service to the second flow management engine according to access control information, wherein the access control information indicates that a target flow management engine of the first HQoS sub-service is the second flow management engine.
2. The method of claim 1, forwarding a first qos sub-service included in the first qos service to a second flow management engine for processing a second qos service, further comprising:
after the second flow management engine receives the first HQoS sub-service, the first HQoS sub-service is accessed into a first flow queue corresponding to the first flow queue identifier for processing according to the first flow queue identifier carried on the first HQoS sub-service, wherein the first flow queue identifier is encapsulated on the first HQoS sub-service by a network processor according to access control information, and the access control information indicates that a target flow queue of the first HQoS sub-service is the first flow queue.
3. The method of claim 1, the second flow management engine outputting the processed first qos sub-traffic to an egress interface of the first qos traffic, comprising:
the second flow management engine outputs the processed first HQoS sub-service from a first logic port in the second flow management engine to an output interface of the first HQoS service according to port mapping information, wherein the port mapping information indicates that the output interface mapped by the first logic port is the output interface of the first HQoS service.
4. The method of claim 1, wherein:
the output interface of the first HQoS service has a hardware channel connected with the first flow management engine and also has a hardware channel connected with the second flow management engine.
5. An apparatus for qos traffic transmission comprising a first traffic engine for handling first qos traffic, a second traffic management engine for handling second qos traffic, characterized by:
when the processing capacity of the first flow management engine does not meet the requirement of the first HQoS service, the second flow management engine receives and processes a first HQoS sub-service included in the first HQoS service; the first flow management engine is a downlink flow management engine, and the second flow management engine is an uplink flow management engine;
the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service
Wherein the second flow management engine receives and processes the first qos sub-service included in the first qos service, comprising: the first HQoS sub-service is forwarded by the network processor according to access control information, wherein the access control information indicates that a target traffic management engine of the first HQoS sub-service is the second traffic management engine.
6. The apparatus of claim 5, the second flow management engine to receive and process the first qos sub-service included with the first qos service, further comprising:
after the second flow management engine receives the first HQoS sub-service, the first HQoS sub-service is accessed into a first flow queue corresponding to the first flow queue identifier for processing according to the first flow queue identifier carried on the first HQoS sub-service, wherein the first flow queue identifier is encapsulated on the first HQoS sub-service by a network processor according to access control information, and the access control information indicates that a target flow queue of the first HQoS sub-service is the first flow queue.
7. The apparatus of claim 5, the second flow management engine to output the processed first qos sub-traffic to an egress interface of the first qos traffic, wherein:
the second flow management engine outputs the processed first HQoS sub-service from a first logic port in the second flow management engine to an output interface of the first HQoS service according to port mapping information, wherein the port mapping information indicates that the output interface mapped by the first logic port is the output interface of the first HQoS service.
8. A system for HQoS traffic transport, comprising a network processor, a first flow management engine, a second flow management engine, wherein:
when the processing capability of the first flow management engine for processing the first qos traffic does not meet the requirement of the first qos traffic, the network processor forwards the first qos sub-traffic to the second flow management engine according to access control information, wherein the access control information indicates that the target flow management engine of the first qos sub-traffic is the second flow management engine; the first flow management engine is a downstream flow management engine, and the second flow management engine is an upstream flow management engine;
the second flow management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910255967.7A CN111756647B (en) | 2019-03-29 | 2019-03-29 | HQoS service transmission method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910255967.7A CN111756647B (en) | 2019-03-29 | 2019-03-29 | HQoS service transmission method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111756647A CN111756647A (en) | 2020-10-09 |
| CN111756647B true CN111756647B (en) | 2023-09-12 |
Family
ID=72672631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910255967.7A Active CN111756647B (en) | 2019-03-29 | 2019-03-29 | HQoS service transmission method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111756647B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1787489A (en) * | 2005-12-22 | 2006-06-14 | 港湾网络有限公司 | Method for average distributing interface flow at multi network processor engines |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE60003518T2 (en) * | 2000-02-08 | 2004-04-22 | Lucent Technologies Inc. | Guaranteed service type in a package-based system |
| US20060136878A1 (en) * | 2004-12-17 | 2006-06-22 | Arun Raghunath | Method and apparatus for enabling compiler and run-time optimizations for data flow applications in multi-core architectures |
| US7609707B2 (en) * | 2005-08-31 | 2009-10-27 | Alcatel Lucent | Communication traffic management systems and methods |
| CN103346950B (en) * | 2013-07-29 | 2016-05-25 | 北京傲天动联技术股份有限公司 | Between a kind of rack wireless controller customer service plate, method and device are shared in load equally |
| CN103929492B (en) * | 2014-04-28 | 2017-08-29 | 华为技术有限公司 | Business chain load-balancing method and its device, system |
| US10021172B2 (en) * | 2015-09-23 | 2018-07-10 | Nec Corporation | Software driven long-term-evolution core network for mobile access |
-
2019
- 2019-03-29 CN CN201910255967.7A patent/CN111756647B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1787489A (en) * | 2005-12-22 | 2006-06-14 | 港湾网络有限公司 | Method for average distributing interface flow at multi network processor engines |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111756647A (en) | 2020-10-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101199168B (en) | Method, device and system for monitoring a queue for a communication link | |
| US7701849B1 (en) | Flow-based queuing of network traffic | |
| CN1981484B (en) | Hierarchal scheduler with multiple scheduling lanes and scheduling method | |
| US7027457B1 (en) | Method and apparatus for providing differentiated Quality-of-Service guarantees in scalable packet switches | |
| US20080256455A1 (en) | Method for Defining the Physical Configuration of a Communication System | |
| US20230275832A1 (en) | Networking processor and network device | |
| US20070171917A1 (en) | Apparatus and method for implementing multiple high speed switching fabrics in an ethernet ring topology | |
| US20100057953A1 (en) | Data processing system | |
| CN102231697A (en) | Bandwidth dispatching method of message queues as well as message reporting method and device | |
| US7483377B2 (en) | Method and apparatus to prioritize network traffic | |
| CN112084027B (en) | Network-on-chip data transmission method, device, network-on-chip, equipment and medium | |
| US7088719B2 (en) | Processor with packet processing order maintenance based on packet flow identifiers | |
| US7477636B2 (en) | Processor with scheduler architecture supporting multiple distinct scheduling algorithms | |
| US20060251071A1 (en) | Apparatus and method for IP packet processing using network processor | |
| US8218440B2 (en) | High speed transmission protocol | |
| KR100916835B1 (en) | METHOD OF PROCESSING PACKETS PER-FLOW USING NETWORK PROCESSOR IN DiffServ-over-MPLS | |
| CN109286564B (en) | Message forwarding method and device | |
| US7953008B2 (en) | Cell copy count hazard detection | |
| CN114374651A (en) | Transport flow control method, network on chip, electronic device, and storage medium | |
| CN115622952A (en) | Resource scheduling method, device, equipment and computer readable storage medium | |
| US7990873B2 (en) | Traffic shaping via internal loopback | |
| CN111756647B (en) | HQoS service transmission method, device and system | |
| US8670454B2 (en) | Dynamic assignment of data to switch-ingress buffers | |
| US9246826B2 (en) | Integrated circuit arrangement for buffering service requests | |
| US20220060392A1 (en) | Network Management System and Method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |