VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

The Gold Standard of Wireless Communication | Ordering Wrapped Sequence Numbers Without Inventing a Global Timeline

A message labelled 1 arrives after one labelled 14. Is it newer? If the field counts through sixteen values and then returns to zero, the ordinary numerical comparison gives the wrong answer in one perfectly reasonable history. Another history can make the same label old.

The short answer is that a wrapped sequence number needs an ordering rule and a valid comparison range. Under the half-range rule developed here, a sufficiently small forward modular difference means ahead, a sufficiently small backward difference means behind, and an exact half-cycle separation is unresolved. Equal labels alone do not prove that two observations represent the same message.

This guide uses original fictional message records. Its tiny counters make the logic visible; they do not specify how Wi-Fi, a mobile network or any particular product implements sequence numbers. Actual protocols define their own fields, lifetimes, sessions and acceptance rules. Start with the mathematical relationship, then preserve the conditions that make it useful.

eduKateSG · Wireless Communication

Find your next learning step

Identify the stream, modulus, difference and comparison boundary. Follow the worked sequence or choose the closest question.

ROUTE 1 · CHAPTERS 1–5

Define the finite field

Identify the stream, modulus, difference and comparison boundary.

ROUTE 2 · CHAPTERS 6–10

Check local order

Derive a bounded signed difference and test cycles, arcs and acceptance windows.

ROUTE 3 · CHAPTERS 11–15

Preserve identity and state

Keep sessions, duplicates, lifetime assumptions, epochs and physical time separate.

ROUTE 4 · CHAPTERS 16–21

Audit and transfer

Test out-of-range histories, reconstruct fields and solve a changed counter.

ROUTE 5 · CHAPTERS 22–26

Practise and continue

Repair overclaims, choose practice and follow the communication guides.

Full chapter contents · Wireless Communication subject guide

Chapter contents

Define the finite field · Chapters 1–5

1. Define the message stream before comparing its labels

2. Explain what wrapping preserves and what it removes

3. Calculate the forward modular difference

4. State the half-range comparison rule

5. Build a comparison ledger around one reference

Check local order · Chapters 6–10

6. Derive the signed difference within the permitted range

7. Explain why the exact half-cycle case is special

8. Show why unrestricted pairwise comparisons can form a cycle

9. Recover an ordinary order inside one short arc

10. Distinguish comparison from accepting a message

Preserve identity and state · Chapters 11–15

11. Keep the stream and session identity attached

12. Explain why equal labels do not prove a duplicate

13. Use a lifetime bound only when its premises hold

14. Distinguish a remembered epoch from a transmitted label

15. Keep sequence order separate from elapsed time

Audit and transfer · Chapters 16–21

16. Recognise an out-of-range history instead of forcing an answer

17. Check a complete record forwards

18. Solve a changed five-bit comparison

19. Apply a changed acceptance window separately

20. Test a changed collection before sorting it

21. Build a reproducible evidence card

Practise and continue · Chapters 22–26

22. Repair three overconfident explanations

23. Choose a practical learner route

24. Questions about wrapped sequence numbers

25. Continue through the relevant communication guides

26. Sources and a final ordering check

CHAPTER 1 OF 26 · Define the finite field

1. Define the message stream before comparing its labels

Back to contents

Imagine one fictional sensor producing a sequence of messages. Each new message advances a counter by one. The transmitted field has four bits, so its possible labels are the integers zero through fifteen. After fifteen comes zero. The number of labels is sixteen, which we call the modulus M.

Keep a message’s conceptual position distinct from its transmitted label. Positions fourteen, fifteen, sixteen and seventeen are different positions in the stream. Their labels are fourteen, fifteen, zero and one. The field carries a remainder; it does not carry the whole conceptual position.

This distinction concerns one identified stream with a stated progression rule. Mixing labels from different devices or sessions without preserving their identities would create another problem before any modular arithmetic began.

