Adaptive node starting method for multi-vehicle platform and related device

Abstract

The invention discloses a self-adaptive node starting method, device and system for a multi-vehicle-type platform, electronic equipment and a storage medium, the node starting method is applied to an SSM system state management module, and the method comprises the steps that after a vehicle is powered on, connection with a CMDB configuration management database is established, and vehicle configuration is acquired; after being connected with a starting control module, the domain controller receives a bootable node list, and the starting control module is deployed on the domain controller; and according to the vehicle configuration and the startable node list, generating a starting node list and issuing the starting node list to the starting control module so as to start a function node corresponding to the vehicle in the domain controller. According to the invention, self-adaptive starting is realized. On one hand, the maintainability and the expandability of system starting configuration are improved, on the other hand, the type needing to be started is automatically recognized after the vehicle type suite is adaptively started, and it is guaranteed that the started function node meets the vehicle type requirement.

Description

Technical Field

[0001] The present application relates to the field of intelligent connected vehicle technology, and in particular to an adaptive node startup method, device, system, electronic device, and storage medium for a multi-vehicle platform. Background Art

[0002] With the development of intelligent connected vehicles, more and more car models have achieved intelligent networking. According to the business needs of different models, the hardware sensors equipped on the models are also different.

[0003] In the existing solution, startup items and startup lists are configured for each vehicle type, and then the startup lists are packaged on the vehicle type to start the relevant function nodes of the vehicle. Based on this solution, once the hardware needs to be modified or startup items need to be added, the version needs to be updated again, which greatly increases the maintenance investment and update cycle. Summary of the invention

[0004] The embodiments of the present application provide an adaptive node startup method, device, system, electronic device, and storage medium for a multi-vehicle platform to achieve adaptive startup and automatically identify the type that needs to be started.

[0005] The present application embodiment adopts the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides a node startup method, which is applied to an SSM system status management module, and the method includes:

[0007] After the vehicle is powered on, a connection is established with the CMDB configuration management database and the vehicle configuration is obtained. The CMDB is used to configure the attribute configuration of the vehicle when there are new vehicles and / or vehicles that need to be modified;

[0008] After connecting with the startup control module, receiving a list of startable nodes, the startup control module is deployed on the domain controller;

[0009] According to the vehicle configuration and the startable node list, a start node list is generated and sent to the start control module to start the functional nodes corresponding to the vehicle in the domain controller.

[0010] In some embodiments, the method further comprises:

[0011] Determining whether all function nodes in the current vehicle model kit of the vehicle have been started;

[0012] If yes, then notify the display end that the startup is complete;

[0013] If not, the notification display terminal fails to start.

[0014] In some embodiments, if the notification display terminal fails to start, the method further includes:

[0015] If the startup failure is caused by incorrect configuration, updating the attribute configuration of the CMDB;

[0016] If the CMDB is correct but the node fails to be started, the node startup method is modified.

[0017] In some embodiments, configuring the attributes of the vehicle includes:

[0018] Configure the type of vehicle and distinguish different types of vehicles;

[0019] Configuring a package version of a vehicle, wherein the package version is determined according to a vehicle version or a function;

[0020] The configuration kit corresponds to the sensor model, and the model corresponds to the startup method one by one.

[0021] In some embodiments, establishing a connection with a CMDB configuration management database and obtaining vehicle configuration includes:

[0022] Establishing a connection with the CMDB after initialization;

[0023] Obtain relevant configuration items of the vehicle from the CMDB and identify nodes that need to be started;

[0024] When the vehicle model kit is identified, it waits for a connection to the starter control module on the domain controller.

[0025] In some embodiments, the domain controller includes multiple nodes, and generates a startup node list according to the vehicle configuration and the startup node list and sends it to the startup control module to start the functional node corresponding to the vehicle in the domain controller, including:

[0026] The startup control module on each of the domain controllers waits for connection, and the startup control module is used to report a list of startable nodes on each of the domain controllers after the connection is successful;

[0027] According to the list of startable nodes on each domain controller and the vehicle configuration, the start list is returned to the start control module to start the corresponding function node in the start control module.

[0028] In a second aspect, an embodiment of the present application further provides a node startup device, which is applied to an SSM system status management module, and the device includes:

[0029] Establishment and acquisition module, used to establish connection with CMDB configuration management database and obtain vehicle configuration after the vehicle is powered on. The CMDB is used to configure the attribute configuration of the vehicle when there are new vehicles and / or vehicles that need to be modified;

[0030] A connection and receiving module, used to receive a list of startable nodes after connecting with a startup control module, wherein the startup control module is deployed on a domain controller;

[0031] A generating and issuing module is used to generate a startup node list according to the vehicle configuration and the startup node list and issue it to the startup control module to start the functional nodes corresponding to the vehicle in the domain controller.

[0032] In a third aspect, an embodiment of the present application further provides a node startup system, wherein the system includes:

[0033] CMDB configuration management database, used to label and manage kits and hardware sensors of different models;

[0034] The SSM system status management module is used to establish a connection with the CMDB configuration management database and obtain the vehicle configuration after the vehicle is powered on. The CMDB is used to configure the vehicle's attribute configuration when there are new vehicles and / or vehicles that need to be modified;

[0035] After connecting with the startup control module, receiving a list of startable nodes, the startup control module is deployed on the domain controller;

[0036] Generate a startup node list according to the vehicle configuration and the startup node list and send it to the startup control module to start the functional nodes corresponding to the vehicle in the domain controller;

[0037] The startup control module is used to be deployed on multiple domain controllers and start the node according to the SSM configuration list after connecting to the SSM.

[0038] In a fourth aspect, an embodiment of the present application further provides an electronic device, comprising: a processor; and a memory arranged to store computer executable instructions, wherein the executable instructions, when executed, cause the processor to perform the above method.

[0039] In a fifth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple application programs, the electronic device executes the above method.

[0040] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: after the vehicle is powered on, a connection is established with the CMDB configuration management database and the vehicle configuration is obtained. The CMDB is used to configure the vehicle's attribute configuration when there are new vehicles and / or vehicles that need to be modified. Then, after connecting to the startup control module, a list of startable nodes is received. The startup control module is deployed on the domain controller. Finally, based on the vehicle configuration and the list of startable nodes, a startup node list is generated and sent to the startup control module to start the functional node corresponding to the vehicle in the domain controller. Through the above method, the maintainability and scalability of the system startup configuration can be improved, while the adaptive startup of the vehicle model kit can be achieved, and it can be ensured that the started functional node meets the vehicle model requirements.

[0041] Through the above method, the vehicle model, vehicle model kit and the hardware sensors used can be dynamically and flexibly identified, and the corresponding functional nodes can be adaptively started according to these vehicle attributes. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0043] Figure 1 A schematic diagram of a system framework in an embodiment of the present application;

[0044] Figure 2 This is a flowchart of a node startup method in an embodiment of the present application;

[0045] Figure 3 This is a schematic diagram of the structure of the node startup device in the embodiment of the present application;

[0046] Figure 4 This is a schematic diagram of the structure of the node startup system in the embodiment of the present application;

[0047] Figure 5 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0049] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0050] The present application embodiment provides a node startup method, such as Figure 2 As shown, a schematic diagram of a node startup method in an embodiment of the present application is provided, which is applied to an SSM system status management module. The method at least includes the following steps S210 to S230:

[0051] SSM (system status management) system status management.

[0052] CMDB (Configuration Management Database) configuration management database.

[0053] Step S210, after the vehicle is powered on, establish a connection with the CMDB configuration management database and obtain the vehicle configuration. The CMDB is used to configure the attribute configuration of the vehicle when there are newly added vehicles and / or vehicles that need to be modified.

[0054] The SSM system status management module establishes a connection with the CMDB configuration management database via an https request.

[0055] Usually, after the intelligent networked car is powered on, the nodes will be started in sequence, so as to start the relevant function nodes of the vehicle. The CMDB can configure the attribute configuration of the vehicle when there is a new vehicle or an existing vehicle needs to be modified.

[0056] It is understandable that each kit has its own configuration for each vehicle model. For example, TAXI taxis and BUS minibuses are different models. For another example, a BUS that relies on lidar sensors and a BUS that relies on visual camera sensors are different kits. Therefore, the kits are defined when the vehicle model is customized. Different models and different kits must have different functions to be activated. Usually, traditional configurations are maintained by configuring the startup items separately. By maintaining the CMDB configuration management database as the basis, maintenance failures can be effectively reduced and the scalability and flexibility of vehicle kit changes can be improved.

