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 .
Response to Amendments / Arguments
Regarding the rejection(s) of claims under 35 USC 103:
Applicant’s arguments, filed 10/29/2025, in view of the amended claims, have been fully considered and are persuasive. Therefore, the rejection has been withdrawn. However, upon further consideration, a new ground(s) of rejection is made in view of Grieve et al. (US 9047393 B1).
DETAILED ACTION
This is a reply to the application filed on 10/29/2025, in which, claims 1-2, 4-9 and 11-21 are pending. Claims 1, 18, 19, and 20 are independent. Claim 3 and 10 is cancelled.
When making claim amendments, the applicant is encouraged to consider the references in their entireties, including those portions that have not been cited by the examiner and their equivalents as they may most broadly and appropriately apply to any particular anticipated claim amendments.
Claim Rejections - 35 USC § 103
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.
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.
Claims 1-2, 4-9 and 11-21 are rejected under 35 U.S.C. 103 as being unpatentable over Grieve et al. (US 9047393 B1, referred to as Grieve) in view of Coimbra et al. (US 20210326430 A1, referred to as Coimbra).
In reference to claim 1, A method, comprising: by a browser data manager operationally coupled to a browser application executed on a computing device (Grieve: Col. 7 line 57 -Col. 8 line 10 and Fig. 3 Provides for a shared worker application that functions essentially as a browser data manager, managing data acquisition and sharing for web applications within the browser.) the browser application having one or more inline frames presented on a web page in a browser for display (Grieve: Col. 11 line 60 - Col. 12 Line 10 Provides for the use of inline frames (iframes) as child web applications within the browser. The patent specifically identifies iframes as the mechanism for creating child applications associated with different domains.)
with each inline frame having a web application and the browser data manager being configured to maintain a repository of data associated with content of each inline frame (Grieve: Col. 8 lines 40-55 and Col. 10 Lines 1-15 and Fig. 4 Provides for that the shared worker (browser data manager) maintains data in local memory 26, which serves as a repository. The shared worker stores "acquired information associated with the second domain" for multiple web applications.)
Receiving, by the browser data manager from the browser application, a network response including data specific to content of a first inline frame (Grieve: Col. 8 lines 5-25, Col. 10 lines 1-10 and Fig. 5 Provides for the shared worker receiving and processing network data for web applications.)
Wherein the repository provides a single source of data shared among the inline frames to reduce duplication of content data, the first inline frame is associated with a first origin or domain (Grieve: Col. 9 lines 15-35 and Col. 5 lines 15-30 Provides for reducing data duplication through a single shared repository. Emphasizing that the shared worker eliminates redundant network requests by maintaining a single source of data accessible to multiple web applications across different domains.)
At least one second inline frame on the web page is associated with a different origin or domain, and the browser data manager provides the received data to the first web application without direct inter-frame messaging between the inline frames (Grieve: Col. 14 Line 50 - Col. 15 line 10 and Fig. 10 Provides for cross-domain communication where applications on Domain A communicate with a shared worker on Domain B through a child iframe.)
Grieve does not explicitly teach the content of each inline frame having a corresponding attribute that indicates the content has changed in the repository, updating a first attribute to indicate that content of the first inline frame having a first web application has changed in the repository responsive to determining that received data specific to the content of the first inline frame does not correspond to the content of the first inline frame stored in the repository and sending, to the first web application, the received data specific to the content of the first inline frame responsive to determining that the updated first attribute indicates that the content of the first inline frame has changed in the repository. However, Coimbra teaches:
with the content of each inline frame having a corresponding attribute that indicates the content has changed in the repository (Coimbra: [0115]-[0120] Provides for monitoring and tracking state changes of iframe content and communicating these changes.) Updating a first attribute to indicate that content of the first inline frame having a first web application has changed in the repository responsive to determining that received data specific to the content of the first inline frame does not correspond to the content of the first inline frame stored in the repository (Coimbra: [0115]-[0120] Provides for monitoring state changes and updating semantic state information.)
sending, to the first web application, the received data specific to the content of the first inline frame responsive to determining that the updated first attribute indicates that the content of the first inline frame has changed in the repository (Coimbra: [0133]-[0142] Provides for sending data to web applications in iframes based on detected changes.)
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the teachings of Grieve, which provides a browser data manager using shared workers to maintain a single repository of data for multiple inline frames across different domains to reduce duplication, with the teachings of Coimbra, which introduces tracking content changes through attributes and selectively sending updated data to web applications only when changes are detected. One of ordinary skill in the art would recognize the ability to incorporate Coimbra's change detection and attribute tracking mechanisms into Grieve's shared data repository system to optimize data synchronization. One of ordinary skill in the art would be motivated to make this modification in order to further improve browser efficiency by avoiding unnecessary data transfers when content hasn't changed.
In reference to claim 2, The method of claim 1,further comprising: receiving, by the browser data manager, from the browser application, the data specific to the content of the first inline frame (Grieve: Col. 14 lines 60-67 Provides for receiving, by the browser data manager, from the browser application, data specific to inline frame content. Coimbra: [0065] and [0120] Provides for a system for receiving data specific to iframe content.)
In reference to claim 4, The method of claim 1, further comprising: storing, in the repository, the received data specific to the content of the first inline frame (Grieve: Col. 8 lines 40-55 and Fig. 5 Provides for storing received data specific to inline frame content in the repository. Coimbra: [0052] and [0059] Provides for storing various types of data in the repository.)
In reference to claim 5, The method of claim 1, wherein the determining that the received data is different from the stored data further includes determining that the received data is specific to new or different content of the first inline frame (Coimbra: [0115]-[0120] Provides for a system for monitoring and identifying the current state and content of the iframe.)
In reference to claim 6, The method of claim 1, wherein the determining that the received data is different from the stored data further includes comparing the received data and the corresponding stored data (Coimbra: [0122] and [0125] Provides for processes of searching and matching received data against stored data.)
In reference to claim 7, The method of claim 1, further comprising: receiving, by the browser data manager, from the first web application, an indication that includes a requests for the data specific to the content of the first inline frame (Grieve: Col. 8 lines 5-20 Provides for receiving, by the browser data manager from the first web application, an indication that includes a request for data specific to inline frame content. Coimbra: [0007] and [0120] Provides for directly addressing the concept of receiving a request for data specific to the content of the iframe.)
In reference to claim 8, The method of claim 7, wherein the sending the data is further responsive to receiving the request indication (Grieve: Col. 8 line 40 – Col. 9 line 15 provides for sending data responsive to receiving the request indication. Coimbra: [0007] and [0139] Provides that the system responds to requests by querying for data.)
In reference to claim 9, The method of claim 1, further comprising: receiving, by the browser data manager, from the first web application, an indication that requests data specific to the content of the first inline frame when the first attribute associated with the content of the first inline frame is changed (Coimbra: [0117]-[0120] Provides for a system where state changes can be detected and communicated.)
In reference to claim 11, The method of claim 1, further comprising: sending, by the browser data manager, to the first web application, an indication that the data specific to the content of the first inline frame has changed responsive to determining that the first attribute associated with the content of the first inline frame changed (Coimbra: [0117]-[0120] Provides for a system for sharing state information between components.)
In reference to claim 12, The method of claim 1, further comprising: receiving, by the browser data manager, from the first web application, an indication that requests data associated with a certain portion of the content of the first inline frame when the first attribute associated with that content of the first inline frame is changed (Coimbra: [0120] and [0126] Provides for requesting specific state information and identifying specific parameters.)
In reference to claim 13, The method of claim 12, further comprising: sending, to the first web application, the requested data responsive to determining that the first attribute associated with the certain portion of the content of the first inline frame changed (Coimbra: [0139]-[0142] Provides for sending requested data to a web application in response to certain conditions being met.)
In reference to claim 14, The method of claim 1, further comprising: sending, to a second web application of a second inline frame of the one or more inline frames, data specific to content of the second inline frame responsive to determining that a second[an] attribute indicates that the content of the second inline frame has changed (Coimbra: [0104] and [0139] Provides for handling multiple iframes and sending data to web applications in iframes.)
In reference to claim 15, The method of claim 1, wherein the browser application is configured to load each inline frame on the web page in the browser, with each inline frame being associated with a different uniform resource locator (URL) (Grieve: Col. 4 lines 20-30, Col. 12 lines 1-20 and Col. 16 lines 1-20 Provides for browser application loading each inline frame on the web page, with each inline frame associated with a different URL. Coimbra: [0062] and [0104] Provides for loading content into iframes and uses URLs for different resources.)
In reference to claim 16, The method of claim 1, wherein the browser data manager is configured as a third web application loaded into a third inline frame on the web page of the browser application (Coimbra: [0105]-[0110] Provides for loading JavaScript libraries and components into iframes.)
In reference to claim 17, The method of claim 16, wherein the browser data manager is operationally coupled to the web application of each inline frame on the web page through a fourth web application of the browser application, with the fourth web application being configured to load the first web application into the first inline frame on the web page and load the browser data manager as the third web application into the third inline frame on the web page of the browser application (Coimbra: [0086] Provides for the process of using iframes to manage distinct segments of content.)
In reference to Claims 18-20, Claims 18-20 are rejected under the same rationale as claim 1.
In reference to claim 21, The method of claim 1, wherein the browser data manager is operable to update the attribute based on a comparison of received data specific to the content for an inline frame and corresponding data specific to the content for that inline frame stored in the repository ( Coimbra: [0122]-[0130] Provides for updating an attribute based on a comparison, it describes a system that compares received state information with stored data to determine matches and predict values.)
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. See PTO-892.
Applicant’s amendment necessitated the new ground(s) of rejection presented in this office action. Accordingly, 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.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to AIDAN EDWARD SHAUGHNESSY whose telephone number is (703)756-1423. The examiner can normally be reached on Monday-Friday from 7:30am to 5pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jeffrey Nickerson, can be reached at telephone number (469) 295-9235. 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 Patent Center and the Private Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from Patent Center or Private PAIR. Status information for unpublished applications is available through Patent Center and Private PAIR for authorized users only. Should you have questions about access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
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) Form at https://www.uspto.gov/patents/usptoautomated-interview-request-air-form.
/A.E.S./Examiner, Art Unit 2432
/Jeffrey Nickerson/Supervisory Patent Examiner, Art Unit 2432