throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`——————
`
`ALARM.COM INC.
`Petitioner
`
`v.
`
`VIVINT, INC.
`Patent Owner
`
`——————
`
`Case IPR2015-02004
`Patent 6,147,601
`
`——————
`
`PETITIONER’S REPLY BRIEF CONCERNING PATENT OWNER’S
`REQUEST FOR CERTIFICATE OF CORRECTION
`
`
`
`
`
`Mail Stop PATENT BOARD
`Patent Trial and Appeal Board
`US Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`
`

`
`Case IPR2015-02004 of
`U.S. Patent No. 6,147,601
`
`By written order of the Patent Trial and Appeal Board, entered on January
`
`28, 2016, Petitioner Alarm.com Inc. (“Alarm.com”) hereby respectfully submits
`
`this reply brief addressing the Request for Certificate of Correction filed by Patent
`
`Owner Vivint, Inc. (“Vivint”) as to U.S. Patent No. 6,147,601 (the “’601 Patent” or
`
`“Patent”), filed December 17, 2015, and attached to Vivint’s January 8, 2016
`
`Preliminary Response to Alarm.com’s Petition for Inter Partes Review (“IPR”),
`
`Paper 1, in Case IPR2015-02004 (“Petition”).
`
`Petitioner Alarm.com respectfully submits this reply brief to address:
`
`(1) whether Vivint’s proposed change to the ’601 Patent is properly characterized
`
`as a correction under 35 U.S.C. § 255, (2) why Petitioner could not discern the
`
`correction unassisted and (3) the impact of this proposed change on Alarm.com’s
`
`Petition—namely, whether the prior art Alarm.com cited in its Petition discloses
`
`the proposed changed claim limitation.
`
`I.
`
`Petitioner’s Views on Vivint’s Proposed Correction and Reasons
`Why Petitioner Could Not Discern the Correction Unassisted
`
`Vivint proposes one change to claim 39 of the ’601 Patent, changing “which
`
`said normal status” to “which a normal status.”
`
`Claim
`
`Vivint’s Proposed Corrected Claim Language
`
`39 A system according to claim 38, wherein said outgoing
`exception message comprises exception information and
`identification information concerning said piece of remote
`equipment to which said normal status which a normal
`
`Dependent
`Claims
`Affected
`none
`
`1
`
`

`
`Case IPR2015-02004 of
`U.S. Patent No. 6,147,601
`
`Claim
`
`Vivint’s Proposed Corrected Claim Language
`
`Dependent
`Claims
`Affected
`
`status message pertains.
`
`Petitioner does not agree that Vivint’s proposed change to claim 39
`
`constitutes an allowable correction under 35 U.S.C. § 255. Under that statute,
`
`corrections are permitted only for “a mistake of a clerical or typographical nature”
`
`or “a mistake . . . of minor character.” The proposed change does not meet the
`
`requirements for either of these two categories of corrections.
`
`First, the change does not constitute a correction, because even assuming the
`
`change is meant to correct a clerical or typographical error, it is not “clearly
`
`evident from the specification, drawings, and prosecution history how the error
`
`should appropriately be corrected.” Superior Fireplace Co. v. Majestic Prods. Co.,
`
`270 F.3d 1358, 1373 (Fed. Cir. 2001).
`
` One defect in claim 39 as issued is that it lacks an antecedent basis for the
`
`element “to which said normal status message pertains.” Like claim 39, neither of
`
`the claims from which claim 39 depends (claims 22 and 38) refers to a normal
`
`status message; instead, each refers to an exception message that is “indicative of
`
`the exception condition.”
`
`A second difficulty with claim 39—both as issued and as revised by
`
`Vivint—is that it supposes that the server could receive contradictory messages—
`
`specifically, an “exception message” (claims 22 and 38 and the preceding language
`
`2
`
`

`
`Case IPR2015-02004 of
`U.S. Patent No. 6,147,601
`
`of claim 39) and a “normal status message” (dependent claim 39)—pertaining to
`
`the same piece of remote equipment at the same time. An “exception condition,”
`
`according to the Patent, exists “whenever a piece of equipment operates outside its
`
`preferred parameters.” Ex. 1001 at 3:46-47. In other words, the equipment is not
`
`operating normally. By contrast, the Patent describes the use of a status message
`
`to indicate that a piece of equipment is “okay.” See Ex. 1001 at 4:60-63. In
`
`addition, the Patent expressly teaches that the preferred embodiment differentiates
`
`between a status message and an exception message using the first digit of the
`
`multi-digit code sent from a device to the message delivery system, further
`
`reinforcing the mutually exclusive nature of the two conditions. See Ex. 1001 at
`
`5:24-27. Vivint’s proposed correction does not follow from or correspond to the
`
`Patent’s description of the invention. Further, it does not resolve the defect in
`
`claim 39, rendering it improbable.
`
`A more probable correction to claim 39 would change “said normal status
`
`message” to “said exception condition,” resolving the contradiction explained
`
`above. However, there are other possible ways to correct claim 39, including,
`
`making it depend from claim 31, instead of claim 38, since claim 31 requires that
`
`the server generate exception messages when the server has not received a normal
`
`status message for a particular piece of remote equipment “within a predetermined
`
`period of time.” However, because nothing in the Patent or its prosecution history
`
`3
`
`

`
`indicates how the error should be corrected and because there is no clearly evident
`
`correction, Vivint’s proposed change cannot be an allowable correction under
`
`Case IPR2015-02004 of
`U.S. Patent No. 6,147,601
`
`Section 255.
`
`Second, Vivint’s proposed change is not of a “minor character” because it
`
`seeks to broaden an element from referring to a specific normal status message (if
`
`an antecedent could be found) to any normal status message, thereby substantively
`
`altering the scope of the claim. See id. at 1375 (“A mistake that, if corrected,
`
`would broaden the scope of a claim must thus be viewed as highly important and
`
`thus cannot be a mistake of ‘minor character.’”); Manual of Patent Examining and
`
`Procedure (MPEP) § 1480.01 (9th Ed. Rev. Nov. 2013) (“A mistake is not
`
`considered to be of the ‘minor’ character . . . if the requested change would
`
`materially affect the scope or meaning of the patent.”).
`
`In addition, because Vivint’s proposed correction, as explained above, is
`
`contradictory and because there are multiple ways to fix the defect in claim 39,
`
`reexamination—rather than correction—would be required to determine the correct
`
`change to claim 39, if any. See 35 U.S.C. § 255 (correction proper only if “[it]
`
`does not involve such changes as would require . . . re-examination”).
`
`Petitioner could not discern the proposed correction in advance because,
`
`while it was apparent the claim contained a mistake—specifically, the lack of
`
`antecedent basis—there are a number of ways the claim could have been corrected
`
`4
`
`

`
`Case IPR2015-02004 of
`U.S. Patent No. 6,147,601
`
`(as discussed above), which were equally or more consistent with the rest of the
`
`claims and the Patent. Furthermore, the prosecution history is silent on the issue,
`
`and therefore there would be no way for the public—including Petitioner—to
`
`know which of these possible changes reflects the intended scope of the Patent. See
`
`Superior Fireplace, 270 F.3d at 1371 (“It would be inconsistent with [Congress’s
`
`objective] to interpret § 255 to allow a patentee to broaden a claim due to the
`
`correction of a clerical or typographical mistake that the public could not discern
`
`from the public file and for which the public therefore had no effective notice.”).
`
`II. Assessment of Effect of Proposed Correction on Petition
`
`
`
`Petitioner’s Petition is not affected by the proposed correction.
`
`Although Petitioner believes claim 39 to be of indefinite scope and that Vivint’s
`
`proposed change does not constitute a correction, the Petition nonetheless
`
`identified where in the cited prior art disclosed a normal status message pertaining
`
`to remote equipment was disclosed. See claim chart for claim 39 at p. 36 (cross-
`
`referencing claim chart for claim 5 at p. 26 (citing Ex. 1003.0110 (“The No Alarm
`
`stage is the stage in which a status channel is in its normal or a value channel (or
`
`any derivative channel types) is within its alarm limits (and the channel has been
`
`reset since any previous alarm).”))).
`
`5
`
`
`
`

`
`Case IPR2015-02004 of
`U.S. Patent No. 6,147,601
`
`Respectfully submitted,
`
`/William H. Mandir/
`William H. Mandir
`Registration No. 32,156
`
`BACK-UP COUNSEL
`Roger G. Brooks
`(rgbrooks@cravath.com)
`Teena-Ann V. Sankoorikal
`(tsankoor@cravath.com)
`Cravath, Swaine & Moore LLP
`825 Eighth Avenue
`New York, NY 10019
`T: 212-474-1000; F: 212-474-3700
`Pro Hac Vice motions pending
`
`
`
`
`
`
`
`Dated: February 3, 2016
`
`
`
`
`
`
`
`
`
`LEAD COUNSEL
`William H. Mandir (Reg. No. 32,156)
`(wmandir@sughrue.com)
`BACK-UP COUNSEL
`Brian K. Shelton (Reg. No. 50,245)
`(bshelton@sughrue.com)
`Sughrue Mion PLLC
`2100 Pennsylvania Ave, NW
`Washington, D.C. 20037
`T: 202-293-7060; F: 202-293-7068
`
`
`
`
`
`
`
`6
`
`

`
`Case IPR2015-02004 of
`U.S. Patent No. 6,147,601
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that a copy of the attached Petitioner's Reply Brief
`
`Concerning Patent Owner's Request for Certificate of Correction was sent via
`electronic mail on February 3, 2016 to the following:
`
`Robert G. Sterne (rsterne-PTAB@skgf.com)
`Jason D. Eisenberg (jasone-PTAB@skgf.com)
`PTAB@skgf.com
`STERNE, KESSLER, GOLDSTEIN & FOX
`1100 New York Avenue, N.W.
`Washington, DC 20005
`Counsel of Record for the Patent Owner in this proceeding
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`By: /s/ Brian K. Shelton
`Brian K. Shelton
`Registration No. 50,245
`Backup Counsel for Petitioner
`
`7
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Dated: February 3, 2016

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