throbber
Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Petitioner: Apple Inc.
`
`Attorney Docket No.:
`
` 104677-5008-811
`Customer No. 28120
`

`Inventor: Racz et al.
`United States Patent No.: 7,942,317 §
`Formerly Application No.: 12/014,558 §
`Issue Date: May 17, 2011

`Filing Date: January 15, 2008

`Former Group Art Unit: 2887

`Former Examiner: Thien M. Le

`
`For: Data Storage and Access Systems
`
`MAIL STOP PATENT BOARD
`Patent Trial and Appeal Board
`United States Patent and Trademark Office
`Post Office Box 1450
`Alexandria, Virginia 22313-1450
`
`PETITION FOR COVERED BUSINESS METHOD PATENT REVIEW OF
`UNITED STATES PATENT NO. 7,942,317 PURSUANT TO 35 U.S.C. § 321,
`37 C.F.R. § 42.304
`
`
`
`
`
`

`

`
`
` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`
`TABLE OF CONTENTS
`
`B. 
`
`INTRODUCTION ....................................................................................................... 1 
`I. 
`II.  OVERVIEW OF FIELD OF THE CLAIMED INVENTION ......................... 4 
`III.  PETITIONER HAS STANDING ............................................................................ 7 
`A. 
`The ’317 Patent Is a Covered Business Method (“CBM”) Patent ............. 7 
`1. 
`Exemplary Claim 18 Is Financial In Nature ...................................... 8 
`2. 
`Claim 18 Does Not Cover A Technological Invention ................. 11 
`Related Matters; Petitioner Is a Real Party In Interest Sued for and
`Charged With Infringement ........................................................................... 15 
`IV.  DETAILED EXPLANATION OF REASONS FOR RELIEF REQUESTED,
`SHOWING IT IS MORE LIKELY THAN NOT THAT AT LEAST ONE
`CHALLENGED CLAIM IS UNPATENTABLE ............................................... 16 
`A. 
`Claim Construction .......................................................................................... 16 
`B. 
`The Challenged Claims Are Invalid Under §§ 102 and/or 103 ................ 20 
`1. 
`Overview of Stefik ............................................................................... 20 
`2. 
`Motivation to Combine Stefik with Poggio ..................................... 25 
`3. 
`Claims 1, 6-8, 12-14, 16, and 18 are Anticipated by Stefik
`(Ground 1), Obvious in Light of Stefik (Ground 2), and
`Obvious in Light of Stefik in View of Poggio (Ground 3). .......... 28 
`CONCLUSION........................................................................................................... 77 
`
`V. 
`
`
`ii
`
`

`

