CN111756647A - HQoS service transmission method, device and system - Google Patents
HQoS service transmission method, device and system Download PDFInfo
- Publication number
- CN111756647A CN111756647A CN201910255967.7A CN201910255967A CN111756647A CN 111756647 A CN111756647 A CN 111756647A CN 201910255967 A CN201910255967 A CN 201910255967A CN 111756647 A CN111756647 A CN 111756647A
- Authority
- CN
- China
- Prior art keywords
- hqos
- service
- management engine
- sub
- traffic management
- 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.)
- Granted
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/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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a method, a device and a system for HQoS service transmission. The method comprises the following steps: when the processing capacity of a first traffic 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 by the first HQoS service to a second traffic management engine for processing a second HQoS service; and the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service. The invention solves the problems of flow congestion and unbalanced flow management engine resource distribution caused by unbalanced flow management engine resource distribution. The invention obtains higher HQoS service processing capacity and avoids the problem that a flow management engine is idle.
Description
Technical Field
The invention relates to the field of communication, in particular to a method, a device and a system for HQoS service transmission.
Background
With the expansion of user scale and the increase of service types, network communication equipment is required to not only further refine and differentiate service flows, but also perform unified management and hierarchical scheduling on transmission objects such as multiple users, multiple services, multiple flows and the like. The multi-queue technology can be used for realizing rich Hierarchical Quality of Service (HQoS), such as traffic speed limitation, congestion avoidance, traffic shaping, queue scheduling, and the like, where queue capacity is an important index for providing a Service that refines user traffic.
A general Network Processor (Network Processor, abbreviated as a Network Processor) integrates a dedicated Traffic Management engine (Traffic Management engine), and fig. 1 shows an architecture diagram of conventional HQoS service transmission, which includes a line side interface, a Network Processor, a Traffic Management engine, and a switch side interface, where the line side interface is connected to a single board external panel port, the switch side interface is connected to an internal backplane switching Network, and two independent Traffic Management engines are built in to implement ingress and egress HQoS service processing functions, respectively. The specific service flow forwarding process is described as follows:
the method comprises the steps that HQoS service flow of a user is received from a line side interface and then is subjected to uplink analysis processing by a network processor, the HQoS service required to be processed in an uplink mode can be searched and matched with rules of an access control list, the network processor can carry information such as a flow queue number after the uplink processing is finished and forwards the information to an uplink flow management engine, the uplink flow management engine performs enqueue processing according to the flow queue number and caches and schedules messages to achieve the HQoS service in the uplink mode, then the uplink flow management engine searches a port mapping table according to a logical port connected with the flow queue, and obtains an actual output interface as a switching side interface to complete dequeue operation.
Generally, an uplink traffic management engine and a downlink traffic management engine may be designed in a completely symmetric manner, the number of resources such as queues and schedulers is the same, the capacities of supported HQoS services are the same, the hardware resources of the traffic management engine are completely allocated to the conventional HQoS service according to the direction of the HQoS service, the uplink traffic management engine is completely applied to the incoming HQoS service, the downlink traffic management engine is completely applied to the outgoing HQoS service, and the incoming and outgoing HQoS services are respectively deployed on different traffic management engine, and are independent from each other and do not affect each other.
In an actual application scenario, the demands of users for incoming and outgoing HQoS services are likely to be different, the users may deploy a large amount of outgoing HQoS services on an exchange-side interface, while only a small amount of incoming and outgoing HQoS services are deployed on a line-side interface, and the large amount of outgoing HQoS services may consume resources on a downlink traffic management engine, so that the users cannot continue to deploy the outgoing HQoS services on an outgoing port, and resources of the uplink traffic management engine are abundant. The traditional HQoS service transmission scheme of this symmetrical design limits the flexibility of users.
Disclosure of Invention
The invention provides a method and a device for service transmission, which are used for at least solving the problem of unbalanced resource allocation of a traffic management engine.
According to an aspect of the embodiments of the present invention, a method for HQoS service transmission is provided, including: when the processing capacity of a first traffic management engine for processing a 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 traffic management engine for processing a second HQoS service, wherein the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first service.
Optionally, forwarding the first HQoS sub-service included in the first HQoS service to a second traffic management engine for processing a second HQoS service, where the forwarding includes: and forwarding the first HQoS sub-service to the second traffic management engine 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, forwarding the first HQoS sub-service included in the first HQoS service to a second traffic management engine for processing a second HQoS service, further comprising: and 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 according to the first flow queue identifier carried on the first HQoS sub service for processing, wherein the first flow queue identifier is encapsulated by a network processor on the first HQoS sub service 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 outputting, by the second traffic management engine, the processed first HQoS sub-service to an output interface of the first service includes: and the second traffic management engine outputs the processed first HQoS sub-service from a first logical port in the second traffic management engine to an outgoing interface of the first service according to port mapping information, where the port mapping information indicates that the outgoing interface mapped by the first logical port is the outgoing interface of the first service.
Optionally, a hardware channel connected to the first traffic management engine exists at an output interface of the first HQoS service, and a hardware channel connected to the second traffic management engine also exists.
According to another aspect of the embodiments of the present invention, there is provided an apparatus for HQoS service transmission, including a first traffic engine for processing a first HQoS service, and a second traffic management engine for processing a second HQoS service, wherein: when the processing capacity of the first traffic management engine does not meet the requirement of a first service, the second traffic management engine receives and processes a first HQoS sub-service included by the first HQoS service; and the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first service.
Optionally, the receiving and processing, by the second traffic management engine, the first HQoS sub-service included in the first HQoS service includes: the first HQoS sub-service is forwarded by the network processor according to access control information, where 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 traffic management engine receives and processes a first HQoS sub-service included in the first HQoS service, and further includes: and 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 according to the first flow queue identifier carried on the first HQoS sub service for processing, wherein the first flow queue identifier is encapsulated by a network processor on the first HQoS sub service 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 traffic management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service, where: and the second traffic management engine outputs the processed first hQoS sub-service from a first logic port in the second traffic 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 the embodiments of the present invention, there is provided a system for HQoS service transmission, including a first traffic management engine and a second traffic management engine, wherein: when the processing capacity of the first traffic management engine for processing a 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 traffic management engine 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; and the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service.
According to the invention, when the first traffic management engine has insufficient residual resources, the two traffic management engines mutually borrow the hardware resources of each other, so that the effect of flexibly calling the traffic 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 invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. 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 service transmission system according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of an HQoS service transmission method according to an embodiment of the present invention;
Detailed Description
From the HQoS service transmission method commonly used at present, the uplink and downlink traffic management engines have the same data processing capability, but due to the difference between the sizes of the uplink and downlink traffic, a certain traffic management engine is overloaded, and another traffic management engine is idle. The embodiment of the invention reasonably calls the appropriate flow management engine according to the actual uplink and downlink flow, thereby improving the service transmission capability and more reasonably utilizing the flow management engine resources.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
The embodiment provides a method for transmitting an HQoS service, which includes: when the processing capacity of a first traffic 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 by the first HQoS service to a second traffic management engine for processing a second HQoS service, wherein the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first service.
By the embodiment, when the first traffic management engine has insufficient residual resources, the two traffic management engines mutually borrow the hardware resources of each other, so that the effect of flexibly calling the traffic management engines is achieved, and higher service processing capacity is realized.
Optionally, forwarding the first HQoS sub-service included in the first HQoS service to a second traffic management engine for processing a second HQoS service, where the forwarding includes: and the network processor forwards the first HQoS sub-service to a second traffic management engine according to the 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, forwarding the first HQoS sub-service included in the first HQoS service to a second traffic management engine for processing a second HQoS service, further comprising: after receiving the first HQoS sub-service, the second traffic management engine accesses the first HQoS sub-service into a first traffic queue corresponding to the first traffic queue identifier according to the first traffic queue identifier carried on the first HQoS sub-service for processing, wherein the first traffic queue identifier is encapsulated by the network processor on the first HQoS sub-service according to the access control information, and the access control information indicates that a target traffic queue of the first HQoS sub-service is the first traffic queue.
Optionally, the outputting, by the second traffic management engine, the processed first HQoS sub-service to the output interface of the first service includes: and the second traffic management engine outputs the processed first HQoS sub-service from a first logic port in the second traffic management engine to an output interface of the first 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 service.
Optionally, a hardware channel connected to the first traffic management engine exists at an output interface of the first HQoS service, and a hardware channel connected to the second traffic management engine also exists.
The embodiment provides a device for transmitting HQoS services, which includes a first traffic engine for processing a first HQoS service, and a second traffic management engine for processing a second HQoS service, and is characterized in that: when the processing capacity of the first traffic management engine does not meet the requirement of the first service, the second traffic management engine receives and processes a first HQoS sub-service included by the first HQoS service; and the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first service.
Optionally, the receiving and processing, by the second traffic management engine, the first HQoS sub-service included in the first HQoS service includes: the first HQoS sub-service is forwarded by the network processor according to the 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 traffic management engine receives and processes a first HQoS sub-service included in the first HQoS service, and further includes: after receiving the first HQoS sub-service, the second traffic management engine accesses the first HQoS sub-service into a first traffic queue corresponding to the first traffic queue identifier according to the first traffic queue identifier carried on the first HQoS sub-service for processing, wherein the first traffic queue identifier is encapsulated by the network processor on the first HQoS sub-service according to the access control information, and the access control information indicates that a target traffic queue of the first HQoS sub-service is the first traffic queue.
Optionally, the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service, where: and the second traffic management engine outputs the processed first HQoS sub-service from a first logic port in the second traffic management engine to an 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 an HQoS service transmission system, which includes a first traffic management engine and a second traffic management engine, wherein: when the processing capacity of a first traffic 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 a second traffic management engine 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; and the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service.
The present invention will be described in detail below with reference to the accompanying drawings in conjunction with specific embodiments. The present embodiment provides an HQoS service transmission system, and fig. 2 is a schematic structural diagram of an HQoS service transmission system according to an embodiment of the present invention, and as shown in fig. 2, the system operates as follows:
for the network processor NP, the parsing processing flows of the uplink HQoS service (corresponding to the second HQoS service in the foregoing embodiment) and the downlink HQoS service (corresponding to the first HQoS service in the foregoing embodiment) are different. For a network processor, the difference between HQoS services is not sensed, and the HQoS services are just enqueued, processed and output according to flow queue identifiers carried by the HQoS services.
When the resource of the TM0 (corresponding to the first traffic management engine in the above embodiment) does not satisfy the requirement of the downlink HQoS service, the TM1 (corresponding to the second traffic management engine in the above embodiment) has enough remaining resource to bear the requirement of the uplink HQoS service, and the TM1 has enough remaining resource to satisfy the borrowed resource required by the downlink HQoS service, at this time, the TM0 borrows all hardware resources required by the downlink HQoS service, including a logical port, a scheduler, a shaper, and a queue, from the TM1 (corresponding to the traffic management engine in the above embodiment).
The NP (equivalent to the network processor in the above embodiment) encapsulates a QID (equivalent to the flow queue id in the above embodiment) into the downstream sub-traffic according to the access control list ACL information and forwards it to the TM 1. The first HQoS sub-service applies for an unused logical port P1 and queue Q1 on TM1, TM1 hangs queue Q1 on logical port P1, and then maps logical port P1 to line side interface a2 through the mapping relationship between logical port P1 and line side interface a2 (corresponding to the first HQoS service outgoing interface in the above embodiment). After the TM1 processes the downlink HQoS service, the downlink HQoS service is output to the line side interface a2 through the logical port P1.
For further explanation on the access control information, the access control information includes borrowable TM number information, flow queue number and a corresponding relationship between the TM number information and the flow queue number, and the access control information is used by the NP to search and match the HQoS service flow, thereby identifying a forwarding destination address of the HQoS flow.
For a further explanation of the mapping relationship,
the embodiment of the invention also provides a method for configuring HQoS service transmission, which comprises the following steps:
s101: configuring a downlink HQoS service (equivalent to the first HQoS service in the foregoing embodiment) at a line side output interface (equivalent to the first HQoS service output interface in the foregoing embodiment);
s102, the network processor analyzes the classification rule of the downlink HQoS flow and analyzes the number of resources such as flow queues and the like required by the downlink HQoS service configuration;
s103: checking whether the current TM0 (which is equivalent to the first traffic management engine in the above embodiment) residual resources meet the resources required by the downlink HQoS service, and meeting the requirement of transferring to S104 and not meeting the requirement of transferring to S107;
s104: completing hooking configuration of a downlink HQoS service queue by using TM0 resources;
s105: mapping a logic port hooked by a TM0 queue to a line side outgoing interface;
s106: writing the downlink HQoS flow classification rule and the TM0 flow queue into an access control information list, and switching to S111;
s107: checking whether the current TM1 (which is equivalent to the second traffic management engine in the above embodiment) residual resources meet the resources required by the downlink HQoS service, and meeting the requirement of transferring to S108 and not meeting the requirement of transferring to S111;
s108: using TM1 resources to complete hooking configuration of a downlink HQoS service queue (which is equivalent to that after receiving a first HQoS sub-service, a second traffic management engine in the above embodiment accesses the first HQoS sub-service into a first traffic queue corresponding to a first traffic queue identifier carried on the first HQoS sub-service for processing);
s109: mapping a logic port hooked by a TM1 queue to a line side outgoing interface;
s110: writing the downlink HQoS flow classification rule and the TM1 flow queue into an access control information list, and switching to S111;
and S111, completing configuration.
The embodiment discloses a service configuration method for processing HQoS service by a downlink traffic management engine through borrowing an uplink traffic management engine, which has the effect of fully utilizing the traffic management engine resources to process the service, improves the processing efficiency of the HQoS service, and avoids possible blockage in the HQoS service processing.
In summary, the embodiments and preferred embodiments of the present invention provide an HQoS service transmission method, which can achieve higher service processing capability, effectively avoid service congestion, and simultaneously can more reasonably utilize traffic management engine resources.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for HQoS service transmission is characterized in that:
when the processing capacity of a first traffic management engine for processing a first HQoS service does not meet the requirement of the first HQoS service, forwarding a first HQoS sub-service included by the first HQoS service to a second traffic management engine for processing a second HQoS service, wherein the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service.
2. The method of claim 1, forwarding a first HQoS sub-service comprised by the first HQoS service to a second traffic management engine for processing a second HQoS service, comprising:
and forwarding the first HQoS sub-service to the second traffic management engine 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.
3. The method of claim 1, forwarding a first HQoS sub-service comprised by the first HQoS service to a second traffic management engine for processing a second HQoS service, further comprising:
and 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 according to the first flow queue identifier carried on the first HQoS sub service for processing, wherein the first flow queue identifier is encapsulated by a network processor on the first HQoS sub service 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.
4. The method of claim 1, the second traffic management engine outputting the processed first HQoS sub-traffic to an outgoing interface of the first HQoS traffic, comprising:
and the second traffic management engine outputs the processed first hQoS sub-service from a first logic port in the second traffic 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.
5. The method of claim 1, wherein:
and the output interface of the first HQoS business has a hardware channel connected with the first traffic management engine and also has a hardware channel connected with the second traffic management engine.
6. The utility model provides a device of HQoS business transmission, includes the first traffic engine that is used for handling first HQoS business, is used for handling the second traffic management engine of second HQoS business, its characterized in that:
when the processing capacity of the first traffic management engine does not meet the requirement of the first HQoS service, the second traffic management engine receives and processes a first HQoS sub-service included by the first HQoS service;
and the second traffic management engine outputs the processed first HQoS sub-service to an output interface of the first HQoS service.
7. The apparatus of claim 6, the second traffic management engine to receive and process the first HQoS sub-traffic comprised by the first HQoS traffic, comprising:
the first HQoS sub-service is forwarded by the network processor according to access control information, where the access control information indicates that a target traffic management engine of the first HQoS sub-service is the second traffic management engine.
8. The apparatus of claim 6, the second traffic management engine to receive and process the first HQoS sub-traffic comprised by the first HQoS traffic, further comprising:
and 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 according to the first flow queue identifier carried on the first HQoS sub service for processing, wherein the first flow queue identifier is encapsulated by a network processor on the first HQoS sub service 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.
9. The apparatus of claim 6, the second traffic management engine to output the processed first HQoS sub-traffic to an egress interface of the first HQoS traffic, wherein:
and the second traffic management engine outputs the processed first hQoS sub-service from a first logic port in the second traffic 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.
10. A system for HQoS service transmission comprises a network processor, a first traffic management engine and a second traffic management engine, wherein:
when the processing capacity of the first traffic management engine for processing a 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 traffic management engine 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;
and the second traffic 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 true CN111756647A (en) | 2020-10-09 |
| CN111756647B 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 (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1124356A2 (en) * | 2000-02-08 | 2001-08-16 | Lucent Technologies Inc. | Guaranteeing types of service in a packet-based system |
| CN1787489A (en) * | 2005-12-22 | 2006-06-14 | 港湾网络有限公司 | Method for average distributing interface flow at multi network processor engines |
| 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 |
| US20070058541A1 (en) * | 2005-08-31 | 2007-03-15 | Alcatel | Communication traffic management systems and methods |
| CN103346950A (en) * | 2013-07-29 | 2013-10-09 | 北京傲天动联技术股份有限公司 | Sharing method and device of load between user service boards of rack-mounted wireless controller |
| CN103929492A (en) * | 2014-04-28 | 2014-07-16 | 华为技术有限公司 | Method, devices and system for load balancing of service chain |
| US20170085628A1 (en) * | 2015-09-23 | 2017-03-23 | Nec Laboratories America, Inc. | Software driven long-term-evolution core network for mobile access |
-
2019
- 2019-03-29 CN CN201910255967.7A patent/CN111756647B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1124356A2 (en) * | 2000-02-08 | 2001-08-16 | Lucent Technologies Inc. | Guaranteeing types of service in a packet-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 |
| US20070058541A1 (en) * | 2005-08-31 | 2007-03-15 | Alcatel | Communication traffic management systems and methods |
| CN1787489A (en) * | 2005-12-22 | 2006-06-14 | 港湾网络有限公司 | Method for average distributing interface flow at multi network processor engines |
| CN103346950A (en) * | 2013-07-29 | 2013-10-09 | 北京傲天动联技术股份有限公司 | Sharing method and device of load between user service boards of rack-mounted wireless controller |
| CN103929492A (en) * | 2014-04-28 | 2014-07-16 | 华为技术有限公司 | Method, devices and system for load balancing of service chain |
| US20170085628A1 (en) * | 2015-09-23 | 2017-03-23 | Nec Laboratories America, Inc. | Software driven long-term-evolution core network for mobile access |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111756647B (en) | 2023-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6914882B2 (en) | Method and apparatus for improved queuing | |
| CN104539440B (en) | Traffic management with in-let dimple | |
| CN1981484B (en) | Hierarchal scheduler with multiple scheduling lanes and scheduling method | |
| US7701849B1 (en) | Flow-based queuing of network traffic | |
| US8626955B2 (en) | Directing packets to a processor unit | |
| US8295305B2 (en) | Dual scheduling of work from multiple sources to multiple sinks using source and sink attributes to achieve fairness and processing efficiency | |
| CN102231697A (en) | Bandwidth dispatching method of message queues as well as message reporting method and device | |
| WO2020087523A1 (en) | Network communication method and apparatus, and electronic device | |
| CN101360309A (en) | Execution method, apparatus and system for service open command | |
| CN101286949A (en) | Wireless Mesh network MAC layer resource scheduling policy based on IEEE802.16d standard | |
| CN111181873B (en) | Data transmission method, data transmission device, storage medium and electronic equipment | |
| CN112084027B (en) | Network-on-chip data transmission method, device, network-on-chip, equipment and medium | |
| CN108768866A (en) | Across the card retransmission method of multicast message, device, the network equipment and readable storage medium storing program for executing | |
| US7088719B2 (en) | Processor with packet processing order maintenance based on packet flow identifiers | |
| US7477636B2 (en) | Processor with scheduler architecture supporting multiple distinct scheduling algorithms | |
| CN102594669A (en) | Data message processing method, device and equipment | |
| CN112995056B (en) | Traffic scheduling method, electronic equipment and storage medium | |
| US8670454B2 (en) | Dynamic assignment of data to switch-ingress buffers | |
| CN111756647B (en) | HQoS service transmission method, device and system | |
| CN112272933B (en) | Queue control method, device and storage medium | |
| US6904056B2 (en) | Method and apparatus for improved scheduling technique | |
| US11516145B2 (en) | Packet control method, flow table update method, and node device | |
| CN102769566B (en) | A kind of Multi-stage scheduling system configuration, variation and device | |
| CN106686739B (en) | Wireless network resource management method based on software defined network and oriented to data flow | |
| CN116800675A (en) | Flow control method, device, equipment and computer readable storage medium |
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 |