Search

3 result(s) for Device.

• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  5.1 Device Identity
  Device Identity Every Device shall have an "Initial Device Identifier" (IDevID) Certificate (see 802.1AR ) that is used to prove the origin of the Device . This identity shall ... field (see RFC 5280 ). If the IDevID Certificate does not have the ProductInstanceUri the Device shall have an LDevID (Locally Significant Device Identifier) Certificate with the ProductInstanceUri in the subjectAltName
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.2 Ticket Distribution
  When transferring Devices, the sender provides a DeviceIdentityTicket (see 8.2.1 ) for each Device. When transferring Composites, the sender provides a CompositeIdentityTicket (see 8.2.4 ) for each Composite and a DeviceIdentityTicket ... each externally visible Device in the Composite. The DeviceIdentityTickets and CompositeIdentityTickets should be created and signed by the original Manufacturer and/or CompositeBuilder , however, a trusted intermediary, such as a Distributor
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  7.1 Overview
  trust. The steps to determine trust are: Read all DeviceIdentity Certificates from the Device ; Locate a Ticket that has a ProductInstanceUri that matches one or more DeviceIdentity Certificates ; Validate ... Validate DeviceIdentity Certificate that matches the Ticket ; Establish a secure connection to the Device using the selected DeviceIdentity Certificate. Issue a DCA Application Instance Certificate to the Device that indicates