Making the Wave

Google has just released the Wave, a new way of combining email, short messages, video, and documents into a mesh of information and collaboration in real-time. It also has functionality to replay the wave to see in which order things were added.

Here'e why I think this will actually take off:

• Meshup of well-known technologies. Utilizing well-known and widely used technologies uptake will be a matter of usability. Combining them together in one user interface simplifies life dramatically. I can hardly keep track of all my Yammers, Twitters, Skype, Y!, MSN, gmail and audio and video clients. Combining them together will make Wave a killer. Even my grand father could use it together with users of Twitter for example.


• Fosters Collaboration. Going from one lonely user sending an asynchronous mail into a virtual cacophony of voices that together discusses using all sorts of tools. Together creating, analyzing and acting upon ideas and thoughts collectively brought together.


• Done in Realtime. No more waiting, no more typing in darkness and no more faceless thoughts. Welcome to a world in realtime where together has a new meaning. I'm looking forward to when I can read as my friend is typing and responding on an instant. Sharing media and documents where editing and changes are visible instantly.


• Open API's from D-day. Integration with my favorite document editor, mobile phone, chess-game, presentation, and the likes will make Wave the number one choice for anyone creating similar software.


• What about video and document sharing? I think I've seen information that Wave will include video and audio streams as well. For this to take off we would need realtime document sharing as well. Is it included?

And finally some thoughts on what the telecoms missed out once again:

• Where's the revenue stream for the telco's?


• Where's the new service models?


• Where's the use of IMS and SIP? Yet another service that has totally bypassed the IMS.


• When will Telco's start to innovate?

Rich Communications Suite, Pimp My PC

What's wrong with Skype, MSN, Yahoo, and the other IM, chatt, and voice over IP providers? Why are you not using them everyday in the same way as your mobile phone? Skype and their likes are after all pretty useful still they aren't part of your DNA. And then why will Rich Communications Suite, RCS, be the one-stop-shop pimping your PC and mobile?

RCS was founded by the gorillas and the sharks in the mobile telecom industry to fight the competiton from internet Web 2.0 and software giants like Microsoft and IBM with their enterprise solutions. Day-by-day the average telco operator transforms like a maggot into a frozen puppet only offering low value commoditized access. They all want to become as cool and hip as Google while still milking the minutes from the traffic-cow, eating and keeping the cake at the same time. The answer was to bundle together some key applications that are as common as opening your eyes in the morning saying "Ahh, another fantastic day!". By including the ever present telephony and mobile access in the package they are creating a milk-and-honey bundle where the sweetness of the honey makes it attractive. None of the other vendors have such a compelling story to offer as the mobile operators and equipment vendors. So now finally the telecom industry have gathered their forces to offer a complete stack of communication tools to combat the evil of internet. Is this good for you?

I think this might be good if the RCS implementations contains at least these levels of freedom and playgrounds for old grandma, Joe-the-plumber and Einstein Jr.

• Intuitive userinterfaces similar, if not identical, to what we have today
• Plug-in concept allowing old grandma to create her own hearing-capability improvements
• Fast communication in reality that leaves no room for WAP-like overselling dissapointments.
• Flat-rate subscription models
• Ad-supported subscription models
• Fully integrated with existing operator B/OSS - not one more invoice from a new silo offering
• Babel's tower of instant translations between protocols and applications
• Developer business models supporting active and creative application and plug-in development

The beauty of RCS is that it is based on IMS and SIP which means any SIP application can be integrated. If the walled garden would just be opened and the snake of wisdom and opportunity be set free. Then it would be a creative chaos contrasting today's God like operator creatures knowing it all.

Greetings RCS, may we all have done our homework and learned the Web 2.0 lesson of collaboration and contribution. Then there will be a lot of Enriched Calls, Enhanced Messages and  Enhanced phone book lookups, even so embedded with Joe-the-plumber's task assignment scheduler. A time when my PC speaks like Babel's tower - all the languages and applications in the world communicating through one standard interface - SIP and IMS pimping my PC. I'm not sure it will ever happen, with the right approach and openness it has the possibility to succeed if the operators open their mindset.

Myths About Network Intelligence

Today ICIN 2008 started with revealing some myths about network intelligence. Roberto Minerva from Telecom Italia has been working with network intelligence for quite some years and collected eperience from what to avoid when dealing with network intelligence.

The topic itself is very interesting and especially the angle taken by Roberto where he uses the Anti-Pattern pattern. Looking at solutions from the other angle than usually gives you new views to an area and opens up for new thoughts. This is what I experienced during the talk.

Roberto had identified the following Myths:

• Network Transparancy
• Network abstraction hides information. In worst case the hidden information prevents further development of services using other features not exposed by the abstraction framework.
• Solution to Network abstraction is to introduce a flat architecture with a gradually increasing level of abstraction. Thus a service can use the highest abstraction level interface possible still meeting the feature needs. If a more finer grained interface is needed that is available by other interfaces in the flat architecture. You could view this as a stair of abstracted interfaces.
• Open API
• Today Open APIs are focused on call control or messaging type of interfaces
• Look at the importance of data and data representation. Google's main business is profiling and collection of data in order to provide targeted advertisements.
• Network with Quality
• The QoS issue impossible in network of networks
• Look at P2P where the intelligence is in the edge.
• Data Networks and Services it is hard if not impossible to keep the network quality promise (or SLA).
• Cloud computing and WebOS was brought up by Roberto. WebOS could very well be sticky service many operators are looking for.
• The Need for Centralization
• IMS and SDP is traditionally seen as a winning proposition. These are centralized solutions.
• Google and Amazon are reinventing the service platform concept and are exploiting the Client-Server paradigm much beyond what an operator could do.
• Operators can use WebOS and P2P much more to create a decentralized network providing sticky services.

