ECSS Communications — Data Unit Identifier (space-systems/ecss/e50-data-unit-identifier)
Use when the identifier carried by each data unit on a space link is being
sized or reviewed, per ECSS-E-ST-50C clause 5.6.13.2 — whether a formatted
unit carries an identifier at all and which endpoint it names, and then,
past what the clause asks, whether the counter carrying that identifier
still names one unit by the time anyone acts on it.
Domain quick reference
- What the clause itself asks is short: a formatted data unit on the
space link carries an identifier, and that identifier names its
source, its destination, or both at once. Step 1 is where that is
settled. Everything after it is this leaf's own discipline — a
counter that wraps still carries an identifier and still satisfies
the item, and can still leave a receiver acting on the wrong unit.
- Unambiguous has a duration. A counter in a fixed field names a unit
uniquely only until it wraps, so the sizing question is never whether
the field is wide enough but whether it is wide enough for the window
the system still cares about that unit in.
- The window is set by what the design does with the identifier, not by
the pass. Retransmission, reordering, gap filling and ground-side
reconciliation all reach back in time, and the longest of them governs.
- Coverage is the number to report: the field modulus divided by the
units live inside the window. Below one, two live units share an
identifier. At exactly one, nothing may ever be late.
- A field that covers the window once has no room for the thing that
will happen. A retransmission, a stretched contact or a slower ground
turnaround all lengthen the window after the field was sized.
- Size the field by doubling an integer, not by taking a logarithm. A
demand landing exactly on a power of two must not come out as one bit
on one platform and the next bit up on another.
- An observed run says different things at once. A backwards step is a
wrap, a repeated value is a duplicate, and a value the field could
never have carried is a decoding fault. Reporting all three as missing
units sends the investigation the wrong way.
Workflow
- Check first that every formatted data unit the space link carries
holds an identifier at all, and which endpoint it names: its source,
its destination, or both at once. An identifier that names
neither leaves a receiver with nothing to act on. The name only has
to hold inside the one spacecraft's domain; a wider, universally
unique name may be built by reading the identifier together with
others, the spacecraft identifier among them.
- State the retention window before the field width. The window is a
system property; the width is the answer to it.
- Compute the field modulus from the width, and the wrap period from
the modulus and the production rate.
- Compute how many units are live inside the window, and take coverage
as the modulus over that count.
- Decide the three-way verdict with a relative tolerance, so a field
sized exactly to its window is decided the same way everywhere.
- Report the narrowest width that would cover the window with the
margin asked for, found by doubling an integer capacity, so the
recommendation is exact rather than a rounded logarithm.
- When reading an observed run, reject any value outside the field
first. It is a decoding fault and it would otherwise manufacture a
long run of phantom gaps.
- Separate wraps, gaps and duplicates in the report, and give the
identifier expected next so a receiver's own bookkeeping can be
checked against it.
Obligations
| Item |
Step |
| ECSS-E-ST-50C Rev.2 5.6.13.2a |
1 |
Pitfalls
- Sizing the counter against the pass rather than the retention window.
The window is usually longer, and the shortfall only shows when a
retransmission arrives after the wrap.
- Reading a coverage of one as adequate. It means the newest unit takes
the identifier of the oldest one still in play, with nothing late.
- Taking a logarithm to size the field. The result lands on either side
of a power of two depending on the platform, so two machines recommend
different widths for the same input.
- Counting a repeated identifier as a wrap. It inflates how many units
the run is thought to cover and hides a genuine duplicate.
- Treating an out-of-field value as a lost unit. It is a decoding or
framing fault, and reported as a gap it produces a list of missing
units that were never sent.
- Deciding the wrap comparison with a bare strict inequality. A field
sized exactly to its window can come out ambiguous on one platform and
unambiguous on another.
Behavior contract (gate 3)
Field width and rate validation, the modulus, the wrap period, live
units in the window, coverage, the three-way verdict with a relative
tolerance at the coverage bound, exact integer sizing of the narrowest
adequate field with an impossible demand raising, and the observed-run
analysis separating wraps, gaps, duplicates and out-of-field values are
exercised by the gate 3 contract test:
scripts/test_e50_data_unit_identifier.py against
scripts/e50_data_unit_identifier_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_e50_data_unit_identifier.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e50-data-unit-identifier3description: "Verify that every formatted data unit a space link carries holds an identifier naming its source, its destination or both, under ECSS-E-ST-50C clause 5.6.13.2, then size the counter field that carries that identifier so it still names one unit for as long as the design acts on it. Compute the modulus of the counter field, the period it takes to wrap, how many units are live inside the retention window, and the coverage of one against the other; separate a field that wraps inside the window from one that covers it with no margin; size the narrowest field that works by exact integer doubling; and read an observed run for gaps, wraps and repeats. Use when sizing or reviewing data unit counters. Trigger: ecss, e-st-50-communications, data-unit-identifier-field-width, data-unit-counter-wrap-ambiguity, data-unit-sequence-gap-detection, data-unit-retention-window-coverage."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13clauses:14 - standard: ECSS-E-ST-50C Rev.215 clause: 5.6.13.216 items: [a]17 relation: verifies18metadata:19 source: https://skillmd.com/skills/ashfordeou/e50-data-unit-identifier20 domain: space-systems21 subdomain: ecss22 tags: [ecss, e-st-50-communications, e50-data-unit-identifier, data-unit-identifier-field-width, data-unit-counter-wrap-ambiguity, data-unit-sequence-gap-detection, data-unit-retention-window-coverage, data-unit-identifier-sizing]23 version: 0.1.024 author: Aero Agent Skills25---2627# ECSS Communications — Data Unit Identifier (space-systems/ecss/e50-data-unit-identifier)2829Use when the identifier carried by each data unit on a space link is being30sized or reviewed, per ECSS-E-ST-50C clause 5.6.13.2 — whether a formatted31unit carries an identifier at all and which endpoint it names, and then,32past what the clause asks, whether the counter carrying that identifier33still names one unit by the time anyone acts on it.3435## Domain quick reference3637- What the clause itself asks is short: a formatted data unit on the38 space link carries an identifier, and that identifier names its39 source, its destination, or both at once. Step 1 is where that is40 settled. Everything after it is this leaf's own discipline — a41 counter that wraps still carries an identifier and still satisfies42 the item, and can still leave a receiver acting on the wrong unit.43- Unambiguous has a duration. A counter in a fixed field names a unit44 uniquely only until it wraps, so the sizing question is never whether45 the field is wide enough but whether it is wide enough for the window46 the system still cares about that unit in.47- The window is set by what the design does with the identifier, not by48 the pass. Retransmission, reordering, gap filling and ground-side49 reconciliation all reach back in time, and the longest of them governs.50- Coverage is the number to report: the field modulus divided by the51 units live inside the window. Below one, two live units share an52 identifier. At exactly one, nothing may ever be late.53- A field that covers the window once has no room for the thing that54 will happen. A retransmission, a stretched contact or a slower ground55 turnaround all lengthen the window after the field was sized.56- Size the field by doubling an integer, not by taking a logarithm. A57 demand landing exactly on a power of two must not come out as one bit58 on one platform and the next bit up on another.59- An observed run says different things at once. A backwards step is a60 wrap, a repeated value is a duplicate, and a value the field could61 never have carried is a decoding fault. Reporting all three as missing62 units sends the investigation the wrong way.6364## Workflow65661. Check first that every formatted data unit the space link carries67 holds an identifier at all, and which endpoint it names: its source,68 its destination, or both at once. An identifier that names69 neither leaves a receiver with nothing to act on. The name only has70 to hold inside the one spacecraft's domain; a wider, universally71 unique name may be built by reading the identifier together with72 others, the spacecraft identifier among them.732. State the retention window before the field width. The window is a74 system property; the width is the answer to it.753. Compute the field modulus from the width, and the wrap period from76 the modulus and the production rate.774. Compute how many units are live inside the window, and take coverage78 as the modulus over that count.795. Decide the three-way verdict with a relative tolerance, so a field80 sized exactly to its window is decided the same way everywhere.816. Report the narrowest width that would cover the window with the82 margin asked for, found by doubling an integer capacity, so the83 recommendation is exact rather than a rounded logarithm.847. When reading an observed run, reject any value outside the field85 first. It is a decoding fault and it would otherwise manufacture a86 long run of phantom gaps.878. Separate wraps, gaps and duplicates in the report, and give the88 identifier expected next so a receiver's own bookkeeping can be89 checked against it.9091## Obligations9293| Item | Step |94|---|---|95| ECSS-E-ST-50C Rev.2 5.6.13.2a | 1 |9697## Pitfalls9899- Sizing the counter against the pass rather than the retention window.100 The window is usually longer, and the shortfall only shows when a101 retransmission arrives after the wrap.102- Reading a coverage of one as adequate. It means the newest unit takes103 the identifier of the oldest one still in play, with nothing late.104- Taking a logarithm to size the field. The result lands on either side105 of a power of two depending on the platform, so two machines recommend106 different widths for the same input.107- Counting a repeated identifier as a wrap. It inflates how many units108 the run is thought to cover and hides a genuine duplicate.109- Treating an out-of-field value as a lost unit. It is a decoding or110 framing fault, and reported as a gap it produces a list of missing111 units that were never sent.112- Deciding the wrap comparison with a bare strict inequality. A field113 sized exactly to its window can come out ambiguous on one platform and114 unambiguous on another.115116## Behavior contract (gate 3)117118Field width and rate validation, the modulus, the wrap period, live119units in the window, coverage, the three-way verdict with a relative120tolerance at the coverage bound, exact integer sizing of the narrowest121adequate field with an impossible demand raising, and the observed-run122analysis separating wraps, gaps, duplicates and out-of-field values are123exercised by the gate 3 contract test:124scripts/test_e50_data_unit_identifier.py against125scripts/e50_data_unit_identifier_logic.py (stdlib unittest, offline).126Run:127python3 scripts/test_e50_data_unit_identifier.py128129## Compliance130131- ECSS standards are freely downloadable (ESA); cite the source and132 paraphrase per standards-map.yaml.133- compliance: STANDARDS-REF, gated: false.