About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Travelping GmbH
Drives connected cars into the data fast lane with cloud-native technologies
EU data protection regulations and network latency issues can stall advancements in connected vehicle performance. To help auto manufacturers gain real-time Internet of Things (IoT) insights, Travelping used IBM Cloud® infrastructure products and its own Kubernetes deployment to create a cloud-native solution that transports data to the vehicles.
Connected cars often experience latency issues that can affect safety-related insights. Travelping GmbH needed to develop an IT infrastructure platform that could negotiate the challenges of cross-border data management regulations to make IoT networking more efficient.
Travelping knew it needed to get the network closer to the connected devices. With help from IBM Cloud, it used a self-developed Kubernetes cluster to create a scalable, cloud-native packet gateway solution that transmits the data to the vehicles.
Results
for real-time vehicle safety data insights
by providing scalable services on commodity hardware
by transporting the payloads to where the vehicles are
Stuck in the slow lane
You don’t have to be George Jetson or his wife, Jane, to enjoy space-age features in your vehicle. Connected cars take advantage of IoT technology to allow drivers to determine how long a trip will take and issues to avoid along the way, all while streaming a movie for the kids in the back seat. The ability to connect devices in vehicles to other devices and networks produces insights such as automobile status, position and speed. These insights can improve passenger safety and vehicle maintenance, among other benefits.
But in the EU, there’s a roadblock of sorts: the General Data Protection Regulation (GDPR). Enacted in May 2018, the GDPR is designed to protect data and privacy for EU citizens and those in the European Economic Area (EEA). In part, the GDPR doesn’t allow personal data to be exported outside the EU and the EEA. When you have a connected car but your data isn’t allowed to leave the region, the ability to gain vehicle insights stalls. Traditional network solutions aren’t ideal, because that’s where the latency comes in.
Let’s say car manufacturer ABC Autos goes to telecommunications provider XYZ Mobile to provide connectivity for its new line of IoT-enabled cars. In a classic deployment, the data is attached to a network housed in a local data center. The car goes to a country outside the EU, but the data can’t. And when the car is in the EU, the data pings all over the place, from the home network to where the vehicle is.
To avoid collisions, connected cars must communicate with one another in real time. Travelping needed to develop an IT infrastructure platform that could negotiate the challenges of cross-border data management. Plus, the data had to remain in a security-rich environment.
“It’s all about the five 9s”
Equipped with years of expertise in the telecommunications industry, Travelping knew it had to get the network closer to the connected devices. It also knew that the environment needed to be highly available. “It’s all about the five 9s [99.999 percent service availability],” says Holger Winkelmann, Travelping Founder and Chief Executive Officer (CEO). “But running on five 9s is highly expensive and complicated.”
So Travelping took a route that led it back to the basics: bare metal servers with a containerized application based on a Kubernetes platform. The client used IBM Cloud infrastructure products and Kubernetes tools to create cloud-native workloads. These containerized workloads can be transported rapidly to auto manufacturers to help make remote diagnosis or maintenance a real-time reality.
Some define Kubernetes as the new Linux or a new API. It uses open source software to enable apps to be deployed as loosely coupled services by packaging individual parts into their own containers. This modular programming process of deconstructing an application into various smaller services helps make the app easier to develop, test and deploy. It also allows for continuous delivery of scalable services.
“That was the reason we moved to Kubernetes and container deployment,” explains Winkelmann. “Because you can run services that are rather simple, maybe even stateless, in a five-9 environment—99.99 percent service availability environment (backed by the IBM® SLA). And then we increased to a five-9 environment you get mostly for free.”
The solution helps Travelping customers deploy in different locations and different environments. If they implement deployments that are network based, they “touch the heart of carrier,” says Winkelmann. “Usually the carrier says that it has to go on its typology. There are reasons for that. It must be in the licensed territory.”
But with Kubernetes, there’s a common API. “It works on private cloud and private deployment, but it also works in public clouds,” Winkelmann adds. “So you are totally agnostic, where you go from developer notebook to private cloud deployments, to edge deployments, or to your Raspberry Pi on the lamppost. You deploy in exactly the same way again and again, and this is only possible with Kubernetes.”
Travelping uses IBM Cloud because it helps the company manage data compliance. It also allows the client to operate its network service on top of that. “Many clouds in the field are what we call north-south clouds. They’re about terminating web traffic,” says Winkelmann. “That's not what we’re doing. We forward the payloads, the traffic for our mobile users. IBM Cloud is the only one that still allows us to transport data from node to node in a network, and not just terminate it.”
Cultural shift
Travelping’s journey to a connected car mobile platform required a cultural shift for its customers. Processing power is centralized in cloud computing and is ideal for IoT-enabled devices. The data is processed closer to the point of origin, which helps reduce latency between devices and the data processing layer. This can enable faster response times and more informed decision-making.
Providing scalable services on commodity hardware rather than telecommunications equipment wasn’t an easy sell. “It's definitely a cultural shift,” explains Winkelmann. “The biggest challenge here is to bring our customer base, which is telcos, out of classic ITSM [IT service management] into the cloud. It's a level of acceptance that you trust the stuff, and you accept that you can deploy a new service version three times a day, and not three times a year as we see it today.”
Even George Jetson’s cantankerous boss, Mr. Spacely, would be pleased.
Based in Magdeburg, Germany, Travelping (link resides outside of ibm.com) is a privately held company that develops software solutions for networks and communication devices. Founded in 2004, it has 30 employees.
Legal
© Copyright IBM Corporation 2020. IBM Corporation, IBM Cloud, New Orchard Road, Armonk, NY 10504
Produced in the United States of America, January 2020.
IBM, the IBM logo, ibm.com, and IBM Cloud are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at “Copyright and trademark information” at ibm.com/legal/copyright-trademark.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
This document is current as of the initial date of publication and may be changed by IBM at any time. Not all offerings are available in every country in which IBM operates.
The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions. THE INFORMATION IN THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT. IBM products are warranted according to the terms and conditions of the agreements under which they are provided.
The client is responsible for ensuring compliance with laws and regulations applicable to it. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the client is in compliance with any law or regulation.
Statement of Good Security Practices: IT system security involves protecting systems and information through prevention, detection and response to improper access from within and outside your enterprise. Improper access can result in information being altered, destroyed, misappropriated or misused or can result in damage to or misuse of your systems, including for use in attacks on others. No IT system or product should be considered completely secure and no single product, service or security measure can be completely effective in preventing improper use or access. IBM systems, products and services are designed to be part of a lawful, comprehensive security approach, which will necessarily involve additional operational procedures, and may require other systems, products or services to be most effective. IBM DOES NOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES ARE IMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THE MALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY.
