throbber

`Paper No. 36
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`CALLIDUS SOFTWARE INC.
`Petitioner
`
`v.
`
`VERSATA DEVELOPMENT GROUP, INC.
`Patent Owner
`
`AND
`
`VERSATA SOFTWARE, INC.
`Real Party-In-Interest
`
`____________
`
`Case CBM2013-00052
`Patent 7,904,326
`____________
`
`Filed: August 22, 2014
`
`
`PETITIONER’S REPLY TO PATENT OWNER RESPONSE
`
`
`
`
`
`
`
`
`
`
`

`

`
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`TABLE OF CONTENTS
`
`Page No.
`
`I. 
`II. 
`
`INTRODUCTION ........................................................................................... 1 
`CLAIM CONSTRUCTION ............................................................................ 2 
`A. ..... PO’s Proposed Construction of “Denormalizing” and “Join” Are
`Not Supported ........................................................................................ 2 
`B. ..... Even PO’s Tortured Claim Constructions Do Not Save Its Claims
`From Abstractness ................................................................................. 4 
`III.  CLAIM 1 IS DIRECTED TO AN ABSTRACT IDEA .................................. 5 
`IV.  THE REMAINDER OF CLAIM 1 DOES NOT TRANSFORM THE
`ABSTRACT IDEA INTO A PATENT-ELIGIBLE CLAIM ......................... 9 
`V.  DEPENDENT CLAIMS 2-22 ARE DIRECTED TO NON-PATENTABLE
`SUBJECT MATTER ..................................................................................... 12 
`VI.  PETITIONER WAS NOT BARRED FROM FILING ITS PETITION ....... 12 
`VII.  CONCLUSION .............................................................................................. 15 
`
`
`
`i
`
`
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`CASES
`
`Alice Corp. Pty. Ltd. v. CLS Bank Int’l,
`134 S. Ct. 2347, 110 U.S.P.Q.2d 1976 (2014) ............................................passim
`
`Bancorp Servs., L.L.C. v. Sun Life Assur. Co. of Canada (U.S.),
`687 F.3d 1266 (Fed. Cir. 2012) ...................................................................... 6, 10
`
`Bilski v. Kappos,
`130 S. Ct. 3218 (2010). ................................................................................passim
`
`Chevron U.S.A. v. Natural Res. Def. Council,
`104 S. Ct. 2778, 467 U.S. 837 (1984) ................................................................. 13
`
`CyberSource Corp v Retail Decisions Inc.,
`654 F.3d 1366, 99 U.S.P.Q.2d 1690 (Fed. Cir. 2011) .................................... 6, 11
`
`Ethicon Inc. v. Quigg,
`849 F.2d 1422 (Fed. Cir. 1988) .......................................................................... 13
`
`Princess Cruises, Inc. v. United States,
`201 F.3d 1352 (Fed. Cir. 2000) .......................................................................... 13
`
`STATUTES
`
`35 U.S.C. § 101 .................................................................................................passim
`
`35 U.S.C. § 321(a) ................................................................................................... 13
`
`35 U.S.C. § 321 (b) .................................................................................................. 13
`
`35 U.S.C. § 325(a)(1) ..................................................................................... 12, 13, 9
`
`35 U.S.C. § 325(a)(3) ............................................................................................... 14
`
`AIA § 18(a)(1)(B) .................................................................................................... 13
`
`AIA § 18(a)(1)(C)(i) and (ii) .................................................................................... 13
`
`AIA §§ 42.300 .......................................................................................................... 12
`
`
`
`ii
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`AIA§ 18(a)(1) .................................................................................................... 12, 13
`
`REGULATIONS
`
`37 C.F.R. § 42.23 ................................................................................................... 1, 3
`
`37 C.F.R. § 42.201 ................................................................................................... 12
`
`37 C.F.R. § 42.300(a). 37 ................................................................................... 12, 13
`
`37 C.F.R. §§ 42.300 et seq. ...................................................................................... 12
`
`OTHER AUTHORITIES
`
`157 Cong. Rec. S952 (daily ed. Feb. 28, 2011) ......................................................... 9
`
`
`
`iii
`
`

