BOM-based automobile software license management method and related product

Abstract

The invention discloses an automobile software license management method based on BOM and a related product, and relates to the technical field of software management, the method comprises the following steps: obtaining a list template of an automobile software license, and determining key information of the automobile software license based on the list template; obtaining a target list of the automobile software license according to the key information; under the condition that the target list is valid, constructing the automobile software license in a bill of material (BOM) system based on the target list; and the automobile software license is managed in the BOM system. According to the BOM-based automobile software license management method provided by the invention, the automobile software license is associated with the automobile type based on the BOM system, so that online management of the automobile software license is realized.

Description

Technical Field

[0001] The present application relates to the technical field of software management, and in particular to a BOM-based automotive software license management method and related products. Background Art

[0002] As the automotive industry develops towards intelligence, networking and electrification, software plays an increasingly important role in automobiles. Modern cars contain a large number of software systems, such as autonomous driving software, in-vehicle infotainment system software, vehicle control system software, etc. The functional realization and legal use of these software depend on effective automotive software license management (i.e. license management). For example, poor management of software licenses for autonomous driving functions may result in the inability to use the functions normally, or unauthorized use, affecting driving safety and the legal liability of the company. Defining cars through software means that the differentiation of cars is increasingly reflected in software functions. Automakers need to ensure that they have legal software resources through strict license management to develop competitive software functions, such as advanced driver assistance systems, smart cockpit interaction functions, etc., thereby enhancing the market competitiveness of automotive products.

[0003] At present, software-defined cars are developing rapidly, and the number of licenses is growing exponentially. Therefore, the main way to manage licenses is to set up a license management team, manually manage the license list offline, check it regularly, and determine the settlement amount based on the configuration and number of vehicles offline. However, the number of licenses is increasing with the increase of software and functions, and it is impossible to manage licenses by relying solely on the offline license management team.

[0004] Therefore, how to manage licenses online has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] A series of simplified concepts are introduced in the Summary of the Invention section, which will be further described in detail in the Detailed Description of the Invention section. The Summary of the Invention section of this application does not mean to attempt to define the key features and essential technical features of the claimed technical solution, nor does it mean to attempt to determine the scope of protection of the claimed technical solution.

[0006] In a first aspect, the present application proposes a BOM-based automotive software license management method, comprising:

[0007] Obtaining a manifest template for an automobile software license, and determining key information of the automobile software license based on the manifest template;

[0008] Obtaining a target list of the automotive software licenses based on the key information;

[0009] If the target list is valid, constructing the automotive software license in a BOM system based on the target list;

[0010] The automotive software license is managed in the BOM system.

[0011] In a feasible implementation manner, the key information includes the type of automobile software license, the number of automobile software licenses, the settlement method of the automobile software license, the configuration of the automobile software license, and the effective time of the automobile software license.

[0012] In a feasible implementation manner, managing the automotive software license in the BOM system includes:

[0013] In response to the automobile financial settlement instruction, determining the type and quantity of the automobile software license of the target automobile in the BOM system according to the actual configuration and quantity of the target automobile;

[0014] The amount of the target vehicle is determined according to the type of the vehicle software license and the number of the vehicle software licenses of the target vehicle.

[0015] In a feasible implementation, it also includes:

[0016] When the number of the automotive software licenses changes, the BOM system is updated based on a preset change process.

[0017] In a feasible implementation manner, after obtaining the target list of the automotive software license, the method further includes:

[0018] In response to the automotive software license review instruction, if the content in the target list meets the preset requirements, establish a countersigning process for the target list;

[0019] In response to a confirmation instruction sent by the user based on the countersigning process, the target list is determined to be valid.

[0020] In a feasible implementation manner, the managing the automotive software license in the BOM system further includes:

[0021] Performing identification and attribute setting on the automotive software license in the BOM system;

[0022] The automobile software license is managed according to the identification and attributes of the automobile software license.

[0023] In a feasible implementation, the identification setting includes at least one of a code setting, a symbol setting, and a color identification setting; the attribute setting includes at least one of an authorization type attribute, an applicable vehicle model attribute, a software function attribute, a supplier information attribute, and an update requirement attribute.

[0024] In a second aspect, the present application proposes a BOM-based automobile software license management system, which is applied to the BOM-based automobile software license management method described in any of the above embodiments, including:

[0025] A confirmation module, used to obtain a list template of the automobile software license and determine key information of the automobile software license based on the list template;

[0026] An acquisition module, configured to obtain a target list of the automotive software licenses according to the key information;

[0027] A construction module, configured to construct the automotive software license in a BOM system based on the target list if the target list is valid;

[0028] A management module is used to manage the automotive software license in the BOM system.

