Prosecution Insights
Last updated: May 04, 2026
Application No. 18/810,804

SECURE MESSAGE EXCHANGE BETWEEN DEPLOYMENTS

Non-Final OA §103§DP
Filed
Aug 21, 2024
Priority
Mar 04, 2020 — continuation of 10/938,780 +2 more
Examiner
SARKER, SANCHIT K
Art Unit
2495
Tech Center
2400 — Computer Networks
Assignee
Snowflake Inc.
OA Round
1 (Non-Final)
78%
Grant Probability
Favorable
1-2
OA Rounds
11m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 78% — above average
78%
Career Allowance Rate
308 granted / 394 resolved
+20.2% vs TC avg
Strong +49% interview lift
Without
With
+49.0%
Interview Lift
resolved cases with interview
Typical timeline
2y 8m
Avg Prosecution
17 currently pending
Career history
411
Total Applications
across all art units

Statute-Specific Performance

§101
10.9%
-29.1% vs TC avg
§103
56.5%
+16.5% vs TC avg
§102
6.1%
-33.9% vs TC avg
§112
17.9%
-22.1% vs TC avg
Black line = Tech Center average estimate • Based on career data from 394 resolved cases

Office Action

§103 §DP
Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . DETAILED ACTION This Office Action is in response to the application 18/810,804 filed on 08/21/2024. Claims 1-21 have been examined and are pending. Priority This application is a Continuation of U.S. Patent Application Serial No. 18/341,954, filed June 27, 2023 (Now U.S. patent No. 12,101,294), which is a continuation of U.S. Patent Application Serial No. 17/156,072, filed January 22, 2021 (Now U.S. patent No. 11,736,438), which is a continuation of U.S. application No. 16/809,209, filed on March 4th, 2020 (Now U.S. patent No. 10,938,780). Information Disclosure Statement The information disclosure statement (IDS), submitted on 01/06/2025, is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. Examiner’s notes Claims 15-21 recite “A machine-storage medium….” The specification explicitly defines as to what type of machine storage medium is claimed. In [par. 0094], the specification discloses “The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium” discussed below.” Therefore, the claims are not directed to non-statutory subject matter. However, The Examiner respectfully suggests that the claims be amended to either “A non-transitory machine storage medium”. 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). “The USPTO internet Web site contains terminal disclaimer forms which may be used. Please visit http://www.uspto.gov/forms/. The filing date of the application will determine what form should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to http://www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp. “ Claims 1-2, 7-9, 14-16 and 21 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1, 7-9, 15-17 and 23-24 of U.S. Patent Application Serial No. 18/341,954 (Now U.S. patent No. 12,101,294). Although the claims at issue are not identical, they are not patentably distinct from each other because pending application has all the limitations of U.S. patent No. 12,101,294. The examiner underlined the difference in claim language. Current Application No. 18/810,804 U.S. Patent Application Serial No. 18/341,954 (Now U.S. patent No. 12,101,294) Claims 1, 8 and 15. A method/ system / machine storage medium, comprising: receiving, by one or more processors of a first deployment, a message from a first computing device in the first deployment to be transmitted to a recipient in a second deployment, the first and second deployments being different types of deployments in a network-based data system; detecting that the second deployment has been compromised; blocking transmission of the message to the second deployment based on detecting that the second deployment has been compromised; detecting that the second deployment is no longer compromised; transmitting the message to the second deployment based on detecting that the second deployment is no longer compromised. Claims 2, 9 and 16. The method/ system / machine storage medium of claims 1/8/15, wherein the first deployment being a private data-system deployment where processing and storage resources are dedicated to a single tenant and the second deployment being a public data-system deployment where processing and storage resources are shared by multiple tenants. Claims 7, 14 and 21. The method/ system / machine storage medium of claims 1/ 8/15, wherein transmitting the message to the second deployment further comprising: detecting a message type of the message, the message type defining an operation to be performed on stored data associated with the first or second deployments; based on the detected message type belonging to a first set of message types, blocking transmission of the message to the second deployment; and based on the detected message type belonging to a second set of message types, transmitting the message from the first deployment to the second deployment. Claims 1, 9 and 17. (Currently Amended) A method / system / machine storage medium, comprising: one or more processors of a machine; and a memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations comprising: receiving, by one or more processors of a first deployment in a network-based data system, a message from a first user in the first deployment to be transmitted to a recipient in a second deployment of the network-based data system, the first deployment being a private data-system deployment where processing and storage resources are dedicated to a single tenant and the second deployment being a public data-system deployment where processing and storage resources are shared by multiple tenants; in a message-type filtering stage, detecting a message type of the message, the message type defining an operation to be performed on stored data associated with the first or second deployments; blocking transmission of the message to the second deployment in the event the detected message type belongs to a first set of message types; passing the message to a data-analysis filtering stage in the event the detected message type belongs to a second set of message types; in the data-analysis filtering stage, performing an analysis of data content in the message based on a content rule set preventing transmission of sensitive customer information; and blocking transmission or transmitting the message to the second deployment based on the analysis of the data content in the message. Claims 7, 8, 15, 16 and 23-24. The method/ system / machine storage medium of claims 1/9/17, further comprising: detecting that the second deployment has been compromised; and based on detecting that the second deployment has been compromised, blocking transmission of the message to the second deployment. blocking reception of any messages at the first deployment from the second deployment. Claims 11-2, 7-9, 14-16 and 21 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1, 6-7, 15-16, 19 and 24-25 of U.S. Patent Application No. 16/809,209 (Now U.S. patent No. 10, 938,780). Although the claims at issue are not identical, they are not patentably distinct from each other because pending application has all the limitations of U.S. patent No. 10, 938,780. The examiner underlined the difference in claim language. Current Application No. 18/810,804 U.S. Patent Application Serial No. 16/809,209 (Now U.S. patent No. 10, 938,780) Claims 1, 8 and 15. A method/ system / machine storage medium, comprising: receiving, by one or more processors of a first deployment, a message from a first computing device in the first deployment to be transmitted to a recipient in a second deployment, the first and second deployments being different types of deployments in a network-based data system; detecting that the second deployment has been compromised; blocking transmission of the message to the second deployment based on detecting that the second deployment has been compromised; detecting that the second deployment is no longer compromised; transmitting the message to the second deployment based on detecting that the second deployment is no longer compromised. Claims 2, 9 and 16. The method/ system / machine storage medium of claims 1/8/15, wherein the first deployment being a private data-system deployment where processing and storage resources are dedicated to a single tenant and the second deployment being a public data-system deployment where processing and storage resources are shared by multiple tenants. Claims 7, 14 and 21. The method/ system / machine storage medium of claims 1/ 8/15, wherein transmitting the message to the second deployment further comprising: detecting a message type of the message, the message type defining an operation to be performed on stored data associated with the first or second deployments; based on the detected message type belonging to a first set of message types, blocking transmission of the message to the second deployment; and based on the detected message type belonging to a second set of message types, transmitting the message from the first deployment to the second deployment. Claims 1, 10 and 19. (Currently Amended) A method / system / machine storage medium, comprising: one or more processors of a machine; and a memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations comprising: receiving, by one or more processors of a first deployment, a message from a first computing device in the first deployment to be transmitted to a recipient in a second deployment, the first deployment being a private data-system deployment where processing and storage resources are dedicated to a single tenant and the second deployment being a public data-system deployment where processing and storage resources are shared by multiple tenants; in a first filtering stage, detecting a message type of the message, the message type defining an operation to be performed on stored data associated with the first or second deployments; based on the detected message type belonging to a first set of message types, blocking transmission of the message to the second deployment; based on the detected message type belonging to a second set of message types, passing the message to a second filtering stage; in the second filtering stage, detecting a characteristic of the message; based on the detected characteristic belonging to a first set of characteristic types, blocking transmission of the message to the second deployment; based on the detected characteristic belonging to a second set of characteristic types, transmitting the message from the first deployment to the second deployment. Claims 6, 7, 15, 16 and 24-25. The method/ system / machine storage medium of claims 1/10/19, further comprising: detecting that the second deployment has been compromised; and based on detecting that the second deployment has been compromised, blocking transmission of the message to the second deployment. blocking reception of any messages at the first deployment from the second deployment. Claims 1-2, 7-9, 14-16 and 21 are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims 1-2, 7-9, 14-16 and 19 of U.S. Patent Application Serial No. 17/156,072 (Now U.S. patent No. 11,736,438). Although the claims at issue are not identical, they are not patentably distinct from each other because pending application has all the limitations of U.S. patent No. 11,736,438. The examiner underlined the difference in claim language. Current Application No. 18/810,804 U.S. Patent Application Serial No. 17/156,072 (Now U.S. patent No. 11,736,438) Claims 1, 8 and 15. A method/ system / machine storage medium, comprising: receiving, by one or more processors of a first deployment, a message from a first computing device in the first deployment to be transmitted to a recipient in a second deployment, the first and second deployments being different types of deployments in a network-based data system; detecting that the second deployment has been compromised; blocking transmission of the message to the second deployment based on detecting that the second deployment has been compromised; detecting that the second deployment is no longer compromised; transmitting the message to the second deployment based on detecting that the second deployment is no longer compromised. Claims 2, 9 and 16. The method/ system / machine storage medium of claims 1/8/15, wherein the first deployment being a private data-system deployment where processing and storage resources are dedicated to a single tenant and the second deployment being a public data-system deployment where processing and storage resources are shared by multiple tenants. Claims 7, 14 and 21. The method/ system / machine storage medium of claims 1/ 8/15, wherein transmitting the message to the second deployment further comprising: detecting a message type of the message, the message type defining an operation to be performed on stored data associated with the first or second deployments; based on the detected message type belonging to a first set of message types, blocking transmission of the message to the second deployment; and based on the detected message type belonging to a second set of message types, transmitting the message from the first deployment to the second deployment. Claims 1, 8 and 15. A method/ system / machine storage medium, comprising: receiving, by one or more processors of a first deployment, a message from a first computing device in the first deployment to be transmitted to a recipient in a second deployment, the first and second deployments being different types of deployments, wherein the first deployment is a private data-system deployment where processing and storage resources are dedicated to a single tenant and the second deployment is public data-system deployment where processing and storage resources are shared by multiple tenants; detecting a message type of the message using a filter based on an outbound rule set defined for the second deployment, the message type defining a data operation to be performed on stored data associated with the first deployments; based on the detected message type belonging to a first set of message types, blocking transmission of the message to the second deployment; based on the detected message type belonging to a second set of message types, proceeding in transmitting the message from the first deployment to the second deployment, the second deployment being configured to execute the data operation on the stored data associated with the first deployment in response to receiving the message; detecting that the second deployment has been compromised; and based on detecting that the second deployment has been compromised, blocking transmission of the message to the second deployment. Claims 2, 9, 16. The method/ system / machine storage medium of claims 1/8/15, further comprising: detecting a characteristic of the message; based on the detected characteristic belonging to a first set of characteristic types, blocking transmission of the message to the second deployment; based on the detected characteristic belonging to a second set of characteristic types, proceeding in transmitting the message from the first deployment to the second deployment. Claims 7, 14 and 19. The method/ system / machine storage medium of claims 1/8/15, further comprising: based on detecting that the second deployment has been compromised, blocking reception of any messages at the first deployment from the second deployment. Claim Rejections - 35 USC § 103 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102 of this title, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 1, 3-6, 8, 10-13, 15 and 17-20 are rejected under 35 U.S.C. 103 as being unpatentable over Liu (US 2005/0015455) and in view of Syrowitz (US 2014/0006522). Regarding claim 1, Liu discloses a method, comprising: receiving, by one or more processors of a first deployment, a message from a first computing device in the first deployment to be transmitted to a recipient in a second deployment (Liu par. 0002, 0054-0056. Liu teaches that E-mail is a popular and efficient means for transferring information from one user to another. The popularity of messaging systems such as E-mail has risen dramatically among individuals, and a similar rise has occurred in the business use of messaging systems. Conventional point to point transfers from one computer to another represent the vast majority of these communications, however a myriad of handheld devices are now available that deliver messages to non-traditional computing platforms and Such a client-based configuration can be used by individual email users connected to the Internet through an ISP or by email users of a corporation that would rather conduct SPAM filtering at the email client level); detecting that the second deployment has been compromised (Liu par. 0022. Liu teaches that the event can include detection that an email address associated with the sender has been compromised. A pass code can be included in the list for one or more confirmed senders. The passcode can be automatically added at a time for transmission of a message from the sender in the messaging system. A plug-in module can be provided for automatically adding the passcode. The plug-in module can be adapted to add the passcode prior to transmission to the messaging system. The method can include correlating sender-recipient data at a spam filter in the messaging system, determining data related to how fast a list of recipients grows for a given sender; determining a list of unacceptable senders using the sender-recipient data and the determined data and sharing the list of unacceptable senders with other spam filters in the messaging system. See also par. 0044 and 0063); blocking transmission of the message to the second deployment based on detecting that the second deployment has been compromised ((Liu par. 0022 and 0027. Liu teaches that the event can include detection that an email address associated with the sender has been compromised. A pass code can be included in the list for one or more confirmed senders. The passcode can be automatically added at a time for transmission of a message from the sender in the messaging system. A plug-in module can be provided for automatically adding the passcode. Using the proposed system, information can be collected by the data center from the spam filters and analyzed to detect spammers, even if these spammers use their real email address and are able to answer confirmation emails).. See also par. 0044, 0063 and Fig. 2); and detecting that the second deployment is no longer compromised (Liu par. 0013 and 0044. Liu teaches that identifying the sender of the message and determining if the sender has been previously confirmed as a valid sender including determining if the sender is included in a list of confirmed senders for any spam filter in the network and Black List (22) is a list of known Spammers or other type of malicious senders (e.g., email senders). See also par. 0023); transmitting the message to the second deployment based on detecting that the second deployment is no longer compromised (Liu par. 0023. Liu teaches that determining if the sender is a confirmed sender including querying a data center to determine if the sender is included in a list of confirmed senders based on information received from any of the plurality of spam filters in the messaging system. Confirmed senders are senders having a verified capability to receive messages. If the sender is a confirmed sender, the method can enable transmission of the message to the intended recipient. See also par. 0013 and 0044). Liu teaches, receiving, by one or more processors of a first deployment, a message from a first computing device in the first deployment to be transmitted to a recipient in a second deployment (Liu par. 0002, 0054-0056). However, Liu does not explicitly disclose receiving, by one or more processors of a first deployment and second deployment and the first and second deployments being different types of deployments in a network-based data system. However, in an analogous art, Syrowitz teaches wherein receiving, by one or more processors of a first deployment and second deployment and the first and second deployments being different types of deployments in a network-based data system (Syrowitz par. 0071. Syrowitz teaches that Email server represent one or more electronic devices that provide and host email services for multiple clients. Email server implemented as a remote or "cloud" deployment accessible over a network, such as the Internet. Email server arranged to provide email services such as, but not limited to, receiving email messages for an email account, sending email messages from an email account, storing email messages, and providing filtering services, such as spam filtering) and the first and second deployments being different types of deployments (Syrowitz par. 0016, 0031, 0048. Syrowitz teaches that System 100 may include a plurality of client devices, such as client device 120. Client device 120 may include any electronic device capable of communicating with email server 102 to send, receive and manage email messages in an email account. Use characteristics of the email message, global filtering rule statistics, and/or information about the recipient's email-related behavior to select which filtering rules may be relevant to the email message. and filtering rules 300 may be organized into different types. For example, filtering rules 300 may include language rules 310, country of origin rules 320, category rules 330, and recipient rules 340. Within each type, the rules may be sub-divided into subtypes. Rule selection logic 260 may select the rules that are in one subtype and be able to exclude rules from one or more other subtypes. The embodiments are not limited to these examples). Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine the teachings of Syrowitz with the method and system of Liu, receiving, by one or more processors of a first deployment and second deployment and the first and second deployments being different types of deployments in a network-based data system to provide users with a means for selecting and prioritizing the application of spam filtering rules in a way that reduces processing time may include receiving an email message for a recipient at a spam filter and extracting email characteristics from the message (Syrowitz Abstract). Regarding claim 3, Liu and Syrowitz disclose the method of claim 1, Liu further discloses wherein the first deployment is located at a first geographic location and the second deployment is located at a second geographic location (Liu par. 0002. Liu teaches that with the advent of modern computer technology, individuals increasingly use electronic means to transfer information from one location to another). Regarding claim 4, Liu and Syrowitz disclose the method of claim 1, Liu further discloses wherein detecting that second deployment has been compromised is based on a notification received from the second deployment (Liu 0044, 0063 and claim 54. Liu teaches that upon receipt of a confirmation from the sender, sharing the sender's confirmed status with the plurality of spam filters in the messaging system including publishing the sender's status to the data center. SPAM Filter Logic (33) checks if the email message contains properly formatted information and if the domain of sender's email address actually exists and the IP address is consistent with the IP address making the SMTP connection, if such information is available. If any of the proscribed checks fails, the process will jump to Step (208) to dispose the message). Regarding claim 5, Liu and Syrowitz disclose the method of claim 1, Liu further discloses wherein detecting that the second deployment is no longer compromised is based on a notification received from the second deployment (Liu par. 0027. Liu teaches that using the proposed system, information can be collected by the data center from the spam filters and analyzed to detect spammers, even if these spammers use their real email address and are able to answer confirmation emails . See also par. 0023). Regarding claim 6, Liu and Syrowitz disclose the method of claim 1, Liu further discloses further comprising: blocking reception of messages from the second deployment based on detecting that the second deployment has been compromised (Liu par. 0022 and 0027. Liu teaches that the event can include detection that an email address associated with the sender has been compromised. A pass code can be included in the list for one or more confirmed senders. The passcode can be automatically added at a time for transmission of a message from the sender in the messaging system. A plug-in module can be provided for automatically adding the passcode. Using the proposed system, information can be collected by the data center from the spam filters and analyzed to detect spammers, even if these spammers use their real email address and are able to answer confirmation emails). Regarding claims 8 and 10-13; claims 8 and 10-13 are directed to a system associated with the method claimed in claims 1 and 3-6. Claims 8 and 10-13 are similar in scope to claims 1 and 3-6 and are therefore rejected under similar rationale respectively. Regarding claim 15; claim 15 is directed to a machine storage medium associated with the method claimed in claim 1. Claim 15 is similar in scope to claim 1, and is therefore rejected under similar rationale respectively. Syrowitz also teaches the additional limitations of claim 15 as follows: A machine-storage medium embodying instructions that, when executed by a machine, cause the machine to perform operations (Syrowitz par. 0062. Syrowitz teaches electronic device 510 may include a processor circuit 530 and a memory unit 550. Processor circuit 530 may be a processing unit or component as described in greater detail below. Memory unit 550 may be, for example, a system memory or other memory device capable of storing instructions and/or data for short term or long term storage). Regarding claims 17-20; claims 17-20 are directed to a machine storage medium associated with the method claimed in claims 3-6 respectively. Claims 17-20 are similar in scope to claims 3-6 respectively and are therefore rejected under similar rationale respectively. Claims 2, 9 and 16 are rejected under 35 U.S.C. 103 as being unpatentable over Liu (US 2005/0015455), in view of Syrowitz (US 2014/0006522) and further in view of Cooper (US 2016/0105408). Regarding claim 2, Liu and Syrowitz disclose the method of claim 1, Liu and Syrowitz failed to disclose but Cooper discloses wherein the first deployment being a private data-system deployment where processing and storage resources are dedicated to a single tenant and the second deployment being a public data-system deployment where processing and storage resources are shared by multiple tenants (Cooper par. 0033. Cooper teaches Cloud computing environment 200 may be configured such that cloud resources 205 provide computing resources to client devices 210 through a variety of deployment models, such as public, private, community, hybrid, and/or any other cloud deployment model. Cloud resources 205 may be configured, in some cases, to support multiple deployment models. For example, cloud resources 205 can provide one set of computing resources through a public deployment model and another set of computing resources through a private deployment model). Therefore, it would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine the teachings of Copper with the method and system of Liu and Syrowitz, wherein deployment is a private data-system deployment dedicated to a single tenant and the second deployment is public data-system deployment shared by multiple tenants to provide users with a means for the secure exchange of data within a network (Cooper Abstract). Regarding claims 9 and 16; claims 9 and 16 are directed to a system and machine storage medium associated with the method claimed in claim 2. Claims 9 and 16 are similar in scope to claim 2 and are therefore rejected under similar rationale respectively. Allowable Subject Matter Claims 7, 14 and 21 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims and if the nonstatutory obviousness-type double patenting rejection(s), set forth in this Office action is resolved. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to SANCHIT K SARKER whose telephone number is (571)270-7907. The examiner can normally be reached M-F 8:30 AM-5:30 PM. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, FARID HOMAYOUNMEHR can be reached at 571-272-3739. 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. /SANCHIT K SARKER/Primary Examiner, Art Unit 2495
Read full office action

