Intelligent cabin software version number integration system and method for vehicle-mounted infotainment system, and electronic equipment

Abstract

The invention discloses a vehicle intelligent cabin software version number integration system and method and electronic equipment, and relates to the technical field of software, and the system comprises a version number rule definition module which is used for setting a composition rule of a vehicle intelligent cabin OS baseline software version number; the trigger mechanism module is used for determining a trigger condition of version number self-increasing and triggering a standard basic task serving as a benchmark through an automatic server tool; when the base line has code update, receives a product stage update instruction or obtains vehicle type and hardware equipment information change, correspondingly triggering a self-increasing signal of a primary version number, a secondary version number or integration times; the self-increasing execution module is used for receiving a signal of the trigger mechanism module and updating a version number according to a preset rule; the integration module is used for integrating the updated version number into a mirror image package and is linked with a development tool chain of the vehicle intelligent cabin OS baseline software; the development tool chain comprises a code warehouse, an automatic testing tool and a project management tool.

Description

TECHNICAL FIELD

[0001] The application relates to the software technical field, in particular to a vehicle intelligent cockpit software version number integration system, a vehicle intelligent cockpit software version number integration system method, an electronic device and a storage medium. BACKGROUND

[0002] In the development of vehicle intelligent cockpit OS, a platform baseline needs to be adapted to multiple hardware devices, and version number management is crucial. At present, the management of software version numbers of each vehicle type corresponding to the vehicle intelligent cockpit OS baseline in the prior art mainly relies on manual operation. The prior art has many shortcomings: first, the accuracy is low, and manual input is prone to errors such as incorrect numbers, repeated version numbers or missed records. An enterprise once delayed the product online time due to the confusion of different versions of functions caused by version number errors during software testing; second, the efficiency is low, and each version update needs a dedicated person to record and synchronize the version number. In the case of multi-team collaborative development, the version number transmission is not timely, which affects the development progress; third, it is difficult to trace back, and when a certain historical version needs to be traced back, it is difficult to quickly and accurately find the corresponding version number and related information due to the possible non-standard manual records.

[0003] The main reason for these problems is the lack of an automatic version number management mechanism. The prior art does not design an automatic version number self-increment scheme that can be deeply integrated with the development process according to the characteristics of the vehicle intelligent cockpit OS baseline software. At the same time, since the development of vehicle software involves multiple teams and links, it is difficult to coordinate all parties to manage the version numbers uniformly, which also leads to the inevitable drawbacks of manual operation. SUMMARY

[0004] Therefore, the purpose of the present application is to provide a vehicle intelligent cockpit software version number integration system, a vehicle intelligent cockpit software version number integration system method, an electronic device and a storage medium, which aims to solve the technical problems of the lack of an automatic version number management mechanism in the prior art, the development of vehicle software involving multiple teams and links, and the difficulty of coordinating all parties to manage the version numbers uniformly.

[0005] The present application provides the following solutions:

[0006] According to one aspect of the present application, a vehicle intelligent cockpit software version number integration system is provided, comprising:

[0007] The version number rule definition module, the trigger mechanism module, the self-increment execution module and the integration module; the version number rule definition module is used to set the constituting rules of the vehicle intelligent cockpit OS baseline software version number;

[0008] The version number includes: the main version number, the secondary version number and the integration times;

[0009] a triggering mechanism module configured to determine a triggering condition for incrementing the version number and trigger a standardized basic task serving as a benchmark through an automated server tool;

[0010] When there is a code update, a product stage update instruction is received, or a vehicle model and hardware device information change is obtained, a signal for incrementing the major version number, the minor version number, or the integration number is triggered;

[0011] an increment execution module configured to receive the signal of the triggering mechanism module and update the version number according to a preset rule;

[0012] an integration module configured to integrate the updated version number into an image package and link the image package with a development tool chain of the vehicle intelligent cockpit OS baseline software;

[0013] The development tool chain includes a code repository, an automated testing tool, and a project management tool.

[0014] Further, the version number includes:

[0015] The version number includes a version number format rule;

[0016] Specifically, the version number includes a major version number, a minor version number, and an integration number.

[0017] The major version number is used to identify a product stage, the minor version number includes two digits, the first digit is used to identify a vehicle model and the second digit is used to identify a hardware device stage, and the last three digits after the decimal point are used to identify the integration number.

