throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`PLAID TECHNOLOGIES INC.
`Petitioner
`
`v.
`
`YODLEE, INC.
`Patent Owner
`
`Case IPR2016-00273
`Patent 6,317,783
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`Plaid Technologies Inc.
`Exhibit 1011
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`TABLE OF CONTENTS
`
`I. 
`
`INTRODUCTION ........................................................................................ 1 
`
`II.  STATEMENT OF RELIEF REQUESTED ................................................. 2 
`
`III.  CLAIM CONSTRUCTION ......................................................................... 2 
`
`A. 
`
`B. 
`
`“non-public personal information” (Claims 1, 18, 20) ............. 2 
`
`“intermediary web site” (Claims 14, 33) .................................. 5 
`
`IV.  THE BOARD SHOULD NOT INSTITUTE PETITIONER’S
`CHALLENGES ............................................................................................ 6 
`
`A. 
`
`Claim 1 ...................................................................................... 6 
`
`1.  [1.1]: A method for delivering non-public personal
`information relating to an end user via a wide-area
`computer network to an end user .............................................. 9 
`
`2.  [1.2]: from at least one of a plurality of information
`providers securely storing the personal information .............. 12 
`
`3.  [1.5]: (b) for a selected end user, the processor retrieving
`personal information for the selected end user from the
`connected at least one information provider .......................... 13 
`
`4.  [1.7]: the information accessible to the processor using
`the protocol also being accessible by the end user via
`the network independently of the system for delivering
`personal information; and ...................................................... 13 
`
`5.  [1.8]: (c) the processor storing the retrieved personal
`information in a personal information store for access
`by the selected end user. ......................................................... 14 
`
`B. 
`
`C. 
`
`D. 
`
`E. 
`
`Claims 6, 7, 10-12, and 14-17 ................................................ 14 
`
`Claim 18.................................................................................. 14 
`
`Claim 20.................................................................................. 15 
`
`Claims 25, 26, 28-31, and 33-36 ............................................ 15 
`
`V.  CONCLUSION .......................................................................................... 15
`
`
`
`i
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Cases
`Cohesive Techs., Inc. v. Waters Corp.,
`543 F.3d 1351 (Fed. Cir. 2008) ....................................................................... 6
`
`KSR Int’l Co. v. Teleflex Inc.,
`550 U.S. 398 (2007) ................................................................................... 8, 12
`
`Statutes
`
`35 U.S.C. § 103 ..................................................................................................... 8
`
`35 U.S.C. § 314 ................................................................................................... 15
`
`ii
`
`
`
`
`
`
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`EXHIBIT LIST
`
`Exhibit No. Description
`2001
`ESPN Insider: Benefits, WayBackMachine June 22, 2001
`
`
`
`
`
`
`
`iii
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`Pursuant to 37 C.F.R. § 42.107(a), the Patent Owner, Yodlee, Inc.
`
`(“Yodlee” or “Patent Owner”), hereby submits the following Preliminary
`
`Response in opposition to the Petition for Inter Partes Review (“IPR”) of U.S.
`
`Patent No. 6,317,783 (“the ʼ783 Patent”) numbered IPR2016-00273, filed by
`
`Plaid Technologies, Inc. (“Plaid” or “Petitioner”).
`
`I.
`
`INTRODUCTION
`
`The ’783 Patent is entitled “Apparatus and Methods For Automated
`
`Aggregation and Delivery of and Transactions Involving Electronic Personal
`
`Information or Data.” As the specification makes clear, the ’783 Patent is
`
`directed to overcoming specific problems that plagued early personalization
`
`technologies. Ex. 1001 at 4:22-51. Every claim (and in fact, almost every
`
`limitation of many of the claims) requires technology that operates on non-
`
`public personal information – specialized technology that is designed to enable
`
`the storage, retrieval, and use of non-public personal information. See, e.g.,
`
`independent claim 1. As described below, the term “personal information” is
`
`even specifically described within the body of the ’783 Patent itself and the file
`
`history.
`
`While Petitioner acknowledges the focus on non-public personal
`
`information in both the specification and the file history of the ’783 Patent, the
`
`Petition lacks any detail regarding how the cited grounds would disclose or
`
`suggest it. As described below, Petitioner focuses solely on the prior art
`
`disclosure of public information and never shows the prior art disclosure of the
`
`
`
`1
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`required “non-public personal information.” In fact, even accepting Petitioner’s
`
`assertion as correct, it only alleges the prior art to disclose “non-public”
`
`information and then asserts that the information is “personal” by virtue of it
`
`being non-public. Petitioner is flawed on both accounts and its arguments
`
`cannot stand.
`
`II.
`
`STATEMENT OF RELIEF REQUESTED
`
`Patent Owner respectfully requests that this Board deny this Petition for
`
`IPR of the ’783 Patent with regard to all claims (1-36).
`
`III. CLAIM CONSTRUCTION
`A.
`“non-public personal information” (Claims 1, 18, 20)
`
`Petitioner proposes that the term “non-public” be construed. However,
`
`the term “non-public” only appears in the claims as part of the larger phrase
`
`“non-public personal information.” In proposing and applying its construction,
`
`Petitioner effectively seeks to remove the word “personal” from the claims by
`
`asserting that any information which meets Petitioner’s proposed construction
`
`of “non-public,” is also “non-public personal information.” See Petition at 12.
`
`The specification makes clear that this is not the case. Moreover, the
`
`specification makes it clear that “non-public personal information” has a
`
`specific meaning.
`
`Petitioner’s proposed construction (and in fact its entire argument for
`
`invalidity) appears to hinge on the incorrect assumption that any information for
`
`which a login is required is “non-public personal information.” This argument
`
`
`
`2
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`completely misses the point of the inventive system. As shown below, the prior
`
`art systems upon which Petitioner relies are systems that use logins as a means
`
`to extract payment from a user. For example, the ESPN Insider system, which
`
`purportedly shown in Exhibit 1011 and relied upon by Petitioner’s expert,
`
`required users to pay a fee to access news reports on sporting events. Ex. 2001,
`
`ESPN Insider: Benefits, WayBackMachine, June 22, 2001. This information,
`
`however, is no different from the stories published in the local newspaper. Like
`
`the ESPN Insider system, a reader must pay a fee to access the news stories
`
`(e.g., the one dollar purchase price for the paper), but regardless of how they are
`
`financed, news stories are not “non-public” much less “personal” information,
`
`as the ’783 Patent uses that term.
`
`As the specification of the ’783 Patent describes, “‘Personal Information’
`
`is all of the data that companies, information providers, have that is specific or
`
`unique to each person such as monthly bills, bank account balances,
`
`investments information, health care benefits, email, voice and fax messages,
`
`401(k) holdings or potentially any other information pertinent to a particular
`
`end user.” Ex. 1001 at 4:15-21. The file history confirms that “the essence of
`
`personal information is that it is not accessible to the general public, i.e., other
`
`end users; rather, each information provider protects personal information
`
`relating to a specific end user against access by persons other than that end
`
`user or one acting under the authority of that end user.” Ex. 1003 at 168.
`
`
`
`3
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`Anyone who pays a fee can access a pay-for-news provider, such as
`
`ESPN Insider. That website is accessible to the general public. On the
`
`contrary, regardless of fee, no other person can (or at least should not be able to)
`
`access another person’s bank
`
`records, stock portfolio, etc., without
`
`authorization. As the intrinsic evidence makes clear, this is “the essence” of the
`
`claimed system. The public cannot access it regardless of fee – it is personal to
`
`the user.
`
`While “pay for play” content and “non-public personal information” may
`
`use similar security features, such as a login, the security features used to
`
`protect non-public personal information do not somehow convert that claim
`
`limitation to include all information regardless of whether it is public or
`
`personal into “non-public personal information.”1 This construction is further
`
`
`1 For example, Petitioner relies on the language “such as by logging onto a Web
`
`site” to support its construction of “non-public.” However, that statement was
`
`made in the context of how a user could access personal information
`
`“independently of the invention.” This corresponds to another aspect of the
`
`claim, particularly that the information is “accessible by the end user via the
`
`network independently of the system for delivering personal information.” See
`
`Ex. 1001, ’783 Patent, claim 1. This language does not inform the meaning of
`
`“non-public.”
`
`
`
`
`
`4
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`confirmed by claim 1’s recitation of “securely storing” as a requirement
`
`separate and apart from “non-public personal information.” If, as Petitioner
`
`asserts, all information that is protected by a login and password were “non-
`
`public personal information,” there would be no need to separately recite
`
`“securely storing” in the claims. The recitation of “securely storing” would
`
`render the “non-public personal” recitation wholly redundant.
`
`Accordingly, in line with the specification, Patent Owner proposes that
`
`the broadest reasonable construction of “non-public personal information” is
`
`“information relating to a specific end user that is not intended for access by
`
`persons other than that end user or those authorized by that end user.”
`
`B.
`
` “intermediary web site” (Claims 14, 33)
`
`Petitioner argues that an “intermediary web site” must be served by a web
`
`server not running on the end user’s computer and not running on the
`
`“processor” of the claims. However, in the passage that Petitioner relies upon,
`
`the ’783 Patent states that “[t]he intermediary Web site 510 contacts the PI
`
`engine 240 across the Internet 230 and directly receives the end user's PI
`
`updated as required from the PI provider Web sites 250.” Ex. 1001, ’783 Patent
`
`at 12:18-21. Thus, the intermediary Web site is directly in contact with the PI
`
`engine and directly receives information from the PI provider, which are both
`
`running on the claimed “processor” – the intermediary Web site is “served” by
`
`the “processor” itself. Petitioner’s argument that the intermediary web site must
`
`be served by a server not running on the “processor” is unsupported and
`
`
`
`5
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`contradicted by the disclosure in the specification. The proper construction of
`
`the “intermediary web site” should therefore be: “a Web site that obtains an end
`
`user’s personal information from the “processor” for display to that end user.”
`
`Patent Owner has addressed the claim terms addressed by Petitioner and
`
`those relevant to the arguments made in this preliminary response. To the
`
`extent that this case is instituted, Patent Owner reserves the right to address
`
`additional claim construction issues that arise with respect to its further
`
`arguments to be made in the Patent Owner’s Response.
`
`IV. THE BOARD SHOULD NOT INSTITUTE PETITIONER’S
`CHALLENGES
`
`In order to make a showing of obviousness, Petitioner must show that a
`
`proposed combination of references discloses all limitations of the challenged
`
`claims. See Cohesive Techs., Inc. v. Waters Corp., 543 F.3d 1351, 1364 (Fed.
`
`Cir. 2008). Petitioner has failed to make such a showing here and thus the
`
`Petition should be denied in full. Particularly, Petitioner has failed to show
`
`evidence that the “non-public personal information” limitation recited in each of
`
`the challenged claims is present in any of the alleged prior art references or in
`
`the combinations of the prior art references relied upon by Petitioner.
`
`A. Claim 1
`
`Claim 1 of the ’783 Patent contains numerous limitations that involve
`
`“non-public personal information.” Each of those limitations (identified using
`
`Petitioner’s numbering system) is reproduced below:
`
`
`
`6
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`[1.1]: A method for delivering non-public personal
`
`information relating to an end user via a wide-area
`
`computer network to an end user
`
`[1.2]: from at least one of a plurality of information
`
`providers securely storing the personal
`
`information
`
`[1.5]: (b) for a selected end user, the processor
`
`retrieving personal information for the selected
`
`end user from the connected at least one
`
`information provider
`
`[1.6]: based on end user data associated with the
`
`selected end user and information provider data
`
`associated with the connected one or more
`
`information providers, the end user data including
`
`information identifying the plurality of information
`
`providers securely storing the personal
`
`information relating to the end user, the provider
`
`data including a protocol for instructing the
`
`processor how to access the securely stored
`
`personal information via the network,
`
`[1.7]: the information accessible to the processor
`
`using the protocol also being accessible by the end
`
`
`
`7
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`user via the network independently of the system
`
`for delivering personal information; and
`
`[1.8]: (c) the processor storing the retrieved personal
`
`information in a personal information store for
`
`access by the selected end user.
`
`Petitioner has wholly failed to establish that “non-public personal
`
`information” is disclosed by the combination of references upon which
`
`Petitioner relies. As described below, Petitioner identifies only public
`
`information in the prior art and fails to identify any prior art that discloses non-
`
`public, personal information.
`
`In fact, nowhere in the Petition does Petitioner ever appear to even
`
`acknowledge the “personal” aspect of the claim. Instead, Petitioner merely
`
`repeats the claim language, without ever identifying any “personal information”
`
`much less the “non-public personal information” required by the claims. Such
`
`conclusory allegations are insufficient as a matter of law to prove obviousness
`
`under 35 U.S.C. § 103. See KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418
`
`(2007) (obviousness analysis “should be made explicit. . . . ‘[R]ejections on
`
`obviousness grounds cannot be sustained by mere conclusory statements;
`
`instead, there must be some articulated reasoning with some rational
`
`underpinning to support the legal conclusion of obviousness.’”)
`
`Petitioner’s specific failure to prove this element is discussed separately
`
`below for each claim element in which “personal information” is recited.
`
`
`
`8
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`1.
`
`[1.1]: A method for delivering non-public personal
`information relating to an end user via a wide-area
`computer network to an end user
`
`With respect to limitation [1.1], Petitioner fails to ever specifically
`
`identify what allegedly discloses the “personal information” aspect of the claim
`
`language. As noted above, Petitioner’s argument is essentially limited to the
`
`“non-public” aspect of the claim language. Petitioner alleges that Brandt
`
`discloses information protected with a user name and password. Petition at 29.
`
`Based solely on this reasoning, Petitioner then asserts that the combination of
`
`Sugiarto and Brandt “would obtain ‘non-public personal information.’” Id.
`
`However, as noted above in the claim construction section, while
`
`protection by a login may be relevant to the “securely storing” aspect of the
`
`claims, it is irrelevant to the question of whether a prior art reference discloses
`
`non-public personal information, as recited in the claims. Moreover, Brandt is
`
`not even directed to protecting information but rather to protecting access to a
`
`piece of software. As Petitioner even notes in describing Brandt “access to a
`
`protected software application 342 is only granted after gateway 332 supplies
`
`the user’s user name and password.” Petition at 29, citing Ex. 1005 12:15–36;
`
`Ex. 1008, Mowry Decl., ¶ 78. The word “information” is never even used in
`
`Brandt. For each of these reasons, the disclosure of Brandt cannot possibly
`
`teach the required “non-public personal information.”
`
`To overcome this deficiency in Brandt, Petitioner seeks to rely on
`
`Sugiarto’s disclosure of collecting public information from a webpage. In
`
`
`
`9
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`particular, Petitioner points to Figure 7 of Sugiarto, which displays information
`
`taken from CNN, ESPN, and the NASDAQ stock exchange. Petitioner then
`
`appears to argue that the public information sources disclosed in Sugiarto would
`
`somehow become non-public personal information if they were placed behind
`
`Brandt’s password system.
`
`This argument is fundamentally flawed. News stories, sports scores, and
`
`stock market quotes do not become non-public personal information simply
`
`because one needs to pay money to access them. For example, the Petition
`
`mentions ESPN Insider, a subscription service that offers access to various news
`
`articles, audio recordings, charts, or statistics about sports. See Ex. 1011 at 3.
`
`The ESPN Insider service – which is never actually mentioned in the cited prior
`
`art – appears to require a login to enable payment for the content. See Ex. 2001,
`
`ESPN Insider: Benefits, WayBackMachine June 22, 2001. The content is still
`
`clearly intended for the public – for anyone willing to pay the $4.95 per month
`
`to access it. While this may only be a few hundred thousand people, these
`
`sports scores are public, not personal. In fact, ESPN Insider could not exist if it
`
`were reporting for an audience of one. By its very nature, the ESPN Insider
`
`service is information for any member of the public willing to pay the monthly
`
`fee.
`
`Moreover, even if one were to incorrectly conclude that professional
`
`sports information, news stores, or stock quotes could somehow qualify as
`
`“non-public,” they certainly cannot qualify as “personal information.” For
`
`
`
`10
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`example, every subscriber of ESPN Insider would obtain access to the same
`
`content precisely because the information is not “personal” to any individual
`
`user. Nor does Petitioner or its expert assert that it would somehow be obvious
`
`for one of ordinary skill in the art to modify the disclosures of Brandt and
`
`Sugiarto to include the recited “non-public personal information.”2 Thus, even
`
`accepting Petitioner’s allegation that it was proper to combine Brandt or
`
`Sugiarto, the combination of those references is wholly insufficient to disclose
`
`the “non-public personal information,” recited in claim 1.
`
`Finally, because Petitioner has failed to identify the alleged “personal
`
`information,” it has not shown that the remainder of the claim language is
`
`satisfied. For example, the claim recites “personal information relating to an
`
`end user.” Because Petitioner has not identified the personal information, it
`
`cannot prove anything about the content of that information, including whether
`
`it “relat[es] to an end user.” Petitioner attempts to argue this limitation by
`
`saying that the end user “is the person ‘to whom the personal information
`
`relates’ because the personalized Web page is based on the user’s configuration
`
`file.” Petition at 28. However, that argument fails to identify the “personal
`
`
`2 Neither Petitioner nor its expert provided any reason or motivation that would
`
`compel or suggest such a modification to one of ordinary skill. Thus, there is
`
`no factual basis in the record to support such a combination – even if it were
`
`asserted.
`
`
`
`11
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`information” and thus fails to explain how the content of the information itself
`
`relates to the user. The fact that the configuration file determines what content
`
`is presented and how does not establish that the information being retrieved is
`
`itself “personal information relating to an end user.”
`
`Petitioner simply does not explain how Brandt (or the proposed
`
`combination of Sugiarto and Brandt) discloses “non-public personal
`
`information” that satisfies the full language of limitation [1.1]. Merely
`
`repeating
`
`the claim
`
`language
`
`in conclusory statements cannot satisfy
`
`Petitioner’s burden to explicitly show how the references allegedly disclose this
`
`limitation of the ’783 Patent. See KSR, 550 U.S. at 418.
`
`2.
`
`[1.2]: from at least one of a plurality of information
`providers securely storing the personal information
`
`Here again, Petitioner fails to specifically identify the alleged “the
`
`personal information” (antecedent basis to the recited “non-public personal
`
`information”) or establish that it satisfies the remaining claim language, namely
`
`that the alleged personal information is “securely stor[ed]” by the “information
`
`providers.” Petitioner simply refers back to its deficient analysis of limitation
`
`[1.1]. Petition at 30. Indeed, Petitioner does not even allege that the
`
`information is securely stored, instead alleging that the combination would
`
`“obtain information from secure content providers” without explaining how that
`
`satisfies the claim language. This analysis is insufficient to make a showing of
`
`obviousness. See KSR, 550 U.S. at 418 (“there must be some articulated
`
`
`
`12
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`reasoning with some rational underpinning to support the legal conclusion of
`
`obviousness”). Nor could Petitioner make a showing of obviousness, given that
`
`Petitioner has failed to identify the alleged “personal information” and thus
`
`cannot say anything about how that information is stored by the alleged
`
`information providers.
`
`3.
`
`[1.5]: (b) for a selected end user, the processor retrieving
`personal information for the selected end user from the
`connected at least one information provider
`
`For limitation [1.5], Petitioner again exclusively refers back to its
`
`deficient analysis for limitation [1.1]. Tellingly, however, Petitioner only
`
`alleges that the modules “retrieve information from respective secure content
`
`providers.” Petition at 32. Here, Petitioner does not even allege that the
`
`information retrieved is “personal information.”
`
`4.
`
` [1.7]: the information accessible to the processor using
`the protocol also being accessible by the end user via the
`network independently of the system for delivering
`personal information; and
`
`Petitioner makes no further argument in its analysis of limitation [1.7]
`
`relating to the “system for delivering personal information,” i.e. the entirety of
`
`claim 1. Thus, for each of the reasons discussed above, Petitioner fails to show
`
`evidence that this limitation is disclosed by the cited prior art.
`
`
`
`13
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`5.
`
`[1.8]: (c) the processor storing the retrieved personal
`information in a personal information store for access by
`the selected end user.
`
`Petitioner’s argument with respect to limitation [1.8] is directed entirely
`
`toward how information is stored by the prior art combination. Petitioner
`
`makes no further argument with respect to what information is stored and
`
`simply refers to it using the claim language “personal information.” Thus,
`
`Petitioner has failed to prove that limitation [1.8] is shown in the prior art for
`
`each of the reasons discussed above.
`
`B. Claims 6, 7, 10-12, and 14-17
`
`Petitioner groups its analysis of these claims, each of which recites
`
`“personal information.” However, Petitioner makes no further analysis of what
`
`qualifies as “personal information.” Instead, Petitioner’s arguments relate to
`
`how the information is allegedly output and/or displayed. Thus, the analysis of
`
`these claims does not show that the prior art discloses the “personal
`
`information” limitation.
`
`C. Claim 18
`
`Independent claim 18 also includes numerous limitations reciting
`
`“personal information”: limitations [18.1], [18.2], [18.5], [18.7], and [18.8].
`
`Petitioner makes no independent analysis of claim 18, but instead solely refers
`
`back to its analysis of claim 1. See Petition at 51. Thus, Petitioner fails to show
`
`that claim 18 is rendered obvious by the proposed combination, for the same
`
`reasons Petitioner failed to show that claim 1 is rendered obvious.
`
`
`
`14
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`D. Claim 20
`
`Independent claim 20 also includes numerous limitations reciting
`
`“personal information”: [20.1], [20.3], [20.5], [20.7], [20.8], [20.9], [20.12], and
`
`[20.13]. For each of these limitations, Petitioner makes no independent
`
`analysis, but instead solely refers back to its analysis of claim 1. See Petition at
`
`52-53. Thus, Petitioner fails to show that claim 20 is rendered obvious by the
`
`proposed combination, for the same reasons Petitioner failed to show that claim
`
`1 is rendered obvious.
`
`E. Claims 25, 26, 28-31, and 33-36
`
`Dependent claims 25, 26, 28-31, and 33-36 each recite “personal
`
`information.” For dependent claims 25, 26, 28-31, and 33-36, Petitioner makes
`
`no independent analysis but solely refers back to its analysis of claims 6, 7, 9-
`
`12, and 14-17 respectively. Thus, for the same reasons, Petitioner has failed to
`
`establish that the “personal information” limitation is shown in the prior art.
`
`V. CONCLUSION
`
`The Petitioner has the burden to show that institution is warranted in
`
`these cases at all. 35 U.S.C. § 314. Petitioner has not met that burden and the
`
`Petition should be denied in full.
`
`15
`
`
`
`
`
`
`
`

`
`Dated: March 11, 2016
`
`Respectfully submitted,
`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`
`
`
`
`
`
`
`
`
`
` By: /David M. Hoffman/
` David M. Hoffman
`Reg. No. 54,174
`
`Fish & Richardson P.C.
`3200 RBC Plaza
`60 South Sixth Street
`Minneapolis, MN 55402
`T: (512) 226-8154
`F: (512) 320-8935
`Email: IPR12233-0047IP1@fr.com
`
`
`Counsel for Patent Owner
`Yodlee, Inc.
`
`
`
`16
`
`
`
`

`
`Case IPR2016-00273
`Attorney Docket No: 12233-0047IP1
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 CFR §§ 42.6(e)(4), the undersigned certifies that on March
`
`11, 2016, a complete and entire copy of this Patent Owner’s Preliminary
`
`Response was provided via electronic service to the Petitioner, by serving the
`
`correspondence address of record as follows:
`
`Brian Buroker
`Omar Amin
`Gibson, Dunn & Crutcher LLP
`1050 Connecticut Avenue, N.W.
`Washington, D.C. 20036-5306
`
`E-mail: bburoker@gibsondunn.com
` oamin@gibsondunn.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` /Jessica K. Detko/
`Jessica K. Detko
`Fish & Richardson P.C.
`60 South Sixth Street, Suite 3200
`Minneapolis, MN 55402
`(612) 337-2516
`
`
`
`
`
`
`
`17

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