ECSS Communications — Space Link Interoperability (space-systems/ecss/e50-interoperability)
Use when the task is the interoperability statement of ECSS-E-ST-50C Rev.2 clause 5.6.4 — naming the external assets a space link has to work with, and showing on what terms it can, rather than asserting that it does.
Domain quick reference
- Interoperability is a requirement before it is a property. The clause asks the mission to say who it must work with; a link that happens to be compatible with a station nobody named has satisfied nothing, and a link with no named partner has an unstated requirement, which is the defect.
- Breadth is what is being required, not one successful pairing. The link has to hold up across the mission types it claims to serve, across the traffic those missions carry — instrument returns, commanding, platform health — and across ground segments that run from a full control centre to a station that only receives. A partner list drawn from one class of mission understates the requirement before any profile is compared.
- Compatibility is per attribute and it is set intersection. Frequency band, modulation, channel coding and frame format each have a set of options a side can operate, and the two sides work together on an attribute only where those sets overlap.
- One clashing attribute is enough. A partner that matches on three of four is not three quarters supported; it is unsupported, and the whole value of the assessment is naming which attribute did it.
- Undeclared is a third outcome, not a failure. A partner that never stated its frame format may well be compatible, and reporting that as incompatible sends a team to redesign a link when the fix was an email.
- The operating option has to be picked deterministically. Where two bands overlap, the pair must agree the same one every time the assessment is run, or two documents describe two different links.
- The remedy belongs on the mission side. The partner is a fact of the ground segment; what can change is the option list the link supports, so the report names the options to add rather than the options to demand.
- Required and optional partners are graded differently. An optional asset that cannot be reached is worth reporting and does not fail the link; a required one does, and the two must not be summed into one fraction.
Workflow
- State the link profile and each partner profile as attribute to option set. Refuse a profile that omits a required attribute rather than reading the gap as unconstrained.
- Name the partners the mission requires, and check the list spans all three breadths the requirement asks of the link: the mission types it claims to serve, so a partner set drawn from a single class of mission is caught as an understated requirement; the kinds of traffic those partners carry, from instrument returns through commanding to platform health; and the ground segments the link is meant to serve — a full control centre and a station that only receives ask different things of it. An empty required set is refused: the missing requirement is the finding, not an empty result.
- Intersect the two profiles attribute by attribute, over the attributes both sides declare.
- Grade each partner into supported, unsupported with the clashing attributes named, or unconfirmed with the undeclared attributes named.
- For a supported partner, derive the operating option per attribute by a fixed rule so the agreement is reproducible.
- For an unsupported partner, report the options the link would have to add per clashing attribute, and check that adding them does restore support before reporting them.
- Close on the required set alone — supported, partial or unsupported — while still reporting every optional partner that cannot be reached.
Obligations
| Item | Step |
|---|---|
| ECSS-E-ST-50C Rev.2 5.6.4a | 2 |
Pitfalls
- Naming one mission's partners and calling the requirement stated. A link sold as serving several mission types, and assessed against the ground segment of one of them, has been graded on the easy case; the breadth it claims is the breadth the partner list has to cover.
- Reading an undeclared attribute as a wildcard. A side that declared no modulation has declared no profile, and the assumption invents an agreement neither party made.
- Scoring a partner by how many attributes matched. Links do not partially connect; a single clashing band makes the pass useless however well the rest lines up.
- Collapsing unconfirmed into unsupported. The remedies differ by orders of magnitude — one is a question to the partner, the other is a change to the spacecraft.
- Picking the operating option by iteration order. Set iteration is not ordered, so the same pair can be documented with two different bands in two runs of the same assessment.
- Reporting an incompatibility with no remedy. The mission side is the side that can change, and a finding that does not say what to add leaves the decision to whoever reads it last.
- Averaging required and optional partners into one coverage number. A link that reaches three optional stations and misses its prime station reads as mostly fine and is not.
Behavior contract (gate 3)
Profile and catalogue validation including the required attributes, the per attribute intersection, the three way partner verdict, the deterministic operating option, the remedy options checked to restore support, the cross support fraction and the required only disposition are exercised by the gate 3 contract test: scripts/test_e50_interoperability.py against scripts/e50_interoperability_logic.py (stdlib unittest, offline). Run: python3 scripts/test_e50_interoperability.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