[0029] In a third aspect, an electronic device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is used to implement the steps of the BOM-based automotive software license management method of any one of the first aspects described above when executing the computer program stored in the memory.

[0030] In a fourth aspect, the present application further proposes a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the BOM-based automotive software license management method of any one of the first aspects is implemented.

[0031] In summary, the BOM-based automotive software license management method proposed in this application determines the key information of the automotive software license through the list template. When the target list is valid, the automotive software license is constructed in the BOM system based on the target list. Finally, the automotive software license is managed in the BOM system to ensure the accurate application and effective tracking of the automotive software license during the production and use of the automobile.

[0032] The BOM-based automotive software license management method proposed in this application and other advantages, objectives and features of this application will be partially reflected through the following description, and will also be partially understood by technical personnel in this field through research and practice of this application. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present specification. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0034] Figure 1 A schematic diagram of a process of managing a BOM-based automotive software license according to an embodiment of the present application;

[0035] Figure 2 A management schematic diagram of a BOM-based automotive software license management method provided in an embodiment of the present application;

[0036] Figure 3 A functional module diagram of a BOM-based automotive software license management system provided in an embodiment of the present application;

[0037] Figure 4 A schematic diagram of the structure of an electronic device for BOM-based automotive software license management provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to better understand the technical solutions provided by the embodiments of this specification, the technical solutions of the embodiments of this specification are described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.

[0039] In this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of more restrictions, the elements limited by the statement "comprise one..." do not exclude the existence of other identical elements in the process, method, article or equipment including the elements. The term "more than two" includes two or more than two situations.

[0040] See also Figure 1 , which is a flow chart of a BOM-based automotive software license management method provided in an embodiment of the present application, which may specifically include:

[0041] S110: Obtain a list template of the automobile software license, and determine key information of the automobile software license based on the list template.

[0042] S120. Obtain a target list of automotive software licenses based on the key information.

[0043] S130 . When the target list is valid, construct an automotive software license in the BOM system based on the target list.

[0044] S140. Manage automotive software licenses in the BOM system.

[0045] Exemplarily, the list template of the automotive software license is a standardized format for recording and managing key license information, and the key license information is determined by the list template. When the target list is valid, the automotive software license is constructed in the BOM system based on the target list. Finally, the automotive software license is managed in the BOM system to ensure the accurate application and effective tracking of the automotive software license during the production and use of the vehicle.

[0046] In some examples, the key information includes the type of automotive software license, the number of automotive software licenses, the settlement method of the automotive software license, the configuration of the automotive software license, and the effective time of the automotive software license.

[0047] For example, the key information in the license includes: the type of license, that is, what type of authorization license it is; the number of licenses, that is, how many specific licenses there are; the settlement method of the license, such as one-time payment, pay-per-use, etc.; the configuration requirements of the license, that is, which system or product configuration the license is applicable to; and the effective time of the license, that is, when the license takes effect.

[0048] In some examples, automobile software licenses are managed in a BOM system, including: in response to an automobile financial settlement instruction, determining the type of automobile software licenses and the number of automobile software licenses for a target automobile in the BOM system according to the actual configuration and quantity of the target automobile; and determining the amount of the target automobile according to the type of automobile software licenses and the number of automobile software licenses for the target automobile.

[0049] For example, when receiving a car financial settlement instruction, the exact license type and quantity are determined based on the actual configuration and quantity of the target car when it comes off the production line. This is because the actual configuration of the vehicle when it comes off the production line will determine which licenses are required, and the quantity corresponds to the specific number of licenses required. Then the amount of the target car is determined based on the license type and quantity.

[0050] In some examples, the BOM-based automotive software license management method may further include: when the number of automotive software licenses changes, updating the BOM system based on a preset change process.

[0051] For example, if the number of licenses increases or decreases, the BOM system needs to be updated according to the preset change process. This means that when the license situation changes, the BOM system needs to be adjusted and updated accordingly according to the specific change management process to ensure that the BOM system always accurately reflects the actual material and license requirements.

[0052] In some examples, after obtaining the target list of automotive software licenses, the BOM-based automotive software license management method may also include: responding to an automotive software license review instruction, and establishing a co-signing process for the target list when the content in the target list meets preset requirements; responding to a confirmation instruction sent by the user based on the co-signing process, determining that the target list is valid.

[0053] For example, when the automotive software license review instruction is received, the review process begins in the BOM system. During the review process, the content in the target list is reviewed and evaluated based on R&D, procurement, finance, materials, etc. to ensure the accuracy, rationality and feasibility of its content. After the review, a countersigning process is established for the target list, and in the countersigning process, the target list is uniformly confirmed based on R&D, procurement, finance, materials, etc. to make it effective.

