Web Enabled Devices home networks Johan Lukkien programme

Web Enabled Devices & home networks Johan Lukkien programme leader “home networks” Eindhoven Embedded Systems Institute Eindhoven University of Technology

Overview n n n Evolution of embedded systems and embedded networking Architecture of Web connected devices Fully networked devices n n requirements a few example networks Internet solutions Conclusion Johan Lukkien 11 -4 -2001 2

Embedded Systems evolution n hardware replaces software n n digitisation and manipulation of signals configuration/programming of systems from outside completely networked systems Johan Lukkien 11 -4 -2001 increase in networking n functionality features 3

Network aware: Information retrieval Network central: Adapt product design with from the system rudimentary fashion respectintoathe network connection Network connected: On-line connection with Fully networked: functionality is defined • Status errors, the wear, use with embedded • Integrate network functions the information: system byhardware the network • Using existing connections and resources and software already within the • available Standardisation ofsystem connections, protocols • Put control hardware/software next to the • Devicesofcontrolling each other • Off-line analysis data embedded system • Intelligent environments, all equipment in the • Transport: telephone, Internet • Interaction! Standalone: embedded network central network aware(Philips: “ambient background intelligence”) hardware and software: time • invisible • are, in fact, an standalone aspect network connected fully networked implementation Advantage: http: //aquarium. eesi. tue. nl of Advantage: the product • remote • • diagnosis service: access to embedded software: debugging, replacement, sell features Advantage: • owner: standardisation, new software Advantage: http: //www. research. philips. com/generalinfo/special/ambintel/index. html • service: diagnostics, leasing of appliances • service: new markets • owner: remote monitor & control, security, • owner: ease of fleet use, maintenance comfort, integration production-control, Johan Lukkien 11 -4 -2001 4 Evolution of embedded networking

The effect of Internet • Data transport (large distance) • Standards: ftp, email, . . . network aware • Distributed access standalone . . . + Johan Lukkien Interoperability network central • Standards for time offering services: Jini, UPn. P, OSGi • Platform for • Standards for network connected • datafully networked exchange • software architectures integration • communication: HTTP, • Java, TCP, UDP, . . • visualisation: browsers information exchange!! • Global addressing 11 -4 -2001 5

Technical background n Moore: number of transistors/mm 2 doubles every 18 months n n Metcalfe: de “value” of a network is proportional to the square of the number of nodes n n n processing power and memory capacity become abundant adding a node benefits existing nodes the larger the network the larger the benefit Gilder: Internet bandwidth triples every 18 months n bandwidth becomes abundant Johan Lukkien 11 -4 -2001 6

Overview n n n Evolution of embedded systems and embedded networking Architecture of Web connected devices Fully networked devices n n requirements a few example networks Internet solutions Conclusion Johan Lukkien 11 -4 -2001 7

Architecture Request connection Remote user Program code sensors Applet HTML browser Johan Lukkien UDP ES-Server HTTP (applet code) 11 -4 -2001 actuators HTTP server 8

Components n HTTP server: n n ES server: provide “driver interface” for embedded system HTTP browser (client): n n standardized access: URL code download: Java applet setup contact run machine-independent code “programmable interactive remote control” Applet: n n interface to user driver of ES Johan Lukkien 11 -4 -2001 9

Trade-offs Observer Embedded System 1 2 Actuators & Sensors Connection 1: Internet n protocol implicit: within applet n protocol explicit: n n available to other systems protocol requirements: n n n access levels of users; security state inspection and modification notification of state changes Johan Lukkien 11 -4 -2001 10

Trade-offs Observer Embedded System 1 2 Actuators & Sensors Connection 2: n proprietary n other network, e. g. , i/o network, field bus n Internet? ? n n bus-like function for Internet aggregation, embedded control What are the criteria to put intelligence at an actuator/sensor? Johan Lukkien 11 -4 -2001 11

Example: ubicom room control Devices not networked individually http: //www. ubicom. com Johan Lukkien 11 -4 -2001 12

Example: EESI coffee maker Switch and heat control not networked individually Request connection Program code Remote user Johan Lukkien 11 -4 -2001 13