`
`EXHIBIT LIST
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`1013
`
`1014
`
`1015
`
`1016
`
`1017
`
`1018
`
`1019
`
`1020
`
` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`
`U.S. Patent No. 7,942,317
`
`Plaintiff’s First Amended Complaint
`
`U.S. Patent No. 8,118,221
`
`File History for U.S. Patent No. 8,118,221
`
`File History for U.S. Patent No. 8,336,772
`
`U.S. Patent No. 4,999,806
`
`U.S. Patent No. 5,675,734
`
`U.S. Patent No. 4,878,245
`
`U.S. Patent No. 5,754,654
`
`File History for U.S. Patent No. 7,942,317
`
`Declaration of Flora D. Elias-Mique In Support of Apple
`Inc.’s Petition for Covered Business Method Patent Review
`U.S. Patent No. 5,103,392
`
`U.S. Patent No. 5,530,235
`
`U.S. Patent No. 5,629,980
`
`U.S. Patent No. 5,915,019
`
`European Patent Application, Publication No. EP0809221A2
`
`PCT Application Publication No. WO 99/43136
`
`JP Patent Application Publication No. H11-164058 (transla-
`tion)
`JP Patent Application Publication No. H10-269289 (transla-
`tion)
`Eberhard von Faber, Robert Hammelrath, and Franz-Peter
`
`iii
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`
`Heider, “The Secure Distribution of Digital Contents,” IEEE
`(1997)
`Declaration of Anthony J. Wechselberger In Support of Apple
`Inc.’s Petition for Covered Business Method Patent Review
`Declaration of Michael P. Duffey In Support of Apple Inc.’s
`Petition for Covered Business Method Patent Review
`U.S. Patent No. 7,334,720
`
`U.S. Patent No. 8,033,458
`
`U.S. Patent No. 8,061,598
`
`U.S. Patent No. 8,336,772
`
`File History for U.S. Patent No. 7,334,720
`
`File History for U.S. Patent No. 8,033,458
`
`File History for U.S. Patent No. 8,061,598
`
`EXHIBIT LIST
`
`1021
`
`1022
`
`1023
`
`1024
`
`1025
`
`1026
`
`1027
`
`1028
`
`1029
`
`iv
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`I.
`
`INTRODUCTION
`
`Pursuant to 35 U.S.C. § 321 and 37 C.F.R. § 42.304, the undersigned, on behalf
`
`of and acting in a representative capacity for Apple Inc. (“Petitioner” and the real par-
`
`ty in interest), petitions for review under the transitional program for covered busi-
`
`ness method patents of claims 1, 6, 7, 8, 12-14, 16, and 18 (challenged claims) of U.S.
`
`Pat. No. 7,942,317 (“the ’317 patent”), issued to Smartflash Technologies Limited and
`
`assigned to Smartflash LLC (“Patentee”). Petitioner hereby asserts that it is more like-
`
`ly than not that at least one of the challenged claims is unpatentable for the reasons
`
`herein and requests review of, and judgment against, the challenged claims as invalid
`
`under 35 U.S.C. §§ 102 and 103.1 Petitioner has concurrently filed a Petition seeking
`
`CBM review of the ’317 patent, requesting judgment against these same claims under
`
`based on different prior art. The Director, pursuant to Rule 325(c), may determine
`
`that merger, or at minimum coordination of these proceedings, is appropriate.
`
`The challenged claims merely recite steps and corresponding basic computer
`
`systems well-known in the field of data storage and access, including methods of
`
`“providing data to a data requester, a “computer system for providing data to a data
`
`requester,” and a “data access system.” E.g., Ex. 1001 at claims 1, 8, 16, 18; 1:18-21;
`
`Abstract “Data storage and access systems are described for downloading and paying
`
`
`1 Petitioner is demonstrating, in pending litigation, that these claims are invalid for
`
`numerous additional reasons. All emphasis herein added unless otherwise noted.
`
`
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`for data . . .”). Claim 18, for example, recites five rudimentary steps relating to data
`
`storage and access—(A) receiving a request for data, (B) receiving payment data
`
`relating to the data, (C) transmitting requested data, (D) reading payment distribu-
`
`tion information, and (E) outputting payment data for distributing the requested data:
`
`18. A method of providing data to a data requester comprising:
`receiving a request for a data item from the requester;
`receiving payment data from the requester relating to payment for
`
`the requested data;
`transmitting the requested data to the requestor;
`reading payment distribution information from a data store; and
`outputting payment data to a payment system for distributing the
`payment for the requested data
`Ex. 1001. But at the patent’s earliest claimed priority date, these simple elements and
`
`their combination were well known to any person of ordinary skill (“POSITA”2). In-
`
`deed, the patent acknowledges that the idea of providing access to data in exchange
`
`for a payment (e.g., purchase of music on a CD) was already well known. E.g., Ex.
`
`1001 5:4-7 (“the purchase outright option may be equivalent to the purchase of a compact
`
`2 All references to a POSITA refer to the knowledge or understanding of a person of
`
`ordinary skill in the art as of October 25, 1999, unless specifically noted. A POSITA
`
`would have at least a B.S. in E.E., computer science or a telecommunications related
`
`field, and at least three years of industry experience that included client-server
`
`data/information distribution and management architectures. See Ex. 1021 ¶ 28.
`
`2
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`disc (CD)”). And, as demonstrated herein, the prior art was teeming with disclosures of
`
`this basic concept and its straightforward implementation in physical systems.
`
`Moreover, claim 18 clearly involves no “technology” at all other than, at most, a
`
`“data requester,” which is merely an entity that may make a data request, and a “pay-
`
`ment system” and “data store,” which were commonplace and do not require any par-
`
`ticularized hardware. E.g., Ex. 1001 4:27-42; 6:38-40; 7:52-53; 9:62; 10:16, 25, 36, 44;
`
`12:29-32; 13:35-47; 14:25-29; 19:43-44; Figs. 6, 12(d), (e). Thus, as the intrinsic record
`
`reflects, Claim 18 recites no more than a method for receiving a request for and
`
`transmitting data while receiving and outputting payment data. Independent claims 1,
`
`8, and 16 are nothing but variations on this same simple theme, with the addition, in
`
`the challenged “system” claims, of equally generic components (such as a communica-
`
`tion interface, program store, and processor).3 See, e.g., Ex. 1001 12:29-32 (“The phys-
`
`ical embodiment of the system is not critical and a skilled person will understand that
`
`the terminals, data processing systems and the like can all take a variety of forms.”).
`
`It is thus no surprise that each element of the challenged claims was disclosed
`
`3 Method claim 8 does not even recite a “data requester,” “payment system,” or “data
`
`store.” Dependent claims 6 and 7 only add to the system of claim 1 a data store and
`
`code, respectively. Claim 12 is directed to a “data access system,” and recites a gener-
`
`ic “data supply computer system,” “electronic payment system,” “data access termi-
`
`nal,” and “data carrier,” all of which were well-known, as discussed infra in II, IV.B.
`
`3
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`in the prior art, either by individual references or by those references in combination,
`
`and each challenged claim is accordingly invalid under 35 U.S.C. §§ 102 and 103.
`
`II. OVERVIEW OF FIELD OF THE CLAIMED INVENTION
`By October 25, 1999, electronic sale, distribution, and content protection for
`
`digital products all would have been well-known to a POSITA, and their combination
`
`as claimed also would have been well-known or at minimum obvious. See, e.g., Ex.
`
`1021 § V. On March 12, 1991, for example, U.S. Pat. No. 4,999,806 (“Chernow,” filed
`
`Sept. 4, 1987) issued, disclosing a system and method for sale and distribution of digi-
`
`tal products by phone, and for content protection. See, e.g., Ex. 1006 Abstract (“central
`
`station distributes software by telephone. . . accepts credit card information, transmits an acceptance
`
`code . . . After verifying the credit card information, the station calls the purchaser back and contin-
`
`ues with the transaction only after receiving the acceptance code.”); 1:67-2:9 (describing “means
`
`for selling and distributing protected software using standard telephone lines,” “permit[ting] the pur-
`
`chaser to rent the protected software for a period of time,” and “to rent the protected software for a
`
`specific number of runs”). Chernow also discloses (1) different types of access, such as
`
`purchase vs. rental and (2) a Control Transfer Program and a Primary Protection Pro-
`
`gram to prevent unauthorized copies. See Ex. 1006 Abstract; 2:65-3:23; Ex. 1021 ¶ 33.
`
`In April 1992, U.S. Patent No. 5,103,392 (“Mori,” filed Dec. 5, 1990) issued,
`
`disclosing use-based charging for digital products. See, e.g., id. Ex. 1012 1:64-2:17:
`
`The data processing apparatus includes user-specific credit data storage
`means for storing data identifying the user . . . and indicating credit for payment ca-
`
`4
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`
`pacity, use time length, or the like of the user . . .. Also included is use deci-
`sion means for determining permission to use the program . . . on the basis of pro-
`gram-specific data supplied from the program storage means or user-specific
`credit data supplied from the user-specific credit data storage means, the
`use decision means delivering either an affirmative or negative signal corresponding
`to results of the decision. Also included is program use history storage means
`connected to the use decision means for storing program use history data . . ..
`Mori’s emphasis on assuring permission to access a program and compensating pro-
`
`viders underscores this existing focus in the art on digital rights management
`
`(“DRM”), over eight years before the claimed priority date. See, e,g., Ex. 1021 ¶ 36.
`
`Exhibit 1016 (“Poggio”, pub’d Nov. 26, 1997) gives another example of secure
`
`content distribution with content protection, disclosing a “virtual vending machine”
`
`system for sale and distribution of digital products. See, e.g., id. Abstract (“virtual vending
`
`machine manages a comprehensive vending service for the distribution of licensed electronic data (i.e.,
`
`products) over a distributed computer system. . . . [and] distributes licenses for the electronic data for
`
`the complete product or for components thereof and for a variety of time frames, including permanent
`
`licenses and rental period licenses. [It] provides . . . capability to obtain information regarding the
`
`available products and the associated license fees and rental periods, to receive the product upon re-
`
`ceipt of a corresponding electronic payment, and to reload the product during the term of the license.”).
`
`Poggio, too, discloses different types of access, including rentals, and re-download ca-
`
`pabilities for already-purchased content. See, e.g., id.; Ex. 1021 ¶¶ 37, 48.
`
`Also in 1997, Exhibit 1020 (“von Faber”) published, making the well-known
`
`5
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`observation that “[e]lectronic commerce systems dealing with the distribution of digital con-
`
`tents . . . have to couple the use of the provided digital goods with a prior payment for the goods in a
`
`way which cannot be bypassed.” See id. 7. Von Faber proposed a system where cus-
`
`tomers purchase keys required to utilize encrypted content. See, e.g., id. (“The basic
`
`idea . . . is to distribute the contents in encrypted form, and to have the customer pay for the key
`
`which he needs to transform the encrypted content in an usable form.”); id. 8 (“The Content Pro-
`
`vider provides digital contents in encrypted form being distributed by the Content Distribu-
`
`tor. . . . The Authorisation System permits the distribution of the appropriate key after settling
`
`of the fees payable by the Customer . . .. The role of the Content Distributor is not essential
`
`for the subsequent discussion but, of course, for the business to take place.”); see also id. Fig.
`
`1. Von Faber notes its system could be used for a variety of known distribution and
`
`payment methods. See, e.g., id. 13 (“Different methods can be used to distribute the encrypted
`
`contents (standard techniques). . . . Different electronic payment methods can be integrated . . . .
`
`This flexibility leads to the fact that totally different authorisation methods can be integrated.”).
`
`Von Faber further addressed the known issue of payment distribution to providers.
`
`See, e.g., id. (“The system automatically divides the package price (payments) and guarantees that
`
`the money is transferred to each Content Provider.”); Ex. 1021 ¶¶ 38-40.
`
`Moreover, on June 22, 1999, U.S. Pat. No. 5,915,019 (“Ginter,” filed Jan. 8,
`
`1997) issued, disclosing “systems and methods for secure transaction management
`
`and electronic rights protection.” See, e.g., Ex. 1015 Abstract. Ginter describes a “vir-
`
`6
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`tual distribution environment” (“VDE”) to “control and/or meter or otherwise moni-
`
`tor use of electronically stored or disseminated information.” Id. Ginter’s system
`
`“help[s] to ensure that information is accessed and used only in authorized ways, and main-
`
`tain the integrity, availability, and/or confidentiality of the information.” See, e.g., id. Further,
`
`Ginter’s “techniques may be used to support an all-electronic information distribution, for
`
`example, utilizing the ‘electronic highway.’” Id. Ginter discloses that the various entities of
`
`the VDE can flexibly take on any VDE roles. See, e.g., id. 255:22-23 (“All participants
`
`of VDE 100 have the innate ability to participate in any role.”); 255:23-43. Ginter thus
`
`highlights the known flexibility in such distribution systems, underscoring that a
`
`POSITA would have known that combinations between and among disclosures of
`
`such distribution systems would have been obvious. See, e.g., Ex. 1021 ¶¶ 41-42.
`
`Thus, as these background examples and the additional prior art detailed below
`
`in IV.B (including the primary prior art Stefik patent) illustrate, the prior art was rife
`
`with awareness and discussion of the same supposed “invention” now memorialized
`
`in the challenged claims. Long before the purported priority date, disclosures abound-
`
`ed of the very features that Smartflash now seeks to claim as its exclusive property. As
`
`outlined below, the challenged claims are anticipated and/or obvious.
`
`III. PETITIONER HAS STANDING
`A.
`Petitioner certifies that the ’317 patent is available for review under 37 C.F.R. §
`
`The ’317 Patent Is a Covered Business Method (“CBM”) Patent
`
`7
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`42.304(a). The ’317 patent is a CBM patent under § 18(d)(1) of the Leahy-Smith
`
`America Invents Act, Pub. L. 112-29 (“AIA”) and § 42.301. Although in fact numer-
`
`ous claims qualify, a patent with even one claim covering a CBM is considered a CBM
`
`patent. See CBM 2012-00001, Doc. 36 at 26; 77 Fed. Reg. 48,709 (Aug. 14, 2012). Ac-
`
`cordingly, Petitioner addresses here exemplary claim 18:4
`
`18. A method of providing data to a data requester comprising:
`receiving a request for a data item from the requester;
`receiving payment data from the requester relating to payment for
`
`the requested data;
`transmitting the requested data to the requestor;
`reading payment distribution information from a data store; and
`outputting payment data to a payment system for distributing the
`payment for the requested data.
`1.
`Exemplary Claim 18 Is Financial In Nature
`A CBM patent is “a patent that claims a method or corresponding apparatus
`
`for performing data processing or other operations used in the practice, administra-
`
`tion, or management of a financial product or service, except that the term does not
`
`4 See also, e.g., Ex. 1001, claim 8 (“8. A method of providing data to a data requester
`
`comprising: receiving a request for a data item from the requester; receiving payment
`
`data from the requester relating to payment for the requested data; reading the re-
`
`quested data from a content provider responsive to the received payment data; and
`
`transmitting the read data to the requester.”); claims 12, 16.
`
`8
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`include patents for technological inventions.” AIA § 18(d)(1); 37 C.F.R. § 42.301.
`
`“[T]he definition of covered business method patent was drafted to encompass pa-
`
`tents claiming activities that are financial in nature, incidental to a financial activity or comple-
`
`mentary to a financial activity.’” 77 Fed. Reg. 48,734-35 (Aug. 13, 2012) (citing 157 Cong.
`
`Rec. S5432 (daily ed. Sept. 8, 2011) (stm’t Sen. Schumer)). “[F]inancial product or ser-
`
`vice” is to be interpreted broadly, id., and “financial . . . simply means relating to monetary
`
`matters”—it does not require any link to traditional financial industries such as banks.
`
`See, e.g., CBM2012-00001, Paper 36 at 23.
`
`This Board previously found, e.g., that a claim for “transferring money electron-
`
`ically via a telecommunication line to the first party . . . from the second party” met
`
`the financial product or service requirement, concluding that “the electronic transfer of
`
`money is a financial activity, and allowing such a transfer amounts to providing a financial service.”5
`
`CBM2013-00020, Paper 14 at 11-12. See also, e.g., CBM2013-00017, Paper 8 at 5-6
`
`5 Indeed, these aspects of claim 18 are generally similar to those of the claim found to
`
`convey covered business method standing in CBM2013-00020, which recited: “A
`
`method for transmitting a desired digital audio signal stored on a first memory of a
`
`first party to a second memory of a second party comprising the steps of: transferring
`
`money electronically . . . connecting electronically via a telecommunications line . . .
`
`transmitting the desired signal . . . and storing the digital signal.” See CBM2013-00020,
`
`paper 14 at 10-17.
`
`9
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`(qualification as CBM patent based on specification’s reference to e-commerce and
`
`fact that a POSITA “would have understood that [one of the claim limitations] may be associated
`
`with financial services”).
`
`As discussed above, the ’317 patent relates to the idea of providing electronic
`
`data in exchange for payment. See AIA § 18(d)(1); 37 C.F.R. § 42.301(a); Ex. 10012:12-
`
`15. Indeed, in seeking to enforce the ’317 patent in litigation, Smartflash itself conced-
`
`ed that the alleged invention relates to a financial activity or transaction, stating that
`
`“[t]he patents-in-suit generally cover a portable data carrier for storing data and man-
`
`aging access to the data via payment information and/or use status rules. The patents-in-
`
`suit also generally cover a computer network . . . that serves data and manages access
`
`to data by, for example, validating payment information.” Ex. 1002 ¶ 17.
`
`The ‘317 patent generally describes the invention as follows (Ex. 1001 1:55-63):
`
`According to the present invention there is therefore provided a method
`of providing portable data comprising providing a portable data storage
`device comprising downloaded data storage means and payment vali-
`dation means; providing a terminal for internet access; coupling the
`portable data storage device to the terminal; reading payment infor-
`mation from the payment validation means using the terminal; validat-
`ing the payment information; and downloading data into the portable
`storage device from a data supplier.”
`More specifically, claim 18 is directed to a method of providing data to a data
`
`
`
`requester in response to receiving payment data. Figures 12d and 12e describe various steps
`
`10
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`in this process, including: (a) receiving a request for a data item (S63), (b) receiving
`
`payment data from the requestor (S66), (c) reading content from the content provider
`
`(S73), (d) transmitting the content to the terminal (S73). Ex. 1001. In addition, Figs.
`
`12d and 12e show that providing data to a data requester may involve (e) transmitting
`
`access rules to the requester (S71), (f) reading payment distribution data (S68), and (g) dis-
`
`tributing payments according to distribution data (S69). Id. The specification describes
`
`that “[p]ayment for the data item or items requested may either be made directly to the system owner
`
`or may be made to an e-payment system.” Id.20:50-54. “E-payment systems [] are coupled to
`
`banks” and may be provided in accordance with cash compliant standards such as
`
`MONDEX, Proton, and/or Visa. Id.13:35-46. Thus because claim 18 explicitly de-
`
`scribes receiving and responding to payment data, as well as outputting payment data, it clearly
`
`relates to a financial activity and providing a financial service. See CBM2013-00020,
`
`Institution Decision at 9-10 (“the electronic transfer of money is a financial activity,
`
`and allowing such a transfer amounts to providing a financial service.”). See also AIA
`
`§ 18(d)(1); 37 C.F.R. § 42.301(a). See also 77 Fed. Reg. at 48,735.
`
`2.
`Further, claim 18 does not cover a “technological invention” within the excep-
`
`Claim 18 Does Not Cover A Technological Invention
`
`tion in AIA § 18(d)(1), because it does not claim “subject matter as a whole [that] re-
`
`cites a technological feature that is novel and unobvious over the prior art[] and solves a
`
`technical problem using a technical solution.” § 42.301(b). To the contrary, the specifica-
`
`11
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`tion that claim 18 does not require any specific hardware at all. The “data requester” is not
`
`any particular hardware according to the patent, and may even be an individual who
`
`requests data. The claimed “data store” and “payment systems” were commonplace
`
`and could be implemented using well-known industry standards.
`
`(a) Claim 18 Does Not Recite A Technological Feature
`That Is Novel and Unobvious
`
`First, no “technological feature” of claim 18 is novel and unobvious. The
`
`PTAB has confirmed that “[m]ere recitation of known technologies, such as comput-
`
`er hardware, communication or computer networks, software, memory, computer-
`
`readable storage medium, scanners, display devices or databases, or specialized ma-
`
`chines, such as an ATM or point of sale device,” or “[r]eciting the use of known prior
`
`art technology to accomplish a process or method, even if that process or method is
`
`novel and non-obvious” will “not typically render a patent a technological invention.”
`
`See, e.g., 77 Fed. Reg. 48,764 (Aug. 14, 2012).
`
`As its language makes clear, claim 18 requires no particularized hardware: in-
`
`stead, it simply describes the idea of providing electronic data in exchange for pay-
`
`ment. The claim involves no “technology” at all other than, at most, the use of a data
`
`store and payment system. Ex. 1001. The “data requestor” of claim 8 is not described
`
`as hardware, let alone any particular type of hardware. The data requester is simply de-
`
`scribed as an entity that may make a data request and to which data is provided. Ex.
`
`10016:38-40; 7:52-53; 9:62; 10:16, 25, 36, 44; 12:29-32. The patent also confirms that
`
`12
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`the “data store” is not any particularized hardware, but rather generic memory. See id.
`
`14:25-29; Fig 6 (136 (payment record data store)); 14:43-44. See also, e.g., Ex.
`
`100112:29-32 (“The physical embodiment of the system is not critical and a skilled
`
`person will understand that the terminals, data processing systems and the like can all
`
`take a variety of forms.”). Further, receiving, reading, and outputting payment data
`
`was known because e-payment systems were known, as were payment systems. See Ex.
`
`100113:35-47. The patent explains that “[e]-payment systems are coupled to banks . . .
`
`these provide an e-payment system according to, for example, MONDEX, Proton, and/or Visa
`
`cash compliant standards . . . payment data may be validated [by] a data access terminal using pay-
`
`ment management code.” Id.13:35-47. The specification makes clear that no particular pay-
`
`ment system is required. See, e.g., Fig. 6 (121a and 121b); 19:43-44; 4:27-42; 12:29-32.
`
`Finally, the mere idea of providing access to data in exchange for a payment, as
`
`claimed in the ’317 patent, was known. See, e.g., Ex. 10015:4-7 (“Thus where the data
`
`carrier stores, for example, music, the purchase outright option may be equivalent to the
`
`purchase of a compact disc (CD), preferably with some form of content copy protection
`
`such as digital watermarking.”). See also, e.g., 5,675,734 (Hair) (Ex. 1007); U.S. Patent
`
`No. 4,999,806 (Chernow) (Ex. 1006) Abstract, 1:67-2:9; U.S. Patent No. 4,878,245
`
`(Bradley) (Ex. 1008) Abstract, 4:27-35; Ex. 1021 § V. The alleged invention of the
`
`‘317 patent merely combines a known payment system with the known ability to
`
`download data. But “combining prior art structures to achieve a normal, expected, or
`
`13
`
`

`