Presence Zone for Contextual Presence Location Information

Presence Zones Enriched Location data with contextual information. 

 

Presented by IBM research in Haifa. They have run a research project trying to enhance presence information by adding context to the location where I am and then set presence status based on that.

 

The concept is based on defined zones with certain attributes. There can be automatic zones and there can be zones set up by a restaurant that pushes out information about menu and offers together with presence info. A zone can be identified using different location technologies like GSM triangulation, cell-id, GPS, Bluetooth, RFID and generic near field communications.

 

In the case of a restaurant owner he puts in a bluetooth device that identifies guests as they enter and leaves and sends that information to the presence server.

 

On top of this enhanced context aware location information there can be applications created that utilize the automatic presence information. The most obvious example would be enabling end-users to create their own mashup between presence and other sources like restaurant guides, astma information, etc.

 

Other applications can be call routing, pre-call presence information, targeted advertisements, offers, quiet zones and what-have-you.

Opening Interfaces - Impacts on Telco Business Models

This morning at ICIN 2008 starts with a panel discussion on opening interfaces and how that impact the business models of the telco operators.

The panel is led by Kristofer Kimbler and consists of Roberto Minerva, Agustin Nunez, and David Pecota.

My key takeaways from the panel disussion:

• Operators are already open, however they want to charge from the beginning limiting adoption. Contract management, charging, payments (between operator and developer) and security are factors in the mind of the operator.
• How to charge? Look at the business model of iPhone applications which enables ease of payment transfers between buyer and vendor.
• Global access to the open APIs is crucial. Here Google and iPhone serves as good examples.
• Open interfaces is happening today through Google Maps for example
• Presence, location, social networks: traditionally the telco has provided this. Today the internet is leading innovation, development and adoption.
• The customer for open interfaces is the developer. Developers are lacy. Make the interfaces easy, global and simple return on investment (payments).
• Customer data and profile information is a unique attribute of the operator.
• IP models on top of existing legacy is the unique heritage of the telco operator. Pure internet players don't have this which simplifies life and provides global access and availability.
• Operators should define themselves as the enabler of the social network, not telephony or access.
• Enterprise applications is an easy market to target today where the end customer is ready to pay and sees a direct value. Discussed Dentists and other healthcare providers. Microsoft providing enterprise services through Exchange server. Going beside the operator avoiding tricky business models. Voice capabilities in the enterprise market
• Business model and common API's today:
• Skype for Salesforce
• Marketsize and availability of enablers and APIs
• Don't fight the internet

I think the panel discussion was interesting and also highlighted the challenges. The telco operators really need to transform themselves in order to catch the opportunity.

Kill your darlings - The death of the Killer Application

We all knew it, the "Killer Application" is dead. What is there to replace it?

During ICIN 2008 a common theme so far is the need for open telco operators providing services for various kinds of mashup. This implies that the search for the next killer application is dead. The open telco should provide services to its customers. It is unclear so far which services the operator should provide and how to charge for the service.

From my point of view the question is wrongly asked. A better question would be "What do your customers need? What would simplify their life?". Opening up the telco only helps if you know what your customers will need to use. The opening of the telco itself is more of a technical exercise than of anything else. It is however important as a foundation for execution of an open telco operator enabling colaboration with external innovation and development. How do you get to know what your customers needs and wants?

One way that I have been experimenting with is to open up labs or trial areas where the operator and customers can collaborate and play with open services. By tracking what becomes popular an operator can focus efforts in that area to provide quality of service, security and the appropriate business model. With a thorough follow-up and evaluation of how services are used a greater understanding of underlying drivers and motivators can be understood. From this point the operator can evaluate which services to open, business models, bundling and alignment to strategy and vision. It is extremely important to be in line with your strategy and vision otherwise customers will be confused and/or there will not be a continuation of the process due to misalignment of strategy.

Another important aspect of opening up telco operators is to provide billing and CRM functionality supporting personalization and business models. Being able to personalize customer offers helps being relevant and meeting the individual customer. Supporting different business models is critical in enabling flexible payments and bundlings of services. Who should pay for the open services and how? Flexibility here enables advertisement and someone-else-is-picking-up-the-bill business models.

In short: The Killer Application is dead, it's time to open up the telco. In order to succeed you need to know your customer and what he wants. Flexible billing supporting business models and payments enables a sound business for all parties.

Why are everyone talking about SDP or Service Delivey Platforms?

During a dinner yesterday I called SDP dead as it is not a generic component. It is rather a philosophy on how to deliver services than a ready steady platform. So from now on it is more correct calling it SDE, Service Delivery Environment, or SDF, Service Delivery Framework, as TM Forum.

Listening to ICIN 2008 Keynote speakers David Pecota, Microsoft, and Augustin Nunez, Open Movilforum, they focus on how to deliver services to customers. David was talking about the converged lifestyle. Users are using telecommunictions in all kinds of possible ways thinkable seamless over telco networks and internet. Delivering services supporting a converged lifestyle means that a service should work across networks and services should be aware of each other. The question is what are users ready to pay for a converged lifestyle?

I think that Augustin was spot on when answering the question with an open telecom transforming from channel to the open sea. Users are not willing to pay for the converged lifestyle itself. However, they will use the open telecom services/enablers to mashup new services. As they are doing this and paying for these mashed-up services they are actually creating the converged lifestyle. So the answer is to expose the different services like IP-TV and let the users create the convergence and inclusion in their lifestyle.

Low cost to fail for which convergence is actually asked for and customer willing to pay for.