`

`I.
`
`INTRODUCTION
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`The Board instituted this CBM Review because it found that “Petitioner has
`
`demonstrated that it is more likely than not that claims 1-22 are unpatentable
`
`under 35 U.S.C. § 101 as being directed to non-statutory subject matter.”
`
`Institution Decision, Paper No. 21 at 19 (P.T.A.B. Mar. 4, 2014) (“ID”). Nothing
`
`in the Patent Owner’s Response (“POR”) changes the reasoned and correct
`
`conclusions in the Institution Decision.
`
`Having failed to move to amend claims, POR now attempts to effect,
`
`through claim construction, what it should have done through claim amendment.
`
`In so doing, Patent Owner (“PO”) tacitly concedes the abstractness of its claims.
`
`PO proposes claim constructions that do not even begin to conform to the broadest
`
`reasonable interpretation (“BRI”) standard, and improperly imports limitations
`
`from the specification. Having foregone a motion to amend, PO cannot now
`
`contort the claim construction process to achieve claim amendment.
`
`Alice reaffirmed that claims directed to abstract ideas, without limitations
`
`sufficient to tie them down, are patent ineligible. Rather than address this
`
`standard, PO concocts its own misguided tests for patent-eligibility that have no
`
`basis in precedent and, in fact, run afoul of the holdings in Alice, Bilski, Benson,
`
`Flook, Bancorp, and CyberSource.
`
`
`
`1
`
`

`

`II. CLAIM CONSTRUCTION
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`Neither party has argued that claim construction is necessary to determine if
`
`the challenged claims are directed to non-statutory subject matter, and the Board
`
`has already concluded that it is not. ID 10. Nonetheless, PO argues that
`
`“denormalizing” and “joining” (in dependent claims 2, 9, 11, 12, and 17) are not
`
`conventional database operations, but instead require “specific programming”
`
`according to “specified criteria.” PO offers no fact or expert testimony to support
`
`its assertion and even its attorney argument never identifies what “specific”
`
`programming or criteria are required.1 PO’s construction is not supported by the
`
`claim language, the specification, or even its own citations. Moreover, PO’s
`
`proposed construction, even if adopted, is entirely circular and cannot rescue its
`
`challenged dependent claims from abstractness.
`
`A.
`
`PO’s Proposed Construction of “Denormalizing” and “Join” Are
`Not Supported
`
`The POR concedes that “denormalizing” was known to ordinarily skilled
`
`artisans, but disputes that it was a conventional database operation. POR 8. PO
`
`argues, without support, that “denormalizing” and “join” require specific, complex
`
`programming according to particular criteria and seeks to inject those terms into
`
`its proposed construction.
`
`
`1 PO does not challenge Petitioner’s “credential information” construction. POR 5.
`
`
`
`2
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`But nothing in the patent’s specification or claims explains how to perform
`
`“denormalizing” or “joining,” or suggests that those operations require any
`
`programming, let alone complex programming.2 Indeed, the fact that the ‘326
`
`patent provides no guidance regarding how to denormalize data or join database
`
`tables suggests that those operations were routine at the time of filing.
`
`While the POR is filled with conjecture regarding what is required to
`
`denormalize data or join database tables, PO offers no declarant testimony, expert
`
`or otherwise, to support its constructions. And none of PO’s citations say or
`
`suggest that complex programming was required to perform “denormalizing” or
`
`“joining.”3 Instead, PO’s citations suggest that “denormalizing” was a
`
`conventional database operation at the time of filing. For example, Exhibit 2017
`
`expressly notes four commonly-adopted denormalization operations in the art:
`
`In this Section, we discuss denormalization patterns that have been
`commonly adopted by experienced database designers. . . . we
`identified and classified four prevalent strategies for denormalization
`
`
`2 For every mention of the term “denormalizing,” see Exh. 1001, 2:15-22, 2:51-58,
`
`11:33-36, 13:38-47, 14:28-31, 14:49-15:4; see claims 2, 9, 11, 12, 17; see also
`
`Fig. 5, nowhere is complex programming (or any programming) indicated.
`
`3 PO’s argument that the lack of any discussion of “denormalizing” in Exh. 2019
`
`implies that complex programming was required is pure conjecture. POR 9.
`
`
`
`3
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`in Figure 4. They are collapsing tables, splitting a table, adding
`redundant columns and adding derived columns.
`
`Exh. 2017 at 4. Nothing in Exhibit 2017 suggests the need for complex
`
`programming. Likewise, both Exhibits 2015 and 2019 suggest that a “join” was a
`
`commonly-used database operation at the time.4 Thus, PO’s proffered claim
`
`construction is unsupported.
`
`B.
`
`Even PO’s Tortured Claim Constructions Do Not Save Its Claims
`From Abstractness
`
`Even if PO’s proposed construction for “denormalizing” and “joining” were
`
`adopted, it would not save claims 2, 9, 11, 12, and 17 from abstractness. As
`
`discussed above, the ‘326 patent does not disclose any way, let alone a particular
`
`way or algorithm, for implementing “denormalizing” or “joining” functionality.
`
`Thus, PO’s proposed construction is entirely circular. Much like trying to
`
`rehabilitate the abstract method by reciting “the non-abstract method of claim 1,”
`
`simply calling something “specific” or “complex” does not make it so. Merely
`
`adding the words “specific programming” and “specified criteria” to
`
`
`4 Exhibit 2015 at 262 (“In SQL, a JOIN TABLE allows users to specify a table
`
`resulting from a join operation in the FROM clause of a query.”); Exh. 2019 at 964
`
`(“Today, MySQL Server and many other modern database systems offer a wide
`
`range of outer join types.”).
`
`
`
`4
`
`