The first useful record therefore contains the stream identity, counter width, progression rule and observation. If any of those are unknown, leave them unknown. A familiar-looking number is not enough to reconstruct the missing contract. We will add the comparison rule explicitly rather than assume it follows from the field’s appearance.

Contents · Next chapter

CHAPTER 2 OF 26 · Define the finite field

2. Explain what wrapping preserves and what it removes

Back to contents

The label of conceptual integer position p is p modulo sixteen. Adding sixteen to p gives the same label. Positions one, seventeen and thirty-three all appear as one in the field.

Wrapping preserves the position within a cycle. It removes the cycle count unless another part of the system supplies it. That is why the label can be useful for local ordering while remaining insufficient for an unlimited historical timeline.

A clock face provides a limited analogy. A reading of one follows twelve in one short forward journey, but a photograph of the dial alone does not identify the day. Our counter differs because we have supplied a precise modulus and advancement rule. The analogy should help distinguish a remainder from its larger history, then give way to the stated arithmetic.

Before trying to recover an order, ask which information the field actually carries. A larger decimal rendering of the same four bits does not restore the lost cycle. A neat table cannot supply a missing generation count by formatting the labels more carefully.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 26 · Define the finite field

3. Calculate the forward modular difference

Back to contents

Choose a reference label r and a candidate label s. Define the forward modular difference d as the unique integer from zero through fifteen congruent to s minus r modulo sixteen.

With reference fourteen and candidate one, ordinary subtraction gives minus thirteen. Adding sixteen gives d equal to three. Counting forward through the labels confirms it: fourteen to fifteen, fifteen to zero, zero to one. There are three steps.

With reference fourteen and candidate thirteen, the forward modular difference is fifteen. A forward journey of fifteen steps is compatible with the labels, but so is a backward journey of one step. The arithmetic gives the remainder of a difference, not yet its intended signed interpretation.

Always name the direction of the subtraction. Reversing reference and candidate changes the difference. A spreadsheet column called difference is incomplete unless its definition survives into the explanation. Our next step introduces a rule for interpreting d within a restricted range; the modular calculation alone has not chosen a history.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 26 · Define the finite field

4. State the half-range comparison rule

Back to contents

For this four-bit example, half the modulus is eight. We define the candidate as ahead when d is greater than zero and less than eight. We define it as behind when d is greater than eight and less than sixteen. A zero difference gives equal labels. A difference of exactly eight is left unordered by this rule.

Thus one is ahead of fourteen because d is three. Thirteen is behind fourteen because d is fifteen, corresponding to a backward separation of one. Six and fourteen are separated by eight in either direction, so the rule supplies no ahead-or-behind answer for that pair.

This is a particular serial comparison convention, motivated by RFC 1982’s formal treatment. That RFC defines serial arithmetic for DNS; it is not a claim that every wireless protocol uses precisely this convention.

The rule is useful when the comparisons actually made satisfy the intended locality assumptions. It does not turn all labels into an ordinary globally ordered set. Keep that limitation beside the definition, because several later mistakes arise from using a local comparison as though it sorted an unlimited history.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 26 · Define the finite field

5. Build a comparison ledger around one reference

Back to contents

Use reference fourteen throughout this first ledger. Work out the modular difference before choosing the result. The categories concern the supplied rule, not a measurement of elapsed time or a verified message identity.

Candidate labelForward difference from 14, modulo 16Result under the stated rule
151Ahead
02Ahead
13Ahead
1315Behind
68Unordered
140Equal labels
Original fictional four-bit comparison ledger using modulus16 and the explicitly stated half-range rule. Equal fields do not establish message identity.

The row for zero catches ordinary numerical sorting: zero is numerically smaller than fourteen but locally ahead under the rule. The row for six catches a subtler error: choosing a direction just because subtraction can be completed would add information the convention deliberately leaves unresolved.

The equal-label row needs its own wording. It says that the four-bit fields match. It does not say whether a message is a duplicate, belongs to a later cycle or came from another session. Those are identity questions requiring the relevant surrounding evidence.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 26 · Check local order

