How to Read a Wireless Standard & System

Five range claims, five different questions

Five people say “Bluetooth range.” Are they discussing the same engineering quantity?

The systems engineer needs complete reports on time. The RF designer needs a receiver criterion. Marketing has a demonstration, and procurement has a qualification record. Each document may be accurate within its scope while supporting none of the other conclusions. First extract the claim; only then decide which document could establish it.

PHY means physical layer; MAC means medium access control. Packet error ratio (PER) is the fraction of expected test packets that fail the stated packet criterion. Bit error ratio (BER) counts erroneous bits against the tested bit population. Neither automatically equals the fraction of complete application reports delivered before a deadline.

Reading task: underline the quantity, circle the population, and mark the plane in each row. Treat every unfilled condition as unknown. Do not convert a missing report into a measured failure, and do not convert absent evidence into a passing value. The consequence is practical: a team that buys the “best range” number may optimize a receiver mode its gateway never uses.

Define the product mode before opening the standard

What must the node deliver before any technology name is useful?

Freeze a local service variant: one 32-byte application report every 60 s, with at least 99% of complete reports delivered within 2 s in each declared mounting/site stratum. D0 is the application boundary; latency begins when the node releases the report and ends when the gateway delivers it. Duplicates count once; late reports miss the deadline. These are chosen teaching requirements, not standard limits or measured achievements.

The portfolio’s 2.450 GHz QPSK waveform remains a generic earlier example. It is not renamed Bluetooth. This module introduces a named LE variant; it carries the earlier antenna evidence IDs without changing their values or turning them into evidence for the new waveform.

Read the host boundary: Core 6.2 GAP §11 defines AD structures with a length byte and type byte. Supplement v14 §1.4 defines manufacturer-specific data with a two-byte company identifier followed by manufacturer-defined content. For a bare 32-byte report, that single AD structure would therefore occupy 36 bytes; no identifier is assigned here. Extra schema/security fields would add bytes. BT-GAP, BT-CSS.

Identify who owns each document

Does a reputable publisher make every document it publishes normative?

No. An issuer identifies who published the material. The document role identifies the question it can answer. The same organization can publish a specification, an introductory article and a qualification policy. Use the title page, scope, interpretation conventions and references to classify the document before trusting a search-result snippet.

Checked example: the SIG’s qualification overview describes an interoperability and licensing process. OFCOM’s CH overview routes a product toward applicable legal requirements. They answer different questions even when both are needed for the same product. BT-QUAL, CH-OFCOM.

Decision: give every consequential claim an owner and a source role. If the source is only a catalogue entry, record identity and access limits; do not record that the body of the standard supports your claim.

Read requirements in their actual scope

Can a keyword search for “shall” replace reading the requirement?

A requirement is a conditional statement with a subject and scope. A sentence can be mandatory for one selected feature and irrelevant to another. Read the preceding conditions and following exceptions, then follow normative references. An informative annex can explain intent without adding a requirement; confirm its designation rather than assuming that all annexes have one status.

Bluetooth Core 6.2 Vol 1 Part E §1 uses “shall” for requirements, “should” for recommendations and “may” for permission. Optional implementation choices still carry the specified behavior when implemented. “Must” has a separate factual/consequence usage in this document; do not import another publisher’s vocabulary mechanically. BT-LANGUAGE, Table 1.1 and following paragraph.

Reading task: rewrite the first fictional sentence as “condition → actor → required behavior.” Attach the feature/conformance-class declaration. The consequence of skipping that step is either overtesting an absent option or overlooking a requirement for a feature you did enable.

Build a compatible version chain

Should every document in a valid chain have the same version number?

A base revision can consolidate earlier amendments. An amendment changes selected material; an erratum corrects identified text. A profile selects application behavior; a release groups features on its own schedule. A test package and regional document can evolve independently. Pin complete identities and curate compatibility for the exact endpoints.

A real different-numbered relationship appears in the Supplement version history: v14 was adopted alongside Core 6.2. For layer mixing, Core 6.2 Vol 0 Part D §3 permits different Host and Controller versions subject to its constraints; all included Controller layers must share one Controller version. A claim that combines PHY 6.2 with Link Layer 6.1 in one Controller violates that rule. Feature dependencies in §4 still need checking. BT-CSS-HISTORY, BT-CONFIG.

Reading task: draw the arrow and write “requires,” “amends,” “tests,” or “explains.” Do not infer that two independently adopted specifications are compatible merely because one is newer. Preserve the evidence that established the old pair so a later reviewer can see what actually changed.

Static broken / repair examples

Trace an RF number with its conditions

Where exactly does an RF number begin and end?

The quantity and its conditions travel together. Channel spacing is not occupied bandwidth; a receiver input criterion is not an OTA distance. Look up the selected mode and test definition before moving a value into the product budget. R1 is a component RF port, R2 the antenna feed, S0 the spatial/OTA reference, and R3 the receiver decision boundary. An antenna connector in a source must be mapped to the actual test fixture; it is never automatically R3.

GFSK is Gaussian frequency-shift keying. Its dimensionless shaping product BT uses Gaussian-filter bandwidth B in hertz and symbol interval T in seconds. That filter parameter does not name the occupied RF bandwidth. The timing symbol T_MAFS below denotes minimum auxiliary frame space, an interval at the packet boundary.

BT-RF: actual normative text read; BT-LL: actual timing definition read. This is a small set of annotations, not a reproduction of the standard’s tables.

Checked comparison: the fictional vendor’s −96 dBm result and the −70 dBm requirement cannot be subtracted into a 26 dB “product range margin” until their mode, signal, criterion and planes match. Even then, the difference would be a conducted receiver comparison. Feed, antenna and channel evidence would still be needed to connect it to D0.

The separately curated real trace

Engineering handoff: preserve the original source plane and explicitly name every feed, mismatch, gain or processing transformation. Count each loss once. RF output power and DC energy are different quantities; a conducted limit does not become EIRP by changing its label.

Connect PHY claims to MAC and state behavior

If 256 payload bits take little PHY time, why might the gateway miss a two-second deadline?

The receiver must be listening to the right transmission. Discovery, scan scheduling, host queues, access collisions and retransmission policy all sit between the PHY and delivered service. Aggregation can reduce overhead per report while increasing the time a report waits. Adaptation changes the selected operating point. A fixed nominal rate cannot describe those states.

For this variant, extended advertising carries the report in an auxiliary PDU. The selected non-scannable mode does not request a scan response; repeated broadcasts are not acknowledged application delivery. Commissioning is a separate state. Read the PDU/event conditions in Core 6.2 Vol 6 Part B §§2.3.1.6 and 2.3.4 and the host format in GAP §11 before borrowing timing from a connection. BT-LL, BT-GAP.

At one complete report per 60 s, the offered D0 rate is 256/60 = 4.2667 bit/s, independent of whether the receiver succeeds. Actual goodput is unique delivered D0 bits divided by the declared observation interval. The 99% deadline target is a different statistic again. A short payload does not prove low energy or reliable discovery.

Separate qualification from market authorization

What does the qualification record leave for the product team to do?

Keep parallel evidence lanes. A qualification record identifies a program submission; a module note describes an implementation; a host change alters the product configuration; a regulator’s requirements address a market. Match identities within each lane and record the joins. A familiar logo cannot fill missing rows.

QPRD v5’s test-plan process uses the declared Implementation Conformance Statement (ICS) and Test Case Reference List (TCRL) package. The executed plan depends on the design and changes being submitted. Core 6.2 Vol 6 Part F §1 explains RFPHY test-control alternatives; it is not a completed device test report. BT-QPRD §§3.2.2.4–3.2.2.5, BT-DTM.

Reading task: cross out the sentence “qualified therefore legal everywhere” and replace it with two evidence requests. OFCOM’s overview explicitly concerns applicable requirements and distinguishes its telecommunications scope from other legislation. No CH limit or authorization is inferred here. CH-OFCOM, 16 January 2025.

Review changes without rewriting history

A new version appears. Which conclusions actually need reopening?

Publication records when a document was issued; adoption records a publisher’s approval status. Supersession, deprecation and withdrawal describe distinct lifecycle events under the relevant policy. Access records when a reader obtained the source; review records when the claim was assessed and when to revisit it. Do not collapse those dates into “latest.”

On 8 September 2026, the official index listed Core 6.3 as adopted and still listed Core 6.2. The selected 6.2 page identifies Expedited Specification Update 28108 as required when claiming 6.2 compliance. Its download and the RFPHY TS p22 download returned landing pages in this research session; the underlying text was not read. Their detailed applicability stays unresolved, even though the public notice and Core text were read. BT-INDEX, BT-UPDATE, BT-TS.

Change task: suppose the firmware owner enables a different advertising mode. Reopen packet-format, gateway capability, timing/current and relevant test claims. An enclosure change instead reopens antenna/OTA evidence and integration applicability. Keep the old reviewed card as history and issue a named variant; do not make every earlier product invalid by declaration.

Complete and audit the evidence card

Can another engineer reconstruct both your conclusion and your next evidence request?

A useful audit makes three things visible: what is supported, the conditions under which it is supported, and the next unresolved decision. Start with the eight flawed statements below. Rewrite each before opening the answers; preserve any supported part rather than rejecting the entire source.

One completed authoritative definition trace: BT-CHANNEL → Core 6.2 identity → Vol 6 Part A §2 → forty channel centers with the stated spacing → arithmetic check in Section 6. This supports a channel-definition annotation for the selected LE mode. NODE-DELIVERY still needs a representative mounted trial; NODE-MARKET still needs an authoritative applicability review. The trace is complete for that definition, not for product conformance.

Handoff to 07.2: compare short-range candidates using this same D0 service definition. Carry the unresolved scan schedule, schema, gateway capability, current trace and market questions with their owners. Changing a number or checking a box cannot manufacture the missing evidence.