Prosecution Insights
Last updated: November 04, 2026
Application No. 18/360,355

LABORATORY DATA MANAGEMENT SYSTEM

Final Rejection §103
Filed
Jul 27, 2023
Priority
Feb 09, 2021 — EU 21156011.5 +1 more
Examiner
MENG, JAU SHYA
Art Unit
2168
Tech Center
2100 — Computer Architecture & Software
Assignee
Hitachi High-Tech Corporaion
OA Round
4 (Final)
79%
Grant Probability
Favorable
5-6
OA Rounds
3m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 79% — above average
79%
Career Allowance Rate
452 granted / 570 resolved
+24.3% vs TC avg
Strong +34% interview lift
Without
With
+33.9%
Interview Lift
resolved cases with interview
Typical timeline
3y 6m
Avg Prosecution
17 currently pending
Career history
592
Total Applications
across all art units

Statute-Specific Performance

§101
18.1%
-21.9% vs TC avg
§103
45.5%
+5.5% vs TC avg
§102
11.0%
-29.0% vs TC avg
§112
17.6%
-22.4% vs TC avg
Black line = Tech Center average estimate • Based on career data from 570 resolved cases

Office Action

§103
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 . DETAILED ACTION Response to Amendment The Amendment filed on July 22, 2026 has been received and entered. Claims 1, 3, 11, 12, 15 and 15 have been amended. Claims 16 and 17 have been newly added. Claims 1-17 are pending for examination. Amendment made to the instant specification has been received and acknowledged. Rejections and/or objections not reiterated from previous office actions are hereby withdrawn. The following rejections and/or objections are either reiterated or newly applied. They constitute the complete set presently being applied to the instant application. Priority Applicant's claim for the benefit of a prior-filed application under 35 U.S.C. 119(e) or under 35 U.S.C. 120, 121, or 365(c) is acknowledged. As required by M.P.E.P. 201.14(c), acknowledgement is made of applicant's claim for priority based on application filed on February 09, 2021 (EP21156011). Receipt is acknowledged of certified copies retrieved under 35 U.S.C. 119(a)-(d), which propriety documents have been placed of record in the file. 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 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 of this title, 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. The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. 4. Considering objective evidence present in the application indicating obviousness or nonobviousness. This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention. Claims 1, 3, 4, 6-8, 11, 13, 15 and 16 are rejected under 35 U.S.C. 103 as being unpatentable over Rao et al. (U.S. Pat. Pub. 2021/0117425) in view of Heilig et al. (U.S. Pat. No. 2020/0395121). Referring to claim 1, Rao et al. teaches a laboratory data management system comprising: a data source layer comprising at least one laboratory device as a data source of data (common storage 4602 may correspond to a storage area network (SAN), network attached storage (NAS), other network-accessible storage system (e.g., a hosted storage system, which may also be referred to as "cloud" storage), see Rao et al., Para. 844) in a data source format (the format in which data is stored in external data sources, see Rao et al., Para. 189, system's native format, see Rao et al., Para. 189), a data adapter layer comprising at least one data source agent obtaining data from the at least one data source (the search service 220 can start executing the search phases of the DAG that cause the worker nodes 214 to search the external data sources 209. Then, in step 2116, the worker nodes 214 collect the partial search results extracted from the external data sources 209, see Rao et al., Para. 438. The index cache components 254 are communicatively coupled to the cloud worker nodes 246, which can collect partial search results from the cloud storage 256 by applying a search query to the index cache components 254, see Rao et al., Para. 565) in a data source format (the format in which data is stored in external data sources, see Rao et al., Para. 189, system's native format, see Rao et al., Para. 189) and converting the data from a data source format to a data-source independent format (the worker nodes receive the partial search results collected from the data sources and transform them into a specified format. As such, partial search results in diverse formats can be transformed into a common specified format….diverse data types obtained from diverse data sources can be transformed into a common format to facilitate subsequent aggregation across all the partial search results obtained in response to the search query, see Rao et al., Para. 465), a consumer layer installing and/or executing consumer application software (a user may install a software application on server computers owned by the user and configure each server to operate as one or more of … an indexer, see Rao et al., Para. 165), a data management layer between the data adapter layer and the consumer layer (the forwarders 204 can forward data from the data sources 203 to the indexers 206, see Rao et al., Para. 619), the data management layer comprising a data storage the data in the data source independent format (the aggregated partial search results can be stored in memory at worker nodes, see Rao et al., Para. 537), at least one data manager executing instructions from the consumer application software (each of the search heads 226 may also have an additional software or process that is installed and running on it (e.g., daemon 232), see Rao et al., Para. 510), a processor (one or more hardware processors configured to execute the instructions stored in the one or more memories, see Rao et al., Para. 143), and a memory storing instructions being executed by the processor and causing the at least one data manager to select application-specific data in the data storage (the indexers to which the query was distributed, search data stores associated with them for events that are responsive to the query, see Rao et al., Para. 263, the search head 210 can engage the search service 220 when a search query is to be applied to at least one external data system, see Rao et al., Para. 429). However, Rao et al. does not explicitly teach to make them accessible to a consumer via the consumer application software in a consumer format; the data adapter layer and the data management layer are arranged in a laboratory gateway connected to the data-source layer and to the consumer layer. Heilig et al. teaches to make them accessible to a consumer via the consumer application software in a consumer format (a plug-in can be added to data router 208 each time a new producer is integrated into diagnostic laboratory network 200 where that new producer provides data in a unique format, i.e., a format that data router 208 does not have the ability to translate. Because data router 208 is configured to incorporate plug-ins specific to each new translation operation, diagnostic laboratory network 200 can be easily modified by integrating new producers, see Heilig et al., Para. 27); the data adapter layer and the data management layer are arranged in a laboratory gateway (the data router provides a streaming and/or a query data access capability, see Heilig et al., Para. 24, data router 452, which translates the information into the common format, see Heilig et al., Para. 59) connected to the data-source layer (The data router may manage its memory and/or data storage resources, see Heilig et al., Para. 31) and to the consumer layer (the streaming model data is pushed from producers to the data router where it is translated into a predetermined format and stored pending retrieval for delivery to subscribers, see Heilig et al., Para. 24). Therefore, 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 method of Rao et al., to have to make them accessible to a consumer via the consumer application software in a consumer format; the data adapter layer and the data management layer are arranged in a laboratory gateway connected to the data-source layer and to the consumer layer, as taught by Heilig et al., to have an improved ability to integrate additional producers into a system without having to make changes to the subscriber (Heilig et al., Para. 47). As to claim 3, Rao et al. teaches the consumer layer comprises at least one consumer device as interface device installing and/or executing of the consumer application software (a user may install a software application on server computers owned by the user and configure each server to operate as one or more of … an indexer, see Rao et al., Para. 165). As to claim 4, Rao et al. teaches the consumer application software and the application-specific data made accessible by the consumer application software are subscription-based (a user may install a software application on server computers owned by the user and configure each server to operate as one or more of a forwarder, an indexer, a search head, etc., see Rao et al., Para. 165. These input data sources and forwarders may be in a subscriber's private computing environment, see Rao et al., Para. 167). As to claim 6, Rao et al. teaches the application-specific data comprise any one or more of events occurred during laboratory device use or maintenance, event-triggered alerts or messages, use and/or consumption data, laboratory device status or configuration data, laboratory device operational parameters, QC data, laboratory device test result data (The system stores the events in a data store. The system enables users to run queries against the stored events, see Rao et al., Para. 137, the IT monitoring application can recognize notable events that may indicate a service performance problem or other situation of interest. These notable events can be recognized by a "correlation search" specifying trigger criteria for a notable event, see Rao et al., Para. 395). As to claim 7, Rao et al. teaches the consumer format comprises a report or display of application-specific data as such and/or after being elaborated into statistical, analytical or predictive data (One or more report formats can be associated with a particular data model and be made available to run against the data model, see Rao et al., Para. 321. The report generator allows the user to specify one or more fields within events and apply statistical analysis on values extracted from the specified one or more fields. The report generator may aggregate search results across sets of events and generate statistics based on aggregated search results, see Rao et al., Para. 322). As to claim 8, Rao et al. teaches the at least one data manager or the consumer application software includes a comparison function for comparing the application-specific data with predetermined reference or threshold values and an alert function or action trigger function in response to the application- specific data deviating from the reference or threshold values (datasets which are determined to be frequently accessed by a user can be stored in the lower-latency memory. Similarly, datasets of less than a threshold size can be stored in the lower-latency memory, see Rao et al., Para. 628). As to claim 11, Rao et al. teaches the laboratory gateway is scalable by locally or remotely adding/removing/updating data source agents md/or data managers and/or services (additional indexers may be added to the system, on which additional worker nodes can be instantiated on, see Rao et al., Para. 558). As to claim 13, Rao et al. teaches the at least one consumer device is a mobile hand-held device (104. Examples of client devices 102 may include, without limitation, smart phones, see Rao et al., Para. 148). As to claim 15, Rao et al. teaches the at least one laboratory device is an apparatus or module within a larger connected system involved in sample processing for in- vitro-diagnostics (the system 16 can apply the same processing task or rule to data from different indexes and time ranges to determine a record generation estimate for different combinations of the processing task, see Rao et al., Para. 1207), wherein the at least one laboratory device is related to analytical and/or to pre- analytical and/or to post-analytical sample processing (obtains a sample set of data. The sample set of data can be identified and obtained based on one or more data criteria. For example, the sample set of data can be identified and retrieved based on a determined range of time and index (or data store partition), see Rao et al., Para. 1236), and wherein the application-specific data comprising any one or more of events occurred during laboratory device use or maintenance, event-triggered alerts or messages, use and/or consumption data, laboratory device status or configuration data, laboratory device operational parameters, QC data, and laboratory device test result data (The system stores the events in a data store. The system enables users to run queries against the stored events, see Rao et al., Para. 137, the IT monitoring application can recognize notable events that may indicate a service performance problem or other situation of interest. These notable events can be recognized by a "correlation search" specifying trigger criteria for a notable event, see Rao et al., Para. 395). As to claim 16, Rao et al. teaches wherein sample processing comprises detection of qualitative and/or quantitative evaluation of samples for diagnostic purposes, and/or sorting and/or preparation of samples before detection, and/or storing and/or disposal of samples after detection (the sample set of data can correspond to data within a particular time range that is obtained from a particular index, and/or has a particular source type, see Rao et al., Para. 1206). Claim 2 is rejected under 35 U.S.C. 103 as being unpatentable over Rao et al. (U.S. Pat. Pub. 2021/0117425) in view of Heilig et al. (U.S. Pat. No. 2020/0395121) as applied to claims 1, 3, 4, 6-8, 11, 13, 15 and 16 above, and in further view of Datta (U.S. Pat. No. 10296594). As to claim 2, Rao et al. teaches the at least one data source agent is programmed to receive data as direct messages from the at least one data source or to query the at least one data source about specific data (a data intake and query system may cause output of the search results or data indicative of the search results on a display device, see Rao et al., Para. 576). However, Rao et al. does not explicitly teach either in response to a particular one or more data-source events or at regular time intervals and to determine data changes between queries. Datta teaches either in response to a particular one or more data-source events or at regular time intervals and to determine data changes between queries (a client device 304 can transmit a request for determining updates made during a specific time period, see Datta, Col. 8, lines 64-65). Therefore, 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 method of Rao et al. as modified, to have either in response to a particular one or more data-source events or at regular time intervals and to determine data changes between queries, as taught by Datta, to allows customers to selectively and thus, efficiently retrieve only such files from Network Attached Storage (NAS) storage (Datta, Para. Col. 1, lines 27-29). Claim 5 is rejected under 35 U.S.C. 103 as being unpatentable over Rao et al. (U.S. Pat. Pub. 2021/0117425) in view of Heilig et al. (U.S. Pat. No. 2020/0395121) as applied to claims 1, 3, 4, 6-8, 11, 13, 15 and 16 above, and in further view of Hanna (U.S. Pat. Pub. 2015/0347096). As to claim 5, Rao et al. as modified does not explicitly teach the consumer application software is downloadable from a cloud and installed onto the at least one consumer device or wherein the consumer application software is a cloud-based progressive web application (PWA) executable via the at least one consumer device. However, Hanna teaches the consumer application software is downloadable from a cloud and installed onto the at least one consumer device or wherein the consumer application software is a cloud-based progressive web application (PWA) executable via the at least one consumer device (one or more third-party software packages are downloaded from the cloud to be integrated into a model, see Hanna, Para.88). Therefore, 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 method of Rao et al. as modified, to have the consumer application software is downloadable from a cloud and installed onto the at least one consumer device or wherein the consumer application software is a cloud-based progressive web application (PWA) executable via the at least one consumer device, as taught by Hanna, to allows a novice level user lacking computer coding skills to develop complex algorithms (Hanna, Para. 4). Claims 9 and 10 are rejected under 35 U.S.C. 103 as being unpatentable over Rao et al. (U.S. Pat. Pub. 2021/0117425) in view of Heilig et al. (U.S. Pat. No. 2020/0395121) as applied to claims 1, 3, 4, 6-8, 11, 13, 15 and 16 above, and in further view of Yung et al. (U.S. Pat. Pub. 2004/0039531). As to claim 9, , Rao et al. as modified does not explicitly teach the data source layer comprises a plurality of laboratory devices as data sources, including at least one analytical device and at least one robotic device configured to interact with the at least one analytical device. However, Yung et al. teaches the data source layer comprises a plurality of laboratory devices as data sources, including at least one analytical device and at least one robotic device configured to interact with the at least one analytical device (analytical system having a control system 100 in communication with some possible types of devices associated with biological measurements. Such devices may include, by way example, one or more sample storage device 102, one or more sample transfer device 104, see Yung et al., Para. 34). Therefore, 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 method of Rao et al. as modified, to have the data source layer comprises a plurality of laboratory devices as data sources, including at least one analytical device and at least one robotic device configured to interact with the at least one analytical device, as taught by Yung et al., to allow effective management of relatively large numbers of different types of devices (Yung et al., Para. 37). As to claim 10, Rao et al. as modified teaches the at least one data manager is programmed to process data from the at least one analytical device and responsive to the processed data to instruct the at least one robotic device directly or via the respective data source agent to interact with the at least one analytical device (issue standardized commands to a given device in response to the standardized states monitored, see Yung et al., Para. 60. FIG. SC illustrates a state 410 of the robotics device. The device state 410 comprises a normal state 412 having a standby state 414 and a "transporting" state 416, and a fault state 420, see Yung et al., Para. 83. If the control system issues the STANDBY command, the device is instructed to go into its standby state (via the idle state) if not in the standby state. If the device is already in the standby state, then the device is instructed to continue its standby operation, see Yung et al., Para. 97). Claim 12 is rejected under 35 U.S.C. 103 as being unpatentable over Rao et al. (U.S. Pat. Pub. 2021/0117425) in view of Heilig et al. (U.S. Pat. No. 2020/0395121) as applied to claims 1, 3, 4, 6-8, 11, 13, 15 and 16 above, and in further view of Allen (U.S. Pat. No. 10,049,222). As to claim 12, Rao et al. as modified does not explicitly teach adding new services comprises adding at least one new data manager a priori, which is to be activated at any time by installing and/or subscribing to new consumer application software that communicates with the at least one previously added data manager thereby granting the consumer access to additional application-specific data in the data storage. However, Allen teaches adding new services comprises adding at least one new data manager a priori, which can then be activated at any time by installing and/or subscribing to new consumer application software that communicates with the at least one previously added data manager (Execution of the application by the mobile device 108 may require an operating system of the mobile device 108 to provide the application access to various components of the mobile device, including other applications., see Allen, Col. 3, lines 48-52) thereby granting the consumer access to additional application-specific data in the data storage (receiving an application image corresponding to an application to be installed on a mobile device;… granting a set of permissions to the application of the mobile device, the set of permissions enabling the application to access data marked as sensitive data by an operating system of the mobile device, see Allen, Col. 21, lines 49-58). Therefore, 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 method of Rao et al. as modified, to have adding new services comprises adding at least one new data manager a priori, which can then be activated at any time by installing and/or subscribing to new consumer application software that communicates with the at least one previously added data manager thereby granting the consumer access to additional application-specific data in the data storage, as taught by Allen, to have improvements in application security for mobile devices or other devices containing sensitive or private information. (Allen, Col. 2, lines 3-5). Claims 14 and 17 are rejected under 35 U.S.C. 103 as being unpatentable over Rao et al. (U.S. Pat. Pub. 2021/0117425) in view of Heilig et al. (U.S. Pat. No. 2020/0395121) as applied to claims 1, 3, 4, 6-8, 11, 13, 15 and 16 above, and in further view of Bradley (U.S. Pat. Pub. 2006/0238919). As to claim 14, Rao et al. teaches one or more gatekeepers configured for filtering data converted by the at least one data source agent (selecting a bin may cause the GUI to display the events of the search results that are timestamped within a range of the corresponding group, see Rao et al., Para. 598). However, Rao et al. as modified does not explicitly teach validating data converted by the at least one data source agent. Bradley teaches validating data converted by the at least one data source agent (data validating step further includes the steps of: normalizing said data loaded from at least two source systems to a common format; adjusting unique data identifiers to a common format; flagging invalid, unrecognized, and missing item identifiers for review, see Bradley, claim 3). Therefore, 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 method of Rao et al. as modified, to have validating data converted by the at least one data source agent, as taught by Bradley, to enable consistent analysis, eliminates one time database coding, and reduces the time required to adjust to changing data sources (Bradley, Para. 22). Referring to claim 17, a laboratory data management system comprising: a data source layer comprising at least one laboratory device as a data source (common storage 4602 may correspond to a storage area network (SAN), network attached storage (NAS), other network-accessible storage system (e.g., a hosted storage system, which may also be referred to as "cloud" storage), see Rao et al., Para. 844), a data adapter layer comprising at least one data source agent obtaining data from the at least one data source (the search service 220 can start executing the search phases of the DAG that cause the worker nodes 214 to search the external data sources 209. Then, in step 2116, the worker nodes 214 collect the partial search results extracted from the external data sources 209, see Rao et al., Para. 438. The index cache components 254 are communicatively coupled to the cloud worker nodes 246, which can collect partial search results from the cloud storage 256 by applying a search query to the index cache components 254, see Rao et al., Para. 565 ) and converting the data from a data source format to a data source independent format (the worker nodes receive the partial search results collected from the data sources and transform them into a specified format. As such, partial search results in diverse formats can be transformed into a common specified format….diverse data types obtained from diverse data sources can be transformed into a common format to facilitate subsequent aggregation across all the partial search results obtained in response to the search query, see Rao et al., Para. 465), a consumer layer comprising consumer application software (a user may install a software application on server computers owned by the user and configure each server to operate as one or more of … an indexer, see Rao et al., Para. 165) comprising instructions to be executed by the data manager (each of the search heads 226 may also have an additional software or process that is installed and running on it (e.g., daemon 232), see Rao et al., Para. 510), a data management layer between the data adapter layer and the consumer layer (the forwarders 204 can forward data from the data sources 203 to the indexers 206, see Rao et al., Para. 619), wherein, the data management layer comprising: at least one data manager executing instructions from the consumer application software (each of the search heads 226 may also have an additional software or process that is installed and running on it (e.g., daemon 232), see Rao et al., Para. 510), a processor (one or more hardware processors configured to execute the instructions stored in the one or more memories, see Rao et al., Para. 143), and a memory storing processor instructions to be executed by the processor (one or more hardware processors configured to execute the instructions stored in the one or more memories, see Rao et al., Para. 143), the executed instructions causing the at least one data manager to select the application-specific data in the data storage (the indexers to which the query was distributed, search data stores associated with them for events that are responsive to the query, see Rao et al., Para. 263, the search head 210 can engage the search service 220 when a search query is to be applied to at least one external data system, see Rao et al., Para. 429) and, the processor executing the processor instructions (one or more hardware processors configured to execute the instructions stored in the one or more memories, see Rao et al., Para. 143). However, Rao et al. does not explicitly teach the data adapter layer and the data management layer are arranged in a laboratory gateway connected to the data source layer and to the consumer layer, a data storage storing data converted by the at least one data source agent, making the application-specific data accessible to a consumer via the consumer application software in a consumer format. Heilig et al. teaches the data adapter layer and the data management layer are arranged in a laboratory gateway (the data router provides a streaming and/or a query data access capability, see Heilig et al., Para. 24, data router 452, which translates the information into the common format, see Heilig et al., Para. 59) connected to the data source layer (The data router may manage its memory and/or data storage resources, see Heilig et al., Para. 31) and to the consumer layer (the streaming model data is pushed from producers to the data router where it is translated into a predetermined format and stored pending retrieval for delivery to subscribers, see Heilig et al., Para. 24), making the application-specific data accessible to a consumer via the consumer application software in a consumer format (a plug-in can be added to data router 208 each time a new producer is integrated into diagnostic laboratory network 200 where that new producer provides data in a unique format, i.e., a format that data router 208 does not have the ability to translate. Because data router 208 is configured to incorporate plug-ins specific to each new translation operation, diagnostic laboratory network 200 can be easily modified by integrating new producers, see Heilig et al., Para. 27). Therefore, 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 method of Rao et al., to the data adapter layer and the data management layer are arranged in a laboratory gateway connected to the data source layer and to the consumer layer, making the application-specific data accessible to a consumer via the consumer application software in a consumer format, as taught by Heilig et al., to have an improved ability to integrate additional producers into a system without having to make changes to the subscriber (Heilig et al., Para. 47). However, Rao et al. as modified still does not explicitly teach a data storage storing data converted by the at least one data source agent. Bradley teaches a data storage storing data converted by the at least one data source agent (data validating step further includes the steps of: normalizing said data loaded from at least two source systems to a common format; adjusting unique data identifiers to a common format; flagging invalid, unrecognized, and missing item identifiers for review, see Bradley, claim 3). Therefore, 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 method of Rao et al. as modified, to have a data storage storing data converted by the at least one data source agent, as taught by Bradley, to enable consistent analysis, eliminates one time database coding, and reduces the time required to adjust to changing data sources (Bradley, Para. 22). Response to Argument Applicant’s remarks filed on 7/22/2026 with respect to claims 1 has been considered but they are not persuasive. Applicant’s argues that “Claim 1 of the present application, in contrast, requires a data management layer in the laboratory gateway, including data storage and at least one data manager programmed to execute instructions from consumer application software to select application-specific data in the data storage and make that selected data accessible via the consumer application software in a consumer format.” The Examiner does not agree, because the Applicant describes the system architecture of references specifically. However, the Examiner teaches claim 1 limitation by 35 USC § 103 rejection by the combination of Rao et al. and Heilig et al.. Please referring to the rejection in claim 1. Conclusion 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 nonprovisional extension fee (37 CFR 1.17(a)) 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 JAU SHYA MENG whose telephone number is (571)270-1634. The examiner can normally be reached 9AM-5PM EST M-F. 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, Charles Rones can be reached at 571-272-4085. 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. /JAU SHYA MENG/Primary Examiner, Art Unit 2168
Read full office action

Prosecution Timeline

Show 6 earlier events
Mar 02, 2026
Applicant Interview (Telephonic)
Mar 27, 2026
Request for Continued Examination
Apr 02, 2026
Response after Non-Final Action
Apr 22, 2026
Non-Final Rejection mailed — §103
Jun 26, 2026
Examiner Interview Summary
Jun 26, 2026
Applicant Interview (Telephonic)
Jul 22, 2026
Response Filed
Oct 05, 2026
Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12737566
ADVANCED MACHINE LEARNING METHODS FOR ENHANCED CALL TRANSCRIPT ANNOTATION AND TARGETED ANALYTICS REPORT GENERATION
2y 5m to grant Granted Sep 15, 2026
Patent 12689753
VIRTUAL FILE SYSTEM FOR CLOUD-BASED SHARED CONTENT
3y 1m to grant Granted Jul 21, 2026
Patent 12675373
METHOD, DEVICE, AND COMPUTER PROGRAM PRODUCT FOR RECOVERING DATA
1y 8m to grant Granted Jul 07, 2026
Patent 12675466
DECENTRALIZED TWO-PHASE COMMIT
1y 3m to grant Granted Jul 07, 2026
Patent 12670179
CLOUD-BASED REPLICATION TO CLOUD-EXTERNAL SYSTEMS
2y 11m to grant Granted Jun 30, 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

5-6
Expected OA Rounds
79%
Grant Probability
99%
With Interview (+33.9%)
3y 6m (~3m remaining)
Median Time to Grant
High
PTA Risk
Based on 570 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