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
1. This action is in response to the application filed on 03 September 2024.
Claims 1-18 are presently pending for examination.
Information Disclosure Statement
2. The information disclosure statement (IDS) submitted on 06/03/2025 has being considered by the examiner.
Double Patenting
3. 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); 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.
Claims 1-18 are rejected under 35 U.S.C. 101 as claiming the same invention as that of claims 1-18 of prior U.S. Patent No. 12081391. This is a statutory double patenting rejection.
4. Double Patenting
Instant Application: 18/823,580
Patent No: 12081391
1. A method for providing singleton micro-service high availability in a telecommunications network, comprising: providing a front-end microservice for terminating an inbound telecom interface; providing a plurality of back-end microservices acting as worker pods; providing an internal controller for monitoring the health of the front-end microservice and the plurality of back-end microservices; identifying, by the internal controller, that the front-end microservice has crashed; initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active; matching a singleton micro-service selector label criterion; advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and receiving, by the newly relabeled pod in the telecommunications network, traffic directed on an IP address of the singleton micro-service.
2. The method of claim 1, wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.
3. The method of claim 1, wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.
4. The method of claim 1, wherein a database handles registration of the front-end microservice and the plurality of back-end microservices.
5. The method of claim 1, further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.
6. The method of claim 1, further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active.”
7. A non-transitory computer-readable medium, which, when executed by at least one processor, causes the at least one processor to perform steps, the steps further comprising: identifying, by an internal controller in a telecommunications network, the internal controller for monitoring the health of a front-end microservice and a plurality of back-end microservices, that the front-end microservice has crashed; initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active; matching a singleton micro-service selector label criterion; advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and receiving, by the newly relabeled pod in the telecommunications network, traffic directed on an IP address of the singleton micro-service, wherein the front-end microservice is for terminating an inbound telecom interface; and wherein the plurality of back-end microservices act as worker pods.
8. The non-transitory computer-readable medium of claim 7, wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.
9. The non-transitory computer-readable medium of claim 7, wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.
10. The non-transitory computer-readable medium of claim 7, wherein a database handles registration of the front-end microservice and the plurality of back-end microservices.
11. The non-transitory computer-readable medium of claim 7, the instructions further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.
12. The non-transitory computer-readable medium of claim 7, the instructions further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active.”
13. A system, comprising: a front-end microservice for terminating an inbound telecom interface, in a telecommunications network; a plurality of back-end microservices acting as worker pods, in the telecommunications network; and an internal controller for monitoring the health of the front-end microservice and the plurality of back-end microservices, in the telecommunications network, wherein the internal controller further comprises instructions that, when executed by a processor, causes the internal controller to: identify that the front-end microservice has crashed; initiate a label change for an existing similar pod labeled as standby to active; match a singleton micro-service selector label criterion; and advertise the newly re-labeled existing similar pod as part of a singleton micro-service, thereby causing the newly relabeled pod in the telecommunications network to receive traffic directed on an IP address of the singleton micro-service.
14. The system of claim 13, wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.
15. The system of claim 13, wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.
16. The system of claim 13, further comprising a database for handling registration of the front-end microservice and the plurality of back-end microservices.
17. The system of claim 13, further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.
18. The system of claim 13, further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active.”
1. A method for providing singleton micro-service high availability in a telecommunications network, comprising: providing a front-end microservice for terminating an inbound telecom interface; providing a plurality of back-end microservices acting as worker pods; providing an internal controller for monitoring the health of the front-end microservice and the plurality of back-end microservices; identifying, by the internal controller, that the front-end microservice has crashed; initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active; matching a singleton micro-service selector label criterion; advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and receiving, by the newly relabeled pod in the telecommunications network, traffic directed on an IP address of the singleton micro-service.
2. The method of claim 1, wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.
3. The method of claim 1, wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.
4. The method of claim 1, wherein a database handles registration of the front-end microservice and the plurality of back-end microservices.
5. The method of claim 1, further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.
6. The method of claim 1, further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active”.
7. A non-transitory computer-readable medium, which, when executed by at least one processor, causes the at least one processor to perform steps, the steps further comprising: identifying, by an internal controller in a telecommunications network, the internal controller for monitoring the health of a front-end microservice and a plurality of back-end microservices, that the front-end microservice has crashed; initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active; matching a singleton micro-service selector label criterion; advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and receiving, by the newly relabeled pod in the telecommunications network, traffic directed on an IP address of the singleton micro-service, wherein the front-end microservice is for terminating an inbound telecom interface; and wherein the plurality of back-end microservices act as worker pods.
8. The non-transitory computer-readable medium of claim 7, wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.
9. The non-transitory computer-readable medium of claim 7, wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.
10. The non-transitory computer-readable medium of claim 7, wherein a database handles registration of the front-end microservice and the plurality of back-end microservices.
11. The non-transitory computer-readable medium of claim 7, the instructions further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.
12. The non-transitory computer-readable medium of claim 7, the instructions further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active”.
13. A system, comprising: a front-end microservice for terminating an inbound telecom interface, in a telecommunications network; a plurality of back-end microservices acting as worker pods, in the telecommunications network; and an internal controller for monitoring the health of the front-end microservice and the plurality of back-end microservices, in the telecommunications network, wherein the internal controller further comprises instructions that, when executed by a processor, causes the internal controller to: identify that the front-end microservice has crashed; initiate a label change for an existing similar pod labeled as standby to active; match a singleton micro-service selector label criterion; and advertise the newly re-labeled existing similar pod as part of a singleton micro-service, thereby causing the newly relabeled pod in the telecommunications network to receive traffic directed on an IP address of the singleton micro-service.
14. The system of claim 13, wherein the inbound telecom interface is an E1 interface with a CU-UP node in a telecommunications network.
15. The system of claim 13, wherein the inbound telecom interface is an NG interface with one or more of an AMF node and an SMF node in a telecommunications network.
16. The system of claim 13, further comprising a database for handling registration of the front-end microservice and the plurality of back-end microservices.
17. The system of claim 13, further comprising using a selector that is a free text field that accepts key-value pairs, the selector including a value that indicates that the pod is selected as active.
18. The system of claim 13, further comprising using a selector that is a free text field that accepts key-value pairs, the selector having the value “active”.
Conclusion
5. Any inquiry concerning this communication or earlier communications from the examiner should be directed to MOHAMED IBRAHIM whose telephone number is (571)270-1132. The examiner can normally be reached on Monday through Friday from 9:30AM to 6:00PM.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, John Follansbee can be reached on 571-272-3964. 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.
/Mohamed Ibrahim/
Primary Examiner, Art Unit 2444