6. Derive the signed difference within the permitted range

Back to contents

Suppose we additionally know that the true signed position difference lies strictly between minus eight and plus eight. For a modular difference below eight, the compatible signed difference is d. For a modular difference above eight, it is d minus sixteen.

Why is this unique? Two integer differences with the same remainder differ by a whole multiple of sixteen. Two distinct numbers inside that open interval cannot be sixteen apart. The interval is too short to contain both candidates.

For d equal to fifteen, the signed difference is minus one. For d equal to three, it is plus three. A remainder of eight has candidates plus eight and minus eight, neither of which lies inside our strict interval. The observation conflicts with the supplied strict-range condition rather than producing an arbitrary tie-break.

The condition is evidence or a design assumption supplied from outside the bare label pair. It cannot be proved by finding a small signed number and then declaring that number to be the true separation. That circular shortcut is exactly what the bounded interpretation is intended to prevent.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 26 · Check local order

7. Explain why the exact half-cycle case is special

Back to contents

Take labels fourteen and six. From fourteen to six is eight forward steps. From six to fourteen is also eight. The two directions have the same length around the sixteen-value cycle.

If the rule called six ahead of fourteen solely from this separation, applying the same reasoning in reverse would call fourteen ahead of six. The convention avoids that contradiction by leaving this pair unordered. An implementation may have a defined response to such a situation, but inventing one would change the model being taught here.

Do not confuse unordered with simultaneous. These messages need not have been produced together. The available field and comparison rule simply do not determine the required order for this separation.

Also distinguish this exact boundary from noisy data. No measurement error is needed to create the ambiguity. The labels can be read perfectly. The uncertainty arises because the representation is finite and the comparison’s admissible range has a boundary. More accurate copying of the same labels cannot resolve a fact that the representation and conditions do not identify.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 26 · Check local order

8. Show why unrestricted pairwise comparisons can form a cycle

Back to contents

Compare labels zero, six and twelve under the same rule. Six is ahead of zero because the forward difference is six. Twelve is ahead of six for the same reason. Zero is ahead of twelve because the forward difference is four.

These three comparisons form a cycle. They cannot all belong to one ordinary strict total order in which ahead behaves like the usual greater-than relation. In an ordinary order, transitivity would require twelve to be ahead of zero after the first two comparisons; the modular convention instead gives the opposite result for that pair.

There is no arithmetic mistake here. The mistake would be expecting the local rule to provide unrestricted transitive ordering over the whole circle.

This matters when reading an audit or sorting records. A comparison function that seems sensible for nearby messages can be unsuitable for globally sorting arbitrary labels from many cycles. The relevant proof must cover the collection and the comparisons actually required. Testing only one friendly pair, such as fourteen followed by one, does not establish that larger claim.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 26 · Check local order

9. Recover an ordinary order inside one short arc

Back to contents

Now supply a different record: conceptual positions fourteen through eighteen from one stream are known to lie in one forward interval only four steps wide. Their transmitted labels are fourteen, fifteen, zero, one and two.

Every pair of conceptual positions differs by less than eight. The half-range rule therefore agrees with their ordinary conceptual order. An anchor can assign lifted positions fourteen, fifteen, sixteen, seventeen and eighteen without a conflicting comparison inside this restricted set.

The short-arc condition does the work that was missing from the cyclic three-label example. It restricts the histories being compared. We have not discovered a global order for all possible four-bit observations; we have identified one compatible ordinary order within the stated local interval.

When writing the conclusion, retain the anchor and range. Saying that the labels were sorted correctly is weaker evidence than explaining why each allowed difference corresponds to the intended signed separation. The explicit lifted record makes that relationship inspectable by another reader rather than relying on a sorting routine’s output alone.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 26 · Check local order

10. Distinguish comparison from accepting a message

Back to contents

An ordering rule answers whether a candidate is locally ahead, behind, equal or unresolved. An acceptance rule decides what a receiver does with that candidate. These are different functions.

