throbber
FACEBOOK, INC., INSTAGRAM, LLC, and WHATSAPP INC.,
`Petitioners
`
`v.
`
`BLACKBERRY LIMITED,
`Patent Owner
`
`IPR2019-00942
`U.S. Patent No. 8,677,250
`
`Patent Owner’s Demonstratives
`
`Hearing: September 8, 2020
`
`1
`
`BlackBerry Exhibit No. 2009
`IPR2019-00942
`
`

`

`Overview of ‘250 Patent
`
`Overview of ’250 Patent
`
`

`

`Overview of the ’250 Patent
`
`Ex. 1001 (’250 Patent)
`
`3
`
`

`

`Overview of the ’250 Patent
`
`Ex. 1001 (’250 Patent)
`
`4
`
`

`

`Overview of the ’250 Patent
`
`Ex. 1001 (’250 Patent) at 1:44-58
`
`5
`
`

`

`Overview of the ’250 Patent
`
`Ex. 1001 (’250 Patent) at FIG. 7B; 10:60-11:4
`
`6
`
`

`

`Overview of the ’250 Patent
`
`Ex. 1001 (’250 Patent) at FIG. 5B; 10:8-15
`
`7
`
`

`

`Overview of the ’250 Patent
`
`Ex. 1001 (’250 Patent) at FIG. 5B, 6B, 8B
`
`8
`
`

`

`Overview of Petitioners’ Ground
`
`Ground
`
`References
`
`Ground 1:
`Claims 1, 4, 5, 6, 8, 9, 12, 13, 14
`
`Galli, Crane, Miyaji
`
`9
`
`

`

`Overview of Prior Art: Galli
`
`

`

`Overview of Prior Art: Galli
`
`Ex. 1003 (Galli)
`
`11
`
`

`

`Overview of Prior Art: Galli
`
`Ex. 1003 (Galli) at FIG. 4, 5A
`
`12
`
`

`

`Overview of Prior Art: Crane
`
`

`

`Overview of Prior Art: Crane
`
`Ex. 1004 (Crane) at FIG. 8, 7:25-31
`
`14
`
`

`

`Overview of Prior Art: Crane
`
`Ex. 1004 (Crane) at 19:5-24
`
`15
`
`

`

`Overview of Prior Art: Crane
`
`Ex. 1004 (Crane) at Fig. 6, 13:9-20
`
`16
`
`

`

`Overview of Prior Art: Miyaji
`
`

`

`Overview of Prior Art: Miyaji
`
`Ex 1005 (Miyaji)
`
`18
`
`

`

`Overview of Prior Art: Miyaji
`
`Ex 1005 (Miyaji) at Fig. 4, ¶ 7-9
`
`19
`
`

`

`Petitioners’ Prior Art Combination Does Not “Utilize
`a Contact List...by Identifying Game Play in the
`Contact List”
`
`

`

`Claim 1: “Utilize a Contact List . . . By Identifying Game Play in the Contact List”
`
`Ex. 1001 (’250 Patent)
`
`21
`
`

`

`Claim 1: “Utilize a Contact List . . . By Identifying Game Play in the Contact List”
`
`Paper 30 (Petitioners’ Reply) at 2
`
`22
`
`

`

`Claim 1: “Utilize a Contact List . . . By Identifying Game Play in the Contact List”
`
`Ex. 1001 (‘250 Patent) at 12:3-16, 12:56-64
`
`23
`
`

`

`Claim 1: “Utilize a Contact List . . . By Identifying Game Play in the Contact List”
`
`Ex. 1003 (Galli) at FIG. 5A, ¶ 41
`
`24
`
`

`

`Claim 1: Petitioners Attempt to Combine Galli, Crane, and Miyaji
`
`Paper 30 (Petitioners’ Reply) at 24
`
`25
`
`

`

`Claim 1: No Motivation to Combine Galli with Turn-Based Game Applications
`
`Galli:
`
`Crane:
`
`Miyaji:
`
`Paper 22 (POR) at 10
`
`V.
`
`Ex. 1004 (Crane)
`
`Galli’s applications are different from turn-based games:
`
`Paper 30 (Petitioners’ Reply) at 13-14
`
`Paper 30 (Petitioners’ Reply) at 11
`
`26
`
`

`

`Claim 1: No Motivation to Combine Galli with Turn-Based Game Applications
`
`Petitioners’ expert confirmed the difference
`
`Petitioners’ expert explained the difference:
`simultaneous v. waiting “longer period” for your turn
`
`Ex. 2008 (Chatterjee Tr.) at 84:20-85:9
`
`Ex. 1019 (Chatterjee Reply Decl.) ¶ 26
`
`27
`
`

`

`Claim 1: No Motivation to Combine References as Petitioners Propose
`
`Ex. 1003 (Galli) at FIG. 4
`
`28
`
`

