throbber

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`—————————————
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`—————————————
`
`LIBERTY MUTUAL INSURANCE CO.
`Petitioner
`
`v.
`
`PROGRESSIVE CASUALTY INSURANCE CO.
`Patent Owner
`
`—————————————
`
`Case CBM2013-00009
`Patent 8,140,358
`
`—————————————
`
`PATENT OWNER’S REPLY IN SUPPORT OF ITS MOTION TO
`EXCLUDE EVIDENCE PURSUANT TO 37 C.F.R. § 42.64(c)
`
`CLI-2148602v3
`
`

`

`Patent Owner Progressive Casualty Ins. Co. (“Progressive”) hereby submits
`
`Case CBM2013-00009
`Patent 8,140,358
`
`
`
`this Reply in support of its Motion to Exclude.
`
`I.
`
`LEGAL STANDARD
`
`37 C.F.R. § 42.304 requires that Liberty’s Petition “specify where each element
`
`of the claim is found in the prior art” and that Liberty “identify[] specific portions of
`
`the evidence that support the challenge.” See 37 C.F.R. § 42.304(b)(4),(5). Progressive
`
`quotes this language on page 2 of its Motion, yet nowhere in Liberty’s Opposition
`
`brief does it ever mention this rule.
`
`Instead, Liberty discusses an NLRB case from 1942, a Tax Court decision from
`
`Nebraska, and an FTC case from 1945, in addressing the admissibility of evidence as a
`
`general proposition. (Opp. at 1.) Then, Liberty cites 37 C.F.R. § 42.5 as “permit[ting]
`
`administrative patent judges wide latitude in administering the proceedings[.]” (Opp. at
`
`1, emphasis added.) And, based on this “wide latitude” under 37 C.F.R. § 42.5,
`
`Liberty concludes that its “evidence is entirely proper, while Progressive’s objections
`
`are baseless.” (Id. at 1-2.)
`
`However, 37 C.F.R. § 42.5 is inapplicable. It only applies to “situation[s] not
`
`specifically covered by this part[.]” 37 C.F.R. 42.5(a). The situation at issue is plainly
`
`“covered” in Part 42 under 37 C.F.R. § 42.304. Liberty’s refusal to address section
`
`42.304 in its brief (and its resort to the inapplicable section 42.5) does not alter the
`
`mandatory requirement that its Petition must specifically identify where each claim
`
`CLI-2148602v3
`
`1
`
`

`

`
`element allegedly appears in each prior art reference.
`
`Case CBM2013-00009
`Patent 8,140,358
`
`On page 2 of its motion, Progressive quoted the requirement under 37 C.F.R. §
`
`42.23(b) that a “reply may only respond to arguments raised in the…patent owner
`
`response.” In addition, Progressive quoted the treatment of this rule in the Office
`
`Patent Trial Practice Guide, which confirms that new evidence in a Reply is
`
`prohibited if it is necessary to make out a prima facie case or could have been presented
`
`in the Petition. (Motion at 2-3; see 77 Fed. Reg. 48,756, 48,767 (Aug. 14, 2012).)
`
`Once again, nowhere in Liberty’s Opposition does it even mention this mandatory
`
`rule or the recitation in the Trial Practice Guide as to how it operates.
`
`Rather, Liberty simply claims that its “prima facie case was complete when [it]
`
`filed its Petition commencing this proceeding” and that to view it any other way
`
`“contradicts both common sense and the Board’s Institution Decision[.]” (Opp. at 2,
`
`4-5.) Not so. The Trial Practice Guide addresses this exact situation of Petitioner
`
`introducing new evidence after a proceeding has commended. It makes clear a reply
`
`that “include[s] new evidence necessary to make out a prima facie case…and
`
`new evidence that could have been presented in a prior filing” indicates that an
`
`improper new issue has been raised. 77 Fed. Reg. at 48,767 (emphasis added).
`
`Indeed, this language would be meaningless if deficiencies in Petitioner’s prima facie
`
`case could not be identified after the Board institutes a proceeding.
`
`CLI-2148602v3
`
`2
`
`

`

`
`II. ARGUMENT
`A.
`
`Liberty’s Reply Introduced New Fuzzy Logic Evidence
`
`Case CBM2013-00009
`Patent 8,140,358
`
`Liberty’s Petition did not allege – or offer any evidence to show – that a
`
`POSITA would understand fuzzy logic. (Motion at 4-5.) Indeed, it argues that there
`
`was “no need” for it to do so, and it was “proper[]” for it to raise for the first time in its
`
`Reply that a POSITA understands fuzzy logic. (See Opp. at 3, 3 n.2.) However, this is
`
`not a deficiency Liberty can cure with its Reply. (See supra at 1-2.) Liberty relied on
`
`Kosaka’s “fuzzy logic” disclosure as the basis for invalidating every element in claim
`
`1. (Motion at 4-5.) It is a damning admission that Liberty is forced to cite only
`
`Rebuttal Declarations to support its claim that a POSITA “would in fact understand
`
`Kosaka’s approach and know how to use it.” (Opp. at 3.) The knowledge and
`
`experience of a POSITA is an element of Liberty’s prima facie obviousness case, yet
`
`there is not a single shred of evidence in Liberty’s Petition as support for the claim
`
`that a POSITA would understand and know how to apply Kosaka.
`
`Instead, Liberty introduces seven new references. (Motion at 5-7.) To defend
`
`this blatantly improper reliance on new art in a Reply, Liberty attempts to transform
`
`the substantive law as to a POSITA’s knowledge of prior art, into a new evidentiary
`
`rule, one which would allow Liberty to introduce any prior art at any time, simply by
`
`claiming that it “would have been known to a POSITA[.]” (Opp. at 4.) This is plainly
`
`not the law, and Liberty’s argument is a smokescreen to cover its improper
`
`CLI-2148602v3
`
`3
`
`

