Search

Scope: Core (OPC-10000-*) All specs

12 result(s) for Composite

OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.3 Composite

Composite a collection of Devices or Composites assembled into a single unit. Note 1 to entry: Each Composite has a globally unique identifier. Note 2 to entry: A Composite ... single Device when connected to a network. Note 3 to entry: A Composite may appear as multiple Devices when connected to a network
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.5 CompositeInstanceUri

CompositeInstanceUri a globally unique resource identifier assigned by a builder to a Composite
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.19 Ticket

Ticket a document that identifies a Device or Composite and has a DigitalSignature
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.1 Device Lifecycle

Device has a unique identifier and may have one or more Applications (see 3.1.4 ). Composite A collection of Devices or Composites assembled into a single unit. Each Composite ... Device . A Ticket describing the Device is created and signed by the Manufacturer. Composite Assembly A Composite is created from Devices and a unique identity is assigned to the Composite
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.3 Transfer of Physical Control

transfer of physical control occurs, the supplier ships the equipment (a Device or Composite ) and an electronic Ticket (see 6 ) that describes the equipment. The receiver may use the Ticket
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.2 Onboarding

Onboarding Onboarding is the process where a Device or Composite is connected to the network managed by an organization. When this happens the authenticity of the Device is verified
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.3 Composite Identity

Composite Identity A Composite is a piece of equipment that contains a network of Devices . All of these Devices are internal to the Composite and can be accessed by other ... Devices within the Composite . Some of these Devices are also visible on an external network and have one or more Applications that need to be provisioned. Composites are an abstraction
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.2 Ticket Distribution

each Device. When transferring Composites, the sender provides a CompositeIdentityTicket (see 8.2.4 ) for each Composite and a DeviceIdentityTicket for each externally visible Device in the Composite. The DeviceIdentityTickets and CompositeIdentityTickets
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.3 Authentication

registration process here also applies to externally visible Devices that are contained in a Composite . In these cases, the CompositeBuilder provides the list of Devices . When a Device is first
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.4 Acquiring and Validating Tickets

authorized. The second strategy uses a Ticket that is distributed with the Device or Composite . This Ticket could be stored on the Device or on physical media that was delivered
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.1 Overview

Method (see pull management in 7.2 ). If the matching DeviceIdentityTicket is referenced by a Composite Ticket (see CompositeIdentityTicketType in 8.2.4 ) then the Registrar looks for a Certificate that has both ... ProductInstanceUri as values in the subjectAltName . A Device that is part of a Composite should provide the Composite Tickets in the RequestTickets or ProvideTickets Method. Partial matches to DeviceIdentityTickets
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.2.4 CompositeIdentityTicketType

CompositeIdentityTicketType The CompositeIdentityTicketType describes a single Composite produced by a CompositeBuilder . The fields of this DataType are defined in Table 11 . Table 11 - CompositeIdentityTicketType Structure Name Type Description CompositeIdentityTicketType ... BaseTicketType DataType defined in 8.2.2 . compositeInstanceUri 0:UriString The ProductInstanceUri assigned to the Composite. This value appears in LDevID Certificates assigned to Devices by the CompositeBuilder (see 5.3 ). devices