For a fictional exercise, suppose the receiver considers only forward differences one through five eligible for a next processing window. Relative to fourteen, labels fifteen, zero, one, two and three fall in that window. A label at difference six is locally ahead under the half-range comparison but outside this particular acceptance window.

That difference is not a contradiction. The comparison range and application window have different jobs. Calling every ahead label acceptable would silently enlarge the supplied window.

A real protocol may keep several windows and states, and its requirements need the actual specification. Our small rule isolates one distinction. A useful explanation lists the label, modular difference, comparison result and acceptance result separately. Combining them into one vague valid flag can hide whether a rejection concerns ordering, window position, identity or a different check altogether.

A reference update is a further state change that should be recorded explicitly. If a receiver advances its reference after accepting one candidate, the next candidate must be compared with that new reference under the stated rule. Reusing an earlier difference column after changing the reference mixes two questions. For example, label one is three steps ahead of fourteen, but it is only one step ahead of zero. Neither calculation is wrong; their reference points differ. A reproducible trace keeps the old reference, candidate, decision and resulting reference on the same row, so a later reader can distinguish a comparison error from an undocumented state update.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 26 · Preserve identity and state

11. Keep the stream and session identity attached

Back to contents

Suppose two devices both transmit label one. The fields agree, but the messages belong to different streams. Comparing them as positions within one counter history would begin with an unsupported identification.

A similar problem arises if a device restarts and its counter resets. A label observed before the restart and the same label observed afterward can refer to different histories. Whether a real system preserves a session identifier, an epoch, another state or a particular restart rule belongs to that system’s specification.

For this exercise, represent an observation as a stream name, session name and sequence label. The names are fictional record fields, not a proposed network format. They help the learner identify which comparisons the supplied model actually permits.

Matching all those fields can still be insufficient for a complete operational claim if the model’s lifetime or uniqueness conditions fail. Conversely, missing identity fields should not be filled by assuming that nearby arrival times prove a common session. Identity, order and time are related questions with different evidence requirements.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 26 · Preserve identity and state

12. Explain why equal labels do not prove a duplicate

Back to contents

In one conceptual stream, positions one and seventeen both have label one. A repeated observation of position one also has label one. The same transmitted field therefore fits both a duplicate observation and a later distinct position.

To call the second observation a duplicate, the system needs conditions or evidence that exclude the later-generation possibility for the comparison being made. A finite label field alone cannot do that for an unlimited lifetime.

The converse shortcut is equally weak: seeing the label change does not prove that the application accepted new unique content. Different positions may carry repeated content, or the application may reject a message for another reason. Sequence position and useful unique payload should remain distinct.

The existing goodput article develops accepted unique payload and retry time. This guide supplies a separate identity-and-order caution. Connect the two at their actual interface: an accounting model needs a defined acceptance event, and a sequence-label comparison can be one input to that event without establishing every part of it.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 26 · Preserve identity and state

13. Use a lifetime bound only when its premises hold

Back to contents

A locality condition needs an appropriate basis. In a fictional model, suppose messages advance at no more than two positions per second and an old message cannot survive for more than three seconds. If the comparison concerns the same continuing stream and the stated bound covers the relevant separation, at most six positions can accumulate during that lifetime. Six is below the half-range of eight.

This arithmetic illustrates how rate and lifetime conditions can support a comparison range. It is not a universal network design rule. The maximum rate must be a genuine bound, not an average that allows larger bursts. The lifetime must cover the relevant old information, not merely one convenient measurement interval.

A reset, a separate producer or a longer retained record can break the supplied premises. The conclusion must then be revisited. Increasing the field width may help a design meet its particular conditions, but width alone does not prove an unlimited-lifetime guarantee.

The practical evidence question is precise: what prevents a compared position from being too far away in the conceptual history? A label cannot answer that question about its own missing cycle count.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 26 · Preserve identity and state

14. Distinguish a remembered epoch from a transmitted label

Back to contents

