There are two parts to neighbor cell information. The first part
provides meta-information on the second part, which is the actual
Like you propose, the first part is a dict, with keys like cell type and
current MCC and MNC.
The second part is the measurement data, and that is different for
different types of cells. Not all information is mandatory for all
modems and all cell types.
The formatting might have been a bit confusing, but I was actually proposing a single
property ("Info") containing an array (one entry for each cell) of dicts, with
the dicts having measurement and other info on that particular cell.
I think the pattern you use here is wrong. This needs to be a method
call; a signal won't work. The measurement data is constantly changing,
and you don't want a constant stream of PropertyChanged() signals.
The important property here is that the location system has a single
method call that retrieves all relevant information from the modem, so
that they can then do their triangulation magic.
Yes, it's important to keep things atomic.
> int8 RSCP [readonly, UMTS only]
> Received Signal Code Power [3GPP TS 25.133
s220.127.116.11] in dBm [-120...-25]
> int8 ECNO [readonly, UMTS only]
> CPICH Ec/No [3GPP TS 25.133 s18.104.22.168] in dB [-
This is already part of the measurement data, which I think should be in
the per-cell information (the serving cell measurement data is still
Yes, all this is per-cell, sorry if that wasn't clear.