throbber
McGee, Sheldon
`
`Subject:
`
`FW: IPR2022-01197 (U.S. Patent No. 6,816,809)- Request for Reply to POPR
`

`From: Zhong, Annita <HZhong@irell.com>  
`Sent: Thursday, November 3, 2022 1:19 PM 
`To: Blaine.Hackman@WolfGreenfield.com; Trials <Trials@USPTO.GOV> 
`Cc: RGiunta‐PTAB@WolfGreenfield.com; BHackman‐PTAB@WolfGreenfield.com; Gregory F. Corbett 
`<Gregory.Corbett@WolfGreenfield.com>; Proctor, Amy <AProctor@irell.com>; Sheasby, Jason <JSheasby@irell.com>; 
`sobrien@hilgersgraben.com 
`Subject: RE: IPR2022‐01197 (U.S. Patent No. 6,816,809)‐ Request for Reply to POPR 

`CAUTION: This email has originated from a source outside of USPTO. PLEASE CONSIDER THE SOURCE before responding, clicking on 
`links, or opening attachments. 

`Dear Board, 
`
`  
`Petitioner has not circulated the email to Patent Owner beforehand, so Patent Owner is unable to insert its position.  In 
`particular, Patent Owner asked Petitioner why it believed the issues could not be addressed by existing briefing and 
`Petitioner declined to explain its reasoning.  Patent Owner submits that based especially on the email below, Petitioner 
`appears to have already addressed the relevant issues in the petition and there are therefore no good cause to file a 
`reply.   
`
`  
`Respectfully, 
`
`  
`H. Annita Zhong 
`Irell & Manella LLP 
`1800 Avenue of the Stars, Suite 900 
`Los Angeles, CA 90067‐4276 
`Telephone: (310) 203‐7183 
`Fax:  (310) 556‐5385 
`
`  
`From: Blaine.Hackman@WolfGreenfield.com <Blaine.Hackman@WolfGreenfield.com>  
`Sent: Thursday, November 3, 2022 10:08 AM 
`To: 'Trials' <Trials@USPTO.GOV> 
`Cc: RGiunta‐PTAB@WolfGreenfield.com; BHackman‐PTAB@WolfGreenfield.com; Gregory F. Corbett 
`<Gregory.Corbett@WolfGreenfield.com>; Zhong, Annita <HZhong@irell.com>; Proctor, Amy <AProctor@irell.com>; 
`Sheasby, Jason <JSheasby@irell.com>; sobrien@hilgersgraben.com 
`Subject: IPR2022‐01197 (U.S. Patent No. 6,816,809)‐ Request for Reply to POPR 
`
`  
`
`Dear Honorable Board, 
`
`Petitioner Google respectfully requests a conference call to seek authorization to file a six‐page Reply to the Patent 
`Owner Preliminary Response (“POPR”) in IPR2022‐01197 to refute: 
`
`1. the POPR’s argument that neither Ogawa nor Vea discloses hardware based metering because their hardware 
`components are reliant on characteristics of software running on the processor (POPR, 11 and 43‐44), which is 
`
`1
`
`

`

`inconsistent with the specification’s disclosure of a hardware based metering device that is reliant on particular 
`software (a modified operating system) running on the processor (e.g., ’809 Patent at 4:36‐57, claim 4; see also 
`Petition at 5, 22, 56, 63); 
`
`2. the POPR’s assertion that because Ogawa’s counter 4 does not stop counting in response to the CLR1 signal 
`when the program stops running Ogawa does not increment a counter based on the time the processor is busy 
`as claimed (POPR, 16, 24), where the Petition explained that the value of counter 4 is loaded into register 5 in 
`response to CLR1 and that “the ‘content’ of register 5 indicates ‘the effective processing time of the [CPU] 1’” 
`(Petition, 12) when the periodic program is the only program running on the processor (Petition, 14); 
`
`3. the POPR’s allegation that an EP counterpart of Vea being cited in an IDS but never commented on by the 
`examiner is a basis for discretionary denial under § 325 (d), where this argument is inconsistent with multiple 
`Board cases Google proposes to cite and further ignores that Vea was used to reject claims of similar scope to 
`those in the ’809 Patent in a continuation thereof (Petition at 41‐42, n9 (citing Ex. 1014)); and 
`
`4. the POPR’s mischaracterization of the Petition as pointing to a data consumer that calculates CPU utilization as 
`the alleged data usage provider (POPR, 51), where the Petition instead identified Vea’s data usage provider as a 
`system component that stores the output of Vea’s frequency counter and makes its “history” available to a 
`different component to perform CPU utilization calculations (Petition, 54). 
`
`Petitioner is prepared to demonstrate on the call that good cause exists for the Reply.  If Petitioner’s request is granted, 
`Petitioner would not oppose Patent Owner being granted a same‐length sur‐reply.  
`
`The parties have met and conferred and Patent Owner opposes the request.  Petitioner’s counsel is available the week 
`of November 7 at the Board’s convenience.  Patent Owner’s counsel stated they “may be available Tuesday and 
`Wednesday between 7‐9 a.m. PT.”   
`
`Respectfully submitted, 
`
`Blaine M. Hackman, Reg. No. 67,479 
`
`  
`  
`
`
`
`
`
`Blaine Hackman 
`Counsel
`Admitted to Practice in NY 
`212.849.3352 
`646.552.5261 
`Wolf, Greenfield & Sacks, P.C.
`600 Atlantic Avenue | Boston, MA 02210 
`605 Third Avenue | New York, NY 10158 
`Blaine.Hackman@WolfGreenfield.com | wolfgreenfield.com |  
`This e-mail message and any attachments may contain confidential or privileged information. If you are not the intended recipient, please notify me
`immediately by replying to this message. Please destroy all copies of this message and any attachments. Thank you. 
`  



`PLEASE NOTE: This message, including any attachments, may include privileged, confidential and/or inside information. 
`Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and 
`may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then 
`delete it from your system. Thank you. 
`
`2
`
`

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