Have you ever counted the number of Linux devices at home or work that haven’t been updated since they came out of the factory? Your cable/fibre/ADSL modem, your WiFi point, television sets, NAS storage, routers/bridges, media centres, etc. Typically this class of devices hosts a proprietary hardware platform, an embedded proprietary Linux and a proprietary application. If you are lucky you are able to log into a web GUI often using the admin/admin credentials and upload a new firmware blob. This firmware blob is frequently hard to locate on hardware supplier’s websites. No wonder the NSA and others love to look into potential firmware bugs. They are the ideal source of undetected wiretapping.
The next IT revolution: micro-servers
The next IT revolution is about to happen however. Those proprietary hardware platforms will soon give room for commodity multi-core processors from ARM, Intel, etc. General purpose operating systems will replace legacy proprietary and embedded predecessors. Proprietary and static single purpose apps will be replaced by marketplaces and multiple apps running on one device. Security updates will be sent regularly. Devices and apps will be easy to manage remotely. The next revolution will be around managing millions of micro-servers and the apps on top of them. These micro-servers will behave like a mix of phone apps, Docker containers, and cloud servers. Managing them will be like managing a “local cloud” sometimes also called fog computing.
Micro-servers and IoT?
Are micro-servers some form of Internet of Things. Yes they can be but not all the time. If you have a smarthub that controls your home or office then it is pure IoT. However if you have a router, firewall, fibre modem, micro-antenna station, etc. then the micro-server will just be an improved version of its predecessor.
Why should you care about micro-servers?
If you are a mobile app developer then the micro-servers revolution will be your next battlefield. Local clouds need “Angry Bird”-like successes.
If you are a telecom or network developer then the next-generation of micro-servers will give you unseen potentials to combine traffic shaping with parental control with QoS with security with …
If you are a VC then micro-server solution providers is the type of startups you want to invest in.
If you are a hardware vendor then this is the type of devices or SoCs you want to build.
If you are a Big Data expert then imagine the new data tsunami these devices will generate.
If you are a machine learning expert then you might want to look at algorithms and models that are easy to execute on constraint devices once they have been trained on potentially thousands of cloud servers and petabytes of data.
If you are a Devop then your next challenge will be managing and operating millions of constraint servers.
If you are a cloud innovator then you are likely to want to look into SaaS and PaaS management solutions for micro-servers.
If you are a service provider then this is the type of solutions you want to have the capabilities to manage at scale and easily integrate with.
If you are a security expert then you should start to think about micro-firewalls, anti-micro-viruses, etc.
If you are a business manager then you should think about how new “mega micro-revenue” streams can be obtained or how disruptive “micro- innovations” can give you a competitive advantage.
If you are an analyst or consultant then you can start predicting the next IT revolution and the billions the market will be worth in 2020.
The next steps…
It is still early days but expect some major announcements around micro-servers in the next months…
Although the number of solutions Amazon AWS is offering has become very large, here are 5 ideas of what Amazon could be adding next.
There are thousands of APIs out there. However what is missing is an easy way for companies to control their costs. In line with other marketplaces Amazon runs, there could be an API marketplace. An API marketplace would allow third-party API providers to let Amazon do the charging. Companies would be able to pay one bill to Amazon AWS and use thousands of APIs. Also third-party API providers would be winning because they often can not charge small amounts to a large set of developers. Amazon already sends you a bill or charges your credit card, hence adding some dollar/euro cents for external API usage would be easy to do. The third-party API provider would avoid having to lock-in users in large monthly usage fees to offset credit card and management charges. Amazon of course would be the big winner because they could get a revenue share on these thousands of APIs. End-users would also be winning because they can easily compare different APIs and get community feedback from other developers and pick those APIs with the best reputation. The typical advantages of any online marketplace. Also cross-selling, advertisement, etc. and other areas can be reused by Amazon. A final advantage would even be to have Amazon be in the middle and offer a standard interface with third-parties offering competing implementations. This would allow developers to easily switch providers.
A lot of applications would be helped if they could use language APIs that are paid per request. Language APIs is a group name for text-to-speech, speech recognition, natural language processing, even mood analysis APIs. These are all APIs that are available individually but there is a clear economies of scale effect. The more speech you transcribe or text documents you process, the better your algorithms become. Also there is an over-supply of English language APIs but an under-supply of any other language in the world, except for Spanish, French and German perhaps. Another problem with existing APIs is that a high monthly volume is needed in the even the most basic subscription plan. Examples are Acapela VaaS pricing that costs a minimum of €1500. Very few applications will use this amount of voice.
M2M APIs and Services
Amazon is already working hard on Big Data solutions. M2M sensors can generate large volumes of data pretty quickly. S3 or DynamoDB would be ideal to store this data. However what is missing is an easy way to connect and manage large number of sensors and devices and their accompanying applications. There are few standards but with examples like Pachube, Amazon should be able to get inspired. Especially the end-to-end service management, provisioning, SLA management, etc. could use a big boost from a disruptive innovator like Amazon. Also M2M sensor intelligence could be offered from Amazon, see my other article about this subject.
Mobile APIs and Solutions
With billions of phones out there, mobilizing the Web will be the next challenge. Securely exposing company data, applications and processes towards mobile devices is a challenge today. BYOD, bring-your-own-device, is a headache for CIOs. We do not all have a MAC so we can not sign iPhone apps and launch them on the App Store. Ideally there would be a technical solution for enterprises to manage private app stores, deploy apps on different devices and be able to send notification to all or subsets of their employees. Also functionality like Usergrid in which developers would not have to focus on the backoffice logic would be of interest. Also tools to develop front-end for different devices would be appreciated, examples like Tiggzi come to mind. There are a lot of island solutions but few really integrated total solutions.
Support APIs and Services
Amazon is becoming more and more important in the global IT infrastructure business. This means that solutions will move more and more to the Cloud and sometimes be hybrid cloud. With these complex solution scenarios in which third-parties, Amazon and on-site enterprise services have to be combined, risks of things going wrong are high. Support services both from a technical point of view:
- detect failures and to automatically try to solve them
- manage support ticket distributions between different partners
- measure SLAs
as well as from a functional point of view:
- dynamic call centers with temporary agents
- 3rd party certification programs in case small partners do not have local resources
- 3rd party support marketplace to offer more competition and compare reputations
are all areas in which global solutions could disrupt local and island solutions that are currently in place.
M2M sensors are predicted to generate more data than their human counterparts in the coming years. Unfortunately the price that will be paid for moving this traffic will be substantially lower than human data traffic. So it makes sense to think about ways to dramatically reduce the amount of data M2M sensors transmit.
How to do it?
In recent weeks I have been playing with RapidMiner. This program might be soon installed on a lot of Windows machines next to MS-Office. RapidMiner allows complete data mining layman to easily get hidden information out of the data they have at hand in files, Excels, Access, databases, etc.
RapidMiner shows how with some simple drag-and-drop in 5 minutes you can use complex algorithms like Neural Networks, Support Vectors Machines, Bayesian Classifiers, Decision Trees, Genetic Algorithms, etc. to make sense out of data.
The fact that you can easily train an algorithm to take a decision on your behalf could be a key factor to reduce the amount of M2M sensor data. So instead of sending all the data to a central point and making decisions there, you would put intelligence into the sensors.
This artificial sensor intelligence would not only be limited to single sensor failure. By applying genetic and swarm algorithms and copying mother nature, you would be able to have different sensors behave like for instance an ant colony. Individual sensors would start sharing alarm data and if enough or the right sensors agree then they would launch collective alerts.
Wireless technologies based on for instance White Spaces technologies can be used, and are already used for instance in Cambridge, to cheaply have many sensors communicate with one another. Also harvesting techniques should be used to avoid having to install batteries into the sensors.
The last part of the puzzle would be extra features in a M2M PaaS to manage the distribution of intelligence for de-centralized and self-organizing sensor networks. Sensors are likely to send data to a central server in which humans will have to train computers on what type of data is critical. Once the trained models are available, then they can be distributed to sensors. The M2M PaaS would focus from then on, on adjusting the algorithms in case certain alarms were not caught or when alarms were launched unnecessary.
If you are a VC and you are unclear where to invest then this post might be of interest to you.
Some Disruptive Technologies and ideas that startups might be working on or for which you might want to assemble a team:
WiFi and 3/4/5G have their limitations. Any alternative networking technology that can change complete industries is probably a good pick. An example would be LiFi.
Networks as a Service – Software-Defined Networks – Openflow
This area is very hot at the moment. Today’s network are very hard to configure and manage, they are very tightly-coupled with hardware, they can not be extended easily.
Anything that makes Software-Defined Networks/Openflow easy for mass adoption is going to be a winner.
Anything that allows enterprises to buy a box once and get the network software later based on day-to-day business requirements, e.g. think about appstore for Openflow.
Anything that links Openflow to the Cloud.
M2M Disruptive Technologies
Printing electronics to make sensors cheaper.
Battery-free electronics to make sensors more mobile and less expensive to maintain.
Auto-discovery sensor mesh networks to avoid paying expensive 3/4G subscriptions.
M2M appstores to allow people to reuse the work others did.
Super-easy M2M APIs/PaaS. Look at Pachube as a model to beat.
Cloud Disruptive Technologies
Niche SaaSification in which applications that are only used in small niches can be offered as SaaS subscriptions in a global way.
Plug-and-Cloud Equipment for Hybrid Cloud & Exposure (Single Sign-on, Internal data sources, Internal integrations) – on-site equipment that allows enterprises in an easy and secure way to expose their internal assets to the Cloud e.g. employee single sign-on, secure exposure of company data, secure exposure and easy integration of company applications
Plug-and-Play SaaS integrations that allow multiple SaaS offerings to be easily integrated without programming.
Mobile PaaS = mobile GUI drag-and-drop designer + no-programming back-end systems like Usergrid + plug-and-play integration with external and enterprise APIs + enterprise mobile app / SaaS stores + BYOD made easy solutions (some elements are optional)
Big Data / Data Analytics
Big Data PaaS (easy tools/APIs for complex big data operations like mood analysis, natural language processing, etc.)
Kaggle type of services but for other domains e.g. competition to create the easiest/best mobile interface or API
Kaggle + Kickstarter => competition together with crowdfunding. Who can build the best solution for this problem, gets their venture funded.
Nail-it-then-scale-it/Lean Startup type of crowdsourcing in which ideas get tested (e.g. paper prototypes, business model discovery, etc. before actual prototype) and funding is delivered bit by bit. Ideally with stock options of the funders in the new venture.
Managed enterprise software-defined networks or BYOD – services that help enterprises to maintain their networks or devices that employees bring along in a managed way hence no experts need to be hired and the service is pay-as-you-go instead of CAPEX.
Cloud + Set-up Boxes – Appstores for ADSL/Cable Modem set-up boxes, SDKs to manage large sets of consumer’s set-up boxes, etc.
These are just a handful of ideas. If you want more or need more detail, let me know at maarten at telruptive dot com. Also if you are in need of an external adviser or executive in a new venture, let me now…
In the computing trend that will change everything, MIT’s Technology Review is showing how power consumption for computer resources has improved at the same speeds as computer chips. Especially the analogy of a Macbook Air with the efficiency of a PC from 1991 would run through a fully charged battery in 2.5 seconds. The trend is to continue with wireless no-batteries sensors. Sensors that get their energy from harvesting existing radio waves. Find out more on powering the internet of things without batteries.
Imagine the possibilities if sensors did no longer have to have batteries. Everything from traffic, the weather, human health, retail, etc. can be revolutionized. Mobile sensors will start generating massive amounts of data, called nanodata. The sensors are unlikely to hold a SIM because of the importance of energy efficiency. Operators should look for M2M business models that go further than only connectivity and should think about low-cost and low-energy wireless mesh networks instead of 3G/4G/5G…
LTE roll-outs are taking place in America and Europe. Over-the-top-players are likely to start offering large-scale and free HD mobile VoIP over the next 6-18 months. Steeply declining ARPU will be the result. The telecom industry needs new revenue: telecom revenue 2.0. How can they do it?
1. Become a Telecom Venture Capitalist
Buying the number 2 o 3 player in a new market or creating a copy-cat solution has not worked. Think about Terra/Lycos/Vivendi portals, Keteque, etc. So the better option is to make sure innovative startups get partly funded by telecom operators. This assures that operators will be able to launch innovative solutions in the future. Just being a VC will not be enough. Also investment in quickly launching the new startup services and incorporating them into the existing product catalog are necessary.
2. SaaSification & Monetization
SaaS monetization is not reselling SaaS and keeping a 30-50% revenue share. SaaS monetization means offering others the development/hosting tools, sales channels, support facilities, etc. to quickly launch new SaaS solutions that are targeted at new niche or long tail segments. SaaSification means that existing license-based on-site applications can be quickly converted into subscription-based SaaS offerings. The operator is a SaaS enabler and brings together SaaS creators with SaaS customers.
3. Enterprise Mobilization, BPaaS and BYOD
There are millions of small, medium and large enterprises that have employees which bring smartphones and tablets to work [a.k.a. BYOD – bring-your-own-device]. Managing these solutions (security, provisioning, etc.) as well as mobilizing applications and internal processes [a.k.a. BPaaS – business processes as a service] will be a big opportunity. Corporate mobile app and mobile SaaS stores will be an important starting point. Solutions to quickly mobilize existing solutions, ideally without programming should come next.
4. M2M Monetization Solutions
At the moment M2M is not having big industry standards yet. Operators are ideally positioned to bring standards to quickly connect millions of devices and sensors to value added services. Most of these solutions will not be SIM-based so a pure-SIM strategy is likely to fail. Operators should think about enabling others to take advantage of the M2M revolution instead of building services themselves. Be the restaurant, tool shop and clothing store and not the gold digger during a gold rush.
5. Big Data and Data Intelligence as a Service
Operators are used to manage peta-bytes of data. However converting this data into information and knowledge is the next step towards monetizing data. At the moment big data solutions focus on storing, manipulating and reporting large volume of data. However the Big Data revolution is only just starting. We need big data apps, big data app stores, “big datafication” tools, etc.
6. All-you-can-eat HD Video-on-Demand
Global content distribution can be better done with the help of operators then without. Exporting Netflix-like business models to Europe, Asia, Africa, Latin-America, etc. is urgently necessary if Hollywood wants to avoid the next generation believing “content = free”. All-you-can-eat movies, series and music for €15/month is what should be aimed for.
7. NFC, micro-subscriptions, nano-payments, anonymous digital cash, etc.
Payment solutions are hot. Look at Paypal, Square, Dwolla, etc. Operators could play it nice and ask Visa, Mastercard, etc. how they can assist. However going a more disruptive route and helping Square and Dwolla serve a global marketplace are probably more lucrative. Except for NFC solutions also micro-subscriptions (e.g. €0.05/month) or nano-payments (e.g. €0.001/transaction) should be looked at.
Don’t forget that people will still want to buy things in a digital world which they do not want others to know about or from people or companies they do not trust. Anonymous digital cash solutions are needed when physical cash is no longer available. Unless of course you expect people to buy books about getting a divorce with the family’s credit card…
8. Build your own VAS for consumers and enterprises – iVAS.
Conference calls, PBX, etc. were the most advanced communication solutions offered by operators until recently. However creating visual drag-and-drop environments in which non-technical users can combine telecom and web assets to create new value-added-services can result in a new generation of VAS: iVAS. The VAS in which personal solutions are resolved by the people who suffer them. Especially in emerging countries where wide-spread smartphones and LTE are still some years off, iVAS can still have some good 3-5 years ahead. Examples would be personalized numbering schemas for my family & friends, distorting voices when I call somebody, etc. Let consumers and small enterprises be the creators by offering them visual do-it-yourself tools. Combine solutions like Invox, OpenVBX, Google’s App Inventor, etc.
9. Software-defined networking solutions & Network as a Service
Networks are changing from hardware to software. This means network virtualization, outsourcing of network solutions (e.g. virtualized firewalls), etc. Operators are in a good position to offer a new generation of complex network solutions that can be very easily managed via a browser. Enterprises could substitute expensive on-site hardware for cheap monthly subscriptions of virtualized network solutions.
10. Long-Tail Solutions
Operators could be offering a large catalog of long-tail solutions that are targeted at specific industries or problem domains. Thousands of companies are building multi-device solutions. Mobile & SmartTV virtualization and automated testing solutions would be of interest to them. Low-latency solutions could be of interest to the financial sector, e.g. automated trading. Call center and customer support services on-demand and via a subscription model. Many possible services in the collective intelligence, crowd-sourcing, gamification, computer vision, natural language processing, etc. domains.
Basically operators should create new departments that are financially and structurally independent from the main business and that look at new disruptive technologies/business ideas and how either directly or via partners new revenue can be generated with them.
What not to do?
Waste any more time. Do not focus on small or late-to-market solutions, e.g. reselling Microsoft 365, RCS like Joyn, etc. Focus on industry-changers, disruptive innovations, etc.
Yes LTE roll-out is important but without any solutions for telecom revenue 2.0, LTE will just kill ARPU. So action is required now. Action needs to be quick [forget about RFQs], agile [forget about standards – the iPhone / AppStore is a proprietary solution], well subsidized [no supplier will invest big R&D budgets to get a 15% revenue share] and independent [of red tape and corporate control so risk taking is rewarded, unless of course you predicted 5 years ago that Facebook and Angry Bird would be changing industries]…