Re: Network Information Use Cases

On 7/4/12 4:45 PM, "jeanfrancois.moy@orange.com"
<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

---
[1]: charter: http://www.w3.org/2012/05/sysapps-wg-charter.html, mailing
list: http://lists.w3.org/Archives/Public/public-sysapps/
>

Received on Wednesday, 4 July 2012 16:48:54 UTC