W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2010

RE: ACTION-16 for SystemInfo API

From: Smith, Kevin, (R&D) VF-Group <Kevin.Smith@vodafone.com>
Date: Mon, 1 Mar 2010 16:51:44 +0100
Message-ID: <37AC1116121D3F43B9A67CB16E2E79FF021BEAE1@VF-MBX11.internal.vodafone.com>
To: "SULLIVAN, BRYAN L (ATTCINW)" <BS3131@att.com>, "Max Froumentin" <maxfro@opera.com>
Cc: "Rotan Hanrahan" <rotan.hanrahan@mobileaware.com>, <public-device-apis@w3.org>, <public-uwa@w3.org>
(Just to provide a reference:

MCC is defined by the ITU-T E.212 at [1], and MNC by ITU-T as an annex
based on that recommendation [2.

[1] http://www.itu.int/publ/T-SP-E.212A-2007/en
[2] http://www.itu.int/publ/T-SP-E.212B-2009/en (shows both MNC and MCC)
)
--Kevin



-----Original Message-----
From: public-uwa-request@w3.org [mailto:public-uwa-request@w3.org] On
Behalf Of SULLIVAN, BRYAN L (ATTCINW)
Sent: 01 March 2010 15:13
To: Max Froumentin
Cc: Rotan Hanrahan; public-device-apis@w3.org; public-uwa@w3.org
Subject: RE: ACTION-16 for SystemInfo API

MCC     = 3 digits // country code
MNC     = 2 digits // mobile network code

Thanks,
Bryan Sullivan | AT&T
-----Original Message-----
From: Max Froumentin [mailto:maxfro@opera.com]
Sent: Monday, March 01, 2010 6:45 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Rotan Hanrahan; public-device-apis@w3.org; public-uwa@w3.org
Subject: Re: ACTION-16 for SystemInfo API

Hi Bryan,

On 01/03/2010 12:27, SULLIVAN, BRYAN L (ATTCINW) wrote:

> But if the same information can be derived from MCC and MNC (which 
> presumably it can), then I agree a Boolean will suffice for roaming.
> But we need to be sure that the MCC/MNC (home and visiting) are things

> that the application can determine through the SysInfo API.

Is it safe to assume that both MCC and MNC are unsigned shorts?

Max
Received on Monday, 1 March 2010 15:55:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:06 GMT