CN116804932A - Vehicle software identification recognition method and device, electronic equipment and storage medium - Google Patents
Vehicle software identification recognition method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116804932A CN116804932A CN202310799993.2A CN202310799993A CN116804932A CN 116804932 A CN116804932 A CN 116804932A CN 202310799993 A CN202310799993 A CN 202310799993A CN 116804932 A CN116804932 A CN 116804932A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- software identification
- identification code
- software
- version 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
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000012545 processing Methods 0.000 claims abstract description 18
- 238000013507 mapping Methods 0.000 claims description 100
- 238000004590 computer program Methods 0.000 claims description 16
- 230000005856 abnormality Effects 0.000 claims description 15
- 238000004458 analytical method Methods 0.000 claims description 7
- 230000008859 change Effects 0.000 claims description 5
- 230000010365 information processing Effects 0.000 claims description 4
- 230000000694 effects Effects 0.000 abstract description 7
- 238000004891 communication Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 238000010438 heat treatment Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000012546 transfer Methods 0.000 description 4
- 230000033228 biological regulation Effects 0.000 description 3
- 238000007689 inspection Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 230000006641 stabilisation Effects 0.000 description 1
- 238000011105 stabilization Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/22—Matching criteria, e.g. proximity measures
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Life Sciences & Earth Sciences (AREA)
- Computer Security & Cryptography (AREA)
- Artificial Intelligence (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Bioinformatics & Computational Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Evolutionary Biology (AREA)
- Evolutionary Computation (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a vehicle software identification recognition method, a device, electronic equipment and a storage medium. The method is applied to the cloud, and comprises the following steps: receiving configuration version information corresponding to each vehicle-mounted controller reported by a vehicle end, and determining at least one second software identification code corresponding to the configuration version information; and receiving at least one first software identification code reported by the vehicle end, matching at least one second software identification code with at least one first software identification code, generating a matching result, and processing the vehicle to be identified to which the vehicle end belongs based on the matching result. According to the technical scheme, the effect of double redundancy identification of the vehicle software identification code by the cloud end of the vehicle is achieved, the identification efficiency and the identification accuracy of the vehicle software identification code are improved, and the software safety of the vehicle is also improved.
Description
Technical Field
The present invention relates to the field of vehicle technologies, and in particular, to a method and apparatus for identifying a vehicle software identifier, an electronic device, and a storage medium.
Background
With the development of automatic driving, the demands of calculation and control capability of automobiles are increasing. More and more functionality is provided to users in the form of software, and therefore software-defined automobiles are becoming an important trend in automobile development. When software in the automobile needs to be installed or updated, the software in the automobile can be installed or updated by means of OTA networking by using an over-the-air technology (over the air technology, OTA). To meet the certification of the software update management system, the vehicle needs to set a Regulation software identifier (RXSWIN) for identifying the influence of software changes on the Regulation related content before and after upgrading.
In the related art, the RXSWIN is usually identified by acquiring configuration version information corresponding to the vehicle-mounted controller during vehicle inspection and sampling, and then, a vehicle inspection worker can manually identify the acquired configuration version information according to a mapping relation table maintained by the vehicle inspection background. Such a recognition method may have problems such as low recognition efficiency and recognition accuracy, and in the case where the configuration version information of the in-vehicle controller is changed, the in-vehicle controller that has changed cannot be located in time.
Disclosure of Invention
The invention provides a vehicle software identification recognition method, a device, electronic equipment and a storage medium, which are used for realizing the effect of double redundancy recognition of a vehicle end cloud to a vehicle software identification code, improving the recognition efficiency and recognition accuracy of the vehicle software identification code, and improving the software security of a vehicle.
According to a first aspect of the present invention, there is provided a vehicle software identification recognition method, which is applied to a cloud, and includes:
receiving configuration version information corresponding to each vehicle-mounted controller reported by a vehicle end, and determining at least one first software identification code corresponding to the configuration version information;
and receiving at least one second software identification code reported by the vehicle end, matching the at least one first software identification code with the at least one first software identification code, generating a matching result, and processing the vehicle to be identified to which the vehicle end belongs based on the matching result.
According to a second aspect of the present invention, there is provided a vehicle software identification recognition method, which is applied to a vehicle end, comprising:
when the change of the software version number of the vehicle-mounted controller is detected, configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified is obtained, and each configuration version information is reported to a cloud;
Determining at least one second software identification code corresponding to the vehicle to be identified based on a pre-stored first software identification mapping table and configuration version information corresponding to each vehicle-mounted controller;
and reporting the at least one second software identification code to the cloud end so that the cloud end can match the received at least one second software identification code with at least one first software identification code generated by the cloud end, and processing the vehicle to be identified based on a matching result.
According to a third aspect of the present invention, there is provided a vehicle software identification recognition device, the device being configured at a cloud end, comprising:
the system comprises a configuration version information receiving module, a configuration version information processing module and a configuration version information processing module, wherein the configuration version information receiving module is used for receiving configuration version information corresponding to each vehicle-mounted controller reported by a vehicle end and determining at least one first software identification code corresponding to the configuration version information;
the software identification matching module is used for receiving at least one second software identification code reported by the vehicle end, matching the at least one first software identification code with the at least one first software identification code, generating a matching result, and processing a vehicle to be identified to which the vehicle end belongs based on the matching result.
According to a fourth aspect of the present invention, there is provided a vehicle software identification recognition apparatus, which is configured at a vehicle end, comprising:
the configuration version information acquisition module is used for acquiring configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified when detecting that the software version number of the vehicle-mounted controller changes, and reporting each configuration version information to the cloud;
the first software identification determining module is used for determining at least one second software identification code corresponding to the vehicle to be identified based on a pre-stored first software identification mapping table and configuration version information corresponding to each vehicle-mounted controller;
the software identification reporting module is used for reporting the at least one second software identification code to the cloud end so that the cloud end can match the received at least one second software identification code with at least one first software identification code generated by the cloud end, and the vehicle to be identified is processed based on a matching result.
According to a fifth aspect of the present invention, there is provided an electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
The memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the vehicle software identification method according to any one of the embodiments of the present invention.
According to a sixth aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to execute a vehicle software identification recognition method according to any one of the embodiments of the present invention.
According to the technical scheme, the configuration version information corresponding to each vehicle-mounted controller reported by the vehicle end is received, at least one first software identification code corresponding to the configuration version information is determined, further, at least one second software identification code reported by the vehicle end is received, at least one first software identification code and at least one first software identification code are matched, a matching result is generated, the vehicle to be identified which the vehicle end belongs to is processed based on the matching result, the problems of low identification efficiency, low identification accuracy and the like in the manual identification mode in the related art are solved, in addition, the problem that the changed vehicle-mounted controller cannot be located in time under the condition that the configuration version information of the vehicle-mounted controller is changed is solved, the effect of double redundancy identification of the vehicle software identification codes by the vehicle end cloud is achieved, the identification efficiency and the identification accuracy of the vehicle software identification codes are improved, and the software safety of the vehicle is also improved.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method for identifying vehicle software identifications provided in accordance with a first embodiment of the present invention;
FIG. 2 is a flow chart of a method for identifying vehicle software identifications provided in accordance with a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a vehicle software identification recognition device according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a vehicle software identification recognition device according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device implementing a vehicle software identification recognition method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1 is a flowchart of a vehicle software identification recognition method according to an embodiment of the present invention, where the method may be applied to a cloud end and may be executed by a vehicle software identification recognition device, and the vehicle software identification recognition device may be implemented in the form of hardware and/or software, and the vehicle software identification recognition device may be configured in a terminal and/or a server. As shown in fig. 1, the method includes:
s110, receiving configuration version information corresponding to each vehicle-mounted controller reported by a vehicle side, and determining at least one first software identification code corresponding to the configuration version information.
It should be noted that the regulatory software identifier (RXSWIN) refers to a unique identifier that defines a series of software unique to a type authentication system conforming to a given united nations Regulation "X". RXSWIN characterizes a collection of software versions of a series of parts associated with a vehicle style authentication system. If the vehicle identification code (Vehicle Identification Number, VIN) is said to be the "identification number" of the whole vehicle, RXSWIN is the "identification number" of the vehicle software in the whole vehicle.
In this embodiment, the cloud may be an over-the-air technology (Overthe Air Technology, OTA) server for issuing the entire car upgrade package, a proxy server, a software client server for updating software, or any form of server that has acquired and updated software from the software client server. The vehicle end may be any type of vehicle that performs a software upgrade, any type of vehicle auxiliary equipment (e.g., a vehicle charging post, etc.), etc., which is not particularly limited in this embodiment. In practical applications, the vehicle end and the cloud end may establish communication connection, for example, the vehicle end and the cloud end may establish communication connection through hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) or based on hypertext transfer security protocol (Hyper Text Transfer Protocolover Secure Socket Layer, HTTPs) and other protocols, which is not limited in this embodiment.
In the present embodiment, the in-vehicle controller may be any electronic control unit (Electronic Control Unit, ECU) provided in the vehicle. Alternatively, the in-vehicle controller may include an emission-related ECU, a heating-related ECU, a power steering ECU, a vehicle body stabilization ECU, a vehicle control ECU, and the like. Wherein the emission-related ECU may be an ECU related to vehicle emission performance. For example, the emission-related ECU may include an engine management system (Engine Management System, EMS), an automatic transmission control unit (Transmission Control Unit, TCU), and a motor control unit (Motor Controller Unit, MCU), etc. The heating-related ECU may be an ECU related to vehicle heating performance. For example, the heating-related ECU may include an EMS, an Air Conditioner control (AC), a start control unit module (Start ControlUnit Module, SCU), and the like. The configuration version information may be information characterizing the software and/or hardware configuration of the in-vehicle controller. Alternatively, the configuration version information may include a part number of the ECU, a version number of software configured in the ECU, hardware high configuration information and/or hardware low configuration information, vendor information, and the like. The first software identification code can be a software identification code which is obtained by the cloud end according to the received configuration version information of the vehicle-mounted controller. Alternatively, the first software identification code may be the vehicle RXSWIN. It should be noted that, for ECUs of different performances, the corresponding RXSWIN may be different, and thus, one vehicle may correspond to at least one first software identification code.
In practical application, when the cloud receives the configuration version information corresponding to each vehicle-mounted controller sent by the vehicle end, at least one first software identification code corresponding to the received configuration version information can be determined according to the mapping relation between the pre-stored configuration version information and the software identification.
Optionally, determining at least one first software identification code corresponding to the configuration version information includes: acquiring a prestored first software identification mapping table corresponding to a vehicle to be identified to which a vehicle end belongs; and determining at least one first software identification code corresponding to the configuration version information according to the first software identification mapping table and each configuration version information.
In this embodiment, the first software identification mapping table may be a table that is pre-established and characterizes a mapping relationship between configuration version information of the vehicle-mounted controller and the software identification code. In practical application, after the vehicle production configuration is completed and leaves the factory, configuration version information of each vehicle-mounted controller in the vehicle can be obtained, a mapping relation table is constructed according to a mapping logic relation between the configuration version information and the software identification, the constructed mapping relation table can be used as a first software identification mapping table, and the first software identification mapping table and the vehicle identification are correspondingly stored in the cloud.
In practical application, the vehicle end can acquire configuration version information corresponding to each vehicle-mounted controller of the affiliated vehicle in real time, periodically or in an event mode. And then, the acquired configuration version information can be sent to the cloud end through the vehicle end, so that the cloud end can call the first software identification mapping table corresponding to the vehicle identification according to the vehicle identification corresponding to the vehicle end under the condition that the configuration version information corresponding to each vehicle-mounted controller sent by the vehicle end is received. Further, the received configuration version information corresponding to each vehicle-mounted controller can be matched according to the first software identification mapping table. Thereby, at least one first software identification code may be obtained.
For example, it is assumed that the received configuration version information corresponding to the in-vehicle controller includes a controller version corresponding to the emission-related ECU and a controller version corresponding to the heating-related ECU. For emission-related ECU, the EMS corresponding controller version is 4001; the controller version corresponding to the TCU is 4001; the controller version corresponding to the MCU is 4000, the first software identification code associated with the emissions may be R83-010. For a heating-related ECU, the version of the controller to which the EMS corresponds is 4001; the controller version corresponding to AC is 4002; the corresponding controller version of SCU is 4000, the first software identification code associated with heating may be R122-001.
S120, receiving at least one second software identification code reported by the vehicle end, matching the at least one first software identification code with the at least one second software identification code, generating a matching result, and processing the vehicle to be identified to which the vehicle end belongs based on the matching result.
In this embodiment, the second software identification code may be a software identification code that is obtained by the vehicle end through recognition according to the collected controller configuration version information. Alternatively, the second software identification code may be RXSWIN. The vehicle to be identified may be a vehicle to be identified and matched by the software identification code.
In practical application, when the collection of the configuration version information corresponding to each vehicle-mounted controller in the vehicle is completed by the vehicle end, at least one software identification code corresponding to the collected configuration version information can be determined according to the software identification mapping table stored by the vehicle end, and the determined software identification code can be used as a second software identification code. And then, the determined at least one second software identification code can be reported to the cloud.
In practical application, after the cloud end identifies at least one first software identification code, at least one second software identification code reported by the vehicle end can be received. And then, under the condition that at least one second software identification code reported by the vehicle end is received, the at least one first software identification code determined by the cloud end can be matched with the at least one second software identification code received by the cloud end. Under the condition that the matching result of the first software identification code and the second software identification code is successful, the vehicle to be identified, to which the vehicle end belongs, can not be processed. However, in the case that the matching result of the first software identification code and the second software identification code is that the matching fails, the vehicle to be identified to which the vehicle end belongs may be processed according to the matching situation of the software identification codes.
Optionally, the matching result is a matching failure, and correspondingly, the processing of the vehicle to be identified to which the vehicle end belongs based on the matching result includes: under the condition that the matching result is that the matching fails, acquiring a second version number of a second software identification mapping table stored at the vehicle end; matching the second version number with the first version number of the first software identification mapping table; and under the condition that the matching of the first version number and the second version number fails, the first software identification mapping table is sent to the vehicle end, so that the vehicle end can re-identify based on the first software identification mapping table under the condition that the vehicle end receives the first software identification mapping table.
In this embodiment, the second version number may be a version number characterizing version information of a second software identification map stored at the vehicle end. The first version number may be a version number characterizing version information of a first software identification map stored by the cloud.
In practical application, the first software identification mapping table stored in the cloud may be in a dynamic update state in real time or periodically, and the first software identification mapping table stored in the cloud is generally not tampered at will, so that when the second software identification code identified by the vehicle end fails to match with the first software identification code identified by the cloud, the first software identification mapping table stored in the cloud may be used as a reference.
In practical application, under the condition that the matching result of at least one first software identification code determined by the cloud and at least one second software identification code received by the cloud is that the matching fails, a first version number of a first software identification mapping table stored by the cloud and a second version number of a second software identification mapping table stored by a vehicle end can be respectively determined. Further, the second version number of the stored second software identification mapping table may be obtained from the vehicle end, and the obtained second version number and the determined first version number may be matched to determine whether the two version numbers are matched. And then, under the condition that the two version numbers are determined to be failed to be matched, the first software identification mapping table stored in the cloud can be sent to the vehicle end. Finally, under the condition that the vehicle end receives the first software identification mapping table sent by the cloud end, each piece of configuration version information collected by the vehicle end can be re-identified based on the received first software identification mapping table.
In practical application, in the process of identifying the received configuration version information by the cloud, the situation that the first software identification code corresponding to the configuration version information cannot be identified according to the stored first software identification mapping table exists. In this case, the vehicle-mounted controller having the abnormality may be determined according to the received configuration version information, and an abnormality instruction may be issued to the vehicle end.
Based on the above, the above technical means further includes: and under the condition that at least one first software identification code corresponding to the configuration version information is not generated, determining a target vehicle-mounted controller for identifying the abnormality from each vehicle-mounted controller according to the first software identification mapping table and each configuration version information, generating a controller abnormality instruction comprising the controller identification of the target vehicle-mounted controller, and sending the controller abnormality instruction to a vehicle end.
In this embodiment, the target vehicle-mounted controller may be a vehicle-mounted controller whose configuration version information is not matched with the configuration version information in the first software identification mapping table; it can also be understood as an in-vehicle controller whose configuration version information is arbitrarily changed. The controller identification may be a tag for identifying the in-vehicle controller. The controller identifier may be any form of identifier information, and may alternatively be an english identifier or a digital identifier. The controller exception command may be a piece of pre-written program code that may be used to indicate to the vehicle end the specifics of the exception vehicle controller.
In practical application, under the condition that the cloud identifies the configuration version information according to a pre-stored first software identification mapping table and at least one first software identification code corresponding to the configuration version information is not obtained, traversing the configuration version information in the first software identification mapping table for each received configuration version information corresponding to each vehicle-mounted controller, so as to determine the configuration version information which does not exist in the first software identification mapping table or is not matched with the received configuration version information, and taking the vehicle-mounted controller corresponding to the determined configuration version information as the target vehicle-mounted controller. Further, the controller identifier of the target vehicle-mounted controller can be determined, a controller abnormality instruction comprising the controller identifier of the target vehicle-mounted controller is generated, and the generated controller abnormality instruction is sent to the vehicle end, so that the vehicle end determines the vehicle-mounted controller with abnormality in the vehicle to be identified, to which the vehicle end belongs, under the condition that the controller abnormality instruction is received.
Based on the above, the above technical means further includes: under the condition that a second software identification code sent by the vehicle end is not received, acquiring a second version number of a second software identification mapping table stored in the vehicle end; matching the second version number with the first version number of the first software identification mapping table; and under the condition that the matching of the first version number and the second version number fails, the first software identification mapping table is sent to the vehicle end, so that the vehicle end can re-identify based on the first software identification mapping table under the condition that the vehicle end receives the first software identification mapping table.
In practical application, under the condition that the cloud end does not receive the second software identification code sent by the vehicle end, the first version number of the first software identification mapping table stored in the cloud end and the second version number of the second software identification mapping table stored in the vehicle end can be respectively determined. Further, the second version number of the stored second software identification mapping table may be obtained from the vehicle end, and the obtained second version number and the determined first version number may be matched to determine whether the two version numbers are matched. And then, under the condition that the two version numbers are determined to be failed to be matched, the first software identification mapping table stored in the cloud can be sent to the vehicle end. Finally, under the condition that the vehicle end receives the first software identification mapping table sent by the cloud end, each piece of configuration version information collected by the vehicle end can be re-identified based on the received first software identification mapping table.
According to the technical scheme, the configuration version information corresponding to each vehicle-mounted controller reported by the vehicle end is received, at least one first software identification code corresponding to the configuration version information is determined, further, at least one second software identification code reported by the vehicle end is received, at least one first software identification code and at least one first software identification code are matched, a matching result is generated, the vehicle to be identified which the vehicle end belongs to is processed based on the matching result, the problems of low identification efficiency, low identification accuracy and the like in the manual identification mode in the related art are solved, in addition, the problem that the changed vehicle-mounted controller cannot be located in time under the condition that the configuration version information of the vehicle-mounted controller is changed is solved, the effect of double redundancy identification of the vehicle software identification codes by the vehicle end cloud is achieved, the identification efficiency and the identification accuracy of the vehicle software identification codes are improved, and the software safety of the vehicle is also improved.
Example two
Fig. 2 is a flowchart of a vehicle software identification recognition method provided in a second embodiment of the present invention, where the present embodiment is applicable to a case of recognizing a software identification code of a vehicle according to configuration version information of a vehicle-mounted controller, the method may be applied to a vehicle end, and may be performed by a vehicle software identification recognition device, where the vehicle software identification recognition device may be implemented in a form of hardware and/or software, and the vehicle software identification recognition device may be configured in a terminal and/or a server. As shown in fig. 2, the method includes:
And S210, when detecting that the software version number of the vehicle-mounted controller changes, acquiring configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified, and reporting each configuration version information to the cloud.
In this embodiment, the software version number may be an identification number of the software version deployed in the in-vehicle controller. The vehicle to be identified may be a vehicle to be identified by the software identification code.
In practical application, when the vehicle-end master node detects that the software version number of any vehicle-mounted controller arranged in the vehicle to be identified changes, the need of re-identifying the vehicle software identification code can be described. Furthermore, configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified can be obtained, and meanwhile, the obtained configuration version information can be sent to a cloud end associated with a vehicle end.
It should be noted that, the acquisition timing of the configuration version information may be event type, that is, in the case that a change of a software version number of any vehicle-mounted controller is detected; alternatively, real-time may be used; alternatively, the cycle may be periodic, and the present embodiment is not particularly limited thereto.
S220, determining at least one second software identification code corresponding to the vehicle to be identified based on a pre-stored second software identification mapping table and configuration version information corresponding to each vehicle-mounted controller.
In this embodiment, the second software identification mapping table may be a predetermined table characterizing a mapping relationship between configuration version information of the vehicle-mounted controller and the software identification code. In practical application, the second software identification mapping table may be a mapping table with a preset format obtained by parsing a text description file. The preset format may be any format, and optionally may be xml format.
Based on the above, the above technical means further includes: acquiring a version description text corresponding to a vehicle to be identified; and analyzing the version description text based on a preset mapping analysis mode to obtain and store a second software identification mapping table corresponding to the vehicle to be identified.
In this embodiment, the version description text may be a text describing, in a text form, a correspondence relationship between the corresponding configuration version information of the vehicle-mounted controller and the software identification code. The version description text may be text information in any format, and alternatively, may be txt text format. The preset mapping parsing mode may be preset, and is used for determining the parsing mode of the software identification mapping table. Based on a preset mapping analysis mode, the acquired version description text in any format can be analyzed into an identification mapping table in a preset format.
In practical application, under the condition of acquiring the version description text corresponding to the vehicle to be identified, the acquired version description text can be analyzed according to a preset mapping analysis mode which is deployed at the vehicle end in advance, so that a software identification mapping table corresponding to the vehicle to be identified can be obtained, and the obtained software identification mapping table is used as a second software identification mapping table corresponding to the vehicle to be identified and stored at the vehicle end.
Further, under the condition that the configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified is obtained, the obtained configuration version information can be identified according to a pre-stored second software identification mapping table. Further, in the case where all the configuration version information can be identified, at least one second software identification code corresponding to the vehicle to be identified can be obtained. The advantages of this arrangement are that: under the condition that the vehicle end cannot normally communicate with the cloud, the vehicle end autonomous identification mode is adopted to complete real-time identification of the vehicle software identification code.
And S230, reporting the at least one second software identification code to the cloud end so that the cloud end can match the received at least one second software identification code with the at least one first software identification code generated by the cloud end, and processing the vehicle to be identified based on a matching result.
In practical application, when the vehicle end obtains at least one second software identification code, the obtained at least one second software identification code can be reported to the cloud end, so that the cloud end can match the received at least one second software identification code with at least one first software identification code generated by the cloud end when the cloud end receives the at least one second software identification code. Furthermore, the vehicle to be identified can be processed according to the matching result of the two software identification codes.
Further, if the matching result is that the matching is successful, no processing can be performed on the vehicle to be identified; and under the condition that the matching result is that the matching fails, triggering the vehicle end to re-identify.
According to the technical scheme, when the change of the software version number of the vehicle-mounted controller is detected, configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified is obtained, and each configuration version information is reported to the cloud, further, based on a pre-stored second software identification mapping table and the configuration version information corresponding to each vehicle-mounted controller, at least one second software identification code corresponding to the vehicle to be identified is determined, and finally, the at least one second software identification code is reported to the cloud, so that the received at least one second software identification code is matched with at least one first software identification code generated by the cloud, the vehicle to be identified is processed based on the matching result, the problems that the identification efficiency and the identification accuracy of a manual identification mode in the related technology are low and the like are solved, and in addition, the problem that the changed vehicle-mounted controller cannot be positioned in time under the condition that the configuration version information of the vehicle-mounted controller is changed is solved, the effect of dual identification of the vehicle software identification code is achieved, the identification efficiency and the identification accuracy of the vehicle software identification code are improved, and the safety of the vehicle is improved.
Example III
Fig. 3 is a schematic structural diagram of a vehicle software identification recognition device according to a third embodiment of the present invention. The device is configured at the cloud, as shown in fig. 3, and the device includes: a configuration version information receiving module 310 and a software identification code matching module 320.
The configuration version information receiving module 310 is configured to receive configuration version information corresponding to each vehicle-mounted controller reported by a vehicle end, and determine at least one first software identification code corresponding to the configuration version information; the software identification code matching module 320 is configured to receive at least one second software identification code reported by the vehicle end, match the at least one first software identification code with the at least one first software identification code, generate a matching result, and process a vehicle to be identified to which the vehicle end belongs based on the matching result.
According to the technical scheme, the configuration version information corresponding to each vehicle-mounted controller reported by the vehicle end is received, at least one first software identification code corresponding to the configuration version information is determined, further, at least one second software identification code reported by the vehicle end is received, at least one first software identification code and at least one first software identification code are matched, a matching result is generated, the vehicle to be identified which the vehicle end belongs to is processed based on the matching result, the problems of low identification efficiency, low identification accuracy and the like in the manual identification mode in the related art are solved, in addition, the problem that the changed vehicle-mounted controller cannot be located in time under the condition that the configuration version information of the vehicle-mounted controller is changed is solved, the effect of double redundancy identification of the vehicle software identification codes by the vehicle end cloud is achieved, the identification efficiency and the identification accuracy of the vehicle software identification codes are improved, and the software safety of the vehicle is also improved.
Optionally, the configuration version information receiving module 310 includes: and a mapping table acquisition unit and a software identification code determination unit.
The mapping table acquisition unit is used for acquiring a prestored first software identification mapping table corresponding to the vehicle to be identified to which the vehicle end belongs;
and the software identification code determining unit is used for determining at least one first software identification code corresponding to the configuration version information according to the first software identification mapping table and each configuration version information.
Optionally, the matching result is a matching failure, and accordingly, the software identification code matching module 320 includes: the device comprises a version number acquisition unit, a version number matching unit and a re-identification triggering unit.
A version number obtaining unit, configured to obtain a second version number of a second software identification mapping table stored in the vehicle end when the matching result is that the matching fails;
the version number matching unit is used for matching the second version number with the first version number of the first software identification mapping table;
and the re-identification triggering unit is used for sending the first software identification mapping table to the vehicle end under the condition that the first version number and the second version number are failed to be matched, so that the vehicle end can re-identify based on the first software identification mapping table under the condition that the vehicle end receives the first software identification mapping table.
Optionally, the apparatus further includes: and the target vehicle-mounted controller determining module.
The target vehicle-mounted controller determining module is used for determining the target vehicle-mounted controller for identifying the abnormality from each vehicle-mounted controller according to the first software identification mapping table and each configuration version information under the condition that at least one first software identification code corresponding to the configuration version information is not generated, generating a controller abnormality instruction comprising the controller identification of the target vehicle-mounted controller and sending the controller abnormality instruction to the vehicle end.
Optionally, the apparatus further includes: the device comprises a version number acquisition module, a version number matching module and a re-identification triggering module.
The version number acquisition module is used for acquiring a second version number of a second software identification mapping table stored in the vehicle terminal under the condition that the second software identification code sent by the vehicle terminal is not received;
the version number matching module is used for matching the second version number with the first version number of the first software identification mapping table;
and the re-identification triggering module is used for sending the first software identification mapping table to the vehicle end under the condition that the first version number and the second version number are failed to be matched, so that the vehicle end can re-identify based on the first software identification mapping table under the condition that the vehicle end receives the first software identification mapping table.
The vehicle software identification recognition device provided by the embodiment of the invention can execute the vehicle software identification recognition method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example IV
Fig. 4 is a schematic structural diagram of a vehicle software identification recognition device according to a fourth embodiment of the present invention. The device is configured at a vehicle end, as shown in fig. 4, and the device includes: a configuration version information acquisition module 410, a first software identification code determination module 420, and a software identification code reporting module 430.
The configuration version information obtaining module 410 is configured to obtain configuration version information corresponding to each vehicle-mounted controller in a vehicle to be identified when detecting that a software version number of the vehicle-mounted controller changes, and report each configuration version information to a cloud; a first software identification code determining module 420, configured to determine at least one second software identification code corresponding to the vehicle to be identified based on a first software identification mapping table stored in advance and configuration version information corresponding to each of the vehicle-mounted controllers; the software identification code reporting module 430 is configured to report the at least one second software identification code to the cloud end, so that the cloud end matches the received at least one second software identification code with at least one first software identification code generated by the cloud end, and process the vehicle to be identified based on a matching result.
According to the technical scheme, when the change of the software version number of the vehicle-mounted controller is detected, configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified is obtained, and each configuration version information is reported to the cloud, further, based on a pre-stored second software identification mapping table and the configuration version information corresponding to each vehicle-mounted controller, at least one second software identification code corresponding to the vehicle to be identified is determined, and finally, the at least one second software identification code is reported to the cloud, so that the received at least one second software identification code is matched with at least one first software identification code generated by the cloud, the vehicle to be identified is processed based on the matching result, the problems that the identification efficiency and the identification accuracy of a manual identification mode in the related technology are low and the like are solved, and in addition, the problem that the changed vehicle-mounted controller cannot be positioned in time under the condition that the configuration version information of the vehicle-mounted controller is changed is solved, the effect of dual identification of the vehicle software identification code is achieved, the identification efficiency and the identification accuracy of the vehicle software identification code are improved, and the safety of the vehicle is improved.
Optionally, the apparatus further includes: the version description text acquisition module and the version description text analysis module.
The version description text acquisition module is used for acquiring version description text corresponding to the vehicle to be identified;
and the version description text analysis module is used for analyzing the version description text based on a preset mapping analysis mode to obtain and store a second software identification mapping table corresponding to the vehicle to be identified.
The vehicle software identification recognition device provided by the embodiment of the invention can execute the vehicle software identification recognition method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example five
Fig. 5 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 5, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as the vehicle software identification method.
In some embodiments, the vehicle software identification recognition method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the vehicle software identification recognition method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the vehicle software identification recognition method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. The vehicle software identification recognition method is characterized by being applied to a cloud and comprising the following steps of:
receiving configuration version information corresponding to each vehicle-mounted controller reported by a vehicle end, and determining at least one first software identification code corresponding to the configuration version information;
and receiving at least one second software identification code reported by the vehicle end, matching the at least one first software identification code with the at least one first software identification code, generating a matching result, and processing the vehicle to be identified to which the vehicle end belongs based on the matching result.
2. The method of claim 1, wherein said determining at least one first software identification code corresponding to said configuration version information comprises:
acquiring a prestored first software identification mapping table corresponding to a vehicle to be identified to which the vehicle end belongs;
and determining at least one first software identification code corresponding to the configuration version information according to the first software identification mapping table and each piece of configuration version information.
3. The method according to claim 1, wherein the matching result is a matching failure, and the processing the vehicle to be identified to which the vehicle end belongs based on the matching result includes:
acquiring a second version number of a second software identification mapping table stored in the vehicle end under the condition that the matching result is that the matching fails;
matching the second version number with the first version number of the first software identification mapping table;
and under the condition that the matching of the first version number and the second version number fails, the first software identification mapping table is sent to the vehicle end, so that the vehicle end can re-identify based on the first software identification mapping table under the condition that the vehicle end receives the first software identification mapping table.
4. The method as recited in claim 2, further comprising:
and under the condition that at least one first software identification code corresponding to the configuration version information is not generated, determining a target vehicle-mounted controller for identifying abnormality from each vehicle-mounted controller according to the first software identification mapping table and each configuration version information, generating a controller abnormality instruction comprising a controller identification of the target vehicle-mounted controller, and sending the controller abnormality instruction to the vehicle side.
5. The method as recited in claim 1, further comprising:
under the condition that the second software identification code sent by the vehicle end is not received, acquiring a second version number of a second software identification mapping table stored in the vehicle end;
matching the second version number with the first version number of the first software identification mapping table;
and under the condition that the matching of the first version number and the second version number fails, the first software identification mapping table is sent to the vehicle end, so that the vehicle end can re-identify based on the first software identification mapping table under the condition that the vehicle end receives the first software identification mapping table.
6. The vehicle software identification recognition method is characterized by being applied to a vehicle end and comprising the following steps of:
When the change of the software version number of the vehicle-mounted controller is detected, configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified is obtained, and each configuration version information is reported to a cloud;
determining at least one second software identification code corresponding to the vehicle to be identified based on a pre-stored first software identification mapping table and configuration version information corresponding to each vehicle-mounted controller;
and reporting the at least one second software identification code to the cloud end so that the cloud end can match the received at least one second software identification code with at least one first software identification code generated by the cloud end, and processing the vehicle to be identified based on a matching result.
7. The method as recited in claim 6, further comprising:
acquiring a version description text corresponding to a vehicle to be identified;
and analyzing the version description text based on a preset mapping analysis mode to obtain and store a second software identification mapping table corresponding to the vehicle to be identified.
8. A vehicle software identification recognition device, characterized in that it is configured in a cloud, comprising:
the system comprises a configuration version information receiving module, a configuration version information processing module and a configuration version information processing module, wherein the configuration version information receiving module is used for receiving configuration version information corresponding to each vehicle-mounted controller reported by a vehicle end and determining at least one first software identification code corresponding to the configuration version information;
The software identification matching module is used for receiving at least one second software identification code reported by the vehicle end, matching the at least one first software identification code with the at least one first software identification code, generating a matching result, and processing a vehicle to be identified to which the vehicle end belongs based on the matching result.
9. A vehicle software identification recognition device, characterized in that it is configured at a vehicle end, comprising:
the configuration version information acquisition module is used for acquiring configuration version information corresponding to each vehicle-mounted controller in the vehicle to be identified when detecting that the software version number of the vehicle-mounted controller changes, and reporting each configuration version information to the cloud;
the first software identification determining module is used for determining at least one second software identification code corresponding to the vehicle to be identified based on a pre-stored first software identification mapping table and configuration version information corresponding to each vehicle-mounted controller;
the software identification reporting module is used for reporting the at least one second software identification code to the cloud end so that the cloud end can match the received at least one second software identification code with at least one first software identification code generated by the cloud end, and the vehicle to be identified is processed based on a matching result.
10. An electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the vehicle software identification recognition method of any one of claims 1-5 or 6-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310799993.2A CN116804932A (en) | 2023-06-30 | 2023-06-30 | Vehicle software identification recognition method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310799993.2A CN116804932A (en) | 2023-06-30 | 2023-06-30 | Vehicle software identification recognition method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116804932A true CN116804932A (en) | 2023-09-26 |
Family
ID=88080632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310799993.2A Pending CN116804932A (en) | 2023-06-30 | 2023-06-30 | Vehicle software identification recognition method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116804932A (en) |
-
2023
- 2023-06-30 CN CN202310799993.2A patent/CN116804932A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109164783B (en) | Vehicle diagnosis method, apparatus, device, and medium | |
| CN108803580B (en) | Method for matching vehicle CAN protocol and related equipment | |
| CN107544271B (en) | Terminal control method, device and computer readable storage medium | |
| CN111813095A (en) | Vehicle diagnosis method, device and medium | |
| CN115437339A (en) | Remote diagnosis method and device, electronic equipment and storage medium | |
| US20220236710A1 (en) | Efficient controller data generation and extraction | |
| CN114386005A (en) | Login method and device of vehicle-mounted system, electronic equipment and readable storage medium | |
| CN112306041A (en) | Vehicle configuration information writing method and device and electronic equipment | |
| CN115086384B (en) | Remote control test method, device, equipment and storage medium | |
| CN115167351B (en) | Controller function updating method, system, vehicle and server | |
| CN116450176A (en) | Version updating method and device, electronic equipment and storage medium | |
| CN116804932A (en) | Vehicle software identification recognition method and device, electronic equipment and storage medium | |
| CN116149709A (en) | Firmware upgrading method, device, equipment and medium | |
| CN115904447A (en) | Version updating system, method, electronic equipment and storage medium | |
| CN115774837A (en) | Signal verification method, device, equipment, medium, program product and vehicle | |
| CN114880007A (en) | Upgrading method, device, equipment and storage medium | |
| CN115469899A (en) | Firmware upgrading method, device, equipment, medium and vehicle-mounted system | |
| CN116449810B (en) | Fault detection method and device, electronic equipment and storage medium | |
| CN114371773B (en) | Power supply control method, electronic equipment and server | |
| CN116931982A (en) | Configuration method and device and vehicle | |
| CN116233826A (en) | Method and device for writing software data, electronic equipment and storage medium thereof | |
| CN118111720A (en) | National standard test system, method, device, equipment and medium for new energy vehicle | |
| CN116016494A (en) | Method, device, equipment, medium and system for transmitting ephemeris file | |
| CN117931882A (en) | Vehicle condition information acquisition method, device, equipment and storage medium | |
| CN116737475A (en) | Chip diagnosis method, device, equipment and storage medium |
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 |