[0018] Further, the version number includes:

[0019] The triggering mechanism module is further configured to push a triggering reason notification to a project management tool in the development tool chain when the signal for incrementing the major version number, the minor version number, or the integration number is triggered;

[0020] The triggering reason notification includes a triggering event type and a corresponding change content summary.

[0021] The triggering event type includes a code update, a product stage update, a vehicle model change, and a hardware device change.

[0022] Further, the version number includes:

[0023] The increment execution module performs compliance verification on the updated version number after updating the version number according to the preset rule.

[0024] The compliance verification includes verifying whether the major version number is a non-negative integer, whether the minor version number conforms to a preset format, and whether the integration number conforms to a preset format.

[0025] If the verification fails, a version number exception alarm is pushed to the project management tool and a version number integration process is suspended.

[0026] Further comprising:

[0027] The integration module, when integrating the updated version number into the image package, retrieves the latest code commit record of the current baseline software from the code repository, and stores the code commit record in association with the updated version number in the version description document of the image package, which is distributed synchronously with the image package.

[0028] Further comprising:

[0029] The version number rule definition module supports receiving user-initiated version number rule adjustment instructions through the project management tool in the development tool chain;

[0030] The version number rule adjustment instructions include modification of the major version number trigger condition, adjustment of the minor version number bit number, and change of the integration count start value, and after the rule adjustment, the version number rule definition module needs to automatically synchronize the adjusted rule to the self-increment execution module.

[0031] Further comprising:

[0032] The linkage of the integration module and the automated test tool further includes: after integrating the updated version number into the image package, automatically triggering the automated test tool to perform version compatibility testing on the image package;

[0033] The version compatibility testing includes adaptation testing of the image package with the current vehicle hardware driver and compatibility testing of the image package with historical version software data interaction;

[0034] If the testing passes, a test report is generated and the image package is marked as a publishable state;

[0035] If the testing fails, the failure items are fed back to the project management tool and associated with the corresponding version number record.

[0036] According to the two aspects of the present application, a vehicle machine intelligent cockpit software version number integration method is provided, comprising the following steps:

[0037] Obtaining the composition rule of the vehicle machine intelligent cockpit OS baseline software version number;

[0038] The version number includes: major version number, minor version number, and integration count;

[0039] When the baseline has code updates, receives product stage update instructions, or obtains vehicle type and hardware device information changes, a self-increment signal of the major version number, minor version number, or integration count is triggered accordingly;

[0040] According to the self-increment signal, updating the version number according to the preset rule;

[0041] Integrate the updated version number into the image package and link it with the development tool chain of the car machine intelligent cockpit OS baseline software.

[0042] According to the three aspects of the present application, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus.

[0043] The memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of a car machine intelligent cockpit software version number integration method.

[0044] According to the four aspects of the present application, a computer readable storage medium is provided, which stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of a car machine intelligent cockpit software version number integration method.

[0045] Compared with the prior art, the present application has the following advantages:

[0046] The present application generates and updates the version number through an automatic self-increment mechanism, avoids errors caused by manual input, makes the record of the version number accurate and error-free, and greatly reduces the error rate of the version number through testing.

[0047] The present application does not require a dedicated person to manually record and transfer the version number, and the version number is automatically updated with the code submission, the version information is synchronized in real time in multi-team collaboration, and the development cycle is shortened by an average of 20%.

[0048] The present application automatically associates the version number with code submission records, development process logs, etc., and when it is necessary to trace back to the historical version, the corresponding version number and related information can be quickly and accurately located, and the trace-back time is shortened from an average of 2 hours to within 5 minutes.

[0049] The present application unifies the generation rule and update standard of the version number, makes the version management of the car machine intelligent cockpit OS baseline software more standardized, and is conducive to the quality control of the software. BRIEF DESCRIPTION OF DRAWINGS

[0050] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings needed to be used in the specific embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0051] Figure 1Is a vehicle machine intelligent cockpit software version number integration system structure diagram provided by one or more embodiments of the present application.

[0052] Figure 2 Is a vehicle machine intelligent cockpit software version number integration method flow chart provided by one or more embodiments of the present application.

