throbber
PATENT
`
`Docket No.: H0003965DIVIE
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`In re Letters Patentof:
`Rajiv R. Singhet al.
`
`Patent No.: 9,157,017
`
`Issued: October 13, 2015
`
`Subject of: PGR2016-00011 and PGR2016-00012
`
`For: COMPOSITIONS CONTAINING
`FLUORINE SUBSTITUTED OLEFINS AND
`METHODS AND SYSTEMS USING SAME
`
`Electronically Filed
`
`Attention: Certificate of Correction Branch
`Commissioner for Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`SECOND RENEWED PETITION FOR RECONSIDERATION
`OF DECISION DENYING PETITION FOR CERTIFICATE OF CORRECTION
`
`Dear Commissioner:
`
`In response to the Decision on the first renewed Petition dated May 26, 2022, this is a
`
`second RenewedPetition under 37 .C.F.R. §1.78(c) and (e) seeking acceptance of the delayed
`
`claim to priority being requested by the Certificate of Correction originally filed on May 6, 2020.
`
`The paymentof the fee required by 37 .C.F.R. §1.17(m) has been made with the original petition.
`
`The entire time between the date the benefit claim was due under 37 CFR §1.78 (d)(3)
`
`and (a)(4) and the date of this renewed request to makethe priority claim was unintentional.
`
`RESPONSE TO PETITION ON DECISION DATED MAY26, 2022
`
`On May 26, 2022, a decision was entered (hereinafter “the Decision’) dismissingthe first
`
`renewedPetition filed on March 15, 2022, for reconsideration of the decision denying the
`
`Petition filed on March 15, 2020, for a Certificate of Correction. In the Decision, the Office of
`
`Petitions stated that “[first] renewed petition does not explain the facts and circumstances
`
`surrounding applicant’s delay in seeking acceptance of the newly claimed benefit chain,” and the
`
`expressly directed the owner of the ‘017 Patent (hereinafter “Petitioner” or “Honeywell”) to
`
`

`

`“address applicant’s delay in seeking acceptance of the newly claimed benefit chain in a renewed
`
`petition under 37 CFR 1.78(c) and (e).” (See last paragraph on page 2 of the Decision). In
`
`particular, it was stated that “additional information that provides an explanation of the
`
`circumstances surrounding the delay that establishes the entire delay was unintentionalis
`
`required.” (See paragraph bridging page 1 and page2).
`
`Honeywell summarizes the addtional items of inquiry that are identified in the Decision
`
`as follows:
`
`1. What date and under what circumstances did petitioner become aware that there was
`
`an issue with the benefit information.
`
`2. When did the processto correct the benefit information begin after the issue was
`
`discovered.
`
`3. Whythe additional priority chain issue was not raised during prosecution of
`
`Application No. 14/225,588.
`
`4. What protocols were present to ensure the benefit information is correct.
`
`5.
`
`Is the patent reviewed for accuracy uponreceipt?
`
`Petitioner’s response to each of these identified areas of inquiry are provided below. Petitioneris
`
`filing concurrently herewith a Third Declaration of Joseph F. Posillico (hereinafter “Third
`
`Posillico Declaration”) to support Petitioner’s response to these areas of inquiry.
`
`1. Discovery of the Issue Regarding the Priority Benefit Claim
`
`Petitioner provides the requested information regarding the discovery ofthe error by first
`
`identifying the nature of the error (see subsection a. below) and by then identifying how and
`
`whenthis error was recognized (see subsecion b. below).
`
`a. The Error In The Priority Benefit Claim
`
`Asset-forth in the Third Posillico Declaration, U.S. Patent Application. No. 14/225,588
`
`(“the 588 application”) is the patent application which led to U.S. Patent No. 9,157,017 (“the
`
`‘017 Patent”), which is the patent that is the subject of the Certificate of Correction. (Third
`
`Posillico Declaration, para. 2). As originally filed on March 26, 2014, the °588 application
`
`included claims focused on cleaning compositions andinflating agents. /d. The claims of the
`
`‘017 Patent, however, covered methods of producing/providing automobile air conditioning and
`
`heat transfer compositions for automobile air conditioning which use 2,3,3,3-tetrafluoropropene
`
`(HFO-1234yf) as the refrigerant.
`
`/d. The priority claim originally made on the face of the ’017
`
`patent is depicted below graphically on the following page:
`2
`
`4862-1692-2663, v. 1
`
`

