From the four modernizations to software defined vehicle (SDV), the traditional automobile industry has come to the crossroads of transformation. The core competitiveness of OEM will change from the hardware integration of vehicles to provide users with software services throughout the life cycle, and meet the personalized needs of users through flexible function configuration. In this context, Zerobeam introduces the CONCEPT of SOA architecture into the software design of the vehicle end, and builds an integrated SOA software platform on the cloud and tube end on this basis, which serves as the technical base platform for the realization of software-defined vehicles.

From this week, Zerobundle will elaborate on the cloud management integrated SOA software platform from seven aspects: product, digital architecture, software architecture, vehicle-cloud integrated architecture, service realization, platform testing and platform ecology.

This is the first in a series of SOA service software platforms that share what SOA software platforms mean for the automotive industry from a product and value perspective.

# Overview of SOA fundamentals

1.1 SOA architecture: Vehicle capability provision

Service Oriented Architecture (SOA) is a service-oriented Architecture. SOA divides the different functions and hardware capabilities of the vehicle end into services, and divides the corresponding services into smaller interfaces based on the atomic capabilities of the vehicle. The interface of each service component is packaged in a standardized way, which can be accessed and extended through established protocols. Its core elements include loose coupling, standardized definition and software reuse. SOA enables application layer functionality to be reused across vehicle types and quickly respond to new user functional requirements based on standardized interfaces. In addition, the SOA platform can fully invoke the hardware capabilities of sensors and actuators in each domain of the vehicle.

1.2 DEPLOYMENT platform of SOA: vehicle centralized EE architecture

If SOA is the software foundation for software-defined vehicle implementation, the whole-vehicle centralized electronic-electrical (EE) architecture is the hardware foundation on which SOA architecture can play.

Traditional vehicles use a distributed EE architecture consisting of hundreds of ECUs. Oems define the functional requirements for each ECUS, and different suppliers are responsible for the final implementation of the functions. As a result, a large amount of functional control logic is completed inside the ECU of sub-nodes, and sensor and actuator signals are buried under the distributed network. Only service-based communication is deployed in the ECU of local network, which cannot fully expose the hardware capability of the vehicle. In addition, considering that based on SOA software platform, future models after SOP also need hardware redundancy capability to cope with OTA software upgrade, the redundant design of hundreds of ECUs will greatly increase the cost and also result in the implementation of OTA with cross-domain functions involving a large number of ECUs.

With the improvement of on-board chip computing power and the landing of on-board Ethernet communication technology with high bandwidth and low delay, EE architecture has evolved from distributed to Domain Centralized. And to Vehicle Centralized + area (Vehicle Computer & Zonal), Vehicle Centralized (Vehicle Centralized) constantly evolve. In the highly integrated EE architecture, the domain controller will assume the main logic of the vehicle, while the actuators and sensors will become pure actuators, executing control commands or providing environmental awareness data.

Based on the “hard foundation” of the whole-vehicle EE architecture, the deployment of SOA on the domain controller can realize the resource acquisition of whole-vehicle capabilities and encapsulate them as standard services and interfaces open to the application layer.

Bosch defines each stage of vehicle EE architecture

2. Cloud management side integrated SOA software platform

2.1 Cloud management side integrated SOA software platform: it is both an architectural mode and a product

The concept of SOA is not a new term in the IT and Internet industry. After nearly two decades of development, IT has formed an inherent and mature system. However, in the automotive field, the hardware resources of the vehicle are far more complex than PC terminal or other consumer electronics, with hundreds of functional features, corresponding to nearly a thousand sensors and actuators. The role of SOA in the car is not only a software architecture pattern to realize software and hardware decoupling, but also an architecture product to realize continuous software operation and software value-added.

As a product capable of supporting OEM to realize continuous software operation, the integrated SOA software platform of Zero-beam cloud pipe terminal provides overall software solutions of vehicle terminal and cloud, as well as tool chain and methodology, enabling OEM to create an architecture for intelligent vehicle products.

Relying on the integrated SOA software platform of Zero-Beam cloud management, Zero-beam will create a new ecosystem capable of developing cross-brand, cross-platform and cross-model application scenarios for end users, OEM and third-party companies. Zero-beam SOA software platform products are based on the rich capabilities provided by the vehicle terminal and the cloud, aiming to hatch more software products that can effectively meet users’ car needs, form an intelligent vehicle ecosystem with user experience as the core and the joint participation and win-win cooperation of developers from all parties.

2.2 Integrated VEHICLE and cloud SOA software architecture products

The SOA architecture based on zero beam and service as the main body can help OEM to provide the hardware capability of the vehicle to the application layer in the form of original services, and realize the software and hardware decoupling of vehicle functions through accessible standardized interfaces. At the same time, third-party company capabilities can also be accessed as services through zero-beam SOA software architecture, providing richer options for application layer developers.

In view of the current situation, the vehicle hardware capability will produce a large number of variations along with the model configuration and annual model modification, zero-beam cloud platform will realize model service and interface management at the same time, to ensure that developer applications can be dynamically delivered to OEM models with hardware adaptation capability.

2.3 Developer Platform products

The SOA software architecture provides domain and third party capabilities, while the Zero-bundle developer platform is an incubator for ecosystem partner application layer software products.

