joyn TV experience. Adding value to the home phone line.

We are happy to show the joyn TV experience. With our RCS-e API from RCS-e Thin Client Server we created an Smart TV App joyn client (using the Samsung Smart TV Hub for Samsung TVs). In the video you can see how even fix carriers can use the home phone number to add media and IP messaging trough the "big screen".
Why not calling your mum after reaching a high summit after hours of hiking and just share your landscape from there on her big TV?

Credits: Solaiemes RCS Thin Client Server API, Silta Neusoft Mobile joyn Client and Samsung Smart TV Hub 

Solaiemes joins the GSMA

We are pleased to announce that Solaiemes has joined the GSMA as an Associate Member (vendor status). Solaiemes since early stage company participated in the GSMA Mobile Innovation Market, exhibited at Mobile World Congress and participated in several GSMA awards competitions.  Finally we are members as the company must join the relevant referent of our industry.
Solaiemes has been pushing RCS-e technology, and making contributions mainly in the RCSe APIs. With the new status we will be able to join the meetings and work more closely with telcos and other vendors pushing ahead RCS-e messaging.

The GSMA represents the interests of mobile operators worldwide. Spanning more than 220 countries, the GSMA unites nearly 800 of the world’s mobile operators, as well as more than 200 companies in the broader mobile ecosystem, including handset makers, software companies, equipment providers, Internet companies, and media and entertainment organisations. The GSMA also produces industry-leading events such as the Mobile World Congress and Mobile Asia Expo.

Solaiemes attended Iberian Telecom Summit

Solaiemes attended and presented its RCS-e portfolio in the Iberian Telecom Summit event in Santiago de Compostela on December 14th.
For us it was a good opportunity to meet new  fix and cable operators which are now acquiring LTE spectrum and looking for applications and solutions to empower their offering. Also VoIP carriers were interested in having their own OTT solutions to offer to their customers.
We shared the stage with impressive companies as Acme Packet, Broadsoft, IPtego and the organizer (and our partner in some projects) Quobis :-) It is incredible how many companies are working hard to deliver outstanding solutions to the carriers to help them in the transition from legacy communications scenario to the new IP world with different types of competitors.
It is important that vendors and carriers will meet in this kind of events to share views and find spaces of cooperation. We are here to help them improve their business and customer loyalty.
Looking forward the next year one !!!

Solaiemes "RCS-e is a platform" video.

We have explain in several posts our views about the telco messaging possibilities and how we envision RCS-e as a platform, a common experience to create person-to-solution, and ubiquitous person-to-person use cases on top. We have compiled several of the things of our RCS-e API technology is making feasible. Feedback welcome.

Solaiemes explained its RCS-e as a Platform vision in Telco 2.0 event.

Solaiemes participated in the New Digital Economy event, organized by STL partners (the original coiners of the term "Telco 2.0"), on Nov 9th. This is a "must attend" for strategists and anybody interested on, as the event name says, "Strategic Threats and Opportunities" for telco service providers.

The agenda covered many different topics and approaches, and RCS was the focus of several sections, with a very nice presentation on what RCS is, how it can complement and live along OTT offers, including a real live demo, by Dr. Rainer Deutschmann, Deutsche Telekom, and Cenk Serdar, Vodafone, and followed by a lively debate.

We were invited to present our view on how RCS-e is as much a platform as an end-user service, and showed some of the possibilities and sample use cases that could be enabled by allowing third parties to use enablers, very well received by an audience that have not been exposed to this approach before in the most part, and with encouraging tweets from the floor.

A very enlightening event, with many different point of views, and a format that encourages and makes very easy participation and exchange of ideas. "Chance Favors the Connected Mind" (Steven Johnson), don't miss the opportunity to attend the next one.

Jose Recio

Our view from past Rich Communication 2011 event in Munich.

Last week we attended the Rich Communication 2011 event in Munich, we participated in a panel defending our view about consider and deploying RCS-e as a platform to enable use cases and not a mere only person to person messaging. We explained our view in the panel, and previously in our demo slot we showed how we are this feasible with APIs and Thin Clients. Also we presented first time the demo of our new product RCS-e Personal Manager.

