Difference between revisions of "OPC UA File Transfer concepts"

From OPC Labs Knowledge Base
Jump to navigation Jump to search
(Created page with " {{Note|The "file transfer" in the name corresponds to how the related OPC UA specification part is titled. In reality, the functionality covers more than just file transfer...")
 
Line 1: Line 1:
 
+
The OPC UA File Transfer is a set of functionality in OPC UA, built on top of core OPC UA, which defines operation on files and directories residing in the OPC UA server that supports it, similar to file system functionality in operating systems. The OPC UA files and directories can be just a temporarily or persistent storage for arbitrary data, with no added intrinsic semantics, but in many cases they will have a specific meaning defined by the OPC server. For example, files with a predefined name and location can be used to upload a new firmware to the PLC. Files provided by the OPC UA server can also be "virtual", i.e. they do not have to be physically stored inside the server, and the file transfer mechanism can be used to facilitate access to large bodies data that would otherwise be impossible to read or write in a single call (files can be read from or written to in pieces). Some OPC UA "higher-level" specifications use the File Transfer mechanism as well. For example, files are used in Certificate Management to transfer application certificates in their binary form.
  
 
{{Note|The "file transfer" in the name corresponds to how the related OPC UA specification part is titled. In reality, the
 
{{Note|The "file transfer" in the name corresponds to how the related OPC UA specification part is titled. In reality, the
 
functionality covers more than just file transfer - it represents a file system in OPC UA, and provides file access
 
functionality covers more than just file transfer - it represents a file system in OPC UA, and provides file access
 
and manipulation operations.}}
 
and manipulation operations.}}

Revision as of 09:53, 22 May 2021

The OPC UA File Transfer is a set of functionality in OPC UA, built on top of core OPC UA, which defines operation on files and directories residing in the OPC UA server that supports it, similar to file system functionality in operating systems. The OPC UA files and directories can be just a temporarily or persistent storage for arbitrary data, with no added intrinsic semantics, but in many cases they will have a specific meaning defined by the OPC server. For example, files with a predefined name and location can be used to upload a new firmware to the PLC. Files provided by the OPC UA server can also be "virtual", i.e. they do not have to be physically stored inside the server, and the file transfer mechanism can be used to facilitate access to large bodies data that would otherwise be impossible to read or write in a single call (files can be read from or written to in pieces). Some OPC UA "higher-level" specifications use the File Transfer mechanism as well. For example, files are used in Certificate Management to transfer application certificates in their binary form.

Note2-icon.png

Note: The "file transfer" in the name corresponds to how the related OPC UA specification part is titled. In reality, the functionality covers more than just file transfer - it represents a file system in OPC UA, and provides file access and manipulation operations.