Search

6 result(s) for MessageChunks

• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.1 Overview
  reason, OPC UA Secure Conversation will break OPC UA Messages into several pieces (called ' MessageChunks' ) that are smaller than the buffer size allowed by the TransportProtocol . UASC requires a TransportProtocol ... based Asymmetric Cryptography (see 6.8 ) is supported. All security is applied to individual MessageChunks and not the entire OPC UA Message . A Stack that implements UASC is responsible for verifying
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.4 Sequence Header
  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 ... Binary encoding as described in 5.2.9 . The body may be split across multiple MessageChunks
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.3 MessageChunks and error handling
  MessageChunks and 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
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.3 Hello Message
  least 8192 bytes otherwise. MaxMessageSize UInt32 The maximum size for any response Message . If MessageChunks have not been sent, the Server shall return an Error Message with a Bad_ResponseTooLarge ... error if a response Message exceeds this value. If MessageChunks have already been sent the Server shall abort the Message as described in 6.7.3 . The Message size is calculated using
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.4 Acknowledge Message
  value the Client shall report a Bad_ Bad_RequestTooLarge error to the application. If MessageChunks have already been sent the Client shall also abort the Message as described
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.3 Establishing a connection
  reported to the SecureChannel layer. The negotiated SendBufferSize specifies the size of the MessageChunks to use for Messages sent over the connection. If the Server creates the TransportConnection the first