[0053] Figure 3 Is the schematic diagram of OS version number automatic generation and integration process of one specific embodiment of the present application.

[0054] Figure 4 Is an electronic device structure block diagram of a vehicle machine intelligent cockpit software version number integration method provided by one or more embodiments of the present application. DETAILED DESCRIPTION

[0055] The technical solutions of the present application will be described clearly and completely below in combination with the drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0056] Figure 1 Is a vehicle machine intelligent cockpit software version number integration system structure diagram provided by one or more embodiments of the present application.

[0057] As Figure 1 shown, including:

[0058] Version number rule definition module, trigger mechanism module, self-increment execution module and integration module. The version number rule definition module is used to set the constituting rules of the vehicle machine intelligent cockpit OS baseline software version number;

[0059] The version number includes: major version number, minor version number and integration times;

[0060] Specifically, by setting the constituting rules of the vehicle machine intelligent cockpit OS baseline software version number, the same naming rules are constructed, which ensures that all team members and automated tools have a consistent understanding of the meaning of the version number, laying a foundation for subsequent automation and tracing.

[0061] The major version number is usually used to represent major, incompatible architecture or function changes, for example, from supporting single-core chips to supporting multi-core chips, which may trigger the increment of the major version number.

[0062] The minor version number is usually used to represent the addition of important functions or features, but maintains backward compatibility, for example, an additional voice assistant function may trigger the increment of the minor version number.

[0063] The integration times, usually used to represent the number of continuous integration or adaptation of the same baseline, for example, for different vehicle models or different hardware configurations, after each successful integration, the integration times will be incremented.

[0064] The trigger mechanism module is used to determine the trigger condition of the version number increment, and trigger the standardized basic task as the benchmark through the automatic server tool.

[0065] When the baseline has code updates, receives product stage update instructions, or obtains changes in vehicle and hardware device information, the primary version number, secondary version number, or integration times increment signal is triggered.

[0066] Specifically, when the baseline has code updates, receives product stage update instructions, or obtains changes in vehicle and hardware device information, the primary version number, secondary version number, or integration times increment signal is triggered.

[0067] The trigger mechanism module listens to specific events and decides whether and how to update the version number according to the event type.

[0068] Among them, the code update includes: major, architecture-level code changes.

[0069] Receiving product stage update instructions means that the product enters the next stage from one stage, usually indicating that a new set of functions has been completed and integrated, at which time the secondary version number is incremented.

[0070] Obtaining changes in vehicle and hardware device information includes:

[0071] When the OS needs to adapt to a new vehicle model or a new hardware configuration, the integration times increment is triggered.

[0072] Triggering the standardized basic task as the benchmark through the automatic server tool specifically includes:

[0073] The baseline Job is triggered by the Jenkins tool at regular intervals or manually when the baseline has code updates, and the version numbers are obtained from the OS version storage data according to the rules, realizing the automation and intelligence of version number updating, and ensuring the accurate synchronization of version number changes with specific development activities (code submission, stage iteration, hardware adaptation)

[0074] The increment execution module is used to receive the signal of the trigger mechanism module and update the version number according to the preset rules.

[0075] Specifically, when receiving the change signal, according to the current version number, the integration times is incremented by one to generate a new version number.

[0076] Through the specific calculation and generation of the version number, the accuracy and consistency of the version number increment are guaranteed, and human calculation errors are avoided.

[0077] an integration module, configured to integrate the updated version number into an image package and link with a development tool chain of the intelligent cockpit OS baseline software of the vehicle machine;

[0078] The development tool chain comprises a code repository, an automated testing tool, and a project management tool.

[0079] Specifically, the version number is written into metadata of a software image package (such as a Docker image) or as a tag of the image. In this way, each delivered image has a unique and explicit version identifier.

[0080] The format rule of the preset major version number, minor version number, and integration times.

[0081] The events include code update, stage iteration, and hardware change.

[0082] When the change event is monitored, it is determined which type of version number increment should be triggered, and a signal is sent to the self-increment execution module.

[0083] The signal is received, and a new version number is calculated and generated according to the preset rule.

[0084] The new version number is embedded into the image package, and the code repository, the testing tool, and the project management tool are notified to update synchronously.

[0085] Further, the version number generation method comprises the following steps:

[0086] The version number generation method further comprises a version number format rule.

[0087] Specifically, the version number format rule comprises a major version number, a minor version number, and integration times.

[0088] The major version number is used to identify the product stage; the minor version number comprises two digits, the first digit is used to identify the vehicle model, and the second digit is used to identify the hardware device stage; and the last three digits after the decimal point are used to identify the integration times.

[0089] Further, the version number generation method comprises the following steps:

[0090] The trigger mechanism module is further configured to push a trigger cause notification to the project management tool in the development tool chain when the self-increment signal of the major version number, the minor version number, or the integration times is triggered.

[0091] The trigger cause notification comprises a trigger event type and a corresponding change content summary.

[0092] The trigger event type comprises code update, product stage update, vehicle model change, and hardware device change.

[0093] Specifically, the notification is sent while triggering the version number to be incremented, and by distinguishing the trigger event type, the event that causes the version number to change is clear, and the code update: corresponds to the major version number increment;

[0094] Product stage update: corresponding to the minor version number increment.

[0095] Vehicle and hardware device change: corresponding to the integration times increment.

[0096] Through the comments in the project management tool, the subsequent traceability is enhanced.

[0097] The relevant team members can understand the reason and content of the version change according to the automatically received notification.

[0098] Further, including:

[0099] The self-increment execution module performs compliance verification on the updated version number after updating the version number according to the preset rules;

[0100] The compliance verification includes: verifying whether the major version number is a non-negative integer, whether the minor version number conforms to the preset format, and whether the integration times conforms to the preset format;

[0101] If the verification fails, the version number exception alarm is pushed to the project management tool and the version number integration process is suspended.

[0102] Specifically, through automatic verification, illegal version numbers caused by script errors, manual intervention or logic loopholes are eliminated, ensuring the uniformity and seriousness of all version numbers.

[0103] Problems are found before the version number takes effect, avoiding the spread of errors in the entire development process and saving the cost of subsequent troubleshooting and correction.

[0104] A solid firewall is added to the version number management system, making it able to cope with abnormal situations and improving the stability and reliability of the entire automated process.

[0105] When problems occur, the system can not only automatically suspend, but also actively alarm, allowing the team to quickly respond and handle, reducing the burden of manual monitoring.

[0106] Further, including:

[0107] The integration module retrieves the latest code commit record of the current baseline software from the code repository when integrating the updated version number into the image package, and stores the code commit record and the updated version number in the version specification document of the image package. The version specification document is distributed synchronously with the image package.

[0108] Further, including:

[0109] The version number rule definition module supports receiving a user-initiated version number rule adjustment instruction through a project management tool in a development tool chain;

[0110] The version number rule adjustment instruction includes a major version number trigger condition modification, a minor version number bit number adjustment, and an integration count start value change, and after the rule adjustment, the version number rule definition module needs to automatically synchronize the adjusted rule to the automatic increment execution module.

[0111] Further, it includes:

[0112] The linkage of the integration module and the automated test tool also includes: after integrating the updated version number into the image package, automatically triggering the automated test tool to perform version compatibility testing on the image package;

[0113] The version compatibility testing includes compatibility testing of the image package with the current vehicle hardware driver and compatibility testing of the interaction of the historical version software data;

[0114] If the testing passes, a test report is generated and the image package is marked as a publishable state;

[0115] If the testing fails, the failure items are fed back to the project management tool and associated with the corresponding version number record.

[0116] It is worth noting that although only some basic functional modules are disclosed in the embodiment, it does not mean that the composition of the system is limited to the above basic functional modules. On the contrary, the embodiment intends to express that on the basis of the above basic functional modules, a person skilled in the art can add one or more functional modules to form an infinite number of embodiments or technical solutions according to the prior art, that is, the system is open rather than closed, and the protection scope of the present application claim cannot be limited to the disclosed basic functional modules. At the same time, for the convenience of description, the above device is described as various units and modules. Of course, in the implementation of the present application, the functions of the units and modules can be realized in the same or multiple software and / or hardware.

[0117] The device implementation described above is only schematic; the units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., they can be located in one place or distributed over multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the present embodiment. A person skilled in the art can understand and implement it without creative labor.

