CN115113603A - Electrical architecture systems and vehicles for vehicles - Google Patents

Abstract

The invention provides an electrical architecture system for a vehicle and a vehicle, the architecture system comprising: the basic platform layer comprises a service software layer, a middleware and a hardware layer, wherein the middleware is arranged between the service software layer and the hardware layer and is used for decoupling software and hardware; the application software layer is used for carrying out service function logic design according to service functions and user requirements; and the application software layer calls the service software of the service software layer through the service communication interface. The functional software does not depend on other functional software, and does not use the fixed CAN signal communication among the functional software for logic binding, but applies the Ethernet dynamic connection technology, designs a service software interface, is called by the functional software, and the whole architecture system has higher mobility, CAN realize the reconstruction of the functional software, rearranges the service and completes the agile development of the software. The invention can quickly and conveniently finish the requirement of function development under the increasing user function requirements, and can carry out infinite function reconstruction according to the user requirements.

Description

Electrical architecture systems and vehicles for vehicles

technical field

The present invention relates to the technical field of automobiles, and in particular, to an electrical architecture system and a vehicle for vehicles.

Background technique

The current electronic and electrical architecture design is a traditional distributed architecture design, and its functional design is relatively solid, and is generally controlled based on the interactive signals between the controllers. Each function needs to be controlled by other function software binding. This kind of electronic and electrical architecture platform is not conducive to platform-based and modular functional design, and it is not conducive to the increasingly personalized, intelligent and user-oriented service design of vehicles.

Especially for the electrical architecture design of the control system of the vehicle, its function development cannot meet the increasing user experience requirements. In the process of function development or in the process of new design changes, a series of logic or CAN signals of related controllers are required. Change, due to the coupling relationship of its software and the functional logic of binding, increases the development difficulty and development cycle of new functions, and increases the cost of change. It not only cannot support the agile development of functions, but also for subsequent functional reconstruction and expansion, It is also very difficult to achieve a user experience with thousands of people.

Referring to FIG. 1, FIG. 1 is a conventional electrical architecture in the prior art. When software controllers (ECU1-ECUn) need to be changed, due to the coupling of the software controllers, each new function needs to be updated when updating a new function. Every software controller is updated, the development cycle is long and the cost is very high.

In view of this, the present invention is proposed.

SUMMARY OF THE INVENTION

The present invention provides an electrical architecture system for a vehicle and a vehicle, so as to solve the above-mentioned control based on the interactive signals between the controllers in the prior art, the electronic and electrical architecture platform is not conducive to platformization, and the modularized functional design, etc. technical problem.

In a first aspect of the present invention, an electrical architecture system for a vehicle is provided. The architecture system includes: a basic platform layer, including a service software layer, a middleware and a hardware layer, and the middleware is arranged between the service software layer and the hardware layer. _It is used for decoupling software and hardware; the application software layer, including application software, is used to design business function logic according to business functions and user requirements; wherein, the application software layer invokes the services of the service software layer through the service communication interface software. The original function software architecture in the existing technology is divided into two layers of software, the application software layer and the basic platform layer, the basic functions of the vehicle are transformed into service software in the service software layer, and the service interface design is completed for the service software, while the application software The application software in the layer, by calling the service software, completes the flexible arrangement and design of functional logic; the basic platform layer completes the control of the actuator or the collection of sensor data, and realizes the layered independent design and layer-by-layer decoupling.

In an optional solution of the present invention, the basic platform layer includes one or more selected from the following: atomic services, integration services, interactive services, and a common implementation service software library for invocation by the application software layer.

In an optional solution of the present invention, the hardware layer includes an MCU microcontroller and an MPU microprocessor, wherein the MCU is used for processing control logic, and the MPU is used for software operation requiring high computing power. Therefore, different controllers are used under different requirements, so that the matching degree of controllers and functions is higher, the response is faster, and the consideration of space and energy consumption is taken into account.

In an optional solution of the present invention, the architecture system further includes: a standard control layer, including a plurality of solidified hardware, and the solidified hardware includes one or more selected from the following: sensors, actuators, drives, and regional control, wherein the standard control Layers are connected at the hardware layer.

In an optional solution of the present invention, the basic platform layer further includes virtualization and an operating system, the virtualization adopts the Hypervisor virtual machine technology, and the operating system includes at least one of LINUX and QNX.

In an optional solution of the present invention, the middleware includes Classic AUTOSAR and Adaptive AUTOSAR software.

In an optional solution of the present invention, the application software layer invokes the service software of the service software layer through the service communication interface, and uses the SOME/IP communication interface to complete the dynamic invocation of the service software.

In an optional solution of the present invention, the application software layer and the basic platform layer are deployed in the functional domain controller.

In an optional solution of the present invention, the software and software decoupling is completed between the application software and the application software of the application software layer through the service software; the application software and the hardware layer of the application software layer are completed through the middleware. Decoupling: Service decoupling is accomplished through middleware between service software and service software at the service software layer.

In a second aspect of the present invention, there is also provided a vehicle comprising the above-described electrical architecture system for a vehicle.

To sum up, the embodiments of the present invention provide an electrical architecture system for a vehicle, which splits the original functional software architecture in the prior art into two layers of software: an application software layer and a basic platform layer, and converts the basic functions of the vehicle into software The service software in the service layer completes the service interface design for the service software, while the application software in the application software layer completes the flexible arrangement and design of functional logic by calling the service software; the basic platform layer completes the control of actuators or sensor data collection , to achieve layered independent design and layer-by-layer decoupling, which solves the decoupling between functional software (functional software is defined as application software and service software), so that functional software no longer depends on other functional software, and no longer uses their mutual The fixed CAN signal communication is logically bound, but the Ethernet dynamic connection technology is used to design the service software interface, which is called by the functional software. The overall architecture system has higher mobility, and can realize functional software reconstruction and rearrangement. Services to complete software agile development. Under the increasing user function requirements, the invention can quickly and conveniently complete the function development requirements, and can perform infinite function reconstruction according to the user requirements.

Additional features and advantages of embodiments of the present invention will be described in the detailed description that follows.

Description of drawings

In order to illustrate the specific embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the specific embodiments or the prior art. Obviously, the accompanying drawings in the following description The drawings are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

1 is a connection topology diagram of an architecture system under the prior art provided by an embodiment of the present invention;

2 is a connection topology diagram of an electrical architecture system for a vehicle provided by an embodiment of the present invention;

3 is a schematic block diagram of an electrical architecture system for a vehicle provided by an embodiment of the present invention; and

FIG. 4 is a schematic block diagram of a specific architecture system according to an exemplary embodiment of the present invention.

In the above drawings, the list of components represented by each label is as follows:

【General Invention Concept】

100. An electrical architecture system for a vehicle;

101. Basic platform layer; 101a. Service software layer;

101b, operating system; 101c, hardware layer;

102. Application software layer; 103. Standard control layer;

b1, middleware; b2, virtualization;

[Example 1]

a, service software layer; b, application software layer;

c, window controller; d, driver state detector;

e, air conditioner controller; f, speaker;

g. Central control screen; h. Body domain controller BU;

i, entertainment cockpit domain controller; j, GW gateway.

Detailed ways

In order to make the above and other features and advantages of the present invention more apparent, the present invention is further described below with reference to the accompanying drawings. It should be understood that the specific embodiments given herein are for the purpose of explaining to those skilled in the art, and are merely illustrative and not restrictive.

In addition, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as indicating or implying relative importance or implying the number of indicated technical features. Thus, a feature delimited with "first", "second" may expressly or implicitly include at least one of that feature. In the description of the present invention, "plurality" means at least two, such as two, three, etc., unless otherwise expressly and specifically defined.

Techniques, methods, and systems known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, techniques, methods, and systems should be considered part of the authorized description.

Most of the vehicle system architectures under the existing technology are controlled based on the interactive signals between the controllers, and their function development cannot meet the increasing user experience requirements. In the process of function development or in the process of new design changes, The logic or CAN signal changes of a series of related controllers are required, which increases the development difficulty and development cycle of new functions, and is not conducive to the iteration of functions. The solution of the present invention aims to solve this problem.

