Vehicle-mounted operation system and operation method based on QNX

Abstract

The invention relates to the technical field of vehicle-mounted operating systems, and discloses a QNX-based vehicle-mounted operating system and an operating method.The system comprises a kernel architecture module used for providing a QNX microkernel architecture and reserving underlying functions in the microkernel architecture, and the underlying functions comprise a real-time task scheduling mechanism, a dynamic content distribution mechanism and an inter-process communication mechanism; the system service library module is used for packaging a bottom layer function and providing the bottom layer function to the upper layer function module through an API (Application Program Interface); and the upper layer function module is used for calling an API interface and realizing corresponding external service based on the bottom layer function. A QNX microkernel architecture is adopted in the vehicle-mounted operation system of the QNX, so that task scheduling can accurately and efficiently respond to various real-time requirements, and the real-time response capability of the vehicle-mounted operation system is improved.

Description

Technical Field

[0001] The present disclosure relates to the technical field of vehicle-mounted operating systems, and in particular to a QNX-based vehicle-mounted operating system and an operating method thereof. Background Art

[0002] With the development of technology, the intelligent development of automobiles has become an inevitable trend. Smart cars can realize intelligent information exchange with people, cars, roads, etc. through the on-board operating system, so that vehicles have intelligent environmental perception capabilities.

[0003] The vehicle-mounted operating system in the related technology still has deficiencies in real-time response capability, which may lead to operational failures in the vehicle. Therefore, how to improve the real-time response capability of the vehicle-mounted operating system and reduce operational failures in the vehicle has become a problem that needs to be solved. Summary of the invention

[0004] In view of this, the present disclosure provides a QNX-based in-vehicle operating system and an operating method to solve the problem of how to improve the real-time response capability of the in-vehicle operating system and reduce vehicle operating failures.

[0005] On the one hand, the present disclosure provides a QNX-based in-vehicle operating system, and the system includes: a kernel architecture module, a system service library module and an upper-layer functional module, wherein: the kernel architecture module is used to provide a QNX microkernel architecture, and retain underlying functions in the microkernel architecture, and the underlying functions include: a real-time task scheduling mechanism, a dynamic content allocation mechanism and an inter-process communication mechanism; the system service library module is used to encapsulate the underlying functions and provide the underlying functions to the upper-layer functional module through an API interface; the upper-layer functional module is used to call the API interface, and based on the real-time task scheduling mechanism, the dynamic content allocation mechanism and the inter-process communication mechanism in the underlying functions, implement corresponding external services.

[0006] On the other hand, the present disclosure also provides an operation method, which includes: a kernel architecture module, which provides a QNX microkernel architecture and retains underlying functions in the microkernel architecture, and the underlying functions include: a real-time task scheduling mechanism, a dynamic content allocation mechanism and an inter-process communication mechanism; a system service library module, which encapsulates the underlying functions and provides the underlying functions to an upper-level function module through an API interface; and an upper-level function module, which calls the API interface and implements corresponding external services based on the real-time task scheduling mechanism, dynamic content allocation mechanism and inter-process communication mechanism in the underlying functions.

[0007] On the other hand, the present disclosure further provides a computer device, which includes: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor implements the above-mentioned operation method by executing the computer instructions.

[0008] On the other hand, the present disclosure further provides a computer-readable storage medium, on which computer instructions are stored, and the computer instructions are used to enable a computer to implement the above-mentioned operating method.

[0009] Through the QNX-based in-vehicle operating system and operating method of the above-mentioned embodiments of the present invention, by adopting the QNX microkernel architecture, task scheduling can accurately and efficiently respond to various real-time needs, thereby improving the real-time response capability of the in-vehicle operating system in a rapidly changing driving environment.

[0010] In addition, a microkernel architecture is adopted, which retains only the most basic underlying functions in the kernel and encapsulates other functions in a modular manner. This allows the in-vehicle operating system to dynamically load and replace different upper-level functional modules without affecting the kernel, thereby improving the flexibility of the system and further improving the real-time performance of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 An exemplary schematic diagram showing an architecture of a QNX-based vehicle operating system according to an embodiment of the present disclosure;

[0013] Figure 2 An exemplary schematic diagram showing the architecture of a system service library module of a QNX-based vehicle operating system according to an embodiment of the present disclosure;

[0014] Figure 3 An exemplary schematic diagram showing the architecture of an upper-layer functional module of a vehicle operating system based on QNX according to an embodiment of the present disclosure;

[0015] Figure 4 An exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system security encryption module according to an embodiment of the present disclosure;

[0016] Figure 5 An exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system communication network module according to an embodiment of the present disclosure;

[0017] Figure 6 An exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system graphical interface module according to an embodiment of the present disclosure;

[0018] Figure 7 An exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system domain controller module according to an embodiment of the present disclosure;

[0019] Figure 8 An exemplary schematic diagram showing the architecture of an upper-layer functional module of another vehicle operating system based on QNX according to an embodiment of the present disclosure;

[0020] Fig. 9 An exemplary schematic diagram showing the architecture of another QNX-based in-vehicle operating system advanced driver assistance module, development tool and support module, and ecosystem module according to an embodiment of the present disclosure;

[0021] Fig.10 is a flowchart of an operation method provided by an embodiment of the present disclosure;

[0022] Fig.11 is a detailed flowchart of an operation method provided by an embodiment of the present disclosure;

