1. 5 August, 2014 Michel Chaudron,Johan Muskens, Johan J. Lukkien and Hailiang Mei TU/e Computer Science, System Architecture and Networking 1 Remote Terminal Management When do we need the Remote Terminal Management? – Routine update and maintenance (e.g. new version of component available or license expired) – Remote diagnosis and healing (error oriented, can be initialized by either terminal itself or user)

2. 5 August, 2014 Michel Chaudron,Johan Muskens, Johan J. Lukkien and Hailiang Mei TU/e Computer Science, System Architecture and Networking 2 Remote Terminal Management When do we need the Remote Terminal Management? – Routine update and maintenance (e.g. new version of component available or license expired) – Remote diagnosis and healing (error oriented, can be initialized by either terminal itself or user)

3. 5 August, 2014 Michel Chaudron,Johan Muskens, Johan J. Lukkien and Hailiang Mei TU/e Computer Science, System Architecture and Networking 3 Routine Update/Maintenance  Self-update through remote server Classical approach, think about Windows Auto-update  Update by following neighbors Terminal can announce its new service to neighbors  Update by server + neighbors Combination of the above two approaches

4. 5 August, 2014 Michel Chaudron,Johan Muskens, Johan J. Lukkien and Hailiang Mei TU/e Computer Science, System Architecture and Networking 4 Remote Terminal Management When do we need the Remote Terminal Management? – Routine update and maintenance (e.g. new version of component available or license expired) – Remote diagnosis and healing (error oriented, can be initialized by either terminal itself or user)

5. 5 August, 2014 Michel Chaudron,Johan Muskens, Johan J. Lukkien and Hailiang Mei TU/e Computer Science, System Architecture and Networking 5 Remote Diagnosis + Healing Scenario A Self observes problem + Server diagnosis + Server healing

6. 5 August, 2014 Michel Chaudron,Johan Muskens, Johan J. Lukkien and Hailiang Mei TU/e Computer Science, System Architecture and Networking 6 Remote Diagnosis + Healing Scenario B User initialization + Self & server diagnosis + Server & neighbor terminal(s) healing