Zum Hauptinhalt springen

ZeqPropagation — RF Path Loss

Spectrum, modulation, channel coding, antenna.

  • Protocol ID — zeq-propagation
  • Category — Telecom
  • Endpoint — POST /api/telecom/propagation
  • Auth — api-key
  • Rate limit — 30/min
  • Version — 1.0
  • Precision — ≤0.1% (KO42-enforced)

What it does

RF propagation modeling using electromagnetic operators. Free-space path loss, atmospheric absorption, and multipath fading computed from first principles.

Signature

Request

POST /api/telecom/propagation
ParamTypeRequiredDefaultDescription
frequencyMhznumberOperating frequency.
distanceKmnumberPath distance.
environmentstring"free-space"'free-space', 'urban', 'suburban', 'indoor'. Default: 'free-space'.

Response

{ pathLossDb, receivedPowerDbm, fresnelRadius, fadeMargin, linkBudget }

Runnable example

curl -sS -X POST \
-H "Authorization: Bearer $ZEQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"frequencyMhz": 0,
"distanceKm": 0,
"environment": "free-space"
}' \
"https://api.zeq.dev/api/telecom/propagation"

Integrate

  1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
  2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
  3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

  • Near — wrap /api/telecom/propagation in a language SDK so builders can call it in three lines.
  • Medium — publish a reference integration demonstrating ZeqPropagation — RF Path Loss alongside a real workload, with pulse-aligned metrics.
  • Far — propose ZeqPropagation — RF Path Loss as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.