Provisioning services in legacy mode in a data center network
US-2016315811-A1 · Oct 27, 2016 · US
US9419903B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9419903-B2 |
| Application number | US-201314072985-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 6, 2013 |
| Priority date | Nov 8, 2012 |
| Publication date | Aug 16, 2016 |
| Grant date | Aug 16, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An embodiment of the invention includes an Openflow switch. The Openflow switch includes Openflow ALL groups. The Openflow ALL groups include ALL group buckets. During ingress ALL group buckets are represented in ingress as a list of output ports with associated queue ID's and associated copy-counts. Each ALL group bucket is represented in egress by an egress Openflow table entry where the egress Openflow table entry matches a group ID and a bucket ID. An action entry in an ALL group bucket table entry is the set of actions in the Openflow ALL group bucket excluding an output port and queue assignment.
Opening claim text (preview).
What is claimed is: 1. A hardware switch comprising: a first multiplexer having a plurality of input ports and an output port; an ingress processor having an input port coupled to the output port of the first multiplexer; a common data buffer having a first input port coupled to the output port of the first multiplexer, a second input and an output port; a first packet pointer having an input port coupled to the output port of the first multiplexer and an output port; a plurality of queues having input ports coupled to the output port of the first packet pointer and an output port; a second packet pointer having an input port coupled to the output port of the plurality of queues and an output coupled to the second input of the common data buffer; an egress processor having an input port coupled to the output port of the common data buffer and an output port; a second multiplexer having an input coupled to the output port of the egress processor and a plurality of output ports; a memory wherein an egress Openflow table and an ALL group bucket table are stored in the memory; Openflow ALL groups wherein the Openflow ALL groups comprise: ALL group buckets; wherein ALL group buckets are represented in ingress as a list of output ports with associated queue ID's and associated copy-counts; wherein each ALL group bucket is represented in egress by the egress Openflow table entry wherein the egress Openflow table entry matches a group ID and a bucket ID; and wherein an action entry in the ALL group bucket table entry is the set of actions in the Openflow ALL group bucket excluding an output port and queue assignment. 2. The hardware switch of claim 1 wherein the bucket ID is a bucket number. 3. The hardware switch of claim 1 wherein the bucket ID is a output port number and a port-index-ID. 4. The hardware switch of claim 1 wherein a packet pointer and a copy-count field are enqueued at each output port of an Openflow ALL group once per packet. 5. The hardware switch of claim 4 wherein the egress processor reads the copy-count field; wherein the egress processor outputs a packet to a queue's port a number of times specified by copy-count field before retiring a packet pointer from the head of the queue. 6. The hardware switch of claim 1 wherein the Openflow ALL groups are egress Openflow tables; wherein an ALL group egress table uses a shared pool of table resources with other egress Openflow tables. 7. The hardware switch of claim 1 wherein the egress Openflow tables and ingress Openflow tables share common table resources; wherein an egress ALL group table uses the common table resources. 8. The hardware switch of claim 6 where the pool of table resources comprises memory for storing matches and actions.
using leaky-bucket · CPC title
Queue service order · CPC title
relying on flow classification, e.g. using integrated services [IntServ] · CPC title
Parsing or analysis of headers · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.