[0057] It can be understood that for each of the above sensors, a fixed launch is defined: each sensor starts at a different node, is processed differently, and has a different launch definition. Different suites may have multiple sensors. By maintaining the CMDB configuration management database, there is no need to perform similar repeated configurations.

[0058] In addition, the startup configuration management needs to be packaged together with the vehicle configuration. In order to start the function normally, the software installation package needs to be packaged separately for different vehicle models, which needs to include the startup configuration management strategy. Each vehicle model can only be packaged and configured separately. After the vehicle is powered on, a connection is established with the CMDB configuration management database and the vehicle configuration is obtained. It can automatically adapt and find the startup method of the relevant nodes according to the different configuration attributes. In this way, after configuring multiple vehicle kits once, there is no need to update them repeatedly, which simplifies the process of introducing new models, new kits, and new sensors, and reduces the complexity of configuration compatibility.

[0059] Step S220, after connecting with the startup control module, receiving a list of startable nodes, wherein the startup control module is deployed on the domain controller.

[0060] The SSM system status management module and the distributed domain controller (startup control module) also establish a connection through an https request.

[0061] like Figure 1 As shown in the figure, the overall framework consists of three layers. The upper layer is the CMDB configuration layer, which is a system for marking and managing kits and hardware sensors. The middle layer is the SSM management layer, which is used to identify whether the node can be started and distribute the node startup list. The lower layer is the startup control layer, which is deployed on multiple domain controllers. Multiple domain controllers are combined with the control layer as an AD system, and AD is the autodrive automatic driving system. After the startup control layer connects to the SSM, it will start the node according to the SSM configuration list.

[0062] The SSM system status management module mainly receives the node configuration and node status reported by the startup control module, issues a startup node list, and manages the start and stop of the node.

[0063] Step S230: Generate a startup node list according to the vehicle configuration and the startup node list and send it to the startup control module to start the functional nodes corresponding to the vehicle in the domain controller.

[0064] The SSM system status management module generates a startup node list based on the vehicle configuration and the startup node list and sends it to the startup control module, so that the functional nodes corresponding to the vehicle can be started in the domain controller.

[0065] It can be understood that the functional nodes are related to the vehicle model and the hardware sensor, and different functional nodes realize different functions of different vehicle models.

[0066] The above node startup method is used in the domain controller to start the corresponding software function after the system of the intelligent networked car is started. By dynamically and flexibly identifying the vehicle model, vehicle model kit, and the hardware sensors used, the corresponding function node can be adaptively started according to these vehicle attributes.

[0067] Different from the high maintenance and iteration costs in related technologies, each vehicle model or kit needs to be managed separately, and the workload of adapting new vehicle models is large. The special update nodes of existing vehicles require system personnel to modify the startup items. Through the above method, a complete node startup configuration inspection process is established, which can automatically adapt and find the startup method of related nodes according to different configuration attributes. After configuring multiple vehicle kits once, there is no need to update them repeatedly, which simplifies the process of introducing new models, new kits, and new sensors, and reduces the complexity of configuration compatibility.

[0068] Different from the inflexible configuration in related technologies: heavily dependent on previous agreements, if the solution is replaced, it has to be reconfigured, repackaged and deployed. The above method is based on the CMDB configuration management database and the SSM system status management module as the execution body, which avoids the problem of multiple modifications and packaging of traditional technologies, and the configuration can only be fixed and difficult to change. It can also effectively reduce maintenance success and improve the scalability and flexibility of vehicle kit changes. For special sensor changes, the adaptive startup of the associated node can be achieved by updating the relevant attributes of CDMB, without the need for version packaging again.

[0069] Different from the situation in related technologies that are not easy to expand: new models or kit upgrades are prone to incompatibility between old and new versions, and poor scalability. The above method has better scalability and supports multiple distributed domain controllers. For some nodes that do not rely on hardware wiring (especially non-hardware wiring related nodes), the node can be easily migrated from one domain controller to another to achieve the effect of starting backup. This feature also provides node self-adaptation capabilities at the application level.

[0070] In one embodiment of the present application, the method further includes: determining whether all functional nodes in the current vehicle model kit of the vehicle have been started; if so, notifying the display terminal that the startup is complete; if not, notifying the display terminal that the startup has failed.

