`
`'072 Patent Claim2
`(P.R. 3-1(a))
`comprising transferring status
`information for the context to the
`interface device during the same
`operation as transferring protocol header
`information to the interface device.
`
`Alacritech Inc.’s Patent Initial Disclosures For Cavium
`Exhibit 2
`
`Accused Instrumentalities And Where Each Claim Element Is Found3
`(P.R. 3-1(b)-(c))
`
`
`Cavium has committed and continues to commit acts of infringement of claim 2 under 35 U.S.C. § 271 in connection with Cavium’s
`Accused Instrumentalities.
`
`Cavium’s Accused Instrumentalities, as used and tested in connection with a server or computer, perform the method of claim 1. See
`[072.1]-[072.1f], supra. In addition, the Cavium Accused Instrumentalities, as used and tested in connection with a server or computer,
`are capable of transferring status information for the context to the interface device during the same operation as transferring protocol
`header information to the interface device.
`
`On information and belief, in connection with infringing LSO functionality, the network controller of each of the Cavium Accused
`Instrumentalities transfers status information for the context from the host computer to local memory during the same operation as
`transferring the protocol header information. For example, on information and belief, the network controller DMA transfers the pseudo
`header (also called a prototype header) containing both status information for the context (e.g., Acknowledgment and Sequence numbers)
`and protocol header information.
`
`See, e.g., 8262-k Datasheet, BATES ALA00007608-7611, at p. 3, describing support for large and giant send offload (LSO, GSO), which
`constitutes infringing LSO functionality.13
`
`
`
`13 See also supra note 7.
`
`06973-00001/8965561.2
`
`
`55
`
`
`Alacritech, Inc. v. CenturyLink Inc., et al.,
`(EDTX, Case No. 2:16-cv-00693-JRG-RSP)
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