A receiver may maintain additional state that helps extend a finite counter. For an educational representation, write a conceptual position as sixteen times an epoch plus the transmitted label. Epoch one, label one corresponds to position seventeen; epoch zero, label one corresponds to position one.

That equation is an accounting representation. It does not explain how an actual receiver learns the correct epoch when messages can arrive late, out of order or after a restart. The inference requires conditions and an algorithm appropriate to the protocol.

RFC 9187 discusses sequence-number extension for windowed protocols and makes its constrained-reordering conditions explicit. It provides useful specialist context for why extension is more than incrementing a remembered counter whenever a numerically smaller field arrives.

For our learner, the important check is whether the epoch is supplied, established under a valid model or guessed. A table can contain an epoch column while still assigning it incorrectly. Extra state helps only when its meaning and update rule are sound for the observations being processed.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 26 · Preserve identity and state

15. Keep sequence order separate from elapsed time

Back to contents

Suppose one record advances three sequence positions. That count does not automatically mean three seconds. The advancement rule may count messages rather than a fixed clock interval, and messages can be produced at unequal times.

Even with a fixed generation schedule supplied for a classroom model, arrival times can differ from generation times. A later-produced message may arrive before an earlier one. Counting positions and measuring transport delay therefore answer different questions.

The existing virtual-reality guide separates sample age from rendering time, and the logical-clock guide separates event ordering from physical time. This serial-number exercise adds another distinction: a finite representation can support a local ordering without identifying the absolute generation number.

A useful report keeps generation position, transmitted field, arrival timestamp and acceptance status in separate columns when the task supplies them. Missing values stay missing. Inferring a timestamp from a label simply because both increase in a friendly example creates a relationship the data may not support.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 26 · Audit and transfer

16. Recognise an out-of-range history instead of forcing an answer

Back to contents

Suppose the conceptual reference position is fourteen and a candidate’s true position is twenty-three. The candidate label is seven. Its forward modular difference is nine, so our local half-range comparison calls it behind, even though the supplied conceptual history puts it nine positions ahead.

This counterexample does not disprove the conditional signed-difference argument. Nine lies outside the assumed interval from minus eight to plus eight. The example shows exactly what can fail when the model is used beyond that condition.

An arithmetic routine can return an answer for a pair whose actual history violates the intended comparison range. A returned category is not evidence that the assumptions held. This is why the range belongs in the explanation and in the analysis of the system that uses the comparison.

If the true positions are supplied, use them to audit the rule’s scope. If they are not supplied, do not claim that a plausible label comparison independently proves them. The right conclusion may remain conditional on a lifetime, window or identity assumption that still needs evidence.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 26 · Audit and transfer

17. Check a complete record forwards

Back to contents

A candidate reconstruction should reproduce the observed fields. Lifted positions fourteen, fifteen, sixteen, seventeen and eighteen produce labels fourteen, fifteen, zero, one and two when reduced modulo sixteen.

This forward check catches a common transcription error: assigning zero to position fifteen because it is the sixteenth item in a casually numbered list. In our convention, conceptual position zero has label zero, so position fifteen has label fifteen. Changing the starting convention requires an explicit change to the mapping.

Forward agreement is necessary but not sufficient for historical truth. Adding sixteen to every lifted position gives the same labels. If an anchor fixes position fourteen, that global shift is excluded for this reconstruction; without an anchor, the fields alone do not choose among those shifted histories.

Check both levels. First, does the proposed history reproduce the record? Second, which evidence distinguishes that compatible history from other possibilities? A polished diagram that passes only the first check can still claim more identification than its observations support.

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 26 · Audit and transfer

18. Solve a changed five-bit comparison

Back to contents

Now use a five-bit field, with labels zero through thirty-one and modulus thirty-two. Half the range is sixteen. Take reference twenty-nine and calculate the candidate differences before reading on.

Candidate three has forward difference six and is locally ahead. Candidate twenty-four has forward difference twenty-seven, corresponding to a signed difference of minus five within the permitted range, so it is locally behind. Candidate thirteen has difference sixteen and is unordered. Candidate twenty-nine has difference zero and gives equal labels.