`

`Provisional Appl. No. 60/421,435
`Provisional Appl. No. 60/421,263
`Filed Oct. 25, 2002
`Filed Oct. 25, 2002
`"PSSSTSSS ASAT
`i
`
`Appl. No. 10/694,273
`Filed Oct. 27, 2003
`Now U.S,Patent No. 7,534,366
`RECREATEECR
`
`POLLOLLLEAL
`
`ORLALLELE,
`
`
`
`ALAREES
`
`Appl. No. 10/694,272
`Filed Oct. 27, 2003
`Now U.S. Patent No. 7,230,146
`“ocmeccemeocceeacmggecoeeeccerercemrormE
`
`:
`
`
`
`onennnennnentDnES
`
`Appl. No. 10/837,525
`Filed Apr. 29, 2004
`Now U-S. Patent No. 7,279,451
`<<pvsion|
`Divisional
`
`Appl. No. 11/847,192
`Filed Aug. 29, 2007
`
`U-S. Patent No. 9,518,225
`
`Issued December 13, 2016
`
`sot
`Divisional
`
`Td.
`
`Appl. No. 13/844,206
`Filed Mar. 15, 2013
`U.S. Patent No. 9,695,363
`Issued July 4, 2017
`AAAAcAOUMOMMUMO
`
`/wenenereceeapreceecrscnenes
`
`Divisiond (eee
`Appl. No. 14/225,588
`Filed Mar. 26, 2014
`_U.S. Patent No. 9,157,017
`|
`Issued on October 13, 2015PSR
`
`Whenthe 588 application wasfiled, Honeywell inadvertently failed to make a claim to
`
`the priority of another chain of applications that was also pending when the 588 application was
`
`filed. (Third Posillico Declaration, para. 3). This additional priority chain is shown in red below,
`
`together with the original priority claim:
`
`Provisional Appl. No. 60/421,263
`Filed Oct. 25, 2002
`
`Provisional Appl. No. 60/421,435
`Filed Oct. 25, 2002
`STR
`
`Appl. No. 10/694,272
`Filed Oct. 27, 2003
`Now U.S. Patent No, 7,230,146
`"RSSRGSS
`
`Appl. No. 10/694,273
`Filed Oct. 27, 2003
`Now U-S: Patent No. 7,534,366
`TRS SANTANAINSEADIANA
`
`
`Provisional Appl: No. 60/693,853
`Filed Jun: 24,2005
`
`ee
`STILLLTITLPE,
`
`
`
`
`
`
`
`
`DLPLPDIDIOLIIIELLE
`
`Abandoned on April 19, 2018 LLLPLLLLPLLLLLPOPTLEDE,
`
`Appl. No. 11/850,025
`
`Filed Sep. 4; 2007
`a
`TOLLEDLPLLEDLELEETEE
`
`Appl, No, 11/475,605
`Appl. No. 10/837,525
`Fileddun: 26;:2006
`Filed Apr. 29, 2004
`U:SePatent No.:9;005,467
`
`Now U:S. Patent No. 7,279,451
`Issued:on April 14,2015
` IRR
`SAQO_owonnnngygqgq\q4gggTTTgggggg
`
`
`*eepuvsiond.|.Divisional
`Appl. No. 11/847,192
`Filed Aug. 29, 2007
`U.S. Patent No. 9,518,225
`Issued December 13, 2016
`“Ssesesenondtee
`ivisional
`
`Sew
`
`Divisional
`
`Appl. No. 13/844,206 (Filed Mar. 15, 2013)
`US. Patent No. 9,695,363
`Issued July 4, 2017
`
`“SigekneiocioneknciocinsknclncnSeNSANSARMRNAS
`
`4862-1692-2663, v. 1
`
`
`
`Appl. No. 14/225,588
`Filed Mar. 26, 2014
`U:S. Patent No. 9,157,017
`*
`Q
`Is sued on Octo ber 1 3 20 1 5
`ISSERSSSSR
`
`

`

