Vehicle development platform, domain controller, vehicle control system and vehicle

Abstract

A vehicle development platform, a domain controller, a vehicle control system, and a vehicle, the development platform including a hardware layer, an operating system and driver layer, a platform service layer, and an application layer, which are interconnected and communicate with each other, the hardware layer forming a resource pool as a carrier of software resources, the operating system and driver layer running on the hardware layer and operating to provide execution conditions to the platform service layer, the platform service layer running on the operating system and transmitting and managing data within the vehicle, and the application layer loading service programs and application programs of the vehicle upper layers.

Description

[Technical field]

[0001] (Cross-reference to related disclosures) This disclosure is based on and claims priority to a Chinese patent application with application number 202111680458.2, filed on December 30, 2021, the entire contents of which are incorporated herein by reference.

[0002] The present disclosure relates to the field of automotive technology, and in particular to a vehicle development platform, a domain controller, a vehicle control system, and a vehicle. [Background technology]

[0003] With the development of computer technology, it provides more and more development space for control in the automotive field.

[0004] In current automobile control systems, a vehicle controller, a motor controller, and a micro base station are arranged to construct a wireless transmission network. While the automobile is driving, the vehicle controller communicates with the motor controller via a signal transceiver and sends control commands to the motor controller, and the motor controller controls the vehicle driving state based on the control commands.

[0005] The above-mentioned automobile control system has a large amount of data that is secondarily transmitted through a wireless network, so that the real-time performance and stability are not high, and the signal is easily interfered with. In addition, the total control of the vehicle controller results in high maintenance costs, uniform performance, and low scalability. Summary of the Invention [Problem to be solved by the invention]

[0006] In view of the above deficiencies or shortcomings in the prior art, it is desirable to provide a vehicle development platform, a domain controller, a vehicle control system, and a vehicle. By installing a heterogeneous operating system in the domain controller, the domain controllers of each function in the vehicle control system are independently developed and seamlessly integrated, and call each other, thereby improving the performance and scalability of vehicle control. [Means for solving the problem]

[0007] In a first aspect, a vehicle development platform running on a controller of a vehicle according to an embodiment of the present disclosure includes a hardware layer, an operating system and driver layer, a platform services layer, and an application layer, which are interconnected and communicate with each other from bottom to top; The hardware layer forms a resource pool as a carrier of software resources; The operating system and driver layer executes on the hardware layer and provides execution conditions to the platform services layer; The platform services layer runs on the operating system and transmits and manages data within the vehicle; The application layer is characterized by loading service programs and application programs of the vehicle upper layers.

[0008] Preferably, in the vehicle development platform according to the embodiment of the present disclosure, the platform service layer includes a data bus module, a data function module and an operating system interface module; The data bus module is used for data transmission and sharing between or within domain controllers on the vehicle; The data function module stores and updates data; The operating system interface module handles upper layer services and applications to invoke functions of the operating system and drivers.

[0009] Preferably, in the vehicle development platform according to the embodiment of the present disclosure, the operating systems in the operating system and driver layer include a Linux (registered trademark) operating system and a QNX operating system, and each operating system corresponds to one POSIX operating system interface.

[0010] Preferably, in a vehicle development platform according to an embodiment of the present disclosure, the lowest layer interface is located at the lowest layer of each of the operating systems.

[0011] Preferably, in a vehicle development platform according to an embodiment of the present disclosure, the data function module includes a time synchronization unit, a service management unit, a data persistence unit, a log and trace unit, a data update unit, an actuator control service unit, a network management, a security management, a signal collection service unit, and / or a diagnostic service unit.

[0012] Preferably, in the vehicle development platform according to the embodiment of the present disclosure, the application layer includes an application service layer and an application program layer, and the application service layer loads the vehicle.

[0013] Preferably, in the vehicle development platform of the embodiment of the present disclosure, the application service layer includes a vehicle status service module, a signal transmission service module, a signal analysis service module, an air conditioning control service module, a window control service module, a door control service module and / or an identity authentication service module.

[0014] Preferably, in the vehicle development platform according to the embodiment of the present disclosure, the application program layer includes a meter application module, an air conditioning application module, a light control application module, a door control application module, a window control application module, a remote control driving application module, and / or a cloud service application module.

