1. Demo

2. Demo setup 3 scenarios 3 orchestrators Services: –Doorbell –MediaSink: display, mobile display –MediaSource: videosource, camera –Context manager –Repository

3. Scenario 1: highlights Discovery without the repository  the repository is optional Orchestrator only establishes the application; it is not involved in the operation of the application.

4. Scenario 1 orchestrator

5. Scenario 1 orchestrator

6. Scenario 1 orchestrator discovers

7. Scenario 1 orchestrator binds

8. Scenario 1 orchestrator

9. Scenario 1 orchestrator

10. Scenario 1 1. The video orchestrator is started 2. The bell, mediasource (video), tv services are started 3. The orchestrator finds the services 4. The video is streamed from the source to tv 5. The orchestrator is shut down 6. The streaming is still running

11. Scenario 1: conclusions Service discovery with optional repository increases reliability. Orchestrator is not involved in the operation of the application: –reusability of the services –less resource usage at the orchestrator

12. Scenario 2: highlights Discovery of existing, new and disappearing services with the repository No dependencies between startup order of services, orchestrators and repository Services are reusable. The actual binding by the orchestrator determines the application

13. Scenario 2 repository registers orchestrator query

14. Scenario 2 repository orchestrator binds

15. Scenario 2 repository orchestrator

16. Scenario 2 0. The previous services are still running 1. The repository is started 2. The previously running services are registered at the repository 3. The mediasource (camera) and another tv are started 4. The new services are registered at the repository 5. The doorbell orchestrator is started 6. The doorbell is pressed 7. The camera output is seen on the tv 8. After n seconds, the image is frozen 9. The camera and tv are shut down 10. The camera and tv are unregistered at the repository

17. Scenario 2: conclusions Discovery with the repository: –Scalability, –Less burden at the orchestrator. Periodic renewal at the repository: –Robustness Independent startup ordering of the repository, orchestrator, and services: –Flexibility External binding of services –Reusability

18. Scenario 3: highlights Change of application –Service removal –Context change Orchestrator can contain preferences for certain services (tv)

19. Scenario 3 repository orchestrator binds Context manager

20. Scenario 3 repository orchestrator Context manager

21. Scenario 3 repository orchestrator binds Context manager

22. Scenario 3 1. The bell, camera, tv, mms, context manager, repository, orchestrator are started 2. The doorbell is pressed 3. The camera output is seen on the tv 4. The tv is switched off 5. The doorbell is pressed 6. The camera output is seen on the mms device 7. The tv is switched on 8. The doorbell is pressed 9. The camera output is seen on the tv 10.The context manager changes the user location to outside 11. The doorbell is pressed 12. The camera output is seen on the mms device (while the tv is still on)

23. Scenario 3: conclusions Applications can change dynamically Policies for device selections