Study of Open Mobile Alliance Device Management Sessions for Most Effective Device Management
Total Page：16
File Type：pdf, Size：1020Kb
Master’s Thesis Computer Science Thesis no: MCS:2011:22 September 2011 Study of Open Mobile Alliance Device Management sessions for most effective device management. Tomasz Smolarek School of Computing Blekinge Institute of Technology SE – 371 79 Karlskrona Sweden This thesis is submitted to the School of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science in Computer Science. The thesis is equivalent to 20 weeks of full time studies. Contact Information: Author: Tomasz Smolarek 870321-P378 [email protected] University advisor: Dr Andrew Moss School of computing School of Computing Internet : www.bth.se/com Blekinge Institute of Technology Phone : +46 455 38 50 00 SE – 371 79 Karlskrona Fax : +46 455 38 50 57 Sweden ii ABSTRACT Effective device management is not trivial due to a variety of devices and software. To keep costs to minimum companies must effectively utilize a unified solution for device management. This research investigated Funambol’s implementation of Open Mobile Alliance Device Management (OMA DM) which is the most popular device management solution. Interviews were used to set experiments and create realistic test cases. A set of devices and a collection of Funambol software were used to create device management sessions. All of the sessions were recorded, analysed, manipulated and resent to identify efficient ways of device management. Additionally, an influence of compression and buffer-like mechanisms were checked. Methods and guidelines are provided for efficient use of OMA DM as well as a reliable analysis of OMA DM Sessions under various conditions. It was found that for most data it is best to use a built-in transport protocol compressor. Hypertext Transfer Protocol’s (HTTP) deflate with a combination of client-side buffering-like mechanism at a client side performed best at most cases. Funambol’s implementation of the Binary Extensible Markup Language (WBXML), in most cases, performed very badly, even though it was designed specifically to compress OMA DM Session messages. It was found that for an efficient use of OMA DM a proper software option set (e.g. forced use of compression) may be sufficient. Keywords: OMA DM, Funambol, testing. iii ACKNOWLEDGEMENTS I would like to express my gratitude for the help I got from my thesis supervisor Dr Andrew Moss. Without his great support, constructive criticism and overall guidance I would not be able to write this thesis. He showed great understanding and a lot of patience when supervising the research. I would like to thank all the people responsible for the Double Diploma program at both Blekinge Instutite of Technology and Gdansk University of Technology who created the program and allowed me to participate. I would also like to thank my girlfriend, who has always believed in me and buoyed me up when I needed it. iv LIST OF ACRONYMS AGPL GNU Affero General Public License BER Bit Error Rate DM Device Management FCAPS Fault, Configuration, Accounting, Performance, Security FRAND Fair, Reasonable, and Non-Discriminatory Terms GSM Global System for Mobile Communications HP Hewlett-Packard HTTP Hypertext Transfer Protocol IIS Internet Information Services IMEI International Mobile Equipment Identity ITU International Telecommunication Union JPEG Joint Photographic Experts Group MD5 Message-digest Algorithm 5 MP3 MPEG-2 Audio Layer III OBEX OBject EXchange OMA Open Mobile Alliance OMA DM Open Mobile Alliance Device Management OMA DM WG Open Mobile Alliance Device Management Working Group POSIX Portable Operating System Interface for Unix RFC Request for Comments RTT Round Trip Time SMS Short Message Service SNMP Simple Network Management Protocol SOAP Simple Object Access Protocol SSL Secure Sockets Layer SyncML Synchronization Markup Language TCP/IP Transmission Control Protocol / Internet Protocol TLS Transport Layer Security UMTS Universal Mobile Telecommunications System URI Uniform Resource Identifier WAP Wireless Application Protocol WBXML Binary XML XML Extensible Markup Language v LIST OF TABLES AND FIGURES Table 1: Fitted functions for session processing times - default behaviour. ......................... 29 Table 2: Confidence intervals for server operation times - default behaviour. ..................... 30 Table 3: Fitted functions for session processing times - compression.................................. 36 Table 4: Fitted functions for messages sizes - compression. ............................................... 37 Table 5: Fitted functions for breakeven points - compression. ............................................ 41 Table 6: Confidence intervals for server operation times - compression.............................. 42 Table 7: Fitted functions describing buffer behaviour - buffering. ...................................... 48 Table 8: Fitted function for buffering time - buffering. ....................................................... 49 Figure 1: OMA DM architecture (based on Figure 18.2 from [9]). ..................................... 10 Figure 2: DM Server initialized DM Session package flow (based on Figure 1 from [25]). 12 Figure 3: OMA DM HTTP usage (based on [28]). ............................................................. 13 Figure 4: Basic synchronization message exchange (based on [12]). .................................. 15 Figure 5: Operating systems used by respondents. ............................................................. 18 Figure 6: Device types used by respondents. ...................................................................... 18 Figure 7: Connection types used in respondents‟ devices. .................................................. 19 Figure 8: Funambol Administration Tool. .......................................................................... 23 Figure 9: OMA DM Session Message pattern. ................................................................... 25 Figure 10: Session processing times – exchange of plain text data, plain text data transformed with base64 and binary data. ................................................................... 27 Figure 11: Session processing times – exchange of mixed data. ......................................... 27 Figure 12: Funambol Server operation times for messages with plain text data. .................. 27 Figure 13: Funambol Server operation times for messages with plain text data transformed with base64................................................................................................................ 27 Figure 14: Funambol Server operation times for messages with binary data. ...................... 28 Figure 15: Funambol Server operation times for messages with mixed data. ...................... 28 Figure 16: Fitted functions for session processing time - exchange of plain text, plain text with base 64 and binary data. ..................................................................................... 29 Figure 17: Fitted functions for session processing time - exchange of mixed data. .............. 29 Figure 18: Plotted confidence intervals for server operations. ............................................. 30 Figure 19: Session processing times – exchange of plain text. ............................................ 32 Figure 20: Session processing times – exchange of plain text transformed with base64. ..... 32 Figure 21: Session processing times – exchange of binary data. ......................................... 32 Figure 22: Session processing times – exchange of mixed data. ......................................... 32 Figure 23: Session message sizes – exchange of plain text data. ......................................... 33 Figure 24: Session message sizes – exchange of plain text data transformed with base64. .. 33 Figure 25: Session message sizes – exchange of binary data. ............................................. 33 Figure 26: Canonization times for messages with plain text data. ....................................... 34 Figure 27: Preprocessing times for messages with plain text data. ...................................... 34 Figure 28: Processing times for messages with plain text data. ........................................... 34 Figure 29: Postprocessing times for messages with plain text data. ..................................... 34 Figure 30: Fitted functions for session processing time – exchange of plain text data. ........ 35 Figure 31: Fitted functions for session processing time – exchange of plain text data transformed with base64. ........................................................................................... 35 Figure 32: Fitted functions for session processing time – exchange of binary data. ............. 35 Figure 33: Fitted functions for session processing time – exchange of mixed data. ............. 35 Figure 34: Fitted functions for message size – exchange of plain text. ................................ 37 Figure 35: Fitted functions for message size – exchange of plain text transformed with base64. ...................................................................................................................... 37 Figure 36: Fitted functions for message size – exchange of binary data. ............................. 37 vi Figure 37: Breakeven points for gzip compressor – exchange of plain text data. ................. 39 Figure 38: Breakeven points for wbxml compressor – exchange of plain text data. ............. 39 Figure 39: Breakeven points for wbxml + deflate compressor – exchange of plain text data.