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

RE: Sys Info network attributes

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Tue, 1 Jun 2010 13:48:48 -0700
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
CC: W3C Device APIs and Policy WG <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D32565AAB290@orsmsx501.amr.corp.intel.com>
Hello

Are you suggesting that we should put mcc and mnc back and make them mandatory? If these are optional, then it seems like APN is sufficient. 

Thanks
Dzung Tran,


-----Original Message-----
From: Anssi Kostiainen [mailto:anssi.kostiainen@nokia.com] 
Sent: Tuesday, June 01, 2010 07:08 AM
To: Tran, Dzung D
Cc: W3C Device APIs and Policy WG
Subject: Re: Sys Info network attributes

Hi Dzung,

On 31.5.2010, at 16.19, ext Tran, Dzung D wrote:

>> (Out of the above mcc and mnc were removed in the latest revision done today.)
> 
> I removed mcc and mnc because these were redundant due to the fact that you can get that information from apn as for example:
> 
> Examples of APN are:
> 
>    Example: internet.mnc012.mcc345.gprs
>    Example: internet (NOTE: This APN example does not contain an operator identifier part)
> 
> This is what I have researched, if this is incorrect, please let me know then I will put these back.

It seems only the APN Network Identifier part ("internet" in your example) is mandatory whereas the APN Operator Identifier ("mnc012.mcc345.gprs") is optional. This behavior is defined in a spec known as "3GPP TS 23.003 Numbering, addressing and identification" [1]. Wikipedia provides a crash course for those who'd prefer to steer clear of Word documents [2].

-Anssi

[1] http://www.3gpp.org/ftp/Specs/html-info/23003.htm
[2] http://en.wikipedia.org/wiki/Access_Point_Name
Received on Tuesday, 1 June 2010 20:49:26 GMT

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