Blog

Accept encrypted advertising through three separate gates: select authorized candidate key material, authenticate and parse the protected payload, then apply the product’s freshness policy. Successful decryption does not tell the receiver that an old authentic advertisement represents the broadcaster’s current state. Applicability: Core Supplement v12 Encrypted Data format, Bluetooth Core 6.1 GAP key-material procedure and…

Choose advertising mode from the interactions the product requires. Extended advertising cannot be both connectable and scannable. A design that depends on a scan response and a connection from the same extended set therefore needs revision before payload construction or radio tuning begins. Applicability: Bluetooth Core 6.1 advertising properties and Zephyr v4.2.0 extended-advertising APIs. This…

Admit advertising roles through a resource ledger with explicit priority and rollback. A controller’s supported-set count is not a guarantee that every proposed combination can be scheduled, and a stopped set is not necessarily a freed set. Track object ownership, controller configuration and radio activity separately. Applicability: Bluetooth Core 6.1 extended-advertising HCI and Zephyr v4.2.0…

Validate the IQ acquisition record before evaluating an angle estimator. Confirm the CTE type, sample format, packet status, reference-sample boundary and physical antenna sequence. Then verify the coordinate transform separately. A plausible angle can survive several mapping errors while pointing in the wrong direction. Applicability: Bluetooth Core 6.1 connectionless CTE IQ reports and Zephyr v4.2.0…

A product distance result should be a qualified estimate with provenance, not a floating-point number detached from its radio evidence. Establish supported roles and modes, collect matching results from both peers, preserve incomplete and aborted outcomes, and identify the estimator and calibration that produced the estimate. Applicability: Bluetooth Core 6.1 Channel Sounding and the Zephyr…

Decode power and path-loss reports into a connection-scoped evidence ledger before allowing them to drive adaptation. A new callback does not necessarily contain a new radio measurement, and an unavailable value must never become a large numeric path loss. Establish controller ownership of power changes before adding another control loop. Applicability: Bluetooth Core 6.1 connected…

Select LE Coded from measured delivery and airtime under the same workload, not from a nominal range multiplier. First prove that the connection uses LE Coded in the intended direction. Then establish which coding scheme the transmitter actually used; requesting S=2 or S=8 does not make that preference a per-packet guarantee. Applicability: Bluetooth Core 6.1…

Prove two different transitions: additional activity permitted by continuation events, and a negotiated change of subrate parameters. Neither should be inferred from a successful request call. Record the effective factor and completion status, then measure the first useful application response from several arrival phases in the idle schedule. Applicability: Bluetooth Core 6.1 and Zephyr v4.2.0,…

PAwR fits a sensor product only when three budgets agree: each device owns a defined response opportunity, its packet fits that opportunity, and the host supplies the response before the controller’s deadline. A schedule with enough numbered slots is necessary but does not establish reliable reporting or application freshness. Applicability: this analysis pins Bluetooth Core…