[0071] During specific implementation, the SSM system status management module determines that all functional nodes of the vehicle model kit have been started and notifies the display system.

[0072] Usually, if SSM determines that all functional nodes of the vehicle have been started within a defined time, it will notify the display end that the system has been started. However, if it exceeds the defined time and SSM finds that there are still domain controllers or nodes that have not been started, it will notify the display end that the startup has failed.

[0073] It can be understood that the specific form of the display end as the output end of the node startup display is not limited, as long as it can meet the display requirements.

[0074] In one embodiment of the present application, if the notification display terminal fails to start, the method further includes: if the startup failure is due to incorrect configuration, updating the attribute configuration of the CMDB; if the CMDB is correct but the startup node fails, modifying the startup mode of the node.

[0075] For the display end startup failure or success, different steps are required:

[0076] Step a: For SSM startup failure, if the problem is due to incorrect configuration, update the CMDB configuration, otherwise continue to step b.

[0077] Step b: For the problem that the CMDB is correct but the SSM fails to start the node, the node is pushed to modify the startup mode. The startup mode of the node can be modified according to the actual situation, and is not specifically limited in the embodiments of the present application.

[0078] In one embodiment of the present application, the configuration of the vehicle attributes includes configuring the type of vehicle to distinguish different types of vehicles; configuring the vehicle kit version, the kit version is determined according to the vehicle version or function; configuring the sensor model corresponding to the kit, and the model corresponds to the startup method one by one.

[0079] The kit version is determined according to the vehicle version or function, including the specifications, number, position, arrangement, shape of connectors with the vehicle body, etc. of the lidar and / or camera.

[0080] It can be understood that intelligent connected vehicles have realized intelligent networking, that is, the hardware sensors equipped on the models are based on the business needs of different models. Through flexible identification of models, model kits, and hardware sensors used, the corresponding functional nodes can be adaptively started according to these vehicle attributes.

[0081] Specifically, when a new smart connected car is added or the configuration of a smart connected car is modified, the attribute configuration of the vehicle needs to be configured in CMDB first. The attribute configuration includes but is not limited to:

[0082] Configure the type of smart connected vehicles, such as distinguishing between TAXI taxis and BUS minibuses.

[0083] The kit version for smart connected cars is equipped with several lidar laser radars or cameras.

[0084] The sensor model corresponding to the kit of the intelligent connected car is configured, and one type of model corresponds to one starting method.

[0085] In one embodiment of the present application, establishing a connection with a CMDB configuration management database and obtaining the vehicle configuration includes: establishing a connection with the CMDB after initialization; obtaining relevant configuration items of the vehicle from the CMDB and identifying the nodes that need to be started; and when the vehicle model kit is identified, waiting for a connection with a startup control module on a domain controller.

[0086] After the intelligent connected car is powered on, the SSM system status management establishes a connection with the CMDB configuration management database to obtain the vehicle model, kit, and hardware sensor information of the vehicle. The vehicle model, kit, and hardware sensor information are as described above and will not be repeated here.

[0087] First, the initialization process of SSM system status management establishes a connection with the CMDB configuration management database;

[0088] Secondly, obtain hardware-related configuration items from the CMDB configuration management database and identify the nodes that need to be started;

[0089] Finally, after the vehicle model kit is identified, initialization is completed, and the SSM system status management waits for connection with the startup control program (startup control module) on the domain controller.

[0090] It should be noted that a startup control program (startup control module) is generally considered to be a software program running on a domain controller.

[0091] In one embodiment of the present application, the domain controller includes multiple ones, and according to the vehicle configuration and the list of bootable nodes, a startup node list is generated and sent to the startup control module to start the functional node corresponding to the vehicle in the domain controller, including: the startup control module on each of the domain controllers waits for connection, and the startup control module is used to report the list of bootable nodes on each of the domain controllers after the connection is successful; according to the list of bootable nodes on each of the domain controllers and the vehicle configuration, the startup list is returned to the startup control module to start the corresponding functional node in the startup control module.

[0092] The startup control program (startup control module) on each distributed domain controller connects to the SSM and starts the node:

[0093] First, after the smart connected car is powered on, the startup control program on each domain controller waits for the SSM connection.

[0094] Then, when the SSM connection is successful, the list of startable nodes on the domain controller of the SSM is reported.