OEM, professional third-party developers and even ordinary users, can through the developer platform provides an IDE environment and through standardized apis for application development, make the combination of different background developers to their business with the car function, hatched cross-domain integration, cross-industry integration (intelligent household, finance, insurance, etc.) a new software product. Through the online debugging tools and simulation environment provided by Zero Beam, the development of vehicle end application functions can be realized quickly while ensuring the quality of code.

Through the zero-bundle developer platform background management system, it can manage account permissions, application risk control and content, and implement new functions in the application market audit, shelf, etc. For OEM end-users, it is convenient to download the desired functions in the vehicle and mobile APP, dynamically meeting the needs of thousands of people, and truly realizing the vision of software-defined vehicles.

Car cloud integrated SOA software architecture

Value of cloud management side integrated SOA software platform

The value of cloud management integrated SOA software platform is not only limited to realizing software and hardware decoupling and providing vehicle capability at the technical level, but also to promoting the transformation of the business model of the entire automotive industry. In the past, OEM mainly earned profits from vehicle sales and brand premium after the integration of sub-system hardware. After the vehicle was sold, it had limited means to obtain sustainable profits from users. In the future, based on the SOA software platform, users can still purchase value-added software services through OTA after car purchase. Rich applications can create differentiated brand characteristics for OEM and promote new car sales in reverse. Higher sales mean that Oems will have access to a huge amount of vehicle data and will be able to collaborate with their partners to enable more intelligent scenario service users through big data analytics.

In the future, intelligent vehicles are expected to form a new software-defined vehicle ecosystem based on SOA platform, with user experience as the core, and jointly created by OEM and advanced Tier1/2, technology companies and other leading enterprises in the industry.

3.1 For Users

Huge amounts of application

A small number of sensors and actuators on mobile phones have been able to support IOS and Android systems to provide millions of applications, completely changing the way people live. The nearly a thousand hardware capabilities provided by automobiles through SOA software platforms are bound to generate a large number of new applications, and may even bring more usage scenarios for automobiles that cannot be expected now, writing a new era of transportation methods.

One thousand thousand

Thanks to the loosely-coupled nature of SOA, the car end features support fast dynamic configuration. Based on the original capability of the vehicle provided by SOA architecture, according to different user mood, the number of passengers, travel purpose, road conditions and other states, the scene mode that can realistically meet user’s personalized needs is provided for users to realize the car experience of thousands of people.

A living companion

The highly integrated EE architecture facilitates redundant design of hardware capabilities and OTA iteration capabilities throughout the vehicle’s life cycle. With improvements in software, algorithms, data mining and other capabilities, the car will evolve from a machine that performs user commands to a living partner that can interact with users and make active decisions.

3.2 for OEM

Low cost agile development

With SOA software platforms, Oems can develop application functions in an agile manner according to user needs. New feature development, integration, and validation cycles that used to take two years will be reduced to a few months or less, and costly development costs paid to vendors will disappear.

Incremental data

With the service interface provided by SOA software architecture, data on the vehicle side can be uploaded according to the actual requirements of cloud computing architecture to save communication traffic. In addition, the data lake combines big data algorithms to analyze user needs, and at the same time, it can provide partners with the data they need to realize data appreciation and realization.

Sales promotion

The rich application scenarios incubated by the developer platform, combined with the BRAND positioning of OEM, create brand characteristics through the push of differentiated software functions, and promote the sales of new cars in the market.

Business model innovation

The cloud-tube-based integrated SOA software platform will help Oems transform from vehicle hardware sales companies into technology companies with continuous software operation capabilities.

3.3 For ecological partners

SOA ecosystem

Looking back at the ecological development of smart phones, a series of technology companies and Internet enterprises have been born, such as Taobao, Alipay, wechat and Bytedance, while the SOA ecosystem based on smart cars is still in its infancy. In addition to traditional players in the automotive industry, other industry leaders can access the automotive business through SOA platforms. Aiming at the hardware capability of the vehicle end and the needs of users, it will inject more vitality into the innovation of the scene functions of intelligent vehicles, promote the interconnection of all things, and realize the deep integration of cars and daily life. The advance layout of the vehicle terminal and the cooperation with the leading OEM in the industry are conducive to seize the vehicle terminal application market and explore the business model of continuous application of vehicle software. The new ecology and the new business model often indicate infinite possibilities.

Data sharing

As the owner of user data and vehicle usage data, OEM can obtain relevant data from OEM according to actual business needs, optimize and iterate existing software products based on users’ feedback on product usage, and excavate new functional requirements behind user portraits through in-depth big data analysis.

SOA Software Platform Product ecology

Car experience of thousands of people

Agile development processes

Ecosystem partner around SOA software platform

From the perspective of products, this paper briefly introduces the concept of SOA, the productization characteristics of cloud tube-side integrated SOA software platform, and the significance of zero-beam cloud tube-side integrated SOA software platform products to users, Oems and ecosphere partners. As the first part of this series, this article will continue to share with you the experience of SOA software platform related technical modules, welcome to pay attention!

Author: Zero small bundle article source: SAIC Zero bundle developer Forum original link: bbs.z-onesoft.com/omp/communi… Copyright notice: This article is the blogger’s original article, reprint please attach the blog link!