Skip to content
Anthony Romaniello edited this page May 10, 2024 · 15 revisions

SCOS Sensor is a work-in-progress reference implementation of the IEEE 802.15.22.3 Spectrum Characterization and Occupancy Sensing sensor, developed by the Institute for Telecommunication Sciences (ITS), the research and engineering arm of the National Telecommunications and Information Administration (NTIA). SCOS Sensor implements a RESTful API which allows authorized users to discover a sensor's capabilities, schedule actions, and acquire resultant data.

Introduction

SCOS Sensor was designed by NTIA/ITS with the following goals in mind:

  • Easy-to-use sensor control and data retrieval via IP network
  • Low-cost, open-source development resources
  • Design flexibility, to allow developers to evolve sensor technologies and metrics
  • Hardware agnostic
  • Discoverable sensor capabilities
  • Task scheduling, using start/stop times, repeat intervals, and/or task priority
  • Standardized metadata/data format that supports cooperative sensing and open data initiatives
  • Security controls to prevent unauthorized users from accessing sensor functionality
  • Easy-to-deploy with provisioned and configured OS
  • Quality assurance of software via automated testing prior to release

Read more about the overall design of SCOS on the Overview wiki page.

Getting Started

A recommended starting point is Tutorial 1, which will guide you through getting SCOS Sensor up and running locally on your computer. This tutorial uses a mock signal analyzer, so no sensor hardware is required. Once you've got up and running, read further on the wiki about Configuring SCOS Sensor and Hardware Support. If you're interested in contributing to SCOS Sensor, check out the Development Guide for relevant information.

References

License

View the SCOS Sensor license: LICENSE.md

TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.

Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.

Disclaimer

Certain commercial equipment, instruments, or materials are identified in this project were used for the convenience of the developers. In no case does such identification imply recommendation or endorsement by the National Telecommunications and Information Administration, nor does it imply that the material or equipment identified is necessarily the best available for the purpose.

Clone this wiki locally