Solaiemes RCS-e API technology compatible with Newpace RCS-e core solution

We are glad to announce the compatibility between our RCS-e 3rd party REST API Exposure technology with the Newpace RCS-e Core.

The Solaiemes RCS-e 3rd party REST API Exposure technology was tested with the Newpace RCS as a Service product core. When combined, these two products provide operators’ an RCS-e in the Box solution with an RCS REST API exposure that allows our customers to create third party services and web access clients on top of NewPace’s hosted RCS-e/joyn services seamlessly.

Newpace RCS-e as a Service (hosted) allows telcos to deploy RCS-e/Joyn minimizing the CAPEX investment. Solaiemes platforms can be also offered "as a Service"(link), making feasible for MNOs to deploy in a very short time RCS-e service with additional services as web access and 3rd party services on top of the basic Joyn services created with REST API.

We are putting the each one innovation overcoming the issues (or myths) that stopped RCS-e deployments:

- No need of a full IMS draining CAPEX budget.
- Having from the beginning a platform for innovations by 3rd parties (CRM services, internet mashup, user generated content in social media using Joyn features from your phonebook, etc).
- Affordable alternative for MVNO's and non tier-1 MNOs to launch RCS-e with a minimum investment and no risk.

For us it is important proving that vendors are cooperating to help telcos to deliver the next big thing in messaging and add value to the telco enablers.
(read the post by Newpace).

Is "Solaiemes RCS-e REST API" Cloud based?

We are being asked whether the way we expose RCS-e capabilities as REST API is "cloud". Well, our platforms are instancing RCS-e Virtual Clients, behaving as "clients" and exposed to internet. In previous post we explain how our platforms installed in the MNO premises become an "extra mile" of their infrastructure, following the SBC. But it is not the only one possible way of using our infrastrucute. We may also install it directly in internet and the virtual RCS-e Virtual Clients (services or web clients) will be registering to the telco RCS-e via internet as device client does.

Even the MNOs are preferring to have "all what they consider infrastructure" in their datacenters, this Cloud based RCS-e API exposure is the way that we are currently providing remote demos and engagement/try&buy pilots, and the interoperation is very easy to the telco core, only need to know the IP Address of SBC or P-CSCF. Yes, it works. Also it has additional advantadges as RCS-e Solution Gateway and RCS-e Thin Client Server are multitenant and can instance RCS-e Virtual Clients in different MNOs/cores/domains. Yes, we need to be flexible and it allows to offer the RCS-e REST API exposure as a Service :-)

Right now, there are appearing vendors with a RCS-e Core as a Service solution (or RCS-e in a Box cloud based) as Newpace. Then it is possible partnering to create a bundle of RCS-e as a Service offering plus our Value Added Services and Thin/Web Client access on top of RCS-e enabling platforms. You can see the chart. It becomes a nice way to deliver #telcoOTT RCS-e with no CAPEX investment.
From the point of view of where our platform can run it is possible both, in dedicated servers, or in public cloud virtual machines, all combinations tested and working fine :-) Then, we can say that Solaiemes is a cloud communications infrastructure/service provider. Feedback welcomed.

Our view about trending topic: Cloud/SaaS market opportunities & challenges.

In these slides we analyze our view about how IT is being changed with the irruption of Cloud & SaaS technology trends and the opportunities and also challenges it will offer for all players.

Solaiemes signs the Open Cloud Manifesto

Solaiemes joined the Open Cloud Manifesto initiative. The ultimate goal of the Manifesto is to make the cloud as open and valuable as possible. Solaiemes believes in the cloud not only for enterprise or personal computing areas but mobility cloud based solutions.
We are happy joining the list of supporters including huge companies as Cisco, Sun, AT&T, Telefonica, IBM and also amazing start-ups.
We are glad to see spanish start-up's very focused in exploring the possibilities in the cloud as SaaS areas as EyeOS, Abiquo, Litebi and others also joining.
We strongly believe in openess as global opportunity and consider a huge step in the right way to find huge companies also supporting standards and looking for an extended community including start-up's of the ecosystem of "the cloud" that is being placed as "early stage". We think this "spirit of collaboration" will be a key point to succed both, technology and ecosystem.

To download the full manifesto in pdf here.

Equality in Mobility User Experience, Is it a dream? No, it is a Right

Hi, 2 weeks ago we talk about a "mobile cloud" alternative to "mobile applications", today we want to show with a real demo how it is possible to provide very good user experience for mobile solutions in mid-tier devices, and it means to deliver "mobility value" for everybody. In this video we compare our network based solution with iPhone and a 3G device (not smartphone) and create for both the same multimodal experience based on browsing, voice call, Solaiemes AVISG usability platform and IVR/ASR/TTS SaaS capabilities from 3rd parties.



Obviously, smartphones have computing advantadges, larger display, touch, etc...but we must take in count that powerful 17" laptops are far away more capable than 9" netbooks and netbooks are beoming now (using browser as cloud based applications enabler) the perfect machine for most of use cases. This is the point we want to evangelize as new trend of mobility, common devices are enough for very rich experiences. Carriers, suppliers, content providers should work together to improve user experience for all mobile subscribers, Solaiemes in pushing for that :-)
feedback welcome

Mobile cloud capabilities VS mobile applications

Lately, there is some "buzz" about 2 debates, initially independent but finally related. First one is related to the innovating capabilities around "the voice" in mobile and web services, and the other one is about the mobile application trend.
When discussing the topic of using "voice" to enhance user experience in mobile services people inmediately think in adding ASR/TTS capabilities to the handsets. This aproach in our opinion has 2 weaknesses: a) you are restricting "rich user experience" capabilities only to smartphones and it means reducing the critical mass of potential users and b) ASR/TTS capabilities as mobile app are far away less capable than server based. For navigate the mobile menu, address book, etc, could be ok, but not to be used in complex multimodal browsing by users using a "close to natural language".
The internet trend is reducing device capacities (less HD storage, slower processor, small display, RAM memory reduced) and using a common interface well known (the browser) to run most of "applications" needed in the cloud. (it took time but finally the Richard Ellison prediction comes true once the "network availability, bandwidth and prices are ok").
A lot of services can be offered as a service, using network infrastructure and making really simple launching services, because nothing to install at computer, no compatibility issues, etc. Companies with successful offering capacities or frameworks in the cloud include Amazon (EC2), SalesForce.com, Voxeo, Google, etc...
In the other hand, mobility, the trend is just the opposite, identifying "rich user experience" with high tier smartphones (iPhone, Windows Mobile, Symbian, RIM, Palm, Android) and downloadable application from mobile stores. Why ????
If the mid tier devices are capable enough, with normal mobile enablers (voice, video, sms, browsing and ptt) properly combined you can create amazing use cases, and the price plans are becoming flat rate, we think mobility trend may align the personal computing trend as soon as possible.
If you can send live video to the web from a low tier 3G device why using an external application only available for smartphones?
If you can use your voice to browse you mobile banking site or google search combining voice call + browser using cloud services (Voxeo cloud IVR/ASR/TTS in this case using CCXML/VXML), why installing a thick client only available to few smartphone devices ?
Even being aware of amazing success of Apple Store, and next to be launched by RIM and Microsoft and Android, we encourage people to think about making things easier, and providing best mobile user experience to the big masses. We believe in the Henry Ford approach, give most of people the chance of becoming drivers, we want to deliver the "rich mobile user experience and capabilities" to everybody, not depending on choosing the expensive handsets. Is that disruptive?