Prosecution Insights
Last updated: April 19, 2026
Application No. 18/821,850

DATABASE ENTITY, ORIGINATING DATABASE ENTITY, AND METHODS FOR USE IN THE SAME

Final Rejection §102
Filed
Aug 30, 2024
Examiner
NGUYEN, KIM T
Art Unit
2153
Tech Center
2100 — Computer Architecture & Software
Assignee
Huawei Technologies Co., Ltd.
OA Round
2 (Final)
87%
Grant Probability
Favorable
3-4
OA Rounds
2y 8m
To Grant
96%
With Interview

Examiner Intelligence

Grants 87% — above average
87%
Career Allow Rate
1607 granted / 1844 resolved
+32.1% vs TC avg
Moderate +8% lift
Without
With
+8.4%
Interview Lift
resolved cases with interview
Typical timeline
2y 8m
Avg Prosecution
13 currently pending
Career history
1857
Total Applications
across all art units

Statute-Specific Performance

§101
10.0%
-30.0% vs TC avg
§103
22.7%
-17.3% vs TC avg
§102
36.5%
-3.5% vs TC avg
§112
19.0%
-21.0% vs TC avg
Black line = Tech Center average estimate • Based on career data from 1844 resolved cases

Office Action

§102
DETAILED ACTION Claim Rejections - 35 USC § 102 1. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention. 2. Claims 1-11, 13-20 and 27 rejected under 35 U.S.C. 102(a)(1) as being anticipated by Michael J. LeBeau (US-2011/0098917-A1). As per claim 1, LeBeau teaches “ A database entity configured for near data processing and comprising a controller and a memory, wherein the controller is configured to: receive a request based on a query received by an originating database entity from a client node, wherein the request comprises an indicator of a function to generate a result, ([0037]-[0039]) an indicator of data on which the function is to be performed, ([0036]-[0038]} and an indicator of a destination for the result to be transmitted to,” ([0039],[0042]-[0044]); “retrieve data according to the indicator of data,” ([0036], [0038]); “execute the indicated function on the retrieved data,” ([0036]-[0038]); and “transmit the result to the indicated destination,” ([0039], [0042]-[0044]). As per claim 2, LeBeau further shows “wherein the controller is configured to receive the request from the originating database entity,” ([0036]). As per claim 3, LeBeau further shows “wherein the destination is another database entity and wherein the controller is configured to generate a partial result, and transmit the partial result to the another database entity,” ([0006], [0040]-[0042]). As per claim 4, LeBeau further shows “wherein the controller is configured to transmit the partial result by generating a further request comprising the partial result, the indicator of function and a further indicator of destination, and to transmit the further request to the another database entity,” ([0006], [0040]-[0043]). As per claim 5, LeBeau further shows “wherein the controller is configured to generate a final result and wherein the destination is the client node,” ([0044]). As per claim 6, LeBeau further shows “wherein the controller is configured to receive the request from another database entity and wherein the data indicator of data includes a partial result to be further processed by the indicated function,” ([0006], [0040]-[0043]). As per claim 7, LeBeau further shows “wherein the controller is configured to retrieve the data according to the indicator of data from the memory,” ([0041]-[0043]). As per claim 8, LeBeau further shows “wherein the controller is configured to retrieve the data from another database entity as indicated by the indicator of data,” ([0041]-[0043]). As per claim 9, LeBeau further shows “wherein the controller is configured to retrieve the data by receiving the data,” ([0036]-[0037]). As per claim 10, LeBeau further shows “wherein the database entity is a database node, wherein the memory is a local memory,” ([0072], [0120]). As per claim 11, LeBeau further shows “wherein the database entity is a database storage node, wherein the memory is a disc storage memory,” ([0072], [0112]). As per claim 13, LeBeau teaches “An originating database entity comprising a controller, wherein the controller is configured to: receive a query from a client node,” ([0036], [0038]); “generate a request based on the query, wherein the request comprises an indicator of a function to generate a result according to the query, an indicator of data on which the function is to be performed, and an indicator of a destination for the result to be transmitted to,” ([0036]-[0039], [0042]-[0044]); and “transmit the request to a database entity configured for near data processing,” ([0039], [0042]-[0044]). As per claim 14, LeBeau teaches “A method for use in a database entity configured for near data processing and comprising a memory, wherein the method comprises: receiving a request based on a query received by an originating database entity from a client node, wherein the request comprises an indicator of a function to generate a result, an indicator of data on which the function is to be performed, and an indicator of a destination for the result to be transmitted to,” ([0036]-[0039], [0042]-[0044]); “retrieving data according to the indicator of data,” ([0036], [0038]); “executing the indicated function on the retrieved data,” ([0036]-[0038]); and “transmitting the result to the indicated destination,” ([0039], [0042]-[0044]). As per claim 15, LeBeau further shows “wherein the method further comprises comprising receiving the request from the originating database entity,” ([0036]). As per claim 16, LeBeau further shows “wherein the destination is another database entity and wherein the method further comprises generating a partial result and transmitting the partial result to the another database entity,” ([0006], [0040]-[0042]). As per claim 17, LeBeau further shows “wherein the method further comprises comprising transmitting the partial result by generating a further request comprising the partial result, the indicator of function and a further indicator of destination, and transmitting the further request to the another database entity” ([0006], [0040]-[0043]). As per claim 18, LeBeau further shows “wherein the method further comprises comprising generating a final result and wherein the destination is the client node,” ([0044]). As per claim 19, LeBeau further shows “wherein the method further comprises comprising receiving the request from another database entity and wherein the data indicator of data includes a partial result to be further processed by the indicated function,” ([0006], [0040]-[0043]). As per claim 20, LeBeau further shows “wherein the method further comprises comprising retrieving the data according to the indicator of data from the memory,” ([0041]-[0043]). As per claim 27, LeBeau further shows “wherein the method further comprises retrieving the data from another database entity as indicated by the indicator of data,” ([0006], [0040]-[0043]). Allowable Subject Matter 3. Claims 1-11, 13-20 and 27 would be allowable if rewritten or amended to overcome the rejections as set forth in this Office action. Conclusion 4. THIS ACTION IS MADE FINAL, 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 extension fee 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. Contact Information 5. Any inquiry concerning this communication or earlier communications from the examiner should be directed to KIM T NGUYEN whose telephone number is (571)270-1757. The examiner can normally be reached on Mon-Thurs 6-4:30pm. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kavita Stanley can be reached on (571)272-8352. 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. Jan. 15, 2026 /KIM T NGUYEN/Primary Examiner, Art Unit 2153
Read full office action

Prosecution Timeline

Aug 30, 2024
Application Filed
Jun 28, 2025
Non-Final Rejection — §102
Oct 01, 2025
Response Filed
Jan 15, 2026
Final Rejection — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12602388
GENERATIVE SEARCH ENGINE TEXT DOCUMENTS
2y 5m to grant Granted Apr 14, 2026
Patent 12596735
SEMANTIC TEXT ANALYSIS FOR GLOSSARY MAINTENANCE
2y 5m to grant Granted Apr 07, 2026
Patent 12596688
Managed Directories for Virtual Machines
2y 5m to grant Granted Apr 07, 2026
Patent 12591579
Aggregation Operations In A Distributed Database
2y 5m to grant Granted Mar 31, 2026
Patent 12586095
METHODS AND APPARATUS TO ANALYZE AND ADJUST DEMOGRAPHIC INFORMATION
2y 5m to grant Granted Mar 24, 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

3-4
Expected OA Rounds
87%
Grant Probability
96%
With Interview (+8.4%)
2y 8m
Median Time to Grant
Moderate
PTA Risk
Based on 1844 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