Distributed historization system

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.

What is claimed is: 
     
         1 . A system comprising:
 a data source device comprising a registration processor and a corresponding memory device coupled thereto storing processor-executable instructions that, when executed by the registration processor, implement a configurator module for:
 connecting the data source device to a historian server; 
 registering the data source device with the historian server; 
 indicating to the historian server to generate data source registration information for identifying the registered data source device; 
 receiving a connection token from the historian server; 
 saving the connection token; and 
 forwarding the connection token to the data source device; and 
   a historian server comprising a corresponding memory device coupled thereto storing processor-executable instructions that, when executed by the historian server, implement a historian module for:
 receiving the connection from the configurator module; 
 registering the data source device as indicated by the configurator module; 
 generating data source registration information for identifying the registered data source as indicated by the configurator module; 
 storing the data source registration information; 
 generating the connection token comprising the data source registration information; and 
 sending the connection token to the configurator module; 
   wherein, in response to receiving the connection token from the configurator module, the data source device stores the connection token and sends data and the connection token to the historian server; and   wherein the historian server compares the connection token received from the data source device to the connection token stored by the historian server and stores the data from data source device when the connection token received from the data source device and the connection token stored by the historian server match.   
     
     
         2 . The system of  claim 1 , wherein the data source registration information comprises a data source ID and a data source secret. 
     
     
         3 . The system of  claim 1 , wherein the connection token comprises data source registration information and connection information for accessing the historian server. 
     
     
         4 . The system of  claim 1 , wherein the data source device stores the data source registration information in an encrypted form. 
     
     
         5 . The system of  claim 1 , wherein the sending of data by the data source device to the historian server is initiated by a user of the data source device, the user having logged in to the data source device through a user authentication process. 
     
     
         6 . The system of  claim 1 , wherein the sending of data by the data source device to the historian server is initiated by an automatic process when no user is signed into the data source device. 
     
     
         7 . The system of  claim 1 , further comprising a plurality of data source devices registered with the historian server, each of the plurality of data source devices storing a connection token comprising data source registration information unique to the data source device on which the connection token is stored. 
     
     
         8 . The system of  claim 1 , further comprising a plurality historian servers to which the data source device is registered. 
     
     
         9 . The system of  claim 8 , wherein a first historian server of the plurality of historian servers stores data on premise and a second historian server of the plurality of historian servers stores data in the cloud. 
     
     
         10 . The system of  claim 9 , wherein the data source device connects with the first historian server and the second historian server through an access layer module, the access layer module maintaining connections to the first historian server and the second historian server. 
     
     
         11 . A method for uploading data from a data source device to a historian server comprising:
 connecting, by a configurator module, the data source device to a historian server;   registering, by the configurator module, the data source device with the historian server;   registering, by the historian server, the data source device as indicated by the configurator module;   indicating to the historian server, by the configurator module, to generate data source registration information for identifying the registered data source device;   generating, by the historian server, data source registration information for identifying the registered data source as indicated by the configurator module;   storing, by the historian server, the data source registration information;   generating, by the historian server, a connection token comprising data source registration information;   sending, by the historian server, the connection token to the configurator module;   receiving, by the configurator module, a connection token from the historian server;   saving, by the configurator module, the connection token;   forwarding, by the configurator module, the connection token to the data source device;   receiving, by the data source device, the connection token from the configurator module;   storing, by the data source device, the connection token;   sending, by the data source device, data and the connection token to the historian server; and   comparing, by the historian server, the connection token received from the data source device to the connection token stored by the historian server, wherein the historian server stores the data from data source device when the connection token received from the data source device and the connection token stored by the historian server are found to match.   
     
     
         12 . The method of  claim 11 , wherein the data source registration information comprises a data source ID and a data source secret. 
     
     
         13 . The method of  claim 11 , wherein the connection token further comprises connection information for accessing the historian server. 
     
     
         14 . The method of  claim 11 , wherein the data source device stores the data source registration information in an encrypted form. 
     
     
         15 . The method of  claim 11 , wherein the sending of data by the data source device to the historian server is initiated by a user of the data source device, the user having logged in to the data source device through a user authentication process. 
     
     
         16 . The method of  claim 11 , wherein the sending of data by the data source device to the historian server is initiated by an automatic process when no user is signed into the data source device. 
     
     
         17 . The method of  claim 11 , wherein a plurality of data source devices are registered with the historian server, each of the plurality of data source devices storing a connection token comprising data source registration information unique to the data source device on which the connection token is stored. 
     
     
         18 . The method of  claim 11 , wherein the data source device is registered with a plurality historian servers. 
     
     
         19 . The method of  claim 18 , wherein a first historian server of the plurality of historian servers stores data on premise and a second historian server of the plurality of historian servers stores data in the cloud. 
     
     
         20 . A method for uploading data from a data source device to a historian server comprising:
 connecting the data source device to a historian server;   registering the data source device with the historian server;   indicating to the historian server to generate data source registration information for identifying the registered data source device, wherein the data source registration information is stored by the historian server;   receiving a connection token from the historian server;   forwarding the connection token to the data source device, wherein data and the connection token is sent to the historian server and the data from data source device is stored by the historian server when the connection token received from the data source device and the connection token stored by the historian server are found to match.