| |
| dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-04-virtual-network-and-communication-requirements:start [2026/08/22 15:42] – created nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-04-virtual-network-and-communication-requirements:start [2026/08/22 16:12] (current) – nick_dido |
|---|
| [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to C.3 Functional Requirements]] | [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to C.3 Functional Requirements]] |
| |
| This section identifies the requirements governing Virtual Networks and communication among [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]], management components, and other entities participating in distributed verification and testing. | This section identifies the requirements governing [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_network|Virtual Networks]] and communication among [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]], management components, and other entities participating in distributed verification and testing. |
| |
| The requirements establish the network relationships and communication characteristics required to represent and exercise distributed systems without prescribing a particular network technology, communication middleware, deployment substrate, or product. | The requirements establish the network relationships and [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_characteristic|Communication Characteristics]] required to represent and exercise distributed systems without prescribing a particular network technology, communication middleware, deployment substrate, or product. |
| |
| A Virtual Network provides the logical communication environment through which participating entities communicate during testing, simulation, or training. The physical resources supporting those entities may be colocated or geographically distributed. | A [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_network|Virtual Network]] provides a logical communication environment through which participating entities communicate during testing, simulation, or training. The physical resources supporting those entities may be colocated or geographically distributed. |
| |
| The communication environment may represent characteristics of a corresponding real-world distributed system, including network topology, physical or logical separation, communication latency, communication protocols, and [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]] characteristics. | The communication environment may represent characteristics of a corresponding real-world distributed system, including [[dido:99_annexes:annex-b-terms-and-definitions:n:network_topology|Network Topology]], physical or logical separation, communication latency, communication protocols, and [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]] characteristics. |
| |
| Virtual Network and communication requirements remain distinct from the requirements governing the lifecycle and behavior of individual Nodes, Twin Realizations, Test Execution, State and Time Control, Security, and Interoperability assessment. | Virtual Network and communication requirements remain distinct from the requirements governing the lifecycle and behavior of individual Nodes, Twin Realizations, Test Execution, State and Time Control, Security, and Interoperability assessment. |
| The requirements in this section derive from the source documents identified in Annex B. | The requirements in this section derive from the source documents identified in Annex B. |
| |
| The U.S. Patent Application describes a DIDO-TE Virtual Network that communicatively couples distributed virtual nodes and permits communication without regard to the physical distance separating those nodes. The source further describes configuration of a Virtual Network to represent distances, latencies, and communication protocols used by corresponding physical distributed systems. | The U.S. Patent Application describes a DIDO-TE Virtual Network that communicatively couples distributed virtual Nodes and permits communication without regard to the physical distance separating those Nodes. The source further describes configuration of a Virtual Network to represent distances, latencies, and communication protocols used by corresponding real-world distributed systems. |
| |
| The patent also describes communication with geographically remote nodes, cooperation between Virtual Networks and physical nodes, interaction with real-world devices and systems, interface testing between nodes, and interoperability testing under differing communication conditions. | The patent also describes communication with geographically remote Nodes, cooperation between Virtual Networks and [[dido:99_annexes:annex-b-terms-and-definitions:r:real-world_node|Real-World Nodes]], interaction with real-world devices and systems, interface testing between Nodes, and interoperability testing under differing communication conditions. |
| |
| The DIDO-TE BAA material extends this concept to distributed interoperability testing involving virtual and real-world systems and identifies testing under degraded or contested communication conditions. | The DIDO-TE BAA material extends this concept to distributed interoperability testing involving virtual and real-world systems and identifies testing under [[dido:99_annexes:annex-b-terms-and-definitions:d:degraded_communication_condition|Degraded Communication Conditions]] or contested communication conditions. |
| |
| The DIDO Reference Architecture provides the broader distributed-system, DDS publish-subscribe, and DDS Quality of Service concepts used to interpret communication requirements without requiring DIDO-TE to prescribe DDS or another specific communication implementation. | The DIDO Reference Architecture provides the broader distributed-system, DDS publish-subscribe, and DDS Quality of Service concepts used to interpret communication requirements without requiring DIDO-TE to prescribe DDS or another specific communication implementation. |
| | NET-001 | Establish a Virtual Network | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], Virtual Network definition and configuration; [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2]]], Virtual Networks and Communication | | | NET-001 | Establish a Virtual Network | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], Virtual Network definition and configuration; [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2]]], Virtual Networks and Communication | |
| | NET-002 | Define Virtual Network Topology | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], Virtual Network and network topography concepts; [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5]]], inter-node topology source requirements | | | NET-002 | Define Virtual Network Topology | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], Virtual Network and network topography concepts; [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5]]], inter-node topology source requirements | |
| | NET-003 | Connect Nodes Through a Virtual Network | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], network communicatively coupling virtual nodes and management systems | | | NET-003 | Connect Nodes Through a Virtual Network | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], network communicatively coupling virtual Nodes and management systems | |
| | NET-004 | Configure Communication Characteristics | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], distance, latency, and communication-protocol representation; [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9]]], DDS Quality of Service concepts | | | NET-004 | Configure Communication Characteristics | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], distance, latency, and communication-protocol representation; [[dido:03-dido-te:99-annexes:annex-b-references:dte-009|[DTE9]]], DDS Quality of Service concepts | |
| | NET-005 | Reproduce Degraded Communication Conditions | [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2]]], degraded or contested communications environments; [[dido:03-dido-te:99-annexes:annex-b-references:dte-003|[DTE3]]], testing in degraded or contested environments | | | NET-005 | Reproduce Degraded Communication Conditions | [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2]]], degraded or contested communications environments; [[dido:03-dido-te:99-annexes:annex-b-references:dte-003|[DTE3]]], testing in degraded or contested environments | |
| | NET-006 | Connect Real-World Nodes Through a Virtual Network | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], physical-node cooperation and real-world device, Node, or system interaction with a Virtual Network | | | NET-006 | Connect Real-World Nodes Through a Virtual Network | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], real-world Node cooperation and interaction with a Virtual Network | |
| | NET-007 | Support Geographically Distributed Nodes | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], geographically remote physical nodes and distance-independent communication; [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5]]], geographically distributed deployments | | | NET-007 | Support Geographically Distributed Nodes | [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1]]], geographically remote Nodes and distance-independent communication; [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5]]], geographically distributed deployments | |
| |
| ===== Contents ===== | ===== Contents ===== |
| Distributed systems depend upon communication relationships among Nodes rather than upon the behavior of isolated Nodes alone. | Distributed systems depend upon communication relationships among Nodes rather than upon the behavior of isolated Nodes alone. |
| |
| A DIDO-TE Test Environment therefore requires a controlled communication environment in which the network relationships and communication characteristics relevant to a test can be established independently of the physical infrastructure hosting the participating entities. | A DIDO-TE [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] therefore requires a controlled communication environment in which the [[dido:99_annexes:annex-b-terms-and-definitions:n:network_topology|Network Topology]] and [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_characteristic|Communication Characteristics]] relevant to a test can be established independently of the physical infrastructure hosting the participating entities. |
| |
| The Virtual Network represents the communication relationships required by the distributed system under test. Those relationships may involve virtual Nodes, physical Nodes, Twin Realizations, management components, or other participating entities. | The [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_network|Virtual Network]] represents the communication relationships required by the distributed system under test. Those relationships may involve virtual Nodes, [[dido:99_annexes:annex-b-terms-and-definitions:r:real-world_node|Real-World Nodes]], Twin Realizations, management components, or other participating entities. |
| |
| Separating the Virtual Network from its physical realization permits DIDO-TE to represent distributed systems whose participating entities are colocated, remotely located, virtualized, physical, or distributed across heterogeneous infrastructure. | Separating the Virtual Network from its physical realization permits DIDO-TE to represent distributed systems whose participating entities are colocated, geographically separated, virtualized, physical, or distributed across heterogeneous infrastructure. |
| |
| Communication characteristics form part of the test conditions. Latency, communication protocol, Quality of Service, and degraded or contested communication conditions can affect distributed-system behavior even when the participating Nodes and application software remain unchanged. | [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_characteristic|Communication Characteristics]] form part of the test conditions. Latency, communication protocol, Quality of Service, and [[dido:99_annexes:annex-b-terms-and-definitions:d:degraded_communication_condition|Degraded Communication Conditions]] can affect distributed-system behavior even when the participating Nodes and application software remain unchanged. |
| |
| These requirements define the capabilities required to establish and control those communication conditions. They do not prescribe a particular networking product, overlay technology, service mesh, DDS implementation, container-network implementation, cloud provider, or physical network. | These requirements define the capabilities required to establish and control those communication conditions. They do not prescribe a particular networking product, overlay technology, service mesh, DDS implementation, container-network implementation, cloud provider, or physical network. |
| |
| Network-oriented Security requirements remain governed by C.4 Security Requirements. State and timing behavior that extends beyond communication characteristics remains governed by C.3.5 State and Time Control Requirements. Test actions that exercise interfaces or interoperability remain governed by the applicable Test Definition and Test Execution requirements. | Network-oriented Security requirements remain governed by C.4 Security Requirements. State and timing behavior that extends beyond Communication Characteristics remains governed by C.3.5 State and Time Control Requirements. Test actions that exercise interfaces or interoperability remain governed by the governing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] and Test Execution requirements. |
| |
| ===== Applies To ===== | ===== Applies To ===== |
| |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_network|Virtual Network]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:n:network_topology|Network Topology]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] | * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:r:real-world_node|Real-World Node]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] | * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realization]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] | * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] | * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] | * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_characteristic|Communication Characteristic]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_parameter|Communication Parameter]] | * [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_parameter|Communication Parameter]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:d:degraded_communication_condition|Degraded Communication Condition]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]] | * [[dido:99_annexes:annex-b-terms-and-definitions:q:qos|Quality of Service]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] |
| This requirement family supports establishment and control of the communication environment used during distributed Test Execution. | This requirement family supports establishment and control of the communication environment used during distributed Test Execution. |
| |
| The ConOps describes how Nodes, Twin Realizations, physical systems, and other participating entities are connected through that environment and how configured communication conditions are applied during testing. | The ConOps describes how Nodes, Twin Realizations, Real-World Nodes, and other participating entities are connected through a Virtual Network and how configured Communication Characteristics and Degraded Communication Conditions are applied during testing. |
| |
| The requirement family remains product-neutral. A realization may use physical networks, virtual networks, overlays, container networking, software-defined networking, DDS, other middleware, or combinations of these mechanisms. | The requirement family remains product-neutral. A realization may use physical networks, virtual networks, overlays, container networking, software-defined networking, DDS, other middleware, or combinations of these mechanisms. |
| Apply the requirement identification, decomposition, source and derivation, normative-language, quality, status, and page-structure rules defined by Annex C. | Apply the requirement identification, decomposition, source and derivation, normative-language, quality, status, and page-structure rules defined by Annex C. |
| |
| NET-004 is expected to be a non-leaf requirement group because independently verifiable communication characteristics should be decomposed into separate leaf requirements. Candidate subordinate requirements include communication latency, communication protocols, and Quality of Service. Add other characteristics only when an authoritative source or approved architectural derivation establishes the requirement. | NET-004 is a non-leaf requirement group because independently verifiable Communication Characteristics should be decomposed into separate leaf requirements. Candidate subordinate requirements include communication latency, communication protocols, and Quality of Service. Add other Communication Characteristics only when an authoritative source or approved architectural derivation establishes the requirement. |
| |
| Do not infer packet loss, jitter, bandwidth constraints, routing behavior, firewall behavior, or other specific network impairments solely from the phrase ''degraded or contested communications''. Derive such requirements separately when their source and required semantics are established. | Do not infer packet loss, jitter, bandwidth constraints, routing behavior, firewall behavior, or other specific network impairments solely from a [[dido:99_annexes:annex-b-terms-and-definitions:d:degraded_communication_condition|Degraded Communication Condition]] or the source phrase ''degraded or contested communications''. Derive such requirements separately when their source and required semantics are established. |
| |
| Do not prescribe DDS, Kubernetes networking, a service mesh, a software-defined network, a cloud virtual network, or another implementation technology in a canonical NET requirement unless the governing source explicitly requires that technology. | Do not prescribe DDS, Kubernetes networking, a service mesh, a software-defined network, a cloud virtual network, or another implementation technology in a canonical NET requirement unless the governing source explicitly requires that technology. |