`

`
`introduction of new evidence with its Reply.
`
`Case CBM2013-00009
`Patent 8,140,358
`
`Indeed, Liberty further claims that it is not “combin[ing] these seven references
`
`with Kosaka” because its “prima facie case was complete” when this proceeding was
`
`commenced, and it is doing “nothing more than rebut[ting.]” (Opp. at 4-5.)
`
`However, as demonstrated above, Liberty misapprehends the effect of instituting this
`
`proceeding. (See supra at 1-2.) And, Liberty’s repeated recitation of the word
`
`“rebuttal” does not somehow transform its tardy evidence into a timely submission.
`
`Liberty next offers a straw man argument, claiming that it “defies common
`
`sense” that its Andrews cannot rely on Kosaka’s Figures 10 and 11 in his Reply
`
`Declaration, simply because they “were not specifically called out in the Petition or his
`
`previous declaration.” (Opp. at 6.) What Progressive actually argued was that
`
`Andrews “relied on Figures 10 and 11” to improperly raise a new argument as to “how
`
`fuzzy logic would be used to classify [] input values in a way that could be used by an
`
`insurance expert[.]” (Motion at 8, emphasis added.) This is a new argument based on a
`
`new opinion as to how an “insurance expert” would benefit from “fuzzy logic,” and it
`
`needed to be raised in its Petition if Liberty wanted to rely on it in arguing invalidity.
`
`Liberty raises another straw man argument, claiming that Progressive seeks to
`
`exclude ¶¶ 6 and 8 from the Andrews Reply Declaration because of his “opinions on
`
`‘insurance aspects.’” (Opp. at 8.) However, what Progressive actually argued, as set
`
`forth on the first paragraph on page 9 of its Motion, was that ¶¶ 6 and 8 are improper
`
`CLI-2148602v3
`
`4
`
`

`

`
`because Andrews used references dated after 1996 for what was allegedly known in
`
`Case CBM2013-00009
`Patent 8,140,358
`
`1996. If Liberty wanted to show what was known in 1996, a reference dated 1997 and
`
`1999 would not cut it, even if they had properly been specified in the Petition.
`
`B.
`
`Liberty’s Reply Raised New Fuzzy And Non-Fuzzy Embodiments
`
`Liberty admits that it did not “refer to ‘crisp’ values or ‘defuzzification’ as a
`
`basis for invalidity in the Petition” and that it “relies upon previously-uncited words in
`
`Kosaka” as to the non-fuzzy aspects of Kosaka. (See Opp. at 10 and 12; Motion at
`
`10-14.) Yet, Liberty claims that “there was no reason” for it to raise these arguments
`
`and identify these embodiments until its Reply. (Opp. at 10, emphasis omitted.) The
`
`reason for Liberty to do so is set forth in 37 C.F.R. § 42.304, and the consequence for
`
`it not doing so is set forth in 37 C.F.R. § 42.23, which requires exclusion.
`
`III. CONCLUSION
`Liberty invites error by raising new issues in its Reply. Progressive has not
`
`been afforded any opportunity to offer its own expert declarations to challenge
`
`Liberty’s seven new references, Liberty’s use of the purported defuzzification/crisp
`
`and non-fuzzy disclosures in Kosaka, or the myriad of other new issues identified by
`
`Progressive in its Motion. The AIA did not create a Due Process loop hole, such that
`
`a patentee could be denied an opportunity to substantively respond to an
`
`unpatentability argument with its own evidence. Yet that is exactly what Liberty urges
`
`by arguing that the ‘358 patent should be invalidated based on new issues in its Reply.
`
`CLI-2148602v3
`
`5
`
`

`

`
`
`
`Case CBM2013-00009
`Patent 8,140,358
`
`
`
`
`
`
`
`
`
`
`
`
`
`October 8, 2013
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`By:
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`JONES DAY
`
`/s/Calvin P. Griffith
`Calvin P. Griffith
`Registration No. 34,831
`JONES DAY
`North Point
`901 Lakeside Avenue
`Cleveland, Ohio 44114-1190
`(216) 586-3939
`(216) 579-0212 (Fax)
`Attorney For Patent Owner
`Progressive Casualty Insurance Co.
`
`CLI-2148602v3
`
`6
`
`

`

`CERTIFICATE OF SERVICE
`
`I certify that a copy of the foregoing PATENT OWNER’S REPLY IN
`
`SUPPORT OF ITS MOTION TO EXCLUDE EVIDENCE PURSUANT TO 37
`
`C.F.R. § 42.64(c) was served on October 8, 2013 by causing them to be sent by email
`
`to counsel for Petitioner at the following email addresses:
`
`
`
`
`
`
`
`
`Steven.baughman@ropesgray.com
`Nicole.jantzi@ropesgray.com
`James.myers@ropesgray.com
`LibertyMutualPTABService@ropesgray.com
`
`
`
`
`
`/s/ John V. Biernacki
`John V. Biernacki
`Registration No. 40,511
`JONES DAY
`North Point
`901 Lakeside Avenue
`Cleveland, Ohio 44114-1190
`Attorney For Patent Owner
`Progressive Casualty Insurance Co.
`
`
`
`

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