[0015] Preferably, the vehicle development platform according to the embodiment of the present disclosure is developed based on a service-oriented architecture (SOA).

[0016] Preferably, in the vehicle development platform according to the embodiment of the present disclosure, the lowest layer interface is located in the domain controller development platform.

[0017] In a second aspect, a domain controller according to an embodiment of the present disclosure includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the vehicle development platform described in the first aspect above is installed in the domain controller.

[0018] In a third aspect, a vehicle control system according to an embodiment of the present disclosure includes at least one domain controller according to the second aspect.

[0019] In a fourth aspect, the vehicle control system according to the third aspect is installed in a vehicle according to an embodiment of the present disclosure. Effect of the Invention

[0020] In the vehicle development platform, domain controller, vehicle control system, and vehicle according to the embodiment of the present disclosure, a platform including a hardware layer, an operating system and driver layer, a platform service layer, and an application layer, which are interconnected and communicate with each other from bottom to top, is developed in the vehicle controller, and after integrating all the logic layers, a platform is provided for the development and application of the vehicle controller, so that controllers with different functions can be independently developed and different functions can be realized.Furthermore, a functionally complete vehicle control system is constructed, and a large amount of data can be transmitted between the controllers in real time during the running of the vehicle system, so as to ensure the safety of the user and the vehicle, and the control system can be remotely called according to the actual needs.

[0021] Other features, objects and advantages of the present disclosure will become more apparent upon reading the detailed description of the non-limiting embodiments thereof, given with reference to the following drawings, in which: [Brief description of the drawings]

[0022] [Figure 1] FIG. 2 is a schematic diagram of a top-layer logic framework of a vehicle domain controller according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a schematic diagram of the software architecture of a domain controller according to an embodiment of the present disclosure. [Diagram 3] FIG. 2 is a schematic diagram of the software hierarchy of a domain controller according to an embodiment of the present disclosure. [Figure 4] FIG. 2 is a schematic configuration diagram of a development module of a domain controller according to an embodiment of the present disclosure. [Diagram 5] FIG. 2 is a schematic diagram of an operating system interface of a domain controller according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a schematic configuration diagram of a development module of a domain controller according to an embodiment of the present disclosure. [Figure 7] FIG. 2 is a schematic diagram of a computer of a processing device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] The present disclosure will be described in more detail below with reference to the drawings and examples. It should be understood that the specific examples described herein are merely for the purpose of illustrating the relevant disclosure, and do not limit the present disclosure. For convenience of explanation, the drawings show only parts related to the disclosure.

[0024] In addition, the embodiments and features of the embodiments of the present disclosure can be combined with each other as long as they are not inconsistent. Hereinafter, the present disclosure will be described in detail with reference to the drawings.

[0025] As can be appreciated, the physical hardware layout of a vehicle control system may include multiple architectures, such as one or more domain controllers, one or more traditional on-board controllers (ECUs) and a central gateway, and during execution, data is transmitted via CAN or Ethernet.

[0026] With the integration of technology, the above architecture is gradually simplified and a new layout architecture is generated, i.e., the number of ECUs in the traditional structure is becoming fewer and fewer, and eventually evolving into two or more domain controllers and a central gateway, among which the central gateway can be integrated into the one domain controller and connected via Ethernet.

[0027] With ever increasing processor capabilities, vehicle control systems may include only one central processing unit.

[0028] Based on this, as shown in FIG. 1, in an embodiment of the present disclosure, in order to improve the time-saving and independence of each function of the vehicle control system, the vehicle control system is divided into multiple independent domain controllers based on the functions that need to be realized in the vehicle.

[0029] For example, a vehicle control system may include one or more domain controllers, each of which may have access to sensors and execution mechanisms, zero or more traditional ECUs, and zero or more central gateways.

[0030] As can be understood, based on the physical architecture of the vehicle control system according to the embodiment of the present disclosure, in order to realize the mutual cooperation between the domain controllers, the remote invocation of the program, and the transparent transmission of the data, it is necessary to arrange a development software platform, i.e., a vehicle development platform, in the domain controllers in the physical architecture, thereby realizing the logic architecture of the domain controllers based on the development platform, and realizing the independence of each domain controller.

