Hi,
Not just the spectrum is available in non-contiguous bands, but a whitespace radio with higher bandwidth requirement may use non-contiguous spectrum aggregation, and consume available spectrum across multiple bands too. Thanks and Regards, Sajeev From: [email protected] [mailto:[email protected]] On Behalf Of Vincent Chen Sent: Friday, September 13, 2013 10:03 PM To: Peter Stanforth Cc: [email protected] Subject: Re: [paws] Encoding of spectrum profile Peter, Agreed. So it is important for the protocol to be able to represent discontiguous bands. Thanks. -vince On Fri, Sep 13, 2013 at 9:06 AM, Peter Stanforth <[email protected]> wrote: The US is not unique in having discontinuous bands, we have come across a mix of VHF and UHF channels in a number of countries. From: Vincent Chen <[email protected]> Date: Friday, September 13, 2013 12:00 PM To: Ray Bellis <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [paws] Encoding of spectrum profile Ray, Sorry for the delay in response. My point about being able to represent discontinuities in the frequency range still appears to stand, however. I see. Television channels do not occupy a contiguous range of frequencies. In the US, - [54MHz, 72MHz] Channel 2-4 - [76MHz, 88MHz] Channels 5-6 - [174MHz, 216MHz] Channels 7-13 - [470MHz, 698MHz] Channels 14-51 So the response given by the database should not include any frequencies not in the plan. That means a "spectrum profile" should be encoded as a list of "array" of (frequency, power) points. - Each array represents a "profile" for a contiguous range of frequencies - The range of frequencies within a list of profiles MUST be disjoint and SHOULD be sorted - The entire set of frequency bands defined by the regulatory domain MUST be represented by a single list of "profiles" (rather than split them across multiple lists) That last point is to remove ambiguity and, thus, variations in database implementation, to simplify logic on devices. Example: "spectra": [ { "bandwidth": 6e6, "profiles": [ [ { "freqHz": 5.4e7, "maxPsdDbmPerBw": -56.8 }, { "freqHz": 7.2e7, "maxPsdDbmPerBw": -56.8 }, ], [ { "freqHz": 7.6e7, "maxPsdDbmPerBw": -56.8 }, { "freqHz": 8.8e7, "maxPsdDbmPerBw": -56.8 }, ], [ { "freqHz": 1.74e8, "maxPsdDbmPerBw": -56.8 }, { "freqHz": 2.16e8, "maxPsdDbmPerBw": -56.8 }, ], [ { "freqHz": 4.70e8, "maxPsdDbmPerBw": -56.8 }, { "freqHz": 5.18e8, "maxPsdDbmPerBw": -56.8 }, { "freqHz": 5.18e8, "maxPsdDbmPerBw": 30.0 }, { "freqHz": 5.24e8, "maxPsdDbmPerBw": 30.0 }, { "freqHz": 5.24e8, "maxPsdDbmPerBw": 36.0 }, { "freqHz": 5.30e8, "maxPsdDbmPerBw": 36.0 }, { "freqHz": 5.30e8, "maxPsdDbmPerBw": -56.8 }, { "freqHz": 6.98e8, "maxPsdDbmPerBw": -56.8 } ] ] }, { "bandwidth": 1e5, "profiles": [ [ { "freqHz": 5.4e7, "maxPsdDbmPerBw": -74.58 }, { "freqHz": 7.2e7, "maxPsdDbmPerBw": -74.58 }, ], [ { "freqHz": 7.6e7, "maxPsdDbmPerBw": -74.58 }, { "freqHz": 8.8e7, "maxPsdDbmPerBw": -74.58 }, ], [ { "freqHz": 1.74e8, "maxPsdDbmPerBw": -74.58 }, { "freqHz": 2.16e8, "maxPsdDbmPerBw": -74.58 }, ], [ { "freqHz": 4.70e8, "maxPsdDbmPerBw": -74.58 }, { "freqHz": 5.18e8, "maxPsdDbmPerBw": -74.58}, { "freqHz": 5.18e8, "maxPsdDbmPerBw": 27.0 }, { "freqHz": 5.24e8, "maxPsdDbmPerBw": 27.0 }, { "freqHz": 5.24e8, "maxPsdDbmPerBw": 33.0 }, { "freqHz": 5.30e8, "maxPsdDbmPerBw": 33.0 }, { "freqHz": 5.30e8, "maxPsdDbmPerBw": -74.58 }, { "freqHz": 6.98e8, "maxPsdDbmPerBw": -74.58 } ] ] } ] Does that address your concern? -- -vince -- -vince
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
