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 .
This is a first office action in response to an application for letters patent filed on 17 September 2024. Claims 1-20 are presented for examination.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 09/17/2024 was filed before the mailing date of the first office action on the merits. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
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. 12155730 and 11765240. Although the claims at issue are not identical, they are not patentably distinct from each other because the claims of the instant application are arguably broader than the claims of the patents, which encompass the same metes, bounds, and limitations. It must be noted that for patent number “730”, only the steps of “generating a first distributed publication/subscription (pub/sub) as a service (DPAAS)” are missing in the method claim. In regard to patent “240” the steps of “receive, via an onboarding interface, a configuration of a first publication/subscription (pub/sub) library” are missing in the application.
Therefore, it would be obvious to a skill artisan before the effective filing date of the invention as claimed to eliminate the limitations of the narrower claims, since it has been held that omission of an element and its functions and a combination where the remaining elements perform the same functions as before involves only routine skills in the art.
See in re Karlson, 136 USPQ 184.
On the table below, the claims numbers are side by side. However, the claims are matched according to their similarities. System with system and method with method.
CLAIM #
APPLICATION #: 18887903
Patent # 11765240
1
Non-transitory computer-readable media storing computer-readable instructions that, when executed by a processor, cause a distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform to: map, by an onboarding interface, functions of a DPAAS library to corresponding functions of a first pub/sub library as a first DPAAS mapping; receive, via a DPAAS library engine, a publication request from a first service; initiate, between a host computing platform and a messaging server, a communication connection via the first DPAAS mapping, wherein the first service is associated with the host computing platform; and publish, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
A system comprising: a host computing platform hosting at least one first service publishing information to a network and/or a second service subscribing to one or more information services; a distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform, comprising: at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: receive, via an onboarding interface, a configuration of a first pub/sub library; map, by the onboarding interface, functions of a DPAAS library to corresponding functions of the first pub/sub library as a first DPAAS mapping; receive, via a DPAAS library engine, a publication request from the first service; initiate, between the host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and publish, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
2
The non-transitory computer-readable media of claim 1, wherein the instructions further cause the DPAAS computing platform to: map, by the onboarding interface, functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; receive, via the DPAAS library engine, a subscription request from a second service; initiate, between the host computing platform and the messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
The system of claim 1, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: receive, via the onboarding interface, a configuration of a second pub/sub library; map, by the onboarding interface, functions of the DPAAS library to corresponding functions of the second pub/sub library as a second DPAAS mapping; receive, via the DPAAS library engine, a subscription request from the second service; initiate, between the host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
3
The non-transitory computer-readable media of claim 2, wherein the first pub/sub library is different from the second pub/sub library.
The system of claim 2, wherein the first pub/sub library is different from the second pub/sub library.
4
The non-transitory computer-readable media of claim 2 wherein the first pub/sub library is incompatible with the second pub/sub library.
The system of claim 2 wherein the first pub/sub library is incompatible with the second pub/sub library.
5
The non-transitory computer-readable media of claim 4, wherein the requested topic comprises the first topic
The system of claim 4, wherein the requested topic comprises the first topic.
6
The non-transitory computer-readable media of claim 4, wherein the requested topic is a second topic different from the first topic.
The system of claim 4, wherein the requested topic is a second topic different from the first topic.
7
The non-transitory computer-readable media of claim 5, wherein the instructions further cause the DPAAS computing platform to log, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
The system of claim 5, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: log, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
8
The non-transitory computer-readable media of claim 1, wherein the instructions further cause the DPAAS computing platform to log, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
The system of claim 1, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: log, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
9
A method comprising: generating a first distributed publication/subscription (pub/sub) as a service (DPAAS) mapping corresponding to relationships between functions of a DPAAS library to corresponding functions of a first pub/sub library; receiving, via a DPAAS library engine, a publication request from a first service; initiating, between a host computing platform and a messaging server based on the first DPAAS mapping, a communication connection; and publishing, via the DPAAS mapping by the first service, a first topic.
A method comprising: receiving, via an onboarding interface, a configuration of a first pub/sub library; mapping, by an onboarding portal, functions of a distributed publication/subscription (pub/sub) as a service (DPAAS) library to corresponding functions of the first pub/sub library as a first DPAAS mapping; receiving, via a DPAAS library engine, a publication request from a first service; initiating, between a host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and publishing, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
10
The method of claim 9, further comprising: mapping functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; receiving, via the DPAAS library engine, a subscription request from a second service; initiating, between the host computing platform and the messaging server, a communication connection via the first DPAAS mapping; and subscribing, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
The method of claim 9, further comprising: receiving, via the onboarding interface, a configuration of a second pub/sub library; mapping, by the onboarding interface, functions of the DPAAS library to corresponding functions of the second pub/sub library as a second DPAAS mapping; receiving, via the DPAAS library engine, a subscription request from a second service; initiating, between the host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and subscribing, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
11
The method of claim 10, wherein the first pub/sub library is different from the second pub/sub library.
The method of claim 10, wherein the first pub/sub library is different from the second pub/sub library.
12
The method of claim 10, wherein the first pub/sub library is incompatible with the second pub/sub library.
The method of claim 10, wherein the first pub/sub library is incompatible with the second pub/sub library.
13
The method of claim 12, wherein the requested topic comprises the first topic.
The method of claim 12, wherein the requested topic comprises the first topic.
14
The method of claim 12, wherein the requested topic is a second topic different from the first topic.
The method of claim 12, wherein the requested topic is a second topic different from the first topic.
15
The method of claim 14, further comprising logging, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
The method of claim 14, further comprising logging, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
16
The method of claim 9, further comprising logging, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
The method of claim 9, further comprising logging, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
17
A system comprising: a first host computing platform hosting at least one first service publishing information to a network; a second host computing platform hosting a second service subscribing to one or more information services; a distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform, comprising: at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: generate a first DPAAS mapping between functions of a DPAAS library and corresponding functions of a first pub/sub library; initiate, based on the first DPAAS mapping, a communication connection for the first service; and publish, via the DPAAS mapping by the first service, a first topic.
Non-transitory computer readable media storing instructions that, when executed by a processor, cause a DPAAS computing platform to: receive, via an onboarding interface, a configuration of a first publication/subscription (pub/sub) library; map, by the onboarding interface, functions of a DPAAS library to corresponding functions of the first pub/sub library as a first DPAAS mapping; receive, via a DPAAS library engine, a publication request from a first service; initiate, between a host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and publish, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
18
The system of claim 17, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: map functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; initiate, based on a subscription request from the second service and between the host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the second service and based on a confirmed connection between the second host computing platform and the messaging server, to a requested topic.
The non-transitory computer readable media of claim 17, wherein the instructions cause a distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform to: receive, via the onboarding interface, a configuration of a second pub/sub library; map, by the onboarding interface, functions of the DPAAS library to corresponding functions of the second pub/sub library as a second DPAAS mapping; receive, via the DPAAS library engine, a subscription request from a second service; initiate, between the host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
19. The system of claim 18, wherein the first pub/sub library is different from the second pub/sub library.
19. The non-transitory computer readable media of claim 17, wherein the first pub/sub library is different from a second pub/sub library.
20. The system of claim 18, wherein the first pub/sub library is incompatible with the second pub/sub library.
20. The non-transitory computer readable media of claim 17, wherein the first pub/sub library is incompatible with a second pub/sub library.
Application #: 18887903
Patent #: 12155730
1. Non-transitory computer-readable media storing computer-readable instructions that, when executed by a processor, cause a distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform to: map, by an onboarding interface, functions of a DPAAS library to corresponding functions of a first pub/sub library as a first DPAAS mapping; receive, via a DPAAS library engine, a publication request from a first service; initiate, between a host computing platform and a messaging server, a communication connection via the first DPAAS mapping, wherein the first service is associated with the host computing platform; and publish, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
1.A distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform, comprising: at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: map, by an onboarding interface, functions of a DPAAS library to corresponding functions of a first pub/sub library as a first DPAAS mapping; receive, via a DPAAS library engine, a publication request from a first service; initiate, between a host computing platform and a messaging server, a communication connection via the first DPAAS mapping, wherein the first service is associated with the host computing platform; and publish, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
2. The non-transitory computer-readable media of claim 1, wherein the instructions further cause the DPAAS computing platform to: map, by the onboarding interface, functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; receive, via the DPAAS library engine, a subscription request from a second service; initiate, between the host computing platform and the messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
2. The DPAAS computing platform of claim 1, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: map, by the onboarding interface, functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; receive, via the DPAAS library engine, a subscription request from a second service; initiate, between the host computing platform and the messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
3. The non-transitory computer-readable media of claim 2, wherein the first pub/sub library is different from the second pub/sub library.
3. The DPAAS computing platform of claim 2, wherein the first pub/sub library is different from the second pub/sub library.
4. The non-transitory computer-readable media of claim 2 wherein the first pub/sub library is incompatible with the second pub/sub library.
4. The DPAAS computing platform of claim 2 wherein the first pub/sub library is incompatible with the second pub/sub library.
5. The non-transitory computer-readable media of claim 4, wherein the requested topic comprises the first topic.
5. The DPAAS computing platform of claim 4, wherein the requested topic comprises the first topic.
6. The non-transitory computer-readable media of claim 4, wherein the requested topic is a second topic different from the first topic.
6. The DPAAS computing platform of claim 4, wherein the requested topic is a second topic different from the first topic.
7. The non-transitory computer-readable media of claim 5, wherein the instructions further cause the DPAAS computing platform to log, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
7. The DPAAS computing platform of claim 5, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: log, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
8. The non-transitory computer-readable media of claim 1, wherein the instructions further cause the DPAAS computing platform to log, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
8. The DPAAS computing platform of claim 1, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: log, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
9. A method comprising: generating a first distributed publication/subscription (pub/sub) as a service (DPAAS) mapping corresponding to relationships between functions of a DPAAS library to corresponding functions of a first pub/sub library; receiving, via a DPAAS library engine, a publication request from a first service; initiating, between a host computing platform and a messaging server based on the first DPAAS mapping, a communication connection; and publishing, via the DPAAS mapping by the first service, a first topic.
9. A method comprising: mapping, by an onboarding portal, functions of a distributed publication/subscription (pub/sub) as a service (DPAAS) library to corresponding functions of a first pub/sub library as a first DPAAS mapping; receiving, via a DPAAS library engine, a publication request from a first service; initiating, between a host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and publishing, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
10. The method of claim 9, further comprising: mapping functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; receiving, via the DPAAS library engine, a subscription request from a second service; initiating, between the host computing platform and the messaging server, a communication connection via the first DPAAS mapping; and subscribing, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
10. The method of claim 9, further comprising: mapping, by the onboarding portal, functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; receiving, via the DPAAS library engine, a subscription request from a second service; initiating, between the host computing platform and the messaging server, a communication connection via the first DPAAS mapping; and subscribing, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, to a requested topic.
11. The method of claim 10, wherein the first pub/sub library is different from the second pub/sub library.
11. The method of claim 10, wherein the first pub/sub library is different from the second pub/sub library.
12. The method of claim 10, wherein the first pub/sub library is incompatible with the second pub/sub library.
12. The method of claim 10, wherein the first pub/sub library is incompatible with the second pub/sub library.
13. The method of claim 12, wherein the requested topic comprises the first topic.
13. The method of claim 12, wherein the requested topic comprises the first topic.
14. The method of claim 12, wherein the requested topic is a second topic different from the first topic.
14. The method of claim 12, wherein the requested topic is a second topic different from the first topic.
15. The method of claim 14, further comprising logging, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
15. The method of claim 14, further comprising logging, via a logging service to a big data repository, confirmation of a successful subscription to the requested topic.
16. The method of claim 9, further comprising logging, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
16. The method of claim 9, further comprising logging, via a logging service to a big data repository, confirmation of a successful creation to the first topic.
17. A system comprising: a first host computing platform hosting at least one first service publishing information to a network; a second host computing platform hosting a second service subscribing to one or more information services; a distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform, comprising: at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: generate a first DPAAS mapping between functions of a DPAAS library and corresponding functions of a first pub/sub library; initiate, based on the first DPAAS mapping, a communication connection for the first service; and publish, via the DPAAS mapping by the first service, a first topic.
17. A system comprising: a first host computing platform hosting at least one first service publishing information to a network; a second host computing platform hosting a second service subscribing to one or more information services; a distributed publication/subscription (pub/sub) as a service (DPAAS) computing platform, comprising: at least one processor; and memory storing computer-readable instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: map, by an onboarding portal, functions of a DPAAS library to corresponding functions of a first pub/sub library as a first DPAAS mapping; initiate, based on a publication request from the first service and between the first host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and publish, via the DPAAS mapping by the first service and based on a confirmed connection between the first host computing platform and the messaging server, a first topic.
18. The system of claim 17, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: map functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; initiate, based on a subscription request from the second service and between the host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the second service and based on a confirmed connection between the second host computing platform and the messaging server, to a requested topic.
18. The system of claim 17, wherein the instructions that, when executed by the at least one processor, cause the DPAAS computing platform to: map, by the onboarding portal, functions of the DPAAS library to corresponding functions of a second pub/sub library as a second DPAAS mapping; initiate, based on a subscription request from the second service and between the host computing platform and a messaging server, a communication connection via the first DPAAS mapping; and subscribe, via the DPAAS mapping by the second service and based on a confirmed connection between the second host computing platform and the messaging server, to a requested topic.
19. The system of claim 18, wherein the first pub/sub library is different from the second pub/sub library.
19. The system of claim 18, wherein the first pub/sub library is different from the second pub/sub library.
19. The system of claim 18, wherein the first pub/sub library is different from the second pub/sub library.
20. The system of claim 18, wherein the first pub/sub library is incompatible with the second pub/sub library.
20. The system of claim 18 wherein the first pub/sub library is incompatible with the second pub/sub library.
Claims 1-20 are allowed over the prior art.
The prior art fails to teach map, by an onboarding interface, functions of a DPAAS library to corresponding functions of a first pub/sub library as a first DPAAS mapping; receive, via a DPAAS library engine, a publication request from a first service; initiate, between a host computing platform and a messaging server, a communication connection via the first DPAAS mapping, wherein the first service is associated with the host computing platform; and publish, via the DPAAS mapping by the first service and based on a confirmed connection between the host computing platform and the messaging server, a first topic.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to FRANTZ B JEAN whose telephone number is (571)272-3937. The examiner can normally be reached 8-5 M-F.
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, Glenton B. Burgess can be reached at 5712723949. The fax phone number for the organization where this Glenton Burgess 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.
/FRANTZ B JEAN/Primary Examiner, Art Unit 2454