`

`“denormalizing” and “joining” without actually requiring or disclosing any
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`specific programming or specified criteria does nothing to tie down the abstract
`
`idea. Thus, construction of these terms is unnecessary to determine if the
`
`challenged claims are directed to non-statutory subject matter.
`
`III. CLAIM 1 IS DIRECTED TO AN ABSTRACT IDEA
`The Supreme Court in Alice was very clear about the standard that should
`
`be used to determine patent eligibility under § 101: “First, we determine whether
`
`the claims at issue are directed to one of those patent-ineligible concepts. . . . If
`
`so, we then ask, “[w]hat else is there in the claims before us?” Alice Corp. Pty.
`
`Ltd. v. CLS Bank Int’l, 134 S. Ct. 2347, 2355 (2014) (quotations omitted). The
`
`Institution Decision is consistent with Alice, which reaffirms the patent
`
`ineligibility of the present claims.
`
`Contrary to the clear authority of Alice and its predecessors, PO argues that
`
`claims are invalid under § 101 only where Petitioner can prove the claims are
`
`directed to a “fundamental economic practice.” See POR 13-14. Nothing in
`
`Alice, Mayo, Bilski, Benson, or Flook limits the categories of patent ineligible
`
`abstract ideas to the specific examples of abstract ideas found in those cases, nor
`
`those made up by PO by a cramped misreading of Alice and Bilski.
`
`In fact, the Supreme Court roundly rejected exactly this line of argument in
`
`Alice: “petitioner contends that the abstract-ideas category is confined to
`
`
`
`5
`
`

