Search

11 result(s) for Stack

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.1 Service Set model
  represent a specification for implementation. The mapping between the abstract descriptions and the Communication Stack derived from these Services are defined in OPC 10000-6 . These Services are organized into
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.2 Request/response Service procedures
  Client and the Server may make use of the API of a Communication Stack to construct and interpret Messages and to access the requested operation. The implementation of each service
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.6.1 Overview
  implemented directly by the OPC UA Application . Instead, they are provided by the Communication Stack on which the OPC UA Application is built. For example, an OPC UA Server ... built on a stack that allows applications to establish a SecureChannel using HTTPS. In these cases, the OPC UA Application shall verify that the Message it received
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.32 RequestHeader
  timeoutHint UInt32 This timeout in milliseconds is used in the Client side Communication Stack to set the timeout on a per-call base. For a Server this timeout is only
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.35 SessionAuthenticationToken
  purposes of this discussion, a Server consists of application (code) and a Communication Stack as shown in Figure 37 . Figure 37 - Logical layers of a Server The security provided ... SessionAuthenticationToken depends on a trust relationship between the Server application and the Communication Stack . The Communication Stack shall be able to verify the sender of the message and it uses
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  4 Overview
  wire. The normative descriptions are defined in Annex B and Annex F . A Stack is a collection of software libraries that implement one or more StackProfiles . The interface between ... application and the Stack is a non-normative API which hides the details of the Stack implementation. An API depends on a specific DevelopmentPlatform . Note that the datatypes exposed
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.1 Security Handshake and Security Policies
  online Profiles website. OPC 10000-7 defines the link to this website. A Stack is expected to have knowledge of the SecurityPolicies that it supports. Applications specify the SecurityPolicy they ... wish to use by passing the URI to the Stack . Table 49 defines the contents of a SecurityPolicy. Each SecurityProtocol mapping specifies how to use each of the parameters
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.1 Overview
  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 and reconstructing
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.2.3 Security Header
  X.690 This indicates what Private Key was used to sign the MessageChunk . The Stack shall close the channel and report an error to the application if the SenderCertificate
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.3 Establishing a connection
  processing while the SecureChannel is negotiated; however, the Server application shall provide the Stack with the list of trusted Certificates . The Stack shall provide notifications to the Server application whenever
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.4 Closing a connection
  Server application does not do any processing when the SecureChannel is closed; however, the Stack shall provide notifications to the Server application whenever a CloseSecureChannel request is received or when ... Stack cleans up an abandoned SecureChannel