Embedded Devices: Big Opportunities in Tiny Packages
We may not notice it, but software is all around us. Much of it is running on embedded devices, tiny computers that many of us would never expect or recognize as such. There’s the smart alarm clock on our nightstand, the scales in the bathroom, the coffeemaker on our countertop, the elevator we take on our way to work. And embedded devices stay with us when we leave the building: trains, trams, busses, cars, even those ubiquitous kick scooters, all have computers hidden in them. Go to the doctor or the dentist, and the tools of their trade will have embedded devices in them. The same goes for building services, the power grid, our phone network, and virtually everything else in modern life.
Only a decade ago, programming devices like these usually meant working on a very low-level Assembler language, just one mental step removed from the actual hardware and its functions, often fixed and set in stone in ASICs. Technology has evolved by leaps and bounds and made embedded devices more powerful, cheaper, and above all, more versatile. Instead of custom hardware, modern devices tend to use standard components, programmed with Java or C without the need for highly specialized Assembler coding experts. This has opened the floodgates for more innovation, but it has also raised the bar when protection, security, and monetization concepts are concerned.
Any entrepreneur who has invested their time and resources into innovations like these want to know that their IP is protected. Their first concerns are piracy and reverse engineering: Users might buy fakes or forged products by intent or by mistake, eroding considerable business from the original makers and potentially harming their reputation when users inevitably run into trouble with their knock-off products. On top of the threats for the makers themselves, users are at risk as well: Their data, be it sensitive sensor data or valuable production data, needs to be safe from theft, espionage, manipulation, or – currently a hot topic – hijacking.
When it comes to monetizing the resources and IP they have invested into their products, manufacturers generally used to have only one route: Selling the physical devices. In the modern world, business models and monetization options have multiplied: Money can be made by selling additional features and functions ("features-on-demand"). This could be the ability to configure additional axes in an industrial robot: The hardware and software could have the built-in 6-axis controls, but the user would have the opportunity to buy an add-on license to activate additional axes beyond the basic functions if they want to. This makes for leaner logistics, as the manufacturer only needs to sell one type of physical device, and for greater freedom for users to choose which features they actually need.
Another option are time-based licenses, like subscriptions. Users could enter into a leasing contract that allows them to use a device for a defined time with guaranteed updates in that period. The manufacturer benefits from the certainty of regular payments, and the user from lower upfront costs, upgrades to new functions, and permanent state-of-the-art security.
A third monetization option seems synonymous with our times: Apps. OEM or third-party developers can offer additional features in the form of apps that can be bought, licensed, and loaded onto devices. Opening up their ecosystem to third parties in this way can make a manufacturer’s products much more appealing for users and generate additional revenue in the form of licensing fees.
In this masterclass, we are going to delve into:
- A look at embedded devices
- The challenges
- Protection against piracy and reverse engineering
- Security for users
- New licensing models for developers
- CodeMeter Runtime and its variants
- CodeMeter Runtime / CodeMeter Embedded / CodeMeter µEmbedded
- Different areas of application
- Software integration
- License logistics
Join the webinar to discover how CodeMeter can fulfill your protection, security, and licensing needs, which flavors of CodeMeter are used for which purpose, and how they can be integrated into your software and logistics processes.