【General Invention Concept】

Please refer to FIG. 2 and FIG. 3 , FIG. 2 is a connection topology diagram of an electrical architecture system for a vehicle provided by an embodiment of the present invention; FIG. 3 is a schematic diagram of a module of an electrical architecture system for a vehicle provided by an embodiment of the present invention . In a general inventive concept of an embodiment of the present invention, an electrical architecture system 100 for a vehicle is first provided, and the architecture system 100 includes:

The basic platform layer 101 includes a service software layer 101a, an operating system 101b and a hardware layer 101c;

The application software layer 102, the application software layer 102 invokes the service software of the service software layer 101a through the service communication interface;

The standard control layer 103 includes a plurality of curing hardware. The curing hardware may include curing software and hardware components with standard interfaces such as sensors, actuators, drivers, etc., such as sunlight sensors, rain sensors, light drivers, electric horns, window regulators, etc., curing The hardware can complete the local drive of the target vehicle, execute or upload data according to the instructions, and there are only software programs that drive or collect data and no functional logic software. The development of the software is separated from the inherent hardware, that is, the functional software does not need to care what brand or type of sensors and actuators are used in the project, it only needs to obtain data or issue control commands. This is beneficial for the platform to be used in various model projects and reduces the binding and dependence on hardware.

It can be understood that the term "application software layer 102" mentioned above is the business software in the vehicle electrical architecture system 100, which is a business function logic design according to business functions and user requirements. The basic function requirements of the vehicle can be divided into body function, power system function, chassis system function, entertainment cockpit system function, etc. according to the business.

The service software layer 101a is defined as the original control function of the vehicle, including atomic services (atomic services: each single service function of the car), integration services (functions obtained by combining multiple single services), interactive services, and jointly implement service software libraries, For application layer use, etc. Exemplary such as: window up, rain information, air conditioning temperature adjustment, cruise function, etc. The service software is positioned to have functions on the original configuration of each target vehicle, as well as specific service software and service interfaces.

Further, the above-mentioned operating system 101b is mainly used for the user to perform interactive operations to execute software running. In this embodiment of the present invention, an in-vehicle operating system such as LINUX, QNX, Android, and Tizen may be used.

In this embodiment of the present invention, the hardware layer 101c includes a controller for controlling the software to run according to preset logic.

Further in this embodiment of the present invention, the controller includes an MCU microcontroller and an MPU microprocessor, the MCU is used for processing control logic, and the MPU is used for software operation that requires high computing power, usually referring to complex algorithms or functions. programs, such as navigation calculation, path planning, sensor data perception of intelligent driving, fusion algorithms, etc., require the system to rely on a large amount of data to perform operations. Therefore, different controllers are used under different requirements, so that the matching degree of controllers and functions is higher, the response is faster, and the consideration of space and energy consumption is taken into account.

Further, the middleware b1 is between the service software layer 101a and the operating system 101b, and the middleware b1 is used as a key basis for decoupling the software and the hardware, using a standard software interface between the software and the hardware to make the software function Development and software changes do not depend on hardware chips.

In the embodiment of the present invention, the middleware technology optionally used by the middleware b1 adopts Classic AUTOSAR and Adaptive AUTOSAR software.

Further, between the operating system 101b and the hardware layer 101c is virtualization b2. By virtualizing the hardware, one computer is virtualized into multiple logical computers, which can be regarded as the abstraction of the platform hardware and the operating system. Capture and process virtualization-sensitive privileged instructions between the hardware layer and the hardware layer, allowing the operating system to run without modification. It is used to be compatible with heterogeneous designs of various operating systems, allowing multiple operating systems and applications to share hardware.

Optionally, virtualized b2 uses Hypervisor virtual machine technology.

In this embodiment of the present invention, the application software layer 102 invokes the service software of the service software layer 101a through the service communication interface.

It can be understood that by transforming the basic functions of the vehicle into service software in the service software layer 101a, and completing the service interface design for the service software, the application software in the application software layer 102 can complete the flexible arrangement and design of functional logic by calling the service software. .

