Observatory ProtocolNode registryLoRaWAN end device
LoRaWAN end device
A 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.
- 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
Role
A node may speak LoRaWAN through a connector. (OBSP 0.1 §5.5) The field data plane names connectors for LoRaWAN. (OBSP 0.1 §6) Every sensor has a sensor passport. (OBSP 0.1 §5.3)
- Class
- Radio access and low-power networks
Devices and radios that reach the grid over cellular, low-power wide-area or mesh links. - Protocol role
- Not a protocol role of its own: the specification reaches LoRaWAN through a connector on a node.
- Conformance profile
- Its readings enter through the OBSP-NODE profile of the gateway node that runs the connector. A sensor passport describes the device.
- Technology domains
- IoT and low-power wireless
Interfaces
The planes and bindings this type uses. Bindings are normative for OBSP 0.1; radio and link layers follow their own standards. (OBSP 0.1 §6)
| Interface | Binding | Sources |
|---|---|---|
| Radio access | LoRaWAN link layer and regional parameters | (LoRaWAN L2 1.0.4 (TS001-1.0.4); LoRaWAN RP002-1.0.4) |
| Into the grid | A LoRaWAN connector on an IoT gateway node | (OBSP 0.1 §5.5; OBSP 0.1 §6) |
Schemas it emits and accepts
Each document is a JSON Schema 2020-12 contract. Open one in the schema explorer. (JSON Schema 2020-12) Every request, command and event also carries a request context. (OBSP 0.1 §4.3)
Emits
sensor-passportSensorPassportcalibration-recordCalibrationRecordobservation-recordObservationRecord
Accepts
None in OBSP 0.1.
Lifecycle and conformance
Its readings enter through the OBSP-NODE profile of the gateway node that runs the connector. A sensor passport describes the device.
| Clause | Stage | In a profile | Contract |
|---|---|---|---|
| §5.1 | Join | No | Contracted |
| §5.2 | Admit | No | Contracted |
| §5.3 | Describe | No | Contracted |
| §5.4 | Time | No | Contracted |
| §5.5 | Observe | No | Contracted |
| §5.6 | Qualify | No | Contracted |
| §5.7 | Federate | No | Open gap G-FED-1 |
| §5.8 | Orchestrate | No | Open gap G-ORCH-1 |
| §5.9 | Correct | No | Contracted |
| §5.10 | Exchange | No | Open gap G-EXCH-1 |
| §5.11 | Prove | No | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | No | Contracted |
Identity, attestation and security
Requirements of the security model that apply to this role. (OBSP 0.1 §8)
- Architecture
- Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
- Workload identity
- SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
- Supply chain
- SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (OBSP 0.1 §8)
- Privacy
- Observation data that can identify a person is a declared data class with its own policy; default is not to collect it (OBSP 0.1 §8)
Interoperability profile and standards
The primary standards this type draws on. Alignment with a standard is stated as alignment. It is not an approval by the standards body. (OBSP 0.1 §13)
- LoRaWAN L2 1.0.4 (TS001-1.0.4)LoRa Alliance technical specifications(LoRaWAN L2 1.0.4 (TS001-1.0.4))
- LoRaWAN RP002-1.0.4LoRaWAN Regional Parameters(LoRaWAN RP002-1.0.4)
- LoRaWAN TS011LoRaWAN relay specification (LoRa Alliance technical specifications)(LoRaWAN TS011)
Not yet defined
What the protocol does not define for this type in version 0.1, stated as the specification states it. Nothing here is filled in from elsewhere.
- OBSP 0.1 does not define attestation for a device without a node agent. Identity and attestation apply to the node that runs the connector. (OBSP 0.1 §5.1)
Across the consortium
Related pages on the consortium's other networks, in their own words.
- Standards
- Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.Early Warning and Anticipatory ActionHazards and Disaster Risk ReductionCities and the Built EnvironmentCommunities, Learning and ContributionIndustry, Trade and Supply ChainsWater and Food SystemsHumanitarian Action and DevelopmentData and EvidenceClimate and Earth SystemsOpen Infrastructure and Developers
- Index
- Country risk indicators that observations with provenance and quality can inform.risksindex.com
- Academy
- Training for implementers and operators of observing systems.risksacademy.com
- Reports
- Published evidence with provenance, citation and corrections.nexustandards.com/nexus-reports
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- OBSP 0.1 §5.5: Observe Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §5.3: Describe Observatory Protocol 0.1 (draft), CC BY 4.0.
- LoRaWAN L2 1.0.4 (TS001-1.0.4) LoRa Alliance technical specifications resources.lora-alliance.org/technical-specifications Checked
- LoRaWAN RP002-1.0.4 LoRaWAN Regional Parameters resources.lora-alliance.org/home/rp002-1-0-4-regional-parameters Checked
- JSON Schema 2020-12 JSON Schema draft 2020-12 json-schema.org/draft/2020-12 Checked
- OBSP 0.1 §4.3: Request context Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
- LoRaWAN TS011 LoRaWAN relay specification (LoRa Alliance technical specifications) resources.lora-alliance.org/technical-specifications Checked
- OBSP 0.1 §5.1: Join Observatory Protocol 0.1 (draft), CC BY 4.0.