Hi Aki,
> >> What is the reason behind a{sv}aa{sv} here? Wouldn't it be simpler to
> >> just go with aa{sv} and declare that the first dict is always the
> >> current serving cell? Are the information from the current cell really
> >> that different than from the neighbors?
> >
> > The rationale is that this is the format OMA-TS-ULP-V2_0-20100816-C and
> > 3GPP RRC define for user plane location. Also, all modems don't provide
> > the same information for serving and neighbor cells; e.g. isimodem
> > follows the above mentioned specs. I believe that for location purposes
> > the information included in the a{sv} part is not needed for neighbors.
> > Hence making the structure flat would not really make things simpler.
>
> I originally suggested a{sv}aa{sv}, but I don't see a problem this
> being just a flat aa{sv}. The keys in dicts can always be different,
> and if the documentation clearly states that the first dict is always
> meta-data, followed by the actual neighbor measurements, it'll work
> just the same.
so the position engine would need the details that you provide in the
current serving cell. And just following network registration is not
good enough here?
Also the information from the current serving cell are really different
from the neighbor cell information?
Regards
Marcel
_______________________________________________
ofono mailing list
[email protected]
http://lists.ofono.org/listinfo/ofono