Trade-offs Observer Embedded System 1 2 Actuators & Sensors Criterion supporting intelligence at A&S Connection 2: • Hardware is locally necessary n proprietary • safety, real-time control (don’t distribute safety n other network, e. g. , i/o network, field bus issues across an unreliable network) • establishing relationship actuator-sensor n Internet? ? • process sensor input bus-like function for Internet n aggregation, embedded control Criteria against intelligence n • Single function (ES is already dedicated) at an What are the criteria to put intelligence • Logical unit controlled from ES actuator/sensor? • No power available Johan Lukkien 11 -4 -2001 14

Overview n n n Evolution of embedded systems and embedded networking Architecture of Web connected devices Fully networked devices n n requirements a few example networks Internet solutions Conclusion Johan Lukkien 11 -4 -2001 15

Fully networked devices n n Separate user interface and driver functions It must be simple to attach to the network n n n Zero configuration connection n lightweight easy to handle build a logical network automatically peer to peer in absence of server Zero configuration interoperable n n n service publication and discovery devices control each other no fixed identification Johan Lukkien 11 -4 -2001 16

n n n (Sunbeam) powerline, RF Zero-config for HLT-enabled appliances n n identification based on unique device id static definition of devices, services (? ) Proprietary protocol, central control prime target: domotica Johan Lukkien 11 -4 -2001 17

Live-in n n Zanussi (Electrolux, Sweden) Home automation: integrated use of telephone, powerline and cable auto-config central access point, remote control Johan Lukkien 11 -4 -2001 18

n n n Use telephone, powerline Four components: communication-link, current meter, tele-link, digital adapter Web Ready Appliance Protocol auto-config for WRAP-enabled appliances Console, web connected Johan Lukkien 11 -4 -2001 19

Lonworks n n n Echelon, fieldbus technology philosophy: 3 networks (computer, control, entertainment) use many types of media auto-config, static typing of devices deployed in n homes transportation industrial automation Johan Lukkien 11 -4 -2001 20

Internet? n n Concerns the layers above the data-link Until now: mainly supporting computers n not much use of alternatives like powerline (is growing now) little internet-use within the home Configuration needs n n n IP address, network mask, router address, domain name server TCP/IP stack. . . + protocols on top of that Johan Lukkien 11 -4 -2001 21

Auto-config issues n Level of discovery n n n Definition of device n n n static (list of known devices) dynamic Definition of services n n physical level (plugging, e. g. “network reset”) network level (broadcasting) static dynamic (publish interface) Centralized/distributed knowledge Resulting network load Johan Lukkien 11 -4 -2001 22

Technologies n Connecting: n IP auto configuration: setup a network locally (integral part of IPv 6, add-on of IPv 4) n n choose a link-local address in the absence of a DHCP server no traffic beyond a router (IPv 4, NAT) Apple-talk, Win 98 Services: n n n Jini (Sun, Java based) OSGi (Java based) Universal Plug ’n Play (Microsoft) Johan Lukkien 11 -4 -2001 23

Jini (Sun) n n n Assuming network connection Centralized information store: lookup service Upon plugging: discovery & join-in n n discover lookup service upload an object implementing the services (driver) Upon using: obtain driver from the lookup service; use RMI General classification of services (e. g. , video source, display, . . . ) Johan Lukkien 11 -4 -2001 24

Universal Plug ’n Play n n Use IPv 4 auto-config or DHCP Simple Service Discovery Protocol n n Service Control Protocol n n n service announcement service request device description: XML document state variables operations Subscription on state updates Optional user interface URL Fully decentralized solution Johan Lukkien 11 -4 -2001 25

Other developments n n n Work of the “zero-configuration networking” Working Group within IETF Service Location Protocol (supports queries) Lightweight Directory Service Protocol n n to access shared information . . P Johan Lukkien 11 -4 -2001 26

Conclusion n n Growth path for (inter)networking Internet pervasive n n n Zero-configuration required as devices n n n but there’s room for a control network connecting control to internet: gateway grow in numbers control each other IP as platform n n open standards available software, infrastructure, experience etc. Johan Lukkien 11 -4 -2001 27