Android based mobile application to control (electronic) sensors

We are looking for an Android based mobile application to control electronic sensor(s). The connectivity between mobile and electronic sensor should be "Wifi". See the attached document to see the communication flow. There are two very important libraries called “Sensor Queuing and Scheduling Library” (SQSL) and “Communication Queuing and Scheduling Library” (CQSL). The reason we have the SQSL and CQSL is because in future we will have multi-sensors and multi-communications simultaneously (phase 2 of this project). So the system should be able to handle the problem of queue and schedule in order to make sure every data packets can be send and received correctly. The communication for sending a packet will be: 1. UI send out “Command/Data” to SQSL (eg. turn on PM2.5 sensor, turn off PM2.5 sensor, get value from PM2.5 sensor). 2. SQSL use sensor library to generate “Sensor packet” and arrange the schedule (eg. identify the corresponding sensor library and schedule depending on the number of requests for different or same sensor(s)). 3. The “Sensor packet” will be sent to CQSL 4. CQSL use communication library to envelop the “Sensor packet” into “Communication packet” (eg. wifi protocol or bluetooth protocol). 5. CQSL arrange the schedule into to send out the packet The communication for receiving a packet will be: 1. The “Communication packet” arrive CQSL and be decoded into “Sensor packet” using communication library 2. The “Sensor packet” arrive SQSL and be decoded into “Command/Data” using sensor library 3. The “Command/Data” will be sent to UI We would like to have only one sensor (PM 2.5 sensor) and one communication protocol (Wifi) at this stage. The in scope items for the project are as follows: 1. PM 2.5 sensor Library (For generating sensor packet) 2. Sensor Queuing and Scheduling Library (For handling the multi-sensors queue and schedule problem) 3. WiFi library (For generating communication packet) 4. Communication Queuing and Scheduling Library (For handling the multi-communications queue and schedule problem) 5. Testing UI for testing the data packet (sending and receiving) Note: The User Interface at the top of the diagram is not in scope of the project. As the User Interface and the relevant physical sensor part is out of scope for the project, point 5 (above) is included. It is nothing but a simulation to show the functionality is working (not much different than what developers do for unit testing). Please also note that the communication is two way communication. So the sensor library and communication library could generate the packet and also decode the received packet. Happy to answer any queries.