`

`preexisting, fundamental truths that exist in principle apart from any human
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`action. . . . Bilski belies petitioner’s assertion.” Alice at 2356 (emphasis added,
`
`quotations and modification omitted). PO does not even attempt to explain how
`
`generating compensation data using validated transactions and validated
`
`distributors’ credentials is different in kind than “managing a stable value
`
`protected life insurance policy” (Bancorp at 1280-81), a “fraud detection method”
`
`(Cybersource at 1376), “risk hedging” (Bilski at 1321), or “intermediated
`
`settlement” (Alice at 2355). In fact, it is not. PO provides no explanation for why
`
`an abstract idea regarding a mundane or ordinary economic practice should be
`
`more deserving of patent protection (and thus, patent eligibility) than an abstract
`
`idea directed to a “fundamental economic practice.” Indeed, to state the premise
`
`is to undermine it. The only proper inquiry is whether the claims are directed to
`
`an abstract idea;5 PO’s attempts at misdirection should be ignored.6
`
`
`5 Both Alice and the Preliminary Examiner Guidelines agree that a fundamental
`
`economic practice is one of several examples of an unpatentable abstract idea, but
`
`that abstract ideas are not limited to a particular category. Exh. 2018 at 2-3.
`
`6 Even if the “fundamental nature” of an economic practice were relevant to the
`
`§101 analysis (which it is not), PO itself offers no evidence to rebut the only
`
`
`
`6
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`Next, PO argues that because the claimed method is limited by its
`
`application to a computer, there is no preemption and, thus, the claims are patent
`
`eligible. POR 14. PO mistakenly adopts preemption as a test for patent elibility.
`
`However, as Alice makes clear, pre-emption is a policy concern justifying the
`
`limits on patent eligibility, but is not itself a test for patentability. See Alice at 2354
`
`(“Laws of nature, natural phenomena, and abstract ideas are not patentable. . . .
`
`We have described the concern that drives this exclusionary principle as one of
`
`pre-emption.”). In any event, PO’s preemption argument based on the use of a
`
`computer is flatly contradicted by Alice and Cybersource, which hold that the
`
`ordinary use of a computer does not make an abstract idea patent-eligible. Indeed,
`
`if that were the case, no computer-implemented business method would ever be
`
`patent ineligible so long as they may be performed by hand or in the human mind.
`
`That is not the law. See infra Section IV.
`
`Moreover, Petitioner’s unrebutted declarant testimony demonstrates that
`
`each of the recited functions of the challenged claims could be performed by hand
`
`or in the human mind.
`
`PO argues that Petitioner has not met its burden of proof for an “inability to
`
`
`evidence of record, which shows the importance of validating transactions and
`
`distributors. E.g., Exh. 1003 ¶¶16-17, 21.
`
`
`
`7
`
`

`

`select one abstract idea upon which to rest its theory of invalidity” is nit-picking
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`nonsense. POR 15-18. The alleged six different abstract ideas are only slightly
`
`different articulations of the same abstract idea: generating compensation data
`
`using validated transactions and validated distributors’ credentials. ID 12-13; Pet.
`
`22. Notably, nowhere does PO argue that claim 1 is not directed to any one of the
`
`six purported abstract ideas. In fact, PO admits that claim 1 is directed to the
`
`abstract idea alleged by Petitioner:
`
`The ‘326 patent describes and claims a specific method for
`performing transaction processing in an efficient manner which
`minimizes
`the use of computing resources
`in a
`traditionally
`computationally-expensive process: the validation of distributor
`credentials and transactions to ensure proper compensation of a
`distributor.
`
`POR 2. Neither Alice nor Bilski state that an abstract idea needs to be distilled to a
`
`single set of magic words, or that a challenge must chant a particular incantation
`
`for a claim to be unpatentable. The Supreme Court in both Alice and Bilski spoke
`
`of the abstract idea much less consistently than Petitioner, and had no problem
`
`still invalidating the abstract claims. E.g. Alice at 2352 (“intermediated
`
`settlement”), 2352 (“computerized scheme for mitigating ‘settlement risk’”), 2353
`
`(“method for exchanging obligations”), 2356 (“exchanging financial obligations
`
`between two parties using a third-party intermediary to mitigate settlement risk”);
`
`
`
`8
`
`

`

`and e.g. Bilski at 3229 (“hedging risk”), 3231 (“hedging, or protecting against
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`risk”), 3231 (“risk hedging”), 3231 (“hedging, described in claim 1 and reduced to
`
`a mathematical formula in claim 4”), 3231 (“hedging risk in the energy market”).
`
`PO’s argument that no court has invalidated a claim having multiple abstract ideas
`
`(POR 18), even if true, is entirely irrelevant: multiple abstract ideas in a claim
`
`would be no less abstract than a single abstract idea. Six times zero is still zero.
`
`IV. THE REMAINDER OF CLAIM 1 DOES NOT TRANSFORM THE
`ABSTRACT IDEA INTO A PATENT-ELIGIBLE CLAIM
`
`Even while stating that “PO does not suggest that the mere recitation of a
`
`computer in a claim is sufficient to qualify as a statutory subject matter under
`
`§ 101” (POR 26), PO’s only argument that part two of the Alice framework is not
`
`met for claim 1 rests on nothing more than generic computer functionality. POR
`
`18-22. PO emphasizes the recitation in claim 1 of “in the computer system” and
`
`“stored in a form that can be processed by the computer system,” and argues that
`
`a person cannot, “whether mentally or using pencil and paper,” perform these
`
`limitations. POR 23-24. First, a person could very well enter data into a
`
`computer system, for example by manually keying in such data into a computer,
`
`thus presenting the data computer-readable form. This is “by hand.” Second,
`
`simply storing data into a computer—which data is necessarily in a computer
`
`readable form—is not a meaningful limitation on an abstract claim. Alice at 2359
`
`
`
`9
`
`

`