Specifically, software and software decoupling is accomplished between application software and application software through service software; application software layer 102 and hardware layer 101c are decoupled between application software and hardware through middleware b1; between service software and service software Complete service decoupling through middleware b1. The application software layer 102 and the basic platform layer 10 can be arbitrarily deployed in the functional domain controller, so as to depend on the capabilities of the hardware layer 101c, such as chip processing, driver, memory, and the like. Optionally, use CP AUTOSAR and AP AUTOSAR middleware to deploy service software, between the application software layer 102 and the service software layer 101a, that is, between the above-mentioned service software and the service software, use the SOME/IP communication interface to complete the dynamic of the service. transfer.

It can be understood that the main focus of platform development is on the basic platform layer 101. The establishment of an SOA service system includes service software libraries and middleware technology applications. Application layer development is not the focus of platform development, but the application of service system development. to develop.

To sum up, in order to realize the decoupling design of the functional software, the original functional software architecture in the prior art is divided into two layers of software: the application software layer 102 and the basic platform layer 101, and the basic functions of the vehicle are transformed into the service software layer 101a. The application software in the application software layer 102 completes the flexible arrangement and design of functional logic by calling the service software; the basic platform layer 101 completes the control of the actuator or the collection of sensor data, Realize layered independent design and layer-by-layer decoupling, which solves the decoupling between functional software (functional software is defined as application software and service software), so that functional software no longer depends on other functional software, and no longer uses their mutual The fixed CAN signal communication is logically bound, but the Ethernet dynamic connection technology is used to design the service software interface, which is called by the functional software. The overall architecture system 100 has higher mobility, and can realize functional software reconstruction and rearrangement. Services to complete software agile development. In order to solve the requirements of fast and convenient completion of function development under the background of increasing user functional requirements, and unlimited functional reconstruction can be carried out according to user needs.

【Example 1】

Please refer to FIG. 4. FIG. 4 is a schematic block diagram of a specific architecture system 100 according to an exemplary embodiment of the present invention; the architecture system 100 applies SOA technology, and the design is divided into three layers, an application layer (also known as a business layer), a basic platform Layer (also known as the service system layer), the standard control layer. The basic platform layer is further divided into service software layer, middleware, operating system and virtualization, and hardware layer. In order to realize the decoupling design of the functional software, the original functional software architecture is divided into two layers of software, the application layer and the basic platform layer, the basic functions of the vehicle are transformed into the service layer software, and the service interface design is completed. Software to complete the flexible arrangement and design of functional logic; the basic platform layer completes the control of the actuator or the acquisition of sensor data through the standard control layer to form a portable architecture system 100 .

Taking the integrated service as "driver status monitoring" as an example, the architecture system 100 specifically includes the following:

Service software layer (a): including window service, air conditioning service, driver status monitoring service, navigation service, and voice service. They are respectively contained in the body domain controller BU(h) and the entertainment cockpit domain controller HU(i).

Application software layer (b): including the intelligent refreshing function, which is deployed in the body domain controller BU (h).

The window controller (c) acts as a window lowering actuator control unit and controls the window lowering.

The driver state monitoring controller (d) acts as a driver fatigue state recognition control unit to recognize whether the driver is fatigued.

The air conditioner controller (e) acts as an air conditioner temperature execution, fragrance execution, air volume execution, and air outlet mode actuator control unit, controlling the air conditioner temperature, fragrance opening, air volume adjustment, and air outlet mode setting.

The audio (f) is controlled by the entertainment domain controller HU (i), which controls the music playback.

The central control screen (g) is controlled by the entertainment domain controller HU (i) for display.

Body domain controller BU (h): realize the window service software, control the execution of the window controller (c) through the CAN bus command; realize the air conditioning service software, control the execution of the air conditioning controller (e) through the CAN bus command; realize the driver The state monitoring service software collects the driver fatigue state identified by the driver state monitoring controller (d) through the CAN bus.

The entertainment cockpit domain controller HU(i): realizes the navigation service software to control the display on the central control screen; realizes the voice service software to control the audio playback;

GW gateway (j), used for Ethernet data transmission interaction.

