Comverse Acquires Solaiemes to Broaden its Digital Services Portfolio.

Acquisition Further Enhances Comverse’s Value Proposition to Service Providers Seeking to Evolve to Digital Lifestyle Players through RCS, WebRTC and Monetization

Key Takeaways:

• Accelerates Comverse’s Digital Services Portfolio with elements such as WebRTC Gateway, and the Industry’s first GSMA accredited RCS API Gateway
• Expands engineering expertise and talent in the IP Messaging and Digital Services Domains
• Makes Comverse’s Evolved Communication Suite the most comprehensive Digital Services offering in the Industry

WAKEFIELD, Mass., August 5, 2014 – Comverse (NASDAQ: CNSI), a global leader in telecom and enterprise business enablement, announced today its acquisition of Spain-based Solaiemes, an innovator focused on enabling the creation and monetization of Service Providers’ (SPs) digital services.

Solutions from Solaiemes complement the market leading Evolved Communication Suite (ECS) offering from Comverse, and the combined portfolio creates an end-to-end platform for service monetization of IP based digital services.

Quotes:
“Unlike other players in the digital economy, Comverse is unique in its product offering that enables SPs to both deliver and monetize digital experiences.” said Aashu Virmani, VP Product Management and Product Marketing of Digital Services at Comverse. “Solaiemes’ technology strengthens Comverse’s Evolved Communication Suite (ECS) portfolio, which enables SPs to become digital lifestyle players by easily and quickly launching innovative digital services with means to monetize them.”


Supporting Facts:

• Comverse ECS offering won TMC’s 2014 “Product of the Year” award, and the 2014 COMET Innovation award.
• Solaiemes’ RCS API solution has won the GSMA RCS Innovation Award, and is the only GSMA accredited RCS API product certified with Joyn Blackbird.
• The combined products are currently in trials at several Tier-1 service providers.
• You can learn more about Comverse’s Evolved Communication Suite here.
• By 2016, the number of devices supporting WebRTC is expected to exceed 4 billion.
• Terms of the deal were not disclosed. The company does not expect the transaction to have a material impact on revenue or profitability for the quarter or fiscal year.

About Comverse
Comverse is a leading global provider of telecom business solutions that enable communication service provider success in the hyper-connected world through service innovation and smart monetization. The company’s proven and innovative product portfolio includes BSS, Policy Management (PCRF) and Enforcement, and Digital Services – all backed by Managed and Professional Services. Comverse’s extensive customer base spans more than 125 countries with solutions successfully delivered to over 450 communication service providers serving more than two billion subscribers. Comverse’s solutions are available in a variety of delivery models, including on-site, cloud, hosted/SaaS and managed services. For more information, visit www.comverse.com.

Statements included or incorporated by reference in this press release may contain “forward-looking statements.” There can be no assurance that any forward-looking statements will be achieved, and actual results could differ materially from forecasts and estimates. Important factors that could affect the company include the risks described in the section entitled “Forward-Looking Statements” Item 1A, “Risk Factors” and elsewhere in the company’s Annual Report on Form 10-K filed with the SEC on April 16, 2014 or in subsequently filed periodic, current or other reports. The company undertakes no commitment to update or revise forward-looking statements except as required by law.

TadHack 2014 in Madrid summary. Telco APIs matter.

Solaiemes sponsored TadHack 2014 event. Our company product is about telco APIs, and it was "the event". It took place in Madrid the past weekend and among the developer resources we offered RCS API Developer Portal & a WebRTC SDK to be used with Nexmo lines.

It was incredible how several satellite events provided very good entries, and how in 2 days onsite developers coming from different countries coded their hacks.

It was a pity that not many telcos sent people to see "where the money will be" but we are sure next year they will be. Thanks to all the telcos present. We could have good chats and also other tech vendors providing complementary APIs. And thanks to the brave developers who used our RCS API, they are the ones that could be named pioneers :-)

We are sure soon Alan Quayle will be postint his own summary with all the details, the decks used and pointers to the hacks.

Also, we were interviewed briefly about the reasons to participate in TadHack and why the telco APIs will be key.

You can find more pics (until the official gallery will be published by TadHack) in our Facebook Page here.
Hope to be next year at TadHack 2015

TadHack Fuenlabrada satellite event summary.

Solaiemes has partnered with Universidad Rey Juan Carlos (a public university in Madrid) to setup a Telco API workshop for Telecommunications and Computer Science students, as academic extracurricular activity, in the context of TADHack 2014.

