Skip to content

Verify USS-provided op intent reference information matches DSS-provided op intent reference information #1378

@BenjaminPelletier

Description

@BenjaminPelletier

Is your feature request related to a problem? Please describe.
In ASTM F3548-21, the full information about an operational intent is split between high-level data and details. The high-level data is found in an op intent "reference" which is the Entity tracked (and synchronized) by the DSS. When a USS provides the full information about an operational intent, that information is provided in two fields: the reference and the details. The reference information should match that in the DSS exactly, except for OVN (the DSS does not provide the true OVN; it can only be obtained directly from the USS), and perhaps uss_availability (but probably not1; I think uss_availability should match too, though we would need to make our reasoning on that very clear).

I've observed a USS provide op intent details containing reference information that differs substantially from the reference information in the DSS (specifically, time bounds were substantially different), but uss_qualifier did not indicate that any requirement was violated. Instead, I would expect that observation to show non-compliance to USS0005 since the change in the op intent was not made discoverable using the DSS.

Describe the solution you'd like
Whenever (to the extent practical) uss_qualifier obtains op intent details from a USS following an op intent reference it just retrieved from the DSS, uss_qualifier should check whether all fields in the reference field from the USS match the fields in the operational_intent_reference field or the appropriate entry in the operational_intent_references field from the DSS, except the ovn field. This is probably best accomplished via OpIntentValidator.

Note that we probably want to be lenient regarding rounding or formatting of the same effective value.

1I would argue that this should match exactly as well since the reference is the information the DSS knows about the op intent. A USS might counterargue that they have better information than the DSS on this state ("I know I'm up!"), but I don't think that argument works since one of DSS's responsibilities is to synchronize this information as canonically provided by the availability arbitrator. A USS should be providing the synchronized information according to the availability arbitrator rather than their unsynchronized belief.

Metadata

Metadata

Assignees

Labels

P1High priorityenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions