`U.S. Patent No. 8,266,432
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`UNITED SERVICES AUTOMOBILE ASSOCIATION,
`Petitioner
`
`v.
`
`NADER ASGHARI-KAMRANI and KAMRAN ASGHARI-KAMRANI,
`Patent Owners
`
`U.S. PATENT NO. 8,266,432
`Case CBM2016-00063
`
`PATENT OWNER PRELIMINARY RESPONSE
`
`Mail Stop: PATENT BOARD
`Patent Trial and Appeal Board
`United States Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`
`Table of Contents
`
`I.
`
`II.
`
`INTRODUCTION ..................................................................................... 1
`
`SUMMARY OF THE ‘432 PATENT ........................................................ 3
`
`III.
`
`THE BOARD DENIED PETITIONER’S PREVIOUS PETITION FOR IPR
`
`OF THE ‘432 PATENT ............................................................................... 6
`
`IV.
`
`THE ‘432 PATENT IS NOT ELIGIBLE FOR REVIEW UNDER § 18 OF
`
`THE AIA ..................................................................................................... 8
`
`A. The ‘432 Patent Is Not A Covered Business Method Patent........................ 9
`1. The Claims of the ‘432 Patent Are Not Directed to a “Financial Product
`or Service”.................................................................................................. 9
`2. The ‘432 Patent Is Not Directed to a “Financial Product or Service”
`Merely Because Its Specification Indicates That “to increase security in e-
`commerce” and/or Merely Because The Specification Includes a Few
`Finance-Related Terms..............................................................................14
`B. The ‘432 Patent Is Directed to a “Technological Invention”.......................21
`1. Considered as a Whole, the ‘432 Patent Claims Recite Novel and Non-
`Obvious Technological Features................................................................21
`2. Considered as a Whole, the ’432 Patent Claims Provide a Technical
`Solution To a Technical Problem...............................................................23
`3. Considered as a Whole, the Claims of the ‘432 Patent Meet the High
`Standard of Novelty...................................................................................31
`CLAIM CONSTRUCTION ......................................................................36
`
`PRIORITY................................................................................................37
`
`V.
`
`VI.
`
`ii
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`A. The Effective Priority Date For the ‘432 Patent is Aug. 29, 2001 and The
`‘676 Patent Provides Sufficient Written Description Support for the Claims of
`The ‘432 Patent ..............................................................................................38
`1. The OPFI and the RPFI of the ‘676 Patent can jointly form the claimed
`external entity. ...........................................................................................39
`2. “digital identity” ....................................................................................44
`3. Claims of the ‘432 Patent are supported by the ‘676 Patent ...................45
`
`B. Additional Chain of Benefit Claim Via U.S. Patent No. 8,281,129 ...........56
`1.Central entity and Trusted-Authenticator ................................................57
`2. External-Entity and Business .................................................................58
`3. User and Individual................................................................................60
`4. Dynamic Code and Dynamic Key..........................................................60
`5. Authentication of Online Users..............................................................61
`C. Patent Owners Do Not Admit that the ‘676 Patent Discloses A Different
`Invention than the ‘432 Patent. .......................................................................74
`VII. REASONS WHY COVERED BUSINESS METHOD PATENT REVIEW
`
`SHOULD NOT BE INSTITUTED .............................................................76
`
`VIII. CONCLUSION.........................................................................................79
`
`iii
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`
`LIST OF EXHIBITS
`
`Exhibit 2001
`
`Statutory Disclaimer
`
`Exhibit 2002
`
`AOL Time Warner, et al.
`
`Exhibit 2003
`
`Renewed Request for Certificate of Correction, and
`Renewed Petition Under pre-AIA 1.78(a)(3)
`
`Exhibit 2004
`
`U.S. 8,281,129 to Asghari-Kamrani et al.
`
`iv
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`
`I.
`
`INTRODUCTION
`
`Pursuant to 35 U.S.C. § 323, Patent Owners Nader Asghari-Kamrani and
`
`Kamran Asghari-Kamrani (“Patent Owner”), who are also the sole Inventors,
`
`respectfully submit
`
`this Preliminary Response responding to the Petition for
`
`Covered Business Method Review (“Petition”) of U.S. Patent No. 8,266,432 (“the
`
`‘432 Patent”).1
`
`This is not the first time Petitioner has challenged the ‘432 Patent before the
`
`Board. On September 1, 2015, Petitioner filed a Petition for Inter Partes Review of
`
`the ‘432 Patent under IPR2015-01842 (“Petition for IPR”) based on alleged prior art.
`
`On February 26, 2016, subsequent
`
`to Patent Owner’s December 10, 2015
`
`Preliminary Response, the Board denied institution of the IPR. Now, Petitioner has
`
`subsequently filed two Covered Business Method challenges to the same patent.
`
`Delayed, serial challenges to the same patent should be viewed unfavorably
`
`because they were not contemplated by the AIA. It places a huge burden on patent
`
`owners, and permits big companies, such as petitioner, to use its economic power,
`
`not its legal positons, to defeat the patent owner. Further, such repetitive activity
`
`1 This filing is within three months of the Notice of Filing Date Accorded to Petition
`
`(Paper No. 3) and is timely under 35 U.S.C. § 323 and 37 C.F.R. § 42.107(b).
`
`1
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`unnecessarily tax the resources of the Board, and prejudices patent owners such as
`
`the Patent Owner here who are the inventors themselves.
`
`The claims of the ‘432 Patent are not eligible for a Covered Business Method
`
`Review (“CBMR”). The ‘432 Patent claims do not contain a single element that can
`
`be characterized as being related to the “practice, administration, or management of
`
`a financial product or service.” AIA §18(d)(1); see also 37 C.F.R. §42.301(a). Rather,
`
`the claims are of “general utility” with no tie to any specific financial product or
`
`service. The Petition should be denied on this basis alone.
`
`Moreover, the ‘432 Patent is directed to a specific technology solution (a new
`
`centralized authentication topology) to an authentication and network security
`
`problem created by the Internet. This is needed because on the Internet nobody
`
`knows if users are who they say they are. Therefore the online environment
`
`introduces new security risks and creates the need for a low cost and easy to use
`
`authentication system and method. That is what the presently claimed invention is
`
`directed to, authenticating a plurality of online users on instantaneous real time basis
`
`that does not have any pre-Internet “real-world” analogue. The Federal Circuit has
`
`confirmed that such inventions are patent-eligible. DDR Holdings, LLC v. Hotels.
`
`Com, L.P., 773 F.3d 1245, 1257 (Fed. Cir. 2014).
`
`Further, the purported basis for Petitioner’s challenge--that the effective
`
`priority date for the ‘432 Patent claims is Sept. 15, 2008-- is wholly unsupported and
`2
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`the priority date for the involved ‘432 Patent is Aug. 29, 2001. This is important
`
`because all of the Petitioner’s proposed grounds of rejection rely upon a single
`
`reference, the Norefors patent, which has a date as a reference that is after the priority
`
`date of the ‘432 Patent. Thus, Norefors is NOT prior art relative to any of the
`
`claims of the ‘432 Patent.
`
`II.
`
`SUMMARY OF THE ‘432 PATENT
`
`The ‘432 Patent relates to a technical cyber security system. More particularly,
`
`it relates to “a centralized identification and authentication system and method for
`
`identifying an individual over a communication network such as Internet, to increase
`
`security” (Ex. 1001 at 1:22-25.), and relates to a computerized “method and system
`
`for generation of a dynamic, non-predictable and time dependent SecureCode for the
`
`purpose of positively identifying an individual.” (Id. at 1:25-28.)
`
`The ‘432 Patent issued on September 11, 2012 and is a continuation-in-part
`
`of U.S. patent application No. 11/239,046, filed on September 30, 2005, now Patent
`
`No. 7,444,676 (the ‘676 Patent), which is a continuation-in-part of U.S. patent
`
`application No. 09/940,635, filed on August 29, 2001, now patent No. 7,356,837
`
`(the ‘837 Patent).
`
`Referring to FIGURE 2, the Specification of the ‘432 Patent describes the
`
`claimed method of claim 1 as shown in Table 1 below.
`
`3
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`
`The ‘432 Patent, FIG. 2
`
`Table 1
`
`Arrows
`(FIG. 2)
`F
`
`Corresponding Claim Features of Claim 1 of the ‘432 Patent
`
`"receiving electronically a request for a dynamic code for the user
`
`by a computer associated with a central-entity during the
`
`transaction between the user and the external-entity”
`
`4
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`“generating by the central-entity during the transaction a dynamic
`
`G
`
`code for the user in response to the request, wherein the dynamic
`
`code is valid for a predefined time and becomes invalid after being
`
`used”
`
`H
`
`“providing by the computer associated with the central-entity said
`
`generated dynamic code to the user during the transaction”
`
`I and J
`
`“receiving electronically by the central-entity a request
`
`for
`
`authenticating the user from a computer associated with the
`
`external-entity based on a user-specific information and the
`
`dynamic code as a digital identity included in the request which
`
`said dynamic code was received by the user during the transaction
`
`and was provided to the external-entity by the user during the
`
`transaction”
`
`K and L “authenticating by the central-entity the user and providing a result
`
`of the authenticating to the external-entity during the transaction if
`
`the digital identity is valid”
`
`One of advantages of the ‘432 Patent is that the centralized identification and
`
`authentication system can be relatively easily established with overall reduced
`
`system cost. Thus, the ‘432 Patent solves a problem of computer network security
`
`5
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`in an online environment for authenticating a user with an easy and economical
`
`authentication system by providing a technical solution. This technical invention is
`
`certainly not a method for performing data processing or other operations used in
`
`the practice of a financial service.
`
`III. THE BOARD DENIED PETITIONER’S PREVIOUS PETITION FOR
`
`IPR OF THE ‘432 PATENT
`
`On September 1, 2015, Petitioner, United Services Automobile Association,
`
`filed a Petition for IPR requesting an inter partes review of claims 1–55 of the ‘432
`
`Patent (Ex. 1001).
`
`Petitioner relied upon the following prior art references: Brown, U.S. Patent
`
`No. 5,740,361, issued April 14, 1998 (“Brown,” IPR2015-01842, Ex. 1010); Myers,
`
`et. al., X.509 Internet Public Key Infrastructure Online Certificate Status Protocol
`
`– OCSP, RFC 2560, Network Working Group (June 1999) (“Myers,” IPR2015-
`
`01842, Ex. 1011); and Neuman, B.C. and Ts’o, T., Kerberos: An Authentication
`
`Service for Computer Networks, ISI Research Report, ISI/RS- 94-399, IEEE
`
`Communications Magazine (September 1994) (“Neuman,” IPR2015-01842, Ex.
`
`1012).
`
`Petitioner argued the challenged claims are unpatentable based upon the
`
`following grounds: (1) obviousness in view of Brown and Myers (claims 1-55); (2)
`
`6
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`anticipation in view of Neuman (claims 1-3, 6-28, and 31-55); and (3) obviousness
`
`in view of Neuman (claims 4, 5, 29, and 30).
`
`On February 26, 2016, the Board denied institution of the IPR (IPR2015-
`
`01842, Paper 13) finding that “[p]etitioner’s argument does not explain how the
`
`combination of Myers and Brown teaches ‘providing a result of the authenticating
`
`to the external entity’ as required by claim 1” (IPR2015-01842, Paper 13 at 9); “we
`
`[(the Board)] are not persuaded that Petitioner has presented sufficient evidence or
`
`argument to establish a reasonable likelihood that either Brown or the combination
`
`of Brown and Myers teaches ‘authenticating by the central-entity the user and
`
`providing a result of the authenticating to the external-entity during the transaction
`
`if the digital identity is valid’ as recited in independent claim 1” (Id. at 11); and
`
`“[h]ere, an allegation that the verifier and authentication server may be the same
`
`entity because such a configuration would not be ‘technically infeasible’ or
`
`‘frustrate the purpose’ of the reference is not sufficient to establish Neuman teaches
`
`that the authentication server and verifier are in fact the same entity” (Id. at 15).
`
`Accordingly, the Board has already found that the technical features recited
`
`in the ‘432 Patent claims are novel and unobvious over what Petitioner must
`
`presumably have considered to be the most relevant prior art.
`
`7
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`IV. THE ‘432 PATENT IS NOT ELIGIBLE FOR REVIEW UNDER § 18
`OF THE AIA
`
`To be eligible for a Covered Business Method Review (CBMR) under § 18 of
`
`the AIA, a patent must be: (i) a “covered business method patent;” and (ii) not
`
`directed to a “technological invention.” Sony Corp. of Am. v. Network-1 Tech., Inc.,
`
`CBM2015-00078, Paper No. 7 at 7-8 (PTAB July 1, 2015) (hereinafter “Sony”). It
`
`is Petitioner’s burden to prove that both elements are established. See 37 C.F.R. §
`
`42.301(a); see also Bloomberg LP v. Quest Licensing Corp., CBM2014-00205,
`
`Paper No. 16 at 7-11 (PTAB Apr. 7, 2015).
`
`Regarding the first element, a patent can only be a “covered business method
`
`patent” if it “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) (emphasis added); see also 37
`
`C.F.R. § 42.301(a).
`
`Regarding the second element, a patent claim is a “technological invention”
`
`if “the claimed subject matter as a whole recites a technological feature that is novel
`
`and unobvious over the prior art; and solves a technical problem using a technical
`
`solution.” 37 C.F.R. § 42.301(b). Here, Petitioner fails to analyze the claims as a
`
`whole as required by 37 C.F.R. § 42.301(b). Petitioner instead generalizes the
`
`challenged claims as a collection of some of their elements (e.g., dynamic code) and
`8
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`alleges that such elements are generic and well-known. Petition at 14-15. Such an
`
`approach is improper. Moreover, the Board has already denied institution of
`
`Petitioner’s Petition for IPR which alleged that
`
`the challenged claims to be
`
`anticipated and obvious. Petitioner’s position that the technical features of those
`
`claims are not novel and unobvious is thus wholly unsupported and contradicts the
`
`Board’s prior decision on that very issue.
`
`It is Petitioner’s burden to prove that the ’432 Patent is a “covered business
`
`method patent” and that it is not directed to a “technological invention.” While
`
`Petitioner’s failure to meet its burden as to either requirement is sufficient to deny
`
`institution, here, Petitioner fails to meet its burden as to both requirements for a
`
`CBMR under § 18 of the AIA. The Board should therefore deny institution of a
`
`CBMR.
`
`A. The ‘432 Patent Is Not A Covered Business Method Patent
`
`1. The Claims of the ‘432 Patent Are Not Directed to a “Financial
`
`Product or Service”
`
`The ’432 Patent is not a CBM Patent because it does not “claim[] 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) (emphasis added).
`
`9
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`As Board precedent demonstrates, the proper focus of the CBM Patent inquiry
`
`should be on the patent claims. See, e.g., Roxane Labs. Inc. v. Jazz Pharm., Inc.,
`
`CBM2014-00161, Paper No. 16 at 10 (PTAB Feb. 9, 2015) (hereinafter “Roxane”)
`
`(“In making [the] determination [of whether a patent is a CBM Patent], our focus is
`
`firmly on the claims.”); and see also Sony, Paper No. 7 at 11. Here, the challenged
`
`claims do not contain a single element related to a “financial product or service.”
`
`Claim 1 of the ’432 Patent reads:
`
`“A method for authenticating a user during an electronic transaction between
`
`the user and an external-entity, the method comprising:
`
`receiving electronically a request for a dynamic code for the user by a
`
`computer associated with a central-entity during the transaction between the user
`
`and the external-entity;
`
`generating by the central-entity during the transaction a dynamic code for the
`
`user in response to the request, wherein the dynamic code is valid for a predefined
`
`time and becomes invalid after being used;
`
`providing by the computer associated with the central-entity said generated
`
`dynamic code to the user during the transaction;
`
`receiving electronically by the central-entity a request for authenticating the
`
`user from a computer associated with the external-entity based on a user-specific
`
`10
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`information and the dynamic code as a digital identity included in the request which
`
`said dynamic code was received by the user during the transaction and was provided
`
`to the external-entity by the user during the transaction; and
`
`authenticating by the central-entity the user and providing a result of the
`
`authenticating to the external-entity during the transaction if the digital identity is
`
`valid.”
`
`There is no term in Claim 1 (or the other challenged claims, which contain
`
`similar elements) that expressly recites a financial product or service, or that
`
`provides any particular relationship to such a product or service. Nor is there any
`
`reasonable claim construction under which these claims could somehow be
`
`interpreted to have such a relationship.
`
`Petition fails to show that any term in Claim 1 expressly recites a financial
`
`product or service, and merely states that “[c]laim 1, for example, recites ‘a method
`
`for authenticating a user during an electronic transaction’ that includes ‘receiving
`
`electronically…a request for authenticating the user…based on a user-specific
`
`information and a dynamic code as a digital identity.’” (Petition at 11). Petitioner,
`
`without any ground, support or basis, boldly concludes that “[t]he method for
`
`authenticating a user of claim 1 is used for data processing in the practice,
`
`administration, and management of financial products and services.” This lack of
`
`any nexus between the claims and a “financial product or service” is fatal to
`11
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`Petitioner’s attempt to institute a CBMR. See, e.g., ServiceNow, Inc. v. Hewlett-
`
`Packard, Co., CBM2015-00108, Paper No. 10 at 15-16 (PTAB October 7, 2015)
`
`(hereinafter “Hewlett-Packard”); J.P. Morgan Chase & Co. v. Intellectual Ventures
`
`II LLC, CBM2014-00160, Paper No. 11 at 11-12 (PTAB Jan. 29, 2015) (hereinafter
`
`“J.P. Morgan Chase”); Sega of Am., Inc. v. Uniloc USA, Inc., CBM2014-00183,
`
`Paper No. 11 at 11 (PTAB Mar. 10, 2015) (hereinafter “Sega”).
`
`Rather than being directed to a financial product or service, the claims of the
`
`‘432 Patent are of “general utility,” i.e., they recite a particular novel technique for
`
`authenticating a user during an electronic transaction between the user and an
`
`external-entity without restricting the field of use of the claimed invention to the
`
`financial sector or financial activity. When claims are of a “general utility” with no
`
`tie to a specific financial product or service, the Board has routinely denied
`
`institution of a CBMR. See, e.g., Hewlett-Packard, Paper No. 10 at 15-16 (patent
`
`claiming a “system for managing a conversation in a web service” is not a CBM
`
`Patent because the “claims are of general utility” with no recitation of “finance-
`
`related” terminology or limitations); J.P. Morgan Chase, at 11-12 (denying
`
`institution for patent claiming techniques for secure electronic communications
`
`that had “general utility not limited or specific to any application”)(emphasis added);
`
`Sega, Paper No. 11 at 11 (denying institution for patent whose “claims on their face
`
`12
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`are directed to technology that restricts the use of software” having “no particular
`
`relationship to a financial product or service”).
`
`There is no term in any of the challenged claims of the ‘432 Patent that has
`
`any arguable, particular relationship to financial products or services. There is no
`
`reasonable claim construction under which these claims could be interpreted as
`
`financial in nature – indeed, not even Petitioner proposes any claim construction that
`
`is financial in nature. See, e.g., Hewlett-Packard, Paper No. 10 at 12. Petitioner
`
`ignores the general nature of the claims, instead improperly focusing on illustrative
`
`embodiments set forth in the Specification, whose financial aspects are not recited
`
`expressly in the claims. Id.
`
`Here, Petitioner has failed to point to any language in the claims relating to a
`
`financial product or service. This is because there is no such language—the
`
`challenged claims of the ’432 Patent are of “general utility” and have no particular
`
`relationship to any financial product or service.
`
`Petitioner states that “Claim 4, which depends from claim 1, adds that ‘the
`
`transaction corresponds to a financial transaction.’” (Petition at 11). However, claim
`
`5, which also depends from claim 1, adds that “the transaction corresponds to a non-
`
`financial transaction. Thus, claims 4 and 5 as a whole reemphasize that claims of
`
`the ‘432 Patent are of “general utility.”
`
`13
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`Although Patent Owner does not concede that any of Petitioner’s argument
`
`related to AIA §18(d)(1) are correct, to expedite and to simplify the process of the
`
`CMBR , Patent Owner filed a disclaimer of claims 4 and 29 under 37 C.F.R. 1.321
`
`on August 3, 2016. See Exhibit 2001.
`
`Under 35 U.S.C. 253, “Such disclaimer shall be in writing and recorded in the
`
`Patent and Trademark Office, and it shall thereafter be considered as part of the
`
`original patent to the extent of the interest possessed by the disclaimant and by
`
`those claiming under him.” (emphasis added). Accordingly, the disclaimer of claims
`
`4 and 29 must be treated as if the ‘432 Patent never had them. Without claims 4 and
`
`29, it is further ensured that Petitioner has failed to point to any language in the
`
`claims relating to a financial product or service. The Board should not institute a
`
`CBMR proceeding based on disclaimed claims 4 and 29.
`
`See for example,
`
`CBM2014-00162, Paper No. 11 at 2.
`
`Thus, for at least the reasons described above, the ‘432 Patent is NOT a CBM
`
`patent eligible for the review requested by Petitioner.
`
`2. The ‘432 Patent Is Not Directed to a “Financial Product or
`Service” Merely Because Its Specification Indicates That “to
`increase security in e-commerce” and/or Merely Because The
`Specification Includes a Few Finance-Related Terms
`
`14
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`Apparently recognizing the lack of nexus between the challenged claims and
`
`a “financial product or service,” Petitioner turns to citing a portion of the ’432
`
`Patent’s specification in an attempt to show that the ‘432 Patent contemplates some
`
`relationship to a financial activity.
`
`Petitioner does not, however, assert that the specification in any way limits or
`
`guides the scope of the challenged claims. Therefore, as a threshold matter, its
`
`approach is irrelevant. As the Board explained in denying institution in J.P. Morgan
`
`Chase, if the claims “have general utility not limited or specific to any application”
`
`and the specification does not limit “the invention to the financial services sector,”
`
`the patent is not a CBM Patent. J. P. Morgan Chase, at 11-12.
`
`The claims are applicable generally to electronic transactions of all types
`
`which are secure, and are not particularly limited to financial services. See id. at 11,
`
`where the Board decided: “The claims of the ʼ574 patent describe methods for
`
`implementing portions of the entire process of using public key encryption to
`
`certify secure electronic communications. The claims, therefore, have general
`
`utility not limited or specific to any application.” (emphasis added). Further, the
`
`Board confirmed that “[w]e agree with Patent Owner’s explanation that electronic
`
`transactions… are not specific to financial transactions and cover various types
`
`of transactions separate from financial transactions.” (emphasis added). Id.
`
`15
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`The Board determined that an authentication over the online network is not
`
`a CBM patent. See id. at 3, 12 (“The ’574 patent relates to public key encryption
`
`(PKE), which is used for securing and authenticating transmissions over
`
`unsecure networks.”… “We are not persuaded by Petitioner’s arguments that
`
`the ’574 patent is a CBM patent, as defined by the AIA and, thus, we do not institute
`
`a CBM patent review of the challenged claims.”) (emphasis added).
`
`Turning to Petitioner’s specific argument, it contends that “[t]he ’432 Patent’s
`
`specification …[has] examples of the invention being used in the context of financial
`
`services, stating e.g., that ‘[e]xamples of Central-Entity are banks, credit card issuing
`
`companies or intermediary service companies” (emphasis added). (Petition at 11).
`
`However,
`
`the Board determined,
`
`for example, clearing houses (i.e.,
`
`intermediary service companies) are not necessarily related to financial services. See
`
`J.P. Morgan Chase, at 8.
`
`The widespread use of authenticating a user
`
`in electronic financial
`
`transactions is immaterial and comparable to asserting that a patent on a stapler
`
`would qualify as a CBM patent because most financial service firms use staplers to
`
`collate financial documents. The claimed method can generally be used to secure or
`
`authenticate an online user by any website related to any industry. For example, the
`
`claims of ‘432 Patent could read on the situation to authenticate voters in an online
`
`election or authenticate students submitting term papers in online academic settings.
`16
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`The authentication system and method of the ‘432 Patent is applicable to any
`
`online business for authentication of users as any other authentication systems and
`
`methods (UserID/password or biometrics, etc.) are. If it is incorrectly assumed that
`
`the authentication system and method of the ‘432 Patent are a financial product or
`
`service, then it would make the definition of financial products and services so broad
`
`such that all other authentication systems and methods would fall in a financial
`
`product and service under AIA § 18(d)(1).
`
`Petition further contends that “the specification also explains, the claims
`
`pertain to ‘transactions to increase security in e-commerce,’ and ‘for centralized
`
`identification and authentication of users’ using ‘personal or financial
`
`information’” (emphasis added). (Petition at 12). As already discussed above, (1)
`
`electronic transactions are not specific to financial transactions (see J.P. Morgan
`
`Chase, at 11); (2) authentication of users is not a CBM patent (see id. at 3, 12); and
`
`(3) the specification does not particularly limit the claimed method to the financial
`
`services sector (see id. at 12).
`
`Petitioner’s argument fails to carry its burden to show any link between the
`
`specification, let alone the claims, and a “financial product or service.” As the Board
`
`has recognized, the breadth of what constitutes a CBM Patent “has limits and does
`
`not cover every method that might be used in a way that
`
`is incidental or
`
`complementary to a financial activity.” (emphasis original). Id. at 6. See also 157
`17
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`Cong. Rec. S5441 (daily ed. Sept. 8, 2011) (statement of Sen. Leahy) (stating that
`
`the definition of a CBM patent is not intended to cover “technologies common in
`
`business environments across sectors and that have no particular relation to the
`
`financial services sector, such as computers, communications networks, and
`
`business software”).
`
`The Board has routinely denied institution of CBM where a patent’s claims
`
`do not relate to a financial service, and the patent’s specification discusses but does
`
`not limit the claims to such services. For example, in J.P. Morgan Chase, the Board
`
`refused to institute a CBMR of a patent that related to public key encryption used
`
`for securing and authenticating transmissions over unsecure networks. Paper No. 11
`
`at 2-3. The petitioner in the J.P. Morgan Chase, a bank, alleged that the challenged
`
`patent constituted a CBM Patent because, among other reasons, (1) the specification
`
`discloses the claimed technology being used by commercial entities, escrow
`
`agencies, clearing houses, and electronic notaries (id. at 7-8), and (2) the claimed
`
`technology was “used in nearly all electronic financial transactions” and was
`
`involved in “nearly all worldwide electronic credit card transactions.” Id. at 9. The
`
`Board rejected these arguments, finding that because the claims “have general utility
`
`not limited or specific to any application” and the specification did not limit “the
`
`invention to the financial services sector,” the patent was not a CBM Patent. Id. at
`
`11-12.
`
`18
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`Another example is the Board’s decision denying a CBMR in ServiceNow,
`
`Inc. v. BMC Software, Inc., CBM2015-00107, Paper No. 12 (PTAB Sept. 11, 2015)
`
`(hereinafter “BMC Software”). In BMC Software, the claims were directed to a
`
`method for fault analysis but did not recite any step that involved a financial activity.
`
`See id. at 10. The petitioner explained that the claimed subject matter was embodied
`
`in the specification with respect to a network of automatic teller machines (“ATMs”).
`
`See id. at 9. The Board, however, denied institution because the claims were not
`
`“tied specifically to a financial product or service,” and while the claims
`
`encompassed the ATM embodiment of the specification they did not recite a
`
`limitation specific to ATMs. Id. at 10.
`
`Similarly, in Hewlett-Packard, the Board denied institution for a patent
`
`claiming a system for monitoring conversations in a web service even though the
`
`patent specification expressly described an embodiment in which the conversations
`
`included “information regarding transactions, such as the amount to be charged and
`
`credit card charge authorizations.” Paper No. 10 at 9, 10, 16-18. The Board explained
`
`that it is insufficient to “show[] that the claimed system could be used in a financial
`
`product or service” and that “the absence of any finance-related limitation in the
`
`claims is the primary driver of our determination.” Id. at 17-18 (emphasis added).
`
`Still further , in Par Pharm., Inc. v. Jazz Pharm., Inc., CBM2014-00149,
`
`Paper No. 12 at 13-14 (PTAB Jan. 13, 2015) (hereinafter “Par Pharm”), the Board
`19
`
`
`
`CBM2016-00063
`U.S. Patent No. 8,266,432
`denied institution even though the claimed method related to a specific embodiment
`
`including the step of verifying a patient’s ability to pay. The claimed invention set
`
`forth a method of distributing a prescription drug. See id. at 10. The specification
`
`included figures relating to the claimed method that set forth steps of verifying
`
`insurance coverage and the patient’s ability to pay. See id. at 5, 7, 13. The Board
`
`nonetheless denied institution because the claimed steps did not “recite or require
`
`verifying insurance coverage or a patient’s ability to pay” as described in the
`
`corresponding embodiment. Id. at 12-13.
`
`Like in BMC Software, J.P. Morgan Chase, Hewlett-Packard, and Par
`
`Pharm., the claims of the ’432 Patent recite a method that is of “general utility”
`
`without a specific tie to a financial application. Indeed, the claimed invention is
`
`equally applicable to a personal, governmental, or any other type of business as it is
`
`applicable to the website of a financial institution. Accordingly, Patent Owner
`
`respectfully submits that Petitioner’s argument that the ’432 Patent is a CBM Patent
`
`should be rejected.
`
`The Board has repeatedly held that the proper focus of the CBM Patent inquiry
`
`should be on the patent claims rather than the specification. See, e.g., Roxa