throbber
Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 1 of 83
`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 1 of 83
`
`EXHIBIT A
`EXHIBIT A
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 2 of 83
`
`
`
`
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`___________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`___________
`
`
`
`TRILLER, INC.
`Petitioner
`
`v.
`
`TIKTOK PTE. LTD.
`Patent Owner
`
`
`
`Case No. _______________
`U.S. Patent No. 9,648,132
`Issue Date: May 9, 2017
`
`Title: Method Of Enabling Digital Music Content To Be Downloaded To And Used
`On a Portable Wireless Computing Device
`
`
`
`
`
`
`
`
`
`PETITION FOR INTER PARTES REVIEW OF U.S. PATENT NO. 9,648,132
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. § 42.100 ET SEQ.
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 3 of 83
`
`TABLE OF CONTENTS
`
`I.
`
`MANDATORY NOTICES UNDER 37 C.F.R. § 42.8(a)(1) .......................... 1
`
`II.
`
`PAYMENT OF FEES UNDER 37 C.F.R. § 42.103 ....................................... 2
`
`III. REQUIREMENTS FOR INTER PARTES REVIEW UNDER 37 C.F.R. §
`42.104 .............................................................................................................. 2
`
`A.
`
`B.
`
`Standing - 37 C.F.R. § 42.104(a) .......................................................... 2
`
`Challenge and Relief Requested - 37 C.F.R. § 42.104(b) ..................... 3
`
`1.
`
`2.
`
`3.
`
`4.
`
`Challenged Claims - 37 C.F.R. § 42.104(b)(1) ........................... 3
`
`Specific Statutory Grounds - 37 C.F.R. § 42.104(b)(2) .............. 3
`
`Claim Construction - 37 C.F.R. § 42.104(b)(3) .......................... 4
`
`- 37 C.F.R. §
`Explanation of Unpatentability
`42.104(b)(4) ................................................................................ 4
`
`5.
`
`Supporting Evidence - 37 C.F.R. § 42.104(b)(5) ........................ 4
`
`IV. THE SPECIFICATION AND CLAIMS OF THE ’132 PATENT ................. 4
`
`V.
`
`CLAIMS 1, 2, 3, 6, 22, 26, 27, and 31 OF THE ’132 PATENT ARE
`UNPATENTABLE ........................................................................................ 11
`
`A.
`
`Claims 1, 22, 26, and 31 Are Anticipated, or At Least Rendered
`Obvious, By Abrams ........................................................................... 11
`
`1.
`
`2.
`
`Overview of Abrams ................................................................. 11
`
`Abrams Anticipates, or At Least Renders Obvious, Claim
`1 ................................................................................................. 21
`
`a)
`
`b)
`
`c)
`
`d)
`
`e)
`
`f)
`
`Limitation 1.1 ................................................................. 21
`
`Limitation 1.2 ................................................................. 21
`
`Limitation 1.3 ................................................................. 22
`
`Limitation 1.4 ................................................................. 22
`
`Limitation 1.5 ................................................................. 24
`
`Limitation 1.6 ................................................................. 27
`
`
`
`ii
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 4 of 83
`
`3.
`
`4.
`
`5.
`
`g)
`
`h)
`
`Limitation 1.7 ................................................................. 27
`
`Limitation 1.8 ................................................................. 28
`
`Abrams Anticipates, or At Least Renders Obvious, Claim
`22 ............................................................................................... 30
`
`Abrams Anticipates, or At Least Renders Obvious, Claim
`26 ............................................................................................... 31
`
`Abrams Anticipates, or At Least Renders Obvious, Claim
`31 ............................................................................................... 31
`
`a)
`
`b)
`
`c)
`
`d)
`
`e)
`
`f)
`
`g)
`
`h)
`
`Limitation 31.1 ............................................................... 32
`
`Limitation 31.2 ............................................................... 32
`
`Limitation 31.3 ............................................................... 32
`
`Limitation 31.4 ............................................................... 32
`
`Limitation 31.5 ............................................................... 32
`
`Limitation 31.6 ............................................................... 33
`
`Limitation 31.7 ............................................................... 33
`
`Limitation 31.8 ............................................................... 33
`
`B.
`
`Claims 2 and 27 Would Have Been Obvious In View of Abrams
`and The Knowledge of a POSITA ...................................................... 33
`
`1.
`
`2.
`
`Claim 2 Would Have Been Obvious In View of Abrams
`and The Knowledge of a POSITA About Multitasking
`and Multithreading .................................................................... 33
`
`Claim 27 Would Have Been Obvious In View of Abrams
`and The Knowledge of a POSITA About Multitasking
`and Multithreading .................................................................... 37
`
`C.
`
`Claims 3, 6, and 27 Are Not Entitled to Their Claimed Priority In
`May 2007 Because Their Subject Matter Is Not Disclosed In the
`May 2007 Priority Document, And Therefore The Applicants’ Own
`Disclosure In Knight 2010 Anticipates, Or At Least Renders
`Obvious, Claims 3, 6, and 27 .............................................................. 38
`
`1.
`
`Knight 2010 Anticipates, Or At Least Renders Obvious,
`
`
`
`iii
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 5 of 83
`
`Claim 3 ...................................................................................... 41
`
`a)
`
`b)
`
`c)
`
`d)
`
`e)
`
`f)
`
`g)
`
`h)
`
`i)
`
`j)
`
`Claim 1, Limitation 1.1 ................................................... 42
`
`Claim 1, Limitation 1.2 ................................................... 42
`
`Claim 1, Limitation 1.3 ................................................... 43
`
`Claim 1, Limitation 1.4 ................................................... 43
`
`Claim 1, Limitation 1.5 ................................................... 43
`
`Claim 1, Limitation 1.6 ................................................... 44
`
`Claim 1, Limitation 1.7 ................................................... 44
`
`Claim 1, Limitation 1.8 ................................................... 44
`
`Additional Limitations of Claim 2.................................. 45
`
`Additional Limitations of Claim 3.................................. 45
`
`2.
`
`3.
`
`Knight 2010 Anticipates, Or At Least Renders Obvious,
`Claim 6 ...................................................................................... 46
`
`Knight 2010 Anticipates, Or At Least Renders Obvious,
`Claim 27 .................................................................................... 47
`
`D.
`
`If The Subject Matter of Claim 6 Is Disclosed In The May 2007
`Priority Document, The Subject Matter of Claim 6 Would Have
`Been Obvious In Light of Abrams and Khedouri ............................... 48
`
`1.
`
`2.
`
`Overview of Khedouri .............................................................. 49
`
`If The Subject Matter of Claim 6 Is Disclosed In The
`May 2007 Priority Document, The Subject Matter of
`Claim 6 Would Have Been Obvious In View of Abrams
`and Khedouri ............................................................................. 55
`
`a)
`
`b)
`
`c)
`
`Khedouri Discloses “A Music Application” .................. 56
`
`Khedouri Discloses That the Music Application Uses
`Track Meta-Data That Defines Attributes of Tracks ...... 56
`
`Khedouri Discloses Track Meta-Data External to A
`Music Track .................................................................... 57
`
`d)
`
`Under Potential Interpretations Derived From Patent
`
`
`
`iv
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 6 of 83
`
`Owner’s Positions In The Related Litigation, Khedouri
`Discloses “Track Meta-Data That Is Formed As A
`Separate Meta-Data Layer” ............................................ 57
`
`e)
`
`The Combination of Khedouri and Abrams Would
`Have Been Obvious ........................................................ 59
`
`E.
`
`F.
`
`Claim 3 Would Have Been Obvious In View of Abrams, Khedouri,
`and The Knowledge of a POSITA About Multitasking and
`Multithreading ..................................................................................... 61
`
`If The Subject Matter of Claim 6 Is Disclosed In The May 2007
`Priority Document, The Subject Matter of Claim 6 Would Have
`Been Obvious In Light of Abrams and Partovi ................................... 63
`
`1.
`
`2.
`
`Overview of Partovi .................................................................. 63
`
`If The Subject Matter of Claim 6 Is Disclosed In The
`May 2007 Priority Document, The Subject Matter of
`Claim 6 Would Have Been Obvious In View of Abrams
`and Partovi ................................................................................ 65
`
`a)
`
`b)
`
`c)
`
`d)
`
`Partovi Discloses “A Music Application” ...................... 66
`
`Partovi Discloses That the Music Application Uses
`Track Meta-Data That Defines Attributes of Tracks ...... 66
`
`Partovi Discloses Track Meta-Data External to A
`Music Track .................................................................... 67
`
`Under Potential Interpretations Derived From Patent
`Owner’s Positions In The Related Litigation, Partovi
`Discloses “Track Meta-Data That Is Formed As A
`Separate Meta-Data Layer” ............................................ 68
`
`e)
`
`The Combination of Partovi and Abrams Would Have
`Been Obvious .................................................................. 69
`
`VI. NO BASIS EXISTS FOR DISCRETIONARY DENIAL ............................ 70
`
`VII. CONCLUSION .............................................................................................. 72
`
`
`
`
`
`v
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 7 of 83
`
`EXHIBIT LIST
`
`Description
`
`Exhibit
`No.
`1001 U.S. Patent No. 9,648,132
`1002 U.S. Patent No. 9,992,322
`1003 U.S. Patent No. 9,924,430
`1004 Prosecution History of U.S. Patent No. 8,510,847
`1005 Prosecution History of U.S. Patent No. 9,924,430
`1006 Prosecution History of U.S. Patent No. 9,648,132
`1007 Prosecution History of U.S. Patent No. 9,992,322
`1008 PCT Publication No. WO 2007/129081
`1009 U.S. Patent Application Publication No. 2005/0021750 (“Abrams”)
`1010 U.S. Patent No. 8,572,169 (“Partovi”)
`1011 U.S. Patent Application Publication No. 2006/0008256 (“Khedouri”)
`1012 U.S. Patent Application Publication No. 2010/0031366 (“Knight 2010”)
`Plaintiffs’ Disclosure of Asserted Claims and Infringement Contentions
`in N.D. Cal. 4:20-CV-7572 (Redacted) (dated Aug. 27, 2021)
`Steve Monas, YourSpace: A Friend’s Guide to MySpace.com: The Basics
`(2006) (excerpts)
`“Java Threads” (2nd Edition, 1999), by Oaks & Wong
`1015
`1016 U.S. Patent No. 6,134,548 (“Gottsman”)
`1017 U.S. Patent No. 6,567,974 (“Czajkowski”)
`U.S. Patent Application Publication No. 2007/0192818 (“Bourges-
`Sevenier”)
`Pages from www.cnet.com archived on Wayback Machine (dated in 2005
`and 2006)
`1020 U.S. Pat. No. 5,963,951 (“Collins”)
`Opposition to Triller’s Motion for Judgment on the Pleadings Regarding
`Second, Third, and Fourth Claims for Relief in Second Amended
`Complaint (N.D. Cal. 4:20-7572) (dated Sep. 29, 2021)
`“MySpace, America's Number One,” available at
`https://mashable.com/archive/myspace-americas-number-one
`“Module 19321 (2012),” available at
`https://www.cs.bham.ac.uk/internal/modules/2012/06-19321/mds
`“Module 06-19321 (2012) Software System Components A,” available at
`https://www.cs.bham.ac.uk/internal/modules/2012/06-19321
`1025 Declaration of Michael Shamos, Ph.D.
`1026 Order Re: Defendant’s Motion to Dismiss, or in the Alternative, To Stay
`
`1013
`
`1014
`
`1018
`
`1019
`
`1021
`
`1022
`
`1023
`
`1024
`
`
`
`vi
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 8 of 83
`
`Exhibit
`No.
`
`Description
`
`1027
`
`First Claim for Relief of Plaintiffs’ First Amended Complaint (N.D. Cal.
`4:20-7572, Dkt. No. 44) (dated Mar. 30, 2021)
`Order Vacating Hearing and Briefing Schedule on Motion for Judgment
`on the Pleadings (N.D. Cal. 4:20-7572, Dkt. No. 47) (dated Apr. 15,
`2021)
`1028 Docket Sheet from N.D. Cal. 4:20-7572
`First Amended Complaint (N.D. Cal. 3:20-7572, now 4:20-7572) (filed
`Nov. 11, 2020) (without exhibits)
`
`1029
`
`
`
`
`
`vii
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 9 of 83
`
`The petitioner in this matter is Triller, Inc. (“Petitioner”). Inter partes review
`
`is requested for claims 1, 2, 3, 6, 22, 26, 27, and 31 of U.S. Patent No. 9,648,132
`
`(“the ’132 patent”) (Ex. 1001).
`
`I. MANDATORY NOTICES UNDER 37 C.F.R. § 42.8(a)(1)
`
`(a) Real Party-In Interest: The real party-in-interest is Petitioner Triller,
`
`Inc., a Delaware corporation. Triller Holdco LLC is the parent company of Triller,
`
`Inc.
`
`(b) Related Matters: The ’132 patent is being asserted against Petitioner in
`
`Bytedance Inc. et al. v. Triller, Inc., 3:20-CV-07572 (N.D. Cal.). In addition,
`
`Petitioner is concurrently filing petitions for inter partes review against U.S. Patent
`
`No. 9,991,322 and U.S. Pat. No. 9,294,430, which share common specifications
`
`and claims of similar scope and which are also being asserted against Petitioner in
`
`the related litigation. Petitioner requests that IPR proceedings with regard to all
`
`three petitions be consolidated.
`
`(c) Lead and Back-Up Counsel: Lead counsel is Chad E. Nydegger (USPTO
`
`Registration No. 61,020). Back-up counsel are Brian N. Platt (USPTO Registration
`
`No. 62,249) and David R. Todd (USPTO Registration No. 41,348).
`
`(d) Service Information: Petitioner consents to electronic service in this
`
`matter. Papers should be served on the following:
`
`1
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 10 of 83
`
`Chad E. Nydegger (cnydegger@wnlaw.com)
`Brian N. Platt (bplatt@wnlaw.com)
`David R. Todd (dtodd@wnlaw.com)
`WORKMAN NYDEGGER
`60 East South Temple, Suite 1000
`Salt Lake City, Utah 84111
`Telephone: (801) 533-9800
`Facsimile: (801) 328-1707
`
`PAYMENT OF FEES UNDER 37 C.F.R. § 42.103
`
`II.
`
`Review is requested for 8 claims of the ’132 patent. The fees required under 37
`
`C.F.R. § 42.103 are calculated under 37 C.F.R. § 42.15(a) as follows:
`
`37 C.F.R. § 42.15(a)(1) – Inter Partes Review Request Fee
`
`$19,000
`
`37 C.F.R. § 42.15(a)(2) –Inter Partes Review Post-Institution Fee
`
`$22,500
`
`37 C.F.R. § 42.15(a)(3) – Excess Claims Request Fee
`
`
`
`37 C.F.R. § 42.15(a)(4) –Excess Claims Post-Institution Fee
`
`
`
`0 claims x $375/claim =
`
`$0
`
`0 claims x $750/claim =
`
`$0
`
`TOTAL: $41,500
`
`
`III. REQUIREMENTS FOR INTER PARTES REVIEW UNDER 37 C.F.R.
`§ 42.104
`
`A.
`
`Standing - 37 C.F.R. § 42.104(a)
`
`Petitioner hereby certifies that the ’132 patent is available for inter partes
`
`review and that Petitioner is not barred or estopped. Petitioner was first alleged to
`
`have infringed the ’132 patent in a First Amended Complaint filed in the related
`
`2
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 11 of 83
`
`litigation on November 11, 2020 and served no earlier than that date. (Ex. 1029.)
`
`Therefore, the one-year limitation in 35 U.S.C. § 315(b) is not applicable. 35 U.S.C. §
`
`315(b); 35 U.S.C. § 21(b).
`
`B. Challenge and Relief Requested - 37 C.F.R. § 42.104(b)
`
`1.
`
`Challenged Claims - 37 C.F.R. § 42.104(b)(1)
`
`Petitioner challenges the patentability of claims 1, 2, 3, 6, 22, 26, 27, and 31 of
`
`the ’132 patent.
`
`2.
`
`Specific Statutory Grounds - 37 C.F.R. § 42.104(b)(2)
`
`Statutory Ground 1a: Claims 1, 22, 26, and 31 are unpatentable for anticipation
`
`by Abrams (Ex. 1009) under 35 U.S.C. § 102.
`
`Statutory Ground 1b: In the alternative, claims 1, 22, 26, and 31 are
`
`unpatentable for obviousness under 35 U.S.C. § 103 in view of Abrams.
`
`Statutory Ground 2: Claims 2 and 27 are unpatentable for obviousness under
`
`35 U.S.C. § 103 in view of Abrams and the knowledge of a POSITA about
`
`multitasking and multithreading (as evidenced by Java Threads (Ex. 1015) and expert
`
`testimony (Ex. 1025)).
`
`Statutory Ground 3a: Claims 3, 6, and 27 are unpatentable for anticipation by
`
`Knight 2010 (Ex. 1012) under 35 U.S.C. § 102.
`
`Statutory Ground 3b: In the alternative, claims 3, 6, and 27 are unpatentable
`
`for obviousness under 35 U.S.C. § 103 in view of Knight 2010.
`
`3
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 12 of 83
`
`Statutory Ground 4: In the alternative, claim 6 is unpatentable for obviousness
`
`under 35 U.S.C. § 103 in view of Abrams and Khedouri (Ex. 1011).
`
`Statutory Ground 5: Claim 3 is unpatentable for obviousness in view of
`
`Abrams and Khedouri and the knowledge of a POSITA about multitasking and
`
`multithreading (as evidenced by Java Threads (Ex. 1015) and expert testimony (Ex.
`
`1025)).
`
`Statutory Ground 6: In the alternative, claim 6 is unpatentable for obviousness
`
`under 35 U.S.C. § 103 in view of Abrams and Partovi (Ex. 1010).
`
`3.
`
`Claim Construction - 37 C.F.R. § 42.104(b)(3)
`
`Where necessary, claim construction is addressed below in Section V in the
`
`context of analyzing the patentability of claims in which the construed terms appear.
`
`4.
`
`Explanation of Unpatentability - 37 C.F.R. § 42.104(b)(4)
`
`An explanation of how claims 1, 2, 3, 6, 22, 26, 27, and 31 of the ’132 patent
`
`are unpatentable is provided in Section V below.
`
`5.
`
`Supporting Evidence - 37 C.F.R. § 42.104(b)(5)
`
`The supporting evidence is discussed in Section V below. Exhibit numbers are
`
`identified when they are first used in this petition and in the Exhibit List beginning at
`
`page vi, above.
`
`IV. THE SPECIFICATION AND CLAIMS OF THE ’132 PATENT
`
` The ’132 patent is entitled “Method of enabling digital music content to be
`
`downloaded to and used on a portable wireless computing device,” but that title is
`
`4
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 13 of 83
`
`misleading. (Ex. 1001.) The broadest claims challenged here do not have anything
`
`to do with music but are merely directed to a social network implemented on a
`
`computer network. Independent claim 1 of the ’132 patent claims a “portable
`
`wireless computing device” comprising “a hardware processor”
`
`that
`
`is
`
`programmed with a “software application” that allows its user to carry out social
`
`networking functions (brackets with numbering have been added to facilitate
`
`discussion of the various claim limitations):
`
`[1.1] A portable wireless computing device comprising [1.2] a
`
`hardware processor programmed with a software application
`
`embodied on a non-transitory storage medium, [1.3] that enables an
`
`end-user to interact with other users in which [1.4] (a) the software
`
`application allows the end-user to, over a wireless connection, create
`
`on a remote server one or more user accounts with associated profiles
`
`for that end-user; and [1.5] (b) the software application allows the
`
`end-user to, over the wireless connection, view profiles created by
`
`other users of a service; and [1.6] (c) the software application allows
`
`the end-user to, over the wireless connection, interact with other users
`
`of the service; and [1.7] (d) the software application allows the end-
`
`user to, over the wireless connection, send and receive messages to
`
`and from other users of the service; and [1.8] (e) the software
`
`application allows the end-user to, over the wireless connection, link
`
`his or her user account on the remote server to user accounts on the
`
`remote server of other users of the same service or of other services.
`
`(Ex. 1001, 86:32-49.)
`
`5
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 14 of 83
`
`Independent claim 31 of the ’132 patent is of similar scope to claim 1,
`
`claiming a “software application” that is “executable on a portable wireless
`
`computing device” to allow a user to carry out the same social networking
`
`functions as claim 1 (brackets with numbering have been added to facilitate
`
`discussion of the various claim limitations):
`
`[31.1] Software application embodied on a non transitory
`
`storage medium, [31.2] wherein the software application is executable
`
`on a portable wireless computing device, [31.3] wherein the software
`
`application enables an end-user to interact with other users and [31.4]
`
`(a) in which the software application allows the end-user to, over a
`
`wireless connection, create on a remote server one or more user
`
`accounts with associated profiles for that end-user; and [31.5] (b) the
`
`software application allows the end-user to, over the wireless
`
`connection, view profiles created by other users of a service; and
`
`[31.6] (c) the software application allows the end-user to, over the
`
`wireless connection, interact with other users of the service; and
`
`[31.7] (d) the software application allows the end-user to, over the
`
`wireless connection, send and receive messages to and from other
`
`users of the service; and [31.8] (e) the software application allows the
`
`end-user to, over the wireless connection, link his or her user account
`
`on the remote server to user accounts on the remote server of other
`
`users of the same service or of other services.
`
`(Ex. 1001, 88:46-64.)
`
`6
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 15 of 83
`
`The specification of the ’132 patent illustrates the social networking
`
`functionality described in these two independent claims. For example, Figure 135
`
`shows the user interface for a software application running on a mobile telephone
`
`that allows an end-user to create a user account with an associated profile, as
`
`recited in claims 1 and 31:
`
`
`
`(Ex. 1001, Fig. 135, 76:18-32.) In this example, the user is creating a user profile
`
`with the profile name “Billy Pepper.” Once a user has created his profile, the
`
`software allows a user to see his “profile” on a “My Profile” screen, shown below:
`
`7
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 16 of 83
`
`(Ex. 1001, Fig. 136.) The profile includes the user’s member name (here,
`
`“Murdock”), an image unique to the user, a rating indicating how other users have
`
`rated the user (here, with five stars), the number of times other users have listened
`
`to one of the user’s shared music playlists (here, 0), the number of friends that the
`
`user has (here, 1), and a “catchphrase” (here, “I knew it, I knew it…you had a
`
`plan!”). (Ex. 1001, 76:34-60.)
`
`The specification further illustrates how a user can view profiles created by
`
`other users, as recited in claims 1 and 31:
`
`8
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 17 of 83
`
`
`
`
`(Ex. 1001, Figs. 141, 142.) The specification explains that in the screens shown in
`
`Figure 141, a user can see a list of the users that the user has added as a friend, and
`
`in the screen shown in Figure 142, the user can view the member profile of other
`
`users (here, another user named “DJ Coldplay”). (Ex. 1001, 77:39-67.)
`
`
`
`The specification also illustrates how a user can link his or her user account
`
`to user accounts of other users (via friend requests), can interact with other users
`
`(by sharing recommendations about music), and can send and receive messages to
`
`and from other users, as recited in claims 1 and 31. (Ex. 1001, 32:26-33.) This
`
`functionality is illustrated in Figures 146 and 148:
`
`9
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 18 of 83
`
`(Ex. 1001, Figs. 146, 148.) In Figure 146, the user is sending a friend request to a
`
`user named “Matt,” and in Figure 148, the user is sending a recommendation about
`
`a music track to another user. (Ex. 1001, 78:12-20, 78:31-43, 78:62-67.) In both
`
`figures, the user is also sending messages to other users. In Figure 146, the user is
`
`sending the message “Billy is ready to rock!” and in Figure 148, the user is sending
`
`the message “U know I’m a bit…” A friend request or a recommendation causes a
`
`message to arrive in the other user’s “inbox.” (Ex. 1001, 78:12-20, 78:66-67, 79:1-
`
`80:14, Figs. 149-154.)
`
`10
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 19 of 83
`
`
`
`As demonstrated below, claims 1 and 31, as well as claims 2, 3, 6, 22, 26, and
`
`27 (which depend from claim 1), are unpatentable.
`
`V. CLAIMS 1, 2, 3, 6, 22, 26, 27, and 31 OF THE ’132 PATENT ARE
`UNPATENTABLE
`
`
`A. Claims 1, 22, 26, and 31 Are Anticipated, or At Least Rendered
`Obvious, By Abrams
`
`1. Overview of Abrams
`
`U.S. Patent Application Publication No. 2005/0021750 (“Abrams”) was
`
`published on January 27, 2005 (Ex. 1009, cover page), and is therefore prior art to
`
`the ’132 patent under pre-AIA 35 U.S.C. § 102(b) or post-AIA 35 U.S.C.
`
`§ 102(a)(1).1 Abrams was not considered by the Examiner of the ’132 patent. (Ex.
`
`1001, References Cited.)
`
`Like the ’132 patent, Abrams describes a social network implemented on a
`
`computer network. The Abrams system allows an end-user to create a user account
`
`with an associated profile, as recited in claims 1 and 31. Figure 3a of Abrams
`
`shows a user interface presented on two web pages designed to obtain “user
`
`
`1 The amendments to 35 U.S.C. § 102 made by the Leahy-Smith America
`Invents Act apply to “any patent application that contains or contained at any time
`a claim to a claimed invention that has an effective filing date that is on or after
`[March 16, 2013].” Pub. L. No. 112-29 § 3(n), 125 Stat. 284, 293 (2011). For the
`reasons set forth below in section V.C., the ’132 patent has one or more claims
`with an effective filing date after March 16, 2013 and is therefore subject to post-
`AIA 35 U.S.C. § 102. Nevertheless, Abrams is prior art to the ’132 patent
`regardless of whether the AIA is applicable or not.
`
`11
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 20 of 83
`
`descriptive data.” (Ex. 1009, ¶¶99, 67.) “Descriptive data generally describes
`
`characteristics and preferences of a user…. For example, a descriptive data element
`
`may be that a user is interested in a certain hobby, say, skiing.” (Ex. 1009, ¶41.)
`
`Descriptive data might also include “a first and last name” or “attributes of the
`
`user, such as gender, marital status or occupation.” (Ex. 1009, ¶64; accord id. at
`
`¶91.) Figure 3a is reproduced below:
`
`(Ex. 1009, Fig. 3a.) In this figure, a first screen 302 is used to collect descriptive
`
`data about the user, and a second screen 304 is used to collect “further descriptive
`
`
`
`12
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 21 of 83
`
`data” about the user. (Ex. 1009, ¶99; see also id. at ¶¶41, 43, 108.) Descriptive data
`
`may also include a digital image of the user. (Ex. 1009, ¶91.) Figure 3b shows a
`
`screen 308 that allows users to upload a digital image:
`
`
`
`(Ex. 1009, Fig. 3b.)
`
`
`
`Descriptive data input by the user is stored in a database on a server
`
`apparatus. (Ex. 1009, Fig. 1, ¶¶46, 50, 67, 76, 86, 88-89.) The contents of the
`
`database are illustrated in Figure 2, reproduced below:
`
`13
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 22 of 83
`
`
`
`In Figure 2, descriptive data within database 200 is grouped into “user data” 202,
`
`“location data” 204, “zip code data” 206, “profile data” 208, “photos” 210, and
`
`“testimonial data” 212. (Ex. 1009, ¶¶91-92.) Note that “profile data” 208 includes
`
`“Interests,”
`
`“Favoritemusic,”
`
`“Favoritebooks,”
`
`“Favoritetv,”
`
`and
`
`“Favoritemovies,” among many other things. (Ex. 1009, Fig. 2, ¶91.) Database 200
`
`14
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 23 of 83
`
`also contains other types of data, including relationship data (216, 218, 220) and
`
`preference data, which will be discussed below. (Ex. 1009, ¶¶90, 93-98.)
`
`
`
`As with the ’132 patent, Abrams discloses that a user can view profiles
`
`created by other users. (Ex. 1009, ¶45.) Figure 5, reproduced below, shows a web
`
`page that presents to a user “the other users within his social network” (Ex. 1009,
`
`¶102):
`
`(Ex. 1009, Fig. 5.) On the web page in this figure, other users within the user’s
`
`social network have been filtered by various parameters shown on the left of the
`
`screen, including gender, age, location, etc. (See Ex. 1009, ¶102.) Three users
`
`meeting the search criteria can be seen on the right side of the screen, along with
`
`
`
`15
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 24 of 83
`
`their photo, gender, relationship status, interests, age, location, and number of
`
`friends. (See Ex. 1009, ¶103.) For each of those three users, the user interface
`
`provides options (shown on the far right of the screen) to “View Profile,” “Send
`
`Message,” etc. (Ex. 1009, Fig. 5.)
`
`
`
`If a user selects “View Profile,” he will be presented with a screen 602 such
`
`as the one shown in Figure 6, reproduced below:
`
`16
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 25 of 83
`
`
`
`(Ex. 1009, Fig. 6.) Figure 6 shows an interface “that displays a profile—a
`
`collection of descriptive, preference and relationship data” about a particular user
`
`named “Cindy.” (Ex. 1009, ¶105.) In this example, “descriptive data shown
`
`includes gender, [relationship] status, age, occupation, location, hometown and
`
`interests,” as well as digital images of the user, the user’s friends, and a testimonial
`
`17
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 26 of 83
`
`from another user. (Ex. 1009, ¶105.) Preference data is also shown, including “her
`
`preference for dating…men.” (Ex. 1009, ¶105.) Relationship data is also shown in
`
`the upper left corner. (See Ex. 1009, ¶105.)
`
`Abrams also discloses that a user can link his or her user account to user
`
`accounts of other users (via friend requests). (Ex. 1009, ¶¶41, 43, 65, 70, 95, 101,
`
`106-108, 122.) A user may link his or her account with someone who does not
`
`currently have an account by inviting a friend to join the system. (Ex. 1009, ¶¶43,
`
`101, 106-108.) To do so, a user provides the system with a friend’s email address,
`
`and the system sends an e-mail invitation to the friend to join the system. (Ex.
`
`1009, ¶¶43, 53, 101, 106, Figs. 4, 7.) The friend can accept the invitation and join
`
`the system by clicking on a link and entering “descriptive data” about
`
`himself/herself. (Ex. 1009, Fig. 4, ¶¶43, 53, 101, 108.) If the friend accepts the
`
`invitation and joins the system, the friend and the inviting user are “automatically
`
`defined within the system as ‘friends.’” (Ex. 1009, ¶108.) Specifically, the users
`
`are listed in the “friends data” 216 in each other’s section of the database 200. (Ex.
`
`1009, Fig. 2, ¶¶95, 41, 43, 65, 70; Ex. 1025, p. 69.) A user may also initiate friend
`
`requests “within the system,” and two users can “confirm that they are ‘friends.’”
`
`(Ex. 1009, ¶¶95, 43; Ex. 1025, pp. 38-39.)
`
`
`
`Abrams also discloses that a user can exchange messages with other users.
`
`As seen in Figure 5, the user interface provides an option to “Send Message.” (Ex.
`
`18
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11/11/21 Page 27 of 83
`
`1009, Fig. 5.) If a user viewing this interface “discovers other users who have
`
`characteristics she finds appealing, …she may wish to communicate with the user”
`
`by selecting this option. (Ex. 1009, ¶45.) This allows her to “contact the user
`
`through the communication system.” (Ex. 1009, ¶45; accord id. at ¶104.) This
`
`system is “an internal messaging system whereby users may send one another
`
`private messages.” (Ex. 1009, ¶97; accord id. at ¶104.) Data about messages sent
`
`through the internal message system are stored as “messages” data 224 in database
`
`200. (Ex. 1009, ¶¶96-97, Fig. 2.)
`
`
`
`Abrams also discloses that a user can interact with other users in other ways
`
`as well. (Ex. 1009, ¶41.) For example, “one user can write a positive comment
`
`about a second user’s personality,” and “the second user may accept or reject
`
`display of the comment.” (Ex. 1009, ¶44.) As another example, users within a
`
`certain number of degrees of relationship can “conduct online discussions” using
`
`an electronic “bulletin board.” (Ex. 1009, ¶98.) Data from those discussions are
`
`stored as “bulletinboard” data 226 in database 200. (Ex. 1009, ¶96, Fig. 2.)
`
`
`
`Abrams discloses that this system is implemented on a “server apparatus”
`
`110 communicating with a Web browser running on user devices 106 and 108, as
`
`shown in Figure 1:
`
`19
`
`

`

`Case 4:20-cv-07572-JSW Document 70-1 Filed 11

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