`(“[T]he relevant question is whether the claims here do more than simply instruct
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`the practitioner to implement the abstract idea of intermediated settlement on a
`
`generic computer. They do not.”).
`
`Even as described by PO, the “processing” recited in “in the computer
`
`system” of claim 1 is entirely generic. POR 20-21; Exh. 1001, 15:31-46. PO only
`
`states that claim 1 requires checking transactions according to validation criteria
`
`before paying the distributor, again “in the computer system.” POR 21. Thus, the
`
`claimed “processing” is not any particular type of functionality imparted by the
`
`computer, just that these checks are done in a computer, rather than not.
`
`PO’s pleas that the specification (e.g. POR 20-21, 28-29) should be
`
`consulted are inappropriate to the § 101 analysis. It is black letter law that the
`
`claims define the scope of patent protection. It simply does not matter if the
`
`“specification of the ‘326 Patent confirms that the invention of the claims is
`
`‘significantly more’ than merely ‘generating compensation data.’” POR 20.
`
`CyberSource and Bancorp are highly relevant to the claims of the ‘326
`
`patent. PO’s statement that “Bancorp is similar [to CyberSource] – the claims, on
`
`their face, did not implicate or even recite a computer” is simply false. POR 26.
`
`In fact, the Federal Circuit invalidated method, system, and computer-readable
`
`medium claims that explicitly recited or required a computer. In Bancorp, one of
`
`the independent claims recited a “computer system for administering an existing
`
`
`
`10
`
`

`

`life insurance policy.” Bancorp at 1271; Exh. 1015, 17:52-55. In Bancorp, the
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`Federal Circuit noted that “particular computing devices” “such as a ‘generator,’ a
`
`‘calculator,’ and ‘digital storage’” were required. Bancorp at 1274. Other
`
`independent claims recited “computer readable media for controlling a computer,”
`
`and were also invalidated. Bancorp at 1271; Exh. 1016, (cl. 18); see also
`
`Exh. 1015, (cls. 18, 63). Likewise, in CyberSource, invalidated independent claim
`
`2 recited “a computer readable medium” that required “execution of the program
`
`instruction by one or more processors of a computer system” where the “computer
`
`system causes that one or more processors to carry out” certain method steps.
`
`CyberSource at 1373-74; Exh. 1017, (cl. 2). The Federal Circuit treated claim 2
`
`no differently than the abstract method of claim 3 that did not recite a computer:
`
`“Here, the incidental use of a computer to perform the mental process of claim 3
`
`does not impose a sufficiently meaningful limit on the claim’s scope.”
`
`CyberSource at 1375. These holdings are consistent with Alice, where the
`
`challenged patents were directed to a “computer-implemented scheme,” and
`
`where each of the method, system, and media claims were held unpatentable as
`
`directed to abstract ideas. Alice at 2360.
`
`Patent Owner argues that the present claims are like those of Diehr (e.g.
`
`POR 19), but the claimed invention of Diehr is wholly different than the claimed
`
`subject matter here. As noted in Alice, “the claims in Diehr were patent eligible
`
`
`
`11
`
`

`

