User Manual
Table Of Contents
- INTRODUCTION
- CONTROLLING THE ACCESS SERVER
- CONFIGURATION
- USING THE SYSTEM
- BLUETOOTH TECHNOLOGY OVERVIEW
- INTRODUCTION TO SDK
- INSTALLING THE WRAP SOFTWARE DEVELOPMENT ENVIRONMENT
- CREATING WRAP APPLICATIONS
- BLUETOOTH SERVER SOCKET INTERFACE
- I/O API
- ABOUT BLUEGIGA
- APPENDIX A – WRAP DIRECTORY STRUCTURE
USER'S AND DEVELOPER'S GUIDE WRAP MULTIRADIO ACCESS SERVER
WPKGD INBOX
/tmp/wpkgd/in
InstallPoint
USB memory USB hotplug
WPKGD OUTBOX
/tmp/wpkgd/out
Bluetooth
Rsync over SSH
FTP
Scp, Sftp
WPKG
processing
Customer System
InstallPoint
USB memory USB writer
Bluetooth
Rsync over SSH
FTP
Scp, Sftp
Figure 4. WRAP Remote Management Architecture.
A management action is performed using the following protocol:
1. A management packet (*.wpk) is prepared by the customer system.
2. The management packet is delivered to WRAP, into packaging daemon’s inbox
directory. One can currently use Bluetooth, Rsync over SSH, Scp, Sftp and plain FTP to
do this. Also some USB memory dongles are supported, see subsection 4.4.5.7.
3. The WRAP packaging daemon processes the management packet, possibly generating
reply packet into daemon's outbox.
4. (optional) Reply packet is delivered (or retrieved) to the customer system.
4.4.5.2 M
ANAGEMENT PACKET FORMAT
- Package name must be of format "name.wpk", where "name" can be user
defined.
- Package must be tar –archive that is compressed with gzip (like files named
*.tar.gz or *.tgz)
- Package must contain package information file called "wpkg.pif" in package root
(contents described later)
Bluegiga Proprietary, Copyright © Bluegiga Technologies 2001-2004 31 (94)