throbber

`
`Filed on behalf of: Meta Platforms, Inc.
`
`Filed: November 17, 2023
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`__________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`__________________
`
`META PLATFORMS, INC.
`Petitioner,
`
`v.
`
`ANGEL TECHNOLOGIES GROUP LLC,
`Patent Owner.
`__________________
`Case No. IPR2023-00057
`U.S. Patent No. 8,954,432
`__________________
`
`PETITIONER’S REPLY TO PATENT OWNER’S RESPONSE
`
`
`
`
`
`
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
` Petitioner’s Reply
`
`TABLE OF CONTENTS
`

`

`
`B. 
`
`C. 
`

`
`INTRODUCTION ........................................................................................... 1 
`GROUND 1: SHARPE ALONE OR IN VIEW OF THE
`KNOWLEDGE OF A POSA RENDERS OBVIOUS CLAIMS 1, 3,
`6-8 .................................................................................................................... 1 
`A. 
`Sharpe Alone Or In View Of The Knowledge Of A POSA
`Teaches The “User Unique Identifier” (6[e], 7[a]) ............................... 2 
`Sharpe Alone Or In View Of The Knowledge Of A POSA
`Teaches A “Second Tagging User” (7[a], 7[b], 1[h]) ........................... 4 
`Sharpe Alone Or In View Of The Knowledge Of A POSA
`Teaches Requests For Image Data (8[a], 1[d], 1[e], 1[h], 1[i]) ............ 6 
`PO Misinterprets the Claim Language ........................................ 6 

`Even Under PO’s Incorrect Interpretation, the Prior Art
`Discloses the Limitation ............................................................. 8 
`PO’s Remaining Arguments are Meritless ................................. 8 

