--- title: "Spectrum monitoring and interference | Nexus Observatory" description: "Every radio service depends on clean spectrum. Monitoring receivers with GNSS timing measure occupancy, detect interference and locate its source…" url: https://observatory.global/industries/telecom/spectrum-monitoring/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Telecom](https://observatory.global/industries/telecom/) / [Specialized fields](https://observatory.global/industries/telecom/fields/) / **Spectrum monitoring and interference** # Spectrum, watched for what should not be there. Every radio service depends on clean spectrum. Monitoring receivers with GNSS timing measure occupancy, detect interference and locate its source, reporting to one record that regulators and operators use to plan bands, resolve complaints and protect safety services. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Telecom **Measurements**: 5 **Sources cited**: 3 1. Telecom · Spectrum monitoring and interference Clean spectrum is invisible until it is not Mobile networks, aviation radios and satellite links all assume clean spectrum. A faulty transmitter or an illegal jammer can degrade a band across a city or a region. Finding the source quickly, and knowing how bands are really used, depends on a network that listens continuously and shares precise time. 2. What is measured Occupancy, parameters, direction and time Fixed monitoring receivers scan bands for occupancy and detect signals that should not be there. They measure each signal's parameters, direction-finding antennas give its bearing, and GNSS-disciplined time lets several stations compare arrival times. Mobile units close in for the final search. InstrumentsMonitoring receivers · Direction-finding antennas · GNSS time references · Mobile units 3. The base node Every detection on the same clock Each station's node scans its bands, matches detections against the licence database, measures parameters and bearing, and time-stamps every detection against GNSS, so stations can locate a source together. Every measurement is signed for the case record. Timing faults are flagged at once. 4. Radio and links Fibre, cellular and the field Fixed stations on buildings with fibre send scans and detections home with low delay. Stations without fibre, and mobile units in the search, report over cellular, and remote stations protecting aviation or satellite bands report by satellite. Each path is supervised. LinksFibre · Public cellular · Satellite 5. How it works From a complaint to a switched-off jammer An operator reports interference in its band. Three stations detect the signal, measure bearings and time differences, and the network locates it to a few streets. A mobile unit finds a faulty device, the owner switches it off, and the case closes with the measurements. 6. From order to operation · Order Scope the bands and the area The scope reads the bands to protect, the interference history, the existing monitoring network and the licence database. Nexus Observatory Inc. returns the station plan for coverage and location geometry, the timing design, the integration with case management and a price per station and per year. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Measure the noise floor first Crews survey candidate sites with a portable receiver to measure the local noise floor and nearby strong transmitters, check views across the area, GNSS sky view, power and fibre or cellular. Sites are chosen so that several stations see every point for location. 8. From order to operation · Permits Sites and the regulator Hosts agree to antennas on their buildings or masts, and masts follow planning rules. Monitoring is operated under the regulator's authority or the operator's licence, and the handling of measured signals follows the rules on privacy of communications. Every agreement is kept. 9. From order to operation · Build Build and synchronise Receivers, antennas, GNSS references and nodes are built, calibrated and enrolled with their identities. Each station is configured with its bands and the licence database, and timing is checked against a common reference before shipping. Configurations are tested together on the bench before stations ship. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install for geometry Crews mount antennas with clear views, GNSS antennas with open sky, and receivers and nodes indoors with fibre or cellular. Each station's position and antenna orientation is surveyed, because location accuracy depends on them. Lightning protection is fitted at every mast, and cables are protected. 11. From order to operation · Commission Locate a known transmitter Each node proves its identity. Receivers are checked with a reference signal, timing compared across stations, and a known test transmitter is located by direction finding and time difference. The network joins the regulator's case system when the location is right. 12. From order to operation · Operate Find it, then fix it Engineers see occupancy across bands for planning, and when an interference complaint arrives, the network detects the signal, locates it to an area and sends a mobile unit for the final search. Every case is kept with its measurements until it is closed. 13. From order to operation · Maintain Keep the timing and the database true Stations are checked on schedule against reference signals, timing verified against GNSS, antennas inspected after storms, and the licence database kept current. Every change is recorded, so measurements stay comparable for planning and cases. Spares are kept ready, so a failed station is restored quickly. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For planners, regulators and operators Spectrum planners receive occupancy reports; regulators and network operators receive interference detections with location; licensing teams receive compliance measurements; enforcement teams receive case records. Each product carries its station, calibration and time. Reports are dated and versioned, and each case keeps its measurements until it closes. [See the data products](https://observatory.global/data-products/) 15. Evidence Cases that close on evidence Every scan, detection, location and case step is signed and kept. Monitoring follows the ITU handbook, operation follows the radio regulations and the European electronic communications rules, and timing is traceable to GNSS, so cases close on evidence that stands up. Drawn againstITU Handbook on Spectrum Monitoring · ITU Radio Regulations · Directive (EU) 2018/1972 16. What you get Spectrum and RF monitoring RF sensing in the band for interference, coexistence and spectrum planning. Delivered as managed service and data licence, for carriers, regulators, airports, venues. Scale: Regional. Service levels are written as numbers you can measure on your own dashboard. The same design repeats from the first site to the last. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan spectrum monitoring and interference with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for spectrum monitoring and interference. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace. [Plan a deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) **01** The place and its hazards ## Where it runs, and what can go wrong. Operating contextSpectrum regulators monitor the radio spectrum to check compliance, measure occupancy for planning and resolve interference to licensed services, following international guidance. Operators of mobile, satellite and safety networks need interference found quickly. Locating a source uses direction finding or time difference of arrival, which needs precise, shared time. Hazards - Interference to safety and aviation services - Interference degrading mobile networks - Unlicensed and faulty transmitters - Planning decisions without occupancy data - Sources that move or transmit briefly **02** What must be measured ## What, where, how often, and under which rules. Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below. | Measurement | Where | Cadence | Sources | | --- | --- | --- | --- | | Spectrum occupancy | Fixed monitoring stations across the area | Continuous scans across bands | 1 | | Signal parameters | Fixed and mobile receivers | On detection | 1 | | Direction of arrival | Direction-finding stations | On detection | 1 | | Time difference of arrival | Time-synchronised receivers | On detection | 1 | | Compliance with licence conditions | Licensed transmitters | On schedule and on complaint | 23 | **03** The observation stack ## From one base unit to a network. The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol. 1. **01** Base unit A monitoring station: a receiver and antennas with a GNSS time reference, read by an edge node that processes and signs every measurement. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site An area: fixed stations placed for coverage and geometry, with mobile units for the final search. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every station of a regulator or operator run as one fleet, with one record. [Managed offers →](https://observatory.global/industries/telecom/solutions/) 4. **04** Network Regulators and operators exchange measurements and interference cases through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** GNSS reference station (RTK) - **02** Edge node (Wedge) - **03** Fibre terminal - **04** Cellular modem/router - **05** Telescopic mast Radio and links ### Fibre Fixed stations on buildings with fibre send scans and detections home with low delay. Radio and links ### Public cellular Stations without fibre, and mobile units in the search, report over cellular. Radio and links ### Satellite Remote stations protecting aviation or satellite bands report by satellite. Edge computeEach station's node scans bands, detects signals that do not match the licence database, measures their parameters and direction, and time-stamps every detection against GNSS so stations can locate a source together. PowerStations run on building power with batteries; remote stations on solar. **04** How it works ## From the instrument to the product. One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks. Spectrum monitoring and interference: data path – of 06 01 Instruments Measurement with sensor identity andcalibration 02 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 03 Backhaul Commit with transactional outbox andpublish, delivered at least once 04 Site Consumer inbox deduplicates and applieseach record once into governed data 05 Data store Governed product through API, map orexport, correction-aware 06 Products ITU Handbook on Spectrum MonitoringOGC SensorThings APINTP and PTP 07 Power and structure Monitoring receivers anddirection-finding antennas Not in the reference kit 01 GNSS reference station (RTK) Ethernet · GNSS antenna · RS-232 ·1PPS/10 MHz 02 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 03 Fibre terminal Fibre · Ethernet 04 Cellular modem/router Ethernet · USB · RS-232 Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Spectrum occupancy reports Interference detections with location Compliance measurements Case records 05 Telescopic mast Ethernet Ethernet Fibre Ethernet Fibre LTE/NR From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation. | Item | Equipment | Data ports | Protocols | Power in | | --- | --- | --- | --- | --- | | 01 | **GNSS reference station (RTK)** Multi-constellation GNSS base station that streams corrections for real-time kinematic positioning. | EthernetGNSS antennaRS-2321PPS/10 MHz | NMEA 0183, NTP with NTS | 12 V DC | | 02 | **Edge node (Wedge)** Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains | | 03 | **Fibre terminal** Optical network terminal or media converter that lands fibre backhaul at a site. | FibreEthernet | IEEE 1588 PTP | 12 V DC, 48 V DC, AC mains | | 04 | **Cellular modem/router** LTE or NR modem or router that uses a public carrier or private network as backhaul. | EthernetUSBRS-232 | 3GPP E-UTRA air interface, 3GPP NR air interface, OMA LwM2M | 12 V DC, PoE | | 05 | **Telescopic mast** Pneumatic or winch telescopic mast on a trailer, vehicle or base. | — | — | — | How it scales 01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces. SITE Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality. CLUSTER ×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites. FLEET Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts. TRUST DOMAIN TRUST DOMAIN TRUST DOMAIN ×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding. **Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. **Telemetry**: OpenTelemetry OTLP. **Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. **Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. **Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. **Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. **Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. **05** From order to operation ## Every step, from the first call to a running site. The same crew and the same record carry the work from scope to maintenance. 1. 01 Order Scope the bands and the area The scope reads the bands to protect, the interference history, the existing monitoring network and the licence database. Nexus Observatory Inc. returns the station plan for coverage and location geometry, the timing design, the integration with case management and a price per station and per year. 1 2. 02 Survey Measure the noise floor first Crews survey candidate sites with a portable receiver to measure the local noise floor and nearby strong transmitters, check views across the area, GNSS sky view, power and fibre or cellular. Sites are chosen so that several stations see every point for location. 3. 03 Permits Sites and the regulator Hosts agree to antennas on their buildings or masts, and masts follow planning rules. Monitoring is operated under the regulator's authority or the operator's licence, and the handling of measured signals follows the rules on privacy of communications. Every agreement is kept. 4. 04 Build Build and synchronise Receivers, antennas, GNSS references and nodes are built, calibrated and enrolled with their identities. Each station is configured with its bands and the licence database, and timing is checked against a common reference before shipping. Configurations are tested together on the bench before stations ship. 5. 05 Install Install for geometry Crews mount antennas with clear views, GNSS antennas with open sky, and receivers and nodes indoors with fibre or cellular. Each station's position and antenna orientation is surveyed, because location accuracy depends on them. Lightning protection is fitted at every mast, and cables are protected. 6. 06 Commission Locate a known transmitter Each node proves its identity. Receivers are checked with a reference signal, timing compared across stations, and a known test transmitter is located by direction finding and time difference. The network joins the regulator's case system when the location is right. 7. 07 Operate Find it, then fix it Engineers see occupancy across bands for planning, and when an interference complaint arrives, the network detects the signal, locates it to an area and sends a mobile unit for the final search. Every case is kept with its measurements until it is closed. 13 8. 08 Maintain Keep the timing and the database true Stations are checked on schedule against reference signals, timing verified against GNSS, antennas inspected after storms, and the licence database kept current. Every change is recorded, so measurements stay comparable for planning and cases. Spares are kept ready, so a failed station is restored quickly. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Spectrum occupancy reports** Spectrum planners - **Interference detections with location** Regulators and network operators - **Compliance measurements** Licensing teams - **Case records** Enforcement teams Integration - **Licence database** Detections are matched to licensed transmitters automatically. - **Interference case management** Detections and locations open and update cases. - **Operators' network management** Operators receive interference events affecting their bands where agreed. Exchanged through ITU Handbook on Spectrum Monitoring, OGC SensorThings API, NTP and PTP. **07** Questions buyers ask ## Before you scope it. Does monitoring record communications? It measures signals and their parameters; handling follows the rules on privacy of communications. How precise is location? It depends on station geometry and timing; the final search uses mobile units. Can operators use it? Yes, for their own bands, with the regulator where it leads. Why GNSS timing? Locating by time difference needs every station on the same precise time. **08** Resources ## The sources behind this page. Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does. 1. **1** [Handbook on Spectrum Monitoring](https://www.itu.int/) International Telecommunication Union · 2011 2. **2** [ITU Radio Regulations](https://www.itu.int/) International Telecommunication Union 3. **3** [Directive (EU) 2018/1972 establishing the European Electronic Communications Code](https://eur-lex.europa.eu/) European Union · 2018 **09** Related ## Use cases and solutions. [Solution Spectrum and RF monitoringRF sensing in the band for interference, coexistence and spectrum planning.Solutions for telecom →](https://observatory.global/industries/telecom/solutions/#rf-spectrum) [Solution Timing and positioning integrityPTP grandmasters with GNSS holdover, interference detection and timing monitoring for networks and instruments.Solutions for telecom →](https://observatory.global/industries/telecom/solutions/#timing-positioning) **10** Telecom: specialized fields ## Other fields of this industry. [Specialized field Mobile network sitesPower and batteries, shelter climate, tower movement, intrusion and site weather at every mobile site, with an out-of-band path that reports when the site itself is down.The full field →](https://observatory.global/industries/telecom/mobile-sites/) [Specialized field Fibre networks and outside plantDistributed fibre sensing along routes, flooding and gas in chambers, and cabinet access and climate, on LoRaWAN and the fibre itself, so dig-ins and faults are found before the cable is cut.The full field →](https://observatory.global/industries/telecom/fibre-networks/) [Specialized field Edge data centresPower and energy, cooling and air, leaks and vibration in edge and regional data centres, on an industrial network behind a security gateway, with efficiency indicators to the standard.The full field →](https://observatory.global/industries/telecom/edge-data-centres/) [Specialized field Satellite ground stationsRain, wind and lightning at the antennas, antenna drive condition, timing and site security at satellite ground stations, on the site's fibre, so passes are planned around the weather and faults are caught between passes.The full field →](https://observatory.global/industries/telecom/ground-stations/) ### Bring us the site. Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details. [Plan a deployment](https://observatory.global/contact/deployment/) [Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) [Request a quote](https://observatory.global/contact/hardware-quote/) [Nexus Observatory](https://observatory.global/)**Telecom** . Towers that compute, sense and connect.[Talk to us](https://observatory.global/contact/) Telecom - [Overview](https://observatory.global/industries/telecom/) - [Explainer](https://observatory.global/industries/telecom/explainer/) - [Specialized fields](https://observatory.global/industries/telecom/fields/) - [Use cases](https://observatory.global/industries/telecom/use-cases/) - [Solutions](https://observatory.global/industries/telecom/solutions/) - [Platforms](https://observatory.global/industries/telecom/platforms/) - [Resources](https://observatory.global/industries/telecom/resources/) - [Contact](https://observatory.global/industries/telecom/contact/) Platforms - [Observatory Protocol](https://observatory.global/protocol/) - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Open governance](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/)