SUPSI Status Report

1
SUPSI Status Report

• May 24th 2007, Cambridge

2
Outline

• On going implementation on Windows XP (New
  features)
• Next steps
• Device selection recommendations

3
New features

• We created a SUPSI_email branch in the Haggle
  repository.
• It contains enhancements in terms of
• Improved usability
• Windows services (ndisprot, wireless zero) are
  automatically managed by Haggle
• Dlls do not have to be moved manually by the
  user
• An installer (Setup.exe) automatically detect the
  list of connectivities, update the configuration
  file and set up libraries and files
• Haggle is launched as an executable file

4
New features
Performance enhancement new DHCP client To speed
up the time for retrieving and setting a new IP
address during the switching to the AP mode we
implemented an enhanced DHCP client. Our DHCP
Client follows the traditional RFC 2131
handshake, but tries to use the IP address
contained in the ARP message sent by the DHCP
Server during the initial phase (asking for the
ownership of the proposed IP). At the end of the
process there is a comparison phase after which
the parameters are validated Experimental results
show that in the best case (IP retrieved from the
ARP broadcast message), the average time for
retrieving and setting the new IP is 90 less
than the time needed for the default Windows DHCP
client. In the worst case scenario (ARP broadcast
message not grabbed and IP retrieved via DHCP
traditional handshake) the average time for
retrieving and setting the new IP is 50 less
than the time needed for the default Windows DHCP
client.
5
New features
Performance enhancement new DHCP client
Forwarding algorithms We are working on the
integration in Haggle of our PROPICMAN
Forwarding Algorithm
6
Next steps

• Integration of the SUPSI_email branch into the
  Haggle official release
• Implementation of our DHCP Client on Linux
  (Ubuntu 7.04)
• Implementation of a Message Board application and
  integration in Haggle (term project with SUPSI
  students, not yet committed ...)
• GPRS management (only on Windows Mobile?)

7
Device selection recommendations

• Implementation oriented approach identify a set
  of candidates, try to make Haggle work on them
  ...
• IDE for Java development IBM WebSphere
  Everyplace Micro Environment
• it uses open standards and a Java 2 Micro Edition
  (J2ME) runtime
• it supports Connected Device Configuration (CDC)
• IBM provides an evaluation version of its JVM
  (J9) (other alternatives, like Esmertec Jbed CDC
  and NSICOM crème, dont )
• IDE for C development Microsoft Embedded
  Visual C 4.0
• My device ranking list
• Samsung SGH-i600 (Smartphone. IBM doesnt
  provide any official CDC implementation of its
  JVM for Windows Mobile Smartphone edtion, but it
  seems to work fine. Esmertec Jbed doesnt provide
  support, NSICOM crème does)
• HTC S620 (Smartphone)
• HTC TYTN (3G support, a practical keyboard, Java
  CDC is supported )
• ASUS A639