`predictable result of that combination” does not render a patent a technological in-
`
` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`
`vention.” 77 Fed. Reg. 157 (Aug. 14, 2012) at 48764.
`
`In sum, the supposed invention of the ’317 patent concerns nothing more than
`
`a non-technical idea of selling data in exchange for payment over the internet. Even
`
`apart from its other failures to trigger the statutory exception, for these reasons alone,
`
`claim 18 would not be a technological invention.
`
`(b) Claim 8 Does Not Solve A Technical Problem Using A
`Technical Solution
`
`Moreover, claim 18 also does not solve a technical problem using a technical
`
`solution because there was no technical problem to begin with. While a POSITA certainly
`
`already would have known how to sell data over the Internet, see, e.g., Ex. 1016 Fig. 7;
`
`1:50-55, 10:41-53; Ex. 1021 § V, the patent nonetheless describes the “problem” it is
`
`intended to solve as the business problem of data piracy: users were downloading online
`
`content (such as MP3s) without paying for the content, and content providers were
`
`losing money as a result. Ex. 1001 1:38-51. However, a POSITA knew well before
`
`2000 how to sell electronic data and how to use payment authorization mechanisms,
`
`and how to provide electronic data based on payment. See, e,g., Ex. 1021 § V. The so-
`
`lution described in claim 18—combining previously-known data access and previous-
`
`ly-known data payment abilities—was also not “technical.” As the patent states,
`
`“[b]inding the data access and payment together allows the legitimate owners of the data to
`
`make the data available themselves over the internet without fear or loss of revenue, thus
`
`14
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`undermining the position of data pirates.” Ex. 1001 2:7-11; see also id. 4:27-29. But the basic
`
`notion of coupling of data access to payment, as claimed in the ’317 patent, is not a
`
`“technical” solution under § 42.301(b).6
`
`Further, even if the solution were somehow deemed “technical” (it is not), it
`
`would not alter that there was no technical problem presented and addressed by the pa-
`
`tent. As the PTAB stated in CBM 2012-00007, “[d]ifficulty implementing an automat-
`
`ed or technical solution to a problem that is not technical does not transform that
`
`non-technical problem into a technical one.” Paper 16 at 17.
`
`In sum, the “invention” of claim 18 concerns no more than the non-technical
`
`idea of restricting access to content based on payment to solve the business problem
`
`of data piracy. For this reason, too, claim 18 does not claim a technological invention.
`
`B. Related Matters; Petitioner Is a Real Party In Interest Sued For
`and Charged With Infringement
`
`Smartflash’s Case No. 6:13-cv-447, Smartflash LLC. et al. v. Apple Inc. et al.,
`
`pending in E.D. Texas, asserts the ’317 patent against Petitioner. Pursuant to Rule
`
`42.8(b)(2), the patent is also the subject of a second litigation, Smartflash LLC et al. v.
`
`Samsung et al., No.6:13-cv-448 (E.D. Tex), to which Apple is not a party. Petitioner
`
`identifies the following administrative matters, including patents to which the ‘317 pa-
`
`
`6 Moreover , the idea of providing access to data in exchange for a payment was itself
`
`known. See, e.g., Ex. 1007; Ex. 1006 Abstract, 1:67-2:9; Ex. 1008 Abstract, col. 4:27-35.
`
`15
`
`

`

` Covered Business Method Patent Review
`United States Patent No. 7,942,317
`
`tent claims the benefit of priority: App’n No. 10/111,716 (filed as No.
`
`PCT/GB00/4110); and U.S. Patent No. 7,334,720.7
`
`IV. DETAILED EXPLANATION OF REASONS FOR RELIEF
`REQUESTED, SHOWING IT IS MORE LIKELY THAN NOT THAT
`AT LEAST ONE CHALLENGED CLAIM IS UNPATENTABLE
`
`Pursuant to §§ 42.22, 42,208, and 42.304(b), a full statement of the reasons for
`
`the relief requested, including a detailed explanation of the evidence, material facts,
`
`and the governing law, rules and precedent is provided below. IV.A lists and explains
`
`the bases for Petitioner’s relevant claim constructions. IV.B provides each ground for
`
`which it is more likely than not that each challenged claim is invalid. In particular,
`
`claims 1, 6-8, 12-14, 16, and 18 are a

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