BioVerity Communications & Endpoint

The intelligence layerthat connects the device to the world.

BioVerity custom firmware links sensing, local memory and wireless communications, allowing an individual sample to build and forward its digital record as communications opportunities are encountered.

What BioVerity provides

The firmware and communications layer.

ONiO provides the ultra-low-power processing and wireless platform. BeFC provides the thin energy layer. BioVerity provides the custom firmware that coordinates device identity, sensing, local storage and transmission, together with the endpoint architecture that turns received observations into an individual sample record.

Rather than placing conventional tracking infrastructure on every label, BioVerity is designed to use compatible communications opportunities already present across the surrounding IoT environment.

No GPS/GNSSreceiver on the label
No SIMin each sensing label
No cellular modemon the label
No dedicated gateway networktravelling with the sample
Sense → Store → Discover → Forward → Reconstruct

Connectivity is an opportunity, not a prerequisite for sensing.

01 · Sense

Observe

Capture configured measurements such as temperature and associate them with the unique sample identity.

02 · Store

Preserve

Retain timestamped observations in local non-volatile memory while communications are unavailable.

03 · Discover

Listen

Identify compatible communications opportunities encountered within the surrounding IoT environment.

04 · Forward

Upload

Forward current and stored observations when a compatible path to the endpoint becomes available.

05 · Reconstruct

Build the record

Associate received observations, timestamps and observed location events with the individual sample.

Custom device firmware

Coordinates sensing intervals, memory, device state, identity and wireless behaviour so the electronics operate as one sample-level sensing system.

Observed location

Location does not require GPS on the label. It can be associated with a communications observation when compatible infrastructure detects the label at a known or resolvable location.

Endpoint integration

Device identity, timestamps, sensing data and observation events are normalised and associated with the individual sample record at the endpoint.

Store-and-forward resilience

No communications nearby? The sensing record continues.

The label is designed to continue its configured sensing and retain observations locally when compatible communications infrastructure is unavailable. When connectivity is encountered later, stored observations can be forwarded to the endpoint, preserving the history accumulated during the offline period.

ConnectedCurrent observations can be forwarded.
DisconnectedSensing continues and observations remain stored locally.
ReconnectedStored observations are uploaded and incorporated into the sample record.
Architecture status: Actual coverage, observation frequency, location availability and upload latency depend on compatible communications infrastructure being encountered, network availability, device configuration and the final production implementation.
← Back to Partners