Mobile Broadband Service » client server

How to deploy Facebook application on wireless internet service

engineer — Sat, 01 May 2010 14:46:52 +0000

Telecommunication companies which has wireless internet service such CDMA 1x and GPRS are not recommended to provided BlackBerry service due to internet access speed reason. However, wireless internet service they already have can be utilized to provide the similar service on the Blackberry service such as email service, Facebook application and messaging service (Yahoo Messanger, Gtalk, WLM etc). Other applications also can be developed there to differentiate it with the service on the mobile broadband service. BREW platform is the term to overcome the problem on wireless internet service to introduce high application on the low and middle mobile phone

To deploy facebook application on wireless internet service, telecommunication companies should prepare below network infrastructures:

client server BREW application
wireless internet network which including Public Data Serving Node (PDSN), Charging Gateway, AAA server and CDMA network which including BTS, BSC and HLR
Internet gateway to connect to outside (Facebook.com)

The key point to introduce Facebook application on wireless internet service which actually has speed up to 153,6 kbps is deploying client – server BREW application. The key parameters while deploying client – server application are:

How much maximum speed can be consumed by low end mobile phone which will access Facebook application
Memory utilization and disk capacity that will be allocated on the mobile phone

Client application in this case is Facebook client that will be inserted on the mobile phone with BREW platform. Algorithm and applications details should be pre-defined and should match with the Server before they deployed on the mobile phone. Meanwhile Server application is middle ware server which interact with mobile phone and facebook server. Beside the algorithm and protocol that should have match with the client, server application should proper and same with algorithm on the facebook server as well. This algorithm which called Facebook Algorithm Programming Interface (API) should be synchronized every time once facebook server made any changing

Incoming search terms for the article:

The failure point of Value Added Service (VAS): Application programming interface (API) Facebook

engineer — Sun, 25 Apr 2010 17:36:47 +0000

Telecommunication companies that offering Facebook application as the part of Value Added Service (VAS) either on mobile broadband service such EVDO, 3G and Wimax should anticipate the changing on Application programming interface (API) by Facebook it self. This could happened especially on mobile facebook developer which using open source Facebook Java Application programming interface (API). Telecommunication Company which plan to provide Facebook application on the bundling mobile phone should deployseveral network elements and application client server to accommodate such Value Added Service (VAS)

To deploy Facebook application on such VAS, there are 2 components that should be deployed. The first is the Facebook client which will be inserted to the mobile phone with Facebook application. The second is middleware server which response any request comes from facebook client to facebook.com. Middleware server should interact with facebook.com so facebook client (mobile phone user) can generate facebook application and can do many activities there such as updating the status, commenting and change the profile. To interact with facebook.com, middleware server use Facebook Java Application programming interface (API) protocol provided by facebook.com itself.

Due to huge traffic especially the traffic comes from mobile facebook application trigged facebook.com to keep updating and changing the open source Java Application programming interface (API) protocol. This changing should be anticipated by mobile developer which responsible on middleware server and synchronize their facebook Java Application programming interface (API) with the new changing. More often, the changing on Facebook API is minor which means that only several sub modules were changed but it is still impacted to the customers experiences while they accessing facebook through mobile phone. The impact of API changing which did not synchronized on midlleware server could be time out response while mobile user tries to access facebook.com. Facebook mobile developer should anticipate this API changing that may come anytime.