Prosecution Insights
Last updated: August 18, 2026
Application No. 17/898,826

SYSTEM AND METHOD INCORPORATING MODULAR DATA ENCRYPTION FOR AN ELECTRONIC DEVICE

Non-Final OA §103
Filed
Aug 30, 2022
Examiner
MAYE, AYUB A
Art Unit
2436
Tech Center
2400 — Computer Networks
Assignee
Genesee Valley Innovations LLC
OA Round
5 (Non-Final)
58%
Grant Probability
Moderate
5-6
OA Rounds
6m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 58% of resolved cases
58%
Career Allowance Rate
380 granted / 658 resolved
At TC average
Strong +42% interview lift
Without
With
+42.1%
Interview Lift
resolved cases with interview
Typical timeline
4y 6m
Avg Prosecution
33 currently pending
Career history
693
Total Applications
across all art units

Statute-Specific Performance

§101
2.8%
-37.2% vs TC avg
§103
59.4%
+19.4% vs TC avg
§102
16.4%
-23.6% vs TC avg
§112
14.4%
-25.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 658 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 . Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 05/18/2026 has been entered. 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. The factual inquiries 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. Claims 1, 7-9 and 15-16 are rejected under 35 U.S.C. 103 as being unpatentable over Zhu et al (2021/0409335) in views of Zakian et al (11782978), Ramanathan et al (10735406) and Parks et al (2015/0186305). For claim 1, Zhu teaches A system (fig.20) (abstract) comprising: sensors (sensor devices 2011 as shown in fig.20 sensors, or “things” capable of capturing and/or recording data associated with an event, and capable of communicating such data with one or more other devices over a network with little or no user intervention) (par.576, lines 1-10); a first data storage element (2036a as shown in fig.20 is computing system that provides compute, storage, and network resources to edge computing applications)(par.601,lines 1-12); a second data storage element (either 2036b or 2036c as shown in fig.20 is computing system that provides compute, storage, and network resources to edge computing applications)(par.601,lines 1-12); a first processor and a first memory (in par.603, Zhu teaches that each of the 2036 as shown in fig.20 includes processor and memory storage and processing resources so that data and/or content can be processed in close proximity to subscribers) having code or instructions stored thereon that, when executed by the first processor, cause the first processor to collect first sensor data, and store the first sensor data on the first data storage element (each of element 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links) (par.576, lines 5-14, par.585, lines 1-3, par.586, lines 1-5; and, par.603, lines 1-12, sensors, par.617); a second processor and a second memory (in par.603, Zhu teaches that each of the 2036b or 2036c which can be the second processor and second memory, as shown in fig.20 includes processor and memory storage and processing resources so that data and/or content can be processed in close proximity to subscribers) having stored thereon code or instructions that, when executed by the second processor, cause the second processor to collect and process second sensor data (each of element 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links) (par.576, lines 5-14, par.585, lines 1-3, par.586, lines 1-5; and, par.603, lines 1-12), periodically retrieve the first sensor data from the first data storage element by reviewing the first data storage element (element 2036b or 2036c as shown in fig.20 can obtain sensor data from other storage 2036 in periodic basis, therefore, each processing devices 2036 can obtain multiple sensor devices data and also can exchange the sensor data with other processing devices 2036 in par.585, lines 1-4 and par.586, lines 1-5). Zhu fails to teach, by selecting at least a portion of the first sensor data collected by the first processor and by copying the selected first sensor data to the second memory, encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data and the second sensor data in the second data storage element in individually accessible data lockers arranged according to a time period when the sensor data was collected or generated, or data type, and wherein the second processor is a higher power processor than the first processor. Zakian teaches, similar data, by selecting at least a portion of the first sensor data collected by the first processor and by copying the selected first sensor data to the second memory (Zakian teaches that generating a third file by at least copying the first file stored in the cache memory, the third file storing second video data corresponding a copy of the first video data as Zakian teaches in col.35, lines 35-45)(abstract), encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data and the second sensor data in the second data storage element (Zakian teaches that he process 400 may include encrypting the video data to generate encrypted video data. For instance, based at least in part on determining that the frames represent the event, the computing device(s) 202 may determine to archive the frames. As such, the computing device(s) 202 may initially encrypt the video data to generate the encrypted video data, encrypting the second video data stored in the third file to generate encrypted video data; and storing the third file in the archive memory which means that the encrypted data includes both copied first and second files data as Zakian teaches in col.16, lines 28-60 and col.35, lines 40-50) (abstract) in individually accessible data arranged according to a time period when the sensor data was collected or generated, or data type (Zakian teaches that computing device(s) may further store metadata describing the sensor data, such as in a first metadata buffer of the first memory. For example, the metadata may include timestamp(s) of when the sensor data was generated, timestamp(s) of when the data files were last accessed, timestamp(s) of when the sensor data in the data files was last modified, timestamp(s) of when the metadata was last changed, an identifier of the sensor that generated the sensor data, and/or the like. In some instances, the computing device(s) store the metadata in one or more files (also referred to as “metadata files”) that correspond to the one or more data files that the computing device(s) use to store the sensor data. Additionally, in such an example, the metadata files may include identifiers that correspond to the identifiers of the data files as Zakian teaches in col.3, lines 25-40). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data as taught and suggested by Zakian for purpose of ensuring that the sensor data is already stored in the memories when performing one or more operations associated with the sensor data and in order to be able to finish any operations on the sensor data without the sensor data being deleted (Zakian, col.5, lines40-45). Zhu, as modified by Zakian, do not explicitly teach store the encrypted sensor data in individually accessible data lockers arranged according to a time period and wherein the second processor is a higher power processor than the first processor. Ramanathan teaches, similar data system, store the encrypted sensor data in individually accessible data lockers arranged according to a time period (Ramanathan teaches the customer centric grid can provide secure areas for storing a subset of customer data that can be transmitted to a service provider, each subset of such customer data is referred to as a locker, the customer data can be stored in the locker for a limited period of time, corresponding to a policy for the data and each item of customer data can be stored in a separate secure area, referred herein as a micro locker, and customer data in each information locker can comprise customer data in a plurality of micro lockers as Ramanathan teaches col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Zakian, to include data lockers as taught and suggested by Ramanathan for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). Zhu, as modified by Zakian and Ramanathan, do not explicitly teach wherein the second processor is a higher power processor than the first processor. Parks teaches, similar system, wherein the second processor is a higher power processor than the first processor (abstract) (Parks teaches that One processor may operate in a higher power mode than another and may power or control a peripheral device as Parks teaches in par.6). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Zakian and Ramanathan, to include the second processor is a higher power processor than the first processor as taught and suggested by Parks for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claim 7, Zhu in view of Zakian, Ramanathan and Parks further teach the system of claim 1. Zhu further teaches wherein symbolic links to files stored in the storage are maintained to provide a catalog of available files to subcomponents of the system (par.641 and par.702). Zhu fails to teach data lockers. Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include data lockers as taught and suggested by Simmons for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claim 8, Zhu in view of Zakian, Ramanathan and Parks further teach the system of claim 1. Zhu further teaches wherein the symbolic links are maintained in a flash storage of a device accessing the storage (par.711). Zhu fails to teach data lockers. Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include data lockers as taught and suggested by Simmons for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claim 9, Zhu teaches a method to be implemented on a system having sensors (sensors devices 2011 as shown in fig.20 sensors, or “things” capable of capturing and/or recording data associated with an event, and capable of communicating such data with one or more other devices over a network with little or no user intervention) (par.576, lines 1-10), a first data storage element (2036a as shown in fig.20 is computing system that provides compute, storage, and network resources to edge computing applications)(par.601,lines 1-12), a second data storage element (either 2036b or 2036c as shown in fig.20 is computing system that provides compute, storage, and network resources to edge computing applications)(par.601,lines 1-12), a first processor and a second processor (in par.603, Zhu teaches that each of the 2036 as shown in fig.20 includes processor and memory storage and processing resources so that data and/or content can be processed in close proximity to subscribers), the method comprising: collecting, by the first processor, first sensor data (each of element 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links) (par.576, lines 5-14, par.585, lines 1-3, par.586, lines 1-5; and, par.603, lines 1-12); storing, by the first processor, the first sensor data on the first data storage element (each of element 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links) (par.576, lines 5-14, par.585, lines 1-3, par.586, lines 1-5; and, par.603, lines 1-12); collecting and processing, by the second processor, second sensor data (in par.603, Zhu teaches that each of the 2036b or 2036c which can be the second processor and second memory, as shown in fig.20 includes processor and memory storage and processing resources so that data and/or content can be processed in close proximity to subscribers); periodically retrieving, by the second processor, the first sensor data from the first data storage element, comprising reviewing the first data storage element (element 2036b or 2036c as shown in fig.20 can obtain sensor data from other storage 2036 in periodic basis, therefore, each processing devices 2036 can obtain multiple sensor devices data and also can exchange the sensor data with other processing devices 2036 in par.585, lines 1-4 and par.586, lines 1-5). Zhu fails to teach selecting at least a portion of the first sensor data collected by the first processor and copying the selected first sensor data to the second data storage element, encrypting, by the second processor, the copied first sensor data and the second sensor data; and, storing, by the second processor, the encrypted sensor data in the second data storage element in individually accessible data lockers arranged according to a time period when the sensor data was collected or generated, or data type, and wherein the second processor is a higher power processor than the first processor Zakian teaches, similar data, selecting at least a portion of the first sensor data collected by the first processor and copying the selected first sensor data t to the second data storage element (Zakian teaches that generating a third file by at least copying the first file stored in the cache memory, the third file storing second video data corresponding a copy of the first video data as Zakian teaches in col.35, lines 35-45)(abstract), encrypting, by the second processor, the copied first sensor data with the second sensor data, and storing, by the second processor, the encrypted sensor data comprising both the copied first sensor data and the second sensor data in the second data storage element (Zakian teaches that he process 400 may include encrypting the video data to generate encrypted video data. For instance, based at least in part on determining that the frames represent the event, the computing device(s) 202 may determine to archive the frames. As such, the computing device(s) 202 may initially encrypt the video data to generate the encrypted video data, encrypting the second video data stored in the third file to generate encrypted video data; and storing the third file in the archive memory which means that the encrypted data includes both copied first and second files data as Zakian teaches in col.16, lines 28-60 and col.35, lines 40-50) (abstract) in individually accessible data arranged according to a time period when the sensor data was collected or generated, or data type (Zakian teaches that computing device(s) may further store metadata describing the sensor data, such as in a first metadata buffer of the first memory. For example, the metadata may include timestamp(s) of when the sensor data was generated, timestamp(s) of when the data files were last accessed, timestamp(s) of when the sensor data in the data files was last modified, timestamp(s) of when the metadata was last changed, an identifier of the sensor that generated the sensor data, and/or the like. In some instances, the computing device(s) store the metadata in one or more files (also referred to as “metadata files”) that correspond to the one or more data files that the computing device(s) use to store the sensor data. Additionally, in such an example, the metadata files may include identifiers that correspond to the identifiers of the data files as Zakian teaches in col.3, lines 25-40). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data as taught and suggested by Zakian for purpose of ensuring that the sensor data is already stored in the memories when performing one or more operations associated with the sensor data and in order to be able to finish any operations on the sensor data without the sensor data being deleted (Zakian, col.5, lines40-45). Zhu, as modified by Zakian, do not explicitly teach store the encrypted sensor data in individually accessible data lockers arranged according to a time period and wherein the second processor is a higher power processor than the first processor. Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Zakian, to include data lockers as taught and suggested by Ramanathan for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). Zhu, as modified by Zakian and Ramanathan, do not explicitly teach wherein the second processor is a higher power processor than the first processor. Parks teaches, similar system, wherein the second processor is a higher power processor than the first processor (abstract) (Parks teaches that One processor may operate in a higher power mode than another and may power or control a peripheral device as Parks teaches in par.6). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Zakian and Ramanathan, to include the second processor is a higher power processor than the first processor as taught and suggested by Parks for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claim 15, Zhu in view of Zakian, Ramanathan and Parks further teach the method of claim 9. Zhu further teaches wherein symbolic links to files stored in the storage modules are maintained to provide a catalog of available files to subcomponents of the system (par.641 and par.702). Zhu fails to teach data lockers. Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include data lockers as taught and suggested by Simmons for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claim 16, Zhu in view of Zakian, Ramanathan and Parks further teach the method of claim 9. Zhu further teaches wherein the symbolic links are maintained in a flash storage of a device accessing the storage modules (par.711). Claim(s) 2-3 and 10-11 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhu et al (2021/0409335) in views of, Zakian et al (11782978), Ramanathan et al (10735406) and Parks et al (2015/0186305) as applied to claims above, and further in view of Simmons et al (2017/0083713). For claims 2 and 10, Zhu, as modified by Zakian, Ramanathan and Parks, teaches all the limitations as previously set forth except for wherein the first processor is further caused to retrieve encrypted sensor data from one or more of the data lockers of the second data storage element in response to, and for transmission to, an interrogation device. Simmons teaches wherein the first processor is further caused to retrieve encrypted sensor data from selected modules of the second data storage element in response to, and for transmission to, an interrogation device (Storage device 200 includes a processor 202, which controls the overall operation of storage device receives the encrypted data and messages and sends the encrypted data and messages via either Internet)(par.64, lines 1-7, par.65, lines 1-6, par.67, lines1-5 and par.78). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include retrieve encrypted sensor data from selected storage modules t as taught and suggested by Simmons for purpose of sending the encrypted data to a backup server for storage without jeopardizing the security of the data and helping improve privacy and security associated with data storage (Simmons, par.21). Zhu fails to teach data lockers. Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include data lockers as taught and suggested by Simmons for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claims 3 and 11, Zhu in view of Zakian, Ramanathan and Parks further teach the system of claim 1. Zhu further teaches wherein the second processor is further caused to trigger transmission of sensor data from the second data storage element to a satellite (the second processor 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links which satellite signal) (par.584, lines 1-20). However, Zhu fails to teach transmission encrypted sensor data. Simmons further teaches transmission encrypted sensor data (abstract). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include transmission encrypted sensor data as taught and suggested by Simmons for purpose of sending the encrypted data to a backup server for storage without jeopardizing the security of the data and helping improve privacy and security associated with data storage (Simmons, par.21). Claim(s) 4 and 12 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhu et al (2021/0409335) in views of Zakian et al (11782978), Ramanathan et al (10735406) and Parks et al (2015/0186305) as applied to claims above, and further in view of Talaalout et al (2016/0320503). For claims 4 and 12, Zhu, as modified by Zakian, Ramanathan and Parks, teaches all the limitations as previously set forth except for wherein the system is incorporated on a float device. Talaalout teaches, similar data system, wherein the system is incorporated on a float device (par.86). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Zakian, Ramanathan and Parks, to include float device as taught and suggested by Talaalout for purpose of collecting seismic data with improved coupling between the seismic sensor and ground. As noted above, the ground can be above or below water (Talaalout, par.86). Claim(s) 5-6 and 13-14 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhu et al (2021/0409335) in views of Zakian et al (11782978), Ramanathan et al (10735406) and Parks et al (2015/0186305) as applied to claims above, and further in view of Shelton (2019/0125459). For claims 5 and 13, Zhu, as modified by Zakian and Ramanathan and Parks, teaches all the limitations as previously set forth except for wherein the data lockers are deleted when determined to be no longer relevant based on information associated with the storage module. Shelton teaches, similar data system, wherein the storage modules are deleted when determined to be no longer relevant based on information associated with the storage module (par.912, lines 10-15 and par.1961, lines 3-8). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Zakian and Ramanathan and Parks to include the storage modules are deleted when determined to be no longer relevant as taught and suggested by Shelton for purpose of ensuring the data cannot be recovered and to maintain patient anonymity (Shelton, par.912, lines 10-15). Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include data lockers as taught and suggested by Zakian for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claims 6 and 14, Zhu, as modified by Zakian and Ramanathan and Parks, teaches all the limitations as previously set forth except for wherein the information associated with the data locker is acquisition date. Shelton further teaches, similar data system, wherein the information associated with the storage module is acquisition date (par.1484, lines 2-6). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include with the storage module is acquisition date as taught and suggested by Shelton for purpose of showing how the data is analyzed by the cloud system to provide a comparison between multiple facilities to compare use of resources and to determine best outcomes based on any and all of these variables, or even one or more combinations of them (Shelton, par.1484, lines 1-2). Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include data lockers as taught and suggested by Simmons for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). Claim(s) 17 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhu et al (2021/0409335) in view of Talaalout et al (2016/0320503), Zakian et al (11782978), and Ramanathan et al (10735406). For claim 17, Zhu teaches the apparatus having sensors positioned thereon to gather sensor data, the float apparatus (par.576) (abstract) comprising: sensors (sensor devices 2011 as shown in fig.20 sensors, or “things” capable of capturing and/or recording data associated with an event, and capable of communicating such data with one or more other devices over a network with little or no user intervention) (par.576, lines 1-10); an inertial measurement unit (par.584); a first data storage element (2036a as shown in fig.20 is computing system that provides compute, storage, and network resources to edge computing applications)(par.601,lines 1-12); a second data storage element (either 2036b or 2036c as shown in fig.20 is computing system that provides compute, storage, and network resources to edge computing applications)(par.601,lines 1-12); a first processor and a first memory (in par.603, Zhu teaches that each of the 2036 as shown in fig.20 includes processor and memory storage and processing resources so that data and/or content can be processed in close proximity to subscribers) having code or instructions stored thereon that, when executed by the first processor, cause the first processor to collect first sensor data, and store the first sensor data on the first data storage element (each of element 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links) (par.576, lines 5-14, par.585, lines 1-3, par.586, lines 1-5; and, par.603, lines 1-12, sensors, par.617); a second processor and a second memory (in par.603, Zhu teaches that each of the 2036b or 2036c which can be the second processor and second memory, as shown in fig.20 includes processor and memory storage and processing resources so that data and/or content can be processed in close proximity to subscribers) having stored thereon code or instructions that, when executed by the second processor, cause the second processor to collect and process second sensor data by selectively using the inertial measurement unit (each of element 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links and the measurements collected by the UEs 2021, 2011 and/or included in the measurement reports) (par.576, lines 5-14, par.585, lines 1-3, par.586, lines 1-5; and, par.603, lines 1-12), periodically retrieve the first sensor data from the first data storage element by reviewing the first data storage element (element 2036b or 2036c as shown in fig.20 can obtain sensor data from other storage 2036 in periodic basis, therefore, each processing devices 2036 can obtain multiple sensor devices data and also can exchange the sensor data with other processing devices 2036 in par.585, lines 1-4 and par.586, lines 1-5). Zhu fails to teach float apparatus sufficiently buoyant to float on the surface of a body of water, selecting at least a portion of the first sensor data and copying the selected first sensor data, encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data and the second sensor data in the data the lockers arranged according to a time period when the sensor data was collected or generated, or data type. Talaalout teaches, similar data system, float apparatus sufficiently buoyant to float on the surface of a body of water (par.86). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include float device as taught and suggested by Talaalout for purpose of collecting seismic data with improved coupling between the seismic sensor and ground. As noted above, the ground can be above or below water (Talaalout, par.86). Zhu, as modified by Talaalout, do not explicitly teach selecting at least a portion of the first sensor data and copying the selected first sensor data, encrypt the copied first sensor data with the second sensor data, and store the lockers arranged according to a time period when the sensor data was collected or generated, or data type. Zakian teaches, similar data, selecting at least a portion of the first sensor data and copying the selected first sensor data (Zakian teaches that generating a third file by at least copying the first file stored in the cache memory, the third file storing second video data corresponding a copy of the first video data as Zakian teaches in col.35, lines 35-45)(abstract), encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data and the second sensor data in the data (Zakian teaches that he process 400 may include encrypting the video data to generate encrypted video data. For instance, based at least in part on determining that the frames represent the event, the computing device(s) 202 may determine to archive the frames. As such, the computing device(s) 202 may initially encrypt the video data to generate the encrypted video data, encrypting the second video data stored in the third file to generate encrypted video data; and storing the third file in the archive memory which means that the encrypted data includes both copied first and second files data as Zakian teaches in col.16, lines 28-60 and col.35, lines 40-50) (abstract) in arranged according to a time period when the sensor data was collected or generated, or data type (Zakian teaches that computing device(s) may further store metadata describing the sensor data, such as in a first metadata buffer of the first memory. For example, the metadata may include timestamp(s) of when the sensor data was generated, timestamp(s) of when the data files were last accessed, timestamp(s) of when the sensor data in the data files was last modified, timestamp(s) of when the metadata was last changed, an identifier of the sensor that generated the sensor data, and/or the like. In some instances, the computing device(s) store the metadata in one or more files (also referred to as “metadata files”) that correspond to the one or more data files that the computing device(s) use to store the sensor data. Additionally, in such an example, the metadata files may include identifiers that correspond to the identifiers of the data files as Zakian teaches in col.3, lines 25-40). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data as taught and suggested by Zakian for purpose of ensuring that the sensor data is already stored in the memories when performing one or more operations associated with the sensor data and in order to be able to finish any operations on the sensor data without the sensor data being deleted (Zakian, col.5, lines40-45). Zhu, as modified by Talaalout and Zakian, do not explicitly teach store the lockers arranged according to a time period. Ramanathan teaches, similar data system, store the lockers arranged according to a time period (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Zakian, to include the lockers as taught and suggested by Ramanathan for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). Claim(s) 18-19 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhu et al (2021/0409335) Talaalout et al (2016/0320503) in view of Zakian et al (11782978), Ramanathan et al (10735406) as applied to claims above, and further in view of Simmons et al (2017/0083713). For claim 18, Zhu, as modified by, Zakian and Ramanathan and Parks, teaches all the limitations as previously set forth except for teach wherein the first processor is further caused to retrieve encrypted sensor data from one or more data lockers of the second data storage element in response to, and for transmission to, an interrogation device. Simmons further teaches wherein the first processor is further caused to retrieve encrypted sensor data from one or more modules of the second data storage element in response to, and for transmission to, an interrogation device (Storage device 200 includes a processor 202, which controls the overall operation of storage device receives the encrypted data and messages and sends the encrypted data and messages via either Internet)(par.64, lines 1-7, par.65, lines 1-6, par.67, lines1-5 and par.78). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include retrieve encrypted sensor data from selected storage modules t as taught and suggested by Simmons for purpose of sending the encrypted data to a backup server for storage without jeopardizing the security of the data and helping improve privacy and security associated with data storage (Simmons, par.21). Zhu fails to teach data lockers. Ramanathan further teaches data lockers (col.3, lines 65-68 to col.4, lines 1-10 and col.8, lines 55-68). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include data lockers as taught and suggested by Simmons for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). For claim 19, Zhu, as modified by, Zakian and Ramanathan and Parks, teaches all the limitations, Zhu further teaches wherein the second processor is further caused to trigger transmission of sensor data from the second data storage element to a satellite (the second processor 2036 which communicates with sensor devices 2011 and collect sensor data from the sensor devices thru the communication links which satellite signal) (par.584, lines 1-20). However, Zhu fails to teach transmission encrypted sensor data. Simmons further teaches transmission encrypted sensor data (abstract). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu to include transmission encrypted sensor data as taught and suggested by Simmons for purpose of sending the encrypted data to a backup server for storage without jeopardizing the security of the data and helping improve privacy and security associated with data storage (Simmons, par.21). Claim(s) 20 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhu et al (2021/0409335) Talaalout et al (2016/0320503) in view of Zakian et al (11782978), Ramanathan et al (10735406) and as applied to claims above, and further in view of Parks et al (2015/0186305). Zhu, as modified by Zakian, Ramanathan and Talaalout, teaches all the limitations as previously set forth except for wherein the second processor is a higher power processor than the first processor. Parks teaches, similar system, wherein the second processor is a higher power processor than the first processor (abstract) (Parks teaches that One processor may operate in a higher power mode than another and may power or control a peripheral device as Parks teaches in par.6). It would have been obvious to one ordinary skill in the art before effective filling date to modify Zhu, as modified by Simmons, Ramanathan and Talaalout, to include the second processor is a higher power processor than the first processor as taught and suggested by Parks for purpose of providing secure areas for storing a subset of customer data that can be transmitted to a service provider and providing who can access the customer data in the locker, for how long and what can be done with the customer data (Ramanathan, col.4, lines 5-7). Response to Amendments/Arguments Applicant’s arguments with respect to claim(s) 1-20 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument. The applicant’s arguments regarding new amendment limitations “encrypt the copied first sensor data with the second sensor data, and store the encrypted sensor data comprising both the copied first sensor data and the second sensor data” in claims 1, 9 and 17, has been considered but is moot, because the examiner applied new art, Zakian et al (11782978), that covers newly amendment limitation. Regarding dependent claims arguments, said arguments are moot because the applied references are not considered to have alleged differences, and therefore are considered to properly show that for which they were cited. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to AYUB A MAYE whose telephone number is (571)270-5037. 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, SHEWAYE GELAGAY can be reached at 571-272-4219. 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. /AYUB A MAYE/Examiner, Art Unit 2436 /SHEWAYE GELAGAY/Supervisory Patent Examiner, Art Unit 2436
Read full office action