The event aimed to give a glimpse into the fascinating world of APIs in general, and Telco APIs in particular, and setup very simple examples using some of the resources available as part of TADHack 2014.
The seminar was very brief, 6 hours in 2 days, it is hard to cover such a broad field, but we indeed tried. A step by step explanation of a RCS-base simple messaging service and deploying a WebRTC dialer application in just a few minutes was part of the seminar. We hope the students got a firm grasp of the importance of telco-related services and APIs, both as a very dynamic technology arena and a potential professional focus for their upcoming entrepreneurial projects or job seeking plans.

Thanks to Pedro de las Heras (@pheras) from the URJC TIC department to help setting this up and to Alan Quayle for their encouraging opening remarks to the event.

Additional pics from the event in our Facebook Page photo album

TadHack WebRTC exposure for Nexmo VoIP lines

As you know Solaiemes is sponsoring TadHack event and providing the RCS API portal to allow developers to get familiar with rich chat possibilities to create valuable interactive services.

As Nexmo is offering its VoIP lines for the hackaton we just prepared a "beta" way to use their lines with WebRTC. In this site the developer can introduce the credentials of the Nexmo lines and get the credentials to use that line with the WebRTC SDK. No need additional registration, if you registered in the Nexmo portal you only need to get your WebRTC SDK credentials linked to your line.

There are included a couple of examples including the code source that can be downloaded, a dialer and a clic2call.

We will keep it live for the Hackaton.

Enjoy the hack!

Solaiemes shortlisted for an IMS Industry Awards 2014 in the RCS Package category.

We're delighted to announce that we have been shortlisted for an #IMS Industry Awards 2014!

The winners will be announced during the IMS World Forum 2014 next week.

We compete in the Best RCS Package with our RCS Monetization Suite package that includes RCS network API and related monetizable tools that telcos can trial with an unbeatable offering.

For us it is very rewarding to be be competing with public companies and VC backed companies and cross the finger that this could open doors for growth, new customers, partnerships and investors.

Also, Solaiemes will participate and showcase demos in the WebRTC preconference Workshop showcasing how telcos can monetize WebRTC, both, exposing as web its voice, and also using WebRTC to create a myriad of innovative services combining web and telco.

Stop talking, start playing the game. Solaiemes RCS Monetization Suite trial unbeatable offer.

Messaging is a hot space and, late but finally happened, telcos are realizing about the risk of becoming the feared "just pipe" if they leave the communication services space.

Amazing OTT apps made mandatory to offer person to person multimedia messaging for free and telcos need to offer a compelling messaging and at the same time discover how to monetize fairly the service.

It's OK, Solaiemes was working almost 4 years to prepare this moment, we build not only the pioneer and most innovative RCS network API but also additional monetization elements as the Developer Portal, RCS Store and RCS Ad Server to innovate in mobile advertising using chat based context "non-push". All our infrastructure can be cloud based and connected easily to whatever RCS core solution. As it makes no sense to launch or be testing RCS in a lab without exploring user engagement VAS and monetization capabilities we would like to present our offering to telcos:

6 Months of hosted Solaiemes Monetization Suite infrastructure including:

- RCS Network API Gateway
- RCS Developer Portal using 3Scale as API Manager
- RCS Store
- RCS Ad Server
- RCS Web/FirefoxOS client based on network API.
- 250 engineering hours for support, training, or creating API based B2C proof of concepts at your request.

TOTAL PRICE: 49.000 € 
& the amount will be discounted if you decide to go ahead and deploy commercially our products in the first licensing PO.

FAQs:

1. Why? Because of it is better to touch the things than just talk about, to build the future you have to touch the pieces as sooner the better.
2. As a telco I would like the trials for free... We understand and would like to do in that way but we have to eat every day, we are not based in the VC paradises and technology for telcos is not their preferred area either :-(. At the same time we think that is a better offering that paying twice or more just to get 50 pages advice from strategic management firms.
3. Can be customized the package with requirements as needing onsite stayings? Yes, let's talk.
4. Is the Solaiemes network API deployed in some telcos? Yes, in 4 tier-1 we can not disclose yet they have our RCS API GW and also the GSMA joyn/RCS innovation accelerator environment for developers is powered with our solutions.
5. What changes are needed in my network to use this trial? Nothing, we only need the RCS or IMS users/pwd and access to IP address of your SBC, the same than configuing device clients.
6. Is it useful without RCS launched commercially and without external develepers? Yes, as you can engage the internal telco geeks to create A2P cases to make the launch more exciting and showing that RCS opened with API is beyond alternative messaging apps regarding use feasible use cases to delight the users.
7. I am not a telco but a complementary technology provider, can we used the trial to create cases to bid jointly in the future to our customer based? Yes, let's talk.
8. As telco I am starting to select RCS core, but we are interested in defining business model and prepare in advance some B2C cases as our own Customer Care based on RCS, can be used the trial without a core? Yes. We can provide a e2e testbed based on Kamailio (the only features you will be missing are group chat and store&forward).

The successful boat is about to sail, come on board !!!

email us at: info (at) solaiemes.com

RCS Monetization Suite

In the past months we have been unveiling additional platforms on top of our pioneering RCS network API GW.

It is time to explain why API itself is not enough in the telco industry today.

We have been talking with many telcos about the possibilities of the API, and they believed in the value, but they think they need huge base of users first. That will not happen if they focus in the person to person messaging where the incumbents today are OTT. We needed to unblock this egg-chicken scenario.

Well, in the last months we have been developing the complementary pieces to the RCS API exposure to move from telco internal trials/PoCs to something they can "sell" to both, enterprise and long-tail developers, engage the final users and the magic world...MONETIZE.

To expose easily the API developers are not keen to call account managers, sign paper contracts, etc...they want a Twilio or Tropo alike portal...and we just used a tier-1 API Management company, 3Scale to offer a RCS Developer Portal cloud based that whatever telco can launch quickly.

As a new way to access to services is born, the rich-chat based interactive cases, it would be needed a way to discover new "chat services" and add to your phonebook, the market of "RCS based cases", and we developed the RCS Store framework to make feasible the "RCS service market" , as standalone app or with API to integrate with RCS clients.

Finally we may talk about money, the well-know sentence "show me the money". Yes, telcos pay a good money to strategy consultants but ask the tech vendors about how to make money :-)

Enabling high rates of API concurrence for B2C is a revenue model with enterprise, but in the other hand, to get adoption telcos need to enrich RCS with casual chat based cases created by developers. How to reward them? Well, in the same way that internet companies are overlapping the telco space and revenue sources, telcos can overlap internet space and their traditional revenue sources as advertisement. Chat based services, person-to-information, person-to-chat-based-game become a new media, providing a context where inserting contextual non-push ads...Yes, the Google model applied to instant messaging. Voilà!, our RCS Advertising Platform fills the gap.

Does it makes sense, doesn't it? Then, bundling all the pieces of the puzzle is what we named as RCS Monetization Suite.

#MWC14 or how RCS is happening without a name.

After the hectic week of #MWC14 and the also hectic post Mobile World Congress week with urgent follow-up's, it's time now to explain our views.

For Solaiemes it was the best MWC ever, more visitors, many meetings with C-level people of telcos and leading vendors, and a lot of unexpected visitors that already knew about our portfolio and interested in include our vision and related portfolio in their future strategy. We can say proudly that had visitors from the 5 continents :-)

This year GSMA did not reserve an specific RCS or joyn area. The RCS acronym is included in the Future Communication space and the commercial brand, joyn, is quietly being removed. Only in a few pods in the Connected City and Future Communication areas RCS use cases were demoed. Does it mean that RCS is being discarded? NO, just the opposite, a lot of telcos are issuing RFP's, and talked openly about plans with us. RCS will happen as messaging evolution, perhaps it does not need new names but providing new experiences and associated use cased based on messaging. Just our vision. Some of the people we talk with expressed our same opinion, we need our own messaging, and SMS is not enough today. It seems that RCS is now in the scope of enlightenment.

Also, we received many visitors interested in how WebRTC can be used by telcos, not only to expose their legacy enablers as voice but to create a myriad of new services. We returned with the batteries full of charge to walk the extra-mile and help to change the telco industry :-)

Apart from the RCS API Gateway for A2P and RCS Web Access, it has been demoed the Personal Manager, an specia RCS AS with additional features for the enterprise market. The idea is solving the overwhelming messaging mess creating personalized filters and autoresponses far more ambitious than the limited white/black lists.

And last but not least we just read a couple of mentions.
We were mentioned in the Frost&Sullivan MWC 2014 Key Takeaways slides by Ronald Gruia.

Also we were mentioned by Andre Rios from Barcinno.com talking about Telco APIs and listing Solaiemes as interesting company together big names as Apigee and Aepona.

Now, it's time to work even harder, this year will be our year!

Solaiemes in the WIPjam developer event at #MWC14

Apart from exhibiting at the #MWC14 Solaiemes will be this year actively participating in a new collateral event, WIPjam, an event to engage de mobile developer community. We will be participating in:

• Telco API Workshop with representatives from very important companies Deutsche Telekom Developer Garden, Apigee, Broadsoft, Intel and the GSMA.


• Innovation Mashup Hackaton our technology exposing RCS as API will be used with other APIs from companies as Apigee, Dejamobile and Orange Partners.


• Expert Table where we will explain our strategy for developer engagement and RCS Monetization. Other companies participating in the Expert Table include Mozilla, Orange, Canonical and Dejamobile.

 We are ready for networking...

See you there !!!

Solaiemes to exhibit at MWC 2014.

As previous years Solaiemes is  exhibiting at the Mobile World Congress 2014. Our stand will be located in the Spanish Pavilion in the Congress Square in the corridor communication the Halls 4 & 5. In the Pavilion our Stand is the number 14.

Solaiemes is presenting its new products with the focus on helping telcos to monetize new enablers as RCS (Rich Communication Services) and tools as WebRTC.
Solaiemes has the right portfolio at the proper time to market but needs strong commercial partnerships (you know, in this telco world size matters) and/or get additional funding for the growth stage. We are interested in meeting:

- Telcos: mobile, fixed, triple play or even OTTs eager to integrate RCS/joyn in their offerings with monetizaton platforms and also interested in WebRTC to generate telco revenues.
- Investors: yes, we are looking for some fuel to accelerate our growth. Yes, we know that Spain is no a sexy country for VC's and telco technology is not the preferred area for investors, but we keep trying :(
- Partners: complementary technology providers or integrators wanting to pioneer RCS and WebRTC in their countries integrating our solutions.
- M&A guys from companies interested in expanding portfolio through selected acquisitions.

If you want to schedule a meeting contact us at: mwc (at) solaiemes (dot) com
See you there !!

RCS Monetization Webinar, the slides.

We started yesterday a series of Webinars with a RCS Monetization one. Thanks to all the attendand online and offline to the seminar for their time and providing feedback with previous questions and a short final survey. We decided to make public the slides as we are pioneering this area, we know some competitors will be copying our pitch soon. It would not be the first time but copying slides is easy, make it happen is more difficult :-)


If you want to make it happen and think RCS can be a monetizable service from the beginning, visit as at Mobile World Congress!

Solaiemes Webinar. RCS Monetization & API blue ocean. Tuesday Jan, 21st.

Solaiemes pioneered the vision of RCS as a Platform to make feasible for telcos to evolve from SMS but keeping the B2C/A2P capabilities of monetization and customer engagement.

Now, Solaiemes, 1st available RCS network API (UNI, plug&play on top of whatever RCS core solution, IMS and not-IMS based) is expanding the VAS layer with additional platforms to speed-up RCS adoption by marketers and also increase the possibilities of engagement of customers.

In the past months we have been presenting VAS platforms using RCS API to create new revenue streams, now we want to explain in a Webinar our vision and compare with what OTTs are doing, and define an strategy to make the telco IP messaging a strong player & how to do it. Join our Seminar.

Solaiemes RCS API supporting WebSockets. Why it matters.

We are receiving as of lately many questions about WebSockets and Telco APIs.

Solaiemes started implementing WebSockets interfaces accross all our infrastructure in 2013, with working prototypes available since the summer. We are sharing now that experience to help the operators looking at this topic. Most likely WebSocket support will be included in the RCS OMA API spec soon and Solaiemes wants, among other API flavours, offer the standardized for the customers requiring it.

In our experience, WebSockets is first and foremost useful for Telco API developers as an additional notification channel. Existing notifications can be reused without any change, because WebSockets provide a native framing mechanism and it is agnostic about the format. Existing notification processing code can be reused.

This approach makes even more sense as in many cases WebSockets won't be available (for example, behind some corporate firewalls), so it is advisable to keep existing channels (native messaging, long polling, etc.).

From the developer point of view, it is just needed to plug (or activate) javascript plugins that automatically manage the transport used (long polling, web sockets, etc.), such as Atmosphere, Socket.io, etc.

