TWIN-010b — Specify Twin Interaction Direction

Go to TWIN-010 — Control Twin Interaction

The DIDO-TE SHALL specify the permitted direction of each interaction identified for a Twin Relationship.

• [DTE1] U.S. Patent Application US20220237111A1, virtual and physical Twin Node concepts, modification of Twin Nodes, comparison of results, and validation
• [DTE2] Non-Traditional BAA Submission, Digital Twin concepts, monitoring, scenario testing, integration, and Twin Nodes Selection
• [DTE9] Distributed Immutable Data Object Reference Architecture (DIDO-RA), Digital Twin, distributed data, DDS publish-subscribe, and Quality of Service concepts

An interaction permitted within a Twin Relationship may not be permitted in every direction.

For example, a Twin Realization may be permitted to receive state information from a corresponding Node without being permitted to modify that Node. Another interaction may permit exchange in both directions.

Explicit specification of interaction direction prevents bidirectional authority from being inferred from connectivity, observation capability, publication and subscription relationships, or access to a technically usable interface.

Interaction direction is distinct from authorization. Direction specifies where an interaction may flow; authorization determines whether the interaction is permitted to execute under the governing conditions.

• DIDO-TE
• Twin Relationship
• Twin Realization
• Node
• Resource
• Configuration
• Communication Parameter
• Quality of Service
• DDS

Verification confirms that:

1. Each permitted interaction identifies its permitted direction.
2. The specified direction identifies the participating source and destination entities.
3. A unidirectional interaction does not imply permission for the reverse interaction.
4. A bidirectional interaction is distinguishable from a unidirectional interaction.
5. Technical connectivity, DDS publication and subscription relationships, API availability, or Quality of Service compatibility does not override the specified interaction direction.
6. The specified direction is traceable to the governing Configuration.

Verification includes at least one unidirectional interaction and confirms that the reverse interaction is not inferred as permitted.

This requirement establishes the permitted direction of interactions identified under TWIN-010a before authorization or execution of those interactions is evaluated.

TBD

Draft

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010b-specify-twin-interaction-direction#Statement&noheader&nofooter&noeditbtn}}