150 likes | 307 Views
Spectrum sharing and information architecture. Martin BH Weiss mbw@pitt.edu. Outline. Context White Spaces Federal Commercial sharing Discussion and conclusions. Motivation for spectrum sharing. 2013. 2005. Motivation for spectrum sharing. Factors affecting sharing.
E N D
Spectrum sharing and information architecture Martin BH Weiss mbw@pitt.edu
Outline • Context • White Spaces • Federal Commercial sharing • Discussion and conclusions
Motivation for spectrum sharing 2013 2005
Factors affecting sharing • Interference is inevitable when spectrum is shared, so how is risk managed? • Sensing • Enforcement • How are various spectrum related rights defined (and managed)?
Some current US spectrum sharing initiatives • Commercial • TV White Spaces • Federal-commercial • 1695-1710 MHz • 1755-1850 MHz • 3550-3600 MHz
Case 1: TV White Spaces • What are spectrum “white spaces”? • What does this have to do with television?
Sharing TV White Spaces • What do you need to know? • What are approaches to finding the information you need? • Sensing • Databases
What does the TVWS database look like? • Let’s look at examples • http://whitespaces.spectrumbridge.com/whitespaces/home.aspx • http://www.google.org/spectrum/whitespace/
Content • What information is provided? • How would you use it?
Case 2: Federal and Commercial sharing • 1695-1710MHz • Currently assigned to weather satellite downlinks • Satellites are in polar orbit • Proposed for LTE uplinks, probably paired with the 2180-2200 MHz band for the downlink
Challenge • How do you protect the “incumbents”?
Exclusion zones • Static • Dynamic
Operations of database-driven spectrum sharing • Assuming you have a need to establish a communication network, you must … • Find out where you are • Find out what channels you can use • Determine when you can use them at that location • Determine if those channel characteristics are suitable for your application • Transmit and follow the requirements of channel use
Web interfaces for spectrum sharing in general • What needs to be in the database? • How context-specific is the information? • Who needs to see it? • How do you design it for human and machine users?