On the infrastructure side, a new notification transport is added, but existing APIs can be kept, as REST or whatever format, because there is no need to move the whole API package to WebSockets.

Solaiemes has also API invocation over WebSockets implemented. It is very easy to transform an HTTP-based invocation model (REST or pseudo-REST) to WebSockets, but in our experience the benefits are not so evident, specially as WebSockets are not as ubiquitous as other HTTP mechanisms and scalability solutions do not play well with WebSockets in some scenarios.

WebSockets may be used where its use has a positive impact but not in the cases that its applicability is a mere "reinventing the wheel" without no straightforward advantage.

New minisites explaining our RCS API + VAS Platforms & WebRTC portfolios.

We created a couple of months ago a "back to school" style mini-site to explain the concept of RCS as a Platfom and detail our products related.

Past 2 weeks we created 2 additional mini-sites with "boards" to explain additional pieces of our portfolio.

To explain the WebRTC for Telcos approach the new minisite explains our WebRTC portfolio showing the webphones and RCS web clients and also the SDK to create easily services, all of them based in our WebRTC-Telco Gateway product.

Also we included the powerful concept of the "WebRTC Telcos Services portal with a demo of portal with innovative services.

And finally, a third minisite explains our vision of "chats in your apps / in-chat services". How group chat becomes thanks to the RCS API in something cooler and more useful.

We envision the group chat as something dynamic, where "chat based bots" can be included temporarily to provide fun (chat based games) or productivity (recorder, translator, group access to a travel agent, etc).
You can see the web "Apps in your Chats"

We are working to also refurbish our corporate site www.solaiemes.com :-) Hope to be on time for the coming Mobile World Congress, we need to make clear what we have to help telcos to keep a relevant role.

2013 recap and...Happy New Year 2014!

We want to wish all of you but specially to our customers, partners, followers, fans and prospects :-) a happy new year.



2013 Recap:
2013 was a challenging year for us. Finally the carriers are taking seriously that they need a messaging alternative, that SMS is great but right now, a multimedia messaging using all the possibilities of the smartphone devices and the speed of 3G and 4G networks are needed.

Also, the new messaging market with free/very cheap alternatives forces service providers to think about how to monetize, and they are realizing that the potential is in the VAS, using the API. We were pioneers in this vision and were awarded by the GSMA 2 years ago, now we see our competitors repeating our pitch.

We can say we have API GW being trialed succesfully in 4 tier-1 telcos and expect some of them going to commercial models. While competitors are trying to replicate our vision we are thinking in the next layer of value, specific servers for messaging monetization as RCS Store, RCS Developer Portal and RCS Ad Server to introduce first time the contextual advertising using the chat as media.
Also we are reinventing the group chat with the "apps in your chats" concept. Telcos are in the crossroad between becoming pipe or instead to become "real service providers" offering new services that could add revenue, our goal is to help them to stay relevant and keep a role in future communications.

Also this year 2013 was the year of WebRTC and we started to create our own technology, initially to complete the RCS API GW and put voice and RCS videoshare on the internet browser without plugings but finally we extended to a full WebRTC-Telco GW with an SDK enabling the development of innovative new Telco and Telco bridging OTT services. We can say we are already competing in tier-1 telcos RFQs with this product too.

But 2013 is coming to and end and we have some goals we could not match. We were unable to raise a growth VC round (1.2-2 M€) we need to move the company to the next stage by attending and converting many of the presales opportunities we are finding. In spite of the change of mind of some telcos, now keen on working with small companies, to compete in others with need some muscle. Being a tech company based in Spain is not easy at all and sometimes even playing at home is complicated :-(

Solaiemes took off but this coming 2014 we expect to get onboard a new investor that could add the fuel needed to reach the cruising height or a strong tech company with complementary portfolio as partner for go to market.

In the short-term we expect all of you visiting our booth at Mobile World Congress 2014.

Happy New Year 2014
the Solaiemes team

Multiparty RCS Translator. More on "apps in your chats"

Have a look to another demo of the concept "apps in your chats".
Have a look how easy could be have a chat when all the participants have not a common language, they add the translation services as a member of the chat, and get instant translation of each message.

Telcos may realize that messaging is not trying to replicate each OTT messaging new feature but exploring new blue oceans in the use of messaging.



Credits: Solaiemes RCS network API Gateway, Google Translate API, Newpace RCS core and Silta RCS Android Client

RCS "in-chat apps". Multiplayer chat based game demo.

Most of messaging apps are only taking care of person to person messaging only, Solaiemes thinks this is not a "finish-line" but a "start-line".
We created a demo using our RCS API Gateway, the pioneer RCS API in the market to create a multiplayer chat based "trivial-like" game. It is added to a group chat and allows you to start playing with your friends, and after finishing it disconnects from the group. Easy to play with.



It has been created using GSMA joyn innovation accelerator API environment, nothing else.

Which messaging app could be more open today to 3rd party innovation?

Our advice on RCS: telcos, launch soon, launch cloud, launch with API to allow developers to flood of content the RCS platform :-)

