1. Applications Morris Sloman Christian Hoene Henning Schulzrinne

2. Applications Traditional (email, VoIP, IM, …) Group interactions Utility computing (grid) E-commerce/E-business applications Embedded applications –pervasive –sensor-style General applications have not done well –cell phone + iPod + digital camera

3. Ubiquitous & autonomic computing Intersection & overlap Ubiquitous computing needs autonomic networking functionality Both strive for invisibility of the underlying “machinery”

4. Autonomic Needs for Applications Self-configuration –reduce configuration (policy preferences) interwork with default configuration –generally similar, particularly for embedded applications (remote medical monitoring) –portability of configurations configuration changes propagate across devices across dis-similar services (I18N) –out-of-the-box security –discovery of new software versions –discovery of off-load servers –learning by observing user behavior: e.g., call handling rules in email and VoIP

5. Application needs Self-diagnosis –application behavior diagnostics policy “no port 25 allowed here” vs. transient failure –turn off automated mechanisms Self-healing –automated updating of software –find alternate servers or services –migrate services to other servers on failure or degradation (e.g., network failure)

6. Example application services File storage (.mac, Yahoo briefcase) –application storage (relaying across disconnections with mobile devices) –configuration storage global configuration (I18N) application-generic configuration Lookup functionality: –mapping –attribute-value based Computation and relaying, such as –NAT traversal (STUN, TURN) –Anonymity relays –media translation (codecs, bit rate) –bridging (mixing) –HTML compression –translation of media types: text-to-speech, speech-to-text Optimization on end-to-end flows