`As shown above, Honeywell could have madea priority claim as a continuation-in-part
`
`(CIP) to Application No. 11/850,025 since that application (and its parent Application No.
`
`11/475,605) was co-pending with and shared common inventors with the ‘588 application.
`
`(Third Posillico Declaration, para. 4).
`
`During early prosecution of the °588 application, the claims focused on cleaning
`
`compositions andinflating agents. (Third Posillico Declaration, paras. 2 and 5). That was
`
`because the 588 application wasfiled as a divisional of the ’206 application, and thus the ’588
`
`application’s specification, claims, andlisting of “Related Applications” closely resembled that
`
`of the ’206 application. /d. In early prosecution, however, Honeywell amendedthe claims in the
`
`°588 application to instead be directed to methods of producing/providing automobile air
`
`conditioning and to heat transfer compositions for automobile air conditioning which use 2,3,3,3-
`
`tetrafluoropropene (HFO-1234yf) as the refrigerant. /d. But Honeywell through inadvertent
`
`error did not make conforming amendments to the ’588 application’s chain ofpriority to fully
`
`list other applications in the same family that describe the claimed compositions’ utility in
`
`automobile air conditioning—including the ’025 and ’605 applications and ’853 provisional. /d.
`
`This mistake was an inadvertent error made in good faith and without any deceptiveintent.
`
`(Third Posillico Declaration, paras. 5 - 9).
`
`b. The Error In The Priority Claim Was Discovered in November 2016
`
`Petitioner was not aware ofthe error described above until a little more than one year
`
`after the ‘017 Patent issued. (Third Posillico Declaration, para. 10). At the time the ‘558
`
`application wasfiled, and throughoutthe time that original prosecution leading to the ‘017 Patent
`
`was ongoing, Petitioner believed that the pending claims were valid and fully in compliance with
`
`35 U.S.C. § 112. Jd. This belief was consistent with the position taken during the original
`
`prosecution by the Examiner, whonever rejected Honeywell’s claims under 35 U.S.C. § 112. /d.
`
`That is, the Examiner’s review of the specification resulted in a conclusion that the specification
`
`of the application fully described and enabled the claims of the ‘017 Patent as issued.
`
`/d.
`
`Honeywell had reached the same conclusion and had no reason to doubtthat the priority chain on
`
`the face of the ’017 patent supported the 017 patent’s claims—specifically that the specification
`
`of the *525 application fully described and enabled the claims—whenthe ’017 patent issued. /d.
`
`In February 2016, the above-noted PGR2016-00011 and PGR2016-00012 (hereinafter
`
`“the PGRs”) werefiled against the ‘017 Patent. (Third Posillico Declaration, para. 11). The
`
`PGRsincluded allegations that the claims of the ‘017 Patent were not supported or enabled by
`4
`
`4862-1692-2663, v. 1
`
`

`

`any application in the priority chain with a date prior to March 26, 2014.
`
`/d.
`
`In June 2016,
`
`Honeywell filed a Preliminary Response to the PGRsvigorously refuting this contention, and
`
`Honeywell subsequently continued to refute these contentions during that proceeding.
`
`/d.
`
`On September 2, 2016, the Board entered a decision instituting post grant review. (Third
`
`Posillico Declaration, para. 11).
`
`In this decision the Board held that the record at that time had
`
`“demonstrated by a preponderance of the evidence that the ‘017 patent claims have an effective
`
`filing date of March 26, 2014.” /d. Prior to this decision by the Board, Petitioner was not aware
`
`of an error in the priority chain.
`
`/d. As Honeywell proceeded with the preparation of its Patent
`
`Owner Responses, which wasdueto be filed on December 16, 2016, it began to evaluate the
`
`possibility that an error may have occurred in the original priority chain.
`
`/d. Honeywellfirst
`
`realized in November 2016 that additional patent applications could have and should have been
`
`includedin the priority chain of the ‘017 Patent.
`
`/d.
`
`In summary,as part of its preparation of its response to the PGRs in November2016,
`
`Honeywell concluded that an error had been madein the priority chain that could be corrected by
`
`a Certificate of Correction.
`
`2. Petitioner Diligently Sought Correction of The Error After Its Discovery
`
`Upon reaching the conclusion in November 2016 that a priority chain error had occurred,
`
`and as required by 37 C.F.R. § 42.02(b), Petitioner sought the Board’s permissionto file a
`
`Certificate of Correction to amendthe priority chain. (Third Posillico Declaration, para. 13).
`
`This request was madeby a telephone conference with the Board that began on November28,
`
`2016, and which was continued on November29, 2016.
`
`/d. The Board denied this request
`
`during the telephone conference of November29, 2016. /d.
`
`From the time the Board denied the request to seek a Certificate of Correction to the
`
`present, Petitioner has acted diligently to obtain the Certificate of Correction. (Third Posillico
`
`Declaration, para. 14). After the Board denied Petitioner’s request to seek the Certificate of
`
`Correction, the Board’s Rules specifically prohibited Honeywell from filing for the certificate of
`
`correction. (See 35 USC 325(d); 37 CFR 42.3; 37 CFR 42.222(a); Alarm.com Inc. v. Vivint, Inc.
`
`2
`
`Case IPR2015-01995, Paper No. 10 (PTAB, Jan. 28, 2016)). Accordingly, Petitioner diligently
`
`proceeded with the PGRsuntil the Board enteredits final decision on August 31, 2017. /d.
`
`Petitioner then timely appealed the Board’s August 31, 2017, decision to the Court of
`
`Appeals for the Federal Circuit on November22, 2017. Jd. Petitioner’s appeal sought review
`
`of:
`
`4862-1692-2663, v. 1
`
`

