Bluetooth Proximity Marketing Software

I am looking for someone or a team of programmer to design a fully completed and branded Bluetooth Advertising Proximity System with custom company logo’s , icons and colors. Based on this, I will need you to provide SOURCE CODE and it should have a well planned modularity to allow anyone with the appropriate expertise to improve or change the functionality. Also, must be compatible with the common USB bluetooth drivers. It should be developed to work on a mini computer with Intel Atom processors with 1 GB of SDRAM and 8 GB solid-state hard disk running Linux Ubantu. Bluetooth Proximity Marketing software will be loaded and installed in a mini computer to broadcast to nearly any type (JPEG,GIF,MP3,MP4,3GP,AMR,AAC,JAR,vCard,vCalendar,txt) of file to cell phones and PDA within its broadcasting range. - Bluetooth Advertising Software for Linux Ubantu Platform - Use Bluez stack - Support at least 4 USB bluetooth dongles (CSR Chipset) - Configurable to have 1 dongle to scan and other 3 dongles to send data - Use OBEX/OPP - Use thread - Must be able to scan very quickly and dump the mac address of the target bluetooth device to other dongle to send - Use XML as database for saving sent list, black list - Software must be able to get the model of the phone - Must keep log of everything (Devices found, devices accepted, devices rejected, successful upload, failed upload, detailed transfer log) - Configurable option as follow: * Sender Name (Device Name) or Message that appears on the mobile phone to request for transfer * Connection Time-Out - Numbers of seconds the hotspot will wait for remote handset to accept connections. Use shorter time-out for high traffic location * Connection Retries - Maximum number of connections attempts * Next Retry After - Break time after maximum number of connection attempts reached * Resend After - When to re-send the same file next time. Choose “never” to avoid re-sending the same file to the same handset * Broadcast Radius - Approximate broadcasting radius. You may consider limiting it at high-traffic events (use of RSSI) * Send Schedule o Duration Based (i.e. June 11, 2010 10:00 to June 12, 2010 21:00) o Routine Based (i.e. Every Monday at 11:00 - 12:00) - All configuration through the use of XML file