HNTF/Home Network TF Discussions/ServiceMigration/comments gp1
Service Migration
Submitter: Jean-Claude Dufourd, Telecom ParisTech
Tracker Issue ID: ISSUE-7
Description: A service moving across devices: e.g. I start using my phone for the user interface to a device, then my tablet becomes available, so I move the interface service to the tablet.
Implementation: Possible implementation on top of UPnP:
- I start using my phone as a UI of a service on my TV, e.g. EPG, but the screen is small.
- My tablet finally becomes available.
- I request the migration of the current document (user agent function).
- The user agent discovers its peers on the network, i.e. other user agents capable of running the current document.
- The user agent proposes to me a list of suitable user agents, including the one running on the tablet.
- I choose the user agent running on the tablet
- The UA on the phone binds to the UA on the tablet, and sends a migration message with the URL of the document, and the URL of the execution state.
- The UA on the tablet receives the migration message, fetches the document and the execution state, loads both.
- The UA on the tablet signals to the UA on the phone that migration is complete, by replying "success" to the migration message.
- The UA on the phone stops rendering the migrated document.
- I pick up the tablet and go on with the service at the point I left it on the phone.
Justification:
Dependencies: None
Comments:
This UC4 asks the questions: how do we move a service and its current "state" to another device ? what is the "state" ?