Hello, Hello, everybody, the second time to play the instrument when it comes to the ~ v-SOA can break down floor by SOC, SORS and SOS, the first bomb has been talked achieve SOC, which is part of the major domestic OEM is going through a stage, a second bomb, we continue to talk and SOS content of SORS.
•
(c) v-SOA how to achieve it?
SORS(Service-Oriented Reuse-shared Design)
Current vehicle distributed in the multi-stage architecture (as shown in FIG. 1), the vehicle includes all nodes Ethernet communication capability discrete hung on the gateway, there is no concept of a domain controller, high-performance central processing node processor or the like . So to achieve SOC is not a problem, but in order to achieve SOA is difficult, because the function is too scattered, resources of each node due to the simple initial planning function can not be reserved for the rich amount of resources to use the new features of postpartum and consumption, it is difficult to achieve functional remodeling on this basis, which is one of the reasons why there is the next generation of electrical and electronic architecture (eg Domain, Zone, as shown in Figure 2) on the need to adapt to the new architecture the new development needs, based on the principle of the shift logic, you can achieve more performance logic, in the central node of a multi-class resources. Current vehicle distributed in the multi-stage architecture (as shown in FIG. 1), the vehicle includes all nodes Ethernet communication capability discrete hung on the gateway, there is no concept of a domain controller, high-performance central processing node processor or the like . So to achieve SOC is not a problem, but in order to achieve SOA is difficult, because the function is too scattered, resources of each node due to the simple initial planning function can not be reserved for the rich amount of resources to use the new features of postpartum and consumption, it is difficult to achieve functional remodeling on this basis, which is one of the reasons why there is the next generation of electrical and electronic architecture (eg Domain, Zone, as shown in Figure 2) on the need to adapt to the new architecture the new development needs, based on the principle of the shift logic, you can achieve more performance logic, in the central node of a multi-class resources.
A schematic view of a distributed architecture EE
Figure II schematically architecture next EE
SORS is a next-generation intelligent network architecture to achieve the Union, notably the completion of the service implementation, service reusability and reflect the design work carried out, the service itself has high cohesion and low coupling between services can improve services reusability, clear boundary concept.
•
that ... this thing done at what stage? Who will do it?
In the vehicle features conceptual design phase, OEM vehicle electrical and electronic architecture departments do. This answer is not surprising, after all, who else would the vehicle itself features more familiar than the architecture department of it - as well known, along with the vehicle functional logic definition and combing, architecture will dominate or participate in requirements development, function definition, function realization, subsystem design, component design process to the best of SORS can achieve throughout, and ultimately will be reflected in part a function implemented.
•
That ... out how to do it?
In the vehicle features conceptual design phase, OEM vehicle electrical and electronic architecture departments do. This answer is not surprising, after all, who else would the vehicle itself features more familiar than the architecture department of it - as well known, along with the vehicle functional logic definition and combing, architecture will dominate or participate in requirements development, function definition, function realization, subsystem design, component design process to the best of SORS can achieve throughout, and ultimately will be reflected in part a function implemented.
•
That ... out how to do it?
SORS no technical standard and no international norms, a maximum of SORS without verification of all the automotive field implementation methodology. For now, there are two ideas, one is bottom-up, the second is from top to bottom.
♦ bottom up: begin to count and sort out from the vehicle center hardware terminal hardware, specific hardware and may provide the same or similar services, e.g., sun rain sensor can provide information about light intensity and rainfall, so that we sun can be abstracted from a rainfall of service, as long as the hardware, our service will be in, without any constraints. After the center can continue to explore and tap the corresponding hardware features, such as data provided by the service were drawn.
♦ Top-down: starting from the existing vehicle functions and business processes, such as vehicle anti-theft certification, there will be security certification process at all levels, during calls to a lot of modules or algorithms, such as randomized algorithms, security authentication algorithms, these algorithms can be extracted form different algorithms service. Starting from one of the business chain functional differentiation pulled out of the library service, and finally the reconstruction can be reversed, i.e., a selected service module from a library service, restore them by calling the permutations and combinations of the original features business scenarios will be no difference .
SORS affect the design of the new features of the future is enormous. In the traditional development mode, the new features can only be deployed by OEM and planning, even the need to develop models, creative limited period of long and big investment. In SORS development model, OEM platform / model development phase will analyze all the hardware and software resources owned by the vehicle itself, and provide possible reuse. OEM or authorized third parties can easily develop new repository-based service, fast iteration is completed and deployed to the vehicle end by OTA technology, continue to improve the user experience.
SOS(Service Oriented Software Architecture)
System for service-oriented architecture, software architecture related to the ECU, namely SOS, is also working to adapt. AUTOSAR Adaptive platform, referred to as AP, a middleware-based service concept, is a good example. It embodies the idea of service-based architecture: the operating environment (ara) is divided into two parts and Service Foundation
Figure III schematically AP software architecture
Foundation：
♦ CM (Communication Management) swept the inter-node inter-process communication &
♦ EM (Execution Management) is responsible for the implementation of process control
♦ the REST (a RESTful) outside the embodied communication connectivity
♦ PHM (Health Management Platform) platform health management system
♦ TimeSyn (Time Synchronization) time synchronization module;
Service：
♦ SM (State Management) function groups and regulators all processes running on the AP state transition
♦ DM (Diagnostic Management) can be flashed to diagnose and size of AAP
♦ NM (Network Management) network management module
♦ UCM (Update and Config Management) led application updates, AP OS update from the update package and update the concept and so on;
AP as middleware, with the need to support the POSIX standard operating system, the upper application (AAP) will be run by ARA to the environment by the AP unified configuration, management, scheduling and allocation of resources.
•
That ... AP AUTOSAR also launched, and CP have to do with it? Why should we introduce the concept of the AP it? Existing operating systems and architectures, such as Android, can not meet the realization of SOA services based on it?
AP and CP are all AUTOSAR family, is the relationship between the brothers. CP launched earlier time, AP is a 2017 first edition had appeared and was formally set AP specification. As you know, the current account for a large proportion of CP used in the development of various types of in-vehicle ECU realization of, mainly deal with the development of embedded ECU, which is in line before we talk of a box to a distributed function of vehicle demand EE architecture, the clear and specific functions can be precisely controlled by the ECU hardware and software development itself, CP software architecture and modular approach with the AUTOSAR OS can fully meet the real-time requirements for certain functions to run when ECU itself.
With the joint development of next-generation intelligent network architecture, requiring some nodes equipped to handle massive amounts of data and the ability to perform large-scale examples of high frequency, which will inevitably require such node has a wealth of software and hardware resources, while meeting the car safety requirements for environment. Against this background, good for embedded ECU of CP becomes beyond its capability.
Of course, the common OS also can not meet this demand, such as Android, in some scenarios it can not meet the in-vehicle functional safety requirements. At this stage of history AP, as an important part of the HPC (High Performance Controller) type of ECU, AP unified management is done under the OS and peripheral resources, so that all scheduling system is running, status, and resource consumption are in a within a controllable range, in order to meet the in-vehicle safety, requiring deterministic. When the rich resources, the choices on the larger, can take advantage of such heterogeneous multicore architectures to handle complex scenarios, like using a virtual machine Hypervisor technology, CP, AP and non-AUTOSAR systems co-exist in the HPC, can be considered a typical implementation methods, of course, all starting from the demand.
The progress bar stays and continue, this time to share first come to an end, the final third bomb, we focus on the major OEM, and see how they are to achieve their SOA, we next goodbye ~~
Jingwei Hengrun
Zhichun Road Haidian District, Building D 7 to really layer 6
Phone: 010-64840808
E-mail: [email protected]
URL: www.hirain.com
