Skip to content

Network allocation vector

A per-station duration state that virtually reserves a shared wireless medium.

Core Idea

A network allocation vector is a station's virtual carrier-sense state in a shared wireless MAC. A received frame duration announces how long another exchange expects to hold the medium; the station tracks that remaining interval and defers while NAV is nonzero. This is a reservation prediction encoded in protocol state, not physical energy detection. A zero NAV means only that this virtual hold has expired; physical sensing and other access rules still apply.

The IEEE 802.11 working group described RTS/CTS duration updates of NAV for an anticipated data exchange. A conceptual station A hearing such an announcement and waiting until expiry makes the mechanism visible. The working-group record is a real standard-design case, not a fabricated operational trace. The broader pattern of coordinating access to a scarce channel might transfer, but this entry requires 802.11-style duration fields and per-station virtual sensing; it is not a generic network allocation of addresses or bandwidth.

Structural Signature

Sig role-phrases:

  • Shared wireless medium — Provides a contention domain among stations using the same channel. It is constitutive. Counterfactual: A private wired link does not need this wireless virtual carrier-sense state.
  • Received duration announcement — Conveys anticipated time needed for another frame exchange. It is constitutive. Counterfactual: A station cannot derive this NAV reservation from an unrelated payload value.
  • Per-station NAV state — Stores the virtual remaining-busy interval inferred from received frames. It is constitutive. Counterfactual: NAV is a station's state, not an allocation vector of numeric network addresses.
  • Deferral while nonzero — Treats the medium as virtually occupied until the state expires under MAC rules. It is constitutive. Counterfactual: Ignoring a nonzero NAV defeats the virtual-carrier-sensing role.
  • Physical-sense qualifier — Keeps zero NAV distinct from confirmed channel idleness or guaranteed access. It is boundary. Counterfactual: A physically busy channel can remain unavailable after NAV reaches zero.

What It Is Not

  • Not physical carrier sensing. NAV predicts future occupation from frame information.
  • Not an address allocation vector. It tracks busy time, not IP assignments.
  • Not guaranteed access. Zero NAV does not override physical busy status.
  • Not the frame duration field itself. The field informs a station's maintained state.
  • Closest near-miss. Physical carrier sensing is the nearest miss: it observes current channel energy rather than maintaining a frame-announced future busy interval.

Scope of Application

  • Wireless MAC design. Coordinate shared-medium deferral from duration announcements.
  • Protocol interpretation. Distinguish virtual and physical busy indications.
  • Packet-trace analysis. Explain why a station waits despite weak current energy observation.
  • Standards education. Relate RTS/CTS duration fields to local station state without assuming universal deployment.

Clarity

Identify the station, received duration information, remaining NAV value and deferred access. Physical carrier sensing is the nearest miss. NAV belongs to a station, not to the radio channel as a global clock. Expiry permits reassessment rather than an unconditional transmit right.

Manages Complexity

A shared channel can appear quiet during a planned multi-frame exchange. NAV compresses an announced future busy interval into a local countdown so each station need not infer every hidden exchange from instantaneous energy. That prediction can be stale or incomplete, which is why physical carrier sense and other MAC conditions remain separate. The state is a coordination aid, not an absolute collision-prevention guarantee.

Abstract Reasoning

  1. Identify a shared wireless contention domain.
  2. Read the duration announcement in a relevant frame.
  3. Track the station's remaining virtual busy interval.
  4. Defer while NAV remains nonzero under the MAC rule.
  5. At expiry, reassess physical channel state and other access constraints.

Knowledge Transfer

The idea of an announced reservation causing temporary local deferral may apply to other shared resources. But a calendar reservation is not a NAV without wireless frame duration and per-station carrier-sense state. Neither physical sensing nor generic resource allocation strictly subsumes the protocol mechanism's whole identity.

Examples

Canonical

Station A hears a valid control frame announcing that another exchange is expected to occupy the shared channel for a stated interval. A sets its NAV to represent the remaining virtual busy time and defers its own transmission while that value is nonzero. When it reaches zero, A may again assess the channel, but physical carrier sensing and other access rules can still prevent immediate sending. No particular timer value or exchange sequence is needed to identify the state.

