Prosecution Insights
Last updated: August 06, 2026
Application No. 19/271,270

SYSTEMS AND METHODS FOR REPORTING CLOUD STORAGE STATISTICS BY A CLOUD STORAGE SERVICE PROVIDER

Non-Final OA §103
Filed
Jul 16, 2025
Priority
Feb 24, 2023 — continuation of 12/373,421
Examiner
MINCEY, JERMAINE A
Art Unit
Tech Center
Assignee
Wasabi Technologies LLC
OA Round
1 (Non-Final)
57%
Grant Probability
Moderate
1-2
OA Rounds
3y 2m
Est. Remaining
98%
With Interview

Examiner Intelligence

Grants 57% of resolved cases
57%
Career Allowance Rate
292 granted / 512 resolved
-3.0% vs TC avg
Strong +41% interview lift
Without
With
+41.2%
Interview Lift
resolved cases with interview
Typical timeline
4y 2m
Avg Prosecution
15 currently pending
Career history
534
Total Applications
across all art units

Statute-Specific Performance

§101
22.0%
-18.0% vs TC avg
§103
54.6%
+14.6% vs TC avg
§102
15.0%
-25.0% vs TC avg
§112
3.2%
-36.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 512 resolved cases

Office Action

§103
DETAILED ACTION 1. This is a Non-Final Office Action Correspondence in response to U.S. Application No. 19/271270 filed on July 16, 2025. Notice of Pre-AIA or AIA Status 2. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Information Disclosure Statement 3. The Information Disclosure Statement filed on July 16, 2025 was reviewed and accepted by the Examiner. Claim Rejections - 35 USC § 103 4. 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 (i.e., changing from AIA to pre-AIA ) 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. 5. 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. 6. Claim(s) 21, 23-29 and 31-40 is/are rejected under 35 U.S.C. 103 as being unpatentable by Telang U.S. Patent No. 10,324,893 (herein as ‘Telang’) and further in view of Zhang U.S. Patent Application Publication No. 2020/0036788 (herein as ‘Zhang’). As to claim 21 a system for customized display of cloud storage statistics comprising one or more processors to: receive a request from a client pertaining to use of cloud storage by the client of a managed service provider (Fig. 7 and Col. 17 Lines 09-40 Telang discloses the request for storage usage); Telang does not teach but Zhang teaches the request including a domain identifier associated with the managed service provider (Par. 0035-0036 Zhang discloses an identifier within the policy manger and using the identifier for the network address); Telang and Zhang are analogous art because they are in the same field of endeavor, processing remote content. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the remote content access of Telang to include the identifier with network of Zhang, to allow for improved quality of service (Par. 0003-0004 Zhang). transmit a request for a custom asset associated with the domain identifier to a first cloud storage service; receive, from the first cloud storage service, the requested custom asset associated with the domain identifier; request, from a database via an application programming interface (API) call, statistics regarding use of a second cloud storage service by the client (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). receive, from the second cloud storage service, statistics regarding use of the second cloud storage service by the client; and render, using the retrieved custom asset and statistics, a customized page displaying the cloud storage statistics (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). As to claim 23 Telang in combination with Zhang teaches each and every limitation of claim 21. In addition Telang teaches wherein the one or more processors retrieve the custom asset using the domain identifier including a second level identifier corresponding to the managed service provider (Col. 10 Lines 5-15 Telang). As to claim 24 Telang in combination with Zhang teaches each and every limitation of claim 21. In addition Telang teaches wherein the one or more processors: transmit, by a browser application of the managing service provider, the request to the first cloud storage via an API call corresponding to the custom asset; and receive, by the browser application from the first cloud storage service, the custom asset responsive to the API call corresponding to the custom asset (Col. 10 Lines 5-15 Telang). As to claim 25 Telang in combination with Zhang teaches each and every limitation of claim 21. In addition Telang teaches wherein the one or more processors: receive, by a browser application of the managing service provider, the request from the client using the first cloud storage service provided to the client by the managed service provider, the first cloud storage service maintained by the managing service provider; and render, by the browser application, the customized page for the client on behalf of the managed service provider (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). As to claim 26 Telang in combination with Zhang teaches each and every limitation of claim 21. In addition Telang teaches wherein the one or more processors: receive, by a browser application of the managing service provider, the request to retrieve the statistics of the client corresponding to a service provided to the client by the managed service provider; send, by the browser application to the first cloud storage service managed by the managing service provider, the API call corresponding to the statistics for the service; and receive, by the browser application from the first cloud storage service, the statistics for the service responsive to the API call (Col. 10 Lines 5-15 Telang). As to claim 27 Telang in combination with Zhang teaches each and every limitation of claim 21. In addition Telang teaches wherein the one or more processors: receive a second request from the managed service provider corresponding to the use of cloud storage by a plurality of clients of the managed service provider; and render, using statistics of the plurality of clients, the customized page displaying cloud storage statistics of the plurality of clients (Col. 10 Lines 5-15 Telang). As to claim 28 Telang in combination with Zhang teaches each and every limitation of claim 21. In addition Telang teaches wherein the one or more processors: transmit, by a browser application of the managing service provider, a second API call corresponding to an access key for the custom asset; and receive, by the browser application, the custom asset using the access key (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). As to claim 29 Telang teaches a method of customized display of cloud storage statistics comprising: receiving, by one or more processors, a request from a client pertaining to use of cloud storage by the client of a managed service provider (Fig. 7 and Col. 17 Lines 09-40 Telang discloses the request for storage usage); Telang does not teach but Zhang teaches the request including a domain identifier associated with the managed service provider (Par. 0035-0036 Zhang discloses an identifier within the policy manger and using the identifier for the network address); Telang and Zhang are analogous art because they are in the same field of endeavor, processing remote content. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the remote content access of Telang to include the identifier with network of Zhang, to allow for improved quality of service (Par. 0003-0004 Zhang). Telang teaches transmitting, by the one or more processors, a request for a custom asset associated with the domain identifier to a first cloud storage service; receiving, by the one or more processors from the first cloud storage service, the requested custom asset associated with the domain identifier; requesting, by the one or more processors from a database via an application programming interface (API) call, statistics regarding use of a second cloud storage service by the client (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). receiving, by the one or more processors from the second cloud storage service, statistics regarding use of the second cloud storage service by the client; and rendering, by the one or more processors using the retrieved custom asset and statistics, a customized page displaying the cloud storage statistics (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). As to claim 31 Telang in combination with Zhang teaches each and every limitation of claim 29. In addition Telang teaches comprising retrieving, by the one or more processors, the custom asset using the domain identifier including a second level identifier corresponding to the managed service provider (Col. 10 Lines 5-15 Telang). As to claim 32 Telang in combination with Zhang teaches each and every limitation of claim 29. In addition Telang teaches comprising: transmitting, by a browser application of the managing service provider, the request to the first cloud storage via an API call corresponding to the custom asset; and receiving, by the browser application from the first cloud storage service, the custom asset responsive to the API call corresponding to the custom asset (Col. 10 Lines 5-15 Telang). As to claim 33 Telang in combination with Zhang teaches each and every limitation of claim 29. In addition Telang teaches comprising: receiving, by a browser application of the managing service provider, the request from the client using the first cloud storage service provided to the client by the managed service provider, the first cloud storage service maintained by the managing service provider; and rendering, by the browser application, the customized page for the client on behalf of the managed service provider (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). As to claim 34 Telang in combination with Zhang teaches each and every limitation of claim 29. In addition Telang teaches comprising: receiving, by a browser application of the managing service provider, the request to retrieve the statistics of the client corresponding to a service provided to the client by the managed service provider; sending, by the browser application to the first cloud storage service managed by the managing service provider, the API call corresponding to the statistics for the service; and receiving, by the browser application from the first cloud storage service, the statistics for the service responsive to the API call (Col. 10 Lines 5-15 Telang). As to claim 35 Telang in combination with Zhang teaches each and every limitation of claim 29. In addition Telang teaches receiving, by the one or more processors, a second request from the managed service provider corresponding to the use of cloud storage by a plurality of clients of the managed service provider; and rendering, by the one or more processors, using statistics of the plurality of clients, the customized page displaying cloud storage statistics of the plurality of clients (Col. 10 Lines 5-15 Telang). As to claim 36 Telang in combination with Zhang teaches each and every limitation of claim 29. In addition Telang teaches comprising: transmitting, by a browser application of the managing service provider, a second API call corresponding to an access key for the custom asset; and receiving, by the browser application, the custom asset using the access key (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). As to claim 37 Telang teaches a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to: receive, by a browser application of a managing service provider, a request from a client pertaining to use of cloud storage by the client of a managed service provider (Fig. 7 and Col. 17 Lines 09-40 Telang discloses the request for storage usage); Telang does not teach but Zhang teaches the request including a domain identifier associated with the managed service provider (Par. 0035-0036 Zhang discloses an identifier within the policy manger and using the identifier for the network address); Telang and Zhang are analogous art because they are in the same field of endeavor, processing remote content. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the remote content access of Telang to include the identifier with network of Zhang, to allow for improved quality of service (Par. 0003-0004 Zhang). Telang teaches transmit, by the browser application, a request for a custom asset associated with the domain identifier to a first cloud storage service; receive, by the browser application from the first cloud storage service, the requested custom asset associated with the domain identifier; request, by the browser application from a database via an application programming interface (API) call, statistics regarding use of a second cloud storage service by the client (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). receive, by the browser application from the second cloud storage service, statistics regarding use of the second cloud storage service by the client; and render, by the browser application using the retrieved custom asset and statistics, a customized page displaying the cloud storage statistics (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). As to claim 38 Telang in combination with Zhang teaches each and every limitation of claim 37. In addition Telang teaches wherein the instructions cause the one or more processors to retrieve the custom asset using the domain identifier including a second level identifier corresponding to the managed service provider (Col. 10 Lines 5-15 Telang). As to claim 39 Telang in combination with Zhang teaches each and every limitation of claim 37. In addition Telang teaches wherein the instructions cause the one or more processors to: transmit, by a browser application of the managing service provider, the request to the first cloud storage via an API call corresponding to the custom asset; and receive, by the browser application from the first cloud storage service, the custom asset responsive to the API call corresponding to the custom asset (Col. 10 Lines 5-15 Telang). As to claim 40 Telang in combination with Zhang teaches each and every limitation of claim 37. In addition Telang teaches wherein the instructions cause the one or more processors to: receive, by the browser application, the request from the client using the first cloud storage service provided to the client by the managed service provider, the first cloud storage service maintained by the managing service provider; and render, by the browser application, the customized page for the client on behalf of the managed service provider (Col. 3 Lines 5-60 Telang discloses storage devices can provide access to content. The device receiving the content is seen as the second cloud storage manager). Allowable Subject Matter 7. Claims 22 and 30 do not contain any prior art search. 22. (Original) The system of claim 21, wherein the one or more processors render, for a browser application of the managing service provider, the customized page by inserting into the customized page a link to a page of a subset of statistics corresponding to a geographic region in which services corresponding to the subset of the statistics were provided. 30. (Original) The method of claim 29, comprising rendering, by the one or more processors, the customized page by inserting into the customized page a link to a page of a subset of statistics corresponding to a geographic region in which services corresponding to the subset of the statistics were provided. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. “Automation and Customization of Rendered Web Pages” by Michael Bolin (herein as ‘Bolin’). Bolin discloses on the desktop, an application can expect to control its user interface down to the last pixel, but on the World Wide Web, a content provider has no control over how the client will view the page, once delivered to the browser. This creates an opportunity for end-users who want to automate and customize their web experiences, but the growing complexity of web pages and standards prevents most users from realizing this opportunity. We describe Chickenfoot, a programming system embedded in the Firefox web browser, which enables end-users to automate, customize, and integrate web applications without examining their source code. One way Chickenfoot addresses this goal is a novel technique for identifying page components by keyword pattern matching. We motivate this technique by studying how users name web page components, and present a heuristic keyword matching algorithm that identifies the desired component from the user’s name. Conclusion 8. Any inquiry concerning this communication or earlier communications from the examiner should be directed to JERMAINE A MINCEY whose telephone number is (571)270-5010. The examiner can normally be reached 8am EST until 5pm EST. 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, Ann J Lo can be reached at (571) 272-9767. 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. /JERMAINE A MINCEY/Examiner, Art Unit 2159
Read full office action

Prosecution Timeline

Jul 16, 2025
Application Filed
Jul 15, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12681919
SYSTEMS AND METHODS OF TRANSACTION IDENTIFICATION GENERATION FOR TRANSACTION-BASED ENVIRONMENT
2y 8m to grant Granted Jul 14, 2026
Patent 12670101
SYSTEM AND METHOD FOR AUTOMATIC RECOVERY OF MISSING METER READINGS
2y 5m to grant Granted Jun 30, 2026
Patent 12664202
AUTOMATED KNOWLEDGE GRAPH POPULATOR FOR DATA SELECTION
3y 0m to grant Granted Jun 23, 2026
Patent 12664215
COMPUTER-IMPLEMENTED DATA STRUCTURE, ELECTRONIC STORAGE MEDIUM, AND METHOD FOR DATA EXCHANGE
2y 7m to grant Granted Jun 23, 2026
Patent 12651655
Time-Based Healthcare Data Management with Partitioned Storage and Compaction
1y 4m to grant Granted Jun 09, 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
57%
Grant Probability
98%
With Interview (+41.2%)
4y 2m (~3y 2m remaining)
Median Time to Grant
Low
PTA Risk
Based on 512 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