These results should be derived from the new modulus rather than copied from the four-bit ledger. In particular, a difference of eight is no longer the half-cycle boundary. The representation’s width changes the relevant range.

Check the first answer by following the conceptual positions twenty-nine, thirty, thirty-one, thirty-two, thirty-three, thirty-four and thirty-five. Their labels end at three after six forward steps. This is an independent changed-context check of the reasoning, not a claim about any real five-bit network field.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 26 · Audit and transfer

19. Apply a changed acceptance window separately

Back to contents

Keep the five-bit comparison but supply an acceptance window of forward differences one through four. Candidate three remains locally ahead of twenty-nine because its difference is six, yet it falls outside this narrower window.

Candidate one has difference four, so it is both locally ahead and inside the supplied window. Candidate twenty-four is behind and outside the forward window. Candidate thirteen remains unordered; the comparison rule does not supply an eligible forward position for it.

The two changed candidates expose different errors. Calling three acceptable confuses local ordering with the application’s selected window. Calling thirteen behind or ahead supplies an answer at an explicitly unresolved boundary.

A useful learner explanation reports both stages in words: calculate the modular difference, classify it under the specified comparison, then apply the separately supplied acceptance condition. If the last condition changes while the first two stay the same, the acceptance result may change without changing the ordering arithmetic. Keeping the stages separate makes the repair precise.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 26 · Audit and transfer

20. Test a changed collection before sorting it

Back to contents

For another five-bit exercise, suppose the positions are known to lie at twenty-seven, twenty-nine, thirty-one and thirty-three. Their labels are twenty-seven, twenty-nine, thirty-one and one. The entire interval is six positions wide, below the half-range of sixteen.

Using twenty-seven as an anchor gives differences zero, two, four and six. Within this supplied short interval, the lifted order agrees with the local comparison. The wrap at thirty-two does not prevent the reconstruction because the needed range condition is present.

Now remove that interval condition and consider labels zero, twelve and twenty-four. Twelve is ahead of zero, twenty-four is ahead of twelve, and zero is ahead of twenty-four, with forward differences twelve, twelve and eight. The cyclic problem returns under the larger modulus.

The lesson is not that a bigger field makes every set sortable. Its size enlarges the local range available to a justified comparison. The question remains whether the actual collection fits the assumptions required for the intended ordering operation.

Contents · Previous chapter · Next chapter

CHAPTER 21 OF 26 · Audit and transfer

21. Build a reproducible evidence card

Back to contents

Start the card with the field’s meaning, bit width and modulus. Name the stream and session, and state how the conceptual sequence advances. Identify which value is the reference and write the subtraction direction.

Record the calculated modular difference separately from its interpretation. Include the comparison convention and its exact boundary treatment. If acceptance uses a narrower window, state that window independently.

Next record the basis for locality: a supplied conceptual interval, a justified maximum separation, or a protocol condition supported by its specification. Mark a classroom assumption as an assumption. A measured average traffic rate should not be relabelled a maximum without evidence.

Finish by checking the proposed lifted positions forwards against the transmitted fields. State what remains unidentified, such as an absolute generation number, an epoch or an elapsed time. Another reader should be able to reproduce the arithmetic and see which additional fact would resolve the remaining uncertainty. That is more useful than a single status column whose definition changes between rows.

Contents · Previous chapter · Next chapter

CHAPTER 22 OF 26 · Practise and continue

22. Repair three overconfident explanations

Back to contents

“The smaller label must be older” fails at an ordinary wrap. Relative to fourteen in our four-bit example, zero is locally ahead under the supplied rule. Repair the sentence by using the stated modular difference and comparison range.

“The rule orders any collection of labels” fails on zero, six and twelve. Repair it by restricting the claim to a collection whose valid local range has been established. An isolated successful pair does not prove a global sorting property.

“Equal labels prove duplicate messages” fails when distinct conceptual positions reuse a finite field. Repair it by stating the identity, lifetime and generation conditions needed for that conclusion.

