throbber

`
`
`
`
`
`Google LLC
`Petitioner
`v.
`AGIS Software Development, LLC
`Patent Owner
`____________
`
`IPR2018-01079 (Patent No. 8,213,970)
`
`
`September 5, 2019
`
`1
`
`Google EX1026
`Google v. AGIS
`IPR2018-01079
`
`

`

`Instituted Grounds
`
`Patent
`
`Instituted
`Grounds
`
`Claims
`
`Reference(s)
`
`’970
`
`Ground 1
`
`Ground 2
`
`Ground 3
`
`1 and 3-9
`
`1 and 3-9
`
`1 and 3-9
`
`Kubala and Hammond
`Hammond, Johnson, and
`Pepe
`Hammond, Johnson, Pepe,
`and Banerjee
`
`2
`
`

`

`Agenda
`
`Whether the prior art teaches or suggests:
`
`
`POR, 14-28.
`
`• “forced message alert”
`
`• “forced message alert software packet”
`
`• “in order to clear recipient’s response list”
`
`• “displaying a listing”
`
`POR, 28-31.
`
`POR, 22.
`
`POR, 22-27.
`
`3
`
`

`

`“Forced Message Alert”
`
`Kubala teaches a “forced message alert”
`
`EX1005, Kubala, FIG. 2; see also Pet., 26-32.
`
`4
`
`

`

`“Forced Message Alert”
`
`AGIS says:
`
`1. Reads limitations into “forced”
`
`2. Prior art teaches “forced”
`
`POR, 15.
`
`5
`
`

`

`1. AGIS’s Argument Reads Limitations into “Forced”
`
`Claim language:
`
`EX1001, ’970 Patent, 9:14-23; see also Pet. Reply, 3-6 .
`
`6
`
`

`

`1. AGIS’s Argument Reads Limitations into “Forced”
`
`Structure in specification:
`
`EX1001, ’970 Patent, 8:37-44;
`see also POR, 17; Pet. Reply, 4-6.
`
`7
`
`

`

`2. Kubala teaches the claimed “forced” message
`
`Kubala’s ¶[0009]:
`
`EX1005, Kubala, ¶[0009]; see also Pet., 30-32.
`
`8
`
`

`

`2. Kubala teaches the claimed “forced” message
`
`Kubala’s ¶[0054]:
`
`EX1005, Kubala, ¶[0054]; see also Pet. 30-32.
`
`9
`
`

`

`2. Kubala teaches the claimed “forced” message
`
`Kubala’s ¶[0055]:
`
`Ex. 1005, Kubala, ¶[0055]; see also Pet. 30-32.
`
`10
`
`

`

`2. Kubala teaches the claimed “forced” message
`
`Kubala’s ¶[0059]:
`
`EX1005, Kubala, ¶[0059]; see also Pet., 30-32.
`
`11
`
`

`

`2. Kubala teaches the claimed “forced” message
`
`Hammond:
`
`EX1006, Hammond, Abstract; see also Pet., 58-59.
`
`12
`
`

`

`2. Johnson also teaches a “forced” message
`
`Johnson:
`
`EX1007, Johnson, 4:3-17; see also Pet., 60.
`
`13
`
`

`

`Agenda
`
`Whether the prior art teaches or suggests:
`
`
`POR, pp. 14-28.
`
`• “forced message alert”
`
`• “forced message alert software packet”
`
`• “in order to clear recipient’s response list”
`
`• “displaying a listing”
`
`POR, pp. 28-31.
`
`POR, p. 22.
`
`POR, pp. 22-27.
`
`14
`
`

`

`“Forced Message Alert Software Packet”
`
`Petition
`
`Pet., 60.
`
`15
`
`

`

`“Forced Message Alert Software Packet”
`
`Institution Decision
`
`Institution Decision, 30.
`
`Institution Decision, 36.
`
`16
`
`

`

`“Forced Message Alert Software Packet”
`
`Petitioner’s Reply:
` construed the term
`
`Pet. Reply, 1.
`
`17
`
`

`

`“Forced Message Alert Software Packet”
`
`Petitioner’s Reply:
`mapped construction to prior art
`
`Pet. Reply, 1-2.
`
`18
`
`

`

`Hammond teaches a “forced message alert software packet”
`
`Hammond’s message delivery
`information is the claimed “packet”
`
`EX1006, Hammond, 3:31-43; see also Pet., 60; Pet. Reply, 19.
`
`19
`
`

`

`Johnson teaches a “forced message alert software packet”
`
`Johnson’s persistent reply attributes
`are the claimed “packet”
`
`EX1007, Johnson, 4:3-6; see also Pet., 60; Pet. Reply, 19.
`
`EX1007, Johnson, 4:25-32; see also Pet., 60; Pet. Reply, 19.
`
`20
`
`

`

`Agenda
`
`Whether the prior art teaches or suggests:
`
`
`POR, pp. 14-28.
`
`• “forced message alert”
`
`• “forced message alert software packet”
`
`• “in order to clear recipient’s response list”
`
`• “displaying a listing”
`
`POR, pp. 28-31.
`
`POR, p. 22.
`
`POR, pp. 22-27.
`
`21
`
`

`

`“In Order to Clear Recipient’s Response List”
`
`Petition
`
`Pet., 31.
`
`Pet., 32.
`
`22
`
`

`

`“In Order to Clear Recipient’s Response List”
`
`AGIS argues:
`
`POR, 22.
`
`23
`
`

`

`“In Order to Clear Recipient’s Response List”
`
`Cited portion of
`Williams Declaration:
`
`EX1003, Williams Decl., ¶109; see also Pet. Reply, 11-12.
`
`24
`
`

`

`Agenda
`
`Whether the prior art teaches or suggests:
`
`
`POR, pp. 14-28.
`
`• “forced message alert”
`
`• “forced message alert software packet”
`
`• “in order to clear recipient’s response list”
`
`• “displaying a listing”
`
`POR, pp. 28-31.
`
`POR, p. 22.
`
`POR, pp. 22-27.
`
`25
`
`

`

`“Displaying a Listing”
`
`Petition relies on Kubala
`
`Pet., 32-33 (discussing limitation 1.7);
`see also Pet., 44 (discussing limitation 6.5).
`
`26
`
`

`

`“Displaying a Listing”
`
`Petition also relies on Hammond
`
`Pet., 32-33.
`
`27
`
`

`

`“Displaying a Listing”
`
`AGIS argues:
`
`
`
`POR, 23.
`
`28
`
`

`

`“Displaying a Listing”
`
`AGIS’s expert admits this argument
`relies on wrong section of petition
`
`EX1022, Carbonell Tr., 57:16-25; see also Pet. Reply, 13-14.
`
`29
`
`

`

`“Displaying a Listing”
`
`AGIS also argues that Hammond
`does not teach this limitation:
`
`
`
`POR, 24; see also Pet. Reply, 15-16.
`
`30
`
`

`

`“Displaying a Listing”
`
`Williams Supplemental Declaration
`
`EX1023, Williams Suppl. Decl., ¶12; see also Pet. Reply, 15-16.
`
`31
`
`

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