CRO / cogradio.org

Cognitive Radio Ontology · Version 2

A common language for autonomous radios

If wireless devices are to communicate and interoperate autonomously, they first need to speak a common language. CRO2 is that language: a formal, machine-interpretable model of radio capability — so that devices can negotiate interoperability rather than be configured into it.

157CRO2 classes
62Object properties
13NuVio core classes
OWL 2Representation

Architecture

Three layers, each replaceable

CRO2 does not define the world from scratch. It specializes NuVio, a small domain-independent foundation, and is in turn specialized by extensions for particular radios and interfaces.

EXTENSIONS · OPTIONAL FM3TR41 classes TransmitterAPI8 classes both marked incomplete owl:imports CRO2 · COGNITIVE RADIO DOMAIN · 157 CLASSES · 62 RELATIONS 24 Channel Component Network Agent … and 20 more 20 Modulation ChannelCoding Protocol Detection … and 16 more 7 Frequency Power Time SignalRate … and 3 more 5 FrequencyUnit PowerUnit TimeUnit … and 2 more 2 DoubleValue LongValue rdfs:subClassOf NuVio · FOUNDATIONAL, DOMAIN-INDEPENDENT · 13 CLASSES Object Process Quantity UnitOfMeasure Value All descend from Entity. Also defined: Attribute · Quality · Situation · InformationEntity · InformationContent · InformationRepresentation · DimensionlessUnit
The Quality / Quantity split under Attribute is what CRO2 gained over CRO1. A quantity carries a value and a unit of measure, so a reasoner can check that a declared transmit power falls inside a transmitter’s stated range, and convert between dBm and mW, without being told how in advance. Counts are read from the published OWL files.

What it is for

Describing capability

State what a radio can do — frequencies, power, modulations, protocols — in a form another machine can read and reason over rather than parse and hope.

Negotiating interoperability

Two nodes that share the ontology can establish what they have in common at run time, instead of relying on a configuration agreed months earlier.

Interpreting policy

Spectrum access policies expressed against the same vocabulary become machine-checkable, which is what IEEE 1900.5 set out to standardize.