A fourth overclaim is that an unordered pair was produced at the same time. The rule’s lack of an ordering result says nothing that strong about time. The repair is to preserve what is unresolved and name the evidence needed. None of these repairs requires less curiosity; each directs it towards the missing relationship.

Contents · Previous chapter · Next chapter

CHAPTER 23 OF 26 · Practise and continue

23. Choose a practical learner route

Back to contents

For repair practice, draw sixteen numbered positions on a paper circle and mark reference fourteen. Ask the learner to count forward differences for zero, thirteen and six, then explain why their categories differ. The drawing should support the calculation rather than replace the definitions.

For stabilisation, switch to a straight conceptual record and cover its epoch column. Reduce the positions modulo sixteen, then ask which parts of the record can be recovered under a supplied short-range condition. Reveal the original positions only after the learner has stated the uncertainty.

For extension, give the five-bit example and the narrower acceptance window. Require a comparison category, an acceptance category, a forward reconstruction and one limitation. Then introduce the cyclic three-label collection and ask which earlier assumption has disappeared.

Use fictional records throughout. The learning task is to explain finite representations and conditional order, not alter a live network. A learner is ready to move on when they can distinguish a correct arithmetic result from an unsupported claim about the history that produced it.

Contents · Previous chapter · Next chapter

CHAPTER 24 OF 26 · Practise and continue

24. Questions about wrapped sequence numbers

Back to contents

Does wrapping always cause an error? No. A finite field can work within a protocol whose conditions and state make the necessary comparisons valid. The problem is using it beyond those conditions or reading it as an unlimited integer.

Why leave the half-cycle pair unresolved? The two directions are equally long. Our convention does not select one from the labels alone. Calling the pair simultaneous would add an unrelated time claim.

Can an epoch remove all ambiguity? An established epoch can restore information. How it is established and maintained under late messages, resets and reordering is part of the actual system’s problem. Merely drawing an epoch column does not solve it.

Does sequence order prove delivery before a deadline? No. Generation position, arrival time and the task’s delivery criterion require their own evidence. The existing deadline-delivery article develops that different question.

Contents · Previous chapter · Next chapter

CHAPTER 25 OF 26 · Practise and continue

25. Continue through the relevant communication guides

Back to contents

Return to The Gold Standard of Wireless Communication for the complete service question. For related performance evidence, read deadline delivery and burst-loss claims, unique payload goodput with retries and path percentiles from per-hop records. They measure different aspects of a service.

For another finite representation, wrapped phase and delay ambiguity concerns physical phase evidence, rather than a sequence-order convention. For wider computing connections, use Internet congestion control and windows, finite tags and the ABA problem and logical clocks and event ordering.

Continue through How X Works and The Gold Standard of Education for the wider learning map. The transferable habit is to preserve a representation’s information limit before using its output in a larger claim.

Contents · Previous chapter · Next chapter

CHAPTER 26 OF 26 · Practise and continue

26. Sources and a final ordering check

Back to contents

RFC 1982, Serial Number Arithmetic, published in August 1996, supplies the formal serial-comparison context. It concerns DNS. RFC 9187, Sequence Number Extension for Windowed Protocols, published in January 2022 as an Informational RFC, discusses endpoint extension under constrained reordering. Both sources were checked on 23 October 2026. Neither makes this fictional four-bit exercise a specification for a particular wireless product.

The numerical records and counterexamples here are original. Their comparisons depend on the stated modulus, convention, identity and range conditions. They do not establish real packet lifetimes, clock times or a protocol’s complete duplicate-handling behaviour.

For a final check, explain why one can be locally ahead of fourteen, why six remains unordered relative to fourteen, and why zero, six and twelve cannot be treated as one ordinary sorted timeline. Then name the extra condition that made the short-arc reconstruction valid. An answer that keeps those distinctions intact transfers beyond the original labels.

Contents · Previous chapter · Return to Wireless Communication