1 Seminar: Pervasive Computing 2004 Automatic mobile device configuration: Status & open challenges Stefan Hoferer Supervisor: Andreas Fasbender

2 Need for an automatic device configuration Mobile devices today:

3 Device Configuration: A first Use Case e.g. Contacts, Ring- tones, Images, etc Transfer of relevant data and settings from an old to a new device Trigger Optimal:Today: Infrared, Bluetooth Data cable 1Data cable 2 Manual entry e.g. Ring-tones, Notes e.g. Ring-tones, Notes e.g. Images, Contacts Configurations

4 Device Configuration: Another Use Case Management Server Web Server Request content “I need a new configuration” Customer Configuration message Content delivery

5 Device Configuration: More Use Cases Customer Service provider Device manufacturer Network operator  Remote device management by operator / service provider  Help desk problem determination, troubleshooting  Easy change of device with all settings and data  Over the air mass configuration  Remote device management  Easy management of services  No automatic mobile device configuration at all  All application areas of automatic mobile device configuration

6 Challenges in mobile device management PDA Camera Internet Notebook PC Printer Company Intranet Company database

7 Challenges in mobile networks  High network latency  Limited bandwidth  Network coverage problems  Heterogeneous devices  Multitude of different applications

8 Requirements for management protocols  Operate efficiently in wireless and wire-line networks  Support a variety of transport protocols  Support any kind of networked data  Support any device  Address the resource limitations of the mobile device

9 WAP Provisioning  Introduced by the WAP-Forum  Provide a device with connectivity information  Built upon existing WAP infrastructure  Independent of device and bearer  Fast and flexible management mechanism

10 WAP infrastructure

11 WAP Provisioning: Trusted relationship Trusted relationship Mobile device Trusted Provisioning Server NAP Proxy- Server

12 Bootstrapping and continuous provisioning

13 WAP Provisioning documents  Binary encoded XML documents  Simple Document Type Definition  Special MIME type:  text/vnd.wap.connectivity-xml  application/vnd.wap.connectivity-wbxml  Parameters related to:  logical proxies, physical proxies, network access points, bootstrap process, vendor specific configuration, client identity  Connectivity Documents must be complete

14 Synchronization Mark-up Language  Introduced by SyncML consortium in the year 2000  Open industry standard  Independent of:  underlying transport protocol  Transport bindings for HTTP, OBEX, WSP  device type or manufacturer  file types  XML and DTD based

15 SyncML Device Management  Introduced 2002 by the SyncML consortium  Re-use of Synchronization Mark-up Language’s core DTD  Re-use of communication framework  Management scope:  device configuration (modify or read operating parameters)  software maintenance  inventory (operating parameters, read installed or running software list, hardware configurations)  diagnostics (listen for alerts sent from a device, invoke local diagnostics on a device)  Mechanism for customer interaction

16 SyncML Device Management Protection Mobile deviceManagement server Alert Management session

17 SyncML DM: Bootstrapping  Necessary information for Initiation of Management Session  Management Server (IP-address, port-number and name)  Network access point settings (address, bearer)  Authentication information  Two possible bootstrap mechanisms:  Customized bootstrap  Server initiated bootstrap

18 SyncML Device Management Management Tree:

19 SyncML DM management commands ADD - creates a new interior node COPY - copies values from a node to another at the client DELETE- deletes a node (and all its sub-nodes) EXEC - process execution on the target REPLACE - overwrites value for an existing node GET - retrieves data from the target RESULTS - contains results from a Get ALERT - used for notifications, text displays ATOMIC - all subcommands must be executed SEQUENCE - subcommands must be executed in order

20 SyncML Device Management //Header information... //management operations...

21 SyncML DM Protocol

22 Status and open challenges  Many proprietary protocols  WAP Provisioning  already used  limited management scope  SyncML DM  not net widely implemented

23 Status and open challenges BrandModelContactsCalendarTasksNotes s MotorolaV300XX--- Nokia3650XXX-- Nokia6230XXX-- Nokia7650XXX-- NokiaN-GageXXX-- PanasonicX70XX--- SiemensM55XXXX- SiemensS55XXXX- Sony EricssonP800XXX-X Sony EricssonT610XXX-- List of mobile devices with SyncML capabilities

24 Status and open challenges Transfer of relevant data and settings from an old to a new device e.g. Contacts, Ring- tones, Images, etc

25 The future of device management Embedded systems:

26 Additional Slides Time Left? => Additional Slides

27 User Agent Profile: Introduction Welcome to the UAProf – test page Welcome to the UAProf – test page Device 1Device 2 Welcome to the UAProf – test page Device 3

28 User Agent Profile: Components Components of a UAProf - profile  HardwarePlatform  SoftwarePlatform  BrowserUA  NetworkCharacteristics  WapCharacteristics

29 User Agent Profile: Transfer of profiles (1) wsp-request User Agent Profile WML-document Transport of User Agent Profiles Origin Server

30 User Agent Profile: Transfer of profiles (2) wsp-request UA Profile with reference WML-document Transport of User Agent Profiles with reference to default profile on a repository server. Origin Server Repository Server