CN101938422A - Method and device for seizing tunnel in multi-protocol label switching (MPLS) traffic engineering - Google Patents
Method and device for seizing tunnel in multi-protocol label switching (MPLS) traffic engineering Download PDFInfo
- Publication number
- CN101938422A CN101938422A CN2010102831393A CN201010283139A CN101938422A CN 101938422 A CN101938422 A CN 101938422A CN 2010102831393 A CN2010102831393 A CN 2010102831393A CN 201010283139 A CN201010283139 A CN 201010283139A CN 101938422 A CN101938422 A CN 101938422A
- Authority
- CN
- China
- Prior art keywords
- tunnel
- bandwidth
- priority
- seizing
- consumed
- 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.)
- Pending
Links
Images
Abstract
The invention discloses a method and a device for seizing a tunnel in multi-protocol label switching (MPLS) traffic engineering. The method comprises the following steps: sequencing tunnels mounted by bandwidths of each priority of a traffic engineering interface according to the capacity of the bandwidth consumed by the tunnels; when the tunnels are seized, preferentially disassembling the tunnels mounted by the bandwidths of low priorities; and disassembling the tunnels mounted by the bandwidths of the same priority according to the sequence of the capacity of the bandwidths consumed by the tunnels from large to small. In the realization process of tunnel seizing of the invention, the priority of the tunnel to be sized is minimized, and the number of sized and disassembled tunnels is ensured to be the smallest, and meanwhile, the bandwidth wasted by seizing the tunnels is ensured to be reduced as much as possible, thus reducing the network shock caused by seizing and the influence on flow of low priority.
Description
Technical field
The present invention relates to communication technical field, relate in particular to the tunnel is seized in a kind of multi-protocol label switching traffic engineering method and device.
Background technology
MPLS (Multi-Protocol Label Switching, multiprotocol label switching) TE (traffic engineering) is a kind of technology that the traffic engineering technology is combined with MPLS, merges in the bearer network in multi-service to play an important role.By MPLS TE, the service provider can accurately control the path that flow is flowed through, thereby can avoid congested node, solves a part of path overload, and the problem of another path free time is fully used existing bandwidth resources.
Among the MPLS TE, can be every tunnel configuration priority according to the importance of institute's bearer traffic, the scope of priority from 0 to 7,7 is minimum priority; Under the not enough situation of bandwidth resources, the tunnel of low priority can be seized in the tunnel of high priority, the service quality of the business of high priority can be accessed better meet.
In the existing MPLS traffic engineering tunnel method for pre-emptively, only considered to minimize the factor of the priority of being seized the tunnel, and do not considered how to make that to seize the network concussion that causes minimum and the service impact of low priority dropped to minimum factor.For example, when the bandwidth that takies when needs was 5M, the tunnel that is removed may be 100M, also may be 10M, if what remove is the tunnel of 100M, so just will slattern the bandwidth resources of 95M
Summary of the invention
In view of above-mentioned analysis, the present invention aims to provide method and the device that the tunnel is seized in a kind of multi-protocol label switching traffic engineering, seizes the network that brings in order to the reduction tunnel and shakes the influence that reaches low priority traffice.
Purpose of the present invention mainly is achieved through the following technical solutions:
The invention provides the method that the tunnel is seized in a kind of multi-protocol label switching traffic engineering, comprising:
To the tunnel of each priority bandwidth institute carry of traffic engineering interface, sort according to the size of tunnel bandwidth consumed;
Carry out the tunnel when seizing, preferentially removing the tunnel of low priority bandwidth institute carry; And, remove according to tunnel bandwidth consumed order from big to small for the tunnel of same priority bandwidth institute carry.
Further, also comprise:
For the tunnel that the last item need be removed, preferentially select that tunnel of bandwidth waste minimum to remove.
Further, also comprise:, sort according to the morning and evening of tunnel settling time for the identical tunnel of bandwidth consumed size.
Further, for the identical tunnel of bandwidth consumed size, remove to order early settling time from evening according to the tunnel.
Further, the process of preferentially removing the tunnel of low priority carry comprises:
Can judgement satisfy the bandwidth requirement in this tunnel by the tunnel of seizing low priority, if, be calculated as and satisfy the also bandwidth of needs of bandwidth that this tunnel consumes, and begin from the tunnel of lowest priority institute carry to remove, until satisfy till the bandwidth that this tunnel consumes according to priority order from low to high; Otherwise the bandwidth requirement in this tunnel can't be satisfied in the notice downstream.
The present invention also provides the device that the tunnel is seized in a kind of multi-protocol label switching traffic engineering, comprising:
Order module is used for the tunnel to each priority bandwidth institute carry of traffic engineering interface, sorts according to the size of tunnel bandwidth consumed;
Module is removed in the tunnel, is used for carrying out the tunnel when seizing, and preferentially removes the tunnel of low priority bandwidth institute carry; And, remove according to tunnel bandwidth consumed order from big to small for the tunnel of same priority bandwidth institute carry.
Further, described tunnel is removed module and also is used for, and for the tunnel that the last item need be removed, preferentially selects that tunnel of bandwidth waste minimum to remove.
Further, described order module also is used for, and for the identical tunnel of bandwidth consumed size, sorts according to the morning and evening of tunnel settling time.
Further, described tunnel is removed module and also is used for, and for the identical tunnel of bandwidth consumed size, removes to order early settling time from evening according to the tunnel.
Beneficial effect of the present invention is as follows:
The present invention is in the implementation procedure that the tunnel is seized, minimize the priority of being seized the tunnel, and the tunnel minimum number of seizing dismounting that makes, reduce simultaneously the bandwidth of being seized the tunnel waste as much as possible, seize the network concussion that causes and to the influence of low-priority traffic thereby reduced.
Other features and advantages of the present invention will be set forth in the following description, and becoming apparent from specification of part perhaps understood by implementing the present invention.Purpose of the present invention and other advantages can realize and obtain by specifically noted structure in the specification of being write, claims and accompanying drawing.
Description of drawings
Fig. 1 is in the described method of the embodiment of the invention, the structural representation of TE interface bandwidth manager;
Fig. 2 is the schematic flow sheet of the described method of the embodiment of the invention;
Fig. 3 is in the described method of the embodiment of the invention, the bandwidth schematic diagram that each priority consumed before the tunnel was seized;
Fig. 4 is in the described method of the embodiment of the invention, and the bandwidth schematic diagram that each priority of back consumes is seized in the tunnel;
Fig. 5 is the structural representation of the described device of the embodiment of the invention.
Embodiment
Specifically describe the preferred embodiments of the present invention below in conjunction with accompanying drawing, wherein, accompanying drawing constitutes the application's part, and is used from explaination principle of the present invention with embodiments of the invention one.For clear and simplification purpose, when it may make theme of the present invention smudgy, with specifying in detail of known function and structure in the omission device described herein.
At first, the described method of the embodiment of the invention is elaborated.
At first, need a pre-defined TE (traffic engineering) interface bandwidth manager, as shown in Figure 1, Fig. 1 is the structural representation of TE interface bandwidth manager, and this TE interface bandwidth manager is writing down the TE total bandwidth of this TE interface, using TE bandwidth and priority bandwidth array; Wherein, each array element of priority bandwidth array writing down bandwidth summation that this priority tunnel consumes, this priority tunnel visible bandwidth (comprising the bandwidth that can seize from the low priority tunnel), point to the pointer of the doubly linked list in this priority tunnel; For the tunnel doubly linked list in the priority bandwidth array, sort from big to small according to the bandwidth of tunnel consumption, for the same tunnel of bandwidth consumed, sort from small to large according to the tunnel creation time.
As shown in Figure 2, Fig. 2 is the schematic flow sheet of the described method of the embodiment of the invention, specifically can comprise:
Step 201: a tunnel is to TE interface bandwidth application;
Step 202: whether the bandwidth of judging this tunnel consumption is not more than the existing remaining bandwidth of TE interface, if forward step 203 to, otherwise forward step 204 to;
Step 203: not needing to seize the tunnel of removing low priority, directly is this tunnel reserved resource, specifically comprises: the dedicated bandwidth of the Bandwidth Broker of updating interface; This tunnel is added in the tunnel chained list of the corresponding priority of priority bandwidth array, the tunnel that adds in this chained list of fashionable assurance is orderly, being the tunnel sorts from big to small according to the bandwidth that consumes, and for the same tunnel of bandwidth consumed, sorts from small to large according to the tunnel creation time; Upgrade the bandwidth consumed of corresponding priority in the priority bandwidth array and the visible bandwidth of this priority; Upgrade the visible bandwidth that is lower than each priority of this tunnel priority in the priority bandwidth array;
Step 204: judge the bandwidth requirement that can satisfy this tunnel by the tunnel of seizing low priority, promptly relatively the bandwidth that consumes of this tunnel whether greater than the visible bandwidth of this priority in the priority array, if greater than, forward step 205 to; Otherwise forward step 206 to;
Step 205: can't satisfy the bandwidth requirement in this tunnel, send signaling message, tell the downstream can't be this tunnel reserved resource to the downstream;
Step 206: be calculated as the bandwidth requirement that satisfies this tunnel, the bandwidth Req_bw that also needs, and execution in step 207;
Step 207: the priority array according in the Bandwidth Broker travels through array from the low priority to the high priority; Specifically comprise the steps:
Step 207-1: to the low priority array, judge whether Req_bw is not less than the dedicated bandwidth of this priority, if show that bandwidth under this priority is not that 0 tunnel all will be removed, and forwards step 207-2 to; Otherwise, show the tunnel under this priority as long as removing a part just can meet the demands, forward step 207-3 to;
Step 207-2: travel through the tunnel chained list under this priority,, then remove this tunnel, discharge bandwidth if the bandwidth of tunnel consumption is not equal to 0; Specifically comprise: when removing the tunnel, the dedicated bandwidth of the Bandwidth Broker of updating interface; Upgrade the bandwidth consumed and the visible bandwidth that are removed the corresponding priority in tunnel in the priority bandwidth array; Upgrade the visible bandwidth that is lower than each priority that is removed tunnel priority in the priority bandwidth array; Upgrading Req_bw is the bandwidth that Req_bw deducts the tunnel release of dismounting;
207-3: judge whether Req_bw equals 0,, need not to have removed the low priority tunnel again, forward step 208 to if Req_bw=0 shows the bandwidth requirement that satisfies new built tunnel; Otherwise forward step 207-4 to;
207-4:, travel through the tunnel chained list under this high priority to a high priority array;
Whether 207-5:Req_bw is greater than 0, if forward step 207-6 to; Otherwise forward step 207-8 to;
207-6: whether the bandwidth of judging tunnel consumption is not more than Req_bw, if forward 207-7 to; Otherwise forward 207-8 to;
207-7: the bandwidth of the consumption in tunnel is not 0, then removes the tunnel, discharges bandwidth, upgrades the bandwidth that the Req_bw=Req_bw-tunnel discharges;
207-8: writing down this tunnel is pre_del_lsp, continue successively to travel through the tunnel chained list of this priority, seek a tunnel bandwidth consumed and be not less than Req_bw, and satisfy the tunnel of min (the tunnel bandwidth consumed deducts Req_bw), if find, then remove the tunnel that finds, do not find and then remove pre_del_lsp, discharge tunnel bandwidth
Step 208: tunnel resource application processing finishes.
For the ease of understanding the method for the invention, will be described further the method for the invention with a concrete example below.
The TE total bandwidth of supposing interface configuration is 200M, and the bandwidth situation that each priority consumes as shown in Figure 3; When a tunnel 7 (priority is 5, and bandwidth is 155M), when this interface bandwidth application, treatment step is as follows:
The 1st step: compare the remaining bandwidth of interface and the bandwidth application in tunnel 7:
The TE total bandwidth that disposes on the interface is 200M, has consumed 200M, and remaining bandwidth is 0, can't satisfy the bandwidth requirement in tunnel 7;
The 2nd step: judge by seizing the low priority tunnel, can satisfy the bandwidth requirement in tunnel 7:
The visible bandwidth of interface priority 5 is 200M, greater than the bandwidth of tunnel 7 applications, therefore by seizing the tunnel of low priority, can satisfy the bandwidth requirement in tunnel 7
The 3rd step: be recorded as the bandwidth requirement that satisfies tunnel 7, the bandwidth Req_bw=155M that need seize, traversal priority bandwidth array begins to remove the tunnel from low priority
The 4th step: in the priority array, priority 7 tunnels are handled:
What judge priority 7 tunnels has been 100M with total bandwidth, less than the bandwidth Req_bw that need are seized, the necessary complete removal in tunnel under this priority is described;
Tunnel chained list under the traversal priority 7 is removed tunnel 1, and tunnel 2 discharges the 100M bandwidth altogether;
The remaining bandwidth of updating interface is 100M;
The dedicated bandwidth that upgrades priority 7 is 0, and visible bandwidth is 100M;
Upgrading the bandwidth Req_bw that also need seize is (155M-100M)=55M;
The 5th step: in the priority array, priority 6 tunnels are handled:
What judge priority 6 tunnels has been 100M with total bandwidth, greater than the bandwidth Req_bw that need are seized, illustrates that the tunnel under this priority need not complete removal, only needs to remove the bandwidth requirement that a part of tunnel just can satisfy tunnel 7;
The 6th step: the tunnel chained list under the traversal priority 6:
Take out tunnel 3, bandwidth consumed is 40M, less than Req_bw, therefore removes tunnel 3, discharges bandwidth 40M;
The remaining bandwidth that upgrades the TE interface is 140M;
The dedicated bandwidth that upgrades priority 6 is 60M, and visible bandwidth is 140M;
The dedicated bandwidth that upgrades priority 7 is 0, and visible bandwidth is 140M;
Upgrading the bandwidth Req_bw that also need seize is (55M-40M)=15M;
The 7th step: take out tunnel 4, bandwidth consumed is 30M, greater than Req_bw, illustrates if remove tunnel 4, will waste (30M-Req_bw)=15M bandwidth;
Mark tunnel 4 is pre_del_lsp, continues traversal tunnel chained list, seeks the tunnel, feasible (tunnel bandwidth consumed-Req_bw) be not less than 0, and value minimum;
The 8th step: take out tunnel 5, bandwidth consumed is 20M, greater than Req_bw, illustrates if remove tunnel 5, will waste (20M-Req_bw)=5M bandwidth;
The 9th step: take out tunnel 6, bandwidth consumed is 10M, less than Req_bw, illustrates that tunnel 6 can't satisfy the Req_bw bandwidth; Therefore will remove last the tunnel in tunnel 6 in the chained list, promptly the tunnel 5;
The 10th step: remove tunnel 5, discharge bandwidth 20M;
The remaining bandwidth that upgrades the TE interface is 160M;
The dedicated bandwidth that upgrades priority 6 is 40M, and visible bandwidth is 160M;
The dedicated bandwidth that upgrades priority 7 is 0, and visible bandwidth is 160M;
The 11st step: for distributing bandwidth resources in tunnel 7:
The remaining bandwidth that upgrades the TE interface is 5M;
The dedicated bandwidth that upgrades priority 5 is 155M, and visible bandwidth is 45M;
The dedicated bandwidth that upgrades priority 6 is 40M, and visible bandwidth is 5M;
The dedicated bandwidth that upgrades priority 7 is 0, and visible bandwidth is 5M;
Through above step, the bandwidth situation that each priority of interface consumes as shown in Figure 4,
Need to prove, for the MPLS traffic engineering tunnel, the resource reservation style has SE pattern and FF pattern for SE mode resource preservation style, and the tunnel of identical SESSION can shared bandwidth, that is to say under the same SESSION to have many tunnels, and the bandwidth in every tunnel is all identical; For the resource reservation style of FF pattern, every tunnel exclusively enjoys bandwidth.In the described method of the embodiment of the invention, for convenience of description, describe as an example with the FF pattern; For the SE pattern, when being seized, dismounting should be many tunnels under the same SESSION, the specific implementation process is identical with the FF pattern.
Next 5 pairs of described devices of the embodiment of the invention are elaborated in conjunction with the accompanying drawings.
As shown in Figure 5, Fig. 5 is the structural representation of the described device of the embodiment of the invention, specifically can comprise:
Order module, the main tunnel of being responsible for each priority bandwidth institute carry of traffic engineering interface sorts according to the size of tunnel bandwidth consumed; When if tunnel bandwidth consumed size is identical,, sort according to the morning and evening of tunnel settling time for the identical tunnel of bandwidth consumed size.
Module is removed in the tunnel, mainly is responsible for carrying out the tunnel when seizing, and preferentially removes the tunnel of low priority bandwidth institute carry; And, remove according to tunnel bandwidth consumed order from big to small for the tunnel of same priority bandwidth institute carry; For the identical tunnel of bandwidth consumed size, remove to order early settling time from evening according to the tunnel; And, preferentially select that tunnel of bandwidth waste minimum to remove for the tunnel that the last item need be removed.
In sum, the embodiment of the invention provides method and the device that the tunnel is seized in a kind of multi-protocol label switching traffic engineering, in the tunnel is seized, this two Considerations have been increased, optimizing the tunnel seizes: (1) seizes the network concussion that causes in order to reduce, improve stability of network, during we require to seize, the minimum number in the low priority tunnel of dismounting; (2) in order to reduce the influence of seizing the low priority user business, improve utilization rate of network resource, the tunnel bandwidth that we require to be seized is wasted minimum; Because newly-increased finding the solution of second factor is a np complete problem, computation complexity and tunnel quantity are exponential relationship, consider the complexity of equipment to the requirement and the realization of real-time, we only seek separating of near-optimal to this factor, thereby it is low to have reduced the complexity of calculating, and is easy to realize on equipment, at the traffic demand that satisfies the high priority tunnel simultaneously, reduce as much as possible and seize the network concussion that causes, reduce influence low-priority traffic.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claims.
Claims (9)
1. the method that the tunnel is seized in the multi-protocol label switching traffic engineering is characterized in that, comprising:
To the tunnel of each priority bandwidth institute carry of traffic engineering interface, sort according to the size of tunnel bandwidth consumed;
Carry out the tunnel when seizing, preferentially removing the tunnel of low priority bandwidth institute carry; And, remove according to tunnel bandwidth consumed order from big to small for the tunnel of same priority bandwidth institute carry.
2. method according to claim 1 is characterized in that, also comprises:
For the tunnel that the last item need be removed, preferentially select that tunnel of bandwidth waste minimum to remove.
3. method according to claim 1 is characterized in that, also comprises: for the identical tunnel of bandwidth consumed size, sort according to the morning and evening of tunnel settling time.
4. method according to claim 3 is characterized in that, for the identical tunnel of bandwidth consumed size, removes to order early settling time from evening according to the tunnel.
5. according to the described method of claim 1 to 4, it is characterized in that the process of preferentially removing the tunnel of low priority carry comprises:
Can judgement satisfy the bandwidth requirement in this tunnel by the tunnel of seizing low priority, if, be calculated as and satisfy the also bandwidth of needs of bandwidth that this tunnel consumes, and begin from the tunnel of lowest priority institute carry to remove, until satisfy till the bandwidth that this tunnel consumes according to priority order from low to high; Otherwise the bandwidth requirement in this tunnel can't be satisfied in the notice downstream.
6. the device that the tunnel is seized in the multi-protocol label switching traffic engineering is characterized in that, comprising:
Order module is used for the tunnel to each priority bandwidth institute carry of traffic engineering interface, sorts according to the size of tunnel bandwidth consumed;
Module is removed in the tunnel, is used for carrying out the tunnel when seizing, and preferentially removes the tunnel of low priority bandwidth institute carry; And, remove according to tunnel bandwidth consumed order from big to small for the tunnel of same priority bandwidth institute carry.
7. device according to claim 6 is characterized in that, described tunnel is removed module and also is used for, and for the tunnel that the last item need be removed, preferentially selects that tunnel of bandwidth waste minimum to remove.
8. device according to claim 6 is characterized in that described order module also is used for, and for the identical tunnel of bandwidth consumed size, sorts according to the morning and evening of tunnel settling time.
9. device according to claim 8 is characterized in that, described tunnel is removed module and also is used for, and for the identical tunnel of bandwidth consumed size, removes to order early settling time from evening according to the tunnel.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010102831393A CN101938422A (en) | 2010-09-16 | 2010-09-16 | Method and device for seizing tunnel in multi-protocol label switching (MPLS) traffic engineering |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010102831393A CN101938422A (en) | 2010-09-16 | 2010-09-16 | Method and device for seizing tunnel in multi-protocol label switching (MPLS) traffic engineering |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101938422A true CN101938422A (en) | 2011-01-05 |
Family
ID=43391564
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010102831393A Pending CN101938422A (en) | 2010-09-16 | 2010-09-16 | Method and device for seizing tunnel in multi-protocol label switching (MPLS) traffic engineering |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101938422A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102123089A (en) * | 2011-02-21 | 2011-07-13 | 杭州华三通信技术有限公司 | Tunnel establishing method and device |
| CN102223299A (en) * | 2011-06-08 | 2011-10-19 | 中兴通讯股份有限公司 | Method and system for managing bandwidth resources between tunnels |
| CN103780474A (en) * | 2014-01-13 | 2014-05-07 | 杭州华三通信技术有限公司 | Traffic engineering tunnel resource preemption method and device |
| CN104202246A (en) * | 2014-07-09 | 2014-12-10 | 北京东土科技股份有限公司 | Dynamic path adjustment method and device for link congestion |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1466339A (en) * | 2002-06-24 | 2004-01-07 | ��Ϊ��������˾ | Method for preempting multi-procotol label switching flow controlling band width resource |
| CN101815035A (en) * | 2009-02-25 | 2010-08-25 | 丛林网络公司 | Use RSVP-TE load balancing network traffics on label switched path |
-
2010
- 2010-09-16 CN CN2010102831393A patent/CN101938422A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1466339A (en) * | 2002-06-24 | 2004-01-07 | ��Ϊ��������˾ | Method for preempting multi-procotol label switching flow controlling band width resource |
| CN101815035A (en) * | 2009-02-25 | 2010-08-25 | 丛林网络公司 | Use RSVP-TE load balancing network traffics on label switched path |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102123089A (en) * | 2011-02-21 | 2011-07-13 | 杭州华三通信技术有限公司 | Tunnel establishing method and device |
| CN102123089B (en) * | 2011-02-21 | 2013-09-18 | 杭州华三通信技术有限公司 | Tunnel establishing method and device |
| CN102223299A (en) * | 2011-06-08 | 2011-10-19 | 中兴通讯股份有限公司 | Method and system for managing bandwidth resources between tunnels |
| CN103780474A (en) * | 2014-01-13 | 2014-05-07 | 杭州华三通信技术有限公司 | Traffic engineering tunnel resource preemption method and device |
| CN103780474B (en) * | 2014-01-13 | 2017-03-15 | 杭州华三通信技术有限公司 | A kind of traffic engineering tunnel resource seizing method and device |
| CN104202246A (en) * | 2014-07-09 | 2014-12-10 | 北京东土科技股份有限公司 | Dynamic path adjustment method and device for link congestion |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103346922B (en) | The controller of determination network state based on SDN and determine method | |
| CN101599908B (en) | Method and equipment for automatically distributing bandwidth | |
| CN104378308A (en) | Method and device for detecting message sending rate | |
| CN105812285A (en) | Port congestion management method and device | |
| CN105721354B (en) | Network-on-chip interconnected method and device | |
| CN102469019B (en) | Device and method for allocating aggregated link bandwidth in packet-switched network | |
| EP2670085B1 (en) | System for performing Data Cut-Through | |
| CN103841052A (en) | Bandwidth resource distribution system and method | |
| CN102811176B (en) | A kind of data flow control method and device | |
| CN104579962A (en) | Method and device for differentiating QoS strategies of different messages | |
| CN110896365B (en) | Traffic scheduling method in network node, server and storage medium | |
| CN105760459A (en) | Distributed data processing system and method | |
| CN101227416A (en) | Method for distributing link bandwidth in communication network | |
| CN102521057A (en) | Resource scheduling method and device | |
| CN108206787A (en) | A kind of congestion-preventing approach and device | |
| CN101938422A (en) | Method and device for seizing tunnel in multi-protocol label switching (MPLS) traffic engineering | |
| CN102970244A (en) | Network message processing method of multi-CPU (Central Processing Unit) inter-core load balance | |
| CN102387076A (en) | Shaping-combined hierarchical queue scheduling method | |
| CN103634223A (en) | Network service flow based dynamic control transmission method and device | |
| CN108322406A (en) | A kind of SDN data plane failure restoration methods based on link performance and flow point class | |
| CN104618157A (en) | Network management method, device and system | |
| CN103312628B (en) | The dispatching method and device of aggregated links in a kind of packet network | |
| CN103685062A (en) | Cache management method and device | |
| CN113132265A (en) | Multi-stage scheduling method and device for multi-path Ethernet | |
| CN102143053A (en) | Method, device and system for transmitting data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110105 |