Proposal for New Items : Seamless mobility API for web applications

Dear Sysapps WG members,

I am Sunghan Kim from ETRI.
On comming W3C sysapps WG F2F meeting, I would like to briefly introduce a new issue regarding seamless mobility issue for
web application. I think that application relevant protocols suite are necessary to consider for web applications, though

now is progressing on the issue of Raw Sockets API for web application. One of crucial features in mobile device is moving from to area to area

and it causes changing network interface on mobile device. And, this will require the application to support the necessity of seamless connection between different networks. These seamless mobility technologies are necessary for web applications to support a capability of seamless mobility.

Therefore, this contribution is to suggest the necessity of seamless mobility issue for web applications.


Some descriptions are described below :

Description:
- Provide some examples of use cases for web applications to support seamless mobility capability in the situation of changing different network interfaces by mobile device.

Motivation:
- Need to maintain a session or network connection for web application on device while changing network interface.
- Web application support “always-on” communication for mobile service, anytime, anywhere, and any networks.

Dependencies:
- Many kinds of service environment : mobility management technologies and handover technologies exist

What needs to be standardized:
- Generic interface may need to be standardized for seamless mobility API
- But, some use cases and requirements need to survey before defining the scope of this API


Use case  (One of examples) :  Mobile web game with vertical handover

Mike plays mobile web game at 3GPP wireless service areas and is walking to outdoor, and the mobile web game is network game in client-server environment. ( He connected to game server was authenticated to network continuously through phone number to have connected at 3GPP areas, and uses ID and PW. Game server checks phone number to confirm that user who is authenticated through ID and PW was coupled continuously to server.)
As he plays a game, he is walking into Wi-Fi area. Network authentication data does not tranfer from 3GPP to Wi-Fi service. But, game server checks IP address whether user is authenticated or not. However, IP is changed as Mike moves from 3GPP areas to Wi-Fi area. Therefore, moble web game application does not continue due to non-authenticated IP by the game server, and as a result, the mobile session is disconnected.



I hope that this issue is reviewed in last 3rd day of F2F meeting, next phase 2 meeting slot, if Chairs and members are agreed.



Best regards,

Sunghan