[0095] Furthermore, SSM receives the startup list from the domain controller, combines it with the vehicle model kit configuration, and returns the startup list to the startup control program.

[0096] Finally, the startup control program starts the relevant functional nodes.

[0097] The present application embodiment also provides a node startup device 300, such as Figure 3 As shown, a schematic diagram of the structure of a node startup device in an embodiment of the present application is provided, wherein the node startup device 300 at least includes: an establishment and acquisition module 310, a connection and receiving module 320, and a generation and delivery module 330, wherein:

[0098] In one embodiment of the present application, the establishment and acquisition module 310 is specifically used to: after the vehicle is powered on, establish a connection with the CMDB configuration management database and obtain the vehicle configuration. The CMDB is used to configure the vehicle's attribute configuration when there are new vehicles and / or vehicles that need to be modified.

[0099] The SSM system status management module establishes a connection with the CMDB configuration management database via an https request.

[0100] Usually, after the intelligent networked car is powered on, the nodes will be started in sequence, so as to start the relevant function nodes of the vehicle. The CMDB can configure the attribute configuration of the vehicle when there is a new vehicle or an existing vehicle needs to be modified.

[0101] It is understandable that each kit has its own configuration for each vehicle model. For example, TAXI taxis and BUS minibuses are different models. For another example, a BUS that relies on lidar sensors and a BUS that relies on visual camera sensors are different kits. Therefore, the kits are defined when the vehicle model is customized. Different models and different kits must have different functions to be activated. Usually, traditional configurations are maintained by configuring the startup items separately. By maintaining the CMDB configuration management database as the basis, maintenance failures can be effectively reduced and the scalability and flexibility of vehicle kit changes can be improved.

[0102] It can be understood that for each of the above sensors, a fixed launch is defined: each sensor starts at a different node, is processed differently, and has a different launch definition. Different suites may have multiple sensors. By maintaining the CMDB configuration management database, there is no need to perform similar repeated configurations.

[0103] In addition, the startup configuration management needs to be packaged together with the vehicle configuration. In order to start the function normally, the software installation package needs to be packaged separately for different vehicle models, which needs to include the startup configuration management strategy. Each vehicle model can only be packaged and configured separately. After the vehicle is powered on, a connection is established with the CMDB configuration management database and the vehicle configuration is obtained. It can automatically adapt and find the startup method of the relevant nodes according to the different configuration attributes. In this way, after configuring multiple vehicle kits once, there is no need to update them repeatedly, which simplifies the process of introducing new models, new kits, and new sensors, and reduces the complexity of configuration compatibility.

[0104] In one embodiment of the present application, the connection and receiving module 320 is specifically used to: receive a list of bootable nodes after connecting with a startup control module, and the startup control module is deployed on a domain controller.

[0105] The SSM system status management module and the distributed domain controller (startup control module) also establish a connection through an https request.

[0106] like Figure 1 As shown in the figure, the overall framework consists of three layers. The upper layer is the CMDB configuration layer, which is a system for marking and managing kits and hardware sensors. The middle layer is the SSM management layer, which is used to identify whether the node can be started and distribute the node startup list. The lower layer is the startup control layer, which is deployed on multiple domain controllers. Multiple domain controllers are combined with the control layer as an AD system, and AD is the autodrive automatic driving system. After the startup control layer connects to the SSM, it will start the node according to the SSM configuration list.

[0107] The SSM system status management module mainly receives the node configuration and node status reported by the startup control module, issues a startup node list, and manages the start and stop of the node.

[0108] In one embodiment of the present application, the generation and distribution module 330 is specifically used to: generate a startup node list according to the vehicle configuration and the startup node list and distribute it to the startup control module to start the functional node corresponding to the vehicle in the domain controller.

[0109] The SSM system status management module generates a startup node list based on the vehicle configuration and the startup node list and sends it to the startup control module, so that the functional nodes corresponding to the vehicle can be started in the domain controller.

[0110] It can be understood that the functional nodes are related to the vehicle model and the hardware sensor, and different functional nodes realize different functions of different vehicle models.

[0111] It can be understood that the above-mentioned node startup device can implement each step of the node startup method provided in the above-mentioned embodiment, and the relevant explanations about the node startup method are applicable to the node startup device and will not be repeated here.

[0112] In one embodiment of the present application, it further includes: a discrimination module for

[0113] Determining whether all function nodes in the current vehicle model kit of the vehicle have been started;

[0114] If yes, then notify the display end that the startup is complete;

[0115] If not, the notification display terminal fails to start.

[0116] In one embodiment of the present application, the discrimination module is also used to

[0117] If the startup failure is caused by incorrect configuration, updating the attribute configuration of the CMDB;

[0118] If the CMDB is correct but the node fails to be started, the node startup method is modified.

[0119] In one embodiment of the present application, the establishing and obtaining module 310 is also used to

[0120] Configure the type of vehicle and distinguish different types of vehicles;

[0121] Configuring a package version of a vehicle, wherein the package version is determined according to a vehicle version or a function;

[0122] The configuration kit corresponds to the sensor model, and the model corresponds to the startup method one by one.

[0123] In one embodiment of the present application, the establishing and obtaining module 310 is also used to

[0124] Establishing a connection with the CMDB after initialization;

[0125] Obtain relevant configuration items of the vehicle from the CMDB and identify nodes that need to be started;

[0126] When the vehicle model kit is identified, it waits for a connection to the starter control module on the domain controller.

[0127] In one embodiment of the present application, the domain controller includes multiple, the generating and issuing module 330 is also used for

[0128] The startup control module on each of the domain controllers waits for connection, and the startup control module is used to report a list of startable nodes on each of the domain controllers after the connection is successful;

[0129] According to the list of startable nodes on each domain controller and the vehicle configuration, the start list is returned to the start control module to start the corresponding function node in the start control module.

[0130] like Figure 4 As shown, an embodiment of the present application provides a node startup system, wherein the system includes:

[0131] CMDB configuration management database 410 is used to mark and manage kits and hardware sensors of different vehicle models;

[0132] The SSM system status management module 420 is used to establish a connection with the CMDB configuration management database and obtain the vehicle configuration after the vehicle is powered on. The CMDB is used to configure the attribute configuration of the vehicle when there are new vehicles and / or vehicles that need to be modified;

[0133] After connecting with the startup control module, receiving a list of startable nodes, the startup control module is deployed on the domain controller;

[0134] Generate a startup node list according to the vehicle configuration and the startup node list and send it to the startup control module to start the functional nodes corresponding to the vehicle in the domain controller;

[0135] The startup control module 430 is used to be deployed on multiple domain controllers, and after connecting to the SSM, starts the node according to the SSM configuration list.

[0136] The above node startup system can effectively reduce maintenance failures and improve the scalability and flexibility of vehicle kit changes. For special sensor changes, the adaptive startup of the associated node can be achieved by updating the relevant attributes of CDMB, without the need for version packaging again.

[0137] The above-mentioned node startup system has established a complete node startup configuration inspection process, which can automatically adapt and find the startup method of related nodes according to different configuration attributes. After configuring multiple vehicle kits once, there is no need to update them repeatedly, which simplifies the process of introducing new models, new kits, and new sensors, and reduces the complexity of configuration compatibility.

[0138] The SSM system proposed in the above-mentioned node startup system has better scalability and supports multiple distributed domain controllers. For some nodes that do not rely on hardware wiring (non-hardware wiring related nodes), it is easy to migrate the node from one domain controller to another domain controller to achieve the effect of startup backup, thereby also providing node adaptation capabilities at the application level.

[0139] Figure 5This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 5 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0140] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0141] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0142] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a node startup device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0143] After the vehicle is powered on, a connection is established with the CMDB configuration management database and the vehicle configuration is obtained. The CMDB is used to configure the attribute configuration of the vehicle when there are new vehicles and / or vehicles that need to be modified;

[0144] After connecting with the startup control module, receiving a list of startable nodes, the startup control module is deployed on the domain controller;

[0145] According to the vehicle configuration and the startable node list, a start node list is generated and sent to the start control module to start the functional nodes corresponding to the vehicle in the domain controller.

[0146] The above application Figure 2The method performed by the node startup device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0147] The electronic device may also perform Figure 2 The method for executing the node startup device in the Figure 2 The functions of the illustrated embodiment will not be described in detail in the embodiments of the present application.

[0148] The present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figure 2 The method executed by the node startup device in the illustrated embodiment is specifically used to execute:

[0149] After the vehicle is powered on, a connection is established with the CMDB configuration management database and the vehicle configuration is obtained. The CMDB is used to configure the attribute configuration of the vehicle when there are new vehicles and / or vehicles that need to be modified;

[0150] After connecting with the startup control module, receiving a list of startable nodes, the startup control module is deployed on the domain controller;

[0151] According to the vehicle configuration and the startable node list, a start node list is generated and sent to the start control module to start the functional nodes corresponding to the vehicle in the domain controller.

[0152] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0153] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0154] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0155] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0157] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0158] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0159] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0160] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0161] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. An adaptive node startup method for a multi-vehicle platform, wherein: Applied to the SSM system status management module, the method includes: After the vehicle is powered on, a connection is established with the CMDB configuration management database and the vehicle configuration is obtained. The CMDB is used to configure the attribute configuration of the vehicle when there are new vehicles and / or vehicles that need to be modified; After connecting with the startup control module, receiving a list of startable nodes, the startup control module is deployed on the domain controller; According to the vehicle configuration and the startable node list, a start node list is generated and sent to the start control module to start the functional nodes corresponding to the vehicle in the domain controller.

2. The method of claim 1, wherein: The method further comprises: Determining whether all function nodes in the current vehicle model kit of the vehicle have been started; If yes, then notify the display end that the startup is complete; If not, the notification display terminal fails to start.

3. The method of claim 2, wherein: If the notification display terminal fails to start, the method further includes: If the startup failure is caused by incorrect configuration, updating the attribute configuration of the CMDB; If the CMDB is correct but the node fails to be started, the node startup method is modified.

4. The method of claim 1, wherein: The configuration of the vehicle attributes includes: Configure the type of vehicle and distinguish different types of vehicles; Configuring a package version of a vehicle, wherein the package version is determined according to a vehicle version or a function; The configuration kit corresponds to the sensor model, and the model corresponds to the startup method one by one.

5. The method of claim 1, wherein: The step of establishing a connection with the CMDB configuration management database and obtaining the vehicle configuration includes: Establishing a connection with the CMDB after initialization; Obtain relevant configuration items of the vehicle from the CMDB and identify nodes that need to be started; When the vehicle model kit is identified, it waits for a connection to the starter control module on the domain controller.

6. The method of claim 1, wherein: The domain controller includes a plurality of nodes, and generates a startup node list according to the vehicle configuration and the startup node list and sends it to the startup control module to start the functional nodes corresponding to the vehicle in the domain controller, including: The startup control module on each of the domain controllers waits for connection, and the startup control module is used to report a list of startable nodes on each of the domain controllers after the connection is successful; According to the list of startable nodes on each domain controller and the vehicle configuration, the start list is returned to the start control module to start the corresponding function node in the start control module.

7. A node startup device, wherein: Applied to the SSM system status management module, the device comprises: Establishment and acquisition module, used to establish connection with CMDB configuration management database and obtain vehicle configuration after the vehicle is powered on. The CMDB is used to configure the attribute configuration of the vehicle when there are new vehicles and / or vehicles that need to be modified; A connection and receiving module, used to receive a list of startable nodes after connecting with a startup control module, wherein the startup control module is deployed on a domain controller; A generating and issuing module is used to generate a startup node list according to the vehicle configuration and the startup node list and issue it to the startup control module to start the functional nodes corresponding to the vehicle in the domain controller.

8. A node startup system, wherein: The system comprises: CMDB configuration management database, used to label and manage kits and hardware sensors of different models; The SSM system status management module is used to establish a connection with the CMDB configuration management database and obtain the vehicle configuration after the vehicle is powered on. The CMDB is used to configure the vehicle's attribute configuration when there are new vehicles and / or vehicles that need to be modified; After connecting with the startup control module, receiving a list of startable nodes, the startup control module is deployed on the domain controller; Generate a startup node list according to the vehicle configuration and the startup node list and send it to the startup control module to start the functional nodes corresponding to the vehicle in the domain controller; The startup control module is used to be deployed on multiple domain controllers and start the node according to the SSM configuration list after connecting to the SSM.

9. An electronic device, comprising: processor; as well as A memory arranged to store computer executable instructions, which when executed cause the processor to perform the method of any one of claims 1 to 6.

10. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, causes the electronic device to execute any one of the methods of claims 1 to 6.

Images