throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`——————
`
`ALARM.COM INC.
`Petitioner
`
`v.
`
`VIVINT, INC.
`Patent Owner
`
`——————
`
`Case IPR2016-00116
`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
`
`

`
`Petitioner Alarm.com respectfully submits this reply to address: (1) whether
`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`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 the Petition—
`
`namely, whether the prior art in the Petition discloses the proposed change.
`
`I.
`
`Petitioner’s Views on Vivint’s Proposed Correction and Reasons
`Why Petitioner Could Not Discern the Correction Unassisted
`
`Vivint, Inc. (“Vivint”) seeks to change “which said normal status” to “which
`
`a normal status” in claim 39 of the 6,147,601 (the “’601 Patent” or “Patent”).
`
`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.” Neither ground applies here.
`
`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 the preceding
`
`language in claim 39, neither of the claims from which claim 39 depends (claims
`
`
`
`1
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`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
`
`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. Also, 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 results in claim 39 reciting the contradictory
`
`conditions of an exception condition and a normal condition.
`
`Petitioner prepared its Petition assuming a more probable correction that
`
`would change “said normal status message” to “said exception condition,”
`
`
`
`2
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`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 piece of remote
`
`equipment “within a predetermined period of time.” Because there is no clearly
`
`evident correction, Vivint’s proposed change is not allowable under § 255.
`
`Second, Vivint’s proposed change is not of a “minor character” because it
`
`would work a substantive change to the claim, as explained above, and require
`
`Petitioner to alter the basis on which it seeks review for claim 39, as explained in
`
`Part II, infra. See Superior Fireplace, 270 F.3d at 1375; MPEP § 1480.01 (9th Ed.
`
`Rev. Nov. 2013) (mistake not “‘minor’ . . . 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 is only proper if
`
`“correction 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
`
`
`
`3
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`(as discussed above), which were equally or more consistent with the other claims
`
`and the Patent, including Petitioner’s proposed correction to “exception condition.”
`
`Furthermore, the prosecution history is silent on the issue, and therefore there
`
`would be no way for the public—including Petitioner—to know which possible
`
`change reflects the intended scope of the Patent. See, e.g., Superior Fireplace, 270
`
`F.3d at 1371 (rejecting corrections “public could not discern from the public file”).
`
`II. Assessment of Effect of Proposed Correction on Petition
`
`Petitioner believes Vivint’s proposed change cannot be viewed as a
`
`correction, including because Petitioner assumed in its Petition a different
`
`correction that is more consistent with the specification—specifically, changing
`
`“normal status” to “exception.” However, if the Board disagrees, Petitioner
`
`contends that the prior art it previously identified also discloses a “normal status
`
`message.” As discussed in Ground 3 of the Petition (pp. 41-42), Britton recites a
`
`“check-in message” that indicates that a particular piece of monitored equipment is
`
`functioning normally. Ex. 1104 at 4:48-51, 7:54-56, 8:7-10, 11:17-21.
`
`Petitioner included claim 39 in Ground 4. For the added “normal status”
`
`limitation, Petitioner would cite Britton (e.g., Pet. pp. 41-42 (Ex. 1104 at 4:48-51)).
`
`Since Britton is not in Ground 4, Petitioner would remove claim 39 from Ground 4
`
`and include claim 39 in Ground 3 and in a new Ground 5. (See table below.)
`
`Because it could not anticipate the correction Vivint proposes, Petitioner seeks this
`
`
`
`4
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`modification on fairness grounds should the Board allow Vivint’s correction.
`
`Regarding Ground 3, Claim 39’s requirement that the exception message
`
`includes identification information is met by at least French’s “graphical report”
`
`(Pet. p. 52) and the implicit need in Shetty to identify equipment to the user in the
`
`notifications (id at 19). Regarding Ground 5, it would have been obvious to
`
`combine Britton in the system of Shetty and French. The Petition explains (id. at
`
`pp. 44-45) why it would have been obvious to incorporate the “check-in message”
`
`handling of Britton with Shetty (Ex. 1107 at ¶¶ 120-21, 134-45), and why it would
`
`have been obvious to combine Shetty with French since French discloses a fax
`
`notification mechanism and Shetty discloses using fax notifications (id. at 53-54).
`
`See also Ex. 1107 at ¶¶ 143-46. Further, Shetty, Britton and French used the same
`
`overall system architecture (Pet. pp. 39, 53). Thus, it would have been obvious to
`
`include the use of Britton’s check-in messages along with French’s fax report in
`
`the fax transmissions sent by Shetty’s central computer (id. at 44-45, 53-54).
`
`Claim 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 status
`message pertains.
`
`Ground 3: Shetty, Levac & Britton
`See claim 38 & 17 charts, Gr. 1.
`See claim 5, 8 & 30 charts, Gr. 3. Ex. 1107 at ¶¶ 130-32.
`Ground 5: Shetty, Levac, Britton & French
`See claim 38 & 18 charts, Gr. 4.
`See claim 5, 8 & 30 charts, Gr. 3. Ex. 1107 at ¶¶ 130-32.
`
`“A further page of the report, not illustrated in the
`drawings, can include a diagram of the mechanical
`room in which the failed supply fan is located, and
`highlight the exact location of the supply fan.” Ex.
`1106 at 10:47-11:12; see also id. at 11:64-12:28.
`
`
`
`5
`
`

`
`
`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
`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`Respectfully submitted,
`
`William H. Mandir
`Registration No. 32,156
`/William H. Mandir/
`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
`
`
`
`
`
`
`
`
`
`
`6
`
`

`
`Case IPR2016-00116 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
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Dated: February 3, 2016
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`By: /s/ Brian K. Shelton
`Brian K. Shelton
`Registration No. 50,245
`Backup Counsel for Petitioner
`
`
`
`7

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