Among them, the application software layer (b) in the body domain controller BU (h) calls the "driver status monitoring service" according to the pre-programmed functional logic, and the driver status monitoring controller (d) passes the CAN bus data Get the "driver fatigue state", send CAN bus commands to control the air conditioning controller (e) to execute by calling "air conditioning service", and call "window service" to send CAN bus commands to control the window controller (c) to execute, through the GW gateway (j) Perform Ethernet communication with the entertainment cockpit domain controller HU(i), and call the "navigation service" in the entertainment cockpit domain controller HU(i) to control the central control screen (g) Display the navigation interface and call the "voice service" Control sound (f) Play music and prompt sound.

An embodiment of the present invention further provides an electric vehicle, including the above-mentioned architecture system 100 .

Further, those skilled in the art should understand that if the architecture platform system for vehicles provided by the embodiments of the present invention, all or part of the sub-modules involved are combined or replaced by means of fusion, simple change, mutual transformation, etc. , such as placing each component in a moving position; or integrating the product formed by it; or detachable design; where the combined components can form equipment/devices/systems with specific functions, use such equipment/devices/systems instead The corresponding components of the present invention also fall within the protection scope of the present invention.

Those skilled in the art will appreciate that the embodiments of the present application may be provided as a system, or as a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-persistent memory in computer readable media, random access memory (RAM) and/or non-volatile memory in the form of, for example, read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media includes both persistent and non-permanent, removable and non-removable media, and storage of information may be implemented by any method or technology. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device comprising a series of elements includes not only those elements, but also Other elements not expressly listed, or which are inherent to such a process, method, article of manufacture, or apparatus are also included. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article of manufacture or apparatus that includes the element.

Although the embodiments of the present invention have been shown and described above, it should be understood that the above-mentioned embodiments are exemplary and should not be construed as limiting the present invention. Embodiments are subject to variations, modifications, substitutions and variations.

Claims (10)

1. An electrical architecture system for a vehicle, wherein the architecture system comprises: The basic platform layer includes a service software layer, a middleware and a hardware layer, and the middleware is arranged between the service software layer and the hardware layer _for decoupling software and hardware; The application software layer, including application software, the application software is used to design business function logic according to business functions and user requirements; Wherein, the application software layer invokes the service software of the service software layer through a service communication interface. 2 . The electrical architecture system for a vehicle according to claim 1 , wherein the basic platform layer comprises one or more selected from the group consisting of atomic services, integration services, interactive services, and common implementation service software. 3 . Libraries to be called by the application software layer. 3. The electrical architecture system for a vehicle according to claim 1, wherein the hardware layer comprises an MCU microcontroller and an MPU microprocessor, wherein the MCU is used for processing of control logic, and the MPU is used for Software that requires high computing power to run. 4. The electrical architecture system for a vehicle of claim 1, wherein the architecture system further comprises: The standard control layer includes a plurality of solidified hardware, and the solidified hardware includes one or more selected from the following: sensors, actuators, drives, and area controls, wherein the standard control layer is connected to the hardware layer. 5. The electrical architecture system for a vehicle according to claim 1, wherein the basic platform layer further comprises virtualization and an operating system, the virtualization adopts the Hypervisor virtual machine technology, and the operating system comprises LINUX , at least one of QNX. 6. The electrical architecture system for a vehicle according to claim 1, wherein the middleware comprises Classic AUTOSAR and Adaptive AUTOSAR software. 7. The electrical architecture system for a vehicle according to claim 1, wherein the application software layer calls the service software of the service software layer through a service communication interface, and adopts the SOME/IP communication interface to complete the service software dynamic call. 8. The electrical architecture system for a vehicle according to claim 1, wherein the application software layer and the base platform layer are deployed in a functional domain controller. 9 . The electrical architecture system for a vehicle according to claim 1 , wherein soft and soft decoupling is accomplished between the application software of the application software layer and the application software through service software; 9 . The decoupling between the application software and the hardware layer is accomplished through the middleware; the service decoupling between the service software and the service software in the service software layer is accomplished through the middleware. 10. A vehicle, characterized by comprising the architecture system according to any one of claims 1 to 9.

Images