[0031] As can be understood, as shown in Fig. 2, in order to achieve the above objective, specifically, for example, microservices, arbitrary access of sensors and actuators, data transmission and reception via wireless communication (OTA), functional modules of terminal devices, etc. are realized in each domain controller, and the software platform developed in the domain controller is executed. That is, a heterogeneous framework of the development platform is constructed, and different suppliers and development teams develop applications of the domain controller in this development platform.

[0032] As can be understood, "heterogeneous" refers to heterogeneous controllers, i.e. the development platform must be able to run on ECUs of domain controllers of different architectures, and these domain controllers of different architectures have multi-cores and multi-processors. The most complex architecture is a CPU with an artificial intelligence (AI) computing unit + a digital integrated circuit chip (FPGA) + an artificial intelligence (AI) chip + a CPU.

[0033] In addition, "heterogeneous" also includes networks, i.e., from the vehicle's perspective, the software platform of the domain controller is heterogeneous, including the Antosar platform and the traditional ECU program, i.e., the vehicle development platform running on the domain controller needs to accommodate such network differences.

[0034] For example, in the vehicle control system shown in FIG. 1, communication between multiple domain controllers is realized via Ethernet (registered trademark), thereby ensuring network security and preventing hacker attacks.

[0035] In addition, remote calling can be performed according to actual needs, making it more convenient for users to use the vehicle and for development teams to develop remote calling of in-vehicle software.

[0036] Therefore, the software architecture of the domain controller is intended for the vehicle development platform and may be designed as a heterogeneous domain controller based on a service-oriented architecture (SOA).

[0037] As can be understood, SOA is a service-oriented architecture, and divides the vehicle development platform according to the embodiment of the present disclosure into platform services and application services, where the platform services can call each other, the application services can call each other, application programs can call the platform services, and the application services can further remotely call application services on other domain controllers.

[0038] In addition, the domain controller in the vehicle uses the developed software platform to flexibly arrange (decouple) sensors, actuators and controllers. The sensor data collection, actuator control and controller functions are no longer tightly coupled, thereby ensuring transparent sharing of data. The data sources are wide and the data volume is large, so it is necessary to support transparent sharing of data between domain controllers and between internal chips of the domain controllers.

[0039] Based on this development platform, all domain controllers can be made open and developed collaboratively, so that each function can be distributed to different development teams, suppliers, etc. for independent development and seamless integration.

[0040] In addition, different hardware platforms can be supported by running the developed software platform on the domain controller. When the hardware platform is changed or upgraded, there is no need to modify each functional software module, and applications with high real-time requirements, such as remote control driving applications, can be quickly responded to. In addition, power consumption can be managed to realize sleep and wake-up functions. This allows the power consumption of the vehicle to be controlled, and the clocks of multiple domain controllers to be synchronized and kept synchronized.

[0041] As can be seen, in the logic architecture of the vehicle control system according to the embodiment of the present disclosure, data is not transmitted through a wireless network, but is directly transmitted through the domain controller, thereby ensuring the real-time, integrity and safety of data, and realizing the real-time transmission of large amounts of data between the domain controllers. Therefore, the automation and intelligence of electrical appliances, and the real-time transmission of large amounts of video and audio data between the domain controllers, improve the safety of automobiles for users, i.e., ensure the safety of users and vehicles.

[0042] Each domain controller exists independently according to the actual functions of the vehicle. That is, each function is independent of the other and does not interfere with the other. This allows functions such as a door lock assembly, a window control assembly, a wiper assembly, a seat assembly, and a body control module (BCM) to be isolated independently.

[0043] FIG. 3 is a layered diagram of a vehicle development platform, i.e., a software platform. The lowest layer is a hardware layer. In the middle is a platform services layer, which may include a real-time multitasking operating system (RTOS), device drivers, and a services layer. The top layer is a portable operating system interface (POSIX) and application layer, which may include an application services layer and an application program layer.

[0044] In order to better understand the vehicle development platform executed on the domain controller according to the embodiment of the present disclosure, a detailed description will be given below with reference to FIGS.

