Search

128 result(s) for Message

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.18 Message
  Message data unit conveyed between Client and Server that represents a specific Service request or response
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  3.1.1.5 message
  message <information theory and communication theory> ordered sequence of characters (usually octets) intended to convey information
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.10 Communication Stack
  application and the hardware that provides various functions to encode, encrypt and format a Message for sending, and to decode, decrypt and unpack a Message that was received
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.5 Publish-Subscribe
  Applications do not directly exchange requests and responses. Instead, Publishers send messages to a Message Oriented Middleware , without knowledge of what, if any, Subscribers there may be. Similarly, Subscribers express ... process messages that contain this data, without knowledge of what Publishers there are. Message Oriented Middleware is software or hardware infrastructure supporting sending and receiving messages between distributed systems
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.3 SecureChannel Service Set
  Applications simply need to verify that a SecureChannel is active whenever it receives a Message . OPC 10000-6 describes how the SecureChannel Services are implemented with different types of communication ... encrypted according to the security policy. A UA application is expected to ignore any Message that does not conform to the security policy for the channel. A SecureChannel is separate
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.10 Subscription Service Set
  send within the keep-alive time interval, the Server sends a keep-alive Message that contains the sequence number of the next NotificationMessage sent. If a Client fails to receive ... Message after the keep-alive interval has expired, or if it determines that it has missed a Message , it can request the Server to resend one or more Messages
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.30 Message Authentication Code
  Message Authentication Code short piece of data that results from an algorithm that uses a secret key (see Symmetric Cryptography ) to hash a Message whereby the receiver of the Message ... check against alteration of the Message by computing a MAC that should be identical using the same Message and secret
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.31 Message Signature
  Message Signature Digital Signature used to ensure the Integrity of Message s that are sent between two entities Note 1 to entry: There are several ways to generate and verify ... Message Signatures however they can be categorized as symmetric (see 3.1.44 ) and asymmetric (see 3.1.6 ) approaches
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.2.2 Message flooding
  Message flooding For Client - Server , an attacker can send a large volume of Message s, or a single Message that contains a large number of requests, with the goal ... Flooding attacks can be conducted at multiple layers including OPC UA, HTTP or TCP. Message flooding attacks can also target a Client , although this is less of a risk, since
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.2.4 Application Crashes
  Application Crashes An attacker can send special message that will cause an application to crash. This is usually the result of a known problem in a stack or application. These ... alternate it could be a Server that can respond to a legitimate message with a response that would cause the Client to crash. The attacker could also be a Publisher
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.3 Eavesdropping
  network infrastructure, then the attacker could be able to record and capture Message s. It could be beyond the capability of a Client or Server to recover from a compromised
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.4 Message spoofing
  Message spoofing This includes feigning identities (user, application, process etc.). An attacker could forge Message s from a Client or a Server or a Publisher where the messages are forged ... process. Spoofing can occur at multiple layers in the protocol stack. By spoofing Message s from a Client, a Server or Publisher , attackers can perform unauthorized operations and avoid detection
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.5 Message alteration
  Message alteration Network traffic and application layer Message s could be captured or modified and forwarded to OPC UA Client s, Servers, and Subscribers . Message alteration could allow illegitimate access ... system. Message alteration impacts Integrity, Authorization, Auditability, Non-Repudiation and during session / SecureChannel establishment Authentication . See 5.1.5 for the reconciliation of this threat
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.6 Message replay
  Message replay Network traffic and valid application layer Message s could be captured and resent to OPC UA Client s, Servers and Subscribers at a later stage without modification ... property loss. An attacker could attempt to establish a Session using a recorded Session . Message replay impacts Authorization and during Session / SecureChannel establishment Authentication. See 5.1.6 for the reconciliation
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.7 Malformed Messages
  Malformed Messages An attacker can craft a variety of Message s with invalid Message structure (malformed XML, UA Binary, etc.) or data values, and send them to OPC UA Client ... Subscribers . The OPC UA Client , Server or Subscriber could incorrectly handle certain malformed Message s by performing unauthorized operations or processing unnecessary information. It could result in a denial
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.8 Server profiling
  damaging attack. The attacker could profile the target by sending valid or invalid formatted Message s to the target and try to recognize the type of target by the pattern
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.9 Session hijacking
  guessing) about a running Session established between two applications to inject manipulated Message s (with valid session information) that allow him or her to take over the Session from
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.10 Application Authentication
  Certificate and based on this check it accepts or rejects the request or response Message from the sender (see OPC 10000-4 Determining if a Certificate is Trusted). This trust
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.13 OPC UA security related Services
  used to establish a SecureChannel which is responsible for securing Message s sent between a Client and a Server . The challenge of the SecureChannel establishment is that it requires ... sends its Public Key in a Certificate and secret information with the OpenSecureChannel service Message to the Server . This Message is secured by applying Asymmetric Encryption with the Server
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.2.2 Message flooding
  Message flooding OPC UA minimizes the loss of Availability caused by Message flooding by minimizing the amount of processing done with a Message before the Message is authenticated. This prevents ... cannot be eliminated. The Server implementation could protect itself from floods of OpenSecureChannel Message s in two ways. First, the Server could intentionally delay its processing of OpenSecureChannel requests once
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.4 Message spoofing
  Message spoofing See 4.3.4 for a description of this threat. As specified in OPC 10000-4 and OPC 10000-6 , OPC UA counters Message spoofing threats by providing the ability ... sign Message s. Additionally, Message s will always contain a valid SessionId , SecureChannelId , RequestId and Timestamp as well as the correct sequence number. OPC UA when operating as part
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.5 Message alteration
  Message alteration See 4.3.5 for a description of this threat. OPC UA counters Message alteration by the signing of Message s that are specified ... Message s are altered, checking the signature will reveal any changes and allow the recipient to discard the Message . This check can also prevent unintentional Message alteration due to communication
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.6 Message replay
  Message replay See 4.3.6 for a description of this threat. OPC UA uses SessionIds , SecureChannelIds , Timestamps , sequence numbers and RequestIds for every request and response Message . Message s are signed ... cannot be changed without detection, therefore it would not be possible to replay a Message without it being detected and rejected. The establishment of a SecureChannel or Session includes
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.7 Malformed Messages
  description of this threat. Implementations of OPC UA Applications counter threats of malformed Message s by checking that Message s have the proper form and that parameters of Message ... within their legal range. Invalid Message s are discarded. This is specified
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.10 Rogue Server or Publisher
  possess the appropriate Private Key (because this will never be distributed) to decrypt Message s secured with the correct Public Key the rogue Server would never be able to read ... without the Private Key the Server would never be able to sign a response message to a Client. If communication is secured using ECC, then the Client would refuse
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.13 Repudiation
  this threat. OPC UA Client and Server applications counter Repudiation by the signing of Message s that are specified in OPC 10000-4 . A signed message within a secure channel ... indicates that the message originated from the owner of the private key. During OpenSecureChannel and Session establishment the communicating parties are clearly identified and confirmed. Lastly Auditing as described
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.5 Confidentiality
  Asymmetric Encryption is used for key agreement and Symmetric Encryption for securing all other Message s sent between OPC UA Application s. Encryption mechanisms are specified
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.6 Integrity
  agreement phase during the SecureChannel establishment. The Symmetric Signatures are applied to all other Message s including PubSub messages. OPC UA relies upon the site CSMS to protect Integrity
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.8 Availability
  Availability OPC UA minimizes the impact of Message flooding as described in 5.1.2 . Some attacks on Availability involve opening more Sessions than a Server can handle thereby causing the Server
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  6.2 Appropriate timeouts:
  timeouts: Timeouts, the time that the implementation waits (usually for an event such as Message arrival), play a very significant role in influencing the security of an implementation. Potential consequences ... idle for long periods of time, the Server keeps the Client 's buffered Message or information for that period, leading to resource exhaustion. The implementer should use reasonable timeouts
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  6.3 Strict Message processing
  Strict Message processing The specifications often specify the format of the correct Message s and are silent on what the implementation should do for Message s that deviate from ... parse such packets, leading to vulnerabilities. The implementer should do strict checking of the Message format and should either drop the packets or send an error Message as described below
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  6.5 Special and reserved packets
  Special and reserved packets The implementation understands and correctly interprets any Message types that are reserved as special (such as broadcast and multicast addresses in IP specification). Failing to understand
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.2 Request/response Service procedures
  return of responses. The procedures begin with the requesting Client submitting a Service request Message to the Server . Upon receipt of the request, the Server processes the Message ... request, it generates a separate success/failure code that it includes in a positive response Message along with any data that is to be returned. To perform these operations, both
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.6.1 Overview
  SecureChannel using HTTPS. In these cases, the OPC UA Application shall verify that the Message it received was in the context of an HTTPS connection. OPC 10000-6 describes ... requirements specified in the EndpointDescription . An OPC UA Application shall not process any Message that does not conform to these requirements. The relationship between the SecureChannel
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.6.2.1 Description
  renew a SecureChannel that can be used to ensure Confidentiality and Integrity for Message exchange during a Session . This Service requires the Communication Stack to apply the various security algorithms ... authenticate Messages . SecurityTokens also have globally-unique identifiers which are attached to each Message secured with the token. This allows an authorized receiver to know how to decrypt and verify
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.6.2.2 Parameters
  SecurityToken within the channel. This is the identifier that shall be passed with each Message secured with the SecurityToken . createdAt UtcTime The time when the SecurityToken was created. revisedLifetime Duration
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.1.1 Description
  reached, a Publish request is de-queued and used to return a keep-alive Message . This keep-alive Message informs the Client that the Subscription is still active. Each keep ... alive Message is a response to a Publish request in which the notificationMessage parameter does not contain any Notifications and that contains the sequence number of the next NotificationMessage that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.1.2 State table
  Subscription expired and there were either Notifications to be sent or a keep-alive Message to be sent. In these cases, the newly received Publish request is processed immediately ... timer expires, it is immediately reset. If there are Notifications or a keep-alive Message to be sent, it de-queues and processes a Publish request. When a Subscription processes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.1.3 State variables and parameters
  TRUE to mean that either a NotificationMessage or a keep-alive Message has been sent on the Subscription . It is a flag that is used to ensure that either ... NotificationMessage or a keep-alive Message is sent out the first time the publishing timer expires. NotificationsAvailable A boolean value that is set to TRUE only when there
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.2.2 Parameters
  times without requiring any NotificationMessage to be sent, the Subscription sends a keep-alive Message to the Client . The negotiated value for this parameter is returned in the response
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.3.2 Parameters
  times without requiring any NotificationMessage to be sent, the Subscription sends a keep-alive Message to the Client . The negotiated value for this parameter is returned in the response
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.5.1 Description
  used to request the Server to return a NotificationMessage or a keep-alive Message . Since Publish requests are not directed to a specific Subscription , they may be used ... maxNotificationsPerPublish parameter passed to the CreateSubscription Service . However, this could still result in a message that is too large for the Client or Server to process. In this situation
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.5.2 Parameters
  sequence number being acknowledged (see 7.8 for Counter definition). The Server may delete the Message with this sequence number from its retransmission queue. Response responseHeader ResponseHeader Common response parameters ... including the sequence number of this response if it is not a keep-alive Message . This list is prepared after processing the acknowledgements in the request (see 7.8 for Counter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.6.1 Description
  NotificationMessage from its retransmission queue. If the Server does not have the requested Message in its retransmission queue, it returns an error response. See 5.14.1.2 for the detail description
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.3.1 Description
  like other Services . Those parameters are already part of the body which contains the Message for the Service to invoke. Any Endpoint used for normal communication could be used
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.3 General audit Events
  AuditEventType and its sub-types are defined in OPC 10000-3 . An audit Event Message also includes the audit record Id. The details of the AuditEventType and its subtypes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.5 Auditing for SecureChannel Service Set
  assignment of the SourceNode , the SourceName and additional parameters. For the failure cases the Message for Events of this type should include a description of why the service failed. This
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.6 Auditing for Session Service Set
  assignment of the SourceNode , the SourceName and additional parameters. For the failure case the Message for Events of this type should include a description of why the Service failed
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.7 Auditing for NodeManagement Service Set
  assignment of the SourceNode , the SourceName and additional parameters. For the failure case, the Message for Events of this type should include a description of why the service failed
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.8 Auditing for Attribute Service Set
  assignment of the SourceNode , the SourceName and additional parameters. For the failure case the Message for Events of this type should include a description of why the Service failed ... detailed assignment of the SourceNode , SourceName and additional parameters. The Message for Events of this type should include a description of why the Service failed. For Clients that support auditing
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.10 Auditing for View, Query, MonitoredItem and Subscription Service Set
  assignment of the SourceNode , the SourceName and additional parameters. For the failure case, the Message for Events of this type should include a description of why the service failed
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.26 NotificationMessage
  defined in Table 164 . Table 164 - NotificationMessage Name Type Description NotificationMessage structure The Message that contains one or more Notifications . sequenceNumber Counter The sequence number of the NotificationMessage . publishTime UtcTime ... time that this Message was sent to the Client . If this Message is retransmitted to the Client , this parameter contains the time it was first transmitted to the Client . notificationData
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.2 BaseEventType
  HasProperty Variable ReceiveTime UtcTime PropertyType Mandatory HasProperty Variable LocalTime TimeZoneDataType PropertyType Optional HasProperty Variable Message LocalizedText PropertyType Mandatory HasProperty Variable Severity UInt16 PropertyType Mandatory HasProperty Variable ConditionClassId NodeId PropertyType Optional ... include DST correction and DST may or may not have been in effect. Message provides a human-readable and localizable text description of the Event . The Server may return
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.14 AuditCertificateExpiredEventType
  SourceName for Events of this type shall be "Security/Certificate". The Message Variable shall include a description of why the certificate was expired (i.e. time before start or time
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.15 AuditCertificateInvalidEventType
  SourceName for Events of this type shall be "Security/Certificate". The Message shall include a description of why the certificate is invalid. There are no additional Properties defined
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.16 AuditCertificateUntrustedEventType
  SourceName for Events of this type shall be "Security/Certificate". The Message Variable shall include a description of why the certificate is not trusted. If a trust chain
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.17 AuditCertificateRevokedEventType
  SourceName for Events of this type shall be "Security/Certificate". The Message Variable shall include a description of why the certificate is revoked (was the revocation list unavailable
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.18 AuditCertificateMismatchEventType
  SourceName for Events of this type shall be "Security/Certificate". The Message Variable shall include a description of misuse of the certificate. There are no additional Properties defined
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  4 Overview
  however, their format is specified by the DataEncoding and TransportProtocol . For this reason, each Message defined in OPC 10000-4 shall have a normative description which specifies exactly what shall
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.15 Messages
  Messages Messages are the top-level Structures exchanged between a Client and Server . A Message sent from a Client to a Server is a Request . A Message sent back ... Client from the Server is a Response . Sending the same Message multiple times (i.e. calling Read ServerState over and over) increases the attack surface. To reduce the attack surface
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.9 Messages
  prefixed by the NodeId of for the OPC UA Binary DataTypeEncoding defined for the Message . Each OPC UA Service described in OPC 10000-4 has a request and response Message
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.3.8 Messages
  Messages Messages are encoded as an xs: complexType. The parameters in each Message are serialized in the same way the fields of a Structure are serialized
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.1 Security Handshake and Security Policies
  Session Each SecurityProtocol mapping specifies exactly how to apply the security algorithms to the Message . A set of security algorithms that shall be used together during a security handshake ... algorithm to use. DerivedSignatureKeyLength The length in bits of the derived key used for Message authentication. CertificateSignatureAlgorithm The asymmetric signature algorithm used to sign certificates. CertificateKeyAlgorithm The algorithm used
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.1 Overview
  supported. All security is applied to individual MessageChunks and not the entire OPC UA Message . A Stack that implements UASC is responsible for verifying the security on each MessageChunk received ... reconstructing the original OPC UA Message . All MessageChunks will have a 4-byte sequence assigned to them. These sequence numbers are used to detect and prevent replay attacks. UASC requires
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.1 Overview
  shows the structure of a MessageChunk and how security is applied to the Message when not using AuthenticatedEncryption algorithms. For these SecurityPolicies any padding is appended to the message before ... shows the structure of a MessageChunk and how security is applied to the Message when using Authenticated Encryption algorithms. For these SecurityPolicies the Signature is calculated during encryption and appended
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.2 Message Header
  Message Header Every MessageChunk has a Message header with the fields defined in Table 57 . Table 57 - OPC UA Secure Conversation Message Header Name Data Type Description MessageType Byte ... three byte ASCII code that identifies the Message type. The following values are defined at this time: MSG A Message secured with the keys associated with a channel. OPN OpenSecureChannel
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.3 Security Header
  Security Header The Message header is followed by a security header which specifies what cryptography operations have been applied to the Message . There are two versions of the security header ... which depend on the type of security applied to the Message . The security header used for asymmetric algorithms is defined in Table 58 . Asymmetric algorithms are used to secure
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.4 Sequence Header
  Table 60 . The sequence header ensures that the first encrypted block of every Message sent over a channel will start with different data. Table 60 - Sequence header Name Data Type ... SecureChannel . RequestId UInt32 An identifier assigned by the Client to OPC UA request Message . All MessageChunks for the request and the associated response use the same identifier. A SequenceNumber shall
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.5.1 Encryption other than Authenticated Symmetric Encryption (AEAD)
  each MessageChunk has a footer with the fields defined in Table 61 . Table 61 - Message Footer with Encryption other than AEAD Name Data Type Description PaddingSize Byte The number ... byte for the PaddingSize). Padding OctetString Padding added to the end of the Message to ensure length of the data to encrypt is an integer multiple of the encryption block
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.5.2 Authenticated Encryption Algorithms (AEAD)
  each MessageChunk has a footer with the fields defined in Table 62 . Table 62 - Message Footer for Sign Mode and AEAD Encryption Name Data Type Description Signature OctetString The signature ... MessageChunk . The signature includes the headers and all Message data. The signature is encoded as sequence of Bytes with a length specified by the SecurityPolicy
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.3 MessageChunks and error handling
  error handling MessageChunks are sent as they are encoded. MessageChunks belonging to the same Message shall be sent sequentially. If an error occurs creating a MessageChunk then the sender shall ... IsFinal flag to 'A' (for Abort). Table 63 specifies the contents of the Message abort MessageChunk . Table 63 - OPC UA Secure Conversation Message abort body Name Data Type Description Error
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.4 Establishing a SecureChannel
  this by sending an OpenSecureChannel request to the Server . The Server shall validate the Message and the ClientCertificate and return an OpenSecureChannel response. Some of the parameters defined ... specified in the security header (see 6.7.2 ) instead of the body of the Message . Table 64 lists the parameters that appear in the body of the Message . Note that
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.7 Verifying Message Security
  Verifying Message Security The contents of the MessageChunk shall not be interpreted until the Message is decrypted and the signature and sequence number verified. If an error occurs during Message ... channel. If the receiver is the Server, it shall also send a transport error Message before closing the channel. Once the channel is closed the Client shall attempt
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.8.1 Secure Channel Handshake
  encoded as described in 5.2.2.2 . When not using AuthenticatedEncryption , the data changes for each Message so the InitializationVector can be calculated once with the keys and reused until the keys ... indicate there is no LastSequenceNumber for the first MessageChunk which is always the OpenSecureChannel Message. It is encoded as a UInt32 as described in 5.2.2.2. The ClientInitializationVector is used when
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.1 Overview
  Overview Figure 18 illustrates the structure of a Message placed on the wire. This also illustrates how the Message elements defined by the OPC UA Binary Encoding mapping ... relate to the OPC UA Connection Protocol Messages . Figure 18 - OPC UA Connection Protocol Message structure
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.2 Message Header
  Message Header Every OPC UA Connection Protocol Message has a header with the fields defined in Table 73 . Table 73 - OPC UA Connection Protocol Message header Name Type Description MessageType ... Byte [3] A three byte ASCII code that identifies the Message type. The following values are defined at this time: HEL a Hello Message . ACK an Acknowledge Message
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.3 Hello Message
  Hello Message The Hello Message has the additional fields shown in Table 74 . Table 74 - OPC UA Connection Protocol Hello Message Name Data Type Description ProtocolVersion UInt32 The version ... lower version it shall return the version it will use in the Acknowledge Message . The ProtocolVersion for this version of the standard is 0. ReceiveBufferSize UInt32 The largest MessageChunk that
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.4 Acknowledge Message
  Acknowledge Message The Acknowledge Message has the additional fields shown in Table 75 . Table 75 - OPC UA Connection Protocol Acknowledge Message Name Type Description ProtocolVersion UInt32 A protocol version supported ... that is less than or equal to the protocol version requested in the Hello Message . If the Client accepts the protocol version it shall ensure that it sends Messages that
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.5 Error Message
  Error Message The Error Message has the additional fields shown in Table 76 . Table 76 - OPC UA Connection Protocol Error Message Name Type Description Error UInt32 The numeric code ... socket is always closed gracefully by the Client after it receives an Error Message
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.6 ReverseHello Message
  ReverseHello Message The ReverseHello Message has the additional fields shown in Table 77 . Table 77 - OPC UA Connection Protocol ReverseHello Message Name Data Type Description ServerUri String The ApplicationUri ... Server which sent the Message . The encoded value shall be less than 4096 bytes. Client shall return a Bad_TcpEndpointUrlInvalid error and close the connection if the length exceeds
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.3 Establishing a connection
  that Clients and Servers may support. If the Client creates the TransportConnection , the first Message sent shall be a Hello which specifies the buffer sizes that the Client supports ... Server shall respond with an Acknowledge Message which completes the buffer negotiation. The negotiated buffer size shall be reported to the SecureChannel layer. The negotiated SendBufferSize specifies the size
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.5 Error handling
  protocol level error occurs that cannot be recovered, the Server shall send an Error Message to the Client and closes the TransportConnection gracefully. When the Client receives an Error Message ... fatal error, it shall report the error to the application and send a CloseSecureChannel Message . The Server shall close the TransportConnection gracefully when it receives the CloseSecureChannel Message . The possible
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.4.1 Overview
  security. This means all bytes are secured as they are sent without considering the Message boundaries. Transport security can only work for point-to-point communication and does not allow ... connect without providing a Certificate during negotiation of the HTTPS connection. HTTP 1.1 supports Message chunking where the Content-Length header in the request response is set to "chunked
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.4.3 XML Encoding
  Encoding This TransportProtocol implements the OPC UA Services using a SOAP request-response message pattern over an HTTPS connection. The body of the HTTP Messages shall be a SOAP ... Message (see SOAP Part 1 ). WS-Addressing headers are optional. The OPC UA XML Encoding specifies a way to represent an OPC UA Message as an XML element. This element
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.4.4 Binary Encoding
  HTTP response header is: HTTP/1.1 200 OK Content-Type: application/octet-stream Content-Length: nnnn The Message body is the request or response structure encoded as an ExtensionObject in OPC UA Binary
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  8.2 XML Schema and WSDL
  encoded. The data type of each field is also captured. The normative contract for Message sent via the SOAP/HTTP TransportProtocol is a WSDL that includes XML Schema
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.6.1 General
  Server to request user input. It provides functionality similar to the standard Message dialogs found in most operating systems. The model can easily be customized by providing Server specific response
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.3 Continuation Points
  ContinuationPoint . The Client specifies the maximum number of results per operation in the request Message . A Server shall not return more than this number of results but it can return
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  4.3 Decoupling by use of middleware
  sources of data, while Subscribers consume that data. Communication in PubSub is message-based. Publishers send messages to a Message Oriented Middleware , without knowledge of what, if any, Subscribers there ... process messages that contain this data, without knowledge of what Publishers there are. Message Oriented Middleware is software or hardware infrastructure that supports sending and receiving messages between distributed systems
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.13.3 PubSubCommunicationFailureEventType
  Units PubSub Model Diagnostics Events This EventType inherits all Properties of the PubSubStatusEventType . The Message Event field inherited from BaseEventType has a localized description of the error. The Error Property
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  B.3.7 Message header
  B.3.7 Message header The AMQP message header has a number of standard fields which are called properties in the AMQP specification. Table B.1 describes how these fields are populated when ... AMQP message is constructed. Table B.1 - AMQP standard header fields Field Name Source message-id A globally unique value per message. Subject Valid values are ua-data or ua-metadata
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  D.1.2 PubSub multicast messages
  extension, the Server shall be configured to be a Publisher with a fixed DataSet message sent to a multicast address. The DataSet shall consist of a single instance that ... data delta frame type messages defined in OPC 10000-14 . A data key frame message for the Publisher shall include an array with all AliasNameCatagory instances in the Server
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.5 Semantic Property Metadata in PubSub Scenarios
  PubSub is configured accordingly, the information is available for the Subscriber through a DataSetMetaData Message . Figure A.5 - Semantic Properties in the FieldMetaData
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  6.2 LogRecord EventType Mapping
  variable, or it might be as defined in BaseEventType in OPC 10000-5 . Message - shall describe the issue that is being represented in the LogRecord . Severity - in the Event system
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.2 ConnectionEndpointType definition
  have SourceName set to the BrowseName of the Connection that was closed. This LogRecord Message shall indicate that a timeout occurred. The ConnectionManagerApplicationUri can be used to identify the ConnectionManager
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.3.2 Establishing Connections
  belongs to . SourceName shall be the BrowseName of the Connection that is being created. Message shall describe the action(s) being reported (e.g. create Connection , Connection creation failed, enable Connection ... failed…). Note: the Message field in future releases will be updated to define fixed strings and mandatory fields for distinct messages. The fixed text will be provided in multiple languages
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.4 EditConnectionConfigurationSets Method
  SourceName shall be the Uri of the Client that invoked the Method . The Message shall include "ConnectionManager/EditConnection". Note:the Message field in future releases will be updated
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.5.2 ProcessConnectionConfigurationSets signature
  ClientDescription of the Client that invoked the Method (see OPC 10000-4 ApplicationDescriptionType) . The Message shall include "ConnectionManager/ProcessConnection" and the Action being invoked. Note:the Message field
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.1 Overview
  changed. The SourceName shall be the BrowseName of the Node being updated. The Message shall include the BrowseName of the ConnectionConfigurationSet that contains the Node being updated, as well ... values for the SelectionList item. Note:the Message field in future releases will be updated to define fixed strings and mandatory fields for distinct messages and will be included
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.2 ConnectionConfigurationSetType definition
  SourceName shall be the BrowseName of the Connection with the status change. The Message shall include the previous state and the new state of the Connection. Note:the Message field
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.9.2 ConnectionConfigurationSetStateMachineType definition
  SourceName shall be the BrowseName of the Transition that the HasEffect is referencing. The Message shall include both the ToState State and FromState State the Transition is associated with. Note ... Message field in future release will be updated to define fixed strings and mandatory fields for distinct messages. The fixed text will be provided in multiple languages
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.10 EstablishConnectionErrorEventType
  related to a specific Connection , then it shall be "ConnectionManager". Message describes the issue. It shall include a description of the action that was being taken, e.g. resolving
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.11 CloseConnectionErrorEventType
  belonged to . SourceName shall be the BrowseName of the Connection that was being closed. Message describes the issue. It shall include a description of the action that was being taken
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  7.4.2.1.5 Engineered time synchronisation spanning tree
  engineered sync tree may then be applied and validated, for example: Set Sync message transmission interval uniformly, e.g., default interval. Set PTP Port states according to synthesis
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.12.2 DeviceHealthDiagnosticAlarmType
  subtypes of DeviceHealthDiagnosticAlarmType become active when the device enters the corresponding abnormal state. The Message field in the Event notification shall be used for additional information associated with the health
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  12.2 IMaintenanceEventType
  maintenance activity. The description of the maintenance activity should be put into the Message field defined for the BaseEventType in OPC 10000-5 . The maintenance activity starts, when the MaintenanceState
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  7.9 AutoIdLogEntryEventType
  written . The new entry to the Logbook will be provided in the Event field Message defined by the BaseEventType
• OPC-30060 – OPC UA for Tobacco Machine Communication
  9.37.1 SetMessage Method
  SetMessage Method The Method SetMessage sets the Message that the underlying system will display for the alarm. Message is inherited from a parent type. The signature of this Method ... specified below. Table 185 specifies the Arguments representation. Signature SetMessage ( [in] 0:LocalizedText Message, [out] MethodExecutionFeedbackType ExecutionFeedback); Table 185 - SetMessage Method Arguments Argument Description Message The message that will
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.2 IOLinkEventType
  IOLinkEventType or a subtype. The content of the Properties SourceNode , SourceName , Time , ReceiveTime , and Message is defined by its subtypes. The optional Property LocalTime shall not be provided. The Property
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.3 IOLinkDeviceEventType
  Link event code is not described in an IODD, the mandatory Property Message shall be set to "IO-Link EventCode: 0x<xxxx>" for the English locale ... event code as hexadecimal representation. For example, for event code 0x18FF the message shall be "IO-Link EventCode: 0x18FF". The server may provide different locales containing a translation
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.4 IOLinkIODDDeviceEventType
  LocalizedText PropertyType Mandatory The following rules for the inherited Properties apply. The mandatory Property Message shall be mapped to the corresponding IODD Event/Description element. Localization should be considered
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.5 IOLinkPortEventType
  mapped to the IOLinkEventCode . In case of a vendor-specific EventCode ID the Message is vendor-specific. In case of all other EventCode IDs the descriptive text of IO-Link ... Addendum shall be used as Message for locale "en". For EventCode IDs 0xFF21 to 0xFFFF no text is defined. For those, the following Message texts defined in Table
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.7 IOLinkAlarmType
  IOLinkAlarmType or a subtype. The content of the Properties SourceNode , SourceName , Time , ReceiveTime , and Message is defined by its subtypes. The optional Property LocalTime shall not be provided. The Property
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.8 IOLinkDeviceAlarmType
  Link event code is not described in an IODD, the mandatory Property Message shall be set to "IO-Link EventCode: 0x<xxxx>" for the English locale ... event code as hexadecimal representation. For example, for event code 0x18FF the message shall be "IO-Link EventCode: 0x18FF". The server may provide different locales containing a translation
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.9 IOLinkIODDDeviceAlarmType
  LocalizedText PropertyType Mandatory The following rules for the inherited Properties apply. The mandatory Property Message shall be mapped to the corresponding IODD Event/Description element. Localization should be considered
• OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture
  9.10 IOLinkPortAlarmType
  mapped to the IOLinkEventCode . In case of a vendor-specific EventCode ID the Message is vendor-specific. In case of all other EventCode IDs the descriptive text of IO-Link ... Addendum shall be used as Message for locale "en". For EventCode IDs 0xFF21 to 0xFFFF no text is defined. For those, the following Message texts defined in Table
• OPC-30140 – OPC UA for PROFINET
  6.3.3.1.1 PnDeviceDiagnosisDataType
  ChannelErrorType UInt16 ExtChannelErrorType UInt16 ExtChannelAddValue UInt32 QualifiedChannelQualifier UInt32 ManufacturerData ByteString Manufacturer specific diagnosis data Message LocalizedText Diagnosis message read from the GSDML HelpText LocalizedText Help text read from the GSDML ... manufacturer specific diagnosis information, the ByteString ManufacturerData contains the manufacturer specific diagnosis data. The Message and the HelpText variables are retrieved from the GSDML file. If the Message includes
• OPC-30140 – OPC UA for PROFINET
  6.3.4.1 PnDiagnosisAlarmType
  manufacturer specific diagnosis information, the variable ManufacturerData contains the manufacturer specific diagnosis data. The Message variable of the Event and the HelpText variable are retrieved from the GSDML file ... message includes a dynamic format string, this is replaced by the ExtChannelAddValue . For an active alarm the Severity variable of the Event must be dependent on the Maintenance
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  8.1 GsdGenAlarmEventType
  manufacturer specific diagnosis information, the variable ManufacturerData contains the manufacturer specific diagnosis data. The Message variable of the Event and the HelpText variable are retrieved from the GSDML file ... message includes a dynamic format string, this is replaced by the ExtChannelAddValue . For an active alarm the Severity variable of the Event must be dependent on the Maintenance
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  5.2.3.4 ErrorConditions Object
  Model from OPC UA, which is defined in IEC 62541-9:2015. An error message is represented by an object of the type AlarmConditionType or by a type derived from ... various states such as EnabledState , AckedState or ActiveState and further properties such as Severity , Message , Time and SourceNode . The Retain Property indicates whether an error message is of interest
• OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components
  7.26.2 ObjectType definition
  ReceiveTime as defined in OPC 10000-5 , indicating the time the Event occurred. Message as defined in OPC 10000-5 , containing a human-readable text of the Event . Severity
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  9.1 LogbookEvent Definition
  instance of IMM_MES_InterfaceType for OPC 40077). NOTE: The EventSource , Time and a Message are already included in the BaseEventType of OPC UA. There shall be a buffer
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  9.15 UserFeedbackLogType
  LogbookEventType 0:HasProperty Variable Classification 0:Enumeration 0:PropertyType M Classification : Classification of the message. The valid values of the Enumeration are specified in the specific Companion Specification (e.g. IMMMessageClassificationEnumeration ... NOTE: The Message itself is included in the BaseEventType
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  14.6 ClearMESMessage
  ClearMESMessage Method for clearing the MESMessage . Calling this method sets the Properties Id and Message in MESMessage to empty string and Severity to 0. Signature ClearMESMessage (); The method
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  14.8 MessageConditionType
  HasProperty Variable IsStandstillMessage 0:Boolean 0:PropertyType M, RO Id : Id of the message Classification : Classification of the message. The valid values of the Enumeration are specified in the specific ... Companion Specification (e.g. IMMMessageClassificationEnumeration in OPC 40077). IsStandstillMessage : Indication if the message has led to a standstill. NOTE: The AlarmConditionType is a subtype of BaseEventType and therefore includes the Properties
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  35.4.3 Inherited properties of BaseEventType
  accordance with clause 6.4 . SourceNode NodeId of the root Node of the specific interface. Message keeps the result of diagnostics as a vendor specific localized text. Examples: "Wiring analysis
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  35.5.2 Inherited properties from BaseEventType
  clause 6.4 . SourceNode contains the NodeId of the root Node of the specific interface. Message keeps the result of diagnostics as a vendor specific localized text. Examples: "Successfully completed
• OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model
  6.10.1 General
  HelpSource : To provide additional information to the alarm that is not covered by the message text ( Message ), the HelpSource parameter may be used. HelpSource is specified as BaseDataType . In case ... example, this could be used to allow UIs to build their own alarm message by combining the different information fragments provided by this parameter. As CncAlarmType is derived from