Prosecution Timeline

Show 8 earlier events
Jun 20, 2025
Response after Non-Final Action
Aug 06, 2025
Non-Final Rejection mailed — §103
Nov 06, 2025
Response Filed
Feb 25, 2026
Final Rejection mailed — §103
Apr 24, 2026
Response after Non-Final Action
May 18, 2026
Request for Continued Examination
May 23, 2026
Response after Non-Final Action
Jun 25, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12665876
System and method for server monitoring and problem resolution for electronic mail messages
3y 8m to grant Granted Jun 23, 2026
Patent 12625987
METHOD AND SYSTEM FOR EXECUTING A SECURE FILE-LEVEL RESTORE FROM A BLOCK-BASED BACKUP
3y 9m to grant Granted May 12, 2026
Patent 12574211
PERSONAL PRIVATE KEY ENCRYPTION DEVICE
3y 10m to grant Granted Mar 10, 2026
Patent 12574247
DEVICE FOR COMPUTING SOLUTIONS OF LINEAR SYSTEMS AND ITS APPLICATION TO DIGITAL SIGNATURE GENERATIONS
3y 4m to grant Granted Mar 10, 2026
Patent 12547740
INFORMATION PROCESSING DEVICES AND INFORMATION PROCESSING METHODS
3y 2m to grant Granted Feb 10, 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
58%
Grant Probability
99%
With Interview (+42.1%)
4y 6m (~6m remaining)
Median Time to Grant
High
PTA Risk
Based on 658 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