[0045] 4 is a schematic diagram of a software architecture of a vehicle development platform according to an embodiment of the present disclosure. As shown in FIG. 4, the vehicle development platform runs on a domain controller of a vehicle, and includes a hardware layer, a platform service layer, an interface layer and an application layer, which are interconnected and communicate with each other from bottom to top.

[0046] The hardware layer is configured to form a resource pool as a carrier of software resources.

[0047] The operating system interface runs on the hardware layer, and the operating system and driver layer provides execution requirements to the platform services layer.

[0048] A platform services layer runs on top of the operating system and transmits and manages data within the vehicle.

[0049] The application layer loads service programs and application programs of the upper layers of the vehicle to realize functions required for the vehicle.

[0050] Specifically, in a vehicle development platform running on a domain controller according to an embodiment of the present disclosure, as can be understood from the logic layer, the lowest layer of the vehicle development platform is the hardware layer, which may be an actual domain controller, or may be a virtual machine or a container, etc., to form a resource pool.

[0051] For example, in the case of a rail vehicle, the hardware layer may be domain controllers mounted at different locations on the vehicle.

[0052] Running on top of the hardware layer is an operating system and driver layer, which provides execution conditions to the platform services layer and mainly handles upper layer services and applications to invoke the functions of the operating system or drivers, which may be an operating system such as Real-Time Multitasking Operating System (TROS), ANX or RLinux.

[0053] As can be understood, in a vehicle development platform, different domain controller hardware needs to be supported, and different functional domain controllers may have different requirements for stability and real-time performance, so different operating systems may be selected. For example, for a body domain controller, the requirements for the real-time performance of the operating system are not high, and a Linux operating system may be selected based on cost considerations, but for a power domain controller, the requirements for both stability and real-time performance are high, and a QNX operating system may be selected.

[0054] The embodiments of the present disclosure are not limited to a specific operating system, and can be flexibly configured according to actual circumstances.

[0055] Above the operating system and driver layer is a platform service layer, which can be used to realize the transmission and management of data generated during the execution of the operating system, such as storage, forwarding, etc. Above the platform service layer is an application layer, which loads the service programs and application programs of the vehicle upper layer to realize different functions of the vehicle, such as air conditioning control, light control, power control, door control, meter display, and various user-oriented services.

[0056] As can be seen, in the domain controller development platform according to the embodiment of the present disclosure, a vehicle development platform including different logic modules is developed and executed on the domain controller, and then all logic modules are integrated, and a platform is provided for the development and application of the domain controller. In this way, domain controllers with different functions can be independently developed to realize different functions and build a vehicle control system with complete functions. A large amount of data can be transmitted between the domain controllers in real time, and the safety of users and vehicles can be guaranteed.

[0057] Preferably, in some embodiments, the platform services layer may include a data bus module, a data function module, and an operating system interface module. The data bus module transmits and shares data between or within domain controllers. The data function module stores and updates data. The operating system interface module processes upper layer services and applications to invoke operating system and driver functions.

[0058] For example, as shown in FIG. 4 and FIG. 6, the platform service layer may include three parts: a data bus, a data function module including multiple processing modules, and an operating system interface module. The data bus module as the first part is mainly responsible for data transmission and sharing between or within domain controllers. Each data function module as the second part realizes a corresponding data processing function. For example, the signal collection service is responsible for collecting sensor signals, and the data persistence management is responsible for storing the state or setting data of application programs, etc. The operating system interface module as the third part is mainly responsible for processing the services and applications of the upper layer to call the functions of the operating system and drivers.

[0059] As shown in FIG. 4, the data function module may specifically include a time synchronization unit, a service management unit, a data persistence unit, a log and trace unit, a data update unit, a diagnostic service unit, a network management unit, a security management unit, a boot management unit, a signal collection service unit, an actuator control service unit, a configuration management unit, a communication protocol stack unit, a Rest interface unit, and / or a domain control state management unit, etc.

[0060] It can be understood that the configuration of the data processing unit in the above data function module is merely an exemplary description, and specifics can be flexibly configured according to actual circumstances, and the present disclosure is not limited thereto.

[0061] Specifically, the data bus may include a DPC, a CPC, and an IPC.