`

`“Whether the Board’s denial of Honeywell’s November28, 2016, request
`
`for authorization to file a motion seeking permissiontofile a Certificate of
`
`Correction to correct the series of applications in the ’017 patent’s priority chain was
`
`arbitrary, capricious, an abuse ofdiscretion, or otherwise not in accordance with law.”
`
`Id. The Federal Circuit issued its decision on appeal on October 1, 2019, and as a part ofits
`
`consideration of the Certificate of Correction question, the Federal Circuit specifically noted
`
`that:
`
`“Finally, in response to the Board’s questions about whetherthe [priority] change would
`
`satisfy the “good faith” requirement of 35 U.S.C. § 255, Honeywell explained that it
`
`learned of the incomplete priority chain forthe first time after the Board issued its
`
`decision to institute. Honeywell asserts, and Arkema doesnot dispute, that Honeywell
`
`sought authorization from the Boardto file its motion for leave “promptly upon
`
`discovering the mistake in the course of preparing its Patent Owner Responses.”
`
`Honeywell sought authorization from the Boarda little over a year after the ’017 patent
`
`issued and less than three months after the Board instituted review.”
`
`Id. The Federal Circuit decided that “the Board abusedits discretion” by denying Petitioner’s
`
`request to seek a Certificate of Correction and that “[w]e find nothing in the record, or in the
`
`Board’s conclusory decision, that warrants denying Honeywell’s request to file a motion for
`
`leave to petition the Director for a Certificate of Correction correcting the priority chain of the
`
`°017 patent.” Jd.
`
`Thus, on October 1, 2019, the Federal Circuit remanded the Certificate of Correction
`
`question to the Board. (Third Posillico Declaration, para. 15). Following the remand,
`
`Honeywell diligently followed the procedures established by the Board to seek leaveto file the
`
`Certificate of Correction.
`
`/d. These proceduresincludedfiling with the Board on January 1,
`
`2020, a Motion for Leave to Request a Certificate of Correction and conducting discovery
`
`relating to the motion and briefing the motion. /d. This diligent effort resulted in the Board
`
`granting Honeywell’s motion on April 27, 2020. Jd.
`
`Following the Board’s Order granting the motion for leave, Petitioner diligently prepared
`
`and filed its request for a Certificate of Correction on May 6, 2020. /d. Petitioner’s request was
`
`dismissed on February 15, 2022, and Petitioner diligently filed its first Renewed Petition on
`
`March 15, 2022.
`
`/d. Petitioner’s first Renewed Petition was dismissed on May 26, 2022, and
`
`4862-1692-2663, v. 1
`
`

`

`Petitioner is now diligently filing its Second RenewedPetition on June 28, 2022, in direct
`
`responseto the Office’s request. /d.
`
`3. Other Questions Raised in the Dismissal
`
`Petitioner respectfully submits that, in view of the explanations provided herein relating
`
`to the date on whichthe error was discovered, the remaining inquiries raised in the Dismissal
`
`(see items 4 and 5 on page 2 above) are not relevant to the question of Petitioner’s unintentional
`
`delay. Each of those inquiries relate to procedures that would have occurred prior to the date
`
`Petitioner discovered the error, and thus are not relevant to any delay in seeking correction once
`
`the error was knownto Petitioner. As explained above, Honeywell did not learn of the error in
`
`the priority chain until after the Board’s decision instituting the PGRsheld that the record at that
`
`time “demonstrated by a preponderance of the evidence that the ‘017 patent claims have an
`
`effective filing date of March 26, 2014.”
`
`CONCLUSION
`
`In view of provision by Petitioner of the additional information requested in the Decision,
`
`Petitioner respectfully renewsits request to enter the Certificate of Correction filed May 5, 2020.
`
`All fees associate with the entry of the Certificate of Correction have been paid, and to the extent
`
`any further fee is deemedto be necessary to enter the Certificate of Correction, the
`
`Commissioneris hereby authorized to charge such fee, or to credit any over payment, to Deposit
`
`Account 60-3928, from which the undersigned is authorized to draw.
`
`Dated: July 2, 2022
`
`Respectfully submitted,
`
`By_/Joseph F. Posillico/
`Joseph F. Posillico
`Registration No.: 32,290
`FisherBroyles, LLP
`One Liberty Place
`1650 MarketStreet, 36th Floor
`Philadelphia, PA 19103
`Telephone: 215 370-2424
`Email: Joseph.Posollico@fisherbroyles.com
`
`4862-1692-2663, v. 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