Difference between revisions of "uaCap:Transport Intro"

From UaCapabilities
Jump to: navigation, search
(Created page with "OPC UA is a set of layered specifications broken into multiple parts. The Base and Functional Parts are described in abstract terms. The implementation parts define the mappin...")
 
Line 1: Line 1:
OPC UA is a set of layered specifications broken into multiple parts. The Base and Functional Parts are described in abstract terms. The implementation parts define the mapping to existing protocol and security technologies on which software can be built.
+
OPC UA is a set of layered specifications broken into multiple parts. The base and functional parts of OPC UA are described in abstract terms. A separate implementation part defines the mapping to existing protocol and security technologies on which interoperable software can be built.
 
[[File:UA fw Transport.JPG|300px|left]]
 
[[File:UA fw Transport.JPG|300px|left]]
This layering is purposely intended to isolate the architectural framework from the inevitable changes in the technology used to implement it. So as new technologies arrive, OPC UA will be able to advance with them. It will be possible to add new over-the-wire Protocols, and to add new Security and Encryption technologies without changing the functional elements of OPC UA.
+
This layering is purposely intended to isolate the architectural framework from the inevitable changes in the technology used to implement it. So as new technologies arrive, OPC UA will be able to advance with them. It will be possible to add new over-the-wire protocols, and to add new security and encryption technologies without changing the functional elements of OPC UA.
OPC UA is applied to different application domains with different requirements. Therefore it supports multiple mappings for different protocols and encodings.
+
To support different application domains with different requirements, OPC UA also allows multiple mappings for different protocols and encodings.
The mappings consist of three functional layers: Data Encodings, Security Protocols and Transport Protocols. Different mappings are combined together to create Transport Capabilities.
+
<br>
 +
Each mapping consists of three functional layers: Data Encoding, Security Protocol and Transport Protocol. Different mappings are combined together to create Transport Capabilities.
 
<br>
 
<br>
 
Note - Transport Mappings are specified in OPC UA Part 6
 
Note - Transport Mappings are specified in OPC UA Part 6

Revision as of 10:53, 5 February 2015

OPC UA is a set of layered specifications broken into multiple parts. The base and functional parts of OPC UA are described in abstract terms. A separate implementation part defines the mapping to existing protocol and security technologies on which interoperable software can be built.

UA fw Transport.JPG

This layering is purposely intended to isolate the architectural framework from the inevitable changes in the technology used to implement it. So as new technologies arrive, OPC UA will be able to advance with them. It will be possible to add new over-the-wire protocols, and to add new security and encryption technologies without changing the functional elements of OPC UA. To support different application domains with different requirements, OPC UA also allows multiple mappings for different protocols and encodings.
Each mapping consists of three functional layers: Data Encoding, Security Protocol and Transport Protocol. Different mappings are combined together to create Transport Capabilities.
Note - Transport Mappings are specified in OPC UA Part 6