Mapped back: Shared wireless medium → A and other stations share a radio channel; Received duration announcement → control frame announces future exchange time; Per-station NAV state → A tracks remaining virtual busy interval; Deferral while nonzero → A waits during announced reservation; Physical-sense qualifier → zero permits reassessment, not guaranteed access.

Applied / In Practice

The IEEE 802.11 working group's 1993 RTS/CTS exchange document states that stations maintain a network allocation vector updated by duration fields, predicting the medium's busy interval during a subsequent data exchange. This is an attested standard-design use of NAV rather than an invented packet trace. The document does not imply that a zero NAV overrides simultaneous physical carrier sensing or proves collision-free transmission.

Mapped back: Shared wireless medium → 802.11 stations in the working-group scenario; Received duration announcement → RTS/CTS duration field; Per-station NAV state → each station maintains the announced interval; Deferral while nonzero → anticipated data exchange occupies channel; Physical-sense qualifier → separate physical sensing remains necessary.

Structural Tensions

T1 — Future Reservation versus Current Physical Signal. NAV predicts a busy interval from protocol announcements, whereas physical sensing observes the radio channel now.

Diagnostic: Which kind of evidence is being used?

T2 — Zero Nav versus Permission To Transmit. Expiry removes one virtual obstacle but does not satisfy all channel-access conditions.

Diagnostic: What other busy indication remains?

Structural–Framed Character

NAV is highly structural within a framed protocol. Evaluative weight: fairness and efficiency are design goals, not intrinsic to every NAV state. Human-practice-bound: stations implement specified MAC rules; the countdown is mechanical. Institutional origin: IEEE standardization defines frame interpretation. Vocabulary travels: reservation and deferral are broader than 802.11. Import versus recognize: a standard-compatible wireless station with duration-based virtual sensing is literal; address allocation is a name analogy.

A general announced-reservation state may be a future-prime candidate; no exact current parent covers NAV. Its character: a protocol-framed coordination state with a strict physical-sense boundary.

Structural Core vs. Domain Accent

Temporary reservation is portable, but NAV is a wireless MAC state.

What is skeletal. An announced future occupation causes other actors to defer until a time limit, coordinating shared use without continuous direct observation. That relation is a future-prime candidate only.

What is domain-bound. The actors are wireless stations, announcements are frame duration fields, and local NAV state joins physical carrier sensing. IEEE interpretation, rather than a generic timer, makes the state operational.

Why this does not clear the prime bar. Remove the radio MAC and NAV becomes a generic reservation timer. Remove the frame-derived deferral and mere physical sensing remains. The specialized protocol roles are necessary.

  • Related — wireless carrier sensing. NAV is the virtual rather than physical indication.

  • Related — RTS/CTS. Those frames commonly announce duration for NAV updates.

  • Related — contention. Deferral helps coordinate access without guaranteeing collision freedom.

Neighborhood in Abstraction Space

Network allocation vector sits in a crowded region of the domain-specific corpus (39th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Queueing, Networks & Concurrent Systems (9 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With

  • Physical sensing. Tell: Is busy status measured now or announced for the future?
  • Frame duration field. Tell: Is the field being distinguished from a station's maintained NAV?
  • Address allocation. Tell: Does the vector track time rather than addresses?
  • Transmission permission. Tell: Are other access conditions still checked at zero?

References

  • IEEE 802, Standards from IEEE 802 Unleash the Wireless Internet (2001): https://www.ieee802.org/16/docs/01/80216c-01_10.pdf
  • IEEE 802.11 Working Group, RTS/CTS Exchange and Net Allocation Vector, document 802.11-93/191 (1993): https://www.ieee802.org/11/Documents/DocumentArchives/1993_docs/1193191_scan.pdf
  • IEEE P802.11-95/22r1, virtual carrier sense draft (1995): https://www.ieee802.org/11/Documents/DocumentArchives/1995_docs/1195227-6r1_scan.pdf
  • Frozen Wikipedia discovery revision: https://en.wikipedia.org/wiki/Network_allocation_vector (revision 1369391239).