[0062] Preferably, in the embodiment of the present disclosure, for domain controllers with different functions, different operating systems are selected due to different requirements for stability and real-time performance. In order to ensure the portability of the developed platform, it is necessary to reserve an operating system interface layer at the lowest layer of the platform service layer, as shown in FIG.

[0063] Preferably, in some embodiments, the operating systems in the operating system and driver layer may include the Linux operating system or the QNX operating system, and each operating system corresponds to an operating system interface. For example, as shown in FIG. 5, in some embodiments, the operating system interface may be the Portable Operating System Interface (POSIX).

[0064] In another embodiment, a lowest-layer hardware interface is disposed at the lowest layer of each operating system to realize the connection of each piece of hardware.

[0065] As shown in FIG. 6, the application layer in some embodiments of the present disclosure includes an application service layer and an application program layer.

[0066] Here, the lowest layer is an application service layer such as a vehicle system service, a signal transmission service, a signal analysis service, an air conditioning control service, a window control service, a door control service, and an identity authentication service.

[0067] The vehicle system service can provide vehicle status signals to the outside, such as power shift notification, shift status, position, speed, acceleration, electricity amount, oil amount, cruising distance, etc. The signal sending service can transmit signals to the outside, such as light signals, air conditioning on / off signals, etc. The signal analysis service can read raw signal data from a data bus and analyze it into specific signal values ​​based on a specific protocol. The air conditioning control service can provide functions related to air conditioning control, such as air conditioning on / off, air volume setting, temperature setting, etc., and the identity authentication service can perform legal authentication of the identity of an operator.

[0068] The upper layer is an application program. According to the specific application logic, the application program can be developed as an application such as a meter application, an air conditioning application, a light application, a remote control driving, a remote call, a cloud service, etc. The upper layer application can freely call the application service of the lower layer. For example, the meter application program can call the vehicle status service to obtain the vehicle information, and refresh the meter interface according to the application logic. In addition, when a signal is to be sent to the outside, the signal sending service can be called to realize the external sending of the signal. The cloud service can also call the control service to realize the turning on of the air conditioning, unlocking the windows, heating and ventilating the seats, etc.

[0069] As can be understood, the vehicle development platform of the above embodiment is provided with a hardware layer, an operating system and driver layer, a platform service layer, an interface layer, an application service layer, and an application program layer, which are interconnected and communicate with each other. During the actual application of the platform, data collected by the hardware at the lowest layer, such as vehicle data collected by sensors, is transmitted to the platform service layer through the interface of the operating system, and the platform service layer further performs corresponding processing, such as updating logs, and further transmits it to different application service layers and application program layers at the upper layers, to realize data sharing and applications, such as controlling parts such as vehicle power systems, air conditioning, or doors.

[0070] Therefore, in the vehicle development platform according to the embodiment of the present disclosure, sensors, actuators, and controllers can be flexibly arranged (decoupled) based on the logic architecture of the domain controller. It is necessary to ensure transparent sharing of data without tightly coupling sensor data collection, actuator control, and controller functions, and to support transparent sharing of data between domain controllers and between internal chips of the domain controllers because the data source is wide and the data volume is large. In addition, it is possible to have openness and collaborative development, distribute each function to different development teams, suppliers, etc., develop it independently, and seamlessly integrate it. It is possible to support different hardware platforms, and when the hardware platform is changed or upgraded, there is no need to modify each functional software module. It is possible to quickly respond to applications with high real-time requirements, such as remote control driving applications. It is possible to realize sleep and wake-up functions by performing power consumption management, control the power consumption of the vehicle, and match the clocks between the domain controllers to maintain synchronization. The vehicle domain controller is provided with Ethernet (registered trademark), which provides network security and prevents hacking.

[0071] On the one hand, by installing the domain controller development platform of the above embodiment in the domain controller of the embodiment of the present disclosure, after the development platform is installed, different users can perform corresponding independent development on the domain controller according to the specific functions they want to realize.

[0072] On the one hand, a vehicle control system according to an embodiment of the present disclosure includes at least the pre-controller in the above embodiment.

[0073] For example, in some embodiments, the vehicle control system may include at least one domain controller, as shown in FIG.

