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
Claims 21-40 are presenting for examination.
Non-statutory double patenting rejection
The non-statutory 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 non-statutory 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); 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 non-statutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a non-statutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) 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 www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 21-29, 33-37, and 40 are rejected on the ground of non-statutory double patenting as being unpatentable over claims 1-3, 7-8, 13, 15, 19-20 of U.S. Patent No. 12,131,206. Although the claims at issue are not identical, they are not patentably distinct from each other because the patent 206 anticipates claims 21-29, 33-37, and 40 as shown in the table below.
18/809,420
12,131,206
21. (New) A system comprising: a processing system; and memory coupled to the processing system, the memory comprising computer executable instructions that, when executed, perform operations comprising: receiving a data request at a first bidirectional application programming interface (API) in a first computing environment of a one-way transfer (OWT) system, the data request being associated with a transaction identifier; transmitting the data request to a second computing environment of the OWT system; receiving, from the second computing environment, response data associated with the data request; and based on the transaction identifier, providing the response data in response to the data request.
22. (New) The system of claim 21, the operations further comprising: prior to transmitting the data request to the second computing environment, applying a first set of policies to the data request using a first security abstraction engine of the first c24. 24.(New) The system of claim 22, wherein a policy engine of the first computing environment provides the first set of policies to the first security abstraction engine.
25. (New) The system of claim 24, wherein the policy engine provides a user interface for building static policies and machine learning (ML)-based policies.
1. A system comprising: a processing system; and memory coupled to the processing system, the memory comprising computer executable instructions that, when executed, perform operations comprising: receiving a data request at a first bidirectional application programming interface (API) in a first computing environment of a one-way transfer (OWT) system, the data request being associated with a transaction identifier; applying a first set of policies to the data request using a first security abstraction engine; transmitting the data request to a second computing environment of the OWT system; receiving, from the second computing environment, response data associated with the data request; and based on the transaction identifier, providing the response data in response to the data request.
23. (New) The system of claim 22, the operations further comprising: in response to receiving, by the second computing environment, the data request, applying a second set of policies to the data request using a second security abstraction engine of the second computing environment.
13. The system of claim 1, wherein the first set of policies dictates at least one of: data content, types of files, or types of task requests that are authorized to be transmitted from the first computing environment to the second computing environment.
26. (New) The system of claim 21, the operations further comprising: in response to receiving the response data, applying a first set of policies to the response data using a first security abstraction engine.
2. The system of claim 1, the operations further comprising: in response to receiving the data request in the second computing environment, invoking a second bidirectional API in the second computing environment; retrieving, by the second bidirectional API, response data associated with the data request; applying a second set of policies to the response data using a second security abstraction engine; and transmitting the response data to the first computing environment.
27. (New) The system of claim 21, wherein the first computing environment is untrusted by the second computing environment.
7. The system of claim 1, wherein the first computing environment is: untrusted by the second computing environment; and unable to track the data request when the data request is in the second computing environment.
28. (New) The system of claim 21, wherein the second computing environment includes a second bidirectional API.
29. (New) The system of claim 28, wherein the second bidirectional API receives the response data from a destination identified by the data request.
37. (New) The method of claim 36, wherein the information comprises at least one of: data content; types of files; or types of task requests.
3. The system of claim 2, wherein transmitting the data request to the second computing environment comprises: transmitting the data request to a third security abstraction engine in the second computing environment, wherein the third security abstraction engine dictates at least one of: data content; types of files; or types of task requests that are authorized to be received from the first computing environment or transmitted by the second computing environment; and applying, by the third security abstraction engine, a thir
33. (New) The system of claim 21, wherein the transaction identifier indicates a user objective for the data request.
8. The system of claim 1, wherein the transaction identifier indicates a use case for the data request, the use case describing at least one of a user objective or routing information for the data request.
34. (New) A method comprising: receiving a data request at a first application programming interface (API) in a first computing environment of a one-way transfer (OWT) system; applying a first set of policies to the data request using a first security abstraction engine; transmitting the data request to a second computing environment of the OWT system; receiving, from the second computing environment, response data associated with the data request; and providing the response data to the first API.
35. (New) The method of claim 34, further comprising: upon receiving the data request at the second computing environment, applying a second set of policies to the data request using a second security abstraction engine.
15. A method comprising: accessing first data at a first bidirectional application programming interface (API) in a first computing environment of a one-way transfer (OWT) system, the first data being associated with a transaction identifier; applying a first policy to the first data using a first policy engine in the first computing environment; transmitting the first data to a second bidirectional API in a second computing environment of the OWT system, the first computing environment and the second computing environment being separated by a data boundary of the OWT system; receiving, by the second bidirectional API, second data associated with the first data; applying a second policy to the second data using a second policy engine in the second computing environment; and providing the second data to the first computing environment.
36. (New) The method of claim 34, wherein the first set of policies specifies information that is authorized to be transmitted from the first computing environment to the second computing environment.
19. The method of claim 15, wherein: the second policy prevents unauthorized data from being transmitted from the second computing environment to the first computing environment; and the first policy is different from the second policy.
40. A one-way transfer (OWT) environment comprising: a processing system; and memory comprising computer executable instructions that, when executed, perform operations comprising: receiving a data request at an application programming interface (API) in a first computing environment of the OWT environment, the data request being associated with a transaction identifier; transmitting the data request to a second computing environment of the OWT environment ;receiving, from the second computing environment, response data associated with the data request; applying a set of policies to the response data using a first security abstraction engine; and based on the transaction identifier, providing the response data to the API.
20. A one-way transfer (OWT) environment comprising: a processing system; and memory comprising computer executable instructions that, when executed, perform operations comprising: receiving a first data at a bidirectional application programming interface (API) in a first computing environment of a one-way transfer (OWT) system, the first data being associated with a transaction identifier and representing a first unidirectional dataflow; applying, based on the transaction identifier, a first set of policies to the first data using a first policy engine; transmitting the first data to a second computing environment of the OWT system; receiving second data associated with the first data, the second data representing a second unidirectional dataflow; applying a second set of policies to the second data, the first set of policies being different from the second set of policies; transmitting the second data to the first computing environment; and providing the second data to the first computing environment.
Claims 30-32, and 38-39 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.
4.1. The prior art of record doesn’t teach:
prior to receiving the data request at the first bidirectional API, establishing a communication channel between the first bidirectional API and a user interface of the system, wherein the user interface receives the data request [claim 30];
the first computing environment is unable to monitor the data request when the data request is in the second computing environment [claim 38];
prior to transmitting the data request to the second computing environment, applying, by the first API, routing information to the data request based on a transaction identifier in the data request, the routing information indicating a route to the second computing environment [claim 39].
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Moustafa M Meky whose telephone number is (571)272-4005. The examiner can normally be reached Monday-Friday 9AM-5PM.
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, Ario Etienne can be reached at 571-272-4001. 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.
MOUSTAFA M. MEKY
Primary Patent Examiner
Art Unit 2457
/MOUSTAFA M MEKY/ Primary Examiner, Art Unit 2457
02/21/2026