CN117785231A - Vehicle-mounted operating system and vehicle - Google Patents
Vehicle-mounted operating system and vehicle Download PDFInfo
- Publication number
- CN117785231A CN117785231A CN202410206887.3A CN202410206887A CN117785231A CN 117785231 A CN117785231 A CN 117785231A CN 202410206887 A CN202410206887 A CN 202410206887A CN 117785231 A CN117785231 A CN 117785231A
- Authority
- CN
- China
- Prior art keywords
- scene
- vehicle
- advanced
- configuration
- communication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000006870 function Effects 0.000 claims abstract description 147
- 230000006854 communication Effects 0.000 claims description 94
- 238000004891 communication Methods 0.000 claims description 87
- 238000000034 method Methods 0.000 claims description 29
- 238000011161 development Methods 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 17
- 230000000007 visual effect Effects 0.000 claims description 6
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 230000008878 coupling Effects 0.000 abstract description 6
- 238000010168 coupling process Methods 0.000 abstract description 6
- 238000005859 coupling reaction Methods 0.000 abstract description 6
- 238000007726 management method Methods 0.000 description 25
- 238000010586 diagram Methods 0.000 description 17
- 230000006978 adaptation Effects 0.000 description 3
- 238000002955 isolation Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000000889 atomisation Methods 0.000 description 2
- 210000004556 brain Anatomy 0.000 description 1
- 230000002950 deficient Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The invention belongs to the technical field of vehicle management, and discloses a vehicle-mounted operating system and a vehicle. An in-vehicle operating system comprising: the system software layer comprises a basic system kernel and an advanced function platform, wherein the basic system kernel is constructed based on a macro kernel and is used for providing basic system functions, and the advanced function platform is constructed based on a micro kernel and is used for providing advanced system functions; and the functional software layer is used for storing application programs, the application programs run based on the system functions provided by the system software layer, and the application programs comprise general application programs and custom-developed application programs. Because the application program of the functional software layer only depends on the system functions provided by the system software layer, and the advanced functional platform is constructed based on microkernel, wherein the advanced system functions have no coupling relation with each other, so that the vehicle-mounted operating system can be cut and deployed according to actual needs, and the actually needed software modules are selected.
Description
Technical Field
The invention relates to the technical field of vehicle management, in particular to a vehicle-mounted operating system and a vehicle.
Background
With the overall development of the vehicle industry, the software on the vehicle is more and more complex, the traditional vehicle industry is transforming and upgrading around a 'software defined vehicle', the software value in future vehicles will greatly exceed the mechanical hardware on the vehicle, and the vehicles gradually transform from highly electromechanical terminals to intelligent, extensible and continuously upgradeable mobile electronic terminals. With the rapid development of intelligent network vehicles, the vehicles are added with more intelligent sensors, massive data needs to be collected, processed and shared, the importance of a vehicle-mounted OS system is increasingly prominent as the brain of the intelligent vehicles, and the intelligent capability of automatic driving and the like is faster to land compared with passenger vehicles for special vehicle types such as commercial vehicles (commercial special vehicles), so that the demands of the vehicle-mounted OS are more urgent.
The current business special car industry provides an integral vehicle-mounted operating system architecture based on an SOA architecture, the SOA architecture is split towards services, a perfect communication adaptation layer needs to be provided, the layer becomes gradually complex along with the increase of compatible protocols, the SOA architecture cannot provide a perfect plug-in management mechanism, dynamic expansion and decoupling of functional services are not facilitated, the SOA architecture is mainly used for carrying out inter-process communication between services, and the communication efficiency is low;
meanwhile, the adoption technology in the industry does not consider generalized scene management and safety management, cannot be decoupled in specific scenes, is deficient in different vehicle type adaptation capability and different scene adaptation capability, and has no convenient and effective development mode when facing vehicle-mounted software developers.
Disclosure of Invention
The invention mainly aims to provide a vehicle-mounted operating system and a vehicle, and aims to solve the technical problem that the application effect of the operating system in a special commercial vehicle in the prior art is poor.
To achieve the above object, the present invention provides a vehicle-mounted operating system including:
the system software layer comprises a basic system kernel and a advanced function platform, wherein the basic system kernel is constructed based on a macro kernel and is used for providing basic system functions, and the advanced function platform is constructed based on a micro kernel and is used for providing advanced system functions;
and the functional software layer is used for storing application programs, the application programs run based on the system functions provided by the system software layer, and the application programs comprise general application programs and custom-developed application programs.
Optionally, the advanced system function includes a communication management function, and the advanced function platform is internally compatible with multiple communication protocols;
the advanced function platform is further used for selecting a target protocol from the multiple communication protocols according to a communication scene; inter-process communication is implemented for the communication process based on the target protocol.
Optionally, the advanced function platform is further configured to determine whether a communication authority exists between the communication processes according to the communication domain and a preset whitelist; and when the communication rights exist, selecting a target protocol from the plurality of communication protocols according to the actual scene.
Optionally, the advanced system function includes a hierarchical plug-in management function;
the advanced function platform is further used for acquiring a plug-in configuration file corresponding to the application program; loading or unloading plug-ins in a process space of the application program according to the plug-in configuration files;
wherein the plugins are divided into a plurality of levels, and a high-level plugin can correspond to at least one low-level plugin.
Optionally, the advanced system function includes a task scheduling function;
the advanced function platform is further used for dividing the acquired tasks into a plurality of task groups, the tasks in the task groups are ordered according to task priorities, each task group corresponds to a different thread pool, and the tasks in the task groups are sequentially executed by the thread pools corresponding to the task groups according to the task priorities;
wherein the tasks are submitted by applications in the functional software layer or generated by system functions in the system software layer.
Optionally, the advanced function platform is further configured to divide the received task into a plurality of task groups, where each task group corresponds to a processor, and the processor corresponding to the task group executes the task in the task group.
Optionally, the advanced system function includes a scene engine function;
the advanced function platform is further used for determining an algorithm, an application program, an application function and/or a system function required to be called for switching to the next scene state according to the scene state of the target application, the data fed back by the target application and the scene configuration definition attribute.
Optionally, the advanced system function includes a scene orchestration function;
the advanced function platform is further configured to perform service scene configuration according to configuration information fed back by a preset scene configuration file or a visual configuration interface, where the service scene configuration is configured to perform service application configuration and scene attribute configuration on an application program corresponding to the service scene, and the service application configuration includes algorithm registration configuration, algorithm creation configuration and application node data stream configuration.
Optionally, the vehicle-mounted operating system further comprises an algorithm shelf, wherein independent controls encapsulated by meta-interface controls provided by the system software layer are stored in the algorithm shelf, and the independent controls are divided into a plurality of layers;
the algorithm shelf is used for selecting corresponding independent controls or meta-interface controls according to the combination information fed back by the visualized low-code development interface, and packaging according to the selected independent controls or meta-interface controls to obtain new independent controls.
Optionally, the vehicle-mounted operating system further includes a general security platform, at least one full security scene is stored in the general security platform, the full security scene corresponds to at least one security sub-scene, the security sub-scene corresponds to at least one atomic event, and a security triggering condition of the full security scene is constructed by all the atomic events corresponding to the full security scene;
the universal safety platform is used for generating an atomic event according to the running information of each application program; if the atom event meets the safety triggering condition corresponding to the full-quantity safety scene, acquiring scene safety configuration corresponding to the full-quantity safety scene; and carrying out security decision according to the scene security configuration, and determining the operation to be executed.
In addition, in order to achieve the above object, the present invention also proposes a vehicle in which the on-vehicle operating system as described above is provided.
The embodiment of the invention provides a vehicle-mounted operating system, which comprises: the system software layer comprises a basic system kernel and an advanced function platform, wherein the basic system kernel is constructed based on a macro kernel and is used for providing basic system functions, and the advanced function platform is constructed based on a micro kernel and is used for providing advanced system functions; and the functional software layer is used for storing application programs, the application programs run based on the system functions provided by the system software layer, and the application programs comprise general application programs and custom-developed application programs. Because the application program of the functional software layer only depends on the system functions provided by the system software layer, and the advanced functional platform is constructed based on microkernel, wherein the advanced system functions have no coupling relation with each other, so that the vehicle-mounted operating system can be cut and deployed according to actual needs, and the actually needed software modules are selected.
Drawings
FIG. 1 is a flow chart of a first embodiment of a vehicle-mounted operating system according to the present invention;
FIG. 2 is a diagram illustrating an architecture of an operating system according to an embodiment of the invention;
FIG. 3 is a schematic diagram of functional components of an advanced function platform according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a communication management flow according to an embodiment of the invention;
FIG. 5 is a schematic diagram illustrating a card management according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a task scheduling process according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of a scene engine execution flow according to an embodiment of the invention;
FIG. 8 is a flow chart of a second embodiment of the vehicle operating system of the present invention;
FIG. 9 is a schematic diagram of an algorithm shelf structure according to an embodiment of the present invention;
FIG. 10 is a diagram illustrating security monitoring and decision making according to an embodiment of the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
An embodiment of the present invention provides a vehicle-mounted operating system, and referring to fig. 1, fig. 1 is a schematic diagram of a first embodiment of a vehicle-mounted operating system according to the present invention.
In this embodiment, the vehicle-mounted operating system includes:
and the system software layer comprises a basic system kernel and an advanced function platform.
And the functional software layer is used for storing application programs, and the application programs run based on the system functions provided by the system software layer.
It should be noted that, the basic system kernel is built based on the macro kernel, and is used for providing basic system functions, i.e. relevant operation logic for providing the basic system functions is loaded to kernel mode operation. The advanced platform functions are constructed based on microkernel and used for providing advanced system functions, the advanced system functions are mutually isolated, the functions are mutually independent, and decoupling is achieved.
Among other things, the underlying system functions may be the most basic functions provided by the system, such as: interfacing with the connected hardware through virtualization, code running logic, etc. The advanced system function may be an advanced function developed further by means of code writing or the like on the basic system function, for example: communication management, plug-in management, task scheduling, state management, scene engine, and other advanced system functions.
It should be noted that, the application program includes a general application program and a custom-developed application program, and the general application program may be an application program that is developed in a general-purpose form and may be applied to most of vehicle hardware, for example: for intelligent driving services, provided general positioning services, general perception services, general prediction services, and the like. The custom developed application may be an application developed for a particular vehicle or a particular scenario, such as: and according to different vehicle types, customizing developed vehicle control services when intelligent driving is performed.
In practical applications, the running of an application depends on basic system functions provided by the system software layer, and in some cases, may also depend on advanced system functions provided by the system software layer.
In a specific implementation, since the application program of the functional software layer only depends on the system function provided by the system software layer, but does not depend on other application programs in the functional software layer, the coupling between the application programs is low, and the application programs do not affect each other, so that the vehicle-mounted operating system of the embodiment can be cut and deployed, that is, only partial application programs required by the application programs are reserved in the functional software layer for deployment.
The advanced function platform is built based on microkernel, so that the advanced system functions in the advanced function platform are not coupled with each other, and therefore, when in cutting deployment, the miniaturized running state deployment can be adopted, namely only basic system kernels are deployed, and then one or more advanced system functions provided by the advanced function platform are selected and deployed according to actual needs.
For ease of understanding, the description will now be given with reference to fig. 2 and 3, but the present solution is not limited thereto. Fig. 2 is a schematic diagram of an operating system architecture of the present embodiment, and fig. 3 is a schematic diagram of functional components of an advanced functional platform of the present embodiment.
As shown in fig. 2, the vehicle-mounted operating system may include a functional software layer and a system software layer, where the functional software layer may be provided with general applications such as a map engine, a general positioning service, a general sensing service, a general prediction service, a general planning service, and a general control service, and may further include a general framework/man-machine interaction framework that can only be driven, so that a developer can customize and develop the application; the System software layer may include a System kernel (basic System kernel, macro kernel (MacroKernel) setting) and platform software (i.e. advanced function platform, system kernel (System Core) setting) where, in order to facilitate interfacing with hardware, the vehicle-mounted operating System further includes a hardware abstraction module and a virtualization management module, where the virtualization management module is used to store virtualization information of the entity hardware, and the hardware abstraction module is used to store an abstract object abstracted according to the virtualization information of the entity hardware.
The advanced SYSTEM functions of the advanced function platform (CORE SYSTEM) may include communication management, plug-in management, task scheduling, state management, a scene engine, and differentiated service plug-ins set by a software framework, where the differentiated service plug-ins may be service plug-ins developed for a specific scene or a specific vehicle according to actual needs, as shown in fig. 3.
In a specific implementation, the advanced system function may include a communication management function, and in order to cope with a complex communication requirement, the advanced functional platform may be compatible with multiple communication protocols, for example: the bottom layer of the advanced function platform can be compatible with SOME IP and DDS communication protocols at the same time, and the TSN network is fused in the DDS, so that the advanced function platform can realize the following functions:
the advanced function platform is further used for selecting a target protocol from the multiple communication protocols according to a communication scene; inter-process communication is implemented for the communication process based on the target protocol.
It should be noted that the communication scenario may be determined by information of both communication parties, for example: the sub thread A1 and the sub thread A2 in the process A communicate, and the communication scene is in-process communication at the moment; the application process A and the application process B are communicated, if the A and the B are in the same communication domain at this time, namely, the A and the B are in a process group corresponding to the same communication domain, the communication scene is intra-domain communication at this time, and if the A and the B belong to different communication domains, the communication scene is inter-domain communication at this time.
Among them, for inter-domain communication, there are also cross-host communication and communication with the host, for example: if the communication domains to which the A and the B belong are in the same host (namely on the same hardware equipment), the communication domain is judged to be communicated with the host; if the communication domains to which A and B belong are on different hosts, the communication is judged to be cross-host communication.
In a specific implementation, selecting the target protocol from the plurality of communication protocols according to the communication scenario may be to use, as the target protocol, a communication protocol applicable in the communication scenario among the plurality of communication protocols. Because the advanced function platform is compatible with multiple communication protocols, there may be multiple communication protocols applicable to the same communication scene, and then the target protocol may be selected from the multiple communication protocols through a preset policy, for example: the communication protocols suitable for the communication scene are multiple, and one can be selected from the QoS strategies as a target protocol at the moment so as to improve the hard real-time and deterministic communication capability.
Furthermore, because different communication isolation requirements exist in practical application, in order to meet the requirements, the advanced function platform can also be used for determining whether communication authorities exist between communication processes according to a communication domain and a preset white list; and when the communication rights exist, selecting a target protocol from the plurality of communication protocols according to the actual scene.
It should be noted that, according to the needs of practical applications, only communication is allowed in a communication domain in some cases, and communication is allowed between specific communication domains in some cases, in order to meet the situations, a first layer of communication isolation may be set according to the communication domain, and then a second layer of communication isolation may be set according to a preset whitelist, so that whether communication authority exists between communication processes may be determined according to the communication domain and the preset whitelist, and when the communication authority exists, a target protocol may be selected from multiple communication protocols according to the practical scenario.
For ease of understanding, the description will now be given with reference to fig. 4, but the present solution is not limited thereto. Fig. 4 is a schematic diagram of a communication management flow of the present embodiment.
As shown in fig. 4, when communication management is performed, communication can be divided into a reader and a writer, if communication is initiated by the writer, whether the reader of the same process exists can be detected first, and if so, communication is performed through an intra-process concentric, i.e. an intra-process notifier;
if the reader of the same process does not exist, detecting whether the reader of the same host exists, and if so, using a shared memory transmitter and a shared memory notifier to communicate;
if the cross-host reader does not exist, detecting whether the cross-host reader exists, and if so, using the shared memory transmitter and the shared memory notifier to communicate.
When the existence of the same host reader is detected or the existence of the cross host reader is detected, whether the communication domain or the host to which the reader belongs is in a white list or not can be detected, and when the communication domain or the host exists in the white list, the shared memory transmitter and the shared memory notifier are used for communication.
In a specific implementation, the advanced system function may include a plug-in management function, and then the advanced function platform is further configured to obtain a plug-in configuration file corresponding to the application program; and loading or unloading the plug-in the process space of the application program according to the plug-in configuration file.
It should be noted that, when the application program runs, in part of the cases, specific plugins, such as algorithm plugins, scene plugins, and the like, in this case, the application program may set the plugin configuration file to declare the plugin that should be loaded, and then the advanced function platform may acquire the plugin configuration file corresponding to the application program at this time, and determine, according to the configuration information in the plugin configuration file, the plugin that should exist in the process space of the application program at this time, so as to load or unload the plugin in the process space of the application program.
Wherein, the plugins can be stored in a plugin library, the plugins can be divided into a plurality of levels, and a high-level plugin can correspond to at least one low-level plugin.
For ease of understanding, the description will now be given with reference to fig. 5, but the present solution is not limited thereto. Fig. 5 is a schematic diagram of card management in this embodiment.
As shown in fig. 5, the plug-ins can be divided into four levels of plug-ins according to the levels: app, module, component, algoPlugin an App may comprise a plurality of modules, a Module may comprise a plurality of components, a Component may comprise a plurality of Algo plug in, and then the application program may declare the plug-ins that need to be loaded in a configuration file (Config), and then the advanced function platform may find all the plug-ins that need to be loaded according to the configuration file, combine them, and load or unload the plug-ins in the process space of the application program according to the plug-ins in the combined form.
In a specific implementation, the advanced system function may include a task scheduling function, where task scheduling may be divided into two modes, i.e., classical scheduling and scheduling, and if the scheduling mode is classical scheduling, the advanced functional platform is further configured to divide the acquired task into a plurality of task groups, where tasks in the task groups are ordered according to task priorities, each task group corresponds to a different thread pool, and tasks in the task groups are sequentially executed by the thread pool corresponding to the task groups according to the task priorities;
and if the executed scheduling mode is scheduling, the advanced function platform is further used for dividing the received task into a plurality of task groups, each task group corresponds to one processor respectively, and the processor corresponding to the task group executes the task in the task group.
It should be noted that, the task managed by the task schedule may be submitted by an application in the functional software layer or may be generated by a system function in the system software layer.
For ease of understanding, the description will now be given with reference to fig. 6, but the present solution is not limited thereto. Fig. 6 is a schematic diagram of task scheduling processing according to the present embodiment.
As shown in fig. 6, if classical scheduling is adopted, the advanced function platform divides the tasks into a plurality of task groups, and groups the tasks in each group again based on the priorities of the tasks (or does not group and directly orders according to the priorities of the tasks), and divides the tasks into a plurality of subgroups, wherein each task group corresponds to a processor pool (i.e. a thread pool), and the thread pool obtains the execution of the task waiting to be executed from the bound task groups according to the priorities of the tasks, so that the task with high priority is guaranteed to be executed first.
If the scheduling is adopted, the advanced function platform divides the tasks into a plurality of task groups, each task group is allocated with a processor, and the processor only executes the tasks in the bound task groups so as to ensure that the tasks can be stably executed.
The classical scheduling and the scheduling can be adopted at the same time, and then the mixed scheduling mode is adopted, at the moment, the advanced functional platform divides the task part into a plurality of task groups, each task group is allocated with a processor, the processor only executes the tasks in the bound task group, and the rest default tasks are allocated according to the classical scheduling.
In a specific implementation, the advanced system function may include a scene engine function, and then the advanced function platform is further configured to determine an algorithm, an application program, an application function and/or a system function that need to be invoked for switching to a next scene state according to a scene state where the target application is located, data fed back by the target application, and a scene configuration definition attribute.
It should be noted that, in order to avoid functional coupling, it is necessary to avoid direct reference or call of functions of other application programs in application program development, while in a specific service scenario, functions of application programs need to be executed sequentially, and in part cases, functions of different application programs need to be executed in cooperation, on this basis, an advanced functional platform is further used to determine, according to a scenario state where a target application is located, data fed back by the target application, a scenario configuration definition attribute, an algorithm, an application program, an application function and/or a system function that need to be called when switching to a next scenario state is determined, so that it is ensured that functions of the application programs can be executed in cooperation without functional coupling.
The service scenario may correspond to a plurality of scenario states, and each scenario state may correspond to a different algorithm, application function, and/or system function.
Furthermore, in order to ensure that the scene engine can normally determine the algorithm, the application program, the application function and/or the system function to be invoked, the advanced system function can further include a scene arrangement function, and the advanced function platform is further configured to perform service scene configuration according to the configuration information fed back by the preset scene configuration file or the visual configuration interface.
It should be noted that, the service scenario configuration may be service application configuration and scenario attribute configuration for an application program corresponding to a service scenario, where the service application configuration includes algorithm registration configuration, algorithm creation configuration, and application node data flow configuration, for example: setting that the service scene comprises sub-scenes A and B, and calling an algorithm XXX aiming at the sub-scene A, wherein the data flow is App_1-App_2-App_3; the sub-for sub-scenario B, the algorithm to be invoked is BXX, and the data flow is App_1-App_2.
For ease of understanding, the description will now be given with reference to fig. 7, but the present solution is not limited thereto. Fig. 7 is a schematic diagram of a scene engine execution flow according to the present embodiment.
As shown in fig. 7, a scene state machine is set in the scene engine, the scene state machine reads various attributes of scene configuration definition (namely scene configuration definition attribute), acquires scene state, acquires current state information, combines the scene configuration definition attribute and current state information according to data fed back by a target application function to determine whether the scene needs to be switched, acquires the next scene state (namely scene state which should be subsequently reached to the sub-scene) when the scene needs to be switched (such as switching from the sub-scene a to the sub-scene B), reads configuration definition attribute corresponding to the next scene state from the scene configuration definition attribute, and determines an algorithm, an application program, an application function and/or a system function to be invoked according to the configuration definition attribute.
The algorithm to be called can be an algorithm plug-in, the application program can be an application program in a functional software layer, the application function can be a certain function in the application program, and the system function can be a basic system function and/or an advanced system function provided by the system software layer.
The current state information may represent a sub-scene where the application is currently located, and an execution state of the sub-scene, such as whether the currently corresponding sub-scene has been executed. The scene definition attribute may be set through scene arrangement, as shown in fig. 7, and the scene configuration is performed for a certain service scene, where multiple sub-scenes (such as scene a and scene B in fig. 7) may be included, and each sub-scene may have a corresponding scene attribute and/or a scene algorithm, and the algorithm, the application program, the application function, and/or the system function that need to be invoked by the sub-scene are specified through the scene attribute and/or the scene algorithm.
The present embodiment provides a vehicle-mounted operating system, including: the system software layer comprises a basic system kernel and an advanced function platform, wherein the basic system kernel is constructed based on a macro kernel and is used for providing basic system functions, and the advanced function platform is constructed based on a micro kernel and is used for providing advanced system functions; and the functional software layer is used for storing application programs, the application programs run based on the system functions provided by the system software layer, and the application programs comprise general application programs and custom-developed application programs. Because the application program of the functional software layer only depends on the system functions provided by the system software layer, and the advanced functional platform is constructed based on microkernel, wherein the advanced system functions have no coupling relation with each other, so that the vehicle-mounted operating system can be cut and deployed according to actual needs, and the actually needed software modules are selected.
Referring to fig. 8, fig. 8 is a flowchart of a second embodiment of an on-vehicle operating system according to the present invention.
Based on the above first embodiment, the vehicle-mounted operating system of the present embodiment further includes:
and the algorithm shelf is used for selecting the corresponding independent control or meta-interface control according to the combination information fed back by the visualized low-code development interface, and packaging according to the selected independent control or meta-interface control to obtain a new independent control.
It should be noted that, the algorithm shelf stores an independent control encapsulated by a meta-interface control provided by the system software layer, where the independent control is divided into a plurality of layers, for example: the independent controls can be classified into an atomic scene service, an algorithm service and an algorithm plug-in according to the hierarchy from high to low. The meta-interface control may be the finest granularity of functionality control provided by the system software layer.
In a specific implementation, the vehicle-mounted operating system further provides a low-code development interface and displays the low-code development interface, a developer can display an independent control or a meta-interface control in the low-code development interface or provide a query selection inlet of the independent control or the meta-interface control, so that the developer can select the independent control or the meta-interface control to be used in the low-code development interface by adopting visual operation, and combine the selected independent control or the meta-interface control, if the developer clicks a submit button in the low-code development interface, the low-code development interface feeds back combined information, and at the moment, the algorithm shelf can select the corresponding independent control or the meta-interface control according to the combined information fed back by the low-code development interface to carry out combined encapsulation, so that a new independent control is formed.
The plug-in library or the functional software layer may also be updated according to the new independent control or application program formed, for example: if the formed new independent control is an algorithm plug-in, the algorithm plug-in can be loaded into a plug-in library at the moment; if the formed new independent control is an atomic scene service or an algorithm service, the new independent control can be loaded into a functional software layer.
For ease of understanding, the description will now be given with reference to fig. 9, but the present solution is not limited thereto. Fig. 9 is a schematic diagram of the algorithm shelf structure of the present embodiment.
As shown in fig. 9, the algorithm shelf may store multiple levels of independent controls, where the independent controls may be classified into an atomic scene service control, an algorithm service control and an algorithm plug-in control from high to low according to the levels, and the independent controls may be combined from bottom to top according to the levels, i.e., where the atomic scene service control may include at least one algorithm service control, and the algorithm service control may include at least one algorithm plug-in control. The independent control is formed by packaging the meta-interface control, an algorithm shelf control (namely the independent control) and the meta-interface control can be displayed in the control visual interface, a developer can adopt low-code visual development to generate an algorithm plug-in or an algorithm service according to the meta-interface control, and an atomic scene service is generated based on the algorithm plug-in or the service control;
the new independent control formed can be added to a local person (such as local personal storage management shown in fig. 9) or a cloud space storage (such as cloud storage management shown in fig. 9) for storage. Local personal storage management can be uploaded to cloud storage management through online resource sharing, and offline sharing can also be carried out through resource library packaging and migration.
Further, in order to ensure the safety of the vehicle on which the vehicle-mounted operating system is mounted, in this embodiment, the vehicle-mounted operating system may further include:
the universal safety platform is used for generating an atomic event according to the running information of each application program; if the atom event meets the safety triggering condition corresponding to the full-quantity safety scene, acquiring scene safety configuration corresponding to the full-quantity safety scene; and carrying out security decision according to the scene security configuration, and determining the operation to be executed.
It should be noted that at least one full-volume security scene is stored in the universal security platform, the full-volume security scene corresponds to at least one security sub-scene, the security sub-scene corresponds to at least one atomic event, and the security triggering condition of the full-volume security scene is constructed by all the atomic events corresponding to the full-volume security scene.
It can be understood that if the atomic event generated by the running information of the application program meets the safety triggering condition corresponding to a certain full-quantity safety scene, the actual scene of the vehicle running with the vehicle-mounted operating system is very similar to the full-quantity safety scene, and the vehicle may have a potential safety hazard and needs to be processed at this time.
For ease of understanding, the present solution will now be described with reference to fig. 10, but is not limited thereto. Fig. 10 may be a schematic diagram of security monitoring and decision making in this embodiment.
As shown in fig. 10, an atomization event library is provided in the vehicle-mounted operating system, and a plurality of general or custom atomic events (i.e., events with extremely small granularity) are stored in the atomization event library, so as to meet the security requirement of diversified scenes, at this time, the combination capability of not limiting the scenes and granularity can be provided, at this time, at least one atomic event can be assembled into a security sub-scene, at least one security sub-scene can be assembled into a full-volume security scene, and then, the triggering condition of the full-volume security scene can be constructed according to all the atomic events corresponding to the full-volume security scene (for example, the triggering condition is set to be that all the atomic events corresponding to the full-volume security scene appear);
and then, the vehicle-mounted operating system can perform safety monitoring, namely, the operating information of the application program is intercepted and acquired by calling a communication interface and combining with atomic event code embedding in the application program, the atomic event generated when the application program operates is determined according to the operating information, then the atoms are matched with the safety triggering conditions corresponding to all the safety scenes, and when the safety triggering conditions corresponding to any all the safety scenes are met, the scene safety configuration of the all the safety scenes is acquired, and safety decision is made according to the scene safety configuration, so that the potential safety hazard can be eliminated as far as possible.
The embodiment also provides an algorithm shelf, wherein the independent control encapsulated by the meta-interface control provided by the system software layer is stored in the algorithm shelf, and a visualized low-code development interface is provided, so that a developer can select the corresponding independent control or the meta-interface control to construct a new independent control according to actual needs, the development difficulty of the developer is greatly reduced, and the developer can rapidly perform function development.
In addition, the embodiment of the invention also provides a vehicle, and the vehicle is provided with the vehicle-mounted operating system provided by any embodiment.
Furthermore, it should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. Read Only Memory)/RAM, magnetic disk, optical disk) and including several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (11)
1. An in-vehicle operating system, the in-vehicle operating system comprising:
the system software layer comprises a basic system kernel and an advanced function platform, wherein the basic system kernel is constructed based on a macro kernel and is used for providing basic system functions, and the advanced function platform is constructed based on a micro kernel and is used for providing advanced system functions;
and the functional software layer is used for storing application programs, the application programs run based on the system functions provided by the system software layer, and the application programs comprise general application programs and custom-developed application programs.
2. The vehicle-mounted operating system of claim 1, wherein the advanced system functions include a communication management function, the advanced function platform being internally compatible with a plurality of communication protocols;
the advanced function platform is further used for selecting a target protocol from the multiple communication protocols according to a communication scene; inter-process communication is implemented for the communication process based on the target protocol.
3. The vehicle-mounted operating system according to claim 2, wherein the advanced function platform is further configured to determine whether communication rights exist between communication processes according to a communication domain and a preset whitelist; and when the communication rights exist, selecting a target protocol from the plurality of communication protocols according to the actual scene.
4. The on-board operating system of claim 1, wherein the advanced system functions include hierarchical plug-in management functions;
the advanced function platform is further used for acquiring a plug-in configuration file corresponding to the application program; loading or unloading plug-ins in a process space of the application program according to the plug-in configuration files;
wherein the plugins are divided into a plurality of levels, and a high-level plugin can correspond to at least one low-level plugin.
5. The vehicle-mounted operating system of claim 1, wherein the advanced system function comprises a task scheduling function;
the advanced function platform is further used for dividing the acquired tasks into a plurality of task groups, the tasks in the task groups are ordered according to task priorities, each task group corresponds to a different thread pool, and the tasks in the task groups are sequentially executed by the thread pools corresponding to the task groups according to the task priorities;
wherein the tasks are submitted by applications in the functional software layer or generated by system functions in the system software layer.
6. The vehicle-mounted operating system according to claim 5, wherein the advanced function platform is further configured to divide the received task into a plurality of task groups, each task group corresponds to a processor, and the processors corresponding to the task groups execute the tasks in the task groups.
7. The in-vehicle operating system of claim 1, wherein the advanced system functions include a scene engine function;
the advanced function platform is further used for determining an algorithm, an application program, an application function and/or a system function required to be called for switching to the next scene state according to the scene state of the target application, the data fed back by the target application and the scene configuration definition attribute.
8. The in-vehicle operating system of claim 7, wherein the advanced system functions include a scene orchestration function;
the advanced function platform is further configured to perform service scene configuration according to configuration information fed back by a preset scene configuration file or a visual configuration interface, where the service scene configuration is configured to perform service application configuration and scene attribute configuration on an application program corresponding to the service scene, and the service application configuration includes algorithm registration configuration, algorithm creation configuration and application node data stream configuration.
9. The vehicle-mounted operating system of claim 1, further comprising an algorithm shelf in which individual controls encapsulated by meta-interface controls provided by the system software layer are stored, the individual controls being divided into a plurality of tiers;
the algorithm shelf is used for selecting corresponding independent controls or meta-interface controls according to the combination information fed back by the visualized low-code development interface, and packaging according to the selected independent controls or meta-interface controls to obtain new independent controls.
10. The vehicle-mounted operating system according to claim 1, further comprising a universal security platform, wherein at least one full security scene is stored in the universal security platform, the full security scene corresponds to at least one security sub-scene, the security sub-scene corresponds to at least one atomic event, and the security triggering condition of the full security scene is constructed by all the atomic events corresponding to the full security scene;
the universal safety platform is used for generating an atomic event according to the running information of each application program; if the atom event meets the safety triggering condition corresponding to the full-quantity safety scene, acquiring scene safety configuration corresponding to the full-quantity safety scene; and carrying out security decision according to the scene security configuration, and determining the operation to be executed.
11. A vehicle in which an on-board operating system as claimed in any one of claims 1 to 10 is provided.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410206887.3A CN117785231A (en) | 2024-02-26 | 2024-02-26 | Vehicle-mounted operating system and vehicle |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410206887.3A CN117785231A (en) | 2024-02-26 | 2024-02-26 | Vehicle-mounted operating system and vehicle |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117785231A true CN117785231A (en) | 2024-03-29 |
Family
ID=90394892
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410206887.3A Pending CN117785231A (en) | 2024-02-26 | 2024-02-26 | Vehicle-mounted operating system and vehicle |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117785231A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20210026688A1 (en) * | 2018-04-20 | 2021-01-28 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and Apparatus for Scheduling Processor Core, and Storage Medium |
| CN114296716A (en) * | 2021-11-18 | 2022-04-08 | 深圳海星智驾科技有限公司 | Function configuration method and device for intelligent operation of engineering machinery and electronic equipment |
| CN115576331A (en) * | 2022-12-07 | 2023-01-06 | 深圳海星智驾科技有限公司 | Automatic driving operation method and device for engineering machinery, electronic equipment and system |
| CN117075980A (en) * | 2023-08-29 | 2023-11-17 | 博泰车联网科技(上海)股份有限公司 | Cabin control system, image processing method and device, vehicle and electronic equipment |
| CN117149378A (en) * | 2023-08-04 | 2023-12-01 | 斑马网络技术有限公司 | Task scheduling method, device, equipment and medium of intelligent automobile operating system |
| CN117325888A (en) * | 2023-11-13 | 2024-01-02 | 深圳海星智驾科技有限公司 | Vehicle automatic driving state monitoring method and device, vehicle machine system and storage medium |
-
2024
- 2024-02-26 CN CN202410206887.3A patent/CN117785231A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20210026688A1 (en) * | 2018-04-20 | 2021-01-28 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and Apparatus for Scheduling Processor Core, and Storage Medium |
| CN114296716A (en) * | 2021-11-18 | 2022-04-08 | 深圳海星智驾科技有限公司 | Function configuration method and device for intelligent operation of engineering machinery and electronic equipment |
| CN115576331A (en) * | 2022-12-07 | 2023-01-06 | 深圳海星智驾科技有限公司 | Automatic driving operation method and device for engineering machinery, electronic equipment and system |
| CN117149378A (en) * | 2023-08-04 | 2023-12-01 | 斑马网络技术有限公司 | Task scheduling method, device, equipment and medium of intelligent automobile operating system |
| CN117075980A (en) * | 2023-08-29 | 2023-11-17 | 博泰车联网科技(上海)股份有限公司 | Cabin control system, image processing method and device, vehicle and electronic equipment |
| CN117325888A (en) * | 2023-11-13 | 2024-01-02 | 深圳海星智驾科技有限公司 | Vehicle automatic driving state monitoring method and device, vehicle machine system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Chen et al. | Android/OSGi-based vehicular network management system | |
| CN109684054A (en) | Information processing method and device, electronic equipment and memory | |
| CN108304234B (en) | Page display method and device | |
| CN112130963A (en) | Virtual machine task scheduling method and device, computer equipment and storage medium | |
| CN113190282A (en) | Android operating environment construction method and device | |
| US20220179711A1 (en) | Method For Platform-Based Scheduling Of Job Flow | |
| CN112714164A (en) | Internet of things system and task scheduling method thereof | |
| CN117093352B (en) | Template-based computing cluster job scheduling system, method and device | |
| CN117785231A (en) | Vehicle-mounted operating system and vehicle | |
| WO2023123493A1 (en) | Data management method and apparatus | |
| CN115098114A (en) | Block chain-based distributed application deployment method and device | |
| CN115964296A (en) | Evaluation method, device, equipment and medium for automatic driving safety verification platform | |
| CN111399928A (en) | Application program starting method and device, electronic equipment and readable storage medium | |
| CN110880099B (en) | Workflow engine-based task event processing method, device, equipment and medium | |
| US20060181405A1 (en) | Dynamically tasking one or more surveillance resources | |
| CN111552461A (en) | Association mapping method for service framework design and service component development | |
| US7408457B2 (en) | Dynamically tasking one or more surveillance resources | |
| CN116954812A (en) | Service request processing method, device, equipment and storage medium | |
| WO2023230760A1 (en) | Privacy protection method and apparatus, and vehicle | |
| CN113472840B (en) | Cloud service dynamic management method and device | |
| US20050278694A1 (en) | Describing Runtime Components of a Solution for a Computer System | |
| CN117272521A (en) | Vehicle scene arrangement method, device, equipment and medium | |
| CN110955474B (en) | Method, device and equipment for adding and calling service in application system | |
| CN116302049A (en) | Configuration method, device and equipment of applet plug-in | |
| Xiao et al. | Visual Optimization of Cluster Simulation Based on Multi Process Service and Load Balancing Agent |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |