Prosecution Insights
Last updated: July 17, 2026
Application No. 19/255,983

ONTOLOGICAL EVALUATION AND FILTERING OF DIGITAL CONTENT

Non-Final OA §112
Filed
Jun 30, 2025
Priority
Feb 27, 2013 — provisional 61/770,163 +4 more
Examiner
ZHAO, YU
Art Unit
2161
Tech Center
2100 — Computer Architecture & Software
Assignee
Pavlov Media Inc.
OA Round
1 (Non-Final)
52%
Grant Probability
Moderate
1-2
OA Rounds
3y 1m
Est. Remaining
94%
With Interview

Examiner Intelligence

Grants 52% of resolved cases
52%
Career Allowance Rate
191 granted / 365 resolved
-2.7% vs TC avg
Strong +41% interview lift
Without
With
+41.3%
Interview Lift
resolved cases with interview
Typical timeline
4y 2m
Avg Prosecution
8 currently pending
Career history
377
Total Applications
across all art units

Statute-Specific Performance

§101
3.8%
-36.2% vs TC avg
§103
92.5%
+52.5% vs TC avg
§102
1.0%
-39.0% vs TC avg
§112
2.4%
-37.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 365 resolved cases

Office Action

§112
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 . Acknowledgment is made of applicant’s amendment filed on 30 June 2025. Claims 2-21 are presented for examination. Claim 1 is cancelled. Information Disclosure Statement The information disclosure statement (IDS) submitted on 17 July 2025 have been considered by the examiner. Drawings The drawings are not of sufficient quality to permit examination. Words within figures are unclear. Accordingly, replacement drawing sheets in compliance with 37 CFR 1.121(d) are required in reply to this Office action. The replacement sheet(s) should be labeled “Replacement Sheet” in the page header (as per 37 CFR 1.84(c)) so as not to obstruct any portion of the drawing figures. If the changes are not accepted by the examiner, the applicant will be notified and informed of any required corrective action in the next Office action. Applicant is given a shortened statutory period of TWO (2) MONTHS to submit new drawings in compliance with 37 CFR 1.81. Extensions of time may be obtained under the provisions of 37 CFR 1.136(a) but in no case can any extension carry the date for reply to this letter beyond the maximum period of SIX MONTHS set by statute (35 U.S.C. 133). Failure to timely submit replacement drawing sheets will result in ABANDONMENT of the application. Claim Rejections - 35 USC § 112 The following is a quotation of the first paragraph of 35 U.S.C. 112(a): (a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention. The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112: The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention. Claims 2-13, 15 and 19-21 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the enablement requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to enable one skilled in the art to which it pertains, or with which it is most nearly connected, to make and/or use the invention. Claim 1 recites “…store the mined request data in at least one of the one or more processors…,” “…whether the user-requested content is already stored on at least one of the one or more processors…,” “…store such response metadata in at least one of the one or more processors…,” “…user-requested content that is likely to be desired for download by other users within the group of users, store on at least one of the one or more processors…” and “…at least a portion of the content channels stored on at least one of the one or more processors…” Although data can be stored on a processor, but only temporarily and in very small amounts. Further, no Content Delivery System can index buffered data within processors and retrieve such data from register/cache of processors. Nowhere in Specification discloses user requested content(s) can be stored in “processor.” At the most, Specification, paragraph [0038] recites “Referring next to Figures 4A and 4B, the method by which incoming requests cause the requested content to be aggregated into channels can be better appreciated. The process of Figures 4A and 4B is, in at least some embodiments, performed on the local network appliance 105 (Figure 1). Alternatively, in other embodiments, at least the majority of the process can be performed on the remote central cloud processor. For convenience, the remainder of the discussion of Figures 4A-4B will assume that the processing occurs on the local network appliance” which clearly shows that “processor” is only used to run “process.” Claims 3-13, 15 and 19-21 are rejected for the similar reasons. Claim 1 recites “…share across a plurality of channels a single copy of content determined to be relevant to multiple channels, and in response to subsequent user requests, deliver to user devices associated with the group of users at least a portion of the content channels stored on at least one of the one or more processors…” Nowhere in Specification discloses above limitation. Specification, paragraph [0054], recites “…content that can be shared among multiple local appliances can be stored on the regional network appliance…” which shows “channels” and “local appliances” are not the same entity. In other words, “a single copy of content” does not “share across a plurality of channels.” At the most, “content” is “shared among multiple local appliances.” Further, Specification does not disclose “deliver to user devices associated with the group of users at least a portion of the content channels stored on at least one of the one or more processors.” Claims 3-21 are rejected for the similar reasons. Allowable Subject Matter Claims 2-21 would be allowable if rewritten or amended to overcome the rejection(s) under 35 U.S.C. 112, set forth in this Office action. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Fliam et al. (U.S. Pub. No.: 20130204961), paragraph [0023], “…homes 102 may include any type of user environment, such as single family homes, apartment complexes, businesses, schools, hospitals, parks, and other suitable environments and combinations of environments.” paragraph [0032], “…FIGS. 3A-3B illustrates an example distribution hierarchy for a content delivery network (CDN). After a content item is requested by a client device, such as one of client devices 303a-d, it is replicated from the origin of the CDN, such as one or more origin servers 300 in tier 310, downward through tiers of lower-tier cache servers, such as mid-tier cache servers 301a-b in tier 320 and edge cache servers 302a-c in tier 330. In some arrangements, mid-tier cache servers 301 may include multiple tiers or layers of cache servers (e.g., in tiers different from tier 320). The various components shown in FIGS. 3A-3B may be implemented using any suitable hardware, software, or both, such as device 200 shown in FIG. 2” paragraph [0033], “…One or more origin servers 300 may store the original copy of a content item, such as a movie or other data available for on-demand access by client devices 303a-d. Origin server 300 may also establish the distribution hierarchy used to cache and distribute its content…” paragraphs [0035], “…For example, the proximity between client devices 303a-d and edge cache servers 302a-c in tier 330 may be closer than the proximity between client devices 303a-d and origin server 300 in tier 310.” Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to YU ZHAO whose telephone number is (571)270-3427. The examiner can normally be reached Monday-Friday 9AM-5PM. 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, Sherief Badawi can be reached at (571) 272-9782. 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. /YU ZHAO/Primary Examiner, Art Unit 2169
Read full office action

Prosecution Timeline

Jun 30, 2025
Application Filed
Jun 29, 2026
Non-Final Rejection mailed — §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12681937
Cloud-Based Metadata Management For On-Premise Storage Systems
1y 10m to grant Granted Jul 14, 2026
Patent 12670124
Tag-Based Enforcement Of Object Storage Policies Across Tenants Of An Object Storage System
2y 5m to grant Granted Jun 30, 2026
Patent 12651020
DIGITAL ASSISTANT INTELLIGENCE ENGINE
1y 2m to grant Granted Jun 09, 2026
Patent 12645677
ENABLING REAL-TIME INTEGRATION OF UP-TO-DATE SILOED DATA
1y 2m to grant Granted Jun 02, 2026
Patent 12639328
ENTERPRISE INFORMATION ITEM LOCATION AND MANAGEMENT SYSTEMS
2y 2m to grant Granted May 26, 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
52%
Grant Probability
94%
With Interview (+41.3%)
4y 2m (~3y 1m remaining)
Median Time to Grant
Low
PTA Risk
Based on 365 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