| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-001-establish-twin-identity:twin-001c-identify-a-twin-realization [2026/08/20 11:17] – nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-001-establish-twin-identity:twin-001c-identify-a-twin-realization [2026/08/20 11:29] (current) – nick_dido |
|---|
| ====== Twin Realization Identifier ====== | ====== TWIN-001c — Identify a Twin Realization ====== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-001-establish-twin-identity:start|Go to TWIN-001 — Establish Twin Identity]] |
| |
| ===== Discussion ===== | ===== Statement ===== |
| |
| A Twin Realization Identifier distinguishes one [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] from other Twin Realizations associated with the same or different [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identities]]. | The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL assign each [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] a unique [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]]. |
| |
| A Twin Realization Identifier identifies a particular realization rather than the logical twin represented by that realization. | ===== Source ===== |
| |
| The [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]] identifies the Twin Identity. The Twin Realization Identifier identifies an individual realization associated with that Twin Identity. | * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts |
| | * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], F17, //Twin Nodes Selection// |
| | |
| | ===== Rationale ===== |
| | |
| | A [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]] identifies the logical twin, while a [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]] identifies a particular [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] associated with that Twin Identity. |
| | |
| | Separate identification of each Twin Realization allows DIDO-TE to distinguish among multiple realizations of the same logical twin while preserving their common [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]]. |
| |
| The Twin Realization Identifier remains independent of implementation-specific identifiers such as container identifiers, process identifiers, host names, network addresses, DDS entity identifiers, or other resource identifiers. | The Twin Realization Identifier remains independent of implementation-specific identifiers such as container identifiers, process identifiers, host names, network addresses, DDS entity identifiers, or other resource identifiers. |
| |
| ===== Definition ===== | This distinction supports [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], realization selection, state acquisition, comparison, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. |
| |
| //an identifier assigned to an individual [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]]// | ===== Applies To ===== |
| |
| ===== Source ===== | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identity|Twin Identity]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization_identifier|Twin Realization Identifier]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_node|Twin Node]] |
| |
| * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]], virtual and physical Twin Node concepts | ===== Verification ===== |
| * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]], F17, //Twin Nodes Selection// | |
| * DIDO-TE normalization of the Twin Identity and Twin Realization concepts | Verification confirms that: |
| | |
| | - Each Twin Realization has a Twin Realization Identifier. |
| | - Two distinct Twin Realizations do not have the same Twin Realization Identifier within the applicable identity scope. |
| | - Multiple Twin Realizations associated with one Twin Identity remain individually distinguishable. |
| | - The Twin Realization Identifier remains distinguishable from the Twin Identifier. |
| | - A change to an implementation-specific resource identifier does not, by itself, change the Twin Realization Identifier. |
| | |
| | Verification includes inspection of a Twin Identity associated with multiple Twin Realizations. |
| | |
| | ===== Traceability ===== |
| | |
| | {{backlinks>.}} |
| |
| ===== Note ===== | ===== ConOps Relationship ===== |
| |
| A Twin Realization Identifier identifies one realization and does not replace the [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_identifier|Twin Identifier]] associated with the logical twin. | This requirement supports registration, Configuration, selection, observation, and comparison of individual Twin Realizations associated with a Twin Identity. |
| |
| Multiple Twin Realizations associated with the same Twin Identity have distinct Twin Realization Identifiers while referencing the same Twin Identifier. | ===== Delivery Phase ===== |
| |
| A change to an implementation-specific resource identifier does not, by itself, require a change to the Twin Realization Identifier. | TBD |
| |
| ===== Example ===== | ===== Requirement Status ===== |
| |
| A Twin Identity with Twin Identifier ''T-4711'' has two Twin Realizations: | Draft |
| |
| * Virtual realization ''TR-101'' | ===== Statement Reference ===== |
| * Real-world realization ''TR-102'' | |
| |
| Both realizations reference ''T-4711'', while ''TR-101'' and ''TR-102'' distinguish the individual realizations. | <code dokuwiki> |
| | {{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-001-establish-twin-identity:twin-001c-identify-a-twin-realization#Statement&noheader&nofooter&noeditbtn}} |
| | </code> |
| |
| ---- | ---- |