`Sharpe Alone Or In View Of The Knowledge Of A POSA
`Teaches The “List of Pictured Users” (8[b], 1[m]) ............................. 10 
`The Petition Plainly Presents Sharpe As A Single-Reference
`Obviousness Ground ........................................................................... 12 
`  GROUND 2: SHARPE IN VIEW OF EINTRACHT RENDERS
`OBVIOUS CLAIMS 1-8 ............................................................................... 17 
`A.  A POSA Would Have Been Motivated To Combine Sharpe
`With Eintracht ..................................................................................... 18 
`PO Fails To Address Eintracht’s Disclosure Of The
`Independent Claims ............................................................................. 20 
`
`D. 
`
`E. 
`
`B. 
`
`i
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
` Petitioner’s Reply
`
`C. 
`
`D. 
`
`Sharpe In View Of Eintracht Teaches “Coordinates” (Claims 2,
`4) .......................................................................................................... 21 
`Sharpe In View Of Eintracht Teaches The Email Notification
`(Claim 5) .............................................................................................. 23 
`  GROUNDS 3 & 4: SHARPE IN VIEW OF CAREY, AND SHARPE
`IN VIEW OF EINTRACHT AND CAREY RENDERS OBVIOUS
`CLAIM 3 ....................................................................................................... 24 
`CONCLUSION .............................................................................................. 24 
`

`
`
`
`ii
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
` Petitioner’s Reply
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`Cases
`Adobe, Inc. v. Realtime Adaptive Streaming LLC,
`No. IPR2019-00712, 2020 WL 4809374 (P.T.A.B. Aug. 17, 2020) .................. 15
`Application of Skoner,
`517 F.2d 947 (C.C.P.A. 1975) ............................................................................ 13
`Arctic Cat Inc. v. Bombardier Recreational Prods. Inc.,
`876 F.3d 1350 (Fed. Cir. 2017) .......................................................................... 14
`B/E Aerospace, Inc. v. C&D Zodiac, Inc.,
`962 F.3d 1373 (Fed. Cir. 2020) ............................................................................ 5
`Beckson Marine, Inc. v. NFM, Inc.,
`292 F.3d 718 (Fed. Cir. 2002) ............................................................................ 19
`Bradium Techs. LLC v. Iancu,
`923 F.3d 1032 (Fed. Cir. 2019) .................................................................... 11, 21
`Dow Jones & Co., Inc. v. Ablaise Ltd.,
`606 F.3d 1338 (Fed. Cir. 2010) ...................................................................... 13, 5
`Elekta Ltd. v. ZAP Surgical Sys., Inc.,
`81 F.4th 1368 (Fed. Cir. 2023) ............................................................... 22, 23, 24
`EWP Corp. v. Reliance Universal Inc.,
`755 F.2d 898 (Fed. Cir. 1985) ............................................................................ 21
`Genentech, Inc. v. Chiron Corp.,
`112 F.3d 495 (Fed. Cir. 1997) .............................................................................. 7
`Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd.,
`821 F.3d 1359 (Fed. Cir. 2016) .......................................................................... 14
`Koninklijke Philips N.V. v. Google LLC,
`948 F.3d 1330 (Fed. Cir. 2020) .......................................................................... 13
`
`iii
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
` Petitioner’s Reply
`
`KSR Int’l Co. v. Teleflex Inc.,
`550 U.S. 398 (2007) .............................................................................................. 3
`M&K Holdings, Inc. v. Samsung Elecs. Co.,
`985 F.3d 1376 (Fed. Cir. 2021) .................................................................... 16, 17
`Maxlite, Inc. v. Jiaxing Super Lighting Elec. Appliance Co., Ltd.,
`No. IPR2020-00208, 2022 WL 1416695 (P.T.A.B. Apr. 29, 2022) ........ 4, 20, 24
`Novartis Pharms. Corp. v. West-Ward Pharms. Int’l Ltd.,
`923 F.3d 1051 (Fed. Cir. 2019) .......................................................................... 22
`Polygroup Ltd. MCO v. Willis Elec. Co., Ltd,
`759 F. App’x 934 (Fed. Cir. 2019) ..................................................................... 15
`Realtime Data, LLC v. Iancu,
`912 F.3d 1368 (Fed. Cir. 2019) .......................................................................... 14
`Smith & Nephew, Inc. v. Ethicon, Inc.,
`276 F.3d 1304 (Fed. Cir. 2001) ............................................................................ 8
`In re Stepan Co.,
`868 F.3d 1342 (Fed Cir. 2017) ..................................................................... 15, 16
`Therasense, Inc. v. Becton, Dickinson & Co.,
`593 F.3d 1325 (Fed. Cir. 2010) .......................................................................... 15
`Ex parte Thomas Lederer,
`No. APPEAL 2012-000270, 2014 WL 4980020 .................................................. 5
`TQ Delta, LLC v. Cisco Sys., Inc.,
`942 F.3d 1352 (Fed. Cir. 2019) ...................................................................... 9, 11
`Other Authorities
`37 C.F.R. § 42.23(b) .................................................................................................. 4
`
`
`
`
`
`
`iv
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
` Petitioner’s Reply
`
`Exhibit
`
`EXHIBIT LIST
`
`Description
`
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`1013
`
`1014
`
`1015
`
`
`
`U.S. Patent No. 8,954,432 (“’432 Patent”)
`
`Prosecution History of U.S. Patent No. 8,954,432 (“’432 FH”)
`
`Declaration of Dr. Benjamin B. Bederson (“Bederson”)
`
`Curriculum Vitae of Dr. Benjamin B. Bederson
`
`U.S. Patent No. 7,461,099 to Sharpe et al. (“Sharpe”)
`
`U.S. Patent No. 6,687,878 to Eintracht et al. (“Eintracht”)
`
`U.S. Patent No. 6,714,793 to Carey et al. (“Carey”)
`
`Prosecution History of U.S. Patent No. 10,628,480 (“’480 FH”)
`
`Excerpt from THE OXFORD AMERICAN DICTIONARY AND LANGUAGE
`GUIDE (1999), at 203 (contact)
`Excerpt from THE AMERICAN HERITAGE DICTIONARY (4th ed. 2001), at
`191 (contact)
`Kuchinsky et al., FotoFile: A Consumer Multimedia Organization and
`Retrieval System, CHI ’99: PROCEEDINGS OF THE SIGCHI
`CONFERENCE ON HUMAN FACTORS IN COMPUTING SYSTEMS, 496-503
`(May 1999) (“FotoFile”)
`Reserved
`
`Reserved
`
`Reserved
`
`Yuichi Yagawa et al., The Digital Album: A Personal File-tainment
`System, PROCEEDINGS OF THE THIRD IEEE INTERNATIONAL
`CONFERENCE ON MULTIMEDIA COMPUTING AND SYSTEMS
`
`v
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
` Petitioner’s Reply
`
`Exhibit
`
`Description
`
`
`
`
`
`1016
`
`1017
`
`1019
`
`1020
`
`1021
`
`(MULTIMEDIA ’96), June 17-23, 1996, at 433-39
`Ben Shneiderman & Hyunmo Kang, Direct Annotation: A Drag-and-
`Drop Strategy for Labeling Photos, 2000 IEEE INTERNATIONAL
`CONFERENCE ON INFORMATION VISUALIZATION (IV ’00), July 19-21,
`2000
`Benjamin B. Bederson et al., Pad++: A Zoomable Graphical
`Sketchpad For Exploring Alternate Interface Physics, 7 J. OF VISUAL
`LANGUAGES & COMPUTING 3 (1996)
`1018 Mark Roseman & Saul Greenberg, Building Real-Time Groupware
`with GroupKit, a Groupware Toolkit, 3 ACM TRANSACTIONS ON
`COMPUTER-HUMAN INTERACTION 1 (Mar. 1996), at 66-106
`Excerpts from ROB KIRKLAND ET AL., DOMINO SYSTEM
`ADMINISTRATION (1999)
`Excerpts from DOROTHY BURKE & JANE CALABRIA, TEN MINUTE
`GUIDE TO LOTUS NOTES 4.6 (1997)
`Elizabeth F. Churchill, et al., Anchored Conversations: Chatting in the
`Context of a Document, CHI ’00: PROCEEDINGS OF THE SIGCHI
`CONFERENCE ON HUMAN FACTORS IN COMPUTING SYSTEMS, April
`2000, at 454-61
`1022 Mark S. Ackerman & David W. McDonald, Answer Garden 2:
`Merging Organizational Memory with Collaborative Help, CSCW
`’96: PROCEEDINGS OF THE 1996 ACM CONFERENCE ON COMPUTER
`SUPPORTED COOPERATIVE WORK, Nov. 1996, at 97-105
`U.S. Patent No. 6,175,831 to Weinreich, et al.
`
`1023
`
`1024
`
`1025
`
`1026
`
`Excerpts from C.J. DATE, AN INTRODUCTION TO DATABASE SYSTEMS
`(6th ed. 1995)
`Excerpts from RANDY JAY YARGER ET AL., MYSQL & MSQL (1st ed.
`1999)
`Ulla Merz & Roger King, DIRECT: A Query Facility for Multiple
`Databases, 12 ACM TRANSACTIONS ON INFORMATION SYSTEMS 4
`(Oct. 1994), at 339-59
`
`vi
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
` Petitioner’s Reply
`
`Exhibit
`
`Description
`
`1027
`
`1028
`
`1029
`
`1030
`
`1031
`
`1032
`
`1033
`
`1034
`
`1035
`
`1036
`
`1037
`
`1038
`
`1039
`
`1040
`
`1041
`
`1042
`
`Excerpts from CHARLES DYE, ORACLE DISTRIBUTED SYSTEMS (1999)
`
`Reserved
`
`Reserved
`
`Reserved
`
`Reserved
`
`Reserved
`
`Reserved
`
`Reserved
`
`Reserved
`
`Board correspondence with Petitioner dated Feb. 24, 2023
`
`Declaration of Eric E. Lancaster in support of Petitioner’s motion for
`pro hac vice admission dated June 14, 2023
`
`Declaration of Sara L. Townsend in support of Petitioner’s motion
`for pro hac vice admission dated June 14, 2023
`
`Declaration of Dr. Benjamin B. Bederson in Support of Petitioner’s
`Reply (“Bederson Reply”)
`
`Deposition transcript of Dr. Eli Saber dated Oct. 20, 2023 (Vol. I)
`
`Reserved
`
`Gilles Falquet, et al., Generating Hypertext Views on Databases,
`ACTES DU XIVÈME CONGRÈS INFORSID 269, 269-84 (1996)
`
`1043
`
`Excerpts from APPLE COMPUTER, INC., MACINTOSH HUMAN
`
`vii
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
` Petitioner’s Reply
`
`INTERFACE GUIDELINES (1992)
`
`1044
`
`1045
`
`Excerpts from MICROSOFT PROFESSIONAL REFERENCE, THE
`WINDOWS INTERFACE GUIDELINES FOR SOFTWARE DESIGN (1995)
`
`Beverly L. Harrison & Kim J. Vicente, An Experimental Evaluation
`of Transparent Menu Usage, CHI ’96: PROCEEDINGS OF THE SIGCHI
`CONFERENCE ON HUMAN FACTORS IN COMPUTING SYSTEMS, April
`2000, at 391-398
`
`
`
`
`
`
`
`
`viii
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`
`
`INTRODUCTION
`The Petition established that the claims of the ’432 Patent would have been
`
`obvious over Sharpe alone or in view of Eintracht and/or Carey. PO cannot establish
`
`otherwise. Indeed, PO does not even dispute that the asserted prior art discloses the
`
`purported point of novelty that the Applicant belatedly inserted, at the Examiner’s
`
`suggestion, after over a decade of prosecution—i.e., the claimed three separate and
`
`distinct databases. PO also no longer attempts to swear behind the asserted prior art,
`
`abandoning the failed position it took in its Preliminary Response.
`
`Instead, PO now resorts to a patchwork of mischaracterizations of fact and
`
`misstatements of law to argue that the asserted prior art does not disclose various
`
`non-novel claim limitations. None of its arguments have merit. PO’s last-ditch
`
`arguments fail to properly consider the asserted prior art references for all that they
`
`teach, and would improperly reduce the POSA to a robotic automaton devoid of any
`
`common sense. The Board should reject PO’s arguments and find all challenged
`
`claims unpatentable.
`
` GROUND 1: SHARPE ALONE OR IN VIEW OF THE KNOWLEDGE
`OF A POSA RENDERS OBVIOUS CLAIMS 1, 3, 6-8
`For Ground 1, PO’s Response relies on mischaracterizations of Petitioner’s
`
`arguments and the asserted references. POR 18-45. PO also disputes the Petition’s
`
`identification of Sharpe as a single-reference obviousness ground. Id., 46-51. As
`
`explained below, none of PO’s arguments have merit.
`
`1
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`A.
`
`Sharpe Alone Or In View Of The Knowledge Of A POSA Teaches
`The “User Unique Identifier” (6[e], 7[a])
`Sharpe teaches the claimed user unique identifier through its username.
`
`Pet. 29-32. As explained in the Petition, a POSA would have understood that
`
`Sharpe’s database system uses a primary key to uniquely identify users in its
`
`database, and a POSA would have recognized Sharpe’s username as “the most
`
`obvious design choice” for implementing the primary key in view of Sharpe’s
`
`disclosures. Id.
`
`In response, PO attacks a straw man. See POR 18-24. According to PO,
`
`Petitioner has presented an inherency argument that must fail because there are other
`
`ways for a POSA to implement a primary key in Sharpe. See, e.g., id., 20
`
`(“Petitioner’s argument is flawed because the mere fact that the user name might be
`
`used in the manner described in the Petition is insufficient for demonstrating
`
`inherency.” (first emphasis original)).1
`
`PO’s straw-man inherency argument rests on a mischaracterization of the
`
`Petition, which never argues that Sharpe’s system must use the username as unique
`
`user identifier. See, e.g., Saber ¶80 (“It appears that Petitioner and Dr. Bederson are
`
`saying that Sharpe’s system must use the user name … as a unique identifier or
`
`‘primary key.’”). Rather, the Petition establishes that the username would have been
`
`
`1 All emphasis added unless otherwise indicated.
`
`2
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`an obvious design choice for a primary key in view of Sharpe’s teachings and the
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`knowledge of a POSA. See, e.g., Pet. 24-25, 31-32.
`
`As Dr. Bederson explained, a username is not the only possible choice, but
`
`the most obvious design choice in view of Sharpe’s teachings. For example,
`
`Dr. Bederson opined that “a POSA would have further understood that a username
`
`is one such unique identifier.” EX1003 ¶307. He explained that “[u]sernames are
`
`often used as primary keys in database schemas, and the most obvious design choice
`
`for the Sharpe system given that each user already required a username to log on to
`
`the system.” Id.; see also Bederson Reply ¶¶7-9.
`
`PO and its expert appear to agree that a username is one of several potential
`
`user unique identifiers available to a POSA to implement Sharpe’s databases.2 For
`
`example, Dr. Saber does not dispute that a username can be a primary key. Instead,
`
`he opines that the username does not “need” to be the primary key, and that there
`
`are several other ways to keep track of users, such as assigning an internal unique
`
`identifier to each user. See Saber ¶¶80-81. Similarly, PO focuses its argument on
`
`“another possible way” to implement Sharpe’s system beyond the username.
`
`POR 20-21. Thus, there appears to be no genuine dispute that a POSA would have
`
`
`2 It was known in the art to utilize usernames as primary keys in database schemas.
`
`Bederson ¶307; Bederson Reply ¶10 (citing EX1042).
`
`3
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`understood Sharpe’s username to be an available design option for implementing
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`Sharpe’s databases. Accordingly, there is no genuine dispute that this limitation
`
`would have been obvious in view of Sharpe’s teachings.3
`
`B.
`
`Sharpe Alone Or In View Of The Knowledge Of A POSA Teaches
`A “Second Tagging User” (7[a], 7[b], 1[h])
`As established in the Petition, it would have been obvious to implement the
`
`claimed tagging features for a second user in view of Sharpe’s disclosure of a
`
`collaborative, multi-user system. Pet. 38-39, 55. PO asserts that the Petition is
`
`“deficient” because it fails to address “additional features not claimed by
`
`limitation 6[e]”—yet PO does not expressly identify the purported “additional
`
`features.” See POR 24-27, 43-44 (addressing 1[h]).
`
`PO appears to rely on the fact that claims 1 and 7 require the identification of
`
`an additional pictured user in the same image by a second user. See POR 25, 44.
`
`But the Petition squarely addressed that requirement. E.g., Pet. 38 (“Accordingly, a
`
`
`3 Even if Sharpe did not teach the “user unique identifier,” Eintracht discloses it.
`
`Pet. 63-64, 68. PO failed to respond to that analysis and has waived any rebuttal.
`
`Maxlite, Inc. v. Jiaxing Super Lighting Elec. Appliance Co., No. IPR2020-00208,
`
`2022 WL 1416695, at *12 n.6 (P.T.A.B. Apr. 29, 2022) (“It is a long-standing
`
`practice in IPR proceedings that arguments not raised in the Patent Owner Response
`
`are waived.”) (citing 37 C.F.R. § 42.23(b)).
`
`4
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`POSA would have understood that a second user could also identify additional users
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`in an image as part of the associated index information used for archival and
`
`retrieval of images in Sharpe’s system, as discussed for 6[e].”). PO’s position,
`
`furthermore, is at odds with its own prior statements. For example, PO argued in its
`
`Preliminary Response that claim 7 is “patentable for the same reasons” as claim 6
`
`without further elaboration. POPR 30.
`
`At bottom, Ground 1 is based on obviousness, and it was well within the skill
`
`of a POSA to implement the features of 6[e], 6[f], and 1[d] for a second user. That
`
`is, it would have been obvious to apply a predictable sequence of nearly identical
`
`software operations to the same image for second user. See Pet. 38-39, 55; see also,
`
`e.g., B/E Aerospace, Inc. v. C&D Zodiac, Inc., 962 F.3d 1373, 1379 (Fed. Cir. 2020)
`
`(modifying prior art combination to include second recess was obvious because it
`
`was “nothing more than the predictable application of known technology”); Ex parte
`
`Thomas Lederer, 2014 WL 4980020, at *3 (P.T.A.B. Sept. 25, 2014) (agreeing that
`
`“it would have been obvious to one of ordinary skill in the art to simply repeat the
`
`search function … a second time”).4
`
`
`4 Even if Sharpe did not teach the “second tagging user,” Eintracht discloses it.
`
`Pet. 70. PO failed to address that analysis and has waived any rebuttal.
`
`5
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`C.
`
`Sharpe Alone Or In View Of The Knowledge Of A POSA Teaches
`Requests For Image Data (8[a], 1[d], 1[e], 1[h], 1[i])
`Sharpe alone or in view of the knowledge of a POSA teaches the “requests”
`
`for image data recited in claims 1 and 8. Pet. 39-40, 44-53, 55. As explained below,
`
`PO’s contentions otherwise are premised on a misinterpretation of the claim
`
`language. See POR 28-32, 36-42, 45. Even under PO’s incorrect interpretation of
`
`the claims, the recited “requests” are taught by the prior art. PO’s remaining
`
`arguments lack merit.
`
`
`PO Misinterprets the Claim Language
`PO asserts that Sharpe fails to disclose the claimed requests for image data
`
`because Sharpe’s image retrieval is not limited to a “specific” or “particular” image.
`
`E.g., POR 31-32. According to PO, Sharpe “finds any and all images matching the
`
`parameters inputted by the user.” Id., 28. Because “multiple images may turn up …
`
`Sharpe does not disclose ‘receiving a request for said image data.’” Id., 32 (second
`
`emphasis original). PO repeats variations of this argument throughout its Response.
`
`See, e.g., POR 36-42, 45.
`
`PO’s argument is premised on a misinterpretation of the claim language. “A
`
`request for said image data” does not require the claimed request to be limited to a
`
`specific or particular image. Rather, “a request for said image data” merely requires
`
`that the request include the image data that was recited earlier in the claim—i.e., the
`
`6
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`one or more images in which one or more users were tagged. Bederson Reply ¶¶13-
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`16.
`
`As an initial matter, the term “image data” is plural and can include multiple
`
`images, based on both plain English and the disclosure of the ’432 Patent itself. See,
`
`e.g., EX1001, 7:8-10 (“Images database 250 receives and stores information about
`
`photos (e.g., image data) uploaded or otherwise made accessible to the network by
`
`users.”). Even if “image data” were limited to a single image, the claims of the
`
`’432 Patent are open-ended “comprising” claims that are not limited to the recited
`
`elements. Instead, “other elements may be added and still form a construct within
`
`the scope of the claim.” Genentech, Inc. v. Chiron Corp., 112 F.3d 495, 501 (Fed.
`
`Cir. 1997).
`
`Importantly, PO’s interpretation would exclude the preferred embodiment
`
`disclosed in the ’432 Patent, in which multiple images are returned in response to a
`
`request. For example, in Figure 10 at step 1000, the “client sends a request for
`
`images (or a list of images) wherein a specified user, or several users, have been
`
`identified.” EX1001, 15:46-56, Fig. 10. The ’432 Patent explains that—just as in
`
`Sharpe—a user may search for several tagged users simultaneously, and the results
`
`may include multiple images with varying numbers of tagged users. See id., 15:56-
`
`16:4. Accordingly, the Board should reject PO’s incorrect interpretation. See Smith
`
`& Nephew, Inc. v. Ethicon, Inc., 276 F.3d 1304, 1309-10 (Fed. Cir. 2001) (“A claim
`
`7
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`interpretation that would exclude the reasonable practice of the method taught in the
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`patent ‘is rarely the correct interpretation.’”)
`
`
`
`Even Under PO’s Incorrect Interpretation, the Prior Art
`Discloses the Limitation
`Even under PO’s improper narrowing interpretation, the claimed requests are
`
`disclosed by the prior art. For example, Sharpe also explains that the user can use
`
`multiple parameters to narrowly focus a search to “reveal[] a smaller number of
`
`items.” EX1005, 3:29-44. Indeed, Sharpe explains that its system can be used to
`
`retrieve a “specific photograph” by “searching on the event or the person.” Id., 2:21-
`
`24. Thus, a POSA would understand that Sharpe teaches a request for a single,
`
`specific image via its narrowly focused search that returns a single result. Bederson
`
`Reply ¶¶17-18.5
`
`
`PO’s Remaining Arguments are Meritless
`PO tacks on two meritless arguments. PO asserts that Sharpe fails to disclose
`
`that “said request” contains “said image identification,” and that the “said request”
`
`also lacks “the user identification of said first tagging user.” POR 40-41.
`
`Regarding the request including “said image identification,” the Petition
`
`establishes that a POSA would understand that Sharpe’s trail request includes an
`
`
`5 Eintracht also discloses the limitation under PO’s improper narrowing
`
`interpretation, as explained below. See infra, 20-21.
`
`8
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`image identifier—as PO acknowledges. Id. (citing Pet. 49-50). PO responds in
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`conclusory fashion that “a request to retrieve a trail” is not “a request to identify
`
`users.” Id., 41. Neither PO nor its expert explain why Sharpe’s trail request is
`
`somehow distinct from a request to identify users. PO’s expert only offers the same
`
`conclusory statement verbatim, with no further explanation. Saber ¶100. PO’s
`
`argument is unsupported by any evidence and thus entitled to no weight. TQ Delta,
`
`LLC v. Cisco Sys., Inc., 942 F.3d 1352, 1358-59 (Fed. Cir. 2019).
`
`In any event, PO’s first argument is meritless. Sharpe’s trail request is a
`
`“request to identify users” because the user can continue to tag additional individuals
`
`after retrieving the photos of a trail. Bederson Reply ¶¶19-20. As explained in the
`
`Petition, Sharpe uses the same UI (Figure 4) for both retrieval and archival. Id.; see
`
`also Pet. 39-42, 44-51. A user of Sharpe’s system first retrieves images into the
`
`work space 51 of Figure 4 in order to tag and archive those images. Bederson Reply
`
`¶20. Sharpe explains that trail items are identified and displayed as part of Sharpe’s
`
`retrieval process. EX1005, 9:20-27, Fig. 7 (steps 93-94). Thus, a POSA would have
`
`understood that, following the retrieval of a trail, the photos of a trail are available
`
`for additional tagging using the archival controls of Figure 4. Bederson Reply ¶20.
`
`Regarding the request including “the user identification,” a POSA would have
`
`understood that Sharpe’s request includes a username to identify the requesting user
`
`and retrieve images corresponding to the user’s group. Pet. 49. PO acknowledges
`
`9
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`that Sharpe includes usernames for that purpose, but then asserts that Sharpe’s drop-
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`down box 55 of Figure 4 includes personal names, not usernames. POR 41. The
`
`relevance of PO’s argument is unclear, but in any event, PO appears to be improperly
`
`importing limitations into its claims. Claim 1[d] only requires that the request
`
`include the user identification of the first tagging user. Claim 1[d] does not include
`
`any requirements for the UI used to form the request, so PO’s argument should be
`
`rejected. See Bederson Reply ¶¶21-22.
`
`D.
`
`Sharpe Alone Or In View Of The Knowledge Of A POSA Teaches
`The “List of Pictured Users” (8[b], 1[m])
`Sharpe alone or in view of the knowledge of a POSA teaches the claimed “list
`
`of pictured users” of claims 1 and 8. Pet. 40-42, 58. In particular, the Petition
`
`explains how a POSA would understand that Sharpe updates the drop-down box 55
`
`of Figure 4 to identify the pictured users as various images are retrieved by a viewing
`
`user, including as part of a nostalgic retrieval. Id.
`
`In response, PO and its expert offer little more than “not so.” POR 32-36, 45.
`
`PO insists that the “drop down list is not a list of people pictured in the image; rather,
`
`it is a list of people in the group.” Id., 34. PO explains that “[t]he group members
`
`in the drop down list depicted in Figure 4 of Sharpe would be the same regardless of
`
`which media item was being shown.” Id., 33. PO provides no evidence in support
`
`of its false choice other than the declaration of its expert, who repeats the statements
`
`10
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`nearly verbatim. Saber ¶94. This conclusory testimony is not entitled to any weight.
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`TQ Delta, 942 F.3d at 1358-59.
`
`To the extent that PO contends that Sharpe’s Figure 4 does not expressly show
`
`the list of pictured users, PO fails to appreciate Sharpe “not only for what it expressly
`
`teaches, but also for what it fairly suggests.” Bradium Techs. LLC v. Iancu, 923 F.3d
`
`1032, 1049 (Fed. Cir. 2019). As Dr. Bederson testified, a POSA would have
`
`understood
`
`that Sharpe’s figures are simplified
`
`illustrations
`
`that do not
`
`comprehensively disclose all capabilities of Sharpe’s graphical user interface.
`
`EX2019, 44:14-45:13; see also EX1005, 7:3-6, 9:4-10 (describing UI elements not
`
`shown in Fig. 4); Bederson Reply ¶25. For all the reasons set forth in the Petition,
`
`a POSA would have understood that Sharpe’s UI would update during repeated
`
`searches to show the currently tagged users. Pet. 40-42, 58. PO has offered no
`
`evidence suggesting otherwise.
`
`To the extent that PO argues that Sharpe’s drop-down box 55 cannot be both
`
`a list of people pictured in an image and a list of people in the group, PO is mistaken.
`
`Drop-down boxes that displayed a full set of options (e.g., all users in a group) along
`
`with a selected subset of options (e.g., tagged users from that group) were known in
`
`the art. Bederson Reply ¶¶26-30. For example, by the early 1990s, Apple systems
`
`included drop-down menus that would place a checkmark next to menu items that
`
`were currently selected, as illustrated below:
`
`11
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`
`
`Id. (citing EX1043). Thus, showing a list of pictured users using Sharpe’s drop-
`
`down box 55 would have been a simple matter of design choice to a POSA
`
`implementing Sharpe’s system. Id. To the extent PO argues otherwise, the Board
`
`should reject PO’s unsupported argument.6
`
`E.
`
`The Petition Plainly Presents Sharpe As A Single-Reference
`Obviousness Ground
`PO feigns ignorance as to whether Ground 1 is an anticipation or obviousness
`
`ground. POR 46-51. This argument strains credulity. The Petition plainly and
`
`repeatedly presents Ground 1 as a single-reference obviousness ground: Sharpe
`
`alone or in view of the knowledge of a POSA. See, e.g., Pet. 5 (identification of
`
`challenges), 22 (section heading); see also Bederson ¶¶3, 139. Similar single-
`
`reference obviousness challenges have been repeatedly affirmed by the Federal
`
`
`6 Even if Sharpe did not teach the list of pictured users, Eintracht discloses it.
`
`Pet. 71. PO failed to address that analysis and has waived any rebuttal.
`
`12
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`Circuit. See, e.g., Koninklijke Philips N.V. v. Google LLC, 948 F.3d 1330, 1338-39
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`(Fed. Cir. 2020); Dow Jones & Co., Inc. v. Ablaise Ltd., 606 F.3d 1338, 1351-52
`
`(Fed. Cir. 2010).
`
`PO’s argument is belied by the proceedings in this action. PO was able to
`
`identify Ground 1 as an obviousness ground in its Preliminary Response. See, e.g.,
`
`POPR 35 (“[T]he Board should deny the proposed obviousness combinations in
`
`Grounds I-IV.”). The Board identified Ground 1 as an obviousness ground in the
`
`Institution Decision, and proceeded to analyze the obviousness of claim 6 in view of
`
`Sharpe alone. ID 7, 24-27. PO’s expert also recognized Ground 1 as an obviousness
`
`ground. EX1040, 7:14-8:3.
`
`PO faults the Petition’s use of the term “discloses” as too potent for an
`
`obviousness ground, POR 47, but disclosure is the “ultimate or epitome of
`
`obviousness.” Application of Skoner, 517 F.2d 947, 950 (C.C.P.A. 1975). PO also
`
`contends that the Petition does not set forth any “obviousness modification” to
`
`Sharpe, POR 47, but the Petition repeatedly describes the knowledge and skills that
`
`a POSA would have applied to implement Sharpe—including the implementation of
`
`the primary key and graphical user interface elements that PO disputes in its
`
`Response. See, e.g., Pet. 31-32, 45-51.
`
`PO further asserts that the Petition failed to address reasonable expectation of
`
`success for Ground 1. POR 47. As an initial matter, “[t]he reasonable expectation
`
`13
`
`
`

