System for multi-layer broadband provisioning in computer networks

• US 6,625,650 B2
• Filed: 06/25/1999
• Issued: 09/23/2003
• Est. Priority Date: 06/27/1998
• Status: Expired due to Term

• Current Assignee: Micron Technology, Inc.
• Original Assignee: Intel Corporation
• Inventors: Stelliga, Tony
• Primary Examiner(s): Najjar, Saleh
• Application Number:
  US09/340,068
• Publication Number:
  US 20030061338A1
• Time in Patent Office: 1,551 Days
• Field of Search: 709/203, 709/217, 709/219, 709/220, 709/221, 709/223, 709/224, 709/225, 709/226, 709/229, 709/231, 709/227, 709/232, 370/352, 370/351
• US Class Current: 709/226
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 12/4608 LAN interconnection over ATM networks
• CPC Class Codes: H04L 12/5601 Transfer mode dependent, e.g. ATM
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/7453 using hashing
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2416 Real-time traffic
• CPC Class Codes: H04L 47/2425 for supporting services specification, e.g. SLA
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/50 Queue scheduling
• CPC Class Codes: H04L 47/52 by attributing bandwidth to queues
• CPC Class Codes: H04L 47/522 Dynamic queue service slot or variable bandwidth allocation
• CPC Class Codes: H04L 47/6215 Individual queue per QOS, rate or priority
• CPC Class Codes: H04L 47/625 for service slots or service orders
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/801 Real time traffic
• CPC Class Codes: H04L 47/805 : QOS or priority aware
• CPC Class Codes: H04L 47/808 : User-type aware
• CPC Class Codes: H04L 47/822 : Collecting or measuring resource availability data
• CPC Class Codes: H04L 47/825 : Involving tunnels, e.g. MPLS
• CPC Class Codes: H04L 49/205 : Quality of Service based
• CPC Class Codes: H04L 49/3009 : Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/351 : for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 49/602 : Multilayer or multiprotocol switching, e.g. IP switching
• CPC Class Codes: H04L 49/90 : Buffering arrangements
• CPC Class Codes: H04L 49/9057 : Arrangements for supporting packet reassembly or resequencing
• CPC Class Codes: H04L 49/9094 : Arrangements for simultaneous transmit and receive, e.g. simultaneous reading/writing from/to the storage element
• CPC Class Codes: H04L 61/00 : Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/10 : of different types
• CPC Class Codes: H04L 63/04 : for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/12 : Protocol engines
• CPC Class Codes: H04L 69/32 : Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04Q 11/0478 : Provisions for broadband connections

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.

Claims

1. A method comprising:

defining a performance level for a specific traffic type in terms of bandwidth, latency, security, and priority;

detecting a data transfer of the specific traffic type;

allocating resources to achieve the performance level for the specific traffic type; and

transferring the data via a virtual channel associated with the specific traffic type to provide the defined bandwidth, latency, security, and priority.

2. The method of claim 1, wherein the resources are allocated among multiple sub-links in the network.

3. The method of claim 1, wherein detecting the data transfer and allocating resources are performed by a provisioning engine, the method further comprising:

receiving a signal at the provisioning engine to change a data rate for the specific traffic type; and

the provisioning engine allocating the bandwidth to achieve the data rate.

4. The method of claim 3, wherein data is transferred in packets that include a header that specifies a traffic type and wherein the provisioning engine detecting data transfers of the specific traffic type includes the provisioning engine detecting data transfer of a specific type based on the specific traffic type specified in the header.

5. The method of claim 4, wherein the header includes one of a packet source, packet destination, traveled route, and priority.

6. The method of claim 4, further comprising:

forming one or more classes of service each associated with a different data rate;

defining one or more rules for associating a traffic type with a class of service;

wherein the provisioning engine allocating the bandwidth to achieve the data rate for the specific traffic type includes using one or more of the rules to allocate the bandwidth.

7. The method of claim 6, 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.

8. The method of claim 1, further comprising collecting information on the actual data rate for the specific traffic type.

9. The method of claim 8, further comprising:

accepting a request for a data rate for a specific traffic type from a customer; and

billing the customer according to the collected information.

10. The method of claim 3, wherein the provisioning engine includes a port for receiving information to change the data rate, the method further comprising:

accepting information specifying the data rate; and

the provisioning engine allocating the bandwidth to achieve the data rate for a traffic type.

11. The method of claim 3, wherein the provisioning engine includes a port for receiving information to change the specified traffic type, the method further comprising:

accepting information specifying a traffic type; and

the provisioning engine allocating the bandwidth to achieve a data rate for the traffic type.

12. The method of claim 3, wherein the provisioning engine includes a port for receiving information to change the specified traffic type, the method further comprising:

accepting information specifying a traffic type; and

the provisioning engine providing 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.

13. A method comprising:

loading a set of rules into a provisioning engine, the set of rules to define a plurality of user service classes that provide a service level based on priority, security, bandwidth, and latency, wherein each user service class is associated with a virtual channel to transmit data packets;

receiving a data packet at the provisioning engine;

parsing the data packet to determine one or more control parameters;

assigning the data packet to one of the plurality of user service classes based on the control parameters and one or more of the rules in the provisioning engine; and

forwarding the data packet to a next network destination via the virtual channel associated with the assigned user service class to provide the defined service level.

14. The method of claim 13, further comprising collecting information on the actual data rate for one or more of the user service classes.

15. The method of claim 14, further comprising accepting a request for a data rate for a specific user service class from a customer;

and billing the customer according to the collected information.

16. An apparatus comprising:

a memory to store a set of rules to define a plurality of user service classes that each provide a service level based on priority, security, bandwidth, and latency;

a receiver to receive a data packet from a network;

a parser to parse the data packet and to determine one or more control parameters;

a mapping table to map the data packet to one of the plurality of user service classes based on the control parameters and one or more of the rules in the memory;

a circuit linker to link the data packet to a virtual circuit associated with the user service class to which the data packet is mapped; and

a transmitter to transmit the data packet to a next network destination via the virtual circuit to which the data packet is linked in order to provide the service level associated with the data packet.