`because they improved an existing technological process, not because they were
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`implemented on a computer.” Alice at 2358. Here, claim 1 takes a process that
`
`can be performed by hand and implements it in some general way on a computer.
`
`Finally, PO does not address, and thus concedes, that claim 1 fails the
`
`machine-or-transformation test. Pet. 36-44. Even after Alice and Bilski, this test
`
`remains an “important clue [or] an investigative tool” to determine whether claims
`
`are patent-eligible under § 101. Bilski v. Kappos 130 S.Ct. at 3227.
`
`V. DEPENDENT CLAIMS 2-22 ARE DIRECTED TO NON-
`PATENTABLE SUBJECT MATTER
`
`PO’s arguments for claims 2, 9, 11, 12, and 17 are premised on a tortured
`
`construction of “denormalizing” and “join/joining.” POR at 29-32. As discussed
`
`in Section II, supra, these constructions are unsupported and, in any event, do not
`
`tie down the abstract idea of the claim. Notably, PO nowhere addressed claims 3-
`
`8, 10, 13-16, and 18-26. Cf Pet. 42-55 with POR 27-32. PO thus concedes that
`
`these are also unpatentable.
`
`VI. PETITIONER WAS NOT BARRED FROM FILING ITS PETITION
`
`As the Board has already held, Petitioner is not estopped from challenging
`
`the claims on the grounds identified in the Petition. ID 5-7; Decision on Request
`
`for Rehearing, Paper No. 27 at 2-6 (April 9, 2014). Petitioner’s second-filed
`
`declaratory judgment (“DJ”) action did not bar Petitioner from filing its Petition.
`
`First, according to 37 C.F.R. §§ 42.300 et seq., 35 U.S.C. § 325(a)(1) does
`
`
`
`12
`
`

`

`not apply to CBM Review. This is because 37 C.F.R. § 42.201—the rule
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`promulgated by the Director of the USPTO to implement 35 U.S.C. § 325(a)(1)—
`
`is explicitly carved out of CBM Review by 37 C.F.R. § 42.300(a). 37 C.F.R.
`
`§§ 42.300; Exh. 1008 at 48691. The Director’s rulemaking that resulted in
`
`37 C.F.R. § 42.300(a) was authorized under AIA § 18(a)(1). See Exh. 1008 at
`
`48680; see also Exh. 2008 at S5428. In that regard, the Director found that the
`
`exceptions set forth in § 42.300(a) were “consistent with section 18(a)(1) of the
`
`AIA.” Exh. 1008 at 48693. The Director’s rulemaking is consistent with the
`
`statutory mandate and entitled to deference.7 See Chevron U.S.A. v. Natural Res.
`
`Def. Council, 467 US 837, 843-44 (1984); see also Ethicon Inc. v. Quigg, 849
`
`F.2d 1422, 1425 (Fed. Cir. 1988).
`
`Contrary to PO’s argument, nothing in AIA § 18 incorporates Chapter 32 in
`
`its entirety for CBM Review. In fact, such incorporation would result in statutory
`
`conflicts with other provisions of Section 18. Compare, e.g. 35 U.S.C. § 321(a)
`
`with AIA § 18(a)(1)(B); compare also 35 U.S.C. § 321 (b) with AIA §
`
`
`7 While the PTAB’s recent decision in SecureBuy tacitly assumed that 35 U.S.C. §
`
`325(a)(1) applies to Section 18 proceedings, the issue was not raised or argued by
`
`either party there. See SecureBuy, LLC v. Cardinalcommerce Corp., CBM2014-
`
`00035, Paper No. 12, 3 (P.T.A.B. Apr. 25, 2014).
`
`
`
`13
`
`

`

