Re: MNC/MCC as string?

[Marcel Holtmann <marcel@holtmann.org>]

[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]

Hi Remi,

> > > >> For geolocation help, sure, but there are other places where MNC/MCC
> > > >> are used as keys to databases containing operator-specific
> > > >> information, like default Internet APN names and such.
> > > >
> > > > shouldn't we just integrate that database into oFono directly or as
> > > > something like ofono-info.git that will be installed along with (for
> > > > easier updates).
> > >
> > > This particular database of default APN names, maybe, although I think
> > > it's really oFono users like Connman that should integrate with that
> > > information.
> > >
> > > However, this wouldn't be the only database ever, so we would still need
> > > a way to reliably identify a specific operator.
> >
> > if we are unclear about the format and the users at this moment, I
> > prefer we remove that interface and just keep it around as a TODO item
> > to add it later.
> 
> I don't see any lack of clarity. It is a series of two or three digits.
> 
> Anyway, if the database has a hole, we probably will have to return the 
> MNC/MCC anyway (ever tried scanning for network with an old phone in a foreign 
> country?). Then there is also the uniqueness problem. MNC/MCC pair solves 
> that.

if the database has a whole or we don't have the network provider string
then we can just show the MNC/MCC in that case. That is pretty simple.
No need to put extra burden into the userspace application and have it
looking for two strings.

I don't understand your uniqueness issue. We will have unique object
path for every network. What else does userspace needs?

Regards

Marcel