[0118] Figure 2is a flowchart of a vehicle machine intelligent cockpit software version number integration method provided by one or more embodiments of the present application.

[0119] As shown in Figure 2 , comprising the following steps:

[0120] Step S1, obtaining the composition rule of the vehicle machine intelligent cockpit OS baseline software version number;

[0121] The version number includes: major version number, minor version number and integration times;

[0122] Step S2, when the baseline has code update, receives product stage update instruction or obtains vehicle type and hardware device information change, corresponding trigger major version number, minor version number or integration times of self-increment signal;

[0123] Step S3, according to the self-increment signal, updating the version number according to the preset rule;

[0124] Step S4, integrating the updated version number into the image package, and linking with the development tool chain of the vehicle machine intelligent cockpit OS baseline software.

[0125] In one embodiment, as shown in Figure 3 , a vehicle machine intelligent cockpit software version number integration system, comprising: version number rule definition module, trigger mechanism module, automatic self-increment execution module and integration module,

[0126] Among them, the version number rule definition module: this module is used to set the composition rule of the vehicle machine intelligent cockpit OS baseline software version number, the version number is composed of major version number, minor version number and integration times, and the format is major version number minor version number integration times. For example 111.120. Among them, the major version number is used to identify the product stage, the minor version number is composed of two parts, the first part identifies the vehicle type and the second part identifies the hardware device stage, and the three digits after the decimal point identify the integration times.

[0127] Among them, the major version number (3-bit non-negative integer): is specially used to identify the product life cycle stage, different values correspond to specific product stages, and the value increment only corresponds to the major iteration of the product stage, and cannot jump across stages.

[0128] The minor version number (2-bit fixed length): adopts the combination logic of vehicle type identification and hardware device stage identification, the first digit corresponds to the vehicle type (such as “1” representing SUV vehicle type, “2” representing car vehicle type, and “3” representing MPV vehicle type), the second digit corresponds to the hardware device stage (such as “0” representing hardware prototype stage, “1” representing hardware trial production stage, and “2” representing hardware mass production stage), the field length is fixed, and 0 is supplemented when it is insufficient (such as vehicle type 1, hardware prototype stage corresponding to minor version number “10”).

[0129] Integration count (fixed length of 3 decimal places): Used to record the number of software integrations under the same major version number and minor version number. The value range is 001-999. If it is less than 3 digits, it is padded with leading zeros (e.g., the 1st integration corresponds to "001", and the 12th integration corresponds to "012"). The core rule is: when either the major version number or the minor version number changes, the integration count is automatically reset to 1 and starts counting again from 1.

[0130] The module supports flexible configuration and expansion of rules, and the meaning of fields can be adjusted according to the car manufacturer's model planning and hardware iteration rhythm (such as only needing to expand the numerical mapping relationship of the first digit of the minor version number when adding a new model), without modifying the core architecture, and adapting to the customized needs of different car manufacturers.

[0131] Trigger Mechanism Module: This module is responsible for determining the trigger conditions for version number auto-increment. Baseline Jobs are triggered periodically or manually using Jenkins tools. When the baseline has code updates, various version numbers are retrieved from the OS version storage data according to rules. When an update instruction is received for the product stage, the major version number auto-increment module is triggered. The minor version number automatically triggers its auto-increment module based on the received vehicle model and hardware device information. The compilation count triggers its auto-increment module based on the major and minor version information. When either the major or minor version changes, the integration count resets to 1 and starts incrementing from 1.

[0132] Specifically, it involves configuring scheduled tasks (such as at 2 AM daily) through Jenkins Pipeline scripts, or listening for commit events in code repositories (such as Git) to automatically trigger baseline jobs (standardized basic tasks, including code fetching, compilation, basic verification, and other processes).

[0133] Manual triggering: When an urgent version update is needed (such as fixing a major security vulnerability), developers can manually trigger the baseline job through the Jenkins interface to ensure the flexibility of version updates in special scenarios.

[0134] After the baseline job is triggered, the module automatically reads the latest version number and associated metadata (such as the current product stage, compatible vehicle models, and hardware stage) from the OS version-specific database (which stores historical version numbers, field mapping relationships, change records, etc.).

[0135] Triggering conditions and signal transmission:

[0136] Product stage update trigger: When a product stage iteration instruction (such as upgrading from Alpha stage to Beta stage) is received from the product management system (such as iwork), the main version number auto-increment signal is immediately triggered and transmitted to the auto-increment execution module through the internal message queue;

[0137] Model / hardware change trigger: when the changes submitted in the code repository contain the configuration files of the newly added / switched vehicle model and the stage upgrade of the hardware device (such as hardware adaptation parameters and vehicle model exclusive function code), the module automatically parses the change content and triggers the self-increment signal of the corresponding bit of the minor version number;

[0138] Integration frequency trigger: when the major version number and the minor version number are not changed, only the regular development activities such as code optimization and bug fixing exist, and the integration frequency self-increment signal is automatically triggered after the baseline job is executed; if either the major version number or the minor version number triggers self-increment, the integration frequency triggers the “return to 1 signal” synchronously.

[0139] Automatic self-increment execution module: this module receives the trigger signal from the trigger mechanism module, and performs automatic calculation and update of the version number according to the rules defined by the version number rule definition module. For example, the current version number is 110.010, when the major version number self-increment module is triggered, the version number is updated to 210.001; when the major version number self-increment module is not triggered and the minor version number hardware device self-increment module is triggered, the version number is updated to 110.001.

[0140] Integration module: integrate the above-mentioned module to generate the OS software version number into the software image package and integrate it with the development tool chain of the vehicle machine intelligent cockpit OS baseline software. It includes the code repository (such as the entire Git repository of the repo xml file), the automatic test tool (such as Jenkins), and the project management tool (such as iwork). When the baseline adapted vehicle model OS software version is successfully compiled, the integration module transmits the submission information to the automatic test tool; after the test is passed, the trigger mechanism module receives the signal, starts the automatic self-increment execution module to update the version number; the updated version number is synchronized with the version number management module, and in the project tool of iwork, the baseline update requirement, task and bug state are automatically changed to the integration state, and the code submission record URL link is written back to the iwork comment, the version number is written to the repair version field, realizing the real-time association of the version number and the development process.

[0141] When the version number is updated, the module automatically performs compliance verification, including:

[0142] Format verification: verify whether the major version number is a 3-digit non-negative integer, whether the minor version number is a 2-digit fixed length, and whether the integration frequency is a 3-digit fixed length, and automatically fill in “0” if the number of digits is insufficient;

[0143] Logical verification: verify whether the major version number increment conforms to the product stage iteration sequence, and whether the minor version number change matches the vehicle model / hardware information;

[0144] Abnormality processing: if the check fails (such as the major version number overflow 3 bits, the minor version number field is invalid), immediately suspend the update process, and push the abnormality alarm to the project management tool (such as iwork), including error type, current version number, trigger signal and other information, so as to facilitate the developer to quickly troubleshoot.

[0145] By the technical scheme, since the generation and update of the version number are completely completed automatically by the system, manual intervention is reduced, so that errors that may occur in manual operation are avoided, and the accuracy of the version number is ensured; meanwhile, the version number is automatically updated along with the development process, without additional manual operation and information transmission, so that the version update speed is accelerated, and the development efficiency is improved; and the version number is associated with information in each development tool, so that tracing the historical version becomes quick and accurate, and beneficial effects are achieved.

[0146] Figure 4 is an electronic device structure block diagram of a vehicle machine intelligent cockpit software version number integration method provided by one or more embodiments of the present application.

[0147] As shown in Figure 4 , the present application provides an electronic device, comprising: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;

[0148] The memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of a vehicle machine intelligent cockpit software version number integration method.

[0149] The present application also provides a computer readable storage medium storing a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of a vehicle machine intelligent cockpit software version number integration method.

[0150] For the method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the embodiments of the present application are not limited by the action order described, because according to the embodiments of the present application, certain steps can be performed in other order or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions involved are not necessarily necessary for the embodiments of the present application.

[0151] Those skilled in the art can clearly understand the application by the description of the above embodiments that the application can be implemented by means of software and the necessary universal hardware platform. Based on such understanding, the technical solutions of the application can be embodied in the form of a software product, which can be stored in a storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, and the like, and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, and the like) execute the methods described in each of the embodiments or some parts of the embodiments of the application.