Credits: Solaiemes RCS network API Gateway, Newpace RCS core and Silta RCS Android Client

RCS as a Platform. Concept, deploying API easily and Monetization case. New Solaiemes site to explain the how to.

Solaiemes has published a minisite "RCS as a platform by Solaiemes" to make easier to understand the potential of instant messaging as a la platform, how to deploy in days the network API and offer it to the developers and how to monetize "RCS" using as context for advertisement third party cases created with the API.

Yes, RCS has a business case, and can be the initial point for telcos take a slice of the cake of contextual advertising business.

Telcos, it'stime to get down to work and we can help :-)

Rich Communication 2013 event. Our view.

We attended the Rich Communication conference in Berlin last week. Juan, our co-founder participated in the WebRTC workshop chaired by Alan Quayle, you can find the slides here. We participated in 2 pannels discussing how RCS deployments were going and the potential of the API to go beyong the person to person messaging case.

Regarding the WebRTC vs RCS, it was explained how WebRTC is a technology that broadens the telco communication reach for services as voice and RCS media (videoshare and IP Videocall). We made live demos involving WebRTC to provide media in RCS clients, also to create Webphones.

During the 2 days of conference along the many keynotes and panels it was clear that RCS is happening, in different ways but happening. The industry is just intruducing the A/B testing for RCS, some telcos are testing with "joyn" common brand and others are introducing RCS as natural evolution of SMS/MMS. RCS UI is combining RCS chat/file transfer and using SMS/MMS when the other party is not RCS enabled. It was the case of the service explained by Vodafone & Wit.

Also, it is interesting to see potential dual deployments on-net + OTT RCS to try to expand the RCS user base until latecomers will be launching. It was the case of Sprint in the US.

Another of the hot topics discussed was the IMS vs non-IMS deployments. As Brent from Newpace said during his presentations, the last editions of the events the presence of the big NEVs trying to sell the "big IMS concept" was overwhelming and this year the RCS hosted solution vendors took charge of the show.

API, API, API....network API...YES! Not only us but several vendors and telcos emphasized the role of the API and the need to open RCS communication to B2C and other person to "something" experiences. Deutsche Telekom & Orange talked about the Paris to Berling hackaton.
The winner in Berlin was Yeppt and we all saw the video of how a web based service can use joyn to add additional channel for their users to interact with their service.

Other speakers as Naren from DT stated the important role of RCS API with examples of human-service instant messaging interaction.

Some telcos with not yet deployed RCS talk about their plans, how they are issuing RFQs, how they plan to use RCS not only as messaging tool but replacing/improving the A2P business they made along the years with the SMS. We see that our vision is shared with telcos (and we fear that now also with competitors).

In our opinion this was the best edition of the event. There was not taboo to talk openly about OTT competitiors as Whatsapp and analyze the opportunities as B2C comms that Whatsapp is not promoting yet. This a very good opportunity for telcos to take the lead there.

Finally, we are starting a newsletter, please join our mailing list here

UPDATE: find a full review of the event by Alan Quayle here .

RCS Developer Portal as a Service. Revolutioning how telco API may be offered.

We are pleased to announce a new offering, the concept of RCS Developer Portal as a Service. Telcos will be able to launch RCS API at the same time that RCS/joyn service itself. No painful integrations, experiment what plug&play means ;).

The telcos just need to provide connectivity with the telco SBC and a bunch of RCS users (numbers) to be used as developer created services will be enough.

What about the API Management layer? Well, it is not needed to try to reinvent the wheel, the portal front-end and API Management use 3Scale, one of the leading vendors in the API management field. The developer look&feel and the developer plans are fully customizable.





Time now for telcos to use the cloud for their own enablers exposure. Time is money!!!