DETAILED ACTION
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 .
Application, submitted on 01/10/2024, has been received, entered, and made of record. Currently, claims 1-20 remain pending in the application.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 01/10/2024 was filed in compliance with the provisions of 37 CFR 1.97 and 1.98. Accordingly, the information disclosure statement is being considered by the examiner. However, Applicant has not provided an explanation of relevance of cited document(s).
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 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 nonstatutory 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 nonstatutory 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 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent No.US 11,910,286 B2. Although the claims at issue are not identical, they are not patentably distinct from each other because it is clear that most of the elements of the instant application claims are to be found in the patent claims. The difference between the claims lies in the fact that the patent claims include many more elements and are thus much more specific. Since instant application claims are obvious over the patent claims, thus they are not patentably distinct from the patent claims. “A later patent claim is not patentably distinct from an earlier patent claim if the later claim is obvious over, or anticipated by, the earlier claim. In re Longi, 759 F.2d at 896, 225 USPQ at 651 (affirming a holding of obviousness-type double patenting because the claims at issue were obvious over claims in four prior art patents); In re Berg, 140 F.3d at 1437, 46 USPQ2d at 1233 (Fed. Cir. 1998) (affirming a holding of obviousness-type double patenting where a patent application claim to a genus is anticipated by a patent claim to a species within that genus). “ELI LILLY AND COMPANY v BARR LABORATORIES, INC., United States Court of Appeals for the Federal Circuit, ON PETITION FOR REHEARING EN BANC (DECIDED: May 30, 2001).
Instant Application 18/409,623
U.S. Patent No.US 11,910,286 B2
1. A computer-implemented method for continuous integration and continuous delivery (CI/CD) and orchestration integration in a wireless network system, the method comprising:
electronically pulling artifacts from a vendor gateway to appropriate service provider blocks;
electronically populating containerized network function (CNF) into a service catalog;
electronically building infrastructure via clusters and namespaces, depending on levels of isolation;
electronically building a service on the infrastructure;
electronically running tests on the wireless network system within the infrastructure; and
electronically collecting and analyzing logs, traces or events resulting from the running of the tests.
1. A computer-implemented method for continuous integration and continuous delivery (CI/CD) and orchestration integration in a wireless network system, the method comprising:
electronically pulling artifacts from a vendor gateway to appropriate service provider blocks;
electronically populating containerized network function (CNF) into a service catalog;
electronically building infrastructure via clusters and namespaces, depending on levels of isolation;
electronically building a service on the infrastructure;
electronically running tests on the wireless network system within the infrastructure;
electronically collecting and analyzing logs, traces or events resulting from the running of the tests;
2. The method of claim 1 wherein the service is a slice, a containerized network function (CNF), or multiple CNFs.
2. The method of claim 1 wherein the service is a slice, a containerized network function (CNF), or multiple CNFs.
3. The method of claim 2 further comprising a Network Services Orchestrator (NSO) receiving requests on a northbound interface with a Customer Facing Service (CFS) and a Resource Facing Service (RFS) defined according to an application programming interface (API).
3. The method of claim 2 further comprising a Network Services Orchestrator (NSO) receiving requests on a northbound interface with a Customer Facing Service (CFS) and a Resource Facing Service (RFS) defined according to an application programming interface (API).
4. The method of claim 3 wherein the RFS includes individual resources.
4. The method of claim 3 wherein the RFS includes individual resources.
5. The method of claim 3 wherein the RFS includes an entire slice as a resource.
5. The method of claim 3 wherein the RFS includes an entire slice as a resource.
6. The method of claim 5 wherein a southbound interface is based on European Telecommunications Standards Institute (ETSI) SOL, Internet Engineering Task Force (IETF) and Open Radio Access Network (RAN) specifications of the O-RAN Alliance to accommodate domains natively.
6. The method of claim 5 wherein a southbound interface is based on European Telecommunications Standards Institute (ETSI) SOL, Internet Engineering Task Force (IETF) and Open Radio Access Network (RAN) specifications of the O-RAN Alliance to accommodate domains natively.
7. The method of claim 1 wherein a CI/CD interface to orchestration that implements the continuous integration and continuous delivery (CI/CD) and orchestration integration comprises four sub interfaces including: an interface to service orchestrator, a catalog interface, an interface to a registry, and an interface to policy.
7. The method of claim 1 wherein a CI/CD interface to orchestration that implements the continuous integration and continuous delivery (CI/CD) and orchestration integration comprises four sub interfaces including: an interface to service orchestrator, a catalog interface, an interface to a registry, and an interface to policy.
8. The method of claim 7 further comprising: the CI/CD interface instantiating RFS for a test slice; and the CI/CD interface creating test users.
8. The method of claim 7 further comprising: the CI/CD interface instantiating RFS for a test slice; and the CI/CD interface creating test users.
9. The method of claim 1 wherein business operations of the service and a test process for running the tests are distinguished by tags only.
9. The method of claim 1 wherein business operations of the service and a test process for running the tests are distinguished by tags only.
10. A system comprising:
at least one computer processor;
a network interface for receiving information; and
a non-transitory memory communicatively coupled to the computer processor having computer-executable instructions stored thereon that when executed by the computer processor cause the computer processor to perform:
electronically pulling artifacts from a vendor gateway to appropriate service provider blocks;
electronically populating containerized network function (CNF) into a service catalog;
electronically building infrastructure via clusters and namespaces, depending on levels of isolation;
electronically building a service on the infrastructure;
electronically running tests on the wireless network system within the infrastructure; and
electronically collecting and analyzing logs, traces or events resulting from the running of the tests.
10. A system comprising:
at least one computer processor;
a network interface for receiving information; and
a non-transitory memory communicatively coupled to the computer processor having computer-executable instructions stored thereon that when executed by the computer processor cause the computer processor to perform:
electronically pulling artifacts from a vendor gateway to appropriate service provider blocks;
electronically populating containerized network function (CNF) into a service catalog;
electronically building infrastructure via clusters and namespaces, depending on levels of isolation;
electronically building a service on the infrastructure;
electronically running tests on the wireless network system within the infrastructure;
electronically collecting and analyzing logs, traces or events resulting from the running of the tests;
11. The system of claim 10 wherein the service is a slice, a containerized network function (CNF), or multiple CNFs.
11. The system of claim 10 wherein the service is a slice, a containerized network function (CNF), or multiple CNFs.
12. The system of claim 11 further comprising a Network Services Orchestrator (NSO) receiving requests on a northbound interface with a Customer Facing Service (CFS) and a Resource Facing Service (RFS) defined according to an application programming interface (API).
12. The system of claim 11 further comprising a Network Services Orchestrator (NSO) receiving requests on a northbound interface with a Customer Facing Service (CFS) and a Resource Facing Service (RFS) defined according to an application programming interface (API).
13. The system of claim 12 wherein the RFS includes individual resources.
13. The system of claim 12 wherein the RFS includes individual resources.
14. The system of claim 12 wherein the RFS includes an entire slice as a resource.
14. The system of claim 12 wherein the RFS includes an entire slice as a resource.
15. The system of claim 14 wherein a southbound interface is based on European Telecommunications Standards Institute (ETSI) SOL, Internet Engineering Task Force (IETF) and Open Radio Access Network (RAN) specifications of the O-RAN Alliance to accommodate domains natively.
15. The system of claim 14 wherein a southbound interface is based on European Telecommunications Standards Institute (ETSI) SOL, Internet Engineering Task Force (IETF) and Open Radio Access Network (RAN) specifications of the O-RAN Alliance to accommodate domains natively.
16. At least one non-transitory computer-readable medium that stores instructions that when executed by at least one computer processor cause the at least one computer processor to perform: electronically pulling artifacts from a vendor gateway to appropriate service provider blocks;
electronically populating containerized network function (CNF) into a service catalog;
electronically building infrastructure via clusters and namespaces, depending on levels of isolation;
electronically building a service on the infrastructure;
electronically running tests on the wireless network system within the infrastructure; and
electronically collecting and analyzing logs, traces or events resulting from the running of the tests.
16. At least one non-transitory computer-readable medium that stores instructions that when executed by at least one computer processor cause the at least one computer processor to perform: electronically pulling artifacts from a vendor gateway to appropriate service provider blocks;
electronically populating containerized network function (CNF) into a service catalog;
electronically building infrastructure via clusters and namespaces, depending on levels of isolation;
electronically building a service on the infrastructure;
electronically running tests on the wireless network system within the infrastructure;
electronically collecting and analyzing logs, traces or events resulting from the running of the tests;
17. The at least one non-transitory computer-readable medium of claim 16 wherein the service is a slice, a containerized network function (CNF), or multiple CNFs.
17. The at least one non-transitory computer-readable medium of claim 16 wherein the service is a slice, a containerized network function (CNF), or multiple CNFs.
18. The at least one non-transitory computer-readable medium of claim 17 further comprising a Network Services Orchestrator (NSO) receiving requests on a northbound interface with a Customer Facing Service (CFS) and a Resource Facing Service (RFS) defined according to an application programming interface (API).
18. The at least one non-transitory computer-readable medium of claim 17 further comprising a Network Services Orchestrator (NSO) receiving requests on a northbound interface with a Customer Facing Service (CFS) and a Resource Facing Service (RFS) defined according to an application programming interface (API).
19. The at least one non-transitory computer-readable medium of claim 16 wherein the instructions, when executed by the at least one computer processor, further cause the at least one computer processor to perform providing a CI/CD interface allowing for dynamic changes including by instantiating a Resource Facing Service (RFS) for a test slice using the CI/CD interface, which is a same northbound interface on which requests are received with a Customer Facing Service (CFS).
19. The at least one non-transitory computer-readable medium of claim 16 wherein the instructions, when executed by the at least one computer processor, further cause the at least one computer processor to perform providing a CI/CD interface allowing for dynamic changes including by instantiating a Resource Facing Service (RFS) for a test slice using the CI/CD interface, which is a same northbound interface on which requests are received with a Customer Facing Service (CFS).
20. The at least one non-transitory computer-readable medium of claim 16 wherein the instructions, when executed by the at least one computer processor, further cause the at least one computer processor to perform using same call-flow for business operations and test processes, but distinguishing the business operations and test processes via tags that are carried until ending of the business operations and test processes.
20. The at least one non-transitory computer-readable medium of claim 16 wherein the instructions, when executed by the at least one computer processor, further cause the at least one computer processor to perform using same call-flow for business operations and test processes, but distinguishing the business operations and test processes via tags that are carried until ending of the business operations and test processes.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MOUSTAPHA DIABY whose telephone number is (571)270-1669. The examiner can normally be reached Monday-Friday: 9AM-6PM.
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, ABDERRAHIM MEROUAN can be reached at (571) 270-5254. 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.
/MOUSTAPHA DIABY/
Primary Examiner, Art Unit 2683