Monday, June 25, 2007

Is AdSense/Words a proper model for Mobile Advertisment?

A lot of people in carriers, internet companies are thinking about how to extend the online marketing/advertisment to mobile and it seems it is not a succesful task.
The successful Google model (AdSense/AdWords) faces difficult constraints with mobile: display size, not too extensive mobile browsing by users due to usability & concerns and uncertain conection costs, etc.

Sometimes when a model is so succesful people tries to replicate it in all "access way" but the answer for the question in the title is NOOOOOOOOOO !!! :-)

For mobile our purpose is re-starting from scratch. Important keys for us:

1/ free for users,
2/ not intrusive,
3/ carriers getting revenue from advertisers,
4/ advertisers getting more for same investment, business intellienge integrated with mobile advertisment

this is our aproach, our model will be explained soon

juan mateu

Monday, June 18, 2007

Sneaking through a hole in a walled garden

I live in Madrid, it is a beautiful city and the capital of Spain. It is a nice place to live with lot of public gardens where all citizens can enjoy. But this has not always been so. Take as an example the Retiro ( It was conceived as a rest place for kings and their kindred around the end of XVII century. Only in the early XIX century, some citizens where allowed to walk inside certain parts of it, and only if they commit to certain "good manners". It was only in the last century when this park was open to the public. And becoming a public garden, allowing all citizens to enjoy it, walking, bicycling, etc., was how it got to realize its full potential. By now, you should be asking what has to do all of this with mobile technologies. Good, let me put you in context:

Ok, I must say that I totally agree with the article from Eugene. And I must say that the problem he points to is no special case of the US, but is a general one also in Europe. Perhaps not so hard, as it is possible to deploy third party applications on most terminals from any carrier (be it J2ME or Symbian). Although, in practical terms this hardly makes a difference as most subscribers are not willing to download any applet :-(

However, it is true that enhancing the browser capabilities in mobile phones, and making them more similar to what we expect to have on a normal laptop will ease the deployment of mobile applications. This is already happening, as most mobiles include nowadays browsers with capabilities close to those of their PC counterparts. But this will be boosted with the iPhone coming out, including a full featured Safari browser. This will allow to have full web style applications on the phones with AJAX interfaces, including all multimedia elements, also with proven good development frameworks, like those built around J2EE, and allowing to easily integrate with all the IT infraestructure in most corporations. This in turn will reduce development and operational costs of mobile applications.

This looks nice, as it may allow application developers to slip through a hole in the carriers walled garden. However, this is not the end of the story, there is still one important element: usability. And this puts the challenge once again on the application developers side. I mean, having web style applications in the phone is nice. But you cannot expect all subscribers to use those applications in the same way they use web desktop applications. So, new user interaction paradigms must be developed: involving touch screens, multimodal interfaces where the user can navigate through voice and get the result in the mobile browser, and why not, even navigation through gestures (ok, I know, I know, I should get a Wii and forget about all this ;-)

Friday, June 15, 2007

Are rational the carrier concerns about PoC? (II). What Solaiemes is doing.

Currently Solaiemes is working in several compelling use cases mobile-to-server with added value use case and no possible SMS or Voice Call cannibalization. We are focused on man-machine interaction to make normal life actions easier with low additional cost for user combined with revenue increase for carrier.
The point is that it is needed a commercial OMA PoC commercial service offered by local carrier to get advantadges of new use cases.

Actualmente Solaiemes está trabajando en la creación de casos de uso para el OMA push to talk (push over cellular) basados en la interacción hombre-máquina (sin posibilidad de canibalización de llamadas vocales y/o SMS) y que permitan simplificar muchas de las tareas diarias por muy bajo coste para el usuario, pero un ingreso agregado para el operador móvil.
Eso sí, necesitamos que se lancen ya los servicios comerciales de OMA PoC en España y los países de nuestro entorno.

juan mateu

Monday, June 11, 2007

the role of IMS in MVNOs

Firstly we should distinguis between "hard MVNOs" owning the own Core infrastructure (softswitch, ims, application servers) and the basic "traffic resellers".
Our approach is about the opporunity for hard MVNOs (i.e: in Spain several MVNO are expected to become full MVNO as Euskaltel, ONO, R, because they are fixed communication companies moving to be converged).
Carriers from fixed world extending their range of services to converged/mobility have mass market users and enterprise/corporate customers, they have now the capability to attract them as a mobile customers as well. Typically IMS is an easy infrastructure to integrate ASP mode services or licensed, the ecosystem of providers is becoming important, and new use cases other than VoIP are appearing.

A full MVNOs could offer OMA PoC (push-to-talk) services to enterprise customers with commercial PoC servers with no full carrier grade dimensioning, they can provide new services based on IMS (as video-sharing applications) without investing huge amounts of money in CAPEX and being a platform to test real use of these solutions:

-without compromising the global revenue due a possible not studied cannibalization of other services as SMS (it is being feared by carriers to deploy PoC i.e.)
-study the real appliability of use cases and help to study the right billing model to extend them to residential customers.
-link mobile and fixed branches into a new model of converged customers paying private services, the services could even become hosted as ASP, increase loyalty and reduce churn.

The MVNO are newcomers in a mature market, their mobile branches should have a light staff structure and could be easily linked to sales objectives in current enterprise base of customers.

They have then a good opportunity if they are fast offering new services while incumbent mobile carriers have slower decission cycle to deploy new services because they have to estimate global impact.

Currently, Solaiemes is developing new use cases to be applied to enterprise and public services customers, they need IP connectivity in both mobile and fixed sides, and could be hosted directly by final customers, become ASP from the telecom provider, or use ASP from external provider and use mobile and fixed data connectivity from the carrier/MVNO.

our ConverG+LiveServe SIP/IMS solutions are described at:

an example is being displayed at the bottom of this blog.

Solaiemes is not only creating technology to create new mobile/converged use cases, is also offering consultancy to help MVNO and carriers to evaluate CAPEX/OPEX investment defining the needs and best options for core and services infrastructure adquisition.

Solaiemes Project :-)

Monday, June 4, 2007

Identity mgmt for service customisation

Opportunities exist now to use identity management as a tool to personalise communication services. By personalisation I mean any of this:

  • dynamically changing service configuration
  • creating new content
  • blending service primitives in a different way
based on customer identity, previous interactions, etc.

Current Parlay/X framework makes this easy. IMS framework makes it even easier. All the components are there, although it is fair to say that some adaptations may be needed.

Customers reaction to a service based on past usage, browser patterns, etc. may be mixed. Some customers would not tolerate too-intrusive a network, whereas others will complain that is too dumb for their expectations.

Which are the technical challenges associated to this? Let's explore it in a bit more detail.