Prosecution Insights
Last updated: October 04, 2026
Application No. 18/769,318

PLATFORM FOR MULTI-REGION CODE DEPLOYMENT OF CUSTOMIZED WORKFLOWS

Non-Final OA §112
Filed
Jul 10, 2024
Examiner
MORSHED, HOSSAIN M
Art Unit
2191
Tech Center
2100 — Computer Architecture & Software
Assignee
Devrev Inc.
OA Round
1 (Non-Final)
84%
Grant Probability
Favorable
1-2
OA Rounds
1m
Est. Remaining
98%
With Interview

Examiner Intelligence

Grants 84% — above average
84%
Career Allowance Rate
376 granted / 447 resolved
+29.1% vs TC avg
Moderate +14% lift
Without
With
+13.6%
Interview Lift
resolved cases with interview
Typical timeline
2y 3m
Avg Prosecution
12 currently pending
Career history
459
Total Applications
across all art units

Statute-Specific Performance

§101
12.2%
-27.8% vs TC avg
§103
48.9%
+8.9% vs TC avg
§102
15.1%
-24.9% vs TC avg
§112
19.8%
-20.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 447 resolved cases

Office Action

§112
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 . 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. Status of the application This Office Action is in response to Applicant's Application filed on 07/10/2024. Claims 1-24 are pending for this examination. Claim Interpretation The following is a quotation of 35 U.S.C. 112(f): (f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) because the claim limitations use a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitations are: Claim 1 recites “wherein the business process infrastructure container is configured to perform a desired operation for the user”, “a business process infrastructure code having computer-readable instructions configured to trigger the user desired operation”, “a platform configured to develop and deploy the business process infrastructure code to create one or more business process infrastructure modules”. Here “configured to” has been used with a function without reciting sufficient hardware to perform the function. As such, the claim has been interpreted under 35 USC 112(f). Similarly claims 8 – 14 have one or more limitations that use “configured to” with a functional language without associated hardware and have been interpreted under 35 USC 112(f). Because these claim limitations are being interpreted under 35 U.S.C. 112(f), they are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof. If applicant does not intend to have these limitations interpreted under 35 U.S.C. 112(f) applicant may: (1) amend the claim limitations to avoid them being interpreted under 35 U.S.C. 112(f) (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitations recite sufficient structure to perform the claimed function so as to avoid them being interpreted under 35 U.S.C. 112(f). Claim Objections Claim 1 is objected to because of the following informalities: Claim recites “a business process infrastructure code having computer-readable instructions configured to trigger the user desired operation via business process infrastructure container the and the manifest file;”. It appears to the examiner that the applicant meant to state “a business process infrastructure code having computer-readable instructions configured to trigger the user desired operation via the business process infrastructure container [[the]] and the manifest file;”. Appropriate correction or clarification is required. Claim Rejections - 35 USC § 112 The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. Claims 1, and 8-14 have one or more limitations that invokes 35 U.S.C. 112(f) as shown under claim interpretation section above. However, the written description fails to disclose the corresponding structure, material, or acts for performing the entire claimed function and to clearly link the structure, material, or acts to the function. Therefore, the above claims (1 and 8-14) are indefinite and is rejected under 35 U.S.C. 112(b). Applicant may: (a) Amend the claims so that the claim limitations will no longer be interpreted as a limitation under 35 U.S.C. 112(f); (b) Amend the written description of the specification such that it expressly recites what structure, material, or acts perform the entire claimed function, without introducing any new matter (35 U.S.C. 132(a)); or (c) Amend the written description of the specification such that it clearly links the structure, material, or acts disclosed therein to the function recited in the claim, without introducing any new matter (35 U.S.C. 132(a)). If applicant is of the opinion that the written description of the specification already implicitly or inherently discloses the corresponding structure, material, or acts and clearly links them to the function so that one of ordinary skill in the art would recognize what structure, material, or acts perform the claimed function, applicant should clarify the record by either: (a) Amending the written description of the specification such that it expressly recites the corresponding structure, material, or acts for performing the claimed function and clearly links or associates the structure, material, or acts to the claimed function, without introducing any new matter (35 U.S.C. 132(a)); or (b) Stating on the record what the corresponding structure, material, or acts, which are implicitly or inherently set forth in the written description of the specification, perform the claimed function. For more information, see 37 CFR 1.75(d) and MPEP §§ 608.01(o) and 2181. Claims 2-14 are rejected for being dependent on a rejected base claim 1. Allowable Subject Matter Claims 15-21 and 22-24 are objected to as being part of a claim set in which some of the claims have been rejected. The above claims would be allowable if written in independent form excluding the rejected claim. Please note that for an application to be allowable, all claims need to be allowable. References of Note In case, the examiner has cited particular columns, line numbers, references, or figures in the references applied to the claims above for the convenience of the applicant. Although the specified citations are representative of the teachings of the art and are applied to specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested from the applicant in preparing responses to fully consider the reference in entirety, as potentially teaching all or part of the claimed invention. See MPEP §§ 2141.02 and 2123. Contact Information Any inquiry concerning this communication or earlier communications from the examiner should be directed to HOSSAIN MORSHED whose telephone number is (571)272-3335. The examiner can normally be reached on Monday – Friday 12:00 PM – 9 PM Eastern Time. The email address for the examiner is hossain.morshed@uspto.gov. Examiner interviews are available via telephone or 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, Wei Mui can be reached on (571)272-3708. /HOSSAIN M MORSHED/Primary Examiner, Art Unit 2191 July 22, 2026
Read full office action

Prosecution Timeline

Jul 10, 2024
Application Filed
Jul 27, 2026
Non-Final Rejection mailed — §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12737170
SOFTWARE MANAGEMENT SYSTEM FOR VEHICLE, SOFTWARE MANAGEMENT METHOD FOR VEHICLE, AND NON-TRANSITORY STORAGE MEDIUM
2y 6m to grant Granted Sep 15, 2026
Patent 12730740
AUTOMATIC SCHEDULING OR EXECUTION OF SOFTWARE TESTS UPON STATUS CHANGE OF SOFTWARE ARTIFACT INCREMENT
2y 7m to grant Granted Sep 08, 2026
Patent 12711048
METHOD AND SYSTEM FOR AUTOMATING SOFTWARE DEVELOPMENT LIFECYCLES
2y 2m to grant Granted Aug 18, 2026
Patent 12704285
CONTROL ENGINE SYSTEM AND METHOD
2y 7m to grant Granted Aug 11, 2026
Patent 12699646
SYSTEM FOR IDENTIFYING VISUAL ANOMALIES AND CODING ERRORS WITHIN A VIDEO GAME
2y 4m to grant Granted Aug 04, 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

1-2
Expected OA Rounds
84%
Grant Probability
98%
With Interview (+13.6%)
2y 3m (~1m remaining)
Median Time to Grant
Low
PTA Risk
Based on 447 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