[0023] Fig.12 It is a structural diagram of another monitoring device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] With the development of mobile Internet, smart cars, as an innovative development direction of the automotive industry, are gradually becoming popular and changing the structure and functions of traditional cars. Smart cars add advanced sensors, controllers, actuators and other equipment based on traditional vehicles, and realize intelligent information exchange with people, cars, roads, etc. through on-board sensor systems and information terminals, so that vehicles have intelligent environmental perception capabilities. Through intelligent analysis, smart cars can automatically judge driving safety and dangerous conditions, and drive autonomously according to user needs, ultimately achieving the purpose of replacing human operation.

[0025] In the related art, for example, in the patent document with publication number CN106891897A, a vehicle-mounted operating system, a smart car and a vehicle-mounted control method are proposed, wherein the vehicle-mounted operating system includes: an instruction generation module, suitable for generating multiple control instructions based on the received vehicle-mounted signal; an instruction classification module, suitable for assigning corresponding processing levels to the control instructions respectively; an instruction distribution module, suitable for distributing multiple control instructions to corresponding processing modules in sequence according to the order of processing levels from high to low; a processing module, suitable for executing corresponding control instructions.

[0026] However, the following technical problems still exist in the vehicle operating system of the related technology:

[0027] 1. The instruction classification process requires judging, sorting and distributing each instruction, which may increase the processing delay of the system. Especially in high-concurrency task scenarios, priority conflicts or scheduling queue blockages are prone to occur, thus affecting the real-time response capability of the system.

[0028] 2. The system does not have a reasonable isolation mechanism. Multiple tasks may share resources or data, causing mutual interference between tasks, triggering system anomalies, and thus reducing the security of the system.

[0029] To solve the above problems, various embodiments of the present disclosure provide a QNX-based in-vehicle operating system, the system comprising: a kernel architecture module, a system service library module and an upper-layer functional module, wherein: the kernel architecture module is used to provide a QNX microkernel architecture, retaining underlying functions in the microkernel architecture, the underlying functions including: a real-time task scheduling mechanism, a dynamic content allocation mechanism and an inter-process communication mechanism; the system service library module is used to encapsulate the underlying functions and provide the underlying functions to the upper-layer functional module through an API interface; the upper-layer functional module is used to call the API interface, and based on the real-time task scheduling mechanism, the dynamic content allocation mechanism and the inter-process communication mechanism in the underlying functions, implement corresponding external services.

[0030] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0031] refer to Figure 1 , Figure 1 An exemplary schematic diagram of the architecture of a vehicle operating system based on QNX according to an embodiment of the present disclosure is shown. Figure 1 As shown, the system 10 includes: a kernel architecture module 101, a system service library module 102 and an upper layer function module 103, wherein:

[0032] The kernel architecture module 101 is used to provide a QNX microkernel architecture, and retain underlying functions in the microkernel architecture, wherein the underlying functions include: a real-time task scheduling mechanism, a dynamic content allocation mechanism, and an inter-process communication mechanism;

[0033] The system service library module 102 is used to encapsulate the underlying functions and provide the underlying functions to the upper-layer function modules through the API interface;

[0034] The upper layer function module 103 is used to call the API interface and implement the corresponding external service based on the real-time task scheduling mechanism, dynamic content allocation mechanism and inter-process communication mechanism in the underlying functions.

[0035] In this embodiment, QNX may be a real-time operating system based on a microkernel architecture, wherein the microkernel architecture may refer to a system kernel having only the most basic operating system services, and other functions running in the user space in the form of independent processes or services.

[0036] Furthermore, the QNX-based in-vehicle operating system 10 may refer to an embedded operating system developed on the QNX operating system platform specifically for the automotive field.

[0037] Furthermore, the kernel architecture module 101 may refer to the kernel and infrastructure module, that is, the core module in the vehicle operating system 10 for providing underlying basic services and operating system operation. The system service library module 102 may refer to the system service and library module, which may serve as the middle layer of the system 10, further encapsulate and expand the kernel functions, and provide a standardized application programming interface (Application Programming Interface, API) interface to the upper-layer functional module for calling and utilizing the underlying resources and services. The upper-layer functional module 103 may be a specific application and functional module in the vehicle operating system, which is used to implement external services and user interactions of the vehicle.

[0038] In one possible implementation, the kernel architecture module 101, a real-time task scheduling mechanism in the underlying functions retained in the microkernel architecture, can ensure that tasks in the system 10 are arranged according to priority, and respond to task requirements in real time by adopting priority preemptive scheduling.

[0039] The dynamic content allocation mechanism in the underlying function can allocate memory resources in real time according to task requirements to avoid memory waste. It can automatically release memory resources when the task is completed to prevent memory leaks.

[0040] The inter-process communication mechanism in the underlying functions can provide data exchange and synchronization methods between different processes, ensuring that each module can work together efficiently.

[0041] Here, the kernel architecture module 101 is the core of the system, which provides an efficient and reliable operating environment for upper-layer functions by coordinating resources, task scheduling and communication. The real-time task scheduling mechanism, dynamic content allocation mechanism and inter-process communication mechanism ensure the real-time response capability, memory usage efficiency and inter-module collaboration performance of the system 10.

[0042] The system service library module 102 can encapsulate the functions of the underlying kernel architecture through an API interface and provide them to the upper-layer functional modules for calling in a standardized manner.

[0043] Here, each API interface can follow a unified calling specification to avoid problems caused by inconsistent calling methods; the calling of each API interface is subject to permission control to ensure that only authorized upper-level functional modules 103 can access the corresponding functions.

[0044] The upper-layer function module 103 interacts with the underlying functions in the kernel framework module 101 by calling the API interface provided by the system service library module to implement at least one external function.

