All,
As was brought up before (and at) the F2F, the current encoding for a
spectrum profile
has a "channelized" view:
- List of (startHz, stopHz, power)
- Has no ability to specify power level in "unavailable" ranges
Example:
{
"point": { "startHz": 5.18e8, "stopHz": 5.24e8, "maxPsdDbmPerBw": 30.0
},
"point": { "startHz": 5.24e8, "stopHz": 5.30e8, "maxPsdDbmPerBw": 36.0
},
}
Question: Should we use a more flexible encoding?
There were two proposals made on the list:
- Option 1: List of (startHz, startPower, stopHz, stopPower)
- Option 2: Ordered list of (freqHz, power)
At the F2F, we agreed that Option 2 was the more general form.
Example:
{
"point": { "freqHz": 4.70e8, "maxPsdDbmPerBw": -56.8 },
"point": { "freqHz": 5.18e8, "maxPsdDbmPerBw": -56.8 },
"point": { "freqHz": 5.18e8, "maxPsdDbmPerBw": 30.0 },
"point": { "freqHz": 5.24e8, "maxPsdDbmPerBw": 30.0 },
"point": { "freqHz": 5.24e8, "maxPsdDbmPerBw": 36.0 },
"point": { "freqHz": 5.30e8, "maxPsdDbmPerBw": 36.0 },
"point": { "freqHz": 5.30e8, "maxPsdDbmPerBw": -56.8 },
"point": { "freqHz": 6.98e8, "maxPsdDbmPerBw": -56.8 }
}
This example explicitly specifies the power levels in the unavailable
frequency ranges.
This example also shows that it's possible to encode "square edges" by
having two
points using the same frequency, but does allow for "slanted edges" for
more gentle roll-offs.
--
-vince
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws
