Service Innovation for automotive
Service Innovation is a key enabler for the automotive OEM to innovate new software enabled service development. It powers the creation of an agile, high velocity process for new service development and innovation, and dramatically shortens the time-to-market for new service launches.
Available via Ericsson’s Connected Vehicle Cloud (CVC), the container-based software platform provides an application execution environment where the application development is separate from the infrastructure layer. With it, OEMs can decouple the vehicle design cycle from the service design cycle, and fully embrace service development methods and processes. These include prototyping, continuous integration and continuous deployment -- critical for success in the rapidly evolving automotive industry.
Applications and data are isolated through policy control to enforce access privileges for both users and applications, so that only the right resources, in the right context, are accessible. This ensures greater security, stability and governance.
Service Innovation also provides the capabilities for creating a developer/third party service provider ecosystem to increase speed and innovation for OEMs service and business development. Developed applications and services are packaged as Docker containers and deployed onto the platform using the Continuous Deployment pipeline. It also uses the CVC base services to integrate with other CVC applications and clients.
Service Innovation Features
Application Execution Environment
The application execution environment is a centrally managed execution environment which can be deployed across multiple cloud providers and/or geographical regions. Geographically distributed environments also help reduce time to market, both when expanding to new regions and when new applications are released.
Application Life Cycle management
Applications are entered into the system by uploading them to a registry. A continuous deployment (CD) function monitors the registry and deploys applications as configured. The CD function can be used to deploy an application in an initial environment, run tests, and promote it to a second environment if the tests pass.
The Marketplace service enables OEMs to differentiate via ease of service integration by allowing non-automotive service providers to become part of the OEM ecosystem. This creates new ways to enhance the monetization for the lifecycle of the vehicle and to innovate and build new services for the mutual benefit of OEMs, partners and customers.
The Marketplace service include a storefront for partner to discover, purchase and follow up the API offers from OEM business owner. It also provides data and API offering management functions for the OEM business owner to manage the resources and setup the product and offer for partners.
The Developer Portal provides an entry point for developers to utilize the Customer APIs, get access to API documentation and to manage App and API access based on the partner agreements.
The Exposure service manages the Applications access to the services/data with sub services such as authentication, security, traffic control and API transformation.
User Consent Service
The consent management services secure that there is a valid consent before any data is exposed and gives the data owner the possibility to give consent or revoke an already given consent.