`18(a)(1)(C)(i) and (ii). Where an “interpretation directly conflicts with the
`
`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`language of the statute,” it must be rejected. Princess Cruises, Inc. v. United
`
`States, 201 F.3d 1352, 1362-63 (Fed. Cir. 2000).
`
`In addition, as the Board found in its ID (at 5-7) and Decision on Request
`
`for Rehearing, Paper No. 27 (“Rehearing Denial”), Petitioner’s DJ action is
`
`properly treated as something that de jure never existed, leaving the parties as
`
`though the action had never been brought. See Rehearing Denial at 3-6, and
`
`authority cited therein. Petitioner was never in a position to litigate invalidity on
`
`multiple fronts simultaneously; Petitioner’s DJ complaint was filed (but never
`
`served) and dismissed without prejudice by May 2013, more than three months
`
`before Petitioner filed its petition for CBM Review. See Exhs. 2001; 2003.
`
`SecureBuy, the only precedential case addressing § 315(a) or § 325(a), is
`
`distinguishable. There, SecureBuy had filed two separate DJ actions two weeks
`
`before filing its petition for CBM Review, and those actions were still ongoing
`
`long after the petition was filed. Decision Denying Institution of Covered
`
`Business Method Patent Review at 3, SecureBuy, LLC v. Cardinalcommerce
`
`Corp., CBM2014-00035, Paper No. 12, (P.T.A.B. Apr. 25, 2014); see Exhs. 1018
`
`and 1019. The Board’s decision is also consistent with the legislative history that
`
`expressed concern about parallel litigation tactics or “abusive serial challenges to
`
`patents.” Exh. 2006 at S1363 (Sen. Schumer); Exh. 2009 at S952 (Sen. Grassley).
`
`
`
`14
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`None of those concerns are implicated where there has been a voluntary dismissal.
`
`Finally, even if § 325(a) applied here, Petitioner’s second-filed DJ action is
`
`properly characterized as an excepted counterclaim within the meaning of
`
`§325(a). See 35 U.S.C. § 325(a)(3). PO sued Petitioner first in the District of
`
`Delaware. Petitioner’s standing for its second-filed DJ action in California was
`
`explicitly based on PO’s first-filed action.8 Exh. 2001 ¶ 9. PO does not dispute
`
`that Petitioner’s DJ counterclaim action was a mirror image of PO’s earlier filed
`
`patent infringement claim, and both parties understood and agreed that it could not
`
`proceed in parallel. Exh. 1020 at 1; Exh. 1021; Exh. 1022. And once the motion
`
`to transfer was resolved, Petitioner voluntarily dismissed its second filed DJ claim
`
`and added precisely the same DJ claim as a counterclaim to PO’s first filed
`
`Delaware action. Exh. 1023.
`
`VII. CONCLUSION
`
`Because Petitioner has demonstrated the patent ineligibility of each claim
`
`under Alice and its predecessors, under any of the proposed constructions, claims
`
`1-22 of the ‘326 patent should be cancelled.
`
`8 Petitioner’s second-filed DJ counterclaim action was filed for the express purpose
`
`of anchoring venue (in response to Patent Owner’s cross-motion for transfer) until
`
`the Delaware Court (the first-filed action) had an opportunity to rule on the then-
`
`pending motion for transfer. Exh. 1024 at 4, n.1; Exh. 1025.
`
`
`
`15
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`Respectfully Submitted,
`
` /
`
` Deborah E. Fishman /
`Deborah E. Fishman (Reg. No. 48,621)
`Jeffrey A. Miller (Reg. No. 35,287)
`Assad H. Rajani (admitted pro hac vice)
`Michael S. Tonkinson (admitted pro hac vice)
`DICKSTEIN SHAPIRO LLP
`1841 Page Mill Road, Suite 150
`Palo Alto, CA 94304
`Phone: (650) 690-9500
`Fax: (650) 690-9501
`Email: fishmand@dicksteinshapiro.com
` millerj@dicksteinshapiro.com
` rajania@dicksteinshapiro.com
` tonkinsonm@dicksteinshapiro.com
`
`
`Attorneys for Petitioner
`CALLIDUS SOFTWARE INC.
`
`
`16
`
`
`
`Dated: August 22, 2014
`
`
`
`
`
`
`

`

`Petitioner’s Reply to Patent Owner Response
`CBM2013-00052
`
`
`The undersigned certifies that the foregoing PETITIONER’S REPLY TO
`
`
`
`PATENT OWNER RESPONSE and associated Exhibits 1015-1025 were served
`
`on Patent Owner on August 22, 2014, via electronic filing in the Patent Review
`
`Processing System.
`
`
`
`/ Deborah E. Fishman /
`Deborah E. Fishman
`Reg. No. 48,621
`
`
`
`
`
`
`
`
`
`1
`
`

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