[0045] As an example, the external functions may include, but are not limited to: information services, entertainment services, security services, control services, etc.

[0046] In the QNX-based vehicle operating system and operation method of the above-mentioned embodiment of the present disclosure, by adopting the QNX microkernel architecture, task scheduling can accurately and efficiently respond to various real-time requirements, and improve the real-time response capability of the vehicle operating system in a rapidly changing driving environment. By adopting the microkernel architecture, only the most basic underlying functions are retained in the kernel, and other functions are modularly packaged, so that the vehicle operating system can dynamically load and replace different upper-level functional modules without affecting the kernel, thereby improving the flexibility of the system and further improving the real-time performance of the system.

[0047] In a possible implementation of the above embodiment, the system service library module 102 includes: a process management unit 1021, a memory management unit 1022, a file management unit 1023, a library and API unit 1024, a POSIX library and graphics library unit 1025, wherein;

[0048] The process management unit 1021 is used to manage the life cycle of at least one process and thread in the system, as well as the communication mechanism between processes;

[0049] The memory allocation unit 1022 is used to allocate memory resources to the process when the process is created by the process management unit 1021;

[0050] The file management unit 1023 is used to obtain the buffer memory from the memory allocation unit 1022, and read or write the file in the storage device of the system based on the buffer memory;

[0051] A library and API unit 1024, for providing a system call interface, the system call interface is used to interact with the operating system and hardware;

[0052] The POSIX library and graphics library unit 1025 is used to extend the system call interface and provide a standardized API interface and graphics rendering support for the system call interface; the standardized API interface complies with the POSIX standard, and the standardized API interface is used to call at least one of the process management unit 1021, the memory allocation unit 1022 and the file management unit 1023.

[0053] refer to Figure 2 , Figure 2 FIG. 1 is an exemplary schematic diagram showing the architecture of a system service library module of a vehicle operating system based on QNX according to an embodiment of the present disclosure. Figure 2 As shown, the system service library module 102 includes: a process management unit 1021, a memory management unit 1022, a file management unit 1023, a library and API unit 1024, and a POSIX library and graphics library unit 1025.

[0054] In this embodiment, the process management unit 1021 can be used to manage the life cycle of processes and threads in the system, including the creation, scheduling, and destruction of processes, as well as inter-process communication mechanisms.

[0055] When creating a process, the process management unit 1021 can allocate memory resources through the memory allocation unit 1022 ; when destroying a process, the process management unit 1021 can release memory resources through the memory allocation unit 1022 .

[0056] The memory allocation unit 1022 may be used to dynamically allocate and reclaim memory resources in the system to ensure that each process uses memory as needed.

[0057] The memory allocation unit 1022 allocates buffer memory to the file management unit 1023 so that the file management unit 1023 performs data read and write operations based on the buffer memory.

[0058] The file management unit 1023 may be used to perform read and write operations on files in the storage device of the system 10 .

[0059] Among them, the process created by the process management unit 1021 needs to complete the file operation task through the file management unit 1023, for example, the process reads the configuration file and the process writes the log information.

[0060] Furthermore, the file management unit 1023 may be used to support at least one file system, for example, a Journaled File System.

[0061] The library and API unit 1024 may be used to provide a system call interface so that the upper layer function module 103 can interact with the operating system and hardware.

[0062] Among them, the process management unit 1021, the memory allocation unit 1022 and the file management unit 1023 can implement corresponding process scheduling, memory allocation and file reading and writing by calling the API interface provided by the library and API unit 1024.

[0063] Furthermore, the API interface provided by the library and API unit 1024 can be expanded by the POSIX library and graphics library unit 1025 into a standardized interface that complies with the POSIX standard, so that it has stronger cross-platform compatibility.

[0064] The POSIX library and graphics library unit 1025 may be used to provide a standardized API interface that complies with the POSIX standard and supports a graphics rendering function.

[0065] Among them, the Portable Operating System Interface (POSIX) standard may be a predefined set of open system interface specifications for improving the portability and compatibility of the operating system.

[0066] Furthermore, by providing a standardized API interface, cross-platform compatibility and development standardization can be ensured; by providing a graphics rendering function for implementing user interface design, the smoothness and beauty of the interface display can be ensured.

[0067] As an example, during the dashboard display process of the vehicle in which the system 10 is located, the memory management unit 1022 can be called through the standardized API interface that complies with the POSIX standard in the POSIX library and graphics library unit 1025 to allocate a display buffer, and the rendering of the vehicle status can be completed through the POSIX library and the graphics library in the graphics library unit 1025.

[0068] In the QNX-based vehicle operating system and operation method of the above-mentioned embodiment of the present disclosure, the process management unit 1021 implements modular design within the system through an inter-process communication mechanism, supports efficient and low-latency data exchange between different modules, and improves the overall operating efficiency and functional flexibility of the system. The memory management unit 1022 can dynamically allocate memory resources so that system resources can be flexibly allocated according to demand to avoid the problem of memory waste or insufficiency. The file management unit 1023 can provide file read and write functions, optimize the access efficiency of storage devices through a buffer mechanism, and reduce the delay of read and write operations. The library and API unit 1024 can shield the complexity of the underlying operating system and hardware by providing a system call interface, so that the upper-level functional module can easily call the underlying function. The POSIX library and graphics library unit 1025 can support the implementation of complex image rendering functions, provide efficient support for user interfaces and display systems, improve the visualization capabilities and user experience of the system, and also provide a consistent development environment to ensure the cross-platform compatibility of software and reduce transplantation costs.