`

`Claim 1: No Motivation to Combine References as Petitioners Propose
`
`Ex. 1003 (Galli)
`
`29
`
`

`

`Claim 1: No Motivation to Combine References as Petitioners Propose
`
`Ex. 1004 (Crane) at FIG. 8, 7:25-31
`
`30
`
`

`

`Claim 1: No Motivation to Combine References as Petitioners Propose
`
`Ex. 1004 (Crane) at 19:5-24
`
`31
`
`

`

`Claim 1: No Motivation to Combine References as Petitioners Propose
`
`Ex 1005 (Miyaji) at Fig. 4, ¶ 7-9
`
`32
`
`

`

`Petitioners’ Prior Art Combination Does Not
`“Display[] at Least One Instant Message . . . Indicative
`of Game Progress”
`
`

`

`Claim 1: “Displaying At Least One Instant Message . . . Indicative of Game Progress”
`
`Ex. 1001 (’250 Patent) at Claim 1
`
`34
`
`

`

`Galli Does Not Display an “Instant Message . . . Indicative of Game Progress”
`
`Ex. 1003 (Galli) at FIG. 4, ¶ 55
`
`35
`
`

`

`Crane’s Email Game Packets Are Not Displayed in Any Conversation
`
`Ex. 1004 (Crane) at Fig. 6, 13:9-20
`
`36
`
`

`

`Crane’s IM Game Packets Are Not Displayed in an IM Conversation
`
`Ex. 1004 (Crane) at FIG. 8, 7:25-31
`
`37
`
`

`

`Petitioners’ Attempt to Disavow Crane’s IM Embodiment
`
`Paper 30 (Petitioners’ Reply) at 15
`
`38
`
`

`

`Combining Galli and Crane Would Not Render Claim 1 Obvious
`
`Ex. 1003 (Galli) at FIG. 4; Ex. 1004 (Crane) at FIG. 8
`
`39
`
`

`

`Combining Galli and Crane Would Not Render Claim 1 Obvious
`
`Ex. 1004 (Crane) at 19:5-24
`
`40
`
`

`

`Petitioners’ Prior Art Combination Does Not
`“Maintain[] the Game Progress Data”
`
`

`

`Claims 6 & 14: “Maintaining the Game Progress Data”
`
`Ex. 1001 (’250 Patent) at Claims 6, 14
`
`42
`
`

`

`Claims 1, 5, & 6
`
`Claims 1, 5, & 6
`
`
`
`
`
`5S. The method according to claim 4, further compri sing
`.
`.
`.
`.
`.
`displaying the game 1n progress user interface upon detecting
`selection of the contactlist entry associated with the game in
`progress.
`
`6. The method according to claim 5, further comprising
`.
`“os
`:
`:
`maintaining, the game progress data upon switching away
`:
`.
`from the gamein progressuserinterface to enable the game in
`progress to be resumed upon a re-invocation of the game in
`.
`progress user interface.
`
`Ex. 1001 (’250 Patent) at Claims 1, 5, 6
`Ex. 1001 (’250 Patent) at Claims 1, 5, 6
`
`
`
`43
`
`to the gamein progress.
`
`1. A method of enabling a game to be played on an elec-
`tronic device, the method comprising:
`enabling a game application on the electronic device to
`utilize a contactlist for an instant messaging application
`for playing games with contacts in the contact list by
`identifying game play in the contactlist;
`during a game in progress with a particular contact in the
`contact list, preparing game messagesto be sent to the
`particular contact by including gameprogress data in an
`instant messaging message and an identifier to associate
`vet
`the data with the gameapplication;
`communicatingatleast one game message during the game
`in progress with the particular contact using an instant
`messaying system used by the instant messayiny applhi-
`cation:
`displaying at least one instant message in an instant mes-
`saging conversation user interface associated with the
`particular contact
`indicative of game progress,
`the
`instant messaging conversation user interface enabling
`additional instant messages to be sent to the particular
`contact in addition to instant messages indicating game
`play; and
`displaying a game in progress user interface associated
`with the game play, after detecting a selection in the
`instant Messaging conversation user interface to switch
`
`

`

`Claims 6 & 14: “Maintaining the Game Progress Data”
`
`Ex. 1001 (’250 Patent) at 8:35-44
`
`44
`
`

`

`Claims 6 & 14: “Maintaining the Game Progress Data”
`
`Ex. 1001 (’250 Patent) at Claims 1-3, 5-6
`
`45
`
`

`

`Claims 6 & 14: “Maintaining the Game Progress Data”
`
`Paper 30 (Petitioners’ Reply) at 23; Ex. 2008 (Chatterjee Tr.) at 99:2-7
`
`46
`
`

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