`

`IPR2023-00057 (USP 8,954,432)
`
`of success requirement refers to the likelihood of success in combining references
`
`
`
`
`
`
`
`
`
`Petitioner’s Reply
`
`to meet the limitations of the claimed invention.” Intelligent Bio-Sys., Inc. v.
`
`Illumina Cambridge Ltd., 821 F.3d 1359, 1367 (Fed. Cir. 2016). There must first be
`
`a proposed combination before there can be a reasonable expectation of success in
`
`making the combination. See Arctic Cat Inc. v. Bombardier Recreational Prods.
`
`Inc., 876 F.3d 1350, 1360-61 (Fed. Cir. 2017) (“[W]here a party argues a skilled
`
`artisan would have been motivated to combine references, it must show the artisan
`
`would have had a reasonable expectation of success from doing so.”). There is no
`
`combination at issue for Ground 1, so there is no reasonable expectation of success
`
`requirement for Ground 1.
`
`In that sense, this case is on all fours with Realtime v. Iancu, where the petition
`
`argued that certain claims were obvious based on a single reference (i.e., Sharpe
`
`alone), with a combination (i.e., Sharpe in view of Eintracht) supporting the
`
`obviousness of those claims in the alternative. Realtime Data, LLC v. Iancu,
`
`912 F.3d 1368, 1372-73 (Fed. Cir. 2019). The Federal Ci

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