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 .
Response to Amendment
The amendment filed 06/22/26 has been entered.
Amended claims:
1) Independent claims: 1, 10 and 17.
Claim Status
Claims 1-17 are pending. They comprise of 3 independent groups:
(1) System1: 1-9, and
(2) Method1: 10-16, and
(3) Article: 17.
As of 06/22/2026, independent claim 1 is as followed:
(Currently Amended): A system for business process automation, the system comprising:
[I] a connect manager configured to register and manage a plurality of application programming interface (API) information for services, by assigning management identifiers (IDs) respectively mapped to a plurality of API information and the services;
[II] a process execution engine configured to execute, in conjunction with a connect broker, a target business process comprising a plurality of tasks, wherein the process execution engine configured to, based on identifying that a current task among the plurality of tasks is a particular service task, which is a task using a particular service provided by a service module, transmit a request to the connect broker to process the particular service task; and
[III] the connect broker configured to, based on the request from the process execution engine, acquire API information for the particular service by searching through the registered plurality of API information using a management ID mapped to the particular service, and process the particular service task, wherein the connect broker is configured to process the particular service task by invoking an API corresponding to the acquired API information, and receiving a response for multiple items from the service module as a result of an execution of the invoked API.
Note: for referential purpose, numerals [I]-[III] are added to the beginning of each device.
Claim Rejections - 35 USC § 112
Claims 1-17 rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
1) In independent claim 1, the phrase “which is a task using a particular service provided by a service module” is vague because the task using a particular service appears to be provided by the “[I] Connect Manager” which registers and manages a plurality of API information for services. It’s not clear the relationship between the “Connect Manager” and the “service module” since they appear to have the same task of providing the “particular service task” to the process execution engine. In other word, is there a relationship between the functions of the “[I] Connect manager” and “[II] a process execution engine”?
[II] a process execution engine configured to execute, in conjunction with a connect broker, a target business process comprising a plurality of tasks, wherein the process execution engine configured to, based on identifying that a current task among the plurality of tasks is a particular service task, which is a task using a particular service provided by a service module, transmit a request to the connect broker to process the particular service task; and
2) In independent claims 1, 10 and 17, the phrase “the connect broker configured to …. Acquire API information for the particular service by searching …. And process the particular service task” is vague because it’s not clear whether the task is processed based on the searching step alone? From par. [0110], it appears that the connect broker (27) retrieves the API information of the connect information object mapped to the service task as a search result, …, and the connect broker may perform this retrieval process either directly on the repository or through the connect manager 26.” Insertion of the “retrieves the API information …mapped to the service task as a search result” and a relationship to the “connect manager” is recommended to improve clarity.
Response to Arguments
Applicant’s arguments filed 06/22/26 has been reviewed: 1) 112 (b) rejections: withdrawn due to amendment, however, the amendment generates new issues and new rejections.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). 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.
Citation of Pertinent Prior Art
1) US 2018/0.321.993, by McClory et al. discloses a system for business process automation (BPA) has similar steps in claim 1 but does not include the use of “Connect Broker” and “Service Module.”
2) US 2016/0.098.661, by Viswanathan et al. discloses a system for business process automation (BPA) has similar steps in claim 1 but does not include the use of “Connect Broker” and “Service Module.”
No claims are allowed.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Tan "Dean" D NGUYEN whose telephone number is (571)272-6806. The examiner can normally be reached on M-F: 6;30-4:30 PM ET.
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, Sarah M Monfeldt can be reached on 571-270-1833. 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.
/TAN D NGUYEN/Primary Examiner, Art Unit 3689
Prosecution Insights