This project requires a developer with expertise in mobile app development for Featured OS (for phones like itel 2160) Android and iOS, cloud server connectivity, mobile communication and security. There is preference to developers who understand token security and experience with data transaction monitoring and capture and experience with Featured OS that contains pre-loaded app on a non-smartphone. The project will have an app developed that will monitor transaction and create a new APIs or program to interact with other systems to process an action or trigger data capture to a cloud database.
The idea would be to develop an app that could use smartphone technology for Android or iOS native phones that could check all data leaving the phone especially, POST and gets from all applications but capture USSD data for non-smartphones.
Android Developer 1 Certification Test is a must and understanding of Featured OS for basic non-smartphone.
Link: Itel 2160 [login to view URL]
Below is an explanation of how USSD works.
[login to view URL]
How USSD works
Unstructured Supplementary Service Data (USSD) is a protocol used by GSM cellphones to communicate with their service provider’s computers. USSD can be used for WAP browsing, prepaid callback service, mobile money services, location-based content services, menu-based information services, or even as part of configuring the phone on the network.
_images/[login to view URL]
From the diagram above, a request is sent from a mobile phone to a telecom network such Vodafone.
The Ussd Gateway (telecom) then sends the request to your ussd application (i.e where we have the business logic which determines the menu to serve the use on receiving user’s request.)
Your ussd application then responds to the request, and Ussd gateway goes ahead and displays your content to the user
Below is a another diagram to help understand the concept
_images/[login to view URL]
Why Ussd Airflow
Before I explain why we need Ussd Airflow lets first look at one example of ussd user case
Example Menu-Driven USSD Application
One could decide to develop a mobile-initiated “Balance Enquiry and Top Up” application using USSD signaling, enabling a mobile user to interact with an application via the user’s handset, in order to view his/her current mobile account balance and top up as needed.
An example of such an application could be as follows:
A mobile user initiates the “Balance Enquiry and Top Up” service by dialing the USSD string defined by the service provider; for example, *#123#.
TheUSSD application receives the service request from the user and responds by sending the user a menu of options.
The user responds by selecting a “current balance” option.
The USSD application sends back details of the mobile user’s current account balance and also gives the option to top up the balance.
The user selects to top up his/her account.
The application responds by asking how much credit to add?
The mobile user responds with the amount to add.
The USSD application responds by sending an updated balance and ends the session.
The figure below shows an example of the MAP/TCAP message sequence required to realize the data transfers between a mobile user’s handset and the USSD application to implement the “Balance Enquiry and Top Up” service described above.