[0069] In a possible implementation of the above embodiment, the upper-layer functional module 103 includes at least one of the following: a security encryption module 1031 , a communication network module 1032 , a graphical interface module 1033 , and a domain controller module 1034 .

[0070] refer to Figure 3 , Figure 3 FIG. 1 is an exemplary schematic diagram showing the architecture of an upper-layer functional module of a vehicle operating system based on QNX according to an embodiment of the present disclosure. Figure 3 As shown, the upper-layer functional module 103 includes: a security encryption module 1031 , a communication network module 1032 , a graphical interface module 1033 , and a domain controller module 1034 .

[0071] In this embodiment, the security encryption module 1031 can be used to ensure the security of the system 10 and the vehicle;

[0072] The communication network module 1032 can be used to manage the communication network inside and outside the vehicle;

[0073] Graphical interface module 1033, which can be used to provide a user interaction interface and display functions;

[0074] The domain controller module 1034 can be used to manage the resources and task scheduling of different functional domains of the vehicle to achieve integration and centralized control of the vehicle.

[0075] Among them, the graphical interface module 1033 can be used to support the development and operation of instrument panels, infotainment systems and touch screens.

[0076] The functional domain of a vehicle may refer to dividing the different functional modules of the vehicle into several relatively independent functional areas, each functional domain focusing on realizing a specific type of function.

[0077] As an example, the functional domains of a vehicle may include, but are not limited to: a power system domain, a chassis control domain, an infotainment domain, a communication network domain, etc.

[0078] The security encryption module 1031, communication network module 1032, graphical interface module 1033, and domain controller module 1034 in the above-mentioned upper-layer functional module 103 can call the underlying functions provided by the kernel architecture module 101 through the standardized API interface provided by the system service library module 102 to implement their respective upper-layer functions.

[0079] In the QNX-based vehicle operating system and operating method of the above embodiment of the present disclosure, by dividing complex vehicle functions into relatively independent modules, the system coupling is reduced, and maintainability and scalability are enhanced. Each submodule achieves seamless collaboration based on the API interface and underlying functions, thereby improving the overall efficiency and performance of the system.

[0080] In a possible implementation of the above embodiment, the security encryption module 1031 includes: a security authentication unit 1031a, a security partition unit 1031b, a network security unit 1031c, a protocol determination unit 1031d, and a security boot unit 1031e, wherein:

[0081] The security authentication unit 1031a is used to verify the identity information of at least one of the user, device and application when processing sensitive data, and classify the identity information into legal identity and illegal identity;

[0082] The security partitioning unit 1031b is used to perform spatial partitioning and temporal partitioning on the processing of key functions and non-key functions based on the preset partitioning result by using hardware isolation and / or virtualization technology;

[0083] The protocol determination unit 1031c is used to provide the data encryption protocol and the secure communication protocol to the network security unit 1031d;

[0084] The network security unit 1031d is used to obtain the legal identity from the security authentication unit 1031a, and authorize the legal identity based on the data encryption protocol and the security communication protocol so that the legal identity can communicate on the network;

[0085] The security startup unit 1031e is used to determine whether there is an illegal identity in the system based on the security authentication unit 1031a, and start the system when it is determined that there is no illegal identity in the system.

[0086] refer to Figure 4 , Figure 4 FIG. 1 is an exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system security encryption module according to an embodiment of the present disclosure. Figure 4 As shown, the security encryption module 1031 includes: a security authentication unit 1031a, a security partition unit 1031b, a network security unit 1031c, a protocol determination unit 1031d, and a security boot unit 1031e.

[0087] In this embodiment, the security authentication unit 1031a can be used to verify identity information related to security and divide the identity information into legal identities and illegal identities.

[0088] The security authentication unit 1031a verifies the identities of users, devices, applications and other targets to ensure that only legitimate identities can access and operate sensitive data when processing such data.

[0089] Here, a legitimate identity can refer to a user, device, or application that has been authenticated, authorized, and confirmed to meet the system security requirements.

[0090] An illegal identity may refer to a subject that attempts to break through system security controls to perform unauthorized operations, or an identity forged by a malicious actor. For example, an illegal identity may include, but is not limited to: hacker attacks, malware, and unauthorized external devices.

[0091] In one possible implementation, the domain controller module 1034 divides the functions in the system 10 into at least one functional domain, and the functional domain can be divided into critical functions and non-critical functions according to security requirements and operational risks.

[0092] The security partition unit 1031b can be used to spatially and temporally partition the processing of critical functions and non-critical functions based on the preset functional domain division results, using hardware isolation and / or virtualization technology to ensure that the operation of critical functions is not interfered with by other non-critical functions.

[0093] Here, key functions may refer to functions that are directly related to system security, stability, reliability, or the execution of core tasks; if the above functions are lost or damaged, the system may not be able to operate normally, and may even endanger personnel safety or cause significant losses.

[0094] For example, key functions may include, but are not limited to: autonomous driving control, battery management system, engine control unit.

[0095] Non-critical functions can refer to functions that do not directly affect the security, stability or core mission of the system. Even if the above functions fail or are interrupted, the system can continue to operate normally.

[0096] For example, non-critical functions may include but are not limited to: in-vehicle entertainment system, navigation system, and entertainment system.

[0097] The protocol determination unit 1031c may be used to determine and provide a suitable data encryption protocol and a secure communication protocol for encrypting and protecting data exchange in the system.