[0054] In some examples, managing the automotive software license in the BOM system may also include: setting an identification and attributes of the automotive software license in the BOM system; and managing the automotive software license according to the identification and attributes of the automotive software license.

[0055] Exemplarily, setting the identification and attributes of the license can facilitate the management and tracking of the license in the BOM system.

[0056] In some examples, the identification setting includes at least one of a code setting, a symbol setting, and a color identification setting; the attribute setting includes at least one of an authorization type attribute, an applicable vehicle model attribute, a software function attribute, a supplier information attribute, and an update requirement attribute.

[0057] For example, the code or symbol setting can assign a unique code or symbol to the automotive software license, for example, starting with a specific letter combination, such as "SL_" (abbreviation of Software License), so that the BOM system can recognize at a glance that this is a software license rather than a physical part. The color identification setting can be to use a specific color to highlight the automotive software license in the display interface of the BOM system. For example, general automotive parts are displayed in white, while automotive software licenses can be displayed in blue, so that they can be quickly distinguished when viewing the BOM system.

[0058] Furthermore, the attribute settings include: Authorization type attribute, that is, to clarify the authorization type of the automotive software license, such as permanent authorization, time-limited authorization, authorization by number of uses, etc. This helps to understand the validity period and restrictions of different licenses during the management process. Applicable vehicle model attribute, that is, to mark which specific vehicle models or configurations the automotive software license applies to. For example, some licenses may only apply to specific configurations of high-end models, while others may apply to multiple vehicle series. Software function attribute, that is, to explain the automotive software function corresponding to the license, such as autonomous driving function license, smart cockpit interaction function license, etc. This helps to accurately match the license with the corresponding software function during the automobile production process. Supplier information attribute, that is, to record the name, contact information and other information of the supplier who provides the automotive software license. This is very important for communicating with suppliers and managing supplier relationships when problems arise. Update requirement attribute, that is, if the automotive software license needs to be updated regularly, the update requirement attribute can be set, including update frequency, update method (automatic update or manual update), etc. This helps to ensure that the automotive software is always up to date and is also convenient for arranging update plans.

[0059] In summary, in the BOM-based automotive software license management method proposed in this application, the BOM system is used to manage the license. The license can be directly associated with the vehicle model through the BOM system. The accurate license list can be directly screened out in the BOM system through offline vehicle models. When the user changes the process, the BOM system can also update the content of the license list in a timely and accurate manner.

[0060] like Figure 2 As shown, the technical solution of the present application is further described in detail below through specific embodiments.

[0061] BOM engineers provide the license list template, and R&D engineers and procurement engineers maintain the license list content and determine the license type, quantity, settlement method, configuration, and effective time. BOM engineers organize R&D, procurement, finance, and materials to review the license list. The reviewed license list is submitted to the platform for a joint signing process and is signed by all relevant parties to take effect. BOM engineers maintain the license in the BOM system based on the license list and maintain the corresponding attributes to distinguish licenses from general parts. During financial settlement, the configuration and quantity of the vehicle offline are used to determine the accurate license type and quantity, and payment is made to the supplier accordingly.

[0062] It can be seen that the above specific embodiments can first present a clear cost structure display, that is, after incorporating license management into BOM, the proportion of each license in the product cost can be clearly determined. Automobile companies can intuitively see how the license costs are allocated to each vehicle, just like managing hardware components. For example, the cost of the in-vehicle infotainment system license for a model can be clearly calculated through the BOM system, which helps companies to accurately grasp the cost structure of the product and avoid ambiguity in cost accounting. Secondly, flexible product configuration adjustment is achieved, that is, automotive products often have multiple configuration options, among which software functions are important differentiating factors. Incorporating license management into BOM allows companies to better adjust product configurations according to market demand and customer preferences. Finally, the reduction of labor costs is achieved, that is, after incorporating license management into BOM, the license update is the responsibility of the responsible engineer, which greatly reduces the cost of labor verification.

[0063] It should be noted that the above embodiments are only the best examples and are not limitations on the implementation methods of the present application.

[0064] Based on the same application concept, the embodiments of the present application also provide a BOM-based automobile software license management system corresponding to the BOM-based automobile software license management method provided in the above embodiments. Since the principle of solving the problem by the BOM-based automobile software license management system in the embodiments of the present application is similar to the BOM-based automobile software license management method in the above embodiments of the present application, the implementation of the BOM-based automobile software license management system can refer to the implementation of the BOM-based automobile software license management method, and the repeated parts will not be repeated.

[0065] like Figure 3 As shown, Figure 3 A functional module diagram of a BOM-based automotive software license management system provided in this application, the BOM-based automotive software license management system may include:

[0066] A confirmation module 21 is used to obtain a list template of the automobile software license and determine key information of the automobile software license based on the list template;

[0067] An acquisition module 22, used to obtain a target list of automobile software licenses based on the key information;

[0068] A construction module 23, configured to construct the automotive software license in the BOM system based on the target list if the target list is valid;

[0069] The management module 24 is used to manage the automobile software license in the BOM system.

[0070] Exemplarily, the key information of the license is determined by the confirmation module 21, and then the target list of the automobile software license is obtained according to the key information in the acquisition module 22. If the target list is valid, the construction module 23 constructs the automobile software license in the BOM system based on the target list. Finally, the automobile software license is managed in the BOM system by the management module 24 to ensure the accurate application and effective tracking of the automobile software license during the production and use of the automobile.

[0071] In summary, the BOM-based automotive software license management system provided by this application uses the BOM system to manage licenses. Licenses can be directly associated with vehicle models through the BOM system, and accurate license lists can be directly screened out in the BOM system through offline vehicle models. When users change the process, the BOM system can also update the contents of the license list in a timely and accurate manner.

[0072] like Figure 4 As shown, based on the same application concept, an embodiment of the present application also provides an electronic device 300, including a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor, and when the processor 320 executes the computer program 311, it implements the steps of any of the above-mentioned methods of BOM-based automotive software license management.

[0073] Since the electronic device introduced in this embodiment is a device used to implement a BOM-based automotive software license management method in the embodiment of the present application, based on the method introduced in the embodiment of the present application, technical personnel in this field can understand the specific implementation method of the electronic device of this embodiment and its various variations. Therefore, how the electronic device implements the method in the embodiment of the present application is not introduced in detail here. As long as the equipment used by technical personnel in this field to implement the method in the embodiment of the present application is within the scope of protection of this application.

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

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

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

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

[0078] An embodiment of the present application also provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device executes the process of the BOM-based automotive software license management method in the corresponding embodiment.

[0079] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

[0080] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0081] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0082] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0083] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

[0084] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program codes.

[0085] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A BOM-based automotive software license management method, characterized in that: include: Obtaining a manifest template for an automobile software license, and determining key information of the automobile software license based on the manifest template; Obtaining a target list of the automotive software licenses based on the key information; If the target list is valid, constructing the automotive software license in a bill of materials (BOM) system based on the target list; The automotive software license is managed in the BOM system.

2. The BOM-based automotive software license management method according to claim 1, characterized in that: The key information includes the type of automobile software license, the number of automobile software licenses, the settlement method of the automobile software license, the configuration of the automobile software license and the effective time of the automobile software license.

3. The BOM-based automotive software license management method according to claim 2, characterized in that: The managing the automotive software license in the BOM system includes: In response to the automobile financial settlement instruction, determining the type and quantity of the automobile software license of the target automobile in the BOM system according to the actual configuration and quantity of the target automobile; The amount of the target vehicle is determined according to the type of the vehicle software license and the number of the vehicle software licenses of the target vehicle.

4. The BOM-based automotive software license management method according to claim 2, characterized in that: Also includes: When the number of the automotive software licenses changes, the BOM system is updated based on a preset change process.

5. The BOM-based automotive software license management method according to claim 1, characterized in that: After obtaining the target list of vehicle software licenses, the method further includes: In response to the automotive software license review instruction, if the content in the target list meets the preset requirements, establish a countersigning process for the target list; In response to a confirmation instruction sent by the user based on the countersigning process, the target list is determined to be valid.

6. The BOM-based automotive software license management method according to claim 1, characterized in that: The managing the automotive software license in the BOM system further includes: Performing identification and attribute setting on the automotive software license in the BOM system; The automobile software license is managed according to the identification and attributes of the automobile software license.

7. The BOM-based automobile software license management method according to claim 6, characterized in that: The identification setting includes at least one of a code setting, a symbol setting and a color identification setting; the attribute setting includes at least one of an authorization type attribute, an applicable vehicle model attribute, a software function attribute, a supplier information attribute and an update requirement attribute.

8. A BOM-based automobile software license management system, applied to the BOM-based automobile software license management method according to any one of claims 1 to 7, characterized in that: include: A confirmation module, used to obtain a list template of the automobile software license and determine key information of the automobile software license based on the list template; An acquisition module, configured to obtain a target list of the automotive software licenses according to the key information; A construction module, configured to construct the automotive software license in a BOM system based on the target list if the target list is valid; A management module is used to manage the automotive software license in the BOM system.

9. An electronic device, comprising: A memory and a processor, wherein the processor is used to implement the steps of the BOM-based automotive software license management method as described in any one of claims 1 to 7 when executing the computer program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the BOM-based automotive software license management method according to any one of claims 1 to 7 are implemented.

Images