CN112015489A - Management method, device, storage medium and system for vehicle-mounted software - Google Patents
Management method, device, storage medium and system for vehicle-mounted software Download PDFInfo
- Publication number
- CN112015489A CN112015489A CN202010986986.XA CN202010986986A CN112015489A CN 112015489 A CN112015489 A CN 112015489A CN 202010986986 A CN202010986986 A CN 202010986986A CN 112015489 A CN112015489 A CN 112015489A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- software
- hardware
- mounted software
- information
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a management method of vehicle-mounted software, which comprises the following steps: obtaining the vehicle type information of each vehicle, and determining a functional module corresponding to each vehicle according to the vehicle type information of each vehicle; correspondingly determining a control unit, vehicle hardware and vehicle-mounted software according to the functional modules corresponding to the vehicles; associating corresponding vehicle hardware according to different types of control units; according to the associated vehicle hardware, corresponding vehicle-mounted software and the upgrade limiting conditions of the vehicle-mounted software are associated, and corresponding software information is determined according to the associated vehicle-mounted software, wherein the software information comprises: a software package version number. The embodiment of the invention also discloses a management device, a storage medium and a system of the vehicle-mounted software, which effectively solve the problem that a uniform software package source cannot be provided when the vehicle-mounted software is upgraded by networking in the prior art, thereby ensuring that the vehicle-mounted software can be accurately upgraded.
Description
Technical Field
The invention relates to the technical field of automobiles, in particular to a management method, a management device, a storage medium and a management system of vehicle-mounted software.
Background
At present, each automobile often comprises a plurality of systems, each system has its corresponding control unit, and in the prior art, the following problems occur:
the automobile configuration functions become richer and richer, the number of control units is correspondingly greatly increased, the software functions become more complex, and the software is updated more frequently, which all put higher requirements on the management of the controller software. The automobile needs to perform networking upgrade on various vehicle-mounted software in the control unit, and different control units have different compatibility, so that a uniform software package source cannot be provided when the vehicle-mounted software is upgraded in a networking mode, and the vehicle-mounted software cannot be accurately upgraded.
Disclosure of Invention
The embodiment of the invention provides a management method, a management device, a storage medium and a management system of vehicle-mounted software, which can effectively solve the problem that a uniform software package source cannot be provided when the vehicle-mounted software is upgraded by networking in the prior art, so that the vehicle-mounted software can be accurately upgraded.
An embodiment of the present invention provides a method for managing vehicle-mounted software, including:
obtaining the vehicle type information of each vehicle, and determining a functional module corresponding to each vehicle according to the vehicle type information of each vehicle;
correspondingly determining a control unit, vehicle hardware and vehicle-mounted software according to the functional modules corresponding to the vehicles;
associating corresponding vehicle hardware according to different types of control units;
according to the associated vehicle hardware, corresponding vehicle-mounted software and the upgrade limiting conditions of the vehicle-mounted software are associated, and corresponding software information is determined according to the associated vehicle-mounted software, wherein the software information comprises: a software package version number.
As an improvement of the above solution, after associating the corresponding vehicle hardware according to the different kinds of control units, the method further includes:
and associating the at least two control units with the dependency relationship so as to synchronously store the software information of the vehicle-mounted software corresponding to the at least two control units with the dependency relationship.
As an improvement of the above solution, after associating the corresponding vehicle hardware according to the different kinds of control units, the method further includes:
determining corresponding hardware information according to the associated vehicle hardware, wherein the hardware information comprises: priority, gating conditions, and version information.
As an improvement of the above solution, after the associating the corresponding vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software according to the associated vehicle hardware, and determining the corresponding software information according to the associated vehicle-mounted software, the method further includes:
and after receiving the vehicle-mounted software upgrading request, verifying the associated software package of the vehicle-mounted software according to a preset software verification algorithm to generate a software verification value.
As an improvement of the above solution, after the associating the corresponding vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software according to the associated vehicle hardware, and determining the corresponding software information according to the associated vehicle-mounted software, the method further includes:
and respectively marking the associated vehicle hardware and the associated vehicle software.
As an improvement of the above solution, after the associating the corresponding vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software according to the associated vehicle hardware, and determining the corresponding software information according to the associated vehicle-mounted software, the method further includes:
and if the software versions of the associated vehicle-mounted software have dependency relationship, associating the depended software.
Another embodiment of the present invention correspondingly provides a management apparatus for vehicle-mounted software, including:
the acquisition module is used for acquiring the vehicle type information of each vehicle and determining a functional module corresponding to each vehicle according to the vehicle type information of each vehicle;
the first correlation module is used for correspondingly determining a control unit, vehicle hardware and vehicle-mounted software according to the functional modules corresponding to the vehicles;
the second correlation module is used for correlating corresponding vehicle hardware according to different types of control units;
the third association module is used for associating corresponding vehicle-mounted software and upgrade limiting conditions of the vehicle-mounted software according to the associated vehicle hardware, and determining corresponding software information according to the associated vehicle-mounted software, wherein the software information comprises: a software package version number.
Another embodiment of the present invention provides a management system for vehicle software, including an iBOM system and a vehicle software package service system for integrating vehicle type information, a control unit, vehicle hardware and vehicle software;
the on-board software package service system includes: the system comprises a processor, a memory and a computer program which is stored in the memory and configured to be executed by the processor, wherein the processor realizes the management method of the vehicle-mounted software of the embodiment of the invention when executing the computer program.
Another embodiment of the present invention provides an upgrade system for vehicle-mounted software, including a vehicle diagnosis upgrade module for sending a vehicle-mounted software upgrade request, and a vehicle-mounted software package service system for sending corresponding software information and upgrade limiting conditions to the vehicle diagnosis upgrade module according to the vehicle-mounted software upgrade request;
the on-board software package service system includes: the system comprises a processor, a memory and a computer program which is stored in the memory and configured to be executed by the processor, wherein the processor realizes the management method of the vehicle-mounted software of the embodiment of the invention when executing the computer program.
Another embodiment of the present invention provides a storage medium, where the computer-readable storage medium includes a stored computer program, where when the computer program runs, a device where the computer-readable storage medium is located is controlled to execute the method for managing vehicle-mounted software according to the above-described embodiment of the present invention.
Compared with the prior art, the management method, the management device, the management system and the storage medium of the vehicle-mounted software disclosed by the embodiment of the invention have the advantages that the vehicle type information of each vehicle is obtained, the corresponding function module is determined according to the vehicle type information of each vehicle, the corresponding control unit, the vehicle hardware and the vehicle-mounted software are determined according to the function module, the corresponding vehicle hardware is associated according to different types of control units, the corresponding vehicle-mounted software is associated according to the vehicle hardware, and meanwhile, the upgrade limiting condition of the vehicle-mounted software is obtained according to the vehicle hardware. Therefore, by establishing the relationship between the functional module and the control unit, the relationship between the control unit and the vehicle hardware, the relationship between the vehicle hardware and the vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software, when the vehicle-mounted software on the vehicle needs to be upgraded in a networking manner, the matching relationship between the same control unit and the software version of the vehicle-mounted software can be automatically identified only according to the vehicle type information, different software package sources are provided according to different control units, and meanwhile, the vehicle-mounted software is upgraded according to the upgrade limiting condition, so that the vehicle-mounted software is accurately upgraded.
Drawings
Fig. 1 is a schematic flowchart of a management method for vehicle-mounted software according to an embodiment of the present invention;
fig. 2 is a schematic specific flowchart of a management method for vehicle-mounted software according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a method for managing vehicle-mounted software according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a method for managing vehicle-mounted software according to an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of a management system for onboard software according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an upgrade system for vehicle-mounted software according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic flow chart of a management method for vehicle-mounted software according to an embodiment of the present invention.
The management method of the vehicle-mounted software provided by the embodiment can be executed by a vehicle-mounted software management system of a vehicle, specifically, the vehicle-mounted software package service system 1. The vehicle-mounted software management system can be realized in a software and/or hardware mode, and the vehicle-mounted software management system can be formed by two or more physical entities or can be formed by one physical entity.
Further, the vehicle-mounted software package service system 1 is connected with the iBOM system 2 of the vehicle, the vehicle diagnosis upgrade module, the wireless communication module, the display system of the vehicle, the driving system of the vehicle, and the like (the connection mode may be a wired connection mode or a wireless connection mode). The vehicle-mounted software management system acquires vehicle type information, a control unit, vehicle hardware and vehicle-mounted software through the iBOM system 2, and establishes a matching relationship between the control unit and the vehicle hardware and a matching relationship between the vehicle hardware and the vehicle-mounted software, so that the matching relationship between the same control unit and a software version of the vehicle-mounted software is identified. The vehicle-mounted software management system displays the content of the state information and the like of the vehicle-mounted software upgrading to a user by controlling a display system of the vehicle. The vehicle-mounted software package service system 1 further receives a vehicle-mounted software upgrading request of a vehicle diagnosis upgrading module, the vehicle-mounted software package service system 1 sends corresponding software information to the vehicle diagnosis upgrading module according to the vehicle-mounted software upgrading request, and the vehicle diagnosis upgrading module can be an OTA upgrading system 3 or other software upgrading systems, and is not limited specifically herein. The various information may be directly transmitted to the on-board software management system, or may be transmitted to another information processing device, processed by the corresponding information processing device, and then transmitted to the on-board software management system by the information processing device.
In the present embodiment, the in-vehicle Software Package service system 1 is integrated with an Electronic Control Unit (ECU), such as a vsp (video Software Package Management system) system. Since the on-board software management system can communicate with the external network, the wireless communication module is an Electronic Control Unit (ECU) of the vehicle, such as a T-Box, that integrates an external network communication function. The onboard software may be electronic control unit software (i.e., ECU software) of the vehicle, or may also be driver software, etc., and is not limited herein.
An embodiment of the present invention provides a method for managing vehicle-mounted software, including:
and S10, acquiring the vehicle type information of each vehicle, and determining the function module corresponding to each vehicle according to the vehicle type information of each vehicle.
And S20, correspondingly determining the control unit, the vehicle hardware and the vehicle-mounted software according to the function modules corresponding to the vehicles.
And S30, associating the corresponding vehicle hardware according to different types of control units.
S40, according to the related vehicle hardware, the corresponding vehicle-mounted software and the upgrade limiting conditions of the vehicle-mounted software are related, and according to the related vehicle-mounted software, the corresponding software information is determined, wherein the software information comprises: a software package version number.
The upgrade limiting condition may be a corresponding relationship between the vehicle hardware and the upgrade limiting condition stored in the system in advance, or may be set according to hardware information of the vehicle hardware, which is not limited herein.
In the present embodiment, a VSP system is taken as an example of a server of an in-vehicle software management system. The VSP system can send the software package, the software package version number and the check code to a downstream system according to the vehicle-mounted software upgrading request. The vehicle is composed of many functional modules, different models have different functional modules, and various functional modules of each model are stored in advance in the iBOM system 2. The VSP system extracts the vehicle type information from the iBOM system 2 and matches the vehicle type information with the function module. The different functional modules are controlled by different Control units, i.e. Electronic Control Units (ECU). The vehicle hardware may be a Battery Management System (BMS), Inertial Measurement Unit (IMU), sensory sensors, etc. Illustratively, the VSP system acquires vehicle type information of each vehicle, so that the VSP system stores the vehicle type information of each vehicle, thereby enabling upgrading of onboard software for any vehicle.
The different types of control units of the vehicle control different pieces of vehicle hardware correspondingly, that is, the different types of control units receive hardware information of the different pieces of vehicle hardware. For example, a control unit for controlling the inertial measurement unit receives information collected by the inertial measurement unit. The VSP system stores in advance the correspondence relationship between the control unit and the vehicle hardware. Therefore, the control unit is correspondingly associated with the vehicle hardware. Different vehicle hardware needs different vehicle software to control, software information of the vehicle software is perfected, and upgrading limiting conditions of the vehicle software are different according to different vehicle hardware. When the vehicle-mounted software of the vehicle is upgraded, the software version number can be directly obtained according to different control units, so that the software package is obtained for upgrading, and the problem that the software versions of different control units are incompatible is solved. The software information not only comprises a software package version number, a software check value and a network address (URL sequence), but also comprises whether the vehicle-mounted software version has a dependency relationship.
Illustratively, the information may be classified into a power system function module, a driving assistance system function module (ADAS), etc. according to the vehicle type. The control unit corresponding to the power system function module is a body area controller (BCDM). And simultaneously, acquiring corresponding vehicle hardware and vehicle-mounted software according to the power system function model.
In summary, vehicle type information of each vehicle is obtained, a corresponding function module is determined according to the vehicle type information of each vehicle, then a corresponding control unit, vehicle hardware and vehicle-mounted software are determined according to the function module, corresponding vehicle hardware is associated according to different types of control units, corresponding vehicle-mounted software is associated according to the vehicle hardware, and meanwhile, an upgrade limiting condition of the vehicle-mounted software is obtained according to the vehicle hardware. Therefore, by establishing the relationship between the functional module and the control unit, the relationship between the control unit and the vehicle hardware, the relationship between the vehicle hardware and the vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software, when the vehicle-mounted software on the vehicle needs to be upgraded in a networking manner, the matching relationship between the same control unit and the software version of the vehicle-mounted software can be automatically identified only according to the vehicle type information, different software package sources are provided according to different control units, and meanwhile, the vehicle-mounted software is upgraded according to the upgrade limiting condition, so that the vehicle-mounted software is accurately upgraded.
As an improvement of the above solution, after associating the corresponding vehicle hardware according to the different kinds of control units, the method further includes:
and S31, associating the at least two control units with the dependency relationship so as to synchronously store the software information of the vehicle-mounted software corresponding to the at least two control units with the dependency relationship.
It should be noted that at least two control units having dependency relationship need to be upgraded synchronously for the control units to work normally. It can be understood that if only one of the control units is upgraded, the problem of failed upgrade is easy to occur.
For example, if the first control unit has a second control unit with a dependency relationship, the first control unit and the second control unit are associated, and therefore, not only the vehicle-mounted software corresponding to the first control unit but also the vehicle-mounted software corresponding to the second control unit need to be acquired, so that the vehicle-mounted software can be successfully upgraded.
As an improvement of the above solution, after associating the corresponding vehicle hardware according to the different kinds of control units, the method further includes:
s32, determining corresponding hardware information according to the associated vehicle hardware, wherein the hardware information comprises: priority, gating conditions, version information, high and low voltages, and whether dependencies exist.
It should be noted that, after associating the control unit with the vehicle hardware, the VSP system acquires the hardware information of the vehicle hardware for matching. And vehicle hardware can be upgraded in sequence according to the priority level, namely vehicle-mounted software can be upgraded in sequence according to the priority level of the vehicle.
In this embodiment, the hardware information is a limiting condition for upgrading the vehicle-mounted software, and the vehicle-mounted software can be successfully upgraded only if all the hardware information of the vehicle hardware needs to be satisfied during upgrading.
As an improvement of the above solution, after the associating the corresponding vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software according to the associated vehicle hardware, and determining the corresponding software information according to the associated vehicle-mounted software, the method further includes:
and S43, after receiving the vehicle-mounted software upgrading request, verifying the associated software package of the vehicle-mounted software according to a preset software verification algorithm to generate a software verification value. The preset software check algorithm may be an SHA256 algorithm, a CRC check algorithm, or other algorithms that can obtain a software check code, which is not limited herein.
In the embodiment, the hash value calculated by the SHA256 algorithm, i.e. the check value SHA256 for ensuring the transmission integrity of the software package, is adopted, and the check code is stored in the check code field.
As an improvement of the above solution, after the associating the corresponding vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software according to the associated vehicle hardware, and determining the corresponding software information according to the associated vehicle-mounted software, the method further includes:
and S41, marking the related vehicle hardware and the related vehicle software respectively.
Specifically, the vehicle hardware and the vehicle software are marked in the VSP system, so that the vehicle hardware can be directly associated with the vehicle software after being associated with the vehicle hardware, the software information of the associated vehicle software and the corresponding software package are stored in the VSP system, when the vehicle software of the vehicle needs to be upgraded, only a vehicle software upgrading request needs to be sent, and the VSP system feeds back the corresponding software package, so that the vehicle software is upgraded.
As an improvement of the above solution, after the associating the corresponding vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software according to the associated vehicle hardware, and determining the corresponding software information according to the associated vehicle-mounted software, the method further includes:
and S42, if the software versions of the associated vehicle-mounted software have dependency relationship, associating the dependent software.
Specifically, in practical applications, a dependency relationship exists among a plurality of pieces of vehicle-mounted software, that is, the vehicle-mounted software with the dependency relationship needs to be updated successfully only by synchronous updating, and therefore, it is necessary to determine whether a dependency relationship exists in a software version of the associated vehicle-mounted software, and if so, the software with the dependency relationship is associated. When the VSP system receives the vehicle-mounted software upgrading request, it is necessary to send not only the software package of the associated vehicle-mounted software but also the software package of the dependent software to the vehicle-mounted upgrading system, thereby ensuring successful upgrading of the vehicle-mounted software.
For ease of understanding, the following is illustrative:
referring to fig. 3, first, vehicle model information, control unit type, vehicle hardware, and in-vehicle software are acquired from the iBOM system 2 to the VSP system, so that the seat builds basic data of an in-vehicle software structure tree in the VSP system.
First layer of the vehicle-mounted software structure tree: and classifying according to the acquired vehicle type information, namely classifying the unified vehicle types into one class.
Second layer of the vehicle-mounted software structure tree: each vehicle type is divided into a plurality of functional modules according to functions.
Third layer of the vehicle-mounted software structure tree: each functional module is associated with a corresponding control unit.
Fourth layer of the vehicle-mounted software structure tree: associating corresponding vehicle hardware according to the control unit; and improves the hardware information of the vehicle hardware. The hardware information includes: priority, gating conditions, version information, high and low voltages, and whether dependencies exist. And associating the control units with the dependencies.
Fifth layer of the vehicle software structure tree: the vehicle hardware is associated with the onboard software according to a development specification. And the software version number, the check code and the URL sequence are combined to construct a vehicle-mounted software structure tree. And uploading the software package with the version number and maintaining the software package to be stored in the VSP system.
And when the VSP system receives a vehicle-mounted software upgrading request sent by the vehicle diagnosis upgrading module, calculating a check code of the software package, and then sending the corresponding software package, the check code and the upgrading limiting condition to the vehicle diagnosis upgrading module, so that the vehicle upgrades the vehicle-mounted software according to the upgrading limiting condition.
Fig. 4 is a schematic structural diagram of a management device for vehicle-mounted software according to an embodiment of the present invention.
An embodiment of the present invention correspondingly provides a management apparatus for vehicle-mounted software, including:
the obtaining module 10 is configured to obtain vehicle type information of each vehicle, and determine a function module corresponding to each vehicle according to the vehicle type information of each vehicle.
And the first association module 20 is used for correspondingly determining the control unit, the vehicle hardware and the vehicle-mounted software according to the function modules corresponding to the vehicles.
And a second association module 30 for associating corresponding vehicle hardware according to different kinds of control units.
A third association module 40, configured to associate, according to the associated vehicle hardware, corresponding vehicle-mounted software and upgrade limiting conditions of the vehicle-mounted software, and determine corresponding software information according to the associated vehicle-mounted software, where the software information includes: a software package version number.
According to the management device for the vehicle-mounted software, provided by the embodiment of the invention, the vehicle type information of each vehicle is obtained, the corresponding function module is determined according to the vehicle type information of each vehicle, then the corresponding control unit, the vehicle hardware and the vehicle-mounted software are determined according to the function module, the corresponding vehicle hardware is associated according to different types of control units, the corresponding vehicle-mounted software is associated according to the vehicle hardware, and meanwhile, the upgrading limiting condition of the vehicle-mounted software is obtained according to the vehicle hardware. Therefore, by establishing the relationship between the functional module and the control unit, the relationship between the control unit and the vehicle hardware, the relationship between the vehicle hardware and the vehicle-mounted software and the upgrade limiting condition of the vehicle-mounted software, when the vehicle-mounted software on the vehicle needs to be upgraded in a networking manner, the matching relationship between the same control unit and the software version of the vehicle-mounted software can be automatically identified only according to the vehicle type information, different software package sources are provided according to different control units, and meanwhile, the vehicle-mounted software is upgraded according to the upgrade limiting condition, so that the vehicle-mounted software is accurately upgraded.
As an improvement of the above, the apparatus further comprises:
and the fourth association module is used for associating the at least two control units with the dependency relationship so as to synchronously store the software information of the vehicle-mounted software corresponding to the at least two control units with the dependency relationship.
As an improvement of the above, the apparatus further comprises:
a hardware information obtaining module, configured to determine corresponding hardware information according to the associated vehicle hardware, where the hardware information includes: priority level, gating condition, version information.
As an improvement of the above, the apparatus further comprises:
and the vehicle-mounted software checking module is used for checking the software package of the associated vehicle-mounted software according to a preset software checking algorithm after receiving the vehicle-mounted software upgrading request to generate a software checking value.
As an improvement of the above, the apparatus further comprises:
and the marking module is used for respectively marking the associated vehicle hardware and the associated vehicle-mounted software.
As an improvement of the above, the apparatus further comprises:
and the fourth association module is used for associating the software versions of the associated vehicle-mounted software with the depended software if the software versions of the associated vehicle-mounted software have dependency relationship.
Fig. 5 is a schematic diagram of a management system of onboard software according to an embodiment of the present invention.
An embodiment of the present invention provides a management system for vehicle-mounted software, including an iBOM system 2 and a vehicle-mounted software package service system 1 for integrating vehicle type information, a control unit, vehicle hardware, and vehicle-mounted software.
The in-vehicle software package service system 1 includes: the system comprises a processor, a memory and a computer program which is stored in the memory and configured to be executed by the processor, wherein the processor realizes the management method of the vehicle-mounted software of the embodiment of the invention when executing the computer program.
According to the management system of the vehicle-mounted software, provided by the embodiment of the invention, the vehicle-mounted software package service system 1 acquires vehicle type information, a function module, a control unit, vehicle hardware and the vehicle-mounted software through the iBOM system 2, the vehicle-mounted software package service system 1 associates the function module with the control unit through the vehicle information and then associates the control unit through the function module, then associates the corresponding vehicle hardware according to different types of control units, associates the corresponding vehicle-mounted software with the vehicle hardware and the limiting conditions of the software according to the vehicle hardware, and associates the control units with the dependency relationship, so that a management framework of the vehicle-mounted software is established.
Fig. 6 is a schematic diagram of an upgrade system for vehicle-mounted software according to an embodiment of the present invention.
The invention provides an upgrading system of vehicle-mounted software, which comprises a vehicle diagnosis upgrading module and a vehicle-mounted software package service system, wherein the vehicle diagnosis upgrading module is used for sending a vehicle-mounted software upgrading request, and the vehicle-mounted software package service system is used for sending corresponding software information and upgrading limiting conditions to the vehicle diagnosis upgrading module according to the vehicle-mounted software upgrading request;
the on-board software package service system includes: the system comprises a processor, a memory and a computer program which is stored in the memory and configured to be executed by the processor, wherein the processor realizes the management method of the vehicle-mounted software of the embodiment of the invention when executing the computer program.
It should be noted that the vehicle-mounted software upgrading request may be vehicle type information of the current vehicle, and may also be vehicle hardware of the current vehicle. The vehicle diagnosis upgrading module in the embodiment comprises: OTA upgrade system 3, diagnostic system 4 is OBD (On-Board Diagnostics). When the diagnosis system 4 diagnoses that the vehicle hardware needs to be upgraded, the specified vehicle hardware is sent to the vehicle-mounted software package service system 1, the vehicle-mounted software package service system 1 matches the corresponding vehicle-mounted software according to the specified vehicle hardware, and the software information and the upgrade limiting condition of the vehicle-mounted software are sent to the diagnosis system 4.
According to the vehicle-mounted software upgrading system provided by the embodiment of the invention, the vehicle-mounted software package service system 1 receives the vehicle-mounted software upgrading request sent by the OTA upgrading system 3, sends the corresponding software package and the check code to the OTA upgrading system 3, and then upgrades the vehicle-mounted software according to the upgrading limiting conditions, so that the vehicle-mounted software is accurately upgraded.
Illustratively, the computer program may be partitioned into one or more modules/units that are stored in the memory and executed by the processor to implement the invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used for describing the execution process of the computer program in the on-board software package service system 1.
The vehicle-mounted software package service system 1 can be a desktop computer, a notebook computer, a palm computer and other computing equipment. The on-board software package service system 1 may include, but is not limited to, a processor, a memory. It will be appreciated by those skilled in the art that the schematic diagram is merely an example of the in-vehicle software package service system 1, and does not constitute a limitation of the in-vehicle software package service system 1, and may include more or less components than those shown, or combine some components, or different components, for example, the in-vehicle software package service system 1 may further include input-output devices, network access devices, buses, etc.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, the processor is the control center of the in-vehicle software package service system 1, and various interfaces and lines are used to connect the various parts of the entire in-vehicle software package service system 1.
The memory may be used to store the computer programs and/or modules, and the processor may implement various functions of the in-vehicle software package service system 1 by operating or executing the computer programs and/or modules stored in the memory and calling data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
Wherein, the modules/units integrated by the vehicle-mounted software package service system 1 can be stored in a computer readable storage medium if they are implemented in the form of software functional units and sold or used as independent products. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like.
It should be noted that the above-described device embodiments are merely illustrative, where the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. In addition, in the drawings of the embodiment of the apparatus provided by the present invention, the connection relationship between the modules indicates that there is a communication connection between them, and may be specifically implemented as one or more communication buses or signal lines. One of ordinary skill in the art can understand and implement it without inventive effort.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
Claims (10)
1. A management method of vehicle-mounted software is characterized by comprising the following steps:
obtaining the vehicle type information of each vehicle, and determining a functional module corresponding to each vehicle according to the vehicle type information of each vehicle;
correspondingly determining a control unit, vehicle hardware and vehicle-mounted software according to the functional modules corresponding to the vehicles;
associating corresponding vehicle hardware according to different types of control units;
according to the associated vehicle hardware, corresponding vehicle-mounted software and the upgrade limiting conditions of the vehicle-mounted software are associated, and corresponding software information is determined according to the associated vehicle-mounted software, wherein the software information comprises: a software package version number.
2. The method for managing on-board software according to claim 1, further comprising, after associating corresponding vehicle hardware according to the heterogeneous control units:
and associating the at least two control units with the dependency relationship so as to synchronously store the software information of the vehicle-mounted software corresponding to the at least two control units with the dependency relationship.
3. The method for managing on-board software according to claim 1, further comprising, after associating corresponding vehicle hardware according to the heterogeneous control units:
determining corresponding hardware information according to the associated vehicle hardware, wherein the hardware information comprises: priority, gating conditions, and version information.
4. The method for managing on-board software according to claim 1, further comprising, after associating the corresponding on-board software according to the associated vehicle hardware and the upgrade limiting condition of the on-board software, and determining the corresponding software information according to the associated on-board software:
and after receiving the vehicle-mounted software upgrading request, verifying the associated software package of the vehicle-mounted software according to a preset software verification algorithm to generate a software verification value.
5. The method for managing on-board software according to claim 1, further comprising, after associating the corresponding on-board software according to the associated vehicle hardware and the upgrade limiting condition of the on-board software, and determining the corresponding software information according to the associated on-board software:
and respectively marking the associated vehicle hardware and the associated vehicle software.
6. The method for managing on-board software according to claim 1, further comprising, after associating the corresponding on-board software according to the associated vehicle hardware and the upgrade limiting condition of the on-board software, and determining the corresponding software information according to the associated on-board software:
and if the software versions of the associated vehicle-mounted software have dependency relationship, associating the depended software.
7. An in-vehicle software management device, comprising:
the acquisition module is used for acquiring the vehicle type information of each vehicle and determining a functional module corresponding to each vehicle according to the vehicle type information of each vehicle;
the first correlation module is used for correspondingly determining a control unit, vehicle hardware and vehicle-mounted software according to the functional modules corresponding to the vehicles;
the second correlation module is used for correlating corresponding vehicle hardware according to different types of control units;
the third association module is used for associating corresponding vehicle-mounted software and upgrade limiting conditions of the vehicle-mounted software according to the associated vehicle hardware, and determining corresponding software information according to the associated vehicle-mounted software, wherein the software information comprises: a software package version number.
8. A management system for in-vehicle software, comprising: the iBOM system and the vehicle-mounted software package service system are used for integrating vehicle type information, a control unit, vehicle hardware and vehicle-mounted software;
the on-board software package service system includes: a processor, a memory and a computer program stored in the memory and configured to be executed by the processor, the processor implementing a method of managing onboard software according to any one of claims 1 to 7 when executing the computer program.
9. An upgrade system for in-vehicle software, comprising: the system comprises a vehicle diagnosis upgrading module used for sending a vehicle-mounted software upgrading request and a vehicle-mounted software package service system used for sending corresponding software information and upgrading limiting conditions to the vehicle diagnosis upgrading module according to the vehicle-mounted software upgrading request;
the on-board software package service system includes: a processor, a memory and a computer program stored in the memory and configured to be executed by the processor, the processor implementing a method of managing onboard software according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, comprising a stored computer program, wherein when the computer program runs, the computer-readable storage medium controls a device to execute the method for managing vehicle-mounted software according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010986986.XA CN112015489A (en) | 2020-09-18 | 2020-09-18 | Management method, device, storage medium and system for vehicle-mounted software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010986986.XA CN112015489A (en) | 2020-09-18 | 2020-09-18 | Management method, device, storage medium and system for vehicle-mounted software |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112015489A true CN112015489A (en) | 2020-12-01 |
Family
ID=73522059
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010986986.XA Pending CN112015489A (en) | 2020-09-18 | 2020-09-18 | Management method, device, storage medium and system for vehicle-mounted software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112015489A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112913190A (en) * | 2021-02-04 | 2021-06-04 | 华为技术有限公司 | Upgrading method and device based on over-the-air technology OTA |
| CN113176903A (en) * | 2021-04-15 | 2021-07-27 | 常州易控汽车电子股份有限公司 | Software integration method and system for applying Simulink model to different automobile controller platforms |
| CN116402496A (en) * | 2023-06-08 | 2023-07-07 | 山东诚卓信息技术有限公司 | Visual maintenance and control method and system for IT (information technology) assets |
| CN116881118A (en) * | 2023-06-01 | 2023-10-13 | 广州汽车集团股份有限公司 | Conflict detection method, device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107835501A (en) * | 2017-10-31 | 2018-03-23 | 广州小鹏汽车科技有限公司 | A kind of automobile method for upgrading software, apparatus and system |
| CN110244959A (en) * | 2018-03-07 | 2019-09-17 | 丰田自动车株式会社 | Vehicle control system and software compatibility inspection method |
| CN110908695A (en) * | 2019-10-18 | 2020-03-24 | 中国第一汽车股份有限公司 | Vehicle remote upgrading method, device and system |
| CN110928567A (en) * | 2019-11-27 | 2020-03-27 | 安徽江淮汽车集团股份有限公司 | Vehicle system upgrading method, terminal device and computer-readable storage medium |
| CN111343064A (en) * | 2020-02-29 | 2020-06-26 | 东风汽车集团有限公司 | System and method for upgrading software of automobile control system |
| CN111385191A (en) * | 2018-12-28 | 2020-07-07 | 联合汽车电子有限公司 | Vehicle-mounted interconnected gateway, vehicle OTA upgrading system and method and computer storage medium |
| CN111478897A (en) * | 2020-04-03 | 2020-07-31 | 爱瑟福信息科技(上海)有限公司 | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) |
-
2020
- 2020-09-18 CN CN202010986986.XA patent/CN112015489A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107835501A (en) * | 2017-10-31 | 2018-03-23 | 广州小鹏汽车科技有限公司 | A kind of automobile method for upgrading software, apparatus and system |
| CN110244959A (en) * | 2018-03-07 | 2019-09-17 | 丰田自动车株式会社 | Vehicle control system and software compatibility inspection method |
| CN111385191A (en) * | 2018-12-28 | 2020-07-07 | 联合汽车电子有限公司 | Vehicle-mounted interconnected gateway, vehicle OTA upgrading system and method and computer storage medium |
| CN110908695A (en) * | 2019-10-18 | 2020-03-24 | 中国第一汽车股份有限公司 | Vehicle remote upgrading method, device and system |
| CN110928567A (en) * | 2019-11-27 | 2020-03-27 | 安徽江淮汽车集团股份有限公司 | Vehicle system upgrading method, terminal device and computer-readable storage medium |
| CN111343064A (en) * | 2020-02-29 | 2020-06-26 | 东风汽车集团有限公司 | System and method for upgrading software of automobile control system |
| CN111478897A (en) * | 2020-04-03 | 2020-07-31 | 爱瑟福信息科技(上海)有限公司 | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112913190A (en) * | 2021-02-04 | 2021-06-04 | 华为技术有限公司 | Upgrading method and device based on over-the-air technology OTA |
| CN113176903A (en) * | 2021-04-15 | 2021-07-27 | 常州易控汽车电子股份有限公司 | Software integration method and system for applying Simulink model to different automobile controller platforms |
| CN113176903B (en) * | 2021-04-15 | 2024-04-26 | 常州易控汽车电子股份有限公司 | Software integration method and system for Simulink model applied to different automobile controller platforms |
| CN116881118A (en) * | 2023-06-01 | 2023-10-13 | 广州汽车集团股份有限公司 | Conflict detection method, device, electronic equipment and storage medium |
| CN116881118B (en) * | 2023-06-01 | 2024-05-14 | 广州汽车集团股份有限公司 | Conflict detection method, device, electronic equipment and storage medium |
| CN116402496A (en) * | 2023-06-08 | 2023-07-07 | 山东诚卓信息技术有限公司 | Visual maintenance and control method and system for IT (information technology) assets |
| CN116402496B (en) * | 2023-06-08 | 2023-08-22 | 山东诚卓信息技术有限公司 | Visual maintenance and control method and system for IT (information technology) assets |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112015489A (en) | Management method, device, storage medium and system for vehicle-mounted software | |
| CN112286170B (en) | Vehicle ECU (electronic control Unit) flashing method, device and equipment and storage medium | |
| CN110673576B (en) | Automatic test method and device, vehicle and storage medium | |
| CN109814524B (en) | Vehicle diagnosis method, device and system | |
| CN110928567A (en) | Vehicle system upgrading method, terminal device and computer-readable storage medium | |
| CN107132788A (en) | A kind of vehicle electronic control unit writes with a brush dipped in Chinese ink method and apparatus automatically | |
| CN112817617A (en) | Software upgrading method, device and system | |
| CN112181449B (en) | Vehicle-mounted software upgrading method, device, system and storage medium | |
| US11935341B2 (en) | Data storage device and non-transitory tangible computer readable storage medium | |
| WO2022165711A1 (en) | Upgrading method and apparatus based on over-the-air (ota) technology | |
| CN111176695A (en) | Vehicle ECU configuration method, server and terminal | |
| EP3405923B1 (en) | Updating a controller unit in a vehicle | |
| CN111527389A (en) | Vehicle diagnosis method, vehicle diagnosis device and storage medium | |
| US20100211582A1 (en) | Open architecture vehicle information module for vehicle and trailer, and system and method thereof | |
| CN111291443B (en) | Automatic generation method, device and equipment for I/O module model of vehicle control unit software | |
| US20170220691A1 (en) | System and Method for Automatically Identifying a Vehicle Model | |
| CN113835729A (en) | Upgrading method and device, terminal equipment and computer readable storage medium | |
| US20230384750A1 (en) | Efficient controller data generation and extraction | |
| CN112306041A (en) | Vehicle configuration information writing method and device and electronic equipment | |
| CN116048587A (en) | Remote automatic upgrading method, device, server, equipment and medium for vehicle | |
| US20230229417A1 (en) | Technologies for over-the-air updates for telematics systems | |
| CN113934198A (en) | Vehicle diagnosis method, vehicle diagnosis device, electronic device, and storage medium | |
| CN115291907A (en) | Vehicle upgrading method, device and system | |
| CN113342430A (en) | Fault code processing method and device, terminal equipment and readable storage medium | |
| WO2022120593A1 (en) | Test method, test apparatus, and terminal device |
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 |