Prosecution Insights
Last updated: August 17, 2026
Application No. 17/960,784

APPLICATION PROGRAMMING INTERFACE TO INDICATE A CONTROLLER TO A DEVICE IN A CORE NETWORK

Final Rejection §102§DOUBLEPATENT
Filed
Oct 05, 2022
Examiner
KHAN, ATTA
Art Unit
2449
Tech Center
2400 — Computer Networks
Assignee
NVIDIA Corporation
OA Round
4 (Final)
84%
Grant Probability
Favorable
5-6
OA Rounds
0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 84% — above average
84%
Career Allowance Rate
277 granted / 331 resolved
+25.7% vs TC avg
Strong +25% interview lift
Without
With
+25.3%
Interview Lift
resolved cases with interview
Typical timeline
2y 6m
Avg Prosecution
5 currently pending
Career history
345
Total Applications
across all art units

Statute-Specific Performance

§101
20.9%
-19.1% vs TC avg
§103
52.7%
+12.7% vs TC avg
§102
6.3%
-33.7% vs TC avg
§112
12.0%
-28.0% vs TC avg
Black line = Tech Center average estimate • Based on career data from 331 resolved cases

Office Action

§102 §DOUBLEPATENT
DETAILED ACTION The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention. 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. Claims 1-20 are rejected in the Instant Application. Status of claims Claims 1-20 have been amended Claims 1-20 are pending in the instant application Claims 1-20 are rejected in the instant application Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 07/23/2025 has been entered. Response to Arguments Applicant’s arguments with respect to claims 1-20 have been considered but not persuasive. Examiner maintains his rejection. See examiners response below. Applicants arguments: Applicant has amended the claims and Abhigyan (Sharma) does not teach the amendments as filed 03/09/2026 Examiners Response: Examiner respectfully disagrees and has updated the rejection below to identify the amendments as taught in Sharma. Examiner respectfully disagrees, Sharma clearly teaches API calls in communication with controllers external to the network. Please see examiners update rejection below. Applicant is kindly asked to set up a formal interview to identify the inventive concept or how the applicant intends the claims to be interpreted. Examiner maintains his rejection. Double patenting rejections are maintained, applicant argues the amendments overcome the double patenting rejection. Examiner respectfully disagrees and points to the mapping of the double patenting rejections highlighted below. Examiner kindly suggests prior to filing a response, the applicant set up a formal interview with the examiner such that details about specific limitations can be clarified inventive concept clearly defined. Information Disclosure Statement The information disclosure statement(s) (IDS) submitted on 10/21/22, 6/3/24, 7/9/25, 8/25/25 is/are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement(s) is/are being considered if signed and initialed by the Examiner. Double Patenting A rejection based on double patenting of the “same invention” type finds its support in the language of 35 U.S.C. 101 which states that “whoever invents or discovers any new and useful process... may obtain a patent therefor...” (Emphasis added). Thus, the term “same invention,” in this context, means an invention drawn to identical subject matter. See Miller v. Eagle Mfg. Co., 151 U.S. 186 (1894); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Ockert, 245 F.2d 467, 114 USPQ 330 (CCPA 1957). A statutory type (35 U.S.C. 101) double patenting rejection can be overcome by canceling or amending the claims that are directed to the same invention so they are no longer coextensive in scope. The filing of a terminal disclaimer cannot overcome a double patenting rejection based upon 35 U.S.C. 101. 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 double patenting rejection is appropriate where the claims at issue 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 reference 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. A terminal disclaimer must be signed in compliance with 37 CFR 1.321(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. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960774 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960774 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (APJ) to indicate one or more controllers to control one or more devices within one or more 5G access networks. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to perform an application programming interface (API) to cause a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (APJ) to indicate one or more controllers to control one or more devices within one or more 5G access networks. claim 15. A method comprising: performing an application programming interface (API) causing a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to indicate one or more controllers to control one or more devices within one or more 5G access networks. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960777 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960777 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (APJ) to indicate one or more controllers to control one or more devices within one or more 5G transport networks. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to perform an application programming interface (API) to cause a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (APJ) to indicate one or more controllers to control one or more devices within one or more 5G transport networks. claim 15. A method comprising: performing an application programming interface (API) causing a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access network. . 15. A method comprising: performing an application programming interface (API) to indicate one or more controllers to control one or more devices within one or more 5G transport networks. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960796 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960796 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G core networks to be stored. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to perform an application programming interface (API) to cause a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G transport networks to be stored. claim 15. A method comprising: performing an application programming interface (API) causing a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G core networks to be stored. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960788 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960788 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G access networks to be stored. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to perform an application programming interface (API) to cause a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G access networks to be stored. claim 15. A method comprising: performing an application programming interface (API) causing a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G access networks to be stored. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960793 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960793 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G transport networks to be stored. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to perform an application programming interface (API) to cause a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G transport networks to be stored. claim 15. A method comprising: performing an application programming interface (API) causing a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to cause one or more indications of one or more devices within one or more 5G transport networks to be stored. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960770 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960770 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) core networks, with which one or more devices within one or more 5G transport networks is to share information. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to perform an application programming interface (API) to cause a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) core networks, with which one or more devices within one or more 5G transport networks is to share information. claim 15. A method comprising: performing an application programming interface (API) causing a controller, external to a core network, to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) core networks, with which one or more devices within one or more 5G transport networks is to share information. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960764 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960764 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) core networks, with which one or more devices within one or more 5G access networks is to share information. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) core networks, with which one or more devices within one or more 5G access networks is to share information. claim 15. A method comprising: receiving an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, causing the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) core networks, with which one or more devices within one or more 5G access networks 1s to share information. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960763 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960763 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) transport networks, with which one or more devices within one or more 5G core networks is to share information. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) transport networks, with which one or more devices within one or more 5G access networks is to share information. claim 15. A method comprising: receiving an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, causing the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) transport networks, with which one or more devices within one or more 5G access networks is to share information. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960762 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960762 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) transport networks, with which one or more devices within one or more 5G access networks is to share information. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) transport networks, with which one or more devices within one or more 5G access networks is to share information. claim 15. A method comprising: receiving an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, causing the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) transport networks, with which one or more devices within one or more 5G access networks is to share information. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960754 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960754 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) access networks, with which one or more devices within one or more 5G core networks is to share information. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) access networks, with which one or more devices within one or more 5G core networks is to share information. claim 15. A method comprising: receiving an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, causing the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network. 15. A method comprising: performing an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (SG-NR) access networks, with which one or more devices within one or more 5G core networks is to share information. Claim 1, 8, 15 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 8, 15 of copending Application No. 17960751 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims in in the instant application are broader than the reference application. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. Instant Application Application No. 17960751 claim 1. One or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network 1. A processor comprising: one or more circuits to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (5G-NR) access networks, with which one or more devices within one or more 5G transport networks is to share information. claim 8. A system, comprising at least one memory storing instructions that, when executed by one or more processors, cause the system to receive an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, cause the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access. 8. A system, comprising memory to store instructions that, as a result of performance by one or more processors, cause the system to perform an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (5G-NR) access networks, with which one or more devices within one or more 5G transport networks is to share information. claim 15. A method comprising: receiving an application programming interface (API) call indicating at least a controller external to a core network; and in response to the API call, causing the controller to communicate one or more control signals to one or more devices within the core network, the one or more control signals to cause the one or more devices to modify performance of the core network, wherein the one or more control signals are generated by the controller using information from a transport network and an access network. . 15. A method comprising: performing an application programming interface (API) to indicate one or more devices within one or more fifth generation new radio (5G-NR) access networks, with which one or more devices within one or more 5G transport networks is to share information. Claim Rejections - 35 USC § 102 The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention. (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Claims 1-20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Sharma et al. (US20230018000A1) hereinafter Sharma. Regarding claims 1, 8, 15. Sharma teaches one or more processors comprising: circuitry to receive an application programming interface (API) call indicating at least a controller external to a core network (¶0060 see Network API gateway 230C provides an external interface for API network service 158. For example, network API gateway 230C may provide a list of APIs available to applications ¶0043 see core network 230A provides an entry point to data networks for user devices. For example, core network 230A may access data networks outside of core network 230A to provide connectivity between external networks and UE 210A.); In response to the API call, cause the controller (¶0033 see control APIs utilize various controllers for access and core networks (e.g., radio access network (RAN) intelligent controller, 5G Network Exposure Function (NEF), etc.). These and other controllers may be exposed by network API service 158 to external applications (and users) for them to request features from the network in an on-demand manner) to communicate one or more control signals to one or more devices within the core network (Fig 2A see element 158: ¶0032 see The communications network 125 also includes network API service 158. As further described below with reference to later figures, network API service 158 collects and stores data from various network elements and access networks, and then makes that data available to applications and other entities that otherwise typically would not have access to network data), the one or more control signals to cause the one or more devices to modify performance of the core network (¶0033 see network API service 158 may provide “guidance” APIs that analyze network data and provide insights to applications (e.g., predictions of future network performance) that enable applications to adapt based on the guidance), wherein the one or more control signals are generated by the controller using information from a transport network and an access network (¶0033 see API service 158 may also provide an analytics engine that ingests data streams from multiple sources and output metrics of interest to applications in real time. Network API service 158 may track these metrics separately for each user and may provide accurate estimates (e.g., wireless/cellular performance) for a given user. In some embodiments, control APIs utilize various controllers for access and core networks (e.g., radio access network (RAN) intelligent controller, 5G Network Exposure Function (NEF), etc.). These and other controllers may be exposed by network API service 158 to external applications (and users) for them to request features from the network in an on-demand manner.. control APIs utilize various controllers for access and core networks) Regarding claims 2, 9, 16. Sharma further teaches one or more processors of claim 1, wherein the core network, the access network, and transport network are comprised in a computing network, and the one or more devices are to perform wireless service using 5G, 6G, or 3GPP communication standards (¶0031 see 5G and wireless access, ¶0134 see transport layer, Fig 2A see access and core networks) Regarding claim 3, 10, 17. Sharma further teaches one or more processors of claim 1, wherein the controller is to receive information from one or more multi-access edge computing networks (MEC), and wherein the controller is to use the received information to generate network settings of the one or more MECs (¶0023 see embodiments combine data from multiple access and core networks to provide guidance to applications ¶0033 see network API service 158 may tap into data sources from multiple access networks (e.g., cellular, fixed-access) as well as core networks (e.g., mobility core, IP backbone). Network API service 158 may also provide an analytics engine that ingests data streams from multiple sources and output metrics of interest to applications in real time. Network API service 158 may track these metrics separately for each user and may provide accurate estimates (e.g., wireless/cellular performance) for a given user ¶0072 see network API services are implemented in a network core or on network edges, or in cloud-based network edge locations). Regarding claims 4, 11, 18. Sharma further teaches one or more processors of claim 1, wherein the controller is to receive information from the core network, the access network, and the transport network, wherein each of the core network, access network, and transport networks are 5G networks (Fig 2D ¶0033 see control APIs utilize various controllers for access and core networks (e.g., radio access network (RAN) intelligent controller, 5G Network Exposure Function (NEF), etc.). These and other controllers may be exposed by network API service ¶0068 see FIG. 2D is a block diagram illustrating an example, non-limiting embodiment of a network API service providing control functionality in accordance with various aspects described herein. FIG. 2D shows all of the elements of FIG. 2C with the addition of access controller 210D and core controller 220D. In embodiments represented by FIG. 2D, network API service 158 may modify network features within access network 220A using access controller 210D, and may modify network features within core network 230A using core controller 220D) Regarding claim 5. Sharma further teaches one or more processors of claim 1, wherein the controller is to receive one or more parameters to identify the one or more devices within the core network (¶0102 see a request to authenticate a UE device to a network API service is performed. In some embodiments, this corresponds to a UE device authenticating on behalf of an application running on the device, on behalf of the device itself, or on behalf of a user to which the UE device is registered. At 220F, an authentication nonce is received. As described above, the authentication nonce may be a cryptographic nonce, a non-cryptographic nonce, or any other identifier capable of identifying a user to a network API service.) Regarding claim 6, 13. Sharma further teaches one or more processors of claim 1, wherein the API call is further to cause the controller to communicate the one or more control signals to at least one access device, the at least one access device within the access network, wherein the API includes a request for the at least one access device to receive the one or more control signals (¶0042 see access network 220A may be any type (or any number) of access networks that enables UE 210A to communicate with core network 230A. For example, access network 220A may be any of the access networks described above with reference to FIG. 1 . Access network 220A may include many devices or elements capable of providing data to network API service 158 at 222A. For example, access network 220A may include network routers, switches, cellular base stations). Regarding claim 7, 14, 20. Sharma further teaches one or more processors of claim 1, wherein the controller performs one or more neural networks to generate network settings, based, at least, in part on the information from the transport network and access network (¶0077 see embodiments described herein can also employ artificial intelligence (AI) to facilitate automating one or more features described herein. The embodiments (e.g., in connection with automatically identifying acquired cell sites that provide a maximum value/benefit after addition to an existing communication network) can employ various AI-based schemes for carrying out various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of each cell site of the acquired network. A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, . . . , xn), to a confidence that the input belongs to a class, that is, f(x)=confidence (class).. classification approaches comprise, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed). Regarding claim 12. Sharma further teaches the system of claim 8, wherein the API is to further cause the controller to identify the one or more devices within the core network based, at least in part, on one or more parameters of the API (¶0102 see a request to authenticate a UE device to a network API service is performed. In some embodiments, this corresponds to a UE device authenticating on behalf of an application running on the device, on behalf of the device itself, or on behalf of a user to which the UE device is registered. At 220F, an authentication nonce is received. As described above, the authentication nonce may be a cryptographic nonce, a non-cryptographic nonce, or any other identifier capable of identifying a user to a network API service.) Regarding claim 19. Sharma further teaches the method of claim 15, wherein the method further comprises: identifying the one or more devices within the core network, in response to the controller calling the API, wherein the API comprises parameters indicating the one or more devices to receive the one or more control signals (¶0102 see a request to authenticate a UE device to a network API service is performed. In some embodiments, this corresponds to a UE device authenticating on behalf of an application running on the device, on behalf of the device itself, or on behalf of a user to which the UE device is registered. At 220F, an authentication nonce is received. As described above, the authentication nonce may be a cryptographic nonce, a non-cryptographic nonce, or any other identifier capable of identifying a user to a network API service.) Conclusion THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. References are cited not only for their quoted language but for all that they teach. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Atta Khan whose telephone number is 571-270-7364. The examiner can normally be reached on M-F 09:00-6:00. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Vivek Srivastava can be reached on (571) 272-7304. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /ATTA KHAN/ Examiner, Art Unit 2449
Read full office action

Prosecution Timeline

Show 12 earlier events
Dec 06, 2024
Notice of Allowance
Jul 03, 2025
Request for Continued Examination
Jul 09, 2025
Response after Non-Final Action
Sep 08, 2025
Non-Final Rejection mailed — §102, §DOUBLEPATENT
Mar 09, 2026
Response Filed
Apr 08, 2026
Final Rejection mailed — §102, §DOUBLEPATENT
Aug 06, 2026
Examiner Interview Summary
Aug 06, 2026
Applicant Interview (Telephonic)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12705344
SECURITY ASSOCIATION LOOKUP IN COMMUNICATION SYSTEM DEPLOYMENTS
2y 3m to grant Granted Aug 11, 2026
Patent 12701046
AUTOMATED INSPECTION OF NETWORK STATE
1y 7m to grant Granted Aug 04, 2026
Patent 12694123
SYSTEM AND METHOD FOR DEFENSE IN DEPTH OF ONE OR MORE SOFTWARE DELIVERY PIPELINES
2y 10m to grant Granted Jul 28, 2026
Patent 12694206
COMPUTERIZED SYSTEM AND METHOD FOR CONTROLLING ELECTRONIC MESSAGES AND THEIR RESPONSES AFTER DELIVERY
2y 6m to grant Granted Jul 28, 2026
Patent 12695798
DOCUMENT-SHARING CONFERENCING SYSTEM
2y 10m to grant Granted Jul 28, 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

5-6
Expected OA Rounds
84%
Grant Probability
99%
With Interview (+25.3%)
2y 6m (~0m remaining)
Median Time to Grant
High
PTA Risk
Based on 331 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