Observatory ProtocolNode registry
Node registry
Every kind of node, device, network and actor the Observatory Protocol 0.1 reaches: its protocol role and interfaces, the schemas it emits and accepts, its conformance profile and lifecycle, its identity and security requirements, and the standards it draws on. Where the protocol does not yet define something, the page says so.
- Version
- 0.1.0-draft
- Status
- Draft specification
- Specification
- CC BY 4.0
- Code
- Apache-2.0
- Steward
- GCRI Canada
- Source
- obsp-0.1-foundation
Browse the node types
Each type is placed by its protocol role and the conformance profile that applies to it. (OBSP 0.1 §3; OBSP 0.1 §7.1) Search by name, standard, interface or schema.
All 22 node types.
| Type | Class | Role | Profile | Schemas |
|---|---|---|---|---|
| Sensor and instrument nodeA device that hosts one or more sensors and runs a conforming node agent. It joins, keeps time and publishes observations with their metadata and quality. | Field devices | NODE | OBSP-NODE | 17 |
| IoT gatewayA node that terminates field buses and low-power radio links and carries their readings to the grid through connectors. It holds a local outbox and publishes at least once with idempotency keys. | Field devices | NODE | OBSP-NODE | 14 |
| 5G NR device or radio nodeA 5G NR user device, radio unit or tower that runs a node agent. The radio itself follows 3GPP. The protocol governs its identity, time, plans and evidence. | Radio access and low-power networks | NODE | OBSP-NODE | 10 |
| LTE-M deviceA licensed cellular IoT device on LTE-M, with mobility and operator-managed security. Power saving mode and extended discontinuous reception set its battery life. | Radio access and low-power networks | NODE | OBSP-NODE | 10 |
| NB-IoT deviceA licensed narrowband cellular IoT device for deep indoor and remote coverage at very low data rates. | Radio access and low-power networks | NODE | OBSP-NODE | 10 |
| LoRaWAN end deviceA long-range, low-power device in licence-exempt bands. It reaches the grid through a LoRaWAN gateway and network server and a connector on a node. | Radio access and low-power networks | No role of its own | None | 3 |
| IEEE 802.15.4 mesh nodeA low-rate wireless node on an IEEE 802.15.4 radio, as used by Thread, Zigbee and Wi-SUN field area networks. Its readings reach the grid through a border router or gateway. | Radio access and low-power networks | No role of its own | None | 2 |
| Satellite terminal (NTN)A node whose upstream link is a satellite, including NR and IoT non-terrestrial networks. It stores and forwards through outages and keeps observations in a local outbox. | Non-terrestrial and Earth observation | NODE | OBSP-NODE | 10 |
| Earth observation sourceA source of satellite or airborne Earth observation data, admitted by source manifest and release, and served onward through catalogues such as STAC. | Non-terrestrial and Earth observation | PROVIDER | OBSP-PROVIDER | 7 |
| Edge compute nodeAn edge computer that runs a node agent and workloads at the site. It applies signed plans in the smallest reversible step and records what it applied. | Compute, relay and control | NODE | OBSP-NODE | 13 |
| Relay nodeA node that extends coverage or carries backhaul for others, such as a LoRaWAN relay or an NR integrated access and backhaul node. | Compute, relay and control | NODE | OBSP-NODE | 7 |
| Site cell controller (hub)The local authority of a site: identity, policy, plan and buffer for its nodes. It runs offline for the autonomy window in the plan and verifies local evidence. | Compute, relay and control | SITE_CELL | OBSP-SITE | 16 |
| Cluster and grid control planeA group of site cells under one operator, sharing fleet, policy and release, and the control plane that serves products through the exchange plane. | Compute, relay and control | CLUSTER | OBSP-GRID | 10 |
| Federation peerA cluster or site cell that exchanges with another trust domain under a federation binding. No binding, no exchange. | Compute, relay and control | FED_PEER | OBSP-GRID | 6 |
| PTP grandmasterThe site's reference clock for the Precision Time Protocol. A node that takes time from it reports the source class PTP and the profile in its time quality record. | Timing sources | No role of its own | None | 1 |
| GNSS timing receiverA satellite navigation receiver used as a time and position source. GNSS alone is not trusted time. Spoofing and jamming indicators lower the reported quality. | Timing sources | No role of its own | None | 1 |
| Authenticated network time (NTS)A network time server that authenticates its responses with Network Time Security, so a node can trust network time without a local grandmaster. | Timing sources | No role of its own | None | 1 |
| Attestation and proof verifierAppraises attestation evidence and proof challenges and issues results bound to a nonce, an expiry and a scope. | Assurance | VERIFIER | None | 5 |
| Data consumer applicationAn application or person reading governed products through the exchange plane, and honouring correction notices on what it has read. | Data consumers | CONSUMER | OBSP-CONSUMER | 4 |
| ProviderA hardware, software, model, data, connectivity or service supplier that enters by manifest for a stated scope and declares a tested exit path. | Operators, providers and stewards | PROVIDER | OBSP-PROVIDER | 8 |
| Grid operatorThe organisation that runs a site cell, cluster or grid and holds its keys. Where it is not the publisher of the software, the operator sovereignty overlay applies. | Operators, providers and stewards | GRID_OPERATOR | None | 5 |
| StewardMaintains the specification and its registers, and runs the open change process. | Operators, providers and stewards | STEWARD | None | 1 |
Classes
The registry groups the types by what they do in a deployment. A class is a reading aid. Conformance is tested against the protocol role and the profile.
- Field devices
- Instruments, sensors and the gateways that carry their readings to a node agent.
- Radio access and low-power networks
- Devices and radios that reach the grid over cellular, low-power wide-area or mesh links.
- Non-terrestrial and Earth observation
- Satellite terminals and Earth observation sources.
- Compute, relay and control
- Edge computers, relays, site cell controllers, clusters and federation peers.
- Timing sources
- The references a node draws its time from. Their quality reaches the grid as time quality records.
- Assurance
- Verifiers that appraise evidence and proof challenges.
- Data consumers
- Applications and people that read governed products.
- Operators, providers and stewards
- Organisations that run deployments, supply components or maintain the specification.
Stages by type
A dot marks a stage of the lifecycle that the type's profile includes. (OBSP 0.1 §7.1) Types with no profile of their own reach the grid through another type.
| Node type | Join | Admit | Describe | Time | Observe | Qualify | Federate | Orchestrate | Correct | Exchange | Prove | Exit and decommission |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sensor and instrument node | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| IoT gateway | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| 5G NR device or radio node | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| LTE-M device | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| NB-IoT device | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| Satellite terminal (NTN) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| Earth observation source | Yes | Yes | Yes | |||||||||
| Edge compute node | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| Relay node | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||||
| Site cell controller (hub) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||
| Cluster and grid control plane | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Federation peer | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Data consumer application | Yes | Yes | ||||||||||
| Provider | Yes | Yes | Yes |
Conformance levels
A level is reached only with the evidence it names; "conformant" describes a tested scope and is never written as certification. (OBSP 0.1 §7.2)
- Declared
DECLARED - Signed self-declaration naming profile, version and scope.
- Self-tested
SELF_TESTED - Conformance report (obsp conformance run) produced by the participant, with digests of the tested artifacts.
- Lab-tested
LAB_TESTED - Conformance report (obsp conformance run) and lab test record from a qualified lab.
- Qualified
QUALIFIED - Lab report plus field observation for the declared scope and a qualification-record.
- Suspended
SUSPENDED - Suspension notice with reason.
- Withdrawn
WITHDRAWN - Withdrawal notice.
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- OBSP 0.1 §3: Participant roles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.1: Profiles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §7.2: Conformance levels Observatory Protocol 0.1 (draft), CC BY 4.0.