# US 2020/0396276 A1 · Distributed historization system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0396276 A1
- Document ID: US20200396276A1
- Status: Published application
- Kind: A1
- Application number: 16/785,733
- Filed: 2020-02-10
- Published: 2020-12-17
- Earliest claimed: 2014-05-05
- Assignees: Aveva Software, LLC
- Applicants: AVEVA Software, LLC
- Inventors: Shiewun Lie; Vinay T. Kamath; Ryan Benedict Saldanha; Abhijit Manushree
- Web page: https://patentgrep.com/patent/US20200396276A1

## CPC

- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system for historizing process control data. A configurator module registers a data source device with a historian server and indicates to the historian server to generate data source registration information for identifying the registered data source device. The historian server generates and stores the data source registration information. The historian server also generates a connection token comprising the data source registration information. The configurator module forwards the connection token to the data source device, which stores the token and sends it to the historian server with data. The historian server compares the connection token received from the data source device to the connection token stored by the historian server, wherein if they match, the historian server stores the data from data source device.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A system for providing access to a historian comprising:
a historian server;
a non-transitory computer readable medium comprising instructions that when executed by a processor implement:
a configuration module;
wherein the configuration module is configured and arranged to:
communicate with the historian server and a publisher of a client providing uploaded data to the historian server;
accept a data source registration request from the publisher to register the client as a registered data source;
generate a data source ID and a data source secret when the data source registration is requested;
store the data source ID and the data secret as a historian data source ID and a historian data source secret;
send the data source ID and the data source secret to the publisher as a client data source ID and a client data source secret;
receive the client data source ID and the client data source secret from the registered data source;
receive a request for a data source upload comprising the uploaded data from the registered data source;
compare the client data source ID and the client data source secret to the historian data source ID and the historian data source secret, respectively, to check if they are a valid match;
store the uploaded data on the historian server if the match is valid; and
reject the uploaded data if the match is not valid;
wherein the data source ID and data source secret uniquely identifies the registered data source; and
wherein the configurator module is configured and arranged to allow automatic uploading from the registered data source to the historian regardless of whether a user is connected to the registered data source.

### Claim 22 (depends on 21)

The system of claim 21,
wherein the client data source ID and the client data source secret are received together with the uploaded data for each data source upload request from the registered data source.

### Claim 23 (depends on 22)

The system of claim 22,
wherein the configurator module is configured and arranged to accept user information from the registered data source, the user information comprising user credentials.

### Claim 24 (depends on 23)

The system of claim 23,
wherein the configurator module is configured and arranged to accept the data source upload from the registered data source even when there are no user credentials to check.

### Claim 25 (depends on 24)

The system of claim 24,
wherein one or more users registering and/or using the registered data source do not have access to the data source ID or data source secret.

### Claim 26 (depends on 25)

The system of claim 25,
further comprising the registered data source;
wherein the data source ID and data source secret are encrypted; and
wherein the one or more users cannot copy the data source ID and data secret from the registered device to another client.

### Claim 27 (depends on 26)

The system of claim 26,
wherein the registered data source is configured and arranged to block one or more users and/or applications from accessing the data source ID and data secret.

### Claim 28

A system for providing access to a historian comprising:
a historian server;
a non-transitory computer readable medium comprising instructions that when executed by a processor implement:
a configuration module;
wherein the configuration module is configured and arranged to:
communicate with the historian server and a client providing uploaded data to the historian server;
accept a data source registration request from the client to register the client as a registered data source;
generate a data source ID and a data source secret when the data source registration is requested;
store the data source ID and the data secret as a historian data source ID and a historian data source secret;
send the data source ID and the data source secret to the registered data source as a client data source ID and a client data source secret;
receive the client data source ID and the client data source secret from the registered data source;
receive a request for a data source upload comprising the uploaded data from the registered data source;
compare the client data source ID and the client data source secret to the historian data source ID and the historian data source secret, respectively, to check if they are a valid match;
store the uploaded data on the historian server if the match is valid; and
reject the data source upload request if the match is not valid;
wherein the configurator module is configured and arranged to accept user information from the registered data source, the user information comprising user credentials; and
wherein the configurator module is configured and arranged to accept the data source upload from the registered data source even when there are no user credentials to check.

### Claim 29 (depends on 28)

The system of claim 28,
wherein one or more users registering and/or using the registered data source do not have access to the data source ID or data source secret.

### Claim 30 (depends on 29)

The system of claim 29,
wherein the one or more users and/or applications are blocked from accessing the data source ID and data secret.

### Claim 31 (depends on 28)

The system of claim 28,
wherein the client data source ID and the client data source secret are received together with the uploaded data for each data source upload request from the registered data source.

### Claim 32 (depends on 31)

The system of claim 31,
wherein one or more users registering and/or using the registered data source do not have access to the data source ID or data source secret.

### Claim 33 (depends on 32)

The system of claim 32,
wherein the one or more users and/or applications are blocked from accessing the data source ID and data secret.

### Claim 34 (depends on 33)

The system of claim 33,
further comprising the registered data source;
wherein the client data source ID and client data source secret are encrypted; and
wherein the one or more users cannot copy the client data source ID and/or the client data secret from the registered device to another client.

### Claim 35 (depends on 34)

The system of claim 34,
wherein the registered data source is configured and arranged to block the one or more users and/or the one or more applications from accessing the data source ID and data secret.

### Claim 36

A system for providing access to a historian comprising:
a historian server;
a non-transitory computer readable medium comprising instructions that when executed by a processor implement:
a configuration module;
wherein the configuration module is configured and arranged to:
communicate with the historian server and a client providing uploaded data to the historian server;
accept a data source registration request from a user to register the client as a registered data source;
generate a data source ID and a data source secret when the data source registration is requested;
store the data source ID and the data secret in a historian token on the historian server;
send the data source ID and the data secret in a client token to the registered data source for storage on the registered data source;
receive the client token from the registered data source;
receive a request for a data source upload from the registered data source;
compare the historian token to the client token to check if they are a valid match;
store the uploaded data on the historian server if the match is valid; and
reject the data source upload if the match is not valid;
wherein the data source ID and data source secret are received together with data for each data source upload request from the registered data source; and
wherein one or more users registering or using the registered data source do not have access to the data source ID or data source secret.

### Claim 37 (depends on 36)

The system of claim 36,
wherein the configurator module is configured and arranged to accept user information from the registered data source, the user information comprising user credentials.

### Claim 38 (depends on 37)

The system of claim 37,
wherein the configurator module is configured and arranged to automatically accept the data source upload from the registered data source even when there are no user credentials to check.

### Claim 39 (depends on 38)

The system of claim 38,
further comprising the registered data source;
wherein the client data source ID and client data source secret are encrypted when stored on the registered data source; and
wherein the user or a different user cannot copy the data source ID and data secret from the registered device to another client.

### Claim 40 (depends on 39)

The system of claim 39,
wherein the registered data source is configured and arranged to block the one or more users and/or one or more applications from accessing the data source ID and data secret.
