TI3.2 Technology and Business Aspects
|Task Title||Technology and Business Aspects|
|Lead partner||Basic Internet Foundation|
|Contributors||Mondragon University, ITS|
|edit this task|
- 1 TI3.2 Technology and Business Aspects
- 2 Deliverables in TI3.2 Technology and Business Aspects
- 3 Technology Issues
- 4 Business considerations
This Task will identify the open issues related to technology and business, resulting from the operation of Phase A of the DigI project.
Deliverables in TI3.2 Technology and Business Aspects
Based on Media:DigI_TechnIssues.pdf
A) Migration of BasicInternet.no to the cloud
- done, Mar2019
- the current platform is based on Ubuntu, and is transferred to Debian 9 for increased stability
B) Voucher creation and handling
Platform in place, needs how to description (Wiki page)
- Cloud platform with login for (Agent) to create vouchers
- should include the specification of the vouchers, in terms of Time, Amount, and Validity
- Note: Sales price depends on the location and the access
- is performed by a local person
C) White List versus Black List
Our current installation is based on a White List, meaning that only white listed pages can be reached. This is the preferred solution for information hot-spots.
However, for locations with fixed bandwidth, as Patandi Teachers College and Caritas Kinderdorf, the solution might rather include black-listing. This is performed through adding the the black lists first, and then *,accept as last line
Note: the White Lists and Black Lists are handled through owncloud, and a script updates them every night
D) Login Page "accept"
Solution: we need a https://accept.basicinternet.no... file for the login (to be established)
Android login: After access to "BasicInternet", we get the message "sign in to network". This brings us to the login.html page (owncloud = BasicInternet = Technology = Mikrotik = TZ_villages = hotspot = login.html). But, the user has no "button" to acknowledge (Accept Free Access) versus (Add Voucher) and (Accept).
In order to use the Internet, the user has to press the 3 vertical dots in the top of the sign-in Window, and then "use network as is". Can we bring that functionality into the (Accept Free Access) button?
- accept: should then close the window and return to the browser
- voucher: as is, but only voucher (not username & password)
Remote update of login page
- how do we practically update the login?
E) Blocked Pages
Currently "404 Error - not available", should redirect to login page. See topic D), redirect should do the job
F) Village platform Yeboo.com
- rudged platform as village serverm, needs a copy of "yeboo.com" on a Raspberry Pi
- remote access through the Local Network Control Centre (LNCC)
Content for each village through phpadmin
- need for a 1-page description (how to edit), Maurice provides the credentials
- need for remote access to village platform (Iñaki?)
- needs to be disabled in the villages where Christine runs the intervention
- suggestion: redirect the link to the health section towards the "about the village"
G) Monitoring of usage
- Maghsoud's implementation
For each village we need roughly 3.000 €/each, as we are still in a pilot phase. Equipment costs "close to nothing", around 300 €/InfoSpot (+500€ for solar kit if needed) and wifi extension adds another 200€. - The OPEX is around 20 €/month (SIM card, broadband).
What really costs is getting the local people and the authorities involved. My take is that we need typically 4 meetings:
- 1 meeting to prepare the authorities
- 1 meeting to make the site survey and connect to the village people
- 1 day to perform the installation (typically done within 2-4 hours/spot)
- 1 meeting to afterwards support the local development.
In Tanzania, as most other African countries, we need to pay daily allowance (~40-50€/day/person) And, we often supply with e.g. 2 tablets per village (~130€ each). Other costs are shipping, import tax++. And, our work force is currently paid by the DigI project, thus not accounted in the cost calculation.