Prosecution Insights
Last updated: April 19, 2026
Application No. 19/349,862

PROCESSING DEVICE AND METHOD FOR MANAGING TASKS THEREOF

Non-Final OA §103§112§DP
Filed
Oct 03, 2025
Examiner
RASHID, WISSAM
Art Unit
2195
Tech Center
2100 — Computer Architecture & Software
Assignee
Rebellions Inc.
OA Round
1 (Non-Final)
88%
Grant Probability
Favorable
1-2
OA Rounds
2y 11m
To Grant
99%
With Interview

Examiner Intelligence

Grants 88% — above average
88%
Career Allow Rate
572 granted / 654 resolved
+32.5% vs TC avg
Moderate +12% lift
Without
With
+12.3%
Interview Lift
resolved cases with interview
Typical timeline
2y 11m
Avg Prosecution
25 currently pending
Career history
679
Total Applications
across all art units

Statute-Specific Performance

§101
9.7%
-30.3% vs TC avg
§103
44.9%
+4.9% vs TC avg
§102
12.4%
-27.6% vs TC avg
§112
19.5%
-20.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 654 resolved cases

Office Action

§103 §112 §DP
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 . Claims 1-20 are pending. Examiner’s Note Although Applicant’s request to participate in the Patent Prosecution Highway (PPH) has been granted, the examiner is unable to allow the application at this stage of prosecution due to several deficiencies. Further, no prior art has been found for claims 1-14, 19, and 20. However, they are each subject to one or more deficiencies as elaborated throughout this Office Action. Specification The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed. 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-19 of U.S. Patent No. 12461780 (hereinafter ‘780). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims of the ‘780 patent anticipate the claims of the instant application. Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-19 of U.S. Patent No. 12079661 (hereinafter ‘661). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims of the ‘661 patent anticipate the claims of the instant application. Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-18 of U.S. Patent No. 12340246 (hereinafter ‘246). Although the claims at issue are not identical, they are not patentably distinct from each other because the claims of the ‘246 patent anticipate the claims of the instant application. 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. The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph: 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) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses 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 limitation(s) is/are: “task buffer”, “task queue”, “runtime handle” in claim 1; “task manager” in claim 11, “task passage” and “done passage” in claim 12, “task buffer, “task queue” in claim 13. Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/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 this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. 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. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claim limitations “task buffer”, “task queue”, “runtime handle” in claim 1; “task manager” in claim 11, “task passage” and “done passage” in claim 12, “task buffer, “task queue” in claim 13 invoke 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. However, the written description fails to disclose the corresponding structure, material, or acts for performing the entire claimed functions and to clearly link the structure, material, or acts to the functions. Therefore, the claims are indefinite and are rejected under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph. Applicant may: (a) Amend the claim so that the claim limitation will no longer be interpreted as a limitation under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph; (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 17 and 18 are 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. With respect to claim 17, it is not clear where or when the run signal is provided. Is it provided or placed after a waiting state in a data structure? Is it provided after the waiting state expires? With respect to claim 18, it is not clear where or when the run signal is provided. Is it provided or placed before a waiting state in a data structure? Is it provided before the waiting state expires? Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claim(s) 15-18 are rejected under 35 U.S.C. 103 as being unpatentable over Brown et al. (US 2017/0270053) in view of Lippett (US 2007/0220517). With respect to claim 15, Brown discloses: receiving, by a task queue of the processing device, a task descriptor, wherein the task descriptor comprises a wait field associated with control of an execution time of the task ([0066], Fig. 2 where 201a-203a are task descriptors, 201b-203b are operations which are interpreted to correspond to Applicant’s “task/s”, the operations 201b-203b are depicted in an order and is interpreted to function like Applicant’s “queue” which essentially stores a list of date or commands retrievable in a definite order); checking, by a runtime handle of the processing device, whether the task descriptor includes the wait field for the task ([0089], checking whether a wait condition needs to be satisfied by checking the wait field corresponds to Applicant’s checking whether the descriptor includes the wait field); and determining, by the runtime handle, a state of the task descriptor as a run state or a waiting state, based on whether the task descriptor includes the wait field ([0089]- [0090]). Brown discloses a processing device, but not a neural processing device. However, Lippett discloses a neural processing device (col. 2, lines 22-31). It would have been obvious to a person having ordinary skill in the art before the effective filing date of the invention to incorporate neural processing devices as taught by Lippett to accelerate artificial intelligence and machine learning tasks with far greater power efficiency, faster real time responses then a generic processing device. It also frees up generic CPU/GPUs for other work. With respect to claim 16, Brown discloses: releasing, by the runtime handle, the waiting state of the task descriptor based on a run signal provided from a command processor of the neural processing device ([0089]-[0090], where the event corresponds to Applicant’s “run signal”). With respect to claim 17, Brown discloses: wherein the run signal is provided after a waiting state of the task descriptor (id. dependent on whether the event meets the wait value, i.e., the wait value may be less or more). With respect to claim 18, Brown discloses: wherein the run signal is provided before a waiting state of the task descriptor ([0089]-[0090], dependent on whether the event meets the wait value, i.e., the wait value may be less or more). Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to WISSAM RASHID whose telephone number is (571)270-3758. The examiner can normally be reached Monday-Friday 8:00 am-5:00 pm. 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, Aimee Li can be reached at (571)272-4169. 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. /WISSAM RASHID/Primary Examiner, Art Unit 2195
Read full office action

Prosecution Timeline

Oct 03, 2025
Application Filed
Dec 23, 2025
Non-Final Rejection — §103, §112, §DP (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12603762
DATA TRANSFER USING A VIRTUAL TERMINAL
2y 5m to grant Granted Apr 14, 2026
Patent 12591443
SYSTEM AND METHOD FOR FACILITATING PARTICIPATION IN A BLOCKCHAIN ENVIRONMENT
2y 5m to grant Granted Mar 31, 2026
Patent 12591454
PROCESSING DEVICE AND METHOD FOR DISTRIBUTING DATA TO A PLURALITY OF PROCESSING UNITS
2y 5m to grant Granted Mar 31, 2026
Patent 12578991
PARALLEL PROCESSING ARCHITECTURE WITH DISTRIBUTED REGISTER FILES
2y 5m to grant Granted Mar 17, 2026
Patent 12572392
FLEXIBLE PARTITIONING OF GPU RESOURCES
2y 5m to grant Granted Mar 10, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

1-2
Expected OA Rounds
88%
Grant Probability
99%
With Interview (+12.3%)
2y 11m
Median Time to Grant
Low
PTA Risk
Based on 654 resolved cases by this examiner. Grant probability derived from career allow 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