[0074] The vehicle control system may further include a gateway, a normal vehicle controller, and a network system, such as a CAN network and / or Ethernet, for connecting the controllers.

[0075] It can be understood that after the domain controller is loaded into a development platform, i.e., the operating system of the domain controller, different suppliers and development teams can develop applications of the domain controller on this platform based on the operating system to achieve different functions, that is, each function of the vehicle can be distributed to different development teams and suppliers, etc., to be independently developed, and then seamlessly integrated to complete the construction of the vehicle control system.

[0076] As can be understood, when the construction of a vehicle control system is completed, the sensors, actuators and controllers are flexibly arranged (decoupled), and the sensor data collection, actuator control and controller functions are not tightly coupled, but the data sources are wide, the data volume is large, and it supports transparent sharing of data between domain controllers and between internal chips of the domain controllers.

[0077] On the other hand, the vehicle control system according to the above embodiment is executed in the vehicle according to the embodiment of the present disclosure.

[0078] For example, a vehicle control system according to the above embodiment is executed in a railway vehicle such as a subway or light rail, and the vehicle control system includes at least one domain controller according to the above embodiment, and a development platform according to the above embodiment is built in the domain controller.

[0079] A domain controller according to an embodiment of the present disclosure includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the domain controller has the domain controller development platform described in the above embodiment installed thereon.

[0080] Below, FIG. 7 is a structural schematic diagram of a computer electronic device of a domain controller according to an embodiment of the present disclosure.

[0081] 7, the computer electronic device 500 includes a central processing unit (CPU) 501. The central processing unit 501 can execute various appropriate operations and processes based on programs stored in a read only memory (ROM) 502 or programs loaded from the storage portion 502 into a random access memory (RAM) 503. The RAM 503 further stores various programs and data required for the operation of the electronic device 500. The CPU 501, the ROM 502 and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0082] An input unit 506 including a keyboard, a mouse, etc., an output unit 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc., a storage unit 508 including a hard disk, etc., and a communication unit 509 including a network interface card such as a LAN card, a modem, etc. are connected to an I / O interface 505. The communication unit 509 executes communication processing via a network such as the Internet. A driver 510 is also connected to the I / O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the driver 510 as necessary so that a computer program read therefrom is installed in the storage unit 508 as necessary.

[0083] In particular, according to an embodiment of the present disclosure, the processes described with reference to the flowcharts above may be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product. The computer program product includes a computer program carried on a machine-readable medium. The computer program includes program code for executing the method illustrated in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via a communication unit 509 and / or installed from a removable medium 511. When the computer program is executed by a central processing unit (CPU) 501, the functions limited to the electronic device of the present disclosure are performed.

[0084] It should be noted that the computer readable medium according to the present disclosure may be a computer readable signal medium, a computer readable storage medium, or any combination of the above. The computer readable storage medium may be, but is not limited to, an electric, magnetic, optical, electromagnetic, infrared, or semiconductor electronic device, apparatus, or device, or any combination thereof. More specific examples of the computer readable storage medium may include, but are not limited to, an electrical connection having one or more conductors, a portable computer magnetic disk, a hard disk, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or flash memory), an optical fiber, a portable compact disk read only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer readable storage medium may be any tangible medium that contains or stores a program, which may be used by or in combination with an instruction executing electronic device, apparatus, or device. In the present disclosure, the computer readable signal medium may include a data signal propagated as part of a baseband or carrier wave, carrying computer readable program code. Such a propagated data signal may take a variety of forms, including, but not limited to, an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may be any computer-readable medium other than a computer-readable storage medium, which may transmit, propagate, or transmit a program for use by or in connection with an instruction-executing electronic device, apparatus, or device. The program code contained in the computer-readable medium may be transmitted in any suitable medium, including, but not limited to, wireless, wire, optical cable, RF, or the like, or any suitable combination of the above.

