AlexandrKonoval

Hello!

You don't need GPRS Terminal IP. You need some web resourses on your server so sensors would send data to the server.

Does this mean you have never used this method but if you were specifically asked to, then this would be a proposal?

 

Yes. That is clearer. You have a (XML?) protocol that contains security tokens.

yes. but not XML. I use JSON, its really comfortable in LabVIEW. And as bonus - other people can make their own applications to connect to the server (for Android or iOS as example)

When you talk of "Package" are you talking about software updates to the cRIO?

I have to tell i don't work with cRIO or other NI hardware.

As i think, cRIO is the controller which is controlling the other hardware and gathering some measurement data? So package is the result of it work - measurements, common system status or other.

I'll try to explain my architecture. There is the server, the remote devices and the clients of the server.

The remote devices are send the result of their work to the server with POST method.

The remote devices sends the 'sync' request to the server to get any new data from it (commands, etc) with GET method.

The clients get the data from the server using GET method.

The clients send the commands to the server using POST method

Example:

System controlls the doors in the office building.

There are controllers on the doors.

Controllers send the door status (open, closed, broken lock) to the server

Controllers asks the server for commands (lock the door, open the door) - 'sync'

Clients could get the status of all the doors from server

Clients could send the request to open or close some door to the server.

Server forwards this command to the relevant controller with the answer to its 'sync' GET request.

I hope you understand what I have written here and my efforts will not pass in vain

My english isn't good, but I'll try

except the general tricks with Windows, firewalls etÑ:

1. Close all port for input connections.

2. Your remoted PC or cRio is the client. He only sends the requests to the server via HTTPs.

3. In my package I use the sign variable which is the package encoded with the AES encryption. There is static key and variable key. The variable key is the units ID. The not-encoded ID also presents in the package.

for example:

<package>

<ID>123</ID>

<data>anydata</data>

<sign>asdjf;lkasjdf;lkas</sign>

</package>

sign = encrypt(package-sign)

4. So first of all the server check is there such unit ID in the database. If it is - we check the sign from the package. And only if everything is OK - parsing the package.

5. In one of my projects I also use my own SSL sertificates.

I recomend you to look at the TeamViewer or the SW with the same functionality.

Also, there are a lot of app-in-cloud services, so you can rent the server, install your LabVIEW and then use it from any device.

The last thing is theoretically. Didn`t try to do this.