Prosecution Timeline

Aug 21, 2024
Application Filed
Dec 10, 2025
Non-Final Rejection — §103, §DP
Mar 30, 2026
Response Filed

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12579285
CENTRAL DATA GOVERNANCE AND ACCESS CONTROL FOR ENTERPRISE DATA
2y 8m to grant Granted Mar 17, 2026
Patent 12579291
SYSTEMS AND METHODS FOR ADAPTIVE DIGITAL REINFORCEMENT LEARNING
2y 11m to grant Granted Mar 17, 2026
Patent 12579305
DATA SECURITY FOR MACHINE LEARNING SYSTEMS
2y 1m to grant Granted Mar 17, 2026
Patent 12566870
COMMUNICATION METHOD, DEVICE, AND SYSTEM FOR OBTAINING AUTHORIZATION INFORMATION OF USER-RELATED DATA
3y 0m to grant Granted Mar 03, 2026
Patent 12561471
METHOD AND SYSTEM FOR DATA COMMUNICATION WITH DIFFERENTIALLY PRIVATE SET INTERSECTION
2y 2m to grant Granted Feb 24, 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
78%
Grant Probability
99%
With Interview (+49.0%)
2y 8m (~11m remaining)
Median Time to Grant
Low
PTA Risk
Based on 394 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