[0085] It should be noted that the flowcharts and block diagrams in the drawings illustrate possible system architectures, functions, and operations of the processing apparatus, method, and computer program product according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, a program segment, or a portion of code. The module, program segment, or portion of code includes one or more executable instructions for implementing a specified logical function. It should be noted that in some alternative implementations, the functions shown in the blocks may be executed in a different order from the order shown in the drawings. For example, two blocks shown in succession may actually be executed substantially in parallel or in the reverse order, depending on the related functions. It should be noted that each block in the block diagrams and / or flowcharts and combinations of blocks in the block diagrams and / or flowcharts may be implemented by dedicated electronic equipment based on hardware that performs the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0086] The units or modules according to the embodiments of the present disclosure may be implemented in the form of software or hardware. The described units or modules may be configured in a processor.

[0087] In another aspect, the computer-readable storage medium according to the present disclosure may be included in the electronic device according to the above embodiment, or may exist independently without being attached to the electronic device. The computer-readable storage medium stores one or more programs, and the programs execute corresponding data processing in each program described in the domain controller development platform according to the present disclosure by one or more processors.

[0088] As described above, the domain controller development platform, domain controller, vehicle control system, and vehicle according to the embodiments of the present disclosure develop an operating system in the domain controller, including a hardware layer, an operating system and driver layer, a platform layer, and an application layer, which are interconnected and communicate with each other from bottom to top, and then integrate all logic layers to provide a platform for the development and application of the domain controller, so that domain controllers with different functions can be independently developed to realize different functions, and a vehicle control system with complete functions can be constructed to realize real-time transmission of large amounts of data between domain controllers during the running of the vehicle system, ensuring the safety of users and vehicles, and allowing the control system to be remotely called according to actual needs.

[0089] The above description is merely a description of the preferred embodiment of the present disclosure and the technical principles applied thereto. Those skilled in the art should understand that the scope of disclosure of the present disclosure is not limited to the technical means consisting of a specific combination of the above technical features, but also includes other technical means formed by any combination of the above technical features or their equivalent features within the scope of the gist of the above disclosure. For example, the above features are technical means formed by mutually replacing technical features having similar functions disclosed in the present disclosure (not limited to these).

Claims

1. A vehicle development platform running on a vehicle controller, comprising: From bottom to top, it includes a hardware layer, an operating system and driver layer, a platform services layer, and an application layer, which are interconnected and communicate with each other; The hardware layer forms a resource pool as a carrier of software resources; The operating system and driver layer executes on the hardware layer and provides execution conditions to the platform services layer; The platform services layer runs on the operating system and transmits and manages data within a vehicle; A vehicle development platform in which the application layer loads service programs and application programs for the vehicle upper layers.

2. the platform service layer includes a data bus module, a data function module, and an operating system interface module; The data bus module is used for data transmission and sharing between or within domain controllers on a vehicle; The data function module stores and updates data; 2. The vehicle development platform of claim 1, wherein the operating system interface module processes upper layer services and applications to call operating systems and drivers.

3. The operating system in the operating system and driver layer includes the Linux operating system and the QNX operating system; 3. A vehicle development platform according to claim 1 or 2, wherein each of said operating systems corresponds to one POSIX operating system interface.

4. 4. The vehicle development platform according to claim 3, wherein a lowest-layer hardware interface is disposed at the lowest layer of each of said operating systems.

5. The vehicle development platform of any one of claims 2 to 4, characterized in that the data function module includes a time synchronization unit, a service management unit, a data persistence unit, a log and trace unit, a data update unit, an actuator control service unit, a network management, a security management, a signal collection service unit and / or a diagnostic service unit.

6. 6. The vehicle development platform according to claim 1, wherein the application layer includes an application service layer and an application program layer.

7. The vehicle development platform of claim 6, wherein the application service layer includes a vehicle status service module, a signal transmission service module, a signal analysis service module, an air conditioning control service module, a window control service module, a door control service module and / or an identity authentication service module.

8. 8. The vehicle development platform according to claim 6 or 7, wherein the application program layer includes a meter application module, an air conditioning application module, a light control application module, a door control application module, a window control application module, a remote control driving application module, and / or a cloud service application module.

9. A vehicle development platform according to any one of claims 1 to 8, characterized in that it is developed based on a service-oriented architecture.

10. A domain controller comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the vehicle development platform according to any one of claims 1 to 9 is installed therein.

11. A vehicle control system comprising at least one domain controller according to claim 10.

12. A vehicle having the vehicle control system according to claim 11 installed therein.

Images