EP1063818A2
Expired / Lapsed
EP
⏱️ 0.0 years remaining
System for multi-layer provisioning in computer networks
Assignee: Intel Corp
•
Filing: 2000-06-23
•
Granted: —
•
Expires: 2020-06-23
Abstract
Abstract A system using a "provisioning engine" that performs high-speed identification, analysis and processing of information in a network. The provisioning engine applies rules to allocate network resources, such as bandwidth, to achieve specified performance. The provisioning engine can transfer, monitor and control information flowing through it, such as data packets. It is provided with an extremely fast mechanism for handling routing and data flow manipulation of the packets. This allows fast, "wire speed," processing of units of information, such as packets, to specific, guaranteed flows and virtual circuits in real time. A preferred embodiment discloses dedicated architecture to process the data traffic. The dedicated architecture uses portions of packet header information to identify traffic types. The types are mapped to a service class that can already exist or that can be created to meet a traffic type bandwidth requirement. Predefined rules based on customer needs, service provider guidelines, bandwidth availability, etc., are then applied. This allows use of Layer 1 through Layer 7 data fields to be the basis for provisioning, security, monitoring and control of packet flow at full line rates.
Inventors
- 👤 Tony Stelliga
Bibliographic Details
Application Number
—
Jurisdiction
EP
Data Source
google_patents
Last Synchronized
2026-11-08 20:00
CPC Classifications
H; H04; H04L; H04L49/00; H04L49/90; H04L49/9057; G; G06; G06F; G06F12/00; G06F12/02; G06F12/0223; G06F12/023; G06F9/00; G06F9/06; G06F9/46; G06F9/54; H04L12/00; H04L12/28; H04L12/46; H04L12/4604; H04L12/4608; H04L12/54; H04L12/56; H04L12/5601; H04L45/00; H04L45/302; H04L45/306; H04L45/74; H04L45/745; H04L45/7453; H04L47/00; H04L47/10; H04L47/15; H04L47/24; H04L47/2408; H04L47/2416; H04L47/2425; H04L47/2441; H04L47/50; H04L47/52; H04L47/522; H04L47/62; H04L47/6215; H04L47/625; H04L47/70; H04L47/80; H04L47/801; H04L47/805; H04L47/808; H04L47/82; H04L47/822; H04L47/825; H04L49/60; H04L49/602; H04L49/9084; H04L49/9089; H04L49/9094; H04L61/00; H04L61/09; H04L61/10; H04L63/00; H04L63/04; H04L63/08; H04Q; H04Q11/00; H04Q11/04; H04Q11/0428; H04Q11/0478; H04L49/20; H04L49/205; H04L49/30; H04L49/3009; H04L49/35; H04L49/351; H04L69/00; H04L69/12; H04L69/30; H04L69/32
Claims Analysis
Total Claims: 16
Claim 1
Independent Claim
62 words
A method for provisioning resources in a communications network,
wherein the communications network uses the resources to transfer data of different
traffic types from sources to destinations, the method comprising defining a target performance level for a specific traffic type; detecting data transfers of the specific traffic type; and allocating resources to achieve the target performance level for the specific
traffic type.
Claim 2
Dependent Claim
10 words
The method of claim 1, wherein the resources include bandwidth.
Claim 3
Dependent Claim
10 words
The method of claim 1, wherein the resources include latency.
Claim 4
Dependent Claim
11 words
The method of claim 1, wherein the resources include quality
parameters.
Claim 5
Dependent Claim
16 words
The method of claim 1, wherein the resources are allocated among
multiple sub-links in the network.
Claim 6
Dependent Claim
59 words
The method of claim 2, wherein the detecting and allocating steps
are performed by a provisioning engine, the method further comprising accepting signals sent to the provisioning engine from an outside source to
change the target data rate for the specific traffic type; and using the provisioning engine to allocate the bandwidth to achieve the new
target data rate.
Claim 7
Dependent Claim
62 words
The method of claim 2, wherein data is transferred in packets,
wherein each packet includes header information, wherein a traffic type is defined in
terms of the header information, wherein the step of "using the provisioning engine to
detect data transfers of the specific traffic type" includes the subset of using the header information to detect packets of the specific traffic type.
Claim 8
Dependent Claim
27 words
The method of claim 7, wherein the header information includes
one or more of the following types of header information: packet source, packet
destination, traveled route, priority.
Claim 9
Dependent Claim
21 words
The method of claim 7, wherein the header information is in a
format in accordance with the ISO Seven Layer model.
Claim 10
Dependent Claim
79 words
The method of claim 7, further comprising forming one or more classes of service wherein different classes of service
are associated with a different data rate; defining one or more rules for allocating a traffic type to a class of service; wherein the step of "using the provisioning engine to allocate the
bandwidth to achieve the target data rate for the specific traffic type" includes the substep
of using one or more of the rules to allocate the bandwidth.
Claim 11
Dependent Claim
50 words
The method of claim 10, wherein the packets are digital
information including bits, the method further comprising using bits in the packet header to form a mesh array of binary bit patterns;
and using a content-addressable memory with hashing pre-processing to map
the mesh array to a class of service.
Claim 12
Dependent Claim
19 words
The method of claim 2, further comprising collecting information
on the actual data rate for the specific traffic type.
Claim 13
Dependent Claim
32 words
The method of claim 12, further comprising accepting a request for a target data rate for a specific traffic type from a
customer; and billing the customer according to the collected information.
Claim 14
Dependent Claim
53 words
The method of claim 2, wherein the provisioning engine includes a
port for receiving information to change the target data rate, the method further
comprising accepting information specifying a new target data rate; and using the provisioning engine to allocate the bandwidth to achieve the new
target data rate for a traffic type.
Claim 15
Dependent Claim
52 words
The method of claim 2, wherein the provisioning engine includes a
port for receiving information to change the specified traffic type, the method further
comprising accepting information specifying a new traffic type; and using the provisioning engine to allocate the bandwidth to achieve a target
data rate for the new traffic type.
Claim 16
Dependent Claim
72 words
The method of claim 2, wherein the provisioning engine includes a
port for receiving information to change the specified traffic type, the method further
comprising accepting information specifying a new traffic type; and using the provisioning engine to provide billing information to the host
system containing the amount of traffic on each of the links over a period of time to
achieve a fee for the usage of the specific traffic type.
References Cited (Backward Citations)
No citation records indexed.
USPTO Annuity & Maintenance Windows
Maintenance schedule is calculated for granted US utility patents.