W3C home > Mailing lists > Public > public-coremob@w3.org > July 2012

Re: Network Information Use Cases

From: Tomoyuki SHIMIZU <tm-shimizu@kddi.com>
Date: Thu, 05 Jul 2012 19:51:22 +0900
Message-ID: <4FF571AA.1080608@kddi.com>
To: jeanfrancois.moy@orange.com
CC: tobie@fb.com, public-coremob@w3.org
Hello everyone,

The use cases proposed by Jean-Francois are of interest to me, too. In addition to them, I want to show another use case of network information such as below:

· International Roaming: Almost all smartphones can access the web when we go anywhere in the world, by applying international 3G roaming. Roaming services require much higher fee, so eliminating data traffic and offline functionality are desired when 3G roaming is being applied and no wi-fi connection is available. It's useful to detect which 3G carrier is currently connected to, as well as to detect/switch the type of connection.

Best,

-- Tomoyuki
KDDI Corporation, Japan

(12/07/05 18:43), jeanfrancois.moy@orange.com wrote:
>>> Hello everyone,
>>>
>>> I had been assigned an action point that consists of describing use
>>> cases that would encourage the inclusion of the Network Information
>>> APIs <http://www.w3.org/TR/netinfo-api/> in the Core Mobile level 1
>>> specification. I will list a few below:
>>>
>>> ·         Visual Voicemail platforms: Visual voicemail platforms are
>>> commonly accessible only through 3G (platform access is restricted
>> from
>>> the Internet). The NetworkInformation APIs are required to detect the
>>> current interface, and switch to 3G if a voicemail needs to be
>> fetched.
>>> The Orange OMTP platforms notably work like that.
>>> ·         TV Services: TV services and streams are secured and
>> encrypted
>>> and use the SIM and 3G network  for the authentication process. After
>>> the authentication has been performed, it is possible to offload
>>> through the Wi-Fi connection.
>>> ·         Usage Applications: Most carriers provide applications that
>>> give real time minutes and data usage for a user, as well as the
>>> possibility to subscribe/unsubscribe to/from various options. Servers
>>> storing these information can only be accessed through 3G access.
>>>
>>> As you see, it is important for carriers to know the current network,
>>> mostly for authentication purposes, but also as some of our platforms
>>> are not accessible from the Internet. It would also be nice to be
>>> capable of routing a connection through an interface, but thatıs
>> another story.
>>
>> Hi Jean-François,
>>
>> Thanks for documenting these use cases. I think it would be worth
>> sharing them with the new sys-apps WG[1] as the Network Info API won't
>> cover any of them: the Network Info API doesn't let you switch network,
>> only get info about the current one.
>>
>> Best,
>>
>> --tobie
>
> Hello,
>
> I am aware of the fact that the current specification would not allow switching from one network to another, but still the fact of knowing of which network we are currently on is of interest.
>
> Best,
>
> Jean-Francois
>
>
>> ---
>> [1]: charter: http://www.w3.org/2012/05/sysapps-wg-charter.html,
>> mailing
>> list: http://lists.w3.org/Archives/Public/public-sysapps/
>>>
>
>
Received on Thursday, 5 July 2012 10:52:56 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 April 2013 17:36:46 UTC