DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This written action is responding to the Request for continued examination (RCE) dated on 12/22/2025.
Claims 1, 7-15, 17-19 and 21 have been amended, Claims 2-6, 16, 20 and 23 have been canceled and all other claims are previously presented.
Claims 1, 7-15, 17-19 and 21-22 are submitted for examination.
Claims 1, 7-15, 17-19 and 21-22 are pending.
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.
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 December 22, 2025 has been entered.
Examiner’s Note
Examiner had contacted the Applicant’s representative for further amending the claims for clarification and address the issue of 35 U.S.C 112(b) to allow the application with an Examiner’s amendment. The Applicant, declined the offer and requested an office action.
Priority
This 371 application filed on December 12, 2013 claims priority of PCT application PCT/EP2021/081367 filed on November 11, 2022 and foreign application DE102020130087.5 filed on November 13, 2020..
Information Disclosure Statement
The following Information Disclosure Statements in the instant application submitted in compliance with the provisions of 37 CFR 1.97, and thus, have been fully considered:
IDS filed on 14 August 2023.
Response to Arguments
Applicant’s amendment, filed on December 22, 2025, has claims 1, 7-15, 17-19 and 21 amended, Claim 2-6, 16, 20 and 23 canceled and all other claims are previously presented.
The prior objections of Claims 1, 4-11 and 21 for claim limitations having “and/or” have been withdrawn in view of the amendment received on December 22, 2025. However the objection to claim 12 is maintained.
The prior objections of Claims 1-12, 15-16 and 18-21 have been withdrawn in view of the amendment received on December 22, 2025.
The prior objections to drawing Figure 1 and Figure 2 have been withdrawn in view of the amendment received on December 22, 2025.
The prior 35 U.S.C. 112(b) rejection of Claims 2-3, 5,7, 11, 16 and 17 have been withdrawn in view of the amendment received on December 22, 2025.
Applicant’s argument regarding 35 U.S.C. 103 is persuasive and the Claims are allowable if the following objections and 35 U.S.C. 112(b) rejection is overcome.
Claim Objections
Claims 1 and 21 are objected to because of the following reason”
Claims 1 and 21 are amended with a recitation, “…automatic obtaining of the electronic data stream by the subscriber system, utilizing a subscription of the subscriber channel, is terminated automatically when the subsequent address contained in a received data package cannot be decrypted by means of a cryptographic key currently available to the subscriber system”. Examiner suggest rewriting the claim limitation as, ”….a subscription of the subscriber channel for automatic receiving the electronic data stream by the subscriber system, is terminated automatically when the subsequent address contained in a received data package cannot be decrypted by means of a cryptographic key currently available to the subscriber system”.
Claim 12 is objected to because of the following reason:
Claim 12 recites limitations having “and/or” which creates an ambiguity for the limitations. Examiner suggest removing either “and” and keeping only “or” alternatively removing “or” and keeping only “and”.
Claim 21 is objected to because of the following reason:
Claim 21 recites a limitation, “A sensor network, comprising
A data generation device or several data generation devices realized as (a) sensor device/s with one or several sensor/s generating sensor data as an electronic data stream,…..”. Examiner suggest rewriting the limitation as follows
“A sensor network, comprising:
a data generation device or several data generation devices realized as (a) sensor device(s) with one or several sensor(s) generating sensor data as an electronic data stream,…..”. OR rewriting the limitation as follow
“A sensor network, comprising:
a data generation device or multiple data generation devices, each realized as (a) sensor device with one or more sensors generating sensor data as an electronic data stream..”.
Claim 22 is objected to because of the following reason:
Claim 22 recites a limitation, “…with an access-control system which is configured to make a subscriber channel publicly available for direct obtainment of the sensor data from the sensor/s, and with at least one subscriber system which is registered with the subscriber channel and obtains the sensor data directly from the sensor/s”. Examiner suggest rewriting the limitation as follow.
“with an access-control system which is configured to make a subscriber channel publicly available for direct obtainment of the sensor data from the sensor(s), and with at least one subscriber system which is registered with the subscriber channel and obtains the sensor data directly from the sensor(s)”.
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “with an access-control system which is configured to make a subscriber channel publicly available for direct obtainment of the sensor data from the sensor/s…” in claim 22.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claim limitation “with an access-control system which is configured to make a subscriber channel publicly available for direct obtainment of the sensor data from the sensor/s…”, invokes 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. However, the written description fails to disclose the corresponding structure, material, or acts for performing the entire claimed function and to clearly link the structure, material, or acts to the function. An access control system is interpreted as access control system 48 as shown in Figure 1. The written description in specification, “The access-control system 48 is realized as an app. via the access-control system 48”. (Page-16, Lines (21-22)), indicates that the access control system is a software and lacks a physical structure. Therefore, the claim is indefinite and is rejected under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph.
Applicant may:
(a) Amend the claim so that the claim limitation will no longer be interpreted as a limitation under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph;
(b) Amend the written description of the specification such that it expressly recites what structure, material, or acts perform the entire claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(c) Amend the written description of the specification such that it clearly links the structure, material, or acts disclosed therein to the function recited in the claim, without introducing any new matter (35 U.S.C. 132(a)).
If applicant is of the opinion that the written description of the specification already implicitly or inherently discloses the corresponding structure, material, or acts and clearly links them to the function so that one of ordinary skill in the art would recognize what structure, material, or acts perform the claimed function, applicant should clarify the record by either:
(a) Amending the written description of the specification such that it expressly recites the corresponding structure, material, or acts for performing the claimed function and clearly links or associates the structure, material, or acts to the claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(b) Stating on the record what the corresponding structure, material, or acts, which are implicitly or inherently set forth in the written description of the specification, perform the claimed function. For more information, see 37 CFR 1.75(d) and MPEP §§ 608.01(o) and 2181.
Allowable Subject Matter
Claims 1, 7-15, 17-19 and 21-22 are objected to as being allowable if the objections of Claims 1, 12, 21-22 and 35 U.S.C. 112(b) rejection of claim 22 is overcome. The following is an examiner’s statement of reason for allowance.
The cited reference Wang et al. (US PGPUB. # US 2020/0356082) discloses, when a data contributor such as a process plant generates measurement data, an encrypted version of a set of measurement data is transmitted to a storage center for secure storage of the measurement data. In some instances, the data contributor divides the set of measurement data into several subsets and transmits each subset of encrypted measurement data to a different storage center. Furthermore, the storage center generates a transaction for the storage operation which is recorded in a distributed ledger. When a data subscriber retrieves the encrypted measurement data from a storage center, the data subscriber can verify the authenticity of the data based on the information recorded in the distributed ledger. (Abstract). The security architecture 200 provides end-to-end security from the field environment of the process plant 10 in which devices 202 are installed and operate, to the remote system providing applications and/or services 208 that consume and operate on the data generated by the process plant 10. As such, data that is generated by the devices 202 and other components of the process plant 10 is able to be securely transported to the remote system including the storage centers 210 for use by the remote applications/services 208 while protecting the plant 10 from cyber attacks, intrusions, and/or other malicious events. In particular, the security architecture 200 includes a field gateway 212, and an edge gateway 218 disposed between the process plant 10 (e.g., between the wireless gateways 205A, 205B of the process plant 10) and the storage centers 210. (Fig. 2, ¶59). Data or packets generated by the devices 202 may be secured for transit 204A, 204B to the wireless gateways 205A, 205B using a first security mechanism, and subsequently secured for transit 225 from the wireless gateways 205A, 205B to the field gateway 212 using a second security mechanism, and still subsequently secured for transit to the edge gateway 218 using a third security mechanism. Additionally or alternatively, and as depicted in FIG. 2, the edge gateway 218 may be protected by a firewall 228. (¶63). FIG. 2 depicts wireless gateways 205A, 205B as communicatively connecting the devices or data sources 202 to the field gateway 212, in some arrangements one or more of the wireless gateways 205A, 205B are omitted and source data is transmitted from the data sources 202 directly to the field gateway 212. For example, the data sources 202 may transmit source data directly to the field gateway 212 via a big data network of the process plant 10. Generally speaking, a big data network of the process plant 10 is not the backbone plant network 105, nor is the big data network an industrial protocol network used to transmit control signals between devices using an industrial communication protocol (e.g., Profibus, DeviceNet, Foundation Fieldbus, ControlNet, Modbus, HART, etc.). Rather, a big data network of the process plant 10 may be an overlay network implemented for the process plant 10 that streams data between nodes for data processing and analytics purposes, for example. The nodes of a big data network may include, for example, the data sources 202, the wireless gateways 205A, 205B, and the field gateway 212, as well as any one or more of the components 7a-7c, 8, 11, 12, 15-22, 26, 28, 35, 40-46, 52, 55, 58, 60, and 70 shown in FIG. 1 and other components. Accordingly, for many nodes of a process plant data network include, respectively, a designated interface for process plant operations that typically utilizes an industrial communication protocol, and another designated interface for data processing/analytics operations that may utilize a streaming protocol, for instance. (¶67). FIG. 7 depicts example encryption and division techniques performed by a data contributor, such as a process plant 10 on a set of measurement data. The data contributor 10 generates sets of measurement data 702 including a first data set 704 (DS1), a second data set 706 (DS2), a third data set 708 (DS3), and an nth data set 710 (DSn). The data contributor 10 divides each data set 704-710 into several subsets. For example, the data contributor 10 divides the first data set 704 into a first subset 704a (ED11), a second subset 704b (ED12), a third subset 704c (ED13), and an nth subset 704n (ED1n). The data contributor 10 also encrypts each subset of measurement data using a different secret key 720-726 (SK1, SK2, SK3, SKn). In some implementations, the secret keys are one-time cryptographic keys used once to encrypt the corresponding subset of measurement data. Then when a data subscriber requests at least some of the measurement data that includes a particular subset, the data contributor 10 provides the one-time cryptographic key used to encrypt the particular subset to the data subscriber for decrypting the particular subset. That one-time cryptographic key may not be used to decrypt any other subset or set of measurement data. (Fig. 6, Fig. 7, ¶87). FIG. 11 illustrates this process is more detail in a messaging diagram 1100 illustrating an example interaction between the data contributor 10, a storage center 210, and a data subscriber 1000. A data contributor 10 such as a process plant obtains 1102 measurement data, for example from field devices 202 or process plant entities operating in the process plant 10. The measurement data may include process parameter values for process parameters corresponding to the process plant entities. The measurement data may also include product parameter values such as properties of a physical material or product produced by the process plant, including a temperature of the product, a volume of the product, a mass of the product, a density of the product, a pressure of the product, etc. Then the data contributor 10 encrypts 1104 the measurement data using a cryptographic key. In some implementations, the data contributor 10 generates a set of measurement data including several measurements collected at the same time or within a time interval (e.g., within a 30 second time interval, within a one minute time interval, etc.). The data contributor 10 then divides the set of measurement data into several subsets. For example, the set of measurement data may include 100 measurements and corresponding information regarding the measurements, such as the time of the measurement, the process parameter, process plant entity, and/or field device corresponding to the measurement, etc. The data contributor 10 may divide the 100 measurements into four subsets of measurement data each including 25 out of the 100 measurements. Then the data contributor 10 may encrypt each subset of measurement data using a different cryptographic key or a unique, one-time cryptographic key. (Fig. 11, ¶96). FIG. 3 depicts an exemplary distributed ledger system 300 for recording storage operations related to encrypted measurement data. The encrypted measurement data may include process parameter data, product parameter data, configuration data, user interaction data, maintenance data, commissioning data, plant network data, product tracking data, event data related to events in the process plant 10 such as alarms, leaks, failures, errors, etc., or any other suitable data generated in or related to one or several process plants. The encrypted measurement data may also include data generated by hospitals, or any other suitable data contributors. (Fig. 3, ¶70). The encrypted subsets of measurement data are then stored at different storage centers 210. This is depicted in FIG. 8 which illustrates several storage centers 210a-210j, including SC00001 (ref no. 210a), SC00010 (ref. no. 210b), SC10000 (ref no. 210c), SC01101 (ref. no. 210d), SCO1001 (ref. no. 210e), SC00101 (ref no. 210f), SC01011 (ref no. 210g), SC01010 (ref no. 210h), SC10101 (ref. no. 210i), and SC01110 (ref. no. 210j). A first subset of an ith set of encrypted measurement data 802 (EDi1) is stored in SCO1001 (ref. no. 210e), a second subset of the ith set of encrypted measurement data 804 (EDi2) is stored in SC10000 (ref. no. 210c), a third subset of the ith set of encrypted measurement data 806 (EDi3) is stored in SC00010 (ref no. 210b), and an nth subset of the ith set of encrypted measurement data 808 (EDin) is stored in SC10101 (ref no. 210i). (Fig. 8, ¶88). At block 1202, measurement data related to a process control element is obtained from a field device. The process control element may be a field device, a controller, or a process plant entity such as a valve, a tank, a mixer, a pump, a heat exchanger, etc. The measurement data may include process parameter data for parameters of the process control element (e.g., a tank fill level, a pump speed, the temperature in a heat exchanger), and product parameter data for a product entering, exiting, within, and/or controlled by the process control element (e.g., the temperature of a fluid in a tank, the flow rate of fluid exiting a valve). In some implementations, the edge gateway 218 obtains a set of measurement data including several measurements collected at the same time or within a time interval (e.g., within a 30 second time interval, within a one minute time interval, etc.). The edge gateway 218 then divides the set of measurement data into several subsets. Then at block 1204, the measurement data is encrypted. For example, the edge gateway 218 may encrypt each subset of measurement data using a different cryptographic key or a unique, one-time cryptographic key. At block 1206, the set of encrypted measurement data is transmitted to a storage center 210. In some implementations, each subset of encrypted measurement data is transmitted to a different storage center 210 or at least two of the subsets are transmitted to different storage centers 210. In response to receiving the set of encrypted measurement data, the storage center 210 stores the set and generates a transaction representing the storage operation. The storage center 210 broadcasts the transaction to a distributed ledger network to be included in a distributed ledger. Then at block 1208, the edge gateway 218 receives the block information from the storage center, such as a transaction ID for the transaction or any other suitable information identifying the transaction in the distributed ledger. (Fig. 12, ¶103-¶104). In response to the request, the data contributor 10 provides the data subscriber 1000 with block information or transaction data for the transactions in the distributed ledger that reference the subsets of encrypted measurement data within the set. This may include transaction IDs which may be used to retrieve the corresponding transactions from the distributed ledger. For each transaction, the data subscriber 1000 may obtain a data contributor ID for the data contributor that generated the set or subset of encrypted measurement data (e.g., “DC”), a data set ID identifying the particular set or subset of encrypted measurement data (e.g., “EDi1”), a storage center ID identifying the storage center that stores the set or subset of encrypted measurement data (e.g., “SCO1001”), and an indication of the set or subset of encrypted measurement data such as a cryptographic hash value corresponding to the set or subset of encrypted measurement data. The data contributor 10 also provides the data subscriber 1000 with one-time cryptographic keys or one-time pads for decrypting each subset of encrypted measurement data. As mentioned above, the data contributor 10 may encrypt each subset of encrypted measurement data using a one-time cryptographic key unique to the subset. Accordingly, the data contributor 10 provides these one-time cryptographic keys to the data subscriber 1000, so that the data subscriber 1000 may decrypt each subset of encrypted measurement data and combine the subsets of measurement data to generate the set of measurement data. In some implementations, the data subscriber 1000 obtains each of the transactions IDs from the data contributor 10 that reference subsets of encrypted measurement data within the set, and retrieves the corresponding transactions from the distributed ledger. For each retrieved transaction, the data subscriber 1000 obtains the identity of the storage center that stores the subset of encrypted measurement data based on the storage center ID. The data subscriber 1000 then transmits a request to the identified storage center 210 for the subset of encrypted measurement data corresponding to the data set ID. Accordingly, the storage center 210 retrieves the subset of encrypted measurement data corresponding to the data set ID and provides it to the data subscriber 1000. Furthermore, the data subscriber 1000 compares the subset of encrypted measurement data to the cryptographic hash value corresponding to the subset of encrypted measurement data included in the transaction. For example, the data subscriber 1000 may perform a cryptographic hashing algorithm on the subset of encrypted measurement data and determine whether the resulting output is the same as the cryptographic hash value included in the transaction. If the resulting output is the same as the cryptographic hash value, the data subscriber 1000 may determine that the subset of encrypted measurement data has not been tampered with and may verify its authenticity. On the other hand, if the resulting output is different from the cryptographic hash value, the data subscriber 1000 may determine that the subset of encrypted measurement data has been tampered with and may not use the measurement data in its analysis or proceed any further with the measurement data. If the resulting output is the same as the cryptographic hash value, the data subscriber 1000 decrypts the subset of encrypted measurement data using the decryption information provided by the data contributor 10, such as the one-time cryptographic key. The data subscriber 1000 may repeat this process for each subset of encrypted measurement data to generate the subsets of measurement data and may combine the subsets to generate the set of measurement data. (¶91-¶95).
The reference by Kwon et al. (US PGPUB. # US 2011/0208829) discloses, a method for transmitting and receiving data are provided. In the method of receiving data, at least one of a plurality of media data generated by encoding content to have different qualities is received, the plurality of media data each including at least one segment; location information indicating a randomly accessible point of each of the at least one segment is obtained; and random accessing is provided on the received media data, based on the location information. (Abstract). The location information may include first offset information representing a location of a randomly accessible subsequent packet included in the at least one segment corresponding to the location information. (¶10). FIG. 1 is a diagram of a streaming system 100 according to an exemplary embodiment. Referring to FIG. 1, the streaming system 100 according to the exemplary embodiment includes an encoding device 110, a server 120, and a client 130. The encoding device 110 generates a plurality of media data about one input content by encoding the input content to have a plurality of different qualities. A streaming environment may change when the server 120 streams media data to the client 130. For example, a bandwidth of a network 140 for streaming may be changed, or a hardware source that may be used by the server 120 to transmit media data or by the client 130 to receive media data may be changed. (Fig. 1, ¶73-¶74). The client 130 receives at least one of the information about content and information about each media data, and requests the server 120 for at least one of the plurality of media data, based on the received at least one of the information about content and information about each media data. The client 130 estimates a streaming environment, and selects at least one of the plurality of media data based on the estimated streaming environment. The at least one media data that may maintain a suitable quality of service (QoS) in the estimated streaming environment may be selected. Then, the client 130 may transmit a hypertext transfer protocol (HTTP) request for requesting the server 120 to transmit the selected at least one media data. (¶77). om among the three types of location information, a first type of location information includes first offset information indicating a location of a subsequent packet that is randomly accessible in a corresponding segment. The first type of location information may be included in a predetermined location that is randomly accessible in each packet. (¶188). In the case of the first type of location information, the obtaining unit 1420 accesses a particular packet, e.g., a first packet, in the segment. The obtaining unit 1420 obtains a location of a subsequent packet that is randomly accessible, based on a predetermined location in the accessed packet, e.g., a `private_data_bytes` field. The obtaining unit 1420 may sequentially access packets that are randomly accessible so as to obtain the location of a subsequent random access point. (Fig. 14, ¶199). FIG. 15A is a table illustrating a first type of location information 1510 according to an exemplary embodiment. Referring to FIG. 15A, a `data_field_tag` field 1511 represents the type of the first type of the location information 1510. In the exemplary embodiment, it is assumed that location information corresponds to the first offset information indicating a subsequent random access point, the second offset information indicating all of random access points, or the third offset information indicating locations of all of access units. A `data_field_length` field 1512 represents field length. An `offset` field 1513 is a 16-bit field, and represents the total number of packets present between a current packet and a subsequent packet that is randomly accessible. Referring to FIG. 15A, although the total number of packets is defined in the `offset` field 1513, any other value, e.g., a total of bytes, a PTS, a DTS, global time of media, or a frame number, may be defined as long as it may represent a subsequent random access point. Global time may represent a position of a subsequent packet that is randomly accessible using hour, minute and seconds. (Fig. 15A, ¶204-¶206).
The reference by Matias Klein (US PGPUB. # US 2018/0211115) discloses, the system further comprises one or more monitoring service provider (MSP) that can subscribe to a sensor and/or video data to provide, without limitation, physical security services, backup services, and/or so forth, to the area within the property perimeter for a defined period of time, or the subscription period. The MSP can be selected by an end user and credentialed (e.g., by a credentialing entity, the SOC, and/or so forth) during an onboarding process to allow for connection with the cloud services, which can securely transmit video streams and sensor data associated with the area to authorized MSP. During the subscription period, the MSP can receive live video and sensor stream correlating to the property that it is monitoring from the cloud services, wherein the cloud services can be configured to consolidate sensor data and video feed received from respective SOCs. In various embodiments, each stream is available for a set time limit via a public key infrastructure (PKI), which may be implemented using blockchain technology. In this regard, the data that is streamed is encrypted and can only be decrypted via a private key available to the MSP, wherein the key can expire when the subscription period is terminated. (¶9). At block 610, the cloud services can transmit encrypted video stream, sensor stream, and/or sensor fusion subscription to the credentialed MSPs. At decision block 612, the cloud services can determine whether subscription period is expired (¶62).
However none of the cited prior art teaches the limitation, “automatic obtaining of the electronic data stream by the subscriber system, utilizing a subscription of the subscriber channel, is terminated automatically when the subsequent address contained in a received data package cannot be decrypted by means of a cryptographic key currently available to the subscriber system”.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Refer to PTO-892, Notice of References Cited for a listing of analogous art.
Jetzfelllner (US PGPUB. # US 2022/0070006) discloses, an ecosystem of devices that autonomously interact with one another by a blockchain is provided, to create a security-protected data processing of sensor data or measurement data for an object by a blockchain infrastructure. Fields of application include supply-chain scenarios or industrial control applications of blockchains.
Callan et al. (US PGPUB. # US 2019/0334700) discloses, a data management blockchain and protocol for controlling access to data, in which no central trusted authority is required, is presented. The data management blockchain and protocol comprises an initial announcement of public keys by a plurality of blockchain participants, through which each blockchain participant establishes an identity. Subsequently a first of the plurality of blockchain participants publishes data encrypted with a cryptographic key on the blockchain. A second of the plurality of blockchain participants is assigned as an owner of the data by an authority. Access to the data is granted or revoked to further participants by the second of the plurality of blockchain participants through signed permission messages published on the blockchain, and a corresponding hand-over of the cryptographic key by the first of the plurality of blockchain participants, allowing access to the data. Access to further data may be revoked by changing the cryptographic key used.
Scriber et al. (US PGPUB. # US 2019/0236286) discloses, a system for securely storing privacy information is provided. The system includes a plurality of nodes configured to maintain a distributed database containing consumer privacy information having a plurality of entries. Each entry of the plurality of entries in the distributed database is (i) encrypted with a unique encryption key associated with a consumer and the distributed database, and (ii) indexed based on a public encryption key associated with the consumer. A most recent entry associated with the consumer includes current personal information about the consumer. A first entry associated with the consumer includes an encrypted version of the unique encryption key.
Cardodo (US PGPUB. # US 2019/0261161) discloses, methods for supporting a network of mobile nodes. As a non-limiting example, various aspects of this disclosure provide communication network architectures, systems, and methods for supporting a dynamically configurable communication network comprising a complex array of both static and moving communication nodes (e.g., the Internet of moving things), where the network may involve autonomous and/or non-autonomous vehicles.
Tran et al. (US PGPUB. # US 2020/0364456) discloses, a drone with vehicular control system/sensors that can share data with other vehicles and that can communicate with the cloud to provide intelligent handling of the irrigation system. The drone can be used to dispense soil additives and to inspect plants/trees on the farm.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to DARSHAN I DHRUV whose telephone number is (571)272-4316. The examiner can normally be reached M-F 9:00 AM-5:00 PM.
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, Yin-Chen Shaw can be reached on 571-272-8878. 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.
/DARSHAN I DHRUV/ Primary Examiner, Art Unit 2498