[0152] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the application, rather than limit them; although the application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the application.

Claims

1. A vehicle machine intelligent cockpit software version number integration system, characterized in that, The version number rule definition module, the triggering mechanism module, the self-increment execution module, and the integration module are included. The version number rule definition module is configured to set the constituting rule of the OS baseline software version number of the intelligent cockpit of the vehicle. The version number includes a major version number, a minor version number, and an integration frequency. The triggering mechanism module is configured to determine the triggering condition of the version number self-increment, and trigger the standardized basic task as a benchmark through an automatic server tool. When the baseline has code updates, receives product stage update instructions, or obtains changes in vehicle type and hardware device information, the self-increment signal of the major version number, the minor version number, or the integration frequency is triggered. The self-increment execution module is configured to receive the signal of the triggering mechanism module and update the version number according to a preset rule. The integration module is configured to integrate the updated version number into an image package and link with the development tool chain of the OS baseline software of the intelligent cockpit of the vehicle. The development tool chain includes a code repository, an automated testing tool, and a project management tool. The constituting rule of the version number further includes a version number format rule. 2.The system of claim 1, wherein, Specifically, the major version number, the minor version number, and the integration frequency. The major version number is used to identify the product stage; the minor version number is two fixed lengths, the first bit identifies the vehicle type, the second bit identifies the hardware device stage, and the three bits after the decimal point identify the integration frequency. The triggering mechanism module is further configured to, when the self-increment signal of the major version number, the minor version number, or the integration frequency is triggered, synchronously push a triggering reason notification to the project management tool in the development tool chain. 3.The system of claim 1, wherein, The triggering reason notification includes a triggering event type and corresponding change content summary. The triggering event type includes code updates, product stage updates, vehicle type and hardware device changes. The self-increment execution module performs compliance verification on the updated version number after updating the version number according to the preset rule.

4. The system according to claim 1, wherein, The compliance verification includes verifying whether the major version number is a non-negative integer, whether the minor version number conforms to the preset format, and whether the integration frequency conforms to the preset format. If the verification fails, an abnormal version number alarm is pushed to the project management tool and the version number integration process is suspended. The integration module, when integrating the updated version number into the image package, retrieves the latest code submission record of the current baseline software from the code repository, and stores the code submission record in association with the updated version number in the version specification document of the image package.

5. The system according to claim 1, wherein the system further comprises a software version number integration module. The version specification document is distributed synchronously with the image package. The version number rule definition module receives version number rule adjustment instructions initiated by the development end through the project management tool in the development tool chain.

6. The system according to claim 1, wherein the system further comprises a software version number integration module. The version number rule adjustment instructions include major version number triggering condition modification, minor version number bit adjustment, and integration frequency count starting value change. If the rule is adjusted, the version number rule definition module synchronously updates the adjusted rule to the self-increment execution module. The linkage of the integration module and the automated testing tool further includes automatically triggering the automated testing tool to perform version compatibility testing on the image package after integrating the updated version number into the image package.

7. The system according to claim 1, wherein the system further comprises a software version number integration module. The version compatibility testing includes image package adaptation testing with the current vehicle type hardware driver and compatibility testing with historical version software data interaction. ​ If the test is passed, a test report is generated and the image package is marked as a release state; If the test fails, the failure item is fed back to the project management tool and the corresponding version number record is associated.

8. A method for integrating a software version number of an intelligent cockpit of a vehicle machine, characterized in that, Comprise: The composition rule of the baseline software version number of the intelligent cockpit OS of the vehicle machine is acquired; The version number comprises a major version number, a minor version number and an integration times; When the baseline has code updates, receives product stage update instructions or acquires vehicle type and hardware device information changes, a self-increment signal of the major version number, the minor version number or the integration times is triggered correspondingly; According to the self-increment signal, the version number is updated according to a preset rule; The updated version number is integrated into the image package and is linked with the development tool chain of the baseline software of the intelligent cockpit OS of the vehicle machine.

9. An electronic device, comprising: Comprise: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus; The memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the vehicle machine intelligent cockpit software version number integration method in claim 8.

10. A computer-readable storage medium, characterized in that, The memory stores a computer program executable by the electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the vehicle machine intelligent cockpit software version number integration method in claim 8.

Images