The G5 representatives from Vodafone, Telefonica, Deustche Telekom, Orange and TIM explained the project and the timeline, with all of them to offer the service by the H1 2012. It seems most of device manufacturers are committed to include RCS-e natively, and GSMA will launch a RCS-e App Client to cover other mainstream platforms (IOs & Android).
There was a lot of discussions about if RCS-e is the SMS replacement or something else (our view), how to monetize, and how to get traction in a very competitive segment with several OTTs (over the top) with interesting solutions.
In our opinion, both, companies creating communication services using the data connectivity (commonly referred as OTT) and telcos may be not considered full antagonists or deadly rivals. We believe in cooperation models and innovation to delight the users. A good communication shared model will allow internet companies with focus on e(m)-commerce, location, etc perhaps try to reach the users using universal communication services rather than creating a new "messenger" only for their use case. The task for telcos is how to design their wholesale offering of API's and perhaps some mediation of API usage to create a powerful model to boost mobility and user/customer engagement.
Finally, from the demos, we may say that there are RCSe available clients from different vendors, device client SDKs, and available server side REST APIs (ours) :-)
The networking was very good with senior representatives from telcos, leading vendors and analysts with different points of view, all of them enriching the discussion.

The technology is here, and time is gold to launch and let the ecosystem work.

A brand new way to RCS-e monetization: End User Confirmation Request API.

RCS-e includes an amazing feature "End User Confirmation Request" (section 12.3 of the spec ), implementing a new mechanism to communicate with the user about the service and query for confirmation (or not) for actions. In the client UI this might map to, e.g., a pop-up or similar UI element.
The original spec talks about a sample use case, accepting an "extra charge" for a large file transfer. Other RCS-e centered use cases can be thought: terms and conditions acceptance, etc.

But we believe this has the potential to much more, it can be extended to profitable, non-purely RCS-e use cases. With an appropriate API, any screen with RCS-e access can use this for any transaction requiring user confirmation or acceptance. With the carriers as trusted partner, and, of course, charging suitable fees.

In many countries SIM owners are legally identified and RCS-e is backed by the IMS security and AAA framework, the telco can send a "End User Confirmation Request" required by a bank to one of the customers making a credit card transacton to confirm (or to ask to introduce the PIN). With this approach telcos have the tool to become a security masterpiece of online transactions, fits naturally in their role as trusted parties, much more than OTTs are right now.

With an open End User Confirmation Request API, that makes easy to 3rd parties to access this capabilities, carriers can become a provider of "identified confirmations" to lots of services that need better mass market security for their mobile online services such as banking, online ticketing, micropayments...and it could be a new revenue stream generators for carriers. In many forums where the RCS-e pricing is discussed the alternatives are only about end user fees, but there is also the complementary alternative of business models billing 3rd parties for securized and registered transactions, a huge market in the "online" era.

The model is simple. The telco host the platform, and registered 3rd parties can request confirmations through RCS-e (using a simple REST-like API) and pay for them and telcos monetize one of the most valuable assets, subscriber relationship and identity, to provide more security for their own subscriber and helping the ecosystem to build more compelling solutions, win-win-win.

Solaiemes is working on this and will shortly unveil it to the world:

• RCS-e End User Confirmation Request Server with REST API.
• Support of RCS-e User Confirmation Request Server pop-up in the Web Clients served from the RCS Thin Client Server.
• Adding new API calls to RCS Solution Gateway to allow 3rd party developers creating services on top of RCS-e to request "securized" transactions trough the carrier "end user confirmation" service.

the Solaiemes team

RCS-e chat with Facebook & Google Talk by Solaiemes

Just to preview our new platform RCS-e <-> XMPP Gateway, an extension of our RCS Solution Gateway product to allow telcos to smoothly interconect their RCS messagin with popular OTT (internet) messaging tooks based on XMPP as Facebook Chat or Google Talk. Soon we will explain more about our platform that does not need hard integration with IMS or IM Server (it is core independent).

The IMS core used in this demo was the Acme Packet Net-Net SMX.
Feedback welcomed

The new Solaiemes RCS-e Web Client for smartphones

We just released a new version of RCS-e Web Client for smartphones served from our RCS Thin Client Server, with the same look&feel as apps, but with the advantadges of web technology (JQuery), no need to install apps, not permission needed from device or OS providers, just using the browser to provide enhanced messaging, person to person and person to application. Just 2 minutes, have a look.



The IMS core used was the Acme Packet Net-Net SMX.
You can also see the screenshots in our Facebook album here
Feedback welcomed

Jose Recio video about Solaiemes.

Jose Recio, talk about Solaiemes story, milestones, product vision, current needs, followed by a portfolio brief review. this video was filmed for the IBM SmartCamp competition.