Prosecution Insights
Last updated: May 29, 2026
Application No. 18/817,965

DISTRIBUTED DNS SECURITY INFRASTRUCTURE TO PRESERVE PRIVACY DATA

Non-Final OA §DOUBLEPATENT
Filed
Aug 28, 2024
Priority
Nov 21, 2022 — continuation of 12/105,840
Examiner
KIM, HEE SOO
Art Unit
2443
Tech Center
2400 — Computer Networks
Assignee
Cisco Technology Inc.
OA Round
1 (Non-Final)
79%
Grant Probability
Favorable
1-2
OA Rounds
1y 2m
Est. Remaining
79%
With Interview

Examiner Intelligence

Grants 79% — above average
79%
Career Allowance Rate
435 granted / 550 resolved
+21.1% vs TC avg
Minimal +0% lift
Without
With
+0.0%
Interview Lift
resolved cases with interview
Typical timeline
2y 12m
Avg Prosecution
24 currently pending
Career history
580
Total Applications
across all art units

Statute-Specific Performance

§101
7.7%
-32.3% vs TC avg
§103
75.3%
+35.3% vs TC avg
§102
12.1%
-27.9% vs TC avg
§112
1.9%
-38.1% vs TC avg
Black line = Tech Center average estimate • Based on career data from 550 resolved cases

Office Action

§DOUBLEPATENT
DETAILED ACTION This action is responsive to application filed on August 28th, 2024. Claims 1~20 are examined. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Information Disclosure Statement The information disclosure statement (IDS) submitted on 08/28/24 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory obviousness-type double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on a nonstatutory double patenting ground provided the conflicting application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. Effective January 1, 1994, a registered attorney or agent of record may sign a terminal disclaimer. A terminal disclaimer signed by the assignee must fully comply with 37 CFR 3.73(b). Claims 1~20 rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1~20 of U.S. Patent No. 12,105,840. Although the claims at issue are not identical, they are not patentably distinct from each other because the U.S Patent mentioned above substantially teaches claims 1~20 of the instant application. For example, claim 1 of the instant application reciting, “…publishing the HPP database to a DNS security service, such that the DNS security service can resolve a DNS query for the client…”, is similar to the U.S Patent’s claim 1 reciting, “authorizing a distributed resolver to provide DNS services to the client; and publishing the HPP database to the distributed resolver”, and thus not patentably distinct from each other. See the comparison below: Application: 18/817,965 U.S Patent 12,105,840 1. A method performed at least in part by a policy engine hosted on premises at an enterprise organization, the method comprising: applying a cryptographic hash function to metadata including personally Identifiable Information (PII) associated with a client of the enterprise organization to generate a client hash value; creating a client Hash to Policy Pair (HPP) by mapping the client hash value to a set of DNS policy instructions associated with the client; storing the client HPP in a HPP database; and publishing the HPP database to a DNS security service, such that the DNS security service can resolve a DNS query for the client of the enterprise organization absent knowledge of the PII associated with the client by mapping the client hash value included in the DNS query to the client HPP in the HPP database. 1. A method performed at least in part by a Domain Name System (DNS) security service comprising: receiving metadata including Personally Identifiable Information (PII) associated with a client; applying a cryptographic hash function to the metadata including PII associated with the client to generate a client hash value; creating a client Hash to Policy Pair (HPP) by mapping the client hash value to a set of DNS policy instructions associated with the client; storing the client HPP in a HPP database; authorizing a distributed resolver to provide DNS services to the client; and publishing the HPP database to the distributed resolver. 2. The method of claim 1, further comprising: updating the HPP database with an updated client HPP in response to a change in the set of DNS policy instructions associated with the client; and publishing the updated HPP database to the DNS service. 2. The method of claim 1, further comprising: updating the HPP database with an updated client HPP in response to a change in the set of DNS policy instructions associated with the client; and publishing the updated HPP database to the distributed resolver. 3. The method of claim 1, further comprising publishing the HPP database to a distributed resolver authorized by the DNS security service to provide DNS services to the enterprise organization. 3. The method of claim 1, further comprising: updating the HPP database with an updated client HPP in response to a change in the client hash value triggered by a change in the metadata including PII associated with the client; and publishing the updated HPP database to the distributed resolver. 4. The method of claim 3, wherein the DNS security service authorizes multiple distributed resolvers to provide DNS services to the enterprise organization and the HPP database is published, using a publish/subscribe messaging model, to the authorized distributed resolvers. 4. The method of claim 1, wherein the DNS security service authorizes multiple distributed resolvers to provide DNS services to the client and the HPP database is published, using a publish/subscribe messaging model, to the authorized distributed resolvers. 5. The method of claim 3, wherein the distributed DNS resolver is a Managed Service Provider (MSP). 5. The method of claim 1, wherein the metadata including PII associated with the client is received from an out-of-band Representational State Transfer (REST) Application Programming Interface (API), or received inline within a DNS query with encryption. 6. The method of claim 1, wherein the PII associated with the client is maintained according to regulatory security requirements. 6. The method of claim 1, wherein the distributed DNS resolver is a Managed Service Provider (MSP). 7. The method of claim 1, wherein the client hash value is added to an additional records section of a client DNS query. 7. The method of claim 1, wherein the DNS security service maintains PII associated with the client according to regulatory security requirements. Allowable Subject Matter The following is a statement of reasons for the indication of allowable subject matter: None of the prior arts teach nor render obvious claims 1~20. The claims will be allowed once a Terminal Disclaimer is filed. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to HEE SOO KIM whose telephone number is (571)270-3229. The examiner can normally be reached M-F 9AM-5PM. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Nicholas Taylor can be reached on (571) 272-3889. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /HEE SOO KIM/Primary Examiner, Art Unit 2443
Read full office action

Prosecution Timeline

Aug 28, 2024
Application Filed
Feb 17, 2026
Non-Final Rejection mailed — §DOUBLEPATENT
May 07, 2026
Response Filed

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12641073
METHODS AND APPARATUSES FOR OBTAINING A KEY SET FROM A NETWORK REPOSITORY FUNCTION
2y 10m to grant Granted May 26, 2026
Patent 12634255
SERVICE REQUEST PROCESSING METHOD, APPARATUS AND SYSTEM, DEVICE, AND STORAGE MEDIUM
1y 6m to grant Granted May 19, 2026
Patent 12627721
DISTRIBUTED MESSAGING COMMUNICATION SYSTEM INTEGRATED WITH A CROSS-ENTITY COLLABORATION PLATFORM
1y 10m to grant Granted May 12, 2026
Patent 12609911
INCLUDING PACKET PROCESSING DATA FOR DEEP PACKET INSPECTION CLASSIFICATION RULES IN A COMBINED LOOKUP TABLE USED FOR PACKET CLASSIFICATION AT A NETWORK DEVICE
2y 4m to grant Granted Apr 21, 2026
Patent 12592968
Cloud-based deception technology with granular scoring for breach detection
3y 11m to grant Granted Mar 31, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
79%
Grant Probability
79%
With Interview (+0.0%)
2y 12m (~1y 2m remaining)
Median Time to Grant
Low
PTA Risk
Based on 550 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month