[0098] The network security unit 1031d can be used to authorize the legal identity by receiving the legal identity information from the security authentication unit 1031a and using the data encryption protocol and the secure communication protocol determined by the protocol determination unit 1031c; the network security unit 1031d can allow the legal identity to communicate on the network after the legal identity is authenticated to ensure the security of the communication process and avoid unauthorized access.

[0099] The secure boot unit 1031e can determine whether there is an illegal identity in the system by accessing the secure authentication unit 1031a. If it is determined that there is an illegal identity, the boot process will be interrupted and the system 10 will not be able to enter a normal state. If it is determined that there is no illegal identity, the system 10 will be started to ensure that the system 10 has complete security protection from the boot stage to prevent the system 10 from being maliciously tampered with or infected by a virus.

[0100] In the QNX-based vehicle operating system and operating method of the above embodiment of the present disclosure, the various units in the security encryption module 1031 work closely together to ensure the multi-layer security protection of the system, thereby increasing the security of the vehicle system. Each unit works at a different security level, from identity authentication to data encryption, to authorization and startup verification of network communications, ensuring that the system can prevent potential security threats at all stages.

[0101] In a possible implementation of the above embodiment, the communication network module 1032 includes: a network protocol stack unit 1032a, a TCP / IP unit 1032b, a vehicle internal communication unit 1032c, an inter-process communication unit 1032d, a message passing unit 1032e, and a shared memory unit 1032f, wherein:

[0102] A network protocol stack unit 1032a, used to support communication between the system 10 and an external network;

[0103] TCP / IP unit 1032b, used to support communication between system 10 and external devices and external servers;

[0104] The vehicle internal communication unit 1032c is used to manage the communication between at least one module inside the system 10;

[0105] An inter-process communication unit 1032d, for managing communication between at least one process in the system;

[0106] The message transmission unit 1032e is used to process message transmission between different processes, between different modules or between different systems;

[0107] The shared memory unit 1032f is used to set a shared memory area between at least one process and use the shared memory area to perform memory sharing.

[0108] refer to Figure 5 , Figure 5 FIG. 1 is an exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system communication network module according to an embodiment of the present disclosure. Figure 5 As shown, the communication network module 1032 includes: a network protocol stack unit 1032a, a TCP / IP unit 1032b, a vehicle internal communication unit 1032c, an inter-process communication unit 1032d, a message passing unit 1032e, and a shared memory unit 1032f.

[0109] In this embodiment, the network protocol stack in the network protocol stack unit 1032a may be a collection of different communication protocols, which may determine how data is transmitted in the network, including operations such as data encapsulation, transmission, and unpacking. Through the network protocol stack in the network protocol stack unit 1032a, the system 10 may send a request to an external network or receive data.

[0110] The TCP / IP unit 1032b may be a part of the network protocol stack in the network protocol stack unit 1032a, and may be used to support the system 10 to communicate with an external device or an external server through an IP address and a port number.

[0111] Among them, the Transmission Control Protocol / Internet Protocol (TCP / IP) family may include TCP and IP, and may be responsible for ensuring reliable transmission and correct routing of data in a network.

[0112] The vehicle internal communication unit 1032c can be used for information exchange and collaboration between at least one independent module within the system 10.

[0113] The inter-process communication unit 1032d can be used to adopt an inter-process communication (IPC) mechanism to manage data sharing and mutual cooperation between at least one process in the system 10 to ensure safe and effective information exchange between different processes.

[0114] The message transmission unit 1032e may be used to process message transmission between different processes, between different modules, or between different systems;

[0115] The shared memory unit 1032f may be used to provide a shared memory area for at least one process, so that different processes can directly access and exchange data through the shared memory area.

[0116] Among them, shared content can be an efficient way of inter-process communication, allowing processes to read and write memory directly without going through other resources.

[0117] In one possible implementation, the network protocol stack unit 1032a and the TCP / IP unit 1032b are used to process the connection and data exchange between the system and external networks and external devices; while the vehicle internal communication unit 1032c, the inter-process communication unit 1032d, the message passing unit 1032e and the shared memory unit 1032f are used to process data sharing and collaboration between modules and processes within the system.

[0118] In the QNX-based in-vehicle operating system and operating method of the above-mentioned embodiment of the present disclosure, the network protocol stack unit 1032a ensures the stability and security of data transmission on the network by providing standard communication protocol support. The TCP / IP unit 1032b ensures that the system can be stably connected to external hardware devices or remote servers, thereby improving the scalability of the system. The vehicle internal communication unit 1032c can ensure low-latency and high-bandwidth communication by managing data exchange between different modules within the vehicle system, thereby ensuring the real-time control capability of the vehicle. The inter-process communication unit 1032d ensures that different processes can efficiently exchange information by managing the communication between different processes, thereby further improving the real-time performance of the system.

[0119] In a possible implementation of the above embodiment, the graphical interface module 1033 includes: a virtualization unit 1033a, a digital cockpit platform unit 1033b, an infotainment unit 1033c, and a dashboard display unit 1033d, wherein:

[0120] A virtualization unit 1033a, configured to use virtualization technology to enable at least one upper functional module 103 to run in a corresponding virtual machine;

[0121] The digital cockpit platform unit 1033b is used to display vehicle information, entertainment content, and navigation maps of the vehicle in which the system is located to the user based on a human-computer interaction interface;

[0122] Infotainment unit 1033c, used to provide multimedia functions to users based on a human-computer interaction interface;

[0123] The instrument panel display unit 1033d is used to display the vehicle status information, warning information and key data information to the user.

