`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_________________
`
`TRILLER, INC.,
`Petitioner
`
`v.
`
`TIKTOK PTE. LTD.
`Patent Owner
`
`
`
`
`
`
`Case IPR2022-00180
`Patent 9,992,322 B2
`
`_________________
`
`
`
`
`
`
`
`PATENT OWNER TIKTOK PTE. LTD.’S
`PRELIMINARY RESPONSE
`
`
`
`
`
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`TABLE OF CONTENTS
`
`
`
`INTRODUCTION ............................................................................................ 1
`I.
`II. LEVEL OF ORDINARY SKILL ..................................................................... 2
`III. CLAIM CONSTRUCTION .............................................................................. 3
`IV. ABRAMS FAILS TO PROVIDE ALL ELEMENTS OF THE
`INDEPENDENT CLAIMS ............................................................................... 3
`A. The Petition Fails To Demonstrate A “Software Application Embodied On
`A Non-Transitory Storage Medium” And “Executable On A Smartphone
`Device,” That Provides the Claimed Functions (Grounds 1a-2b and 4a-6b)
` ....................................................................................................................... 3
`B. The Petition Fails to Demonstrate that the System of Abrams Would Have
`“inherently” Performed the Claimed Functions “over a wireless
`connection” as Required by the Independent Claim (Grounds 1a-2b and 4a-
`6b) ................................................................................................................ 13
`C. The Petition fails to address the limitation “creat[ing] on a remote server
`one or more user accounts” recited in independent claim 30 (Grounds 1a-
`2b and 4a-6b) ............................................................................................... 24
`V. KNIGHT 2010 IS NOT PRIOR ART TO THE ’322 PATENT (GROUNDS
`3a AND 3b) ..................................................................................................... 26
`A. Legal Standard for Written Description Support ........................................ 27
`B. The 2007 PCT Application Provides Written Description Support for
`Claims 32 and 56 ......................................................................................... 28
`C. The 2007 PCT Application Provides Written Description Support for
`Claim 35 ...................................................................................................... 36
`D. Grounds 3a and 3b Fail Because Knight 2010 is Not Prior Art to the ’322
`Patent ........................................................................................................... 42
`VI. CONCLUSION ............................................................................................... 43
`
`
`
`
`
`
`
`i
`
`
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`LIST OF EXHIBITS
`
`
`Description
`U.S. Patent Pub. No. 2004/0268005 to Dickie (“Dickie”)
`U.S. Patent Pub. No. 2007/0130592 to Haeusel (“Haeusel”)
`U.S. Patent No. 7,260,381 to Lipsit (“Lipsit”)
`U.S. Patent Pub. No. 2007/0214141 (“Sittig”)
`
`
`
`
`Exhibit No.
`EX2001
`EX2002
`EX2003
`EX2004
`
`
`ii
`
`
`
`
`I.
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`INTRODUCTION
`The Petition sets forth thirteen Grounds of unpatentability, each of which
`
`suffers from critical defects that render Inter Partes Review untenable. Throughout
`
`the Petition, Triller repeatedly identifies high level descriptions in the cited
`
`references without specifying how each specific claim recitation is found within the
`
`references, while insisting that other non-disclosed features occur “inherently” or
`
`would occur in “all” such systems with no support for such assertions. This failure
`
`to proper demonstrate how each claim element is provided in the prior art. Is
`
`pervasive throughout the Petition, including both the independent and dependent
`
`claims.
`
`To start, Triller fails to demonstrate that the Abrams reference (EX1009)
`
`includes a software application “executable on a portable wireless computing
`
`device” that performs each of the functions recited by the challenged claims. Rather,
`
`Abrams discloses a web-server that performs various functions and merely “sends
`
`out Web pages” to end user devices. EX1009, [0077]. That is, as demonstrated
`
`below, all relevant functionality described in Abrams is performed at a “Web
`
`application server” and not by a software application installed on and executed by a
`
`portable wireless computing device. Id.
`
`Second, Triller argues that all of the functions recited by the challenged claims
`
`would “inherently occur over a ‘wireless connection’” in Abrams’s system. See, e.g.,
`
`1
`
`
`
`
`Pet., 28. As demonstrated below, however, the evidence of record shows that such
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`functionality is anything but inherent.
`
`Finally, the Knight 2010 reference (EX1012) does not qualify as prior art with
`
`respect to any of the challenged claims because all of the challenged claims (and in
`
`particular, dependent claims 3, 6, and 27) are fully supported by the earlier filed May
`
`2007 PCT application to which the ’322 patent claims priority. As demonstrated
`
`below, each of Grounds 1a-6b as articulated in the Petition fail, and therefore
`
`institution should be denied.
`
`II. LEVEL OF ORDINARY SKILL
`For purposes of this IPR, a person of ordinary skill in the art at the time of
`
`the alleged invention (a “POSITA”) would have had a Bachelor’s degree in
`
`Computer Science, Computer Engineering, Human Factors, or an equivalent
`
`degree and at least two years of experience working in the fields of user interfaces,
`
`communications applications, networking applications, or media applications, or a
`
`person with equivalent education, work, or experience in such fields.
`
`
`
`
`
`
`
`2
`
`
`
`
`III. CLAIM CONSTRUCTION
`Patent Owner submits that all claim terms should be construed according to
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`the Phillips standard. Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005); 37
`
`C.F.R. §42.100. Unless otherwise noted below, Patent Owner submits that terms
`
`should be given their plain meaning in light of the specification, but reserves
`
`opportunity to respond to constructions offered by Petitioner or adopted by the
`
`Board.
`
`The following term is defined by the ’322 Patent in the “Definitions”
`
`section, but was not construed by the Petition. Phillips, 415 F.3d at 1316 (“[T]he
`
`specification may reveal a special definition given to a claim term by the patentee
`
`that differs from the meaning it would otherwise possess. In such cases, the
`
`inventor's lexicography governs.”).
`
`“Software Application” – “The Client software application which is to be
`
`delivered over-the-air to, or pre-installed on, the Wireless Computing Device.”
`
`EX1002, 8:63-65.
`
`IV. ABRAMS FAILS TO PROVIDE ALL ELEMENTS OF THE
`INDEPENDENT CLAIMS
`A. The Petition Fails To Demonstrate A “Software Application
`Embodied On A Non-Transitory Storage Medium” And
`
`3
`
`
`
`
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`“Executable On A Smartphone Device,” That Provides the
`Claimed Functions (Grounds 1a-2b and 4a-6b)
`Independent claim 30 recites a “Software application embodied on a non-
`
`transitory storage medium” and “executable on a smartphone device” that
`
`“enables an end-user to interact with other users” and “allows the end-user to”
`
`perform a number of recited actions.1 EX1002, cl. 30. The “software application”
`
`elements thus require not merely any “software application” generally, but a
`
`specific software application configured to perform the claimed functions. Id.
`
`Additionally, the software application that “enables an end-user to interact with
`
`other users” and “allows the end-user to” perform a number of actions must be
`
`“embodied on a non-transitory storage medium” and “executable on the
`
`smartphone device.” Id. The Petition’s terse analysis, which relies exclusively on
`
`Abrams, fails to fully address these “software application” elements.
`
`Rather than a dedicated software application for performing the claimed
`
`functions, the Petition identifies a generic “browser” of Abrams as allegedly
`
`providing the claimed “software application”—“[T]he ‘software application’ of
`
`claim 30 is found in Abrams as a Web browser executing on user devices 106 and
`
`108 so as to receive and render Web pages from a Web server.” Pet., 20. From
`
`there, the Petition relies on other aspects of Abrams system for features of claim
`
`
`1 All emphasis added unless otherwise noted.
`
`4
`
`
`
`
`30, including “a bulletin board that users can use to conduct online discussions”
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`(Pet., Limitation 30.3), “interfaces” related to profile data or messaging (Pet.,
`
`Limitations 30.4, 30.7), and a “web page” that presents other users within the
`
`social network (Limitation 30.5), etc. Such reliance ignores the full limitations of
`
`claim 30.
`
`For example, the Petition ignores that the features it relies on as purportedly
`
`part of the “software application” that “enables an end-user to interact with other
`
`users” and “allows the end-user to” perform a number of actions are not actually
`
`“embodied on” the portable device at all, as required by independent claim 30.
`
`Instead, Abrams plainly states that these aspects of its system are located at a
`
`remote “Web server”:
`
`The Web application server 130 is a system that sends out Web pages
`in response to Hypertext Transfer Protocol (HTTP) requests from
`remote browsers (i.e. users of the apparatus 110). That is, the Web
`server 130 provides the GUI 102 & 104 to users of the system in the
`form of Web pages. These Web pages sent to the user’s device 106 &
`108 would result in GUI screens 102 & 104 being displayed.
`
`EX1009, [0077]. Simply put, the features identified by the Petition are not
`
`“embodied on” the purported smartphone at all. In Abrams system, the “Web
`
`server,” and other components of its system remote from the user device, handle
`
`these functions—not the user device. The web server provides the GUI to users of
`
`5
`
`
`
`
`the system in the form of web pages that are merely displayed by the user interface
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`devices.2
`
`
`
`The Petition never addresses Abrams straightforward description on this
`
`point, and thus fails to fully address the “software application” elements of
`
`independent claim 30. Claim 30 requires that the “software application” that
`
`“enables an end-user to interact with other users” and “allows the end-user to”
`
`carry out the recited set of actions be “embodied on” the non-transitory storage
`
`medium and “executable on” the smartphone. The Petition, instead, identifies a
`
`generic browser used in a system in which a web server handles these functions,
`
`merely pushing HTML code to the generic browser. This defect infects the
`
`Petitioner’s mapping of each aspect of claim 30, including the “bulletin board,” the
`
`“interfaces,” and “web page,”—all of which are provided by Abrams’ “Web
`
`server,” and none of which have been shown to be “embodied on” the non-
`
`transitory storage medium (identified by Petitioner as provide by a smartphone).
`
`The Abrams grounds fail for this independent reason.
`
`
`2 To be clear, this is not an issue of whether a web browser is a “software
`
`application”—the ’322 patent acknowledges that some “browsers” may provide a
`
`“software application.” EX1002, 62:8-12. But the claims require more, which the
`
`Petition fails to address.
`
`6
`
`
`
`Critically, the Petition never addresses the ’322 Patent’s prosecution history
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`
`
`
`relevant to the “software application” features. For example, during prosecution of
`
`the parent of the ’322 patent (EX1006) involving nearly identical claim language,
`
`the Sittig reference (U.S. 2007/0214141, EX2004) was distinguished in part
`
`because Sittig’s system lacked a “software application” having the claimed
`
`features on the user device: “Sittig lacks any disclosure of any key functionality
`
`on a portable wireless computing device. Instead, the key functionality in Sittig is
`
`disclosed to be in the social network engine.” EX1006, 45-47. Like Abrams,
`
`Sittig described a “social networking website” (accessed via a computing device),
`
`and “one or more servers operating the social networking website.” EX2004,
`
`[0016]-[0017]. Applicant’s remarks were followed by a notice of allowance in
`
`which the Examiner concluded that “the substance of applicant’s arguments filed
`
`on 10/25/16 are persuasive” and “applicant’s reply make evident the reasons for
`
`allowance.”3 EX1006, 12. The Petition simply does not demonstrate that Abrams
`
`
`3 The Petition’s analysis of Abrams on this element is “substantially the same” as
`
`prior art applied in a substantive rejection and fails for the same reasons—both
`
`describe a generic browser/website pushed out by a web server, with all of the
`
`functionality provided by the web server. The Petition never explains any
`
`7
`
`
`
`
`discloses the claimed “software application” features when, like Sittig, Abrams
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`describes a mere “browser” at the user device with the relevant functionality
`
`provided by a remote “Web server.”
`
`
`
`The Petition also ignores the ’322 Patent specification itself, which discusses
`
`“browsers” generally as distinct from the claimed “software application.” For
`
`example, the ’322 patent distinguishes its “software application” (e.g., such as the
`
`example MusicStation software application described at length by the ’322 Patent)
`
`from “Wireless Application Protocol” browsers. See, e.g., EX1002, 2:5-21
`
`(describing WAP technology as “unfriendly, slow and cumbersome for users” and
`
`“the world’s largest mobile phone group . . . has avoided selling full music
`
`downloads on anything but top-of-the-range 3G phones because of the end-user
`
`difficulties associated with WAP.”); id, 17:28 (“WAP browser”); id, 32:8-11
`
`(“WAP page” and “WAP browser,” distinct from “MusicStation” software
`
`application). “Two alternatives to WAP based acquisition of full music content are
`
`
`difference between the Petition’s reliance on Abrams and the features purportedly
`
`disclosed by Sittig and applied in a rejection during original prosecution. 35
`
`U.S.C. § 325(d); Advanced Bionics, LLC v. MED-EL Elektromedizinische Gerate
`
`GmbH, IPR2019-01469, Paper 6 at 9 (PTAB Feb. 13, 2020) (precedential). Denial
`
`of institution under 325(d) is thus appropriate.
`
`8
`
`
`
`
`currently favored,” including “Music shop applications, running locally on a
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`mobile telephone.” EX1002, 2:27-32. Here again, the Petition inexplicably
`
`ignores the ’322 Patent specification, relying instead on “browsers” explicitly
`
`addressed in the Background and that lack critical elements of independent claim
`
`30.
`
`The Petition’s deficiencies in the Abrams grounds are not remedied by
`
`arguments (1) that the “browser” would “inherently” be “embodied on” the
`
`smartphone device because the “browser” does not have to be repeatedly
`
`reinstalled, or (2) that it would have been obvious to modify Abrams so the
`
`“browser” was “embodied on” the smartphone device. Pet., 20-21. Even if true as
`
`to the generic “browser” (which the Petition does not demonstrate), the Petition
`
`fails to show a software application that “enables an end-user to interact with other
`
`users” and “allows the end-user to” perform the claimed actions is “embodied on a
`
`non-transitory storage medium” and “executable on the smartphone device,” or any
`
`evidence that such elements would be “necessarily present” in Abrams’ user
`
`device. In re Robertson, 169 F.3d 743, 745 (Fed. Cir. 1999) (Inherency “may not
`
`be established by probabilities or possibilities. The mere fact that a certain thing
`
`may result from a given set of circumstances is not sufficient.”). Instead, Abrams’
`
`description shows Abrams’ preference in which the claimed configuration is not
`
`present—the features in Abrams that Petitioner relies upon are provided by a “Web
`
`9
`
`
`
`
`server,” not “embodied on” the purported smartphone. EX1009, [0077]. None of
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`the “interfaces” in Abrams identified by the Petition are part of the purported
`
`“browser,” nor are they “embodied on non-transitory memory” on the purported
`
`smartphone device. The “interfaces” in Abrams are accessible at the user device
`
`when pushed out by the web server, and the interfaces reflect whatever updates or
`
`changes are made at the web server each time the web page is displayed (e.g.,
`
`independent of the browser at the user device). Simply put, there is an
`
`irreconcilable disconnect between Petitioner’s identification of the “browser” as
`
`the purported “software application,” and identification of other system aspects
`
`that are provided by the remote “Web server.”
`
`To be clear, the Shamos declaration (EX1025) adds nothing. Pages 61-62
`
`and 75 cited in the Limitation 30.1 analysis, and pages 75-76 cited in the
`
`Limitation 30.2 analysis, include text that is nearly identical to the Petition. A
`
`declarant’s bare conclusion does not provide evidentiary support, and is
`
`insufficient to demonstrate features that are never specifically addressed. TQ
`
`Delta, LLC v. Cisco Sys., 942 F.3d 1352, 1362-64 (Fed. Cir. 2019). (reversing
`
`finding of obviousness and refusing to give weight to petitioner’s “ipse dixit
`
`declaration”); see also In re Am. Acad. of Sci. Tech Ctr., 367 F.3d 1359, 1368 (Fed.
`
`Cir. 2004) (“the Board is entitled to weigh the declarations and conclude that the
`
`lack of factual corroboration warrants discounting the opinions expressed in the
`
`10
`
`
`
`
`declarations”); Tate & Lyle Americas LLC v. Cargill, Inc., IPR2014-00084, Paper
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`12 at 17-18 (PTAB April 1, 2014); Kamada, ITD. V. Grigols Therapeutics Inc.,
`
`IPR2014-00899, Paper 43 at 10 (PTAB Dec. 15, 2015). In short, this is not a case
`
`in which the Board should give deference to Petitioner’s declarant at the institution
`
`stage.
`
`The Petition’s analysis of the “software application” elements fails for an
`
`additional, independent reason. The Petition never addresses the definition of
`
`“software application” and related claim terms in the ’322 Patent’s specification.
`
`For example, the ’322 Patent includes a “Definitions” section that defines the term
`
`“Software Application” as “The Client software application which is to be
`
`delivered over-the-air to, or pre-installed on, the Wireless Computing Device.”
`
`EX1002, 8:62-65; see also supra, Section II. The ’322 Patent itself thus limits the
`
`claimed “Software Application” according to its stated definition, and does not
`
`extend to generic “browsers” that do not meet this definition.
`
`The Board’s rules require that “the petition must set forth: . . . [h]ow the
`
`challenged claim is to be construed” and “[h]ow the construed claim is
`
`unpatentable.” 37 C.F.R. 42.104(b)(3)-(b)(4). In inter partes review, the logic of
`
`this requirement is apparent—petitioners carry the burden of proof and must state a
`
`complete prima facie case in the initiating petition. See Intelligent Bio-Systems,
`
`Inc. v. Illumina Cambridge, Ltd., 821 F.3d 1359, 1369 (Fed. Cir. 2016) (“the
`
`11
`
`
`
`
`expedited nature of IPRs bring with it an obligation for petitioners to make their
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`case in their petition to institute”). While a petitioner may include a statement that
`
`the claim requires no express construction, such a statement is not always
`
`sufficient, and it certainly is not sufficient here where the ’322 Patent specification
`
`includes a “Definitions” section that defines particular claim terms. E.g., Phillips,
`
`415 F.3d at 1316.
`
`
`
`Here, Petitioner attempts to evade its claim construction burden. The
`
`Petition includes a claim construction section indicating that, “[w]here necessary,
`
`claim construction is addressed below in Section V in the context of analyzing the
`
`patentability of claims in which the construed claims appear.” Pet., 5. But in the
`
`Section V mapping of the “software application” elements, the Petition never
`
`addresses the ’322 Patent’s definition of “Software Application,” and never
`
`attempts to map Abrams “browser” to the definition of “Software Application”
`
`provided by the ’322 Patent See, e.g., Pet., Section V.A. For example, the Petition
`
`never addresses delivery of Abrams purported “browser,” and never addresses
`
`whether the “browser” is “delivered over-the-air to, or pre-installed on,” the
`
`purported smartphone (e.g., versus alternative techniques such as a USB cable or
`
`other wired connection (see Section IV.B., infra)). The Petition simply ignores the
`
`12
`
`
`
`
`’322 Patent’s definition altogether.4 The Abrams grounds fail for this additional,
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`independent reason.
`
`B.
`
`The Petition Fails to Demonstrate that the System of Abrams
`Would Have “inherently” Performed the Claimed Functions
`“over a wireless connection” as Required by the Independent
`Claim (Grounds 1a-2b and 4a-6b)
` When addressing elements [30.4], [30.5], [30.6], [30.7], and [30.8], Triller
`
`repeatedly, yet incorrectly, insists that the “cellular telephones” briefly mentioned
`
`by Abrams would “inherently communicate with server apparatus 110 over a
`
`‘wireless connection’” to perform each of the functions recited by elements [30.4]-
`
`[30.8] and that “all interactions” between the cellular telephones and the server
`
`“inherently occur over a ‘wireless connection.’”5 Pet., 23, 27-30. The Shamos
`
`
`4 Petitioner’s strategy here defies the Board’s rules and fails to satisfy its burden to
`
`set forth both “[h]ow the challenged claim is to be construed” and “[h]ow the
`
`construed claim is unpatentable under the statutory grounds identified.” 37 C.F.R.
`
`§§ 42.104(b)(3) and 42.104(b)(4).
`
`5 The Petition addresses elements [31.4]-[31.8] through mere citation back to the
`
`analysis of elements [1.4]-[1.8]. Similar to claim 1, each of elements [31.4]-[31.8]
`
`recite that the claimed functions are performed “over [a/the] wireless connection.”
`
`Claim 31 therefore distinguishes over Abrams for the same reasons discussed here
`
`with respect to claim 1.
`
`13
`
`
`
`
`declaration does not expand upon, provide analysis with respect to, or identify
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`additional evidence to support this incorrect assertion that all communications in
`
`Abrams involving a cellular phone/PDA are “inherently” wireless, but rather
`
`merely repeats the same bald assertion as the Petition that “[a]ll interactions
`
`between the ‘server apparatus 110’ and user devices 106 and 108 are inherently via
`
`a ‘wireless connection’ when the user device is a ‘cellular telephone’ or PDA.”
`
`EX1025, p. 63 (cited at Pet., 23). However, there is simply no support in the record
`
`that “all” of the communications involved in performing each of the distinct
`
`functions of elements [30.4]-[30.8] would “inherently occur” over a wireless
`
`connection, as Triller asserts. Indeed, the evidence here shows the opposite.
`
`First, Abrams’ disclosure of “cellular telephones” is, at best, terse. Abrams
`
`makes passing reference to the fact that “user interface devices 106 & 108” may be
`
`implemented as “any device capable of presenting data, including, but not limited
`
`to, cellular telephones, television sets or hand-held ‘personal digital assistants’.”
`
`EX1009, [0074]. The discussion of the user interface devices 106 & 108 in
`
`general is also limited. They are merely described as being capable of receiving
`
`and displaying “Web pages” communicated “via the Internet 112.” Id., [0077],
`
`[0074].
`
`Furthermore, Triller’s assertion that the cellular telephone implementation of
`
`Abrams’ user interface devices 106 & 108 would “inherently” utilize wireless
`
`14
`
`
`
`
`communications for “all interactions” with the server when performing all of the
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`functions of elements [30.4]-[30.8] is not supported by any corroborating evidence
`
`or any analysis on the subject from Triller’s expert. Rather, Triller appears to rely
`
`on the reader’s understanding of capabilities of cellular telephones at the present
`
`time, without any discussion of the far more limited capabilities of cellular
`
`telephones prior to the May 5, 2006 priority date of the ’132 patent.6
`
`During the relevant time frame (prior to May 2006), early cellular phones
`
`capable of both voice and data communication relied upon a hybrid of wireless
`
`communications (for voice communications and certain limited data
`
`communication such as SMS messaging) and wired communications (for data
`
`communications). For example, as previously discussed, the software application
`
`described by the ’322 patent is directed toward providing social interaction and
`
`connection between various users to allow for the easy sharing of music and other
`
`media content. EX1002, 33:62-34:3, 36:32-54. Haeusel (Ex. 2002) describes that
`
`in prior art mobile phones, such communication of media content was provided to
`
`the mobile phone over a wired connection. Ex. 2002, [0042], [0059] (“media
`
`content includes video, music, and other data”). Specifically, Haeusel describes
`
`that users would generally “plug (i.e., ‘dock’) their mobile phone into their [set top
`
`
`6 See fn. 8, infra, re the proper May 5, 2006 priority claim of the ’132 patent.
`
`15
`
`
`
`
`box]. By interacting with an electronic programming guide (‘EPG’) displayed on a
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`television coupled to the STB, users connect to media content services such as
`
`electronic storefronts or virtual shopping to browse, select and then purchase
`
`and/or download media content such as music to their mobile phones through the
`
`STB.” Id. Such a physical connection was used to deliver media and other data to
`
`a cellular phone in prior art systems because “the mobile phone used in such an
`
`arrangement needs no modifications or alterations.” Id.
`
`The data provided to the mobile phone over the physical, wired connection
`
`is communicated to the set top box via “distributed networks such as the Internet.”
`
`Id., [0043]. Hausel also provides depictions of the state of the art cell phones of
`
`the time, far from the fully functional, touch-screen smart phones of today:
`
`
`
`16
`
`
`
`
`Ex. 2002, Figs. 2-5. Such mobile phones included “accessory connector[s] 238”
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`for connecting accessories such as “data cables.” Id., [0049]. Haeusel describes
`
`that “contacts in contact set 626 used for data transmission are operatively coupled
`
`to the mobile phone's I/O controller circuitry.” Id., [0055], see also [0057]
`
`(describing various physical connection arrangements, including USB, for
`
`communicating data to the cell phone).
`
`As another example, Lipsit (Ex. 2003) describes that data communications
`
`between cellular telephones and other computing devices would often occur over a
`
`physical, wired connection. FIG. 1 of Lipsit shows “a cellular telephone 160” in
`
`communication with a computer 102 over a wired, physical connection:
`
`
`
`17
`
`
`
`
`Ex. 2001, FIG. 1, 4:15-25. Specifically, Lipsit describes that “[t]he computer 102
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`is connected to a serial interface 150 via a cable 135 which connects the serial
`
`port 114 of the computer 102 to the serial interface 150. The serial interface 150 is
`
`connected to a data interface port 162 of a cellular telephone 160, via cable 155.”
`
`Id. Lipsit goes on to describe that “[t]he data interface port 162 allows the
`
`microprocessor of the cellular telephone 160 to communicate with external
`
`devices. Thus, cable 135, serial interface 150, and cable 155 allow the computer
`
`102 to communicate with the cellular telephone 160.” Id. Lipsit goes on to
`
`describe conducting data communication with the cellular telephone 160 “via the
`
`serial interface 150 and cables 135 and 155.” Id., 8:3-9.
`
`Similarly, Dickie (Ex. 2001) describes a PDA 102 implemented as a
`
`“cellular phone” that communicates with a portable computer 104 via a physical
`
`docking cradle 120. Ex. 2001, [0013]-[0016]. Data communication for various
`
`applications executing on the cellular phone, including calendar and email
`
`applications, occurs over the physical dock connection. Id., [0013], [0030]. As
`
`Dickie explains “[i]n addition to physically mounting the PDA 102, the PDA
`
`docking cradle 120 provides an interface that supports both data communication
`
`and power resources. In this manner, the integrated PDA docking cradle 120 offers
`
`the cradle functionality to interface the PDA 102 with the portable computer 104,
`
`thereby eliminating the need for external docking cradles.” Id., [0020]. The user
`
`18
`
`
`
`
`can fully interact with the cellular phone to interact with these applications when
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`the cellular phone is docked. Id., [0021].
`
`As can be seen from these examples, wired connections for providing data
`
`communications with cellular telephones were ubiquitous during the relevant time
`
`frame. Communication of application data, such as that described in Abrams, over
`
`a wireless connection is anything but “inherent[]” and wireless communication was
`
`certainly not utilized for “all interactions” between cellular phones and servers in
`
`prior art systems, as Triller asserts. In re Robertson, 169 F.3d at 745 (Inherency
`
`“may not be established by probabilities or possibilities. The mere fact that a
`
`certain thing may result from a given set of circumstances is not sufficient.”).
`
`Indeed, the ’322 patent expressly describes that one of the “[b]enefits” of the
`
`claimed invention was that the claimed functions are performed “when on the
`
`move, not just when it is physically attached to an internet-connected PC.”
`
`EX1002, 4:18-22.
`
`Furthermore, Triller has not even attempted to provide any evidence that the
`
`wireless communication of all application data “is necessarily present” in the prior
`
`art in general or in Abrams’ system specifically. Continental Can Co. USA v.
`
`Monsanto Co., 948 F.2d 1264, 1268 (Fed. Cir. 1991) (“Such evidence must make
`
`clear that the missing descriptive matter is necessarily present in the thing
`
`described in the reference, and that it would be so recognized by persons of
`
`19
`
`
`
`
`ordinary skill.”). The fact that a certain function may occur or be present in the
`
`Case IPR2022-00180
`Attorney Docket No: 50048-0016IP1
`
`prior art is not sufficient to establish the inherency of that function. In re Rijckaert,
`
`9 F.3d 1531, 1534 (Fed. Cir. 1993); In re Robertson, 169 F.3d at 745.
`
`The only citation in Triller’s assertion in the Petition regarding the functions
`
`of elements [30.4]-[30.8] being performed “over a wireless connection” is a nearly
`
`identical, two sentence statement in Triller’s Shamos declaration. Compare Pet.,
`
`22-23 with EX1025, p. 63. But a declarant’s bare conclusion, unsupported by any
`
`underlying facts or data, does not provide evidentiary support and is insufficient to
`
`demonstrate features that are never specifically addressed. TQ Delta, 942 F.3d at
`
`1362-64 (reversing finding of obviousness and refusing to give weight to
`
`petitioner’s “ipse dixit declaration”). Triller has therefore failed to that establish
`
`that each of the functions recited by elements [30.4]-[30.8] is inherently performed
`
`“over a wireless connection” in Abrams’ system.
`
`Triller’s insistence that the mere presence of a cellular phone somehow
`
`indicates each of the functions recited by elements [30.4]-[30.8] are inherently
`
`performed “over a wireless connection” essentially reads this requirement entirely
`
`out of the claim. This unsupported assertion by Triller “turns the Petition into an
`
`empty invitation f