The first step in the onboarding process is the selection of identities that the DCA offers to the Registrar.
There are different options available to enable the DCA to discover the available GTA API DeviceIdentity personalities (4.3.3).
- Start from a well-known vendor defined personality name. This is the most straight forward approach. Figure 7 illustrates the interaction of DCA with GTA API. A vendor may also provide a list of personality names that can be provided to the Registrar.
- Start from a well-known vendor defined identifier. Multiple DeviceIdentity personalities can be associated with the same identifier, e.g., to support different profiles. Figure 8 illustrates the interaction of DCA with GTA API. It is possible that multiple personalities are eligible for onboarding and are offered to the Registrar.
- Start from a well-known vendor defined application name. Multiple personalities can be assigned the same application name. Figure 9 illustrates the interaction of DCA with GTA API. It is possible that multiple personalities are eligible for onboarding and are offered to the registrar.
- Search for a personality flagged with the dedicated attribute type org.opcfoundation.product_instance_uri. Figure 10 illustrates the interaction of DCA with GTA API. It is possible that multiple personalities are eligible for onboarding and are offered to the Registrar.
The device vendor should advise the implementor of the DCA which options apply for a specific device.
Figure 7 – Discover DeviceIdentity personality using personality name
Figure 8 – Discover DeviceIdentity personality using identifier value
Figure 9 – Discover DeviceIdentity personality using application name
Annex A.1.1 provides a code example for the search and discovery of personalities by the application name.
Figure 10 – Discover DeviceIdentity personality using attribute type org.opcfoundation.product_instance_uri
Annex A.1.2 provides a code example for the search and discovery of personalities using attribute type org.opcfoundation.product_instance_uri.
The call to gta_context_open() at the end of each sequence is representative for any further operations the DCA intends to do with the selected personality, e.g., retrieval of the Device Identity Certificate that may be stored as part of the DeviceIdentity personality as shown in Figure 11.
Figure 11 – Get DeviceIdentity Certificate
Annex A.2 gives an example for the retrieval of personality attributes.