[0124] refer to Figure 6 , Figure 6 FIG. 1 is an exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system graphical interface module according to an embodiment of the present disclosure. Figure 6 As shown, the graphical interface module 1033 includes: a virtualization unit 1033a, a digital cockpit platform unit 1033b, an infotainment unit 1033c, and a dashboard display unit 1033d.

[0125] In this embodiment, the virtualization unit 1033a can be used to adopt virtualization technology to run multiple operating systems at the same time, so that each upper functional module can run independently in its virtual environment to avoid mutual interference and conflict of system resources.

[0126] The digital cockpit platform unit 1033b can be used to display vehicle information, entertainment content, navigation maps and other content to users based on a human-computer interaction interface.

[0127] Among them, the digital cockpit platform unit 1033b enables drivers and passengers to easily obtain information about the vehicle and entertainment system by providing users with an intuitive interactive interface.

[0128] The infotainment unit 1033c can be used to provide entertainment content and navigation information to the user with the help of the digital cockpit platform unit 1033b.

[0129] The instrument panel display unit 1033d can be used to provide the user with vehicle status information, warning information and key data information with the help of the digital cockpit platform unit 1033b. The key data information may include but is not limited to: vehicle speed, fuel level, engine temperature, etc.

[0130] In the QNX-based in-vehicle operating system and operation method of the above-mentioned embodiment of the present disclosure, the virtualization unit 1033a implements the isolation and independent operation of the system modules by allocating each upper functional module to an independent virtual machine, thereby improving the stability of the in-vehicle system. Through virtualization technology, various system resources can be flexibly allocated, further improving the flexibility of the in-vehicle system. The collaboration of each unit enables the seamless display of in-vehicle information and entertainment content, ensuring that the driver can obtain key information in real time, improving safety and driving experience.

[0131] In a possible implementation of the above embodiment, the domain controller module 1034 includes: domain controller software 1034a, a centralized management module 1034b, and a high-performance computing module 1034c, wherein:

[0132] Domain controller software 1034a, for dividing at least one function of the vehicle in which the system is located into corresponding functional domains;

[0133] Centralized management module 1034b, used for centralized management of at least one functional domain of the vehicle;

[0134] The high performance computing module 1034c is used to process computing-intensive tasks in at least one functional domain.

[0135] refer to Figure 7 , Figure 7 FIG. 1 is an exemplary schematic diagram showing the architecture of a QNX-based vehicle operating system domain controller module according to an embodiment of the present disclosure. Figure 7 As shown, the domain controller module 1034 includes: domain controller software 1034a, a centralized management module 1034b, and a high-performance computing module 1034c.

[0136] In this embodiment, the domain controller software 1034a may be the core of the domain controller module 1034, and may be used to perform a logical division of vehicle functions according to different functional requirements and determine at least one functional domain.

[0137] The centralized management module 1034b can be used to uniformly manage multiple functional domains of the vehicle and implement status monitoring, resource allocation and coordination of each functional domain.

[0138] The centralized management module 1034b can make use of the functional domain division information provided by the domain controller software 1034a to ensure that various functions of the vehicle can operate in an orderly and reliable manner through the management of each functional domain.

[0139] The centralized management module can also use the high-performance computing module 1034c to ensure that the processing of computing-intensive tasks does not affect the normal operation of other functional domains.

[0140] The high performance computing module 1034c is used to process computing-intensive tasks, which may refer to tasks that require a large amount of computing resources to complete.

[0141] For example, computationally intensive tasks may include, but are not limited to: image and video processing, autonomous driving algorithms, and sensor data processing.

[0142] Furthermore, the high-performance computing module 1034c can provide computing power support for the centralized management module 1034b, and when computing-intensive tasks are required, the high-performance computing module 1034c can be scheduled to execute the tasks.

[0143] In the QNX-based vehicle operating system and operation method of the above-mentioned embodiment of the present disclosure, by dividing different functions into multiple functional domains, the system can run different functional modules without interfering with each other, thereby enhancing the stability and scalability of the system. The collaboration between the centralized management module 1034b and the high-performance computing module 1034c can dynamically allocate computing resources according to the needs of the task, ensuring that computing-intensive tasks are supported by sufficient computing power without affecting the normal operation of other functional domains. This efficient resource management can improve the overall performance and response speed of the system.

[0144] In a possible implementation of the above embodiment, the upper-layer functional module 103 may further include: an advanced driving assistance module 1035 , a development tool and support module 1036 , and an ecosystem module 1037 .

[0145] In this embodiment, the advanced driving assistance module 1035 may include: an ADAS platform 1035a, a sensor integration unit 1035b, and an algorithm and decision unit 1036c;

[0146] The development tool and support module 1036 may include: QNX software development platform 1036a, development tool chain 1036b, simulator and testing tool 1036c, document and community support module 1036d, technical document unit 1036e, developer community 1036f;

[0147] The ecosystem module 1037 may include: a hardware support unit 1037a, a hardware platform compatibility unit 1037b, a software ecosystem unit 1037c, and a third-party application support unit 1037d.

[0148] refer to Figure 8 , Figure 8 FIG. 1 is an exemplary schematic diagram showing the architecture of an upper functional module of another vehicle operating system based on QNX according to an embodiment of the present disclosure. Figure 8 As shown, the upper-level functional module 103 may also include: an advanced driving assistance module 1035 , a development tool and support module 1036 , and an ecosystem module 1037 .

