throbber

`
`
`
`
`
`
`
`
`
`
`
`
`Exhibit 1021
`
`Exhibit 1 02 1
`
`
`
`

`

`Routing lookups in hardware at memory access speeds - IEEE Xplore Document
`
`
` IEEE.org IEEE Xplore Digital Library
`|
`
`
`|
`
`IEEE-SA
`
`
`|
`
`IEEE Spectrum
`
`
`|
`
`More Sites
`
`
`
`
` Cart(0) Welcome Charles Koch
`|
`
`
`
`Institutional Sign In
`
`
`
`BROWSE
`
`MY SETTINGS
`
`GET HELP
`
`WHAT CAN I ACCESS?
`
`
`
`Search
`
`
`
`Basic Search
`
`Author Search
`
`Publication Search
`
`Browse Conferences > INFOCOM '98. Seventeenth Annu...
`
`
`
`Advanced Search
`Other Search Options
`
`Routing lookups in hardware at memory access speeds
`
`
`
`Related Articles
`
`Sign In or Purchase
`to View Full Text
`
`220
`Paper
`Citations
`
`
`
`87
`Patent
`Citations
`
`
`
`377
`Full
`Text Views
`
`
`
`3
`Author(s)
`
` P. Gupta ; S. Lin ; N. McKeown
`
`Using multiple hash functions to improve IP
`lookups
`
`RR-TCP: a reordering-robust TCP with DSACK
`
`High-performance IP routing table lookup using
`CPU caching
`
`View All
`
`
`
`View All Authors
`
`Abstract
`
`Authors
`
`Figures
`
`References
`
`Citations
`
`Keywords
`
`Metrics
`
`Media
`
`Abstract:
`The increased bandwidth in the Internet puts great demands on network routers; for example, to route minimum sized Gigabit Ethernet packets, an
`IP router must process about 1.5/spl times/10/sup 6/ packets per second per port. Using the "rule-of-thumb" that it takes roughly 1000 packets per
`second for every 10/sup 6/ bits per second of line rate, an OC-192 line requires 10/spl times/10/sup 6/ routing lookups per second; well above
`current router capabilities. One limitation of router performance is the route lookup mechanism. IP routing requires that a router perform a longest-
`prefix-match address lookup for each incoming datagram in order to determine the datagram's next hop. We present a route lookup mechanism
`that when implemented in a pipelined fashion in hardware, can achieve one route lookup every memory access. With current 50 ns DRAM, this
`corresponds to approximately 20/spl times/10/sup 6/ packets per second; much faster than current commercially available routing lookup
`schemes. We also present novel schemes for performing quick updates to the forwarding table in hardware. We demonstrate using real routing
`update patterns that the routing tables can be updated with negligible overhead to the central processor.
`
`Published in: INFOCOM '98. Seventeenth Annual Joint Conference of the IEEE Computer and Communications Societies. Proceedings. IEEE
`
`Date of Conference: 29 March-2 April 1998
`
` INSPEC Accession Number: 6004783
`
`Date Added to IEEE Xplore: 06 August 2002
`
`DOI: 10.1109/INFCOM.1998.662938
`
` ISBN Information:
`
`Print ISSN: 0743-166X
`
` Download PDF
`
`
`
`Publisher: IEEE
`
`This article is only available in PDF.
`Read document
`
`
`
`
`
`http://ieeexplore.ieee.org/document/662938/[4/20/2017 11:42:28 AM]
`
`
`
`
`
`
`
`
`
`

`

`Routing lookups in hardware at memory access speeds - IEEE Xplore Document
`
` Download Citations
`
`View References
`
`Keywords
`
` Email
`
` Print
`
` Request Permissions
`
` Export to Collabratec
`
` Alerts
`
`IEEE Keywords
`Routing, Hardware, Random access memory, Costs, Spine, Laboratories, Bit rate, Internet,
`Ethernet networks, Uninterruptible power systems
`
`INSPEC: Controlled Indexing
`pipeline processing, telecommunication network routing, Internet, packet switching, transport
`protocols, table lookup, DRAM chips
`
`INSPEC: Non-Controlled Indexing
`50 ns, memory access speeds, IP routing lookups, bandwidth, Internet, network routers, Gigabit
`Ethernet packets, longest-prefix-match address lookup, OC-192 line, router performance,
`datagram, pipelined hardware implementation, DRAM, routing update patterns, forwarding table
`updates, routing tables, central processor
`
`Abstract
`
`Authors
`
`Figures
`
`References
`
`Citations
`
`Keywords
`
`Back to Top
`
`Authors
`
`P. Gupta
`Comput. Syst. Lab., Stanford Univ., CA, USA
`
`S. Lin
`
`N. McKeown
`
`Related Articles
`
`Using multiple hash functions to improve IP lookups
`A. Broder; M. Mitzenmacher
`
`RR-TCP: a reordering-robust TCP with DSACK
`Ming Zhang; B. Karp; S. Floyd; L. Peterson
`
`High-performance IP routing table lookup using CPU caching
`T. Chiueh; P. Pradhan
`
`A passive approach for detecting shared bottlenecks
`D. Katabi; I. Bazzi; Xiaowei Yang
`
`Beyond TCAMs: An SRAM-Based Parallel Multi-Pipeline Architecture for Terabit IP Lookup
`W. Jiang; Q. Wang; V. K. Prasanna
`
`Fast incremental updates for pipelined forwarding engines
`A. Basu; Girija Narlikar
`
`Optimal routing table design for IP address lookups under memory constraints
`G. Cheung; S. McCanne
`
`A fast IP routing lookup scheme for gigabit switching routers
`Nen-Fu Huang; Shi-Ming Zhao; Jen-Yi Pan; Chi-An Su
`
`http://ieeexplore.ieee.org/document/662938/[4/20/2017 11:42:28 AM]
`
`

`

`Routing lookups in hardware at memory access speeds - IEEE Xplore Document
`
`An IP packet forwarding technique based on partitioned lookup table
`M.J. Akhbarizadeh; M. Nourani
`
`Scalable High Throughput and Power Efficient IP-Lookup on FPGA
`Hoang Le; Viktor K. Prasanna
`
`
`
`IEEE Account
`
` Purchase Details
`
` Profile Information
`
` Need Help?
`
`» Change Username/Password
`» Update Address
`
`» Payment Options
`» Order History
`» View Purchased Documents
`
`» Communications Preferences
`» Profession and Education
`» Technical Interests
`
`» US & Canada: +1 800 678 4333
`» Worldwide: +1 732 981 0060
`» Contact & Support
`
`
` Welcome Charles Koch My Account
`|
`
`
`|
`
`Sign Out
`
`
`About IEEE Xplore Contact Us
`|
`
`
`|
`
`Help
`
`
`|
`
`Terms of Use
`
`
`|
`
`Nondiscrimination Policy
`
`
`|
`
`Sitemap
`
`
`|
`
`Privacy & Opting Out of Cookies
`
`A not-for-profit organization, IEEE is the world's largest technical professional organization dedicated to advancing technology for the benefit of humanity.
`© Copyright 2017 IEEE - All rights reserved. Use of this web site signifies your agreement to the terms and conditions.
`
`http://ieeexplore.ieee.org/document/662938/[4/20/2017 11:42:28 AM]
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket