`______________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`______________________
`
`GOOGLE INC.
`Petitioner
`
`v.
`
`CONTENTGUARD HOLDINGS, INC.
`Patent Owner
`
`______________________
`
`Case CBM: Unassigned
`______________________
`
`PETITION FOR COVERED BUSINESS METHOD PATENT REVIEW OF
`U.S. PATENT NO. 7,774,280 UNDER 35 U.S.C. § 321 AND § 18 OF THE
`LEAHY-SMITH AMERICA INVENTS ACT
`
`Mail Stop “PATENT BOARD”
`Patent Trial and Appeal Board
`U.S. Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`
`Google CBM Petition for U.S. Patent No. 7,774,280
`
`TABLE OF CONTENTS
`
`Page
`
`I.
`
`II.
`
`INTRODUCTION ...........................................................................................1
`
`OVERVIEW OF THE ‘280 PATENT AND PETITIONER’S
`CHALLENGE .................................................................................................1
`
`III. MANDATORY NOTICES .............................................................................6
`
`IV. GROUNDS FOR STANDING (37 C.F.R. § 42.304(a)).................................8
`
`A.
`
`The ‘280 Patent is Directed to a Covered Business Method.................9
`
`1.
`
`2.
`
`The ‘280 Patent claims methods and systems used in
`financial services.........................................................................9
`
`The ‘280 Patent is not directed to a technological
`invention....................................................................................15
`
`i.
`
`ii.
`
`The claimed subject matter as a whole does not
`recite a technological feature that is novel and
`unobvious over the prior art............................................16
`
`The claimed subject matter does not solve a
`technical problem using a technical solution..................20
`
`V.
`
`VI.
`
`CLAIMS FOR REVIEW...............................................................................25
`
`IDENTIFICATION OF THE CHALLENGE ...............................................25
`
`VII. CLAIM CONSTRUCTION ..........................................................................26
`
`A. Meta-right............................................................................................27
`
`B.
`
`C.
`
`D.
`
`E.
`
`Right(s)................................................................................................30
`
`License.................................................................................................31
`
`State variable .......................................................................................31
`
`Repository ...........................................................................................33
`
`62401440_23
`
`i
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`Page
`
`VIII. FULL STATEMENT OF THE REASONS FOR RELIEF
`REQUESTED................................................................................................36
`
`A.
`
`The § 101 Grounds..............................................................................36
`
`1.
`
`[Ground 1] Claims 1, 5, 11, 12 and 22 of the ‘280 Patent
`are Invalid Under 35 U.S.C. § 101 as Being Directed to
`Non-Statutory Subject Matter...................................................36
`
`i.
`
`ii.
`
`iii.
`
`iv.
`
`Patent-eligibility framework...........................................37
`
`The ‘280 Patent claims are directed to an
`unpatentable abstract idea...............................................39
`
`The ‘280 Patent’s claims add nothing to the
`abstract idea except use of known and general
`purpose computers..........................................................46
`
`No further meaningful method or system elements
`beyond the abstract idea are claimed..............................52
`
`B.
`
`[Ground 2] Claims 1, 5, 11, 12 and 22 Are Invalid Under 35
`U.S.C. § 102 In View of the ‘012 Patent ............................................56
`
`1.
`
`2.
`
`3.
`
`The ‘012 Patent is Prior Art to the ‘280 Patent Under 35
`U.S.C. § 102(a) and (b).............................................................56
`
`The Teaching of the ‘012 Patent...............................................56
`
`Every element of the challenged claims of the ‘280
`Patent is anticipated or rendered obvious by the ‘012
`Patent.........................................................................................61
`
`C.
`
`[Ground 2] Element-By-Element Anticipation Analysis....................63
`
`1.
`
`2.
`
`Claim 1, Preamble, “A computer-implemented method
`for transferring rights adapted to be associated with items
`from a rights supplier to a rights consumer, the method
`comprising:”..............................................................................63
`
`Claim 1, Element A, “obtaining a set of rights associated
`with an item, the set of rights including a meta-right
`specifying a right that can be created when the meta-right
`
`ii
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`Page
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`9.
`
`is exercised, wherein the meta-right is provided in digital
`form and is enforceable by a repository;”.................................63
`
`Claim 1, Element B, “determining, by a repository,
`whether the rights consumer is entitled to the right
`specified by the meta-right;”.....................................................65
`
`Claim 1, Element C, “and exercising the meta-right to
`create the right specified by the meta-right if the rights
`consumer is entitled to the right specified by the meta-
`right, wherein the created right includes at least one state
`variable based on the set of rights and used for
`determining a state of the created right.”:.................................68
`
`Claim 5, “The method of claim 1, wherein the state
`variable is updated upon exercise of a right associated
`with the state variable.”.............................................................70
`
`Claim 11, “The method of claim 1, further comprising
`generating a license including the created right, if the
`rights consumer is entitled to the right specified by the
`meta-right.” ...............................................................................70
`
`Claim 12, Preamble, “A system for transferring rights
`adapted to be associated with items from a rights supplier
`to a rights consumer, the system comprising:”.........................71
`
`Claim 12, Element A, “means for obtaining a set of rights
`associated with an item, the set of rights including a
`meta-right specifying a right that can be created when the
`meta-right is exercised, wherein the meta-right is
`provided in digital form and is enforceable by a
`repository;”................................................................................71
`
`Claim 12, Element B, “means for determining whether
`the rights consumer is entitled to the right specified by
`the meta-right; and” ..................................................................72
`
`10. Claim 12, Element C, “means for exercising the meta-
`right to create the right specified by the meta-right if the
`rights consumer is entitled to the right specified by the
`meta-right, wherein the created right includes at least one
`
`iii
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`Page
`
`state variable based on the set of rights and used for
`determining a state of the created right.”..................................73
`
`11. Claim 22, “The system of claim 12, further comprising
`means for generating a license including the created
`right, if the rights consumer is entitled to the right
`specified by the meta-right.”.....................................................74
`
`D.
`
`[Ground 3] Claims 1, 5, 11, 12 and 22 Are Invalid Under 35
`U.S.C. § 103 in View of the ‘012 Patent and the Knowledge of
`a Person of Ordinary Skill in the Art ..................................................74
`
`IX. CONCLUSION..............................................................................................76
`
`iv
`
`
`
`Google CBM Petition for U.S. Patent No. 7,774,280
`
`TABLE OF AUTHORITIES
`
`CASES
`Accenture Global Servs. v. Guidewire Software, Inc.,
`728 F.3d 1336 (Fed. Cir. 2013) ..........................................................................55
`
`Page(s)
`
`Alice Corp. v. CLS Bank Int’l,
`573 U.S. __, 134 S. Ct. 2347 (2014)............................................................passim
`
`Bancorp Services, L.L.C. v. Sun Life Assurance Co. of Canada (U.S.),
`687 F.3d 1266 (Fed. Cir. 2012) ..............................................................36, 39, 50
`
`Bilski v. Kappos,
`130 S. Ct. 3218 (2010).................................................................................passim
`
`Cochrane v. Deener,
`94 U.S. 780 (1976)..............................................................................................47
`
`ContentGuard Holdings, Inc. v. Amazon.com Inc. et al.,
`No. 2:13-cv-01112-JRG (E.D. Tex.) ....................................................................7
`
`ContentGuard Holdings, Inc. v. Google Inc.,
`No. 2:14-cv-00061-JRG-RSP (E.D. Tex.)............................................................6
`
`CyberSource Corp. v. Retail Decisions,
`654 F.3d 1366 (Fed. Cir. 2011) ....................................................................46, 50
`
`Dealertrack, Inc. v. Huber,
`674 F.3d 1315 (Fed. Cir. 2012) ..........................................................................50
`
`Diamond v. Diehr,
`450 U.S. 175 (1981)......................................................................................23, 47
`
`DyStar Textilfarben GmbH & Co. v. C.H. Patrick Co.,
`464 F.3d 1356 (Fed. Cir. 2006) ..........................................................................75
`
`Google Inc. v. ContentGuard Holdings, Inc.,
`No. 3:14-cv-00498-WHA (N.D. Cal.)..................................................................7
`
`Gottschalk v. Benson,
`409 U.S. 63 (1972)........................................................................................39, 47
`
`v
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`Page(s)
`
`Graham v. John Deere Co.,
`383 U.S. 1, 148 USPQ 459 (1966) .....................................................................74
`
`Halliburton Energy Servs., Inc. v. M-I LLC,
`514 F.3d 1244 (Fed. Cir. 2008) ..........................................................................33
`
`In re Am. Acad. Of Sci. Tech. Ctr.,
`367 F.3d 1359 (Fed. Cir. 2004) ..........................................................................26
`
`In re Kahn,
`441 F.3d 977 (Fed. Cir. 2006) ............................................................................75
`
`In re Lund,
`376 F.2d 982 (C.C.P.A. 1967)......................................................................13, 34
`
`In re Paulsen,
`30 F.3d 1475 (Fed. Cir.1994) .............................................................................26
`
`In re Translogic Tech., Inc.,
`504 F.3d 1249 (Fed. Cir. 2007) ..........................................................................26
`
`In re Van Geuns,
`988 F.2d 1181 (Fed. Cir. 1993) ..........................................................................26
`
`KSR Int’l Co. v. Teleflex Inc.,
`550 U.S. 398 (2007)......................................................................................74, 75
`
`Mayo v. Prometheus,
`132 S. Ct. 1289 (2012).................................................................................passim
`
`Parker v. Flook,
`437 U.S. 584 (1978)............................................................................................47
`
`STATUTES
`35 U.S.C. § 101.................................................................................................passim
`
`35 U.S.C. § 102(a) .............................................................................................25, 56
`
`35 U.S.C. § 102(b) .............................................................................................25, 56
`
`35 U.S.C. § 103............................................................................................25, 74, 75
`
`AIA § 18(a)(1)(C) ....................................................................................................56
`
`vi
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`Page(s)
`
`OTHER AUTHORITIES
`
`37 CFR 1.57(b)(1)..............................................................................................13, 34
`
`37 C.F.R. § 42.8(b)(1)................................................................................................6
`
`37 C.F.R. § 42.8(b)(2)................................................................................................6
`
`37 C.F.R. § 42.8(b)(3)................................................................................................7
`
`37 C.F.R. § 42.8(b)(4)................................................................................................7
`
`37 C.F.R. § 42.300(b) ..............................................................................................26
`
`37 C.F.R. § 42.301 .....................................................................................................9
`
`37 C.F.R. § 42.301(a)...............................................................................................15
`
`37 C.F.R. § 42.301(b) ..............................................................................................15
`
`37 C.F.R. § 42.302(a).................................................................................................8
`
`37 C.F.R. § 42.302(b) ................................................................................................8
`
`vii
`
`
`
`Google CBM Petition for U.S. Patent No. 7,774,280
`
`Exhibit
`#
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`1013
`
`1014
`
`1015
`
`1016
`
`1017
`
`1018
`
`EXHIBIT LIST
`
`Description
`
`U.S. Patent No. 7,774,280 to Nguyen et al. (“the ‘280 Patent”)
`
`U.S. Patent No. 5,634,012 to Stefik et al. (“the ‘012 Patent”)
`
`Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 134 S.Ct. 2347 (June 19, 2014)
`
`Complaint, ContentGuard Holdings, Inv. V. Google Inc., Case No.
`2:14-cv-00061-JRG-RSP (E.D. Tex.), Dkt. No. 1
`SAP America, Inc. v. Versata Dev. Group, Inc., CBM2012-00001,
`Paper 36 (Jan. 9, 2013)
`Office Patent Trial Practice Guide, 77 Fed. Reg. 157 (August 14, 2012)
`
`Congressional Record – Senate, 157 Cong. Rec. S1360-1394 (daily ed.
`March 8, 2011) (Sen. Schumer)
`Volusion, Inc. v. Versata Software, Inc. et al., CBM2013-00017, Paper
`No. 8 (October 24, 2013)
`Salesforce.com, Inc. v. Virtualagility, Inc., CBM2013-00024, Paper No.
`47 (Sept. 16, 2014)
`Google Inc. v. Inventor Holdings, LLC, CBM2014-00002, Paper No. 16
`(April 1, 2014)
`Experian Marketing Solutions, Inc. v. RPost Communications Ltd.,
`CBM2014-00010, Paper No. 20 (April 22, 2014)
`Apple Inc. v. Sightsound Techs., LLC, CBM2013-00019, Paper No. 17
`(October 8, 2013)
`Hulu, LLC v. Intertainer, Inc. Case CBM2014-00053, Paper 11 (June
`23, 2014)
`Declaration of Benjamin Goldberg, Ph.D.
`
`Bray et al., “Extensible Markup Language (XML) 1.0,” W3C
`Recommendation, February 10, 1998
`Reserved
`
`Bloomberg Inc. et al. v. Markets-Alert PTY LTD, CBM2013-00005,
`Paper No. 18 (Mar. 29, 2013)
`Definition of “Meta,” Oxford English Dictionary
`www.oxforddictionaries.com/definition/english/meta
`
`viii
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`Exhibit
`#
`1019
`
`1020
`
`1021
`
`1022
`
`1023
`
`1024
`
`1025
`
`1026
`
`1027
`
`1028
`
`1029
`
`1030
`
`Description
`
`Definition of “Right,” Merriam-Webster Online Dictionary, available at
`http://www.merriam-webster.com/dictionary/right
`Definition of “Variable,” The Free Dictionary, available at
`http://www.thefreedictionary.com/variable+%28computer+science%29
`ZTE Corp. and ZTE (USA) Inc. v. ContentGuard Holdings, IPR2013-
`00133, Paper No. 61 (July 1, 2014)
`File History for U.S. Patent No. 7,774,280, March 29, 2010 Notice of
`Allowance
`EBay, Inc. v. Paid, Inc., CBM2014-00125, Paper No. 15 (Sept. 30,
`2014)
`File History for U.S. Patent No. 7,774,280, December 29, 2008 Non-
`Final Rejection
`File History for U.S. Patent No. 7,774,280, May 28, 2009 Applicant
`Response to Final Rejection
`Reserved
`
`Reserved
`
`Reserved
`
`Ultramercial, Inc. et al v. Hulu, LLC et al., 2010-1544 (Fed Cir.
`November 14, 2014)
`U.S. Patent No. 5,629,980 to Stefik et al. (“the ‘980 Patent”)
`
`ix
`
`
`
`Google CBM Petition for U.S. Patent No. 7,774,280
`
`I.
`
`INTRODUCTION
`
`Google Inc. (“Google” or “Petitioner”) petitions for Covered Business
`
`Method Patent Review (“Petition”), seeking cancellation of claims 1, 5, 11, 12 and
`
`22 of U.S. Patent No. 7,774,280 to Nguyen et al. (“the ‘280 Patent”) (See GOOG-
`
`1001), owned by ContentGuard Holdings, Inc. (“ContentGuard” or “Patent
`
`Owner”).
`
`II. OVERVIEW OF THE ‘280 PATENT AND PETITIONER’S
`CHALLENGE
`
`The ‘280 Patent is directed generally to digital rights management (“DRM”)
`
`and specifically to the concept of transferring “usage rights” that grant one or more
`
`users access to digital content, like a movie or an eBook. (See GOOG-1001, 1:36-
`
`51; 2:51-64; 12:41-46; 13:65-14:43.) The ‘280 Patent describes known ways of
`
`implementing DRM over the internet, where content owners or distributors attach
`
`prescribed usage rights to digital content. (See GOOG-1001, 2:14-29.) The usage
`
`rights define one or more manners of use, i.e., how a recipient of the content may
`
`use the digital content. (See id., 2:14-16.) For example, an owner or distributor of
`
`digital content may grant the recipient of the digital content the usage rights for
`
`“viewing only.” (Id., 2:16-18; see also id., 2:9-14.) Conditions on use may also be
`
`included with the usage rights such that “usage rights can be contingent on
`
`payment or other conditions.” (Id., 2:18-19.) The ‘280 Patent describes known,
`
`prior art DRM concepts like “authentication, authorization, accounting, payment
`
`1
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`and financial clearing, rights specification, rights verification, rights enforcement,
`
`and document protection” that are described in U.S. Patent No. 5,634,012 (“the
`
`‘012 Patent”), which is incorporated by reference into the ‘280 Patent
`
`specification. (See GOOG-1001, 1:34-43; 2:9-16; GOOG-1014, ¶¶ 20, 21.)
`
`The ‘280 Patent specification describes two drawbacks of the prior art. First,
`
`it says that content owners cannot control the use of content by downstream users
`
`unless the content owners remain a party to the transaction:
`
`DRM systems have facilitated distribution of digital content by
`permitting the content owner to control use of the content. However,
`known business models for creating, distributing, and using digital
`content and other items involve a plurality of parties. For example, a
`content creator may sell content to a publisher who then authorizes a
`distributor to distribute content to an on-line storefront who then sells
`content to end-users. Further, the end users may desire to share or
`further distribute the content. In such a business model, usage rights
`can be given to each party in accordance with their role in the
`distribution chain. However, the parties do not have control over
`downstream parties unless they are privy to any transaction with the
`downstream parties in some way. For example, once the publisher
`noted above provides content to the distributor, the publisher cannot
`readily control rights granted to downstream parties, such as the
`first or subsequent users unless the publisher remains a party to the
`downstream transaction. This loss of control combined with the ever
`
`2
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`increasing complexity of distribution chains results in a situation
`which hinders the distribution of digital content and other items.
`
`(GOOG-1001, 2:22-42 (emphasis added).) In addition to the issue of downstream
`
`control of content, the ‘280 Patent also notes that the prior art fails to provide a
`
`facility for allowing a downstream party to grant rights that are different from the
`
`rights held by the downstream party itself:
`
`Further, the publisher may want to prohibit the distributor and/or the
`storefront from viewing or printing content while allowing an end user
`receiving a license from the storefront to view and print. Accordingly,
`the concept of simply granting rights to others that are a subset of
`possessed rights is not adequate for multi-party, i.e. multi-tier,
`distribution models.
`
`(GOOG-1001, 2:42-48; GOOG-1014, ¶ 22.)
`
`The ‘280 Patent purports to address these shortcomings by the claimed use
`
`of “meta-rights” and “state variables.” Meta-rights are usage rights that permit the
`
`granting of rights to others, i.e., meta-rights are rights that allow a recipient of the
`
`right to create a new usage right and send that new usage right on to another party.
`
`(GOOG-1001, 5:47-56.) State variables track dynamic state conditions. (Id., 8:3-
`
`16.) (GOOG-1014, ¶ 23.)
`
`3
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`As an example, as shown by Figure 12 of the ‘280 Patent, a creator of digital
`
`media (1201) offers usage rights to a distributor of digital media (1202 and 1203).
`
`The usage rights provided by the content creator to the distributors include meta-
`
`rights, which grant the distributor the rights to provide “play” right to users of the
`
`digital content further down the distribution chain in the form of licenses (1204,
`
`1205 and 1206). State variables track the “play” right exercised by the user (e.g.,
`
`Alice, Bob and Cathy). The “play” right is limited to 5 concurrent plays for each
`
`organization (urn:acme:club, urn:foo:club) and the play uses are tracked by the
`
`4
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`respective state variables. (Id., 12:57-13:8.) Here, state variables are counters
`
`where a state represents the number of times the “play” right is exercised. (Id.,
`
`13:9-17; 13:54-64.) (GOOG-1014, ¶ 24.)
`
`As will be fully described by this Petition, the ‘012 Patent, which is
`
`incorporated by reference into the ‘280 Patent and issued more than four years
`
`before the earliest priority date of the ‘280 Patent, describes every element of the
`
`challenged claims. The ‘012 Patent describes usage rights in which a “Next-Set-of-
`
`Rights” may be specified. (See GOOG-1002; Fig. 15; Element 1509.) Like a meta-
`
`right, this “Next-Set-of-Rights” allows a creator of usage rights to specify a set of
`
`usage rights that the receiver of the rights may create and provide to a next party.
`
`Further, the ‘012 Patent describes the use of state variables that can track changing
`
`conditions relating to a created right, such as the “Copies-in-Use” and “Copy-
`
`Count” variables, that count and limit the number of “copies” of the work that may
`
`be exercised simultaneously for the right. (Id., 10:51-54; 22:2-5.)
`
`As demonstrated by this Petition, the challenged claims of the ‘280 Patent
`
`are anticipated and/or rendered obvious by the prior art ‘012 Patent that is
`
`incorporated by reference into the specification of the ‘280 Patent. The ‘280 patent
`
`does not claim priority and has no direct relationship to the ‘012 Patent.
`
`This Petition will also show that the ‘280 Patent claims subject matter that is
`
`not patentable under 35 U.S.C. §101. During the prosecution of the ‘280 Patent,
`
`5
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`the examiner twice rejected the pending claims based on “101 issues.” In response
`
`to the examiner’s rejection, the Patent Owner amended the independent claims to
`
`recite use of “a repository,” “a computer-implemented method” and to recite that
`
`meta-rights are in “digital form,” to render the claims patentable under the then-
`
`dispositive “machine or transformation” test. However, the Supreme Court and
`
`Federal Circuit’s recent decisions involving Section 101 have made clear that the
`
`“machine or transformation” test applied by the ‘280 Patent examiner is no longer
`
`controlling; and those decisions vitiate Patent Owner’s attempts to secure claims
`
`covering abstract ideas simply by adding language reciting generic and well-
`
`known computer processing steps and devices. For this additional reason, the
`
`challenged claims are invalid. (See generally GOOG-1003.)
`
`III. MANDATORY NOTICES
`
`Real Party-in-Interest: In accordance with 37 C.F.R. § 42.8(b)(1), Petitioner
`
`identifies Google Inc. as the real Party-in-Interest.
`
`Related Matters: In accordance with 37 C.F.R. § 42.8(b)(2), Petitioner
`
`identifies the following related proceedings:
`
`1) ContentGuard Holdings, Inc. v. Google Inc., No. 2:14-cv-00061-JRG-
`
`RSP (E.D. Tex.), filed February 5, 2014 (referred to hereafter as “the
`
`Litigation”);
`
`6
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`2) Google Inc. v. ContentGuard Holdings, Inc., No. 3:14-cv-00498-WHA
`
`(N.D. Cal.),1 filed January 31, 2014;
`
`3) ContentGuard Holdings, Inc. v. Amazon.com Inc. et al., No. 2:13-cv-
`
`01112-JRG (E.D. Tex.), filed December 18, 2013 (collectively, the
`
`“Related Litigations.”); and
`
`4) Petition for Covered Business Method Review for U.S. Patent No.
`
`8,001,053.
`
`Designation of Lead and Back-Up Counsel: In accordance with 37 C.F.R.
`
`§ 42.8(b)(3):
`
`Lead: Robert R. Laurenzi (Reg. # 45,557), KAYE SCHOLER LLP, 250
`
`West 55th Street, New York, New York 10019-9710, 212-836-7235 (telephone).
`
`Backup: Nisha Agarwal, (Reg. # 67,039), KAYE SCHOLER LLP, 2 Palo
`
`Alto Square, 3000 El Camino Real, Suite 400, Palo Alto, CA 94306, 650-319-4549
`
`(telephone).
`
`Notice of Service Information: In accordance with 37 C.F.R. § 42.8(b)(4),
`
`please direct all correspondence to lead and back-up counsel at the above address.
`
`1 Google did not challenge the validity of the ‘280 Patent in this declaratory
`
`judgment action.
`
`7
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`Petitioners consent to email service at Robert.Laurenzi@kayescholer.com and
`
`CBM7774280-1@kayescholer.com
`
`IV. GROUNDS FOR STANDING (37 C.F.R. § 42.304(a))
`
`The undersigned and Google certify that the ‘280 Patent is available for
`
`post-grant review because the ‘280 Patent constitutes a covered business method
`
`patent as defined by Section 18 of the America Invents Act. See AIA
`
`§ 18(a)(1)(A). The AIA defines covered business method patents as patents that
`
`relate to financial products or services and are not directed towards a technological
`
`invention. AIA § 18(d)(1). For the reasons described below, the ‘280 Patent
`
`satisfies both of these requirements.
`
`Further, Google meets all standing requirements and maintains full
`
`eligibility to file this petition. A petitioner may not file a petition to institute a
`
`covered business method review unless the petitioner has been sued for patent
`
`infringement. 37 C.F.R. § 42.302(a). Here, ContentGuard has sued Google for
`
`infringement of the ‘280 Patent. (See, e.g., GOOG-1004.) Thus, Google has
`
`standing to file the present petition.
`
`Also, a petitioner may not file a petition for covered business method review
`
`where the petitioner is estopped from challenging the claims. 37 C.F.R.
`
`§ 42.302(b). Google is not estopped from challenging the claims of the ‘280 Patent
`
`on the grounds herein.
`
`8
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`A.
`
`The ‘280 Patent is Directed to a Covered Business Method
`
`The ‘280 Patent is eligible for CBM review. The ‘280 Patent is directed to a
`
`covered business method because the claims are used in financial services and are
`
`not directed to a technological invention.
`
`1.
`
`The ‘280 Patent claims methods and systems used in financial
`services
`
`The AIA defines a covered business method patent as a “patent that claims a
`
`method or corresponding apparatus for performing data processing or other
`
`operations used in the practice, administration, or management of a financial
`
`product or service …” AIA § 18(d)(1); see also 37 C.F.R. § 42.301. Under covered
`
`business method review, “financial product or service” is “broadly interpreted and
`
`encompass[es] patents claiming activities that are financial in nature, incidental to
`
`a financial activity or complementary to a financial activity.” (See GOOG-1005 at
`
`21-22 (citing GOOG-1006 at 2-3).) In this context, financial “is an adjective that
`
`simply means relating to monetary matters.” (See GOOG-1005 at 23.) The
`
`“presence of a single claim is sufficient to institute a covered business method
`
`review.” (Id. at 26.) The U.S.P.T.O. noted that the AIA’s legislative history
`
`demonstrates that “financial product or service” should be “interpreted broadly,”
`
`encompassing patents claiming activities that are “financial in nature, incidental to
`
`a financial activity or complementary to a financial activity.” (See GOOG-1006 at
`
`3.) Of particular pertinence to the ‘280 Patent, Sen. Schumer, co-author of § 18,
`
`9
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`stated “[t]o meet this [eligibility] requirement, the patent need not recite a specific
`
`financial product or service. Rather, the patent claims must only be broad enough
`
`to cover a financial product or service.” (See GOOG-1007 at 6 (emphasis added).)
`
`In Volusion v. Versata (See GOOG-1008 at 6), the PTAB ruled that although the
`
`claims merely recited a method of representing a plurality of items in a database,
`
`the specification pointed out that the invention could be used in the field of e-
`
`commerce and were therefore eligible for Covered Business Method review. (See
`
`GOOG-1008 at 7-8; see also GOOG-1009 at 7-8 (finding that items displayed to a
`
`user may be associated with a financial service).) Thus, a claim need not map
`
`directly to a monetary or financial activity to qualify for covered business method
`
`review, but need only have claims that encompass embodiments that are financial
`
`in nature, incidental to financial activity or complementary to a financial activity.
`
`(See GOOG-1010 at 8.)
`
`The claims of the ‘280 Patent encompass embodiments that facilitate the use
`
`or distribution of digital content based on the payment of fees by users, thus
`
`rendering the claims, at the very least, incidental and complementary to financial
`
`activity. The ‘280 Patent claims describe the purported invention using economic
`
`terms - the claimed system and method facilitate the transfer of rights between a
`
`rights “supplier” and a rights “consumer.” (GOOG-1001, 2:52-55.) To this end, the
`
`independent claims of the ‘280 Patent are all directed toward “obtaining a set of
`
`10
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`rights” by the consumer including “meta-rights” relating to an item such as digital
`
`content. (See id., 15:10-11; 15:55-56; 16:37-38.) The ‘280 Patent specification
`
`confirms the financial nature of this claimed content acquisition activity, including
`
`the purchase of digital assets and the payment of fees. (See, e.g., id., 4:3-14.)
`
`The specification describes the claimed rights as being contained in a
`
`license. Digital content is provided by way of a license in exchange for a monetary
`
`fee:
`
`Rights label 40 is associated with content 42 and specifies usage
`rights and possibly corresponding conditions that can be selected by a
`content recipient. License Server 50 manages the encryption keys and
`issues licenses for protected content. These licenses embody the actual
`granting of usage rights to an end user. For example, rights label 40
`may include usage rights permitting a recipient to view content for a
`fee of five dollars and view and print content for a fee of ten dollars.
`License 52 can be issued for the view right when the five dollar fee
`has been paid, for example. Client component 60 interprets and
`enforces the rights that have been specified in license 52.
`
`(Id., 4:3-14 (emphasis added).) Later, when describing conditions that must be
`
`satisfied to exercise the claimed “right” from the license, the specification explains
`
`that conditions may be based on payment of a fee: “[f]or, example, [sic] a
`
`condition may be the payment of a fee, submission of personal data, or any other
`
`requirement desired before permitting exercise of a manner of use.” (Id., 4:39-43;
`
`11
`
`
`
`Google Petition of U.S. Patent No. 7,774,280
`
`see also id., 5:4-11 (emphasis added).) The specification of the ‘280 Patent also
`
`discusses the use of a financial clearinghouse to process transactions and verify
`
`payment relating to the claimed rights transfers. (Id., 5:35-37.)
`
`The ‘280 Patent thus describes and claims embodiments necessitating the
`
`payment of fees in exchange for licenses for content usage, i.e., e-commerce
`
`embodiments that are directed to the buying and selling of products or services
`
`over electronic systems that comports with “‘an agreement between two parties
`
`stipulating movements of money or other consideration now or in the future.’”
`
`(GOOG-1011 at 6, citing GOOG-1012 at 12 (internal citations omitted).) The use
`
`of licenses are required by challenged claims 11 and 22. These are activities that
`
`are “‘complementary to a financial activity’” and “‘relate to monetary matters’”
`
`and therefore place the ‘280 Patent within the ambit of CBM review. (Id. at 12.)
`
`The ‘012 Patent, which is incorporated by reference into the ‘280 Patent, is
`
`also replete with references to financial activities relating to the distribution and
`
`use of digital content. The ‘280 Patent inco