[0149] refer to Fig. 9 , Fig. 9 FIG. 1 is an exemplary schematic diagram showing the architecture of another QNX-based vehicle operating system advanced driver assistance module, development tools and support module, and ecosystem module according to an embodiment of the present disclosure. Fig. 9As shown, the advanced driving assistance module 1035 may include: ADAS platform 1035a, sensor integration unit 1035b, algorithm and decision unit 1036c, the development tool and support module 1036 may include: QNX software development platform 1036a, development tool chain 1036b, simulator and testing tool 1036c, document and community support module 1036d, technical document unit 1036e, developer community 1036f, and the ecosystem module 1037 may include: hardware support unit 1037a, hardware platform compatibility unit 1037b, software ecosystem unit 1037c, and third-party application support unit 1037d.

[0150] The Advanced Driver Assistance System (ADAS) platform 1035a may be the core infrastructure of the entire Advanced Driver Assistance System 1035, responsible for coordinating the collaboration, resource allocation and management of various modules. The ADAS platform 1035a may be used to improve the driving experience, enhance the safety of the vehicle, and assist the driver in completing complex driving tasks through a variety of sensors and algorithms.

[0151] The sensor integration unit 1035b may be a hardware part of the advanced driver assistance system 1035, and may be responsible for integrating information from different sensors, collecting data about the vehicle's surroundings by integrating a variety of sensors, fusing and preprocessing the raw data, and providing the raw data to the algorithm and decision unit 1036c for further analysis and processing.

[0152] The sensor integration unit 1035b may include but is not limited to: a camera, a radar, and a lidar sensor.

[0153] The algorithm and decision unit 1036c can be used to perform in-depth analysis on the data collected by the sensor integration unit 1035b, generate control instructions, and realize functions such as adaptive cruise control, lane keeping, and automatic parking.

[0154] The development tools and support module 1036 can be used to support system development, debugging, testing, etc., so that developers can build and optimize the system more efficiently.

[0155] The QNX software development platform 1036a may be a complete development environment based on the QNX operating system, providing a variety of tools and resources necessary for development to support developers in developing applications on the QNX operating system.

[0156] The development tool chain 1036b can be a collection of application development, compilation and debugging, and can include: compiler, debugger, linker. The tool chain can convert the source code written by the developer into machine code and debug it. The compiler compiles the code into a target program, and the debugger helps the developer identify and fix errors during the development process.

[0157] The simulator and test tools 1036c can be used to simulate the system environment and perform functional verification. The technical documentation unit 1036e can be used to provide detailed documentation required by developers to help them understand how to use development tools, libraries, and API interfaces. The developer community 1036f can be used to provide technical exchanges and answer questions. The ecosystem module 1037 can be used to provide hardware and software support for developers, promote the integration of third-party applications, and ensure system compatibility.

[0158] The hardware support unit 1037a can be used to provide drivers, hardware interface protocols, and configuration files for specific hardware devices to ensure that the system can operate normally in different hardware environments. The hardware platform compatibility unit 1037b can ensure that the system can run across platforms by abstracting hardware differences. The software ecosystem unit 1037c can be used to provide support for operating systems, development platforms, libraries, and other software to ensure that the system can be integrated with other software and services. The third-party application support unit 1037d can be used to ensure that the system can support and be compatible with third-party application software.

[0159] In the QNX-based in-vehicle operating system and operating method of the above-mentioned embodiment of the present disclosure, the advanced driving assistance module 1035 improves the intelligence and automation level of the in-vehicle operating system, and the development tool and support module 1036 provides developers with a wealth of tools and resources, shortens the development cycle and improves development efficiency and quality. The ecosystem module 1037 ensures the hardware compatibility, software ecosystem integration and third-party application support of the system, and enhances the scalability and flexibility of the system.

[0160] In a specific embodiment, reference Fig.10 , Fig.10 is a flowchart of an operation method provided by an embodiment of the present disclosure, which is applied to the above Figure 1 The QNX-based in-vehicle operating system shown in the figure may include the following steps:

[0161] Step S1001, the kernel architecture module provides the QNX microkernel architecture and retains the underlying functions in the microkernel architecture. The underlying functions include: real-time task scheduling mechanism, dynamic content allocation mechanism and inter-process communication mechanism.

[0162] Step S1002: The system service library module encapsulates the bottom-level functions and provides the bottom-level functions to the upper-level function modules through the API interface.

[0163] Step S1003, the upper layer function module calls the API interface to implement the corresponding external service based on the real-time task scheduling mechanism, dynamic content allocation mechanism and inter-process communication mechanism in the underlying function.

[0164] In one embodiment, reference Fig.11 , Fig.11 is a detailed flow chart of an operation method provided by an embodiment of the present disclosure, which is applied to the above Figure 1 The QNX-based in-vehicle operating system shown in the figure may include the following steps:

[0165] Step S1101, system architecture design;

[0166] Here, a modular and scalable QNX system architecture is designed;

[0167] Step S1102, hardware platform selection;

[0168] Here, select the hardware platform suitable for the QNX system;

[0169] Step S1103, operating system installation;

[0170] Here, install the QNX operating system in the hardware platform, that is, use the Neutrino host installation CD provided by QNX to install the operating system;

[0171] Step S1104, system startup and configuration;

[0172] Here, configure the initial system settings and enter the operation interface. After the system starts, it will automatically detect the hardware configuration. No password is required to log in to the system so that you can quickly enter the root permission, which is suitable for debugging during the development stage;

[0173] Step S1105, process management and dynamic loading;

[0174] Here, dynamic loading of processes and modules in the system is managed;

[0175] Step S1106, building a development environment;

[0176] Here, install the QNX software development platform, start compiling the Integrated Development Environment (IDE), and configure the connection between the virtual machine and the IDE;

[0177] Step S1107, software integration and testing;

