A distributed spectrum monitoring system

Slides:



Advertisements
Similar presentations
Outdoor Use Case Date: Authors: November 2005 January 2995
Advertisements

[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
IEEE WG Status Report – July 2005
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
TV White Space Coexistence Plan
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
November Opening Report
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
(Presentation name) For (Name of group) (Presenter’s name,title)
IEEE P Motions July Plenary EC Closing Meeting
TGp Motions Date: Authors: November 2005 Month Year
March Opening Report Date: Authors: March 2010
TGp Closing Report Date: Authors: March 2006 Month Year
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Contribution on Location Privacy
IEEE WG Opening Report – March 2007
November Opening Report
On Coexistence Mechanisms
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGu Timeline Date: Authors: January 2005 January 2005
TGv Redline D0.06 Insert and Deletion
Experimental DTV Sensor
IEEE WG Opening Report – July 2008
ADS Study Group Mid-week Report
IEEE P Wireless RANs Date:
Spectrum Sensing Tiger Team
TGu-changes-from-d0-01-to-d0-02
September Opening Report
LB73 Noise and Location Categories
Addressing White Spaces Across all of IEEE 802
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
IEEE WG Opening Report – July 2007
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
November Opening Report
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
Advanced Beaconing Schedule and Timelines
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

A distributed spectrum monitoring system March 2015 doc.: IEEE 802.22-16/0005r0 November 2016 A distributed spectrum monitoring system Authors: Name Company Address Phone email Roger Hislop Internet Solutions 57 Sloane St Bryanston +27115751000 roger.hislop@is.co.za Notice: This document has been prepared to assist IEEE 802.22. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.22. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures http://standards.ieee.org/guides/bylaws/sb-bylaws.pdf including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair Apurva Mody <apurva.mody@ieee.org> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.22 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at patcom@iee.org. SCOS Task Group Roger Hislop, Internet Solutions

November 2016 SCOS Architecture SCOS task group

November 2016 Detail of SSD SCOS Task Group

November 2016 Detail of SSM and Users SCOS Task Group

November 2016 Message Flow SCOS Task Group

Fundamental Design Considerations November 2016 Fundamental Design Considerations The main area of focus is how we abstract the layers between user, sensor management, sensor device, and sensed data. The intention is to make it very flexible, and use as much of the tech that’s already well developed: Distributed/Cloud-based data storage and processing Ubiquitous public shared networks (Internet, GSM) Low cost open computer platforms Low cost RF receivers and SDRs SCOS Task Group

Put as much in the Cloud as possible November 2016 Put as much in the Cloud as possible Every part of the architecture can be hosted on a VM or even Code-as-a-Service – apart from the sensing front end itself. The sensor could be a simple embedded device that meets basic requirement of standard... …or better, it should contain a computing platform (e.g. Linux-based computer board) that allows on-the-fly changes in sensor capabilities (e.g. pushing a processing algorithm to it) and autonomous activity SCOS Task Group

November 2016 Design Thinking We have no idea how the hardware tech will develop –SDRs, antenna, processing power of devices… or the use cases and user requirements. The intent of the standard is to not enforce sensing hardware capabilities. Collect data as to when and how sensing was done, the user must interpret it. All scans have associated metadata describing the requestor, device capabilities, current configuration, environment, etc. Sensing hardware capabilities reported in discovery process` to user. User decides on scan type/schedule, and requests it to be done. This “package” of scan data + metadata is sent to a data store(s) – where user retrieves it and interprets. SCOS Task Group

Purpose Regulation/enforcement activities November 2016 Purpose Regulation/enforcement activities Interference detection, classification, location Drive low cost sensing into White Space radio/CR Spectrum planning SCOS Task Group

November 2016 Where P1900.6 group can help There are people in this group that could bring a lot to the table in this new IEEE 802 standard: Distributed, future proof: Defining APIs, making the architecture Cloud-centric Mass deployment: Understanding parameterising the tech of low cost sensor hardware Consistency in metrics: Ensure the data collected allows users to compare apples and apples, and what kind of apples they’re getting. SCOS Task Group

Thank you roger.hislop@is.co.za November 2016 Thank you roger.hislop@is.co.za SCOS Task Group