throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`SAMSUNG ELECTRONICS AMERICA, INC. and
`SAMSUNG ELECTRONICS CO., LTD.,
`Petitioner
`
`v.
`
`SMARTFLASH LLC,
`Patent Owner
`
`
`
`
`
`
`
`
`Case CBM2014-00199
`Patent 8,118,221
`
`
`
`
`
`
`
`
`
`
`
`
`
`PETITIONERS’ REPLY TO PATENT OWNER’S RESPONSE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`
`
`TABLE OF CONTENTS
`
`
`
`I. Introduction ........................................................................................................... 1
`II. Testimony from Dr. Bloom Deserves Full Credit (POR §§ II & III) ................... 1
`A. Dr. Bloom’s testimony is grounded in underlying facts and data, and
`worthy of weight, despite PO’s unsupported suggestion that his
`declaration must state the evidentiary standard used in formulating his
`opinions (POR § II & III) ........................................................................... 1
`
`B. The POR’s allegation of bias of Dr. Bloom is unfounded and purely
`speculative (POR § III) ............................................................................... 3
`
`III. Claim Construction (POR § IV) ........................................................................... 6
`A. Petitioner’s proposed construction of “payment data” comports with
`ordinary and customary meaning, as imparted by the specification of the
`‘221 Patent. ................................................................................................. 6
`
`IV. Claims 2 and 11 are anticipated by Ginter (POR § V) .................................... 8
`A. Ginter teaches claim 1, from which claims 2 and 11 depend ..................... 9
`
`B. Ginter teaches claim 2: A data access terminal as claimed in claim 1,
`further comprising code to transmit at least a portion of the payment
`validation data to the data supplier or to a destination received from the
`data supplier. ............................................................................................. 20
`
`C. Ginter teaches claim 11 ............................................................................ 25
`
`
`
`
`
`
`
`
`
`i
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`EXHIBIT LIST
`SAMSUNG-1001 U.S. Patent No. 8,118,221 to Racz et al. (“the ‘221 Patent” or
`“’221”)
`
`SAMSUNG-1002 Excerpts from the Prosecution History of the ‘221 Patent (“the
`Prosecution History”)
`
`SAMSUNG-1003 Declaration of Dr. Jeffrey Bloom re the ‘221 Patent (“Bloom”)
`
`SAMSUNG-1004 RESERVED
`
`SAMSUNG-1005 RESERVED
`
`SAMSUNG-1006 RESERVED
`
`SAMSUNG-1007 PCT Application No. PCT/GB00/04110 (“the ‘110 Appln.” Or
`“‘110”)
`
`SAMSUNG-1008 United Kingdom Patent Application GB9925227.2 (“the ‘227.2
`Appln.” or “‘227.2”)
`
`SAMSUNG-1009 Transitional Program for Covered Business Method Pa-tents—
`Definitions of Covered Business Method Patent and
`Technological Invention, 77 Fed. Reg. 157 (August14, 2012)
`
`SAMSUNG-1010 A Guide to the Legislative History of the America Invents Act;
`Part II of II, 21 Fed. Cir. Bar J. No. 4
`
`SAMSUNG-1011 Interim Guidance for Determining Subject Matter Eligibility for
`Process Claims in View of Bilski v. Kappos (July 27, 2010)
`
`SAMSUNG-1012 Apple Inc. v. Sightsound Technologies, LLC, CBM2013-00019
`Paper No. 17 (entered October 8, 2013) at 11-13
`
`SAMSUNG-1013 Volusion, Inc. v. Versata Software, Inc. and Versata Devel-
`opment Group, Inc., CBM2013-00017 Paper No. 8 (entered
`October 24, 2013)
`
`
`
`
`
`ii
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`SAMSUNG-1014 Salesforce.com, Inc. v. VirtualAgility, Inc., CBM2013-00024
`Paper No. 16 (entered November 19, 2013)
`
`SAMSUNG-1015 RESERVED
`
`SAMSUNG-1016 RESERVED
`
`SAMSUNG-1017 RESERVED
`
`SAMSUNG-1018 RESERVED
`
`SAMSUNG-1019 U.S. Patent No. 7,942,317 (“the ‘317 Patent” or “‘317”)
`
`SAMSUNG-1020 U.S. Patent Application No. 12/014,558
`
`SAMSUNG-1021 U.S. Patent No. 7,334,720 (“the ‘720 Patent” or “‘720”)
`
`SAMSUNG-1022 U.S. Patent Application No. 12/943,872 (“the ‘872 Appln.” or
`“872”)
`
`SAMSUNG-1023 U.S. Patent No. 5,915,019
`
`
`
`SAMSUNG-1024 Affidavit in Support of Petitioner's Motion for Pro Hac Vice
`Admission of Ralph A. Phillips
`
`SAMSUNG-1025 RESERVED
`
`SAMSUNG-1026 RESERVED
`
`SAMSUNG-1027 RESERVED
`
`SAMSUNG-1028 RESERVED
`
`SAMSUNG-1029 RESERVED
`
`SAMSUNG-1030 RESERVED
`
`SAMSUNG-1031 RESERVED
`
`
`
`
`iii
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`SAMSUNG-1032 RESERVED
`
`SAMSUNG-1033 RESERVED
`
`SAMSUNG-1034 RESERVED
`
`SAMSUNG-1035 RESERVED
`
`SAMSUNG-1036 RESERVED
`
`SAMSUNG-1037 RESERVED
`
`SAMSUNG-1038 RESERVED
`
`SAMSUNG-1039 RESERVED
`
`SAMSUNG-1040 RESERVED
`
`SAMSUNG-1041 RESERVED
`
`SAMSUNG-1042 RESERVED
`
`SAMSUNG-1043 Kennametal, Inc. v. Ingersoll Cutting Tool Co., 780 F.3d 1376,
`1381 (Fed. Cir. 2015)
`
`SAMSUNG-1044 RESERVED
`
`SAMSUNG-1045 Nautilus, Inc. v. Biosig Instruments, Inc., 134 S. Ct. 2120
`(2014)
`
`SAMSUNG-1046 Markman v. Westview Instruments, Inc., 517 U.S.370 (1996)
`
`SAMSUNG-1047 In re Am. Acad. Sci., 367 F.3d 1359, 1364 (Fed.Cir.2004)
`
`SAMSUNG-1048 Microstrategy, Inc. v. Zillow, Inc, IPR2013-00034, Paper 42
`
`
`
`
`
`iv
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`I.
`
`Introduction
`
`Smartflash (“Patent Owner”) does not dispute that the claimed data access
`
`terminal is used for data processing in the practice, administration, and
`
`management of financial products and services; specifically, for processing
`
`payments for data downloads. Petition at 8-11. Nor does the Patent Owner’s
`
`response (POR) deny that the challenged claims are not directed to a technological
`
`invention. Petition at 11-13.
`
`Instead, Patent Owner alleges that Dr. Bloom’s testimony should be given
`
`little or no weight. POR at 2-3. Patent Owner then attempts to advance that
`
`particular passages from the prior art are without disclosure of the claimed
`
`“payment data,” assuming an unduly narrow construction of “payment data” (See
`
`POR at 4-6) and assuming that the prior art passages are read in isolation (See POR
`
`at 6-41).
`
`As demonstrated below, the Petitioner addresses POR’s arguments regarding
`
`Dr. Bloom (POR § III) before delving into the substantive discussion (POR §§ IV
`
`and V) on claim construction and anticipation.
`
`II. Testimony from Dr. Bloom Deserves Full Credit (POR §§ II & III)
`
`
`A. Dr. Bloom’s testimony is grounded in underlying facts and
`data, and worthy of weight, despite Patent Owner’s
`unsupported suggestion that his declaration must state the
`evidentiary standard used in formulating his opinions (POR §
`II & III)
`
`
`
`
`
`1
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`The POR asserts that the Bloom Declaration (Exhibit 1003) is entitled to
`
`little or no weight based on its observation that the Declaration stated no
`
`evidentiary standard. See POR at 2-3 (citing 37 CFR 42.65). Yet, Patent Owner
`
`bases this contention on its flawed and unsupported interpretation of 37 CFR
`
`42.65, which requires only that a declarant “disclose the underlying facts or data
`
`on which the opinion is based” and, notably, does not require a declarant to
`
`expressly state an evidentiary basis on which the opinion is based. See POR at 2-3
`
`(quoting 37 CFR 42.65) (emphasis added).
`
`That decision was consistent with the Board’s earlier decision in the Vibrant
`
`Media v. General Electric Company case, IPR2013-00172. Specifically, in the
`
`Vibrant Media case, a party argued that 35 U.S.C. § 316(e) requires an expert
`
`declaration to expressly recite or apply the preponderance of the evidence standard
`
`in order for the expert testimony to be accorded weight. See Vibrant Media, Paper
`
`50 at 42. The Board considered and decisively rejected that argument, concluding
`
`that 35 U.S.C. § 316(e) makes no such requirement and finding that “[r]ather, it is
`
`within our discretion to assign the appropriate weight to be accorded to evidence
`
`based on whether the expert testimony discloses the underlying facts or data on
`
`which the opinion is based.” Id. (emphasis added)(citing 37 C.F.R. § 42.64(a)).
`
`42.65 does not undermine the authority rightly noted in the Vibrant Media
`
`
`
`
`
`2
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`decision. It is instead consistent with that authority, setting forth requirements
`
`having nothing to do with citation of an evidentiary standard.
`
`Consistent with the requirements of 37 §§ CFR 42.65, Dr. Bloom’s
`
`testimony disclosed underlying facts and data on which his opinions were based.
`
`For example, Dr. Bloom’s declaration extensively referenced prior art disclosures,
`
`and it also noted Dr. Bloom’s relevant and timely industry experience with digital
`
`right management. See Exhibit 1003 at ¶¶ 5-22, ¶¶ 29-103.
`
`Moreover, by attesting to facts set forth in his declaration, Dr. Bloom has
`
`indicated his belief that those facts are correct, and, therefore, that those facts are
`
`more likely true than not based on evidence known to him. See Exhibit 1003at ¶
`
`138 (“I hereby declare that all statements made herein of my own knowledge are
`
`true and that all statements made on information and belief are believed to be
`
`true”). From this, Dr. Bloom’s statements are self-revealing of his satisfaction of
`
`the preponderance of evidence standard.
`
`Accordingly, Petitioner respectfully submits that Dr. Bloom’s declaration is
`
`worthy of weight.
`
`B. The POR’s allegation of bias of Dr. Bloom is unfounded and
`purely speculative (POR § III)
`
`The POR contends bias by Dr. Bloom based on nothing more than his
`
`employment by SiriusXM Radio, and alleged “similarity between his employer’s
`
`products and the claims of the patent would provide Dr. Bloom with a bias against
`
`
`
`
`
`3
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`the claims.” Id. at 6. This argument is unsustainable, as it is unproven and
`
`illogical.
`
`Substantively, while SiriusXM is Dr. Bloom’s employer, there is no
`
`evidence that Dr. Bloom perceived similarities between his employer’s products
`
`and the claims of the patent prior to his deposition. That is, whether alleged
`
`similarities existed or not, an allegation of bias would require a showing that Dr.
`
`Bloom did indeed perceive such similarities when rendering the opinions offered in
`
`the instant case. The Patent Owner had the opportunity to question Dr. Bloom on
`
`this point during his deposition, yet the record is without such evidence.
`
`Logically, this argument is equally flawed. Without more, Patent Owner
`
`seeks to establish bias based on mere affiliation of an expert with an operating
`
`company. Surely, for an expert to have bias, it is necessary for the expert to have
`
`knowledge of the facts giving rise to the same. Mere employment is not enough,
`
`nor is knowledge of the products offered by one’s employer. It is instead
`
`necessary to perceive infringement for bias to exist, and for such perception to
`
`exist at the time of an opinion’s rendering. On a record that is without a showing
`
`of either, this argument is logically flawed.
`
`Equally flawed is the apparent suggestion by Patent Owner’s counsel that, to
`
`avoid allegations of bias, Petitioner should have used a University professor in
`
`place of Dr. Bloom. See Transcript at 232:5-35. Indeed, applying the POR’s logic
`
`
`
`
`
`4
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`across the breadth of proceedings before the Board and asserting it as a general
`
`basis for discrediting expert opinion would seem to foreclose consideration by the
`
`Board of relevant testimony from experts (like Dr. Bloom) who have professional
`
`experiences that inform opinions on technology to which they directed their
`
`careers. Specifically, Patent Owner would deny the Board access to testimony by
`
`engineers working for companies that develop related technologies since those
`
`technologies might be accused of infringing a patent under review, even if such
`
`engineers are (like Dr. Bloom) without knowledge of such offerings or prospective
`
`infringement. Such an outcome would be absurd, yet it is precisely what Patent
`
`Owner was advocating during Dr. Bloom’s deposition when counsel suggested
`
`that, to avoid allegations of bias, Petitioner should have used a University
`
`professor. See Transcript at 232:5-35.
`
`The Petitioner, moreover, was free at the outset of this proceeding to provide
`
`testimony from a qualified expert of the Petitioner’s choosing, and the selection of
`
`Dr. Bloom reflects confidence that his opinions are objective and technically-
`
`sound. Ultimately, Patent Owner has provided no reason to avoid taking Dr.
`
`Bloom at his word – that he believes his testimony is true and objective, and that
`
`he therefore believes in the positions that he has advanced. See Exhibit 1003 at ¶
`
`138 (“I hereby declare that all statements made herein of my own knowledge are
`
`true and that all statements made on information and belief are believed to be
`
`
`
`
`
`5
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`true”).
`
`III. Claim Construction (POR § IV)
`
`Patent Owner contends “payment data” should be construed to mean “data
`
`that can be used to make payment for content.” POR at 4-5. In particular, Patent
`
`Owner wants “payment data” to be narrowly construed so that “payment data” is
`
`not “data representing payment made for requested content data….” POR at 5-6.
`
`(emphasis added). As demonstrated below, this construction is unduly narrow as
`
`demonstrated by its disregard of even the explicit teachings of the ‘221 Patent
`
`itself.
`
`A. Petitioner’s proposed construction of “payment data” comports
`with ordinary and customary meaning, as imparted by the
`specification of the ‘221 Patent.
`
`In a covered business method patent review, claim terms are given their
`
`broadest reasonable interpretation in light of the specification in which they appear
`
`and the understanding of others skilled in the relevant art. See 37 C.F.R. §
`
`42.300(b); see also In re Cuozzo Speed Techs., LLC, 2015 WL 448667 at *7 (Fed.
`
`Cir. Feb. 4, 2015) (“We conclude that Congress implicitly adopted the broadest
`
`reasonable interpretation standard in enacting the AIA.”); In re Translogic Tech.,
`
`Inc., 504 F.3d 1249, 1257 (Fed. Cir. 2007) (discussing that applying the BRI
`
`standard, claim terms should be construed according to their ordinary and
`
`customary meaning in the context of the patent’s written description).
`
`
`
`
`
`6
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`Petitioner proposed to construe “payment data” to include and be met by
`
`data that relates to previous, present, and/or prospective payment. Petition at 6. In
`
`response, Patent Owner countered that “payment data” should be construed to
`
`mean “data that can be used to make payment for content.” POR at 4-5.
`
`Furthermore, Patent Owner argued that “payment data” should be read to exclude
`
`“data representing payment made for requested content data.” POR at 5-6. Here,
`
`Patent Owner seems to distinguish prospective payments (“can be used to make
`
`payment”) from previous payments (“payment made for”), and it suggests that a
`
`broadest reasonable construction of payment data includes data used for
`
`prospective payments without including data used for previous payments. Such a
`
`construction is simply unsustainable, as revealed through the support provided by
`
`Patent Owner for the same.
`
`Specifically, Patent Owner attempts to justify this position by turning to Fig.
`
`12C of the ‘221 Patent, which it describes as showing payment data being used for
`
`making a payment. POR at 5-6. Notably absent from the Fig. 12C example or
`
`Patent Owner’s characterization of the same – any mention, much less preclusion
`
`of data relating to previously payments.
`
`By contrast, Samsung’s proposed construction comports with the ordinary
`
`and customary meaning as imparted by the specification of the ‘221 Patent, which
`
`specifically teaches that “[t]he payment data received may either be data relating to
`
`
`
`
`
`7
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`an actual payment made to the data supplier, or it may be a record of a payment.”
`
`‘221 Patent 6:60-63 (emphasis added). In this instance, a “record of a payment”
`
`must represent a previous payment. Indeed, the notion of previous payment as a
`
`credit is disclosed in other portions of the specification of the ‘221 Patent, which
`
`purports to use both debit (pre-pay) or credit mode to facilitate download of
`
`content. See ‘221 Patent 22:6-8. By ignoring the express teachings of the ‘221
`
`Patent itself, Patent Owner’s proposed claim construction for “payment data” is
`
`unduly narrow and does not comport with the BRI standard required for a CBM
`
`review.
`
`Moreover, this construction is not supported by even the stated objectives of
`
`the ‘221 Patent, which include provision of a terminal for “reading payment
`
`information from the payment validation means using the terminal; validating the
`
`payment information; and downloading data into the portable storage device from
`
`a data supplier.” ‘221 Patent at 1:64-67.
`
`IV. Claims 2 and 11 are anticipated by Ginter (POR § V)
`
`Patent Owner’s response attempts to show that Ginter does not anticipate
`
`claims 2 and 11 by looking at limitations 1(f) and 1(g) of base claim 1, and by also
`
`looking at claim 2’s recitation of code to transmit payment validation data. In
`
`doing so, Patent Owner mischaracterized the challenged claims and interpreted
`
`
`
`
`
`8
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`Ginter in a manner that is inconsistent with the interpretation afforded to its
`
`teachings by those of skill, as demonstrated by Dr. Bloom.
`
`A. Ginter teaches claim 1, from which claims 2 and 11 depend
`Patent Owner exhorted form over substance by proclaiming that evidence
`
`relied upon by Petitioner – Dr. Bloom’s characterizations of Ginter – are not
`
`supported by citations to Ginter that were provided by Dr. Bloom in his
`
`declaration. Yet Patent Owner didn’t even address all of the citations provided by
`
`Dr. Bloom. Moreover, a careful review of the extensively cited portions of Ginter
`
`reveals that those sections (particularly when read in light of and in conjunction
`
`with the entirety of Ginter’s disclosure) do indeed disclose each of the subject
`
`claim limitations, including “payment validation data” and “responsive to payment
`
`validation data.”
`
`1. Ginter teaches 1(f): code to receive payment validation data from the
`payment validation system
`
`The Petition demonstrated that this element was disclosed in Ginter. As pled
`
`in the Petition, “[t]he payment validation system then replies with payment
`
`validation data resulting from the analysis (in, e.g., an administrative response
`
`object); the payment validation data is received by CPU 654 of electronic
`
`appliance 600.” See Petition at 35-36, citing Ginter at 161:42-162:6 (“The clearing
`
`house may, as a result of the analysis, generate one or more responsive
`
`administrative objects that it then sends to the end user’s appliance 600”), 162:5-6
`
`
`
`
`
`9
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`(“The end user’s electronic appliance 600 may process events that update its secure
`
`database 610 and/or SPU 500 contents based on the administrative object
`
`received”), and 162:38-64.
`
`Patent Owner sought to address this limitation by focusing on Dr. Bloom’s
`
`deposition testimony on the different configurations of administrative objects.
`
`Specifically, and looking past Dr. Bloom’s other testimony, Patent Owner focused
`
`on the following portion of the transcript, inferring that Dr. Bloom relied upon a
`
`portion of Ginter that discloses administrative objects (i.e., administrative objects
`
`returned responsive to budget requests) that do not necessarily include payment
`
`validation data:
`
`Q. Did you base your opinion on the fact that Ginter anticipates … the
`challenged claims of the ‘221 patent based on the fact that payment
`validation data is anything other than an administrative object which
`is communicated back to a user node as part of a budget request?
`
`A. No
`
`Q. So if I told you that Ginter described an administrative object in a
`particular portion of the specification and I didn't tell you what kind of
`administrative object it was, you wouldn't know what was in that
`administrative object, correct?
`
`A. That's true.
`
`See POR at 9, citing Transcript Exhibit 2055 at 21:8-14 and 54:3-10.
`
`10
`
`
`
`
`
`
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`This argument is flawed for at least two reasons1. First, in the context of its
`
`disclosure of a response to a budget request, Ginter provides sufficient disclosure
`
`to meet the claimed receipt of payment validation data limitation. Therefore, even
`
`if (improperly) overlooking the petition’s reference to other portions of Ginter,
`
`such as the cited-to portions of Ginter that do not relate to the budget request
`
`response example, this feature is met. Indeed, as is also suggested by Dr. Bloom,
`
`in the context of a budget request, Ginter teaches administrative response objects
`
`that include audit trails and records. See Petition at 25-27, and 35-36, Exhibit 1003
`
`at¶¶ 38-42, 592, and 80-82, Ginter at Fig. 42c and 176:13-17(“Upon receiving the
`
`
`
`1 However, the declaration unquestionably cited to sections of Ginter that were not
`
`responsive to budget requests, revealing the confusing nature of the double
`
`negative within this question.
`
`2 While cross-examining Dr. Bloom regarding his Declaration (Exhibit 1003), the
`
`Patent Owner never questioned paragraph 59 in which Dr. Bloom had already
`
`opined:
`
`SPU 500 and/or CPU 2616 implement code to receive, via a wireless
`interface, payment validation data defining if the payment validation system
`has validated payment for the selected item(s) of multimedia content. See
`Ginter at 163:38-61; 175:3-22; 176:13-33. In more detail, following receipt
`of forwarded audit information, the payment validation system processes the
`audit information to determine its validity. Ginter at 161:42-162:6, 175:3-22,
`175:47-176:1. The payment validation system then replies with an
`
`
`
`
`
`11
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`administrative object, BUDGET method 2250 at the VDE financial provider site
`
`may prime a budget communications and response audit trail (blocks 2306, 2308),
`
`and may then unpack the administrative object and retrieve the budget request(s),
`
`audit trail(s) and record(s) it contains (block 2310)”), 176: 29-37(“BUDGET
`
`method 2250 may then write these Budget administrative response records into an
`
`administrative object (blocks 2322, 2324), which it may then communicate back to
`
`the user node that initiated the budget request. BUDGET method 2250 may then
`
`save communications and response processing audit trail information into
`
`appropriate audit trail UDE(s) (blocks 2326,2328) before terminating (at
`
`termination point 2330.”).
`
`Second, irrespective of whether Bloom’s testimony was limited to Ginter’s
`
`budget request response example or not, the petition did not similarly narrow its
`
`focus within Ginter. Therefore, even if Bloom’s testimony was discounted, which
`
`it should not be (see immediately preceding paragraphs), POR’s argument fails to
`
`address the petition’s mapping of Ginter to this claim element for the reasons set
`
`
`
`administrative response object containing payment validation data resulting
`from the analysis, which is received by PEA 2600. Ginter at 161:42-162:6,
`162:5-6, 162:38-64.
`Exhibit 1003 at ¶ 59.
`
`
`
`
`
`
`
`12
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`forth above. That is, the petition cites to various sections of Ginter that are distinct
`
`and otherwise go beyond disclosure of Ginter’s budget request response example.
`
`See, e.g., Petition at 25-27, citing Ginter at 38-42. And, the Petition additionally
`
`references Ginter generally, making clear its position that Ginter’s extensive
`
`disclosure of budget information was relied upon, including, e.g., disclosures made
`
`by Figs. 35 and 44b. See, e.g., Petition at 17 (reproduced below):
`
`
`
`In this manner, Ginter further expands to describe the generation of an
`
`administrative response object, such as its illustration of processing that is applied
`
`to administrative objects. See Ginter Fig. 35 at blocks 1158 and 1160 showing an
`
`administrative response object being sent from a clearing house (block 1160) after
`
`appliance has sent administrative objects containing audit information to the
`
`
`
`
`
`13
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`clearing house (block 1158); see also Ginter Fig. 44b that shows an example of a
`
`clearinghouse that processes an incoming administrative object containing audit
`
`info, and that writes AUDIT administrative response records into administrative
`
`Object (block 2566). Through these and various other sections, Ginter generally
`
`and specifically discloses administrative objects that include payment validation
`
`data, e.g., AUDIT records, and receipt of the same, consistent with 1(f). See POR
`
`at 9 (citing Transcript Exhibit 2055 at 21:8-14 and 54:3-10).
`
`2. Ginter teaches 1(g): code responsive to payment validation data to
`retrieve data from the data supplier and to write the retrieved data into
`the data carrier.
`
`According to Patent Owner, Petitioner failed to demonstrate that Ginter
`
`teaches the particular limitation of “responsive to payment validation data.”
`
`However, in setting forth this argument, Patent Owner relies upon a deposition
`
`transcript that improperly sought to have Dr. Bloom read various sections of Ginter
`
`out of context, as if divorced from the full disclosure of Ginter. Read properly,
`
`however, consistent with citation of those sections within the complete teaching of
`
`Ginter, the subject and other cited sections of, Ginter does indeed disclose
`
`limitation 1(g), and its recitation of “responsive to payment validation data.”
`
`Initially, in the deposition and its POR, Patent Owner did not even account
`
`for the full complement of Dr. Bloom’s extensive citations to Ginter, and instead
`
`focused on a subset of such citations to Ginter. See, e.g., Petition at 36-38, Exhibit
`
`
`
`
`
`14
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`1003 at ¶82 (citing Ginter at 289:41-290:23) and ¶ 83 (citing Ginter at 41:7-124).
`
`As a result, even if Patent Owner’s argument were accepted, the failure of Patent
`
`Owner’s cross examination and argument to account for the full testimony of Dr.
`
`Bloom renders that argument moot. That is, even if Patent Owner were correct in
`
`reading cross-examined sections of Ginter out of context, which it is not, Patent
`
`Owner failed to address Dr. Bloom’s citation to other sections of Ginter that were
`
`said by Dr. Bloom to teach this feature.
`
`Moreover, as pled in the Petition at 36-39 and in addition to Dr. Bloom’s
`
`declaration, Petitioner cited a variety of sections from Ginter that collectively teach
`
`“responsive to payment validation data.” For example, page 37 of the Petition
`
`cited to Ginter at 41:7-12, which recites:
`
`
`
`3 While cross-examining Dr. Bloom regarding whether Ginter teaches claim 1(g),
`
`Patent Owner failed to address Dr. Bloom’s citation to Ginter 289:41-67. See POR
`
`at 23 (challenging 289:67-290:2 only).
`
`4 Interestingly, Patent Owner never cross-examined Dr. Bloom regarding whether
`
`Ginter 41:7-12, in connection with other cited portions to Ginter, teaches claim
`
`1(g). See POR at 11, 14, and 27 (dismissing Ginter 41:7-12 without evidence from
`
`deposition).
`
`
`
`
`
`15
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`“[a PEA and connected electronic appliance] can securely exchange
`information related to a transaction, with . . . transaction information
`flowing back to the card.”
`
`This passage provides the context for the exchange of information related to
`
`transactions, such as data retrieval in response to payment validation data. Exhibit
`
`1003 at ¶ 60. As set forth in Petition at 17, Ginter describes secure transaction
`
`management and electronic rights protection achieved through a virtue distribution
`
`environment (“VDE”) that controls, using payment and other information, access
`
`to electronically disseminated and stored content objects. In this context, Ginter
`
`289:41-67, as pled in the Petition at 36-38, provides further details on data retrieval
`
`(“If the transaction is authorized . . . the container packager takes this package of
`
`control information and the content and forms an appropriate container . . . the
`
`container is transmitted across the network to the end user.”) (emphasis added).
`
`Here, the condition that the transaction is “authorized” means that the transaction,
`
`for example, retrieving a container object that includes content and access rules, is
`
`premised on a proof of the request being valid and legitimate. See Petition at 25-
`
`27 (describing framework of access rules). Such requirement has been amplified
`
`through other cited passages of Ginter, also as pled. See Petition at 36-38 citing
`
`Ginter 161: 42-162:6 (“The clearinghouse may receive the administrative object
`
`and process its contents to determine whether the contents are ‘valid’ and
`
`‘legitimate.’ E.g., the clearinghouse may analyze the contained audit information
`
`
`
`
`
`16
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`to determine whether it indicates misuse of the applicable VDE object 300.) As
`
`pled, the proof of “valid” and “legitimate” can be encoded as control information
`
`and by an administrative object. See Petition at 17-27 citing Ginter at Fig. 5B ann.
`
`(c) (quoted below).
`
`As set forth in the Petition at 36-38, the collection of cited portions from
`
`Ginter do teach that data retrieval is performed after exchange of information
`
`
`
`
`
`
`
`17
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`related to the data retrieval transaction, for example, in response to a coded
`
`administrative object.
`
`Similarly, as pled in the Petition at 36-38, Ginter offers ample teachings on
`
`data storage in the context of retrieved data. “Portable appliance 2600 may, in one
`
`embodiment, comprise means to perform substantially all of the functions of a
`
`VDE electronic appliance 600. Thus, e.g., portable appliance 2600 may include the
`
`means for storing . . . information.” Ginter at 229:18-34 (cited in Petition at 36-38).
`
`Ginter also discloses that “[s]tored in each electronic appliance secondary memory
`
`652 may be, e.g., . . . objects 300 containing VDE controlled property content and
`
`related information.” Ginter at 65:61-67 (cited in Petition at 36-38). Moreover,
`
`“[r]emovable/replaceable memory 2622 may comprise a memory cartridge or
`
`memory medium such as a bulk storage device, for providing additional long-term
`
`or short-term storage.” Ginter at 230:15-19 (cited in Petition at 36-38). These
`
`storage examples, along with the above discussion of data retrieval responsive to
`
`payment validation data, demonstrate that Ginter teaches storing the retrieved data
`
`at the data carrier such that end user is allowed to use and access downloaded
`
`media data, as pled in the Petition at 36-38.
`
`The Petitioner set forth an anticipation challenge based on a collection of
`
`teachings from Ginter that include 41:1-27, which when read together with other
`
`sections of Ginter, teach the purported limitation. In response, Patent Owner
`
`
`
`
`
`18
`
`

`
`Case CBM2014-00199
`Attorney Docket No: 39843-0007CP2
`
`attempted to discredit the collection by cross-examining Dr. Bloom in a piece-meal
`
`manner without any consideration of the collective teachings. In particular, the
`
`response attempted to show that Dr. Bloom conceded that each cited section from
`
`Ginter, viewed on its own and divorced from the collective teaching of Ginter as a
`
`whole, lacks the teaching for the entire claim limitation. Yet, Patent Owner failed
`
`to cross examine Dr. Bloom on all citations to Ginter (e.g. Ginter 41:7-12) that Dr.
`
`Bloom relied upon for this limitation of “responsive to payment validation data to
`
`retrieve data from the data supplier and to write the retrieved data into the data
`
`carrier.” POR at 14 (dismissing Ginter 41:7-12 without

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