[0178] Here, import the pre-downloaded board support package (BSP) for compilation, import the example demo for compilation and testing to verify whether the core functions meet the design requirements;

[0179] Step S1108, network structure configuration;

[0180] Here, configure the system's network communication capabilities;

[0181] Step S1109, virtualization technology support;

[0182] Here, multiple virtual machines are run on a single system-level chip through the Hypervisor virtualization solution provided by the QNX system.

[0183] See also Fig.12 , Fig.12 is a schematic diagram of the structure of another QNX-based vehicle operating system provided by an embodiment of the present disclosure, such as Fig.12 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig.12 A processor 10 is taken as an example.

[0184] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0185] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0186] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0187] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0188] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Fig.12 The example of connecting through bus is taken in the following.

[0189] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0190] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0191] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0192] A part of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0193] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A QNX-based in-vehicle operating system, characterized in that: The system includes: a kernel architecture module, a system service library module and an upper layer function module, wherein: A kernel architecture module, used to provide a QNX microkernel architecture, in which underlying functions are retained, including: a real-time task scheduling mechanism, a dynamic content allocation mechanism, and an inter-process communication mechanism; A system service library module is used to encapsulate the underlying functions and provide the underlying functions to the upper-layer function modules through an API interface; The upper-layer function module is used to call the API interface and implement corresponding external services based on the real-time task scheduling mechanism, dynamic content allocation mechanism and inter-process communication mechanism in the underlying functions.

2. The system according to claim 1, characterized in that The system service library module includes: a process management unit, a memory management unit, a file management unit, a library and API unit, a POSIX library and a graphics library unit, wherein; A process management unit, used to manage the life cycle of at least one process and thread in the system, as well as the communication mechanism between processes; A memory allocation unit, configured to allocate memory resources to a process when the process is created by the process management unit; A file management unit, configured to obtain a buffer memory from the memory allocation unit, and read or write a file in a storage device of the system based on the buffer memory; A library and API unit, for providing a system call interface, wherein the system call interface is used to interact with an operating system and hardware; The POSIX library and graphics library unit are used to expand the system call interface and provide a standardized API interface and graphics rendering support for the system call interface; the standardized API interface complies with the POSIX standard, and the standardized API interface is used to call at least one of the process management unit, the memory allocation unit and the file management unit.

3. The system according to claim 1, characterized in that The upper-layer functional module includes at least one of the following: a security encryption module, a communication network module, a graphical interface module, and a domain controller module.

4. The system according to claim 3, characterized in that The security encryption module includes: a security authentication unit, a security partition unit, a network security unit, a protocol determination unit, and a security boot unit, wherein: A security authentication unit, used to verify the identity information of at least one of a user, a device, and an application when processing sensitive data, and to classify the identity information into a legal identity and an illegal identity; A security partitioning unit, used to perform spatial and temporal partitioning of the processing of critical functions and non-critical functions based on a preset partitioning result by using hardware isolation and / or virtualization technology; A protocol determination unit, configured to provide a data encryption protocol and a secure communication protocol to the network security unit; A network security unit, used to obtain a legal identity from the security authentication unit, and authorize the legal identity based on the data encryption protocol and the security communication protocol, so that the legal identity can perform network communication; The security startup unit is used to determine whether there is an illegal identity in the system based on the security authentication unit, and start the system when it is determined that there is no illegal identity in the system.

5. The system according to claim 3, characterized in that The communication network module includes: a network protocol stack unit, a TCP / IP unit, a vehicle internal communication unit, an inter-process communication unit, a message passing unit, and a shared memory unit, wherein: A network protocol stack unit, used to support the communication between the system and the external network; TCP / IP unit, used to support the communication between the system and external devices and external servers; a vehicle internal communication unit, for managing communication between at least one module within the system; an inter-process communication unit for managing communication between at least one process in the system; Message passing unit, used to handle message passing between different processes, modules or systems; The shared memory unit is used to set a shared memory area between the at least one process and use the shared memory area to perform memory sharing.

6. The system according to claim 3, characterized in that The graphical interface module includes: a virtualization unit, a digital cockpit platform unit, an infotainment unit, and an instrument panel display unit, wherein: A virtualization unit, used to use virtualization technology to enable at least one upper functional module to run in a corresponding virtual machine respectively; The digital cockpit platform unit is used to display vehicle information, entertainment content, and navigation maps of the vehicle in which the system is located to the user based on a human-computer interaction interface; An infotainment unit, configured to provide multimedia functions to the user based on the human-computer interaction interface; The instrument panel display unit is used to display the vehicle status information, warning information and key data information to the user.

7. The system according to claim 3, characterized in that The domain controller module includes: domain controller software, centralized management module, high-performance computing module, wherein: Domain controller software for dividing at least one function of a vehicle in which the system is located into corresponding functional domains; A centralized management module, used for centrally managing at least one functional domain of the vehicle; A high performance computing module is used to process computing-intensive tasks in the at least one functional domain.

8. An operating method, characterized in that: The method comprises: A kernel architecture module provides a QNX microkernel architecture, in which underlying functions are retained, including: a real-time task scheduling mechanism, a dynamic content allocation mechanism, and an inter-process communication mechanism; The system service library module encapsulates the underlying functions and provides the underlying functions to the upper-layer function modules through the API interface; The upper-layer function module calls the API interface to implement corresponding external services based on the real-time task scheduling mechanism, dynamic content allocation mechanism and inter-process communication mechanism in the underlying functions.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the operating method described in claim 8 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the operating method described in claim 8.

Images