Controller software and hardware matching relation management method and device, equipment and storage medium

Abstract

The invention discloses a controller software and hardware matching relationship management method and device, equipment and a storage medium. The method comprises the following steps of: constructing a chunk corresponding to each technical scheme under the same functional group; for each block, determining a controller assembly contained in the block; for each controller assembly, the structural relationship between the controller software and the controller assembly is set, and the structural relationship is a parallel type or a hanging type; and according to the structural relationship, establishing an association relationship between the controller software and the controller hardware. According to the method and the device, the incidence relation between the controller software and the controller hardware is automatically established based on the structural relation between the controller software and the controller assembly, most manual operation is omitted, the accuracy of the matching relation between the controller software and the controller hardware is ensured, and the efficiency of establishing the matching relation between the controller software and the controller hardware is also improved.

Description

Technical Field

[0001] The present application relates to the field of data management technology, and in particular to a controller software and hardware matching relationship management method, device, equipment and computer-readable storage medium. Background Art

[0002] As the degree of automotive electronics continues to increase and consumer demands become increasingly diverse, more and more controllers are involved. Controllers need to be used with controller software. When there are a large number of controllers and controller software, how to accurately and efficiently match the corresponding controller software for each controller is a technical problem that needs to be solved urgently. Summary of the invention

[0003] In order to solve the above technical problems, the present application provides a controller software and hardware matching relationship management method, device, equipment and computer-readable storage medium.

[0004] In a first aspect, an embodiment of the present application provides a method for managing a controller software and hardware matching relationship, the method comprising:

[0005] Construct the corresponding blocks for each technical solution under the same functional grouping;

[0006] For each block, determine the controller assembly included in the block;

[0007] For each controller assembly, set the structural relationship between the controller software and the controller assembly, and the structural relationship is parallel or under-hung;

[0008] Based on the structural relationship, an association relationship between the controller software and the controller hardware is established.

[0009] In combination with the first aspect, in one implementation, the structural relationship between the controller software and the controller assembly is set to include:

[0010] If the flashing operation execution location of the controller software is the target location, the structural relationship between the controller software and the controller assembly is set to be parallel;

[0011] If the flashing operation of the controller software is performed at a non-target location, the structural relationship between the controller software and the controller assembly is set to a down-hanging type.

[0012] In combination with the first aspect, in one implementation, establishing an association relationship between the controller software and the controller hardware according to the structural relationship includes:

[0013] If the structural relationship between the controller software and the controller assembly is a down-hanging type, the part number of the controller software and the part number of the controller hardware are associated.

[0014] In combination with the first aspect, in one implementation, establishing an association relationship between the controller software and the controller hardware according to the structural relationship includes:

[0015] If there is only one set of controller software and controller assembly in a parallel structural relationship, the part number of the controller software and the part number of the controller hardware are associated.

[0016] In combination with the first aspect, in one implementation, establishing an association relationship between the controller software and the controller hardware according to the structural relationship includes:

[0017] If there are more than one set of controller software and controller assembly in a parallel structural relationship, the part number of each controller software and the part number of its corresponding controller hardware are associated based on the specified operation.

[0018] In a second aspect, an embodiment of the present application provides a controller software and hardware matching relationship management device, the controller software and hardware matching relationship management device comprising:

[0019] Building modules are used to build blocks corresponding to each technical solution under the same functional grouping;

[0020] A determination module, used for determining, for each block, a controller assembly included in the block;

[0021] A setting module is used to set the structural relationship between the controller software and the controller assembly for each controller assembly, and the structural relationship is parallel or under-hung;

[0022] The association module is used to establish an association relationship between the controller software and the controller hardware according to the structural relationship.

[0023] In conjunction with the second aspect, in one implementation, a module is provided for:

[0024] If the flashing operation execution location of the controller software is the target location, the structural relationship between the controller software and the controller assembly is set to be parallel;

[0025] If the flashing operation of the controller software is performed at a non-target location, the structural relationship between the controller software and the controller assembly is set to a down-hanging type.

[0026] In conjunction with the second aspect, in one implementation, the association module is used to:

[0027] If the structural relationship between the controller software and the controller assembly is a down-hung type, the part number of the controller software and the part number of the controller hardware are associated;

[0028] If there is only one set of controller software and controller assembly in a parallel structural relationship, the part number of the controller software and the part number of the controller hardware are associated;

[0029] If there are more than one set of controller software and controller assembly in a parallel structural relationship, the part number of each controller software and the part number of its corresponding controller hardware are associated based on the specified operation.

[0030] In a third aspect, an embodiment of the present application provides a controller software and hardware matching relationship management device, wherein the controller software and hardware matching relationship management device comprises a processor, a memory, and a controller software and hardware matching relationship management program stored in the memory and executable by the processor, wherein when the controller software and hardware matching relationship management program is executed by the processor, the steps of the controller software and hardware matching relationship management method described in the first aspect are implemented.

[0031] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a controller software and hardware matching relationship management program is stored. When the controller software and hardware matching relationship management program is executed by a processor, the steps of the controller software and hardware matching relationship management method described in the first aspect are implemented.

[0032] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0033] In the embodiment of the present application, the corresponding blocks of each technical solution are constructed under the same functional grouping; for each block, the controller assembly contained in the block is determined; for each controller assembly, the structural relationship between the controller software and the controller assembly is set, and the structural relationship is parallel or hanging; according to the structural relationship, the association relationship between the controller software and the controller hardware is established. Through the embodiment of the present application, the association relationship between the controller software and the controller hardware is automatically established based on the structural relationship between the controller software and the controller assembly, which saves most of the manual operations, ensures the accuracy of the controller software and hardware matching relationship, and improves the efficiency of establishing the controller software and hardware matching relationship. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 This is a flow chart of an embodiment of a method for managing software and hardware matching relationships of a controller of the present application;

[0035] Figure 2 This is a schematic diagram of the structural relationship in an embodiment of the controller software and hardware matching relationship management method of this application;

[0036] Figure 3 This is a schematic diagram of the structural relationship in another embodiment of the controller software and hardware matching relationship management method of the present application;

[0037] Figure 4 This is a schematic diagram of the structural relationship in another embodiment of the controller software and hardware matching relationship management method of the present application;

[0038] Figure 5 This is a schematic diagram of the structural relationship in another embodiment of the controller software and hardware matching relationship management method of the present application;

[0039] Figure 6 This is a functional module diagram of an embodiment of a device for managing software and hardware matching relationships of a controller of the present application;

[0040] Figure 7 This is a schematic diagram of the hardware structure of a controller software and hardware matching relationship management device involved in the embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0043] In a first aspect, an embodiment of the present application provides a method for managing the software and hardware matching relationship of a controller.

[0044] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of an embodiment of the controller software and hardware matching relationship management method of this application. Figure 1 As shown, the controller software and hardware matching relationship management method includes:

[0045] Step S10, constructing a block corresponding to each technical solution under the same functional grouping;

[0046] In this embodiment, for the same functional grouping, there may be different technical solutions, and each technical solution has a corresponding block. For example, if there are three different technical solutions for the same functional grouping, three blocks corresponding to the three technical solutions can be constructed under the functional grouping. Taking the central control display function as an example, the technical solutions corresponding to the central control display function include:

[0047] Technical solution 1: 13.2-inch capacitive screen + touch control;

[0048] Technical solution 2: 14.6-inch capacitive screen + touch control;

[0049] Technical solution 3: 15.6-inch 2K capacitive screen + touch control.

[0050] For each technical solution, the required equipment (which may also include other parts, such as software, fixtures, brackets, etc.) serves as the corresponding block that constitutes the technical solution.

[0051] Step S20, for each block, determining the controller assembly included in the block;

[0052] In this embodiment, the controller assembly included in each block depends on the actual situation and is not limited here.

[0053] Step S30, for each controller assembly, setting the structural relationship between the controller software and the controller assembly, the structural relationship being a parallel type or a down-hung type;

[0054] In this embodiment, refer to Figure 2 , Figure 2 This is a schematic diagram of the structural relationship in an embodiment of the controller software and hardware matching relationship management method of this application. Figure 2 As shown, the controller software 1 and the controller assembly 1 belong to the same level under the block, that is, the structural relationship between the controller software 1 and the controller assembly 1 is parallel; the controller software 2 is hung under the controller assembly 2, that is, the structural relationship between the controller software 2 and the controller assembly 2 is hanging.

[0055] Further, in one embodiment, setting the structural relationship between the controller software and the controller assembly includes:

[0056] If the flashing operation execution location of the controller software is the target location, the structural relationship between the controller software and the controller assembly is set to be parallel;

[0057] If the flashing operation of the controller software is performed at a non-target location, the structural relationship between the controller software and the controller assembly is set to a down-hanging type.

[0058] In this embodiment, for the controller software corresponding to each controller assembly, its data structure is divided into parallel type and down-hung type according to whether it is flashed in the final assembly factory. That is, if the flashing operation of the controller software is performed in the final assembly factory, its structural relationship with the controller assembly is parallel type; if the flashing operation of the controller software is not performed in the final assembly factory, its structural relationship with the controller assembly is down-hung type.

[0059] The controller software flashed in the final assembly plant must be defined as parallel type. If it is defined as down-hung type, the flashed software will be missing, and the vehicle will not be able to flash the software, resulting in a shutdown. At the same time, the software not flashed in the final assembly plant should be defined as down-hung type. If it is defined as parallel type, it will not affect production, but it will cause data redundancy and increase management costs.

[0060] In this way, it is easy to distinguish which controller software needs to be flashed in the final assembly factory and which controller software does not need to be flashed in the final assembly factory.

[0061] Step S40: establishing an association relationship between the controller software and the controller hardware according to the structural relationship.

[0062] In this embodiment, for the execution subject of this embodiment, after determining the structural relationship between each controller assembly and the controller software, the association relationship between the controller software and the controller hardware can be established based on the structural relationship, thereby reducing most of the manual operations.

[0063] Furthermore, in one embodiment, step S40 includes:

[0064] If the structural relationship between the controller software and the controller assembly is a down-hanging type, the part number of the controller software and the part number of the controller hardware are associated.

[0065] In this embodiment, refer to Figure 3 , Figure 3 This is a schematic diagram of the structural relationship in another embodiment of the controller software and hardware matching relationship management method of this application. Figure 3 As shown, the execution subject of this embodiment detects that the structural relationship between the controller assembly 1 and the controller software 1 is a down-hanging type, and then automatically associates the controller hardware 1 with the controller software 1, and specifically, the part number of the controller software 1 and the part number of the controller hardware 1 are associated. Similarly, if it is detected that the structural relationship between the controller assembly 2 and the controller software 2 is a down-hanging type, the controller hardware 2 and the controller software 2 are automatically associated, and specifically, the part number of the controller software 2 and the part number of the controller hardware 2 are associated.

[0066] It should be noted that the association action in this embodiment is performed based on a downward-hanging structural relationship, that is, the association relationship is not affected by changes in the part number of the controller software and / or the part number of the controller hardware. That is, if the part number of the controller software changes, the association relationship changes synchronously; if the part number of the controller hardware changes, the association relationship changes synchronously.

[0067] Furthermore, in one embodiment, step S40 includes:

[0068] If there is only one set of controller software and controller assembly in a parallel structural relationship, the part number of the controller software and the part number of the controller hardware are associated.

[0069] In this embodiment, refer to Figure 4 , Figure 4 This is a schematic diagram of the structural relationship in another embodiment of the controller software and hardware matching relationship management method of this application. Figure 4 As shown, when the execution subject of this embodiment detects that there is only one set of controller software and controller assembly in a parallel structural relationship under the group block, the controller software is automatically associated with the controller hardware. Specifically, the part number of the controller software and the part number of the controller hardware can be associated.

[0070] It should be noted that if there is only one set of controller software and controller assembly in a parallel structural relationship, the association relationship will not be affected by changes in the part number of the controller software and / or the part number of the controller hardware, that is, if the part number of the controller software changes, the association relationship will change synchronously; if the part number of the controller hardware changes, the association relationship will change synchronously.

[0071] Furthermore, in one embodiment, step S40 includes:

[0072] If there are more than one set of controller software and controller assembly in a parallel structural relationship, the part number of each controller software and the part number of its corresponding controller hardware are associated based on the specified operation.

[0073] In this embodiment, refer to Figure 5 , Figure 5 This is a schematic diagram of the structural relationship in another embodiment of the controller software and hardware matching relationship management method of this application. Figure 5 As shown, the controller assembly 1 and the controller software 1, and the controller assembly 2 and the controller software 2 are all in a parallel structural relationship. In this case, the system cannot automatically determine which controller hardware is associated with the controller software, and human intervention is required. That is, through the human-specified method, for the execution subject, in response to the specified operation, the association relationship between the controller software and the controller hardware is determined. For example, if the controller software 1 is manually specified to be associated with the controller hardware 1, and the controller software 2 is manually specified to be associated with the controller hardware 2, the execution subject will associate the part number of the controller software 1 with the part number of the corresponding controller hardware 1, and the part number of the controller software 2 with the part number of the corresponding controller hardware 2.

[0074] In the embodiment of the present application, the corresponding blocks of each technical solution are constructed under the same functional grouping; for each block, the controller assembly contained in the block is determined; for each controller assembly, the structural relationship between the controller software and the controller assembly is set, and the structural relationship is parallel or hanging; according to the structural relationship, the association relationship between the controller software and the controller hardware is established. Through the embodiment of the present application, the association relationship between the controller software and the controller hardware is automatically established based on the structural relationship between the controller software and the controller assembly, which saves most of the manual operations, ensures the accuracy of the controller software and hardware matching relationship, and improves the efficiency of establishing the controller software and hardware matching relationship.

[0075] Furthermore, after step S40, the method further includes:

[0076] For each block, the relationship between the controller hardware and the controller software with a parallel structure is verified, and the verification result is prompted. Specifically:

[0077] When the controller software is not associated with the controller hardware or the controller software has evolved and changed, the system prompts "Software is not associated with hardware". At this time, the controller software needs to be associated with the corresponding controller hardware;

[0078] When the controller hardware evolves and changes its number, the system prompts "need to change the corresponding software association relationship". At this time, the controller hardware associated with the controller software of the controller hardware needs to be changed to the new controller hardware;

[0079] When the controller software and controller hardware are associated, the system prompts "The software has been associated with the hardware, please check the correspondence". At this time, you need to check whether the correspondence between the software and hardware is correct. If not, you need to re-associate.

[0080] In a second aspect, an embodiment of the present application also provides a controller software and hardware matching relationship management device.

[0081] In one embodiment, referring to Figure 6 , Figure 6 This is a functional module diagram of an embodiment of the controller software and hardware matching relationship management device of the present application. Figure 6 As shown, the controller software and hardware matching relationship management device includes:

[0082] A construction module 10 is used to construct a block corresponding to each technical solution under the same functional grouping;

[0083] A determination module 20, for determining, for each block, a controller assembly included in the block;

[0084] A setting module 30 is used to set the structural relationship between the controller software and the controller assembly for each controller assembly, and the structural relationship is a parallel type or a hanging type;

[0085] The association module 40 is used to establish an association relationship between the controller software and the controller hardware according to the structural relationship.

[0086] Furthermore, in one embodiment, a module 30 is provided for:

[0087] If the flashing operation execution location of the controller software is the target location, the structural relationship between the controller software and the controller assembly is set to be parallel;

[0088] If the flashing operation of the controller software is performed at a non-target location, the structural relationship between the controller software and the controller assembly is set to a down-hanging type.

[0089] Furthermore, in one embodiment, the association module 40 is used to:

[0090] If the structural relationship between the controller software and the controller assembly is a down-hung type, the part number of the controller software and the part number of the controller hardware are associated;

[0091] If there is only one set of controller software and controller assembly in a parallel structural relationship, the part number of the controller software and the part number of the controller hardware are associated;

[0092] If there are more than one set of controller software and controller assembly in a parallel structural relationship, the part number of each controller software and the part number of its corresponding controller hardware are associated based on the specified operation.

[0093] Among them, the functional implementation of each module in the above-mentioned controller software and hardware matching relationship management device corresponds to the various steps in the above-mentioned controller software and hardware matching relationship management method embodiment, and its functions and implementation processes are no longer repeated here.

[0094] In a third aspect, an embodiment of the present application provides a controller software and hardware matching relationship management device, which can be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0095] Reference Figure 7 , Figure 7 Schematic diagram of the hardware structure of the controller software and hardware matching relationship management device involved in the embodiment of the present application. In the embodiment of the present application, the controller software and hardware matching relationship management device may include a processor, a memory, a communication interface and a communication bus.

[0096] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0097] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the controller software and hardware matching relationship management device, and the interface used to realize the interconnection between the controller software and hardware matching relationship management device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display (Display), a keyboard (Keyboard), etc.

[0098] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0099] The processor may be a general-purpose processor, and the general-purpose processor may call the controller software and hardware matching relationship management program stored in the memory, and execute the controller software and hardware matching relationship management method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the controller software and hardware matching relationship management program is called may refer to the various embodiments of the controller software and hardware matching relationship management method of the present application, and will not be repeated here.

[0100] Those skilled in the art will understand that Figure 7 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0101] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0102] The computer-readable storage medium of the present application stores a controller software and hardware matching relationship management program, wherein when the controller software and hardware matching relationship management program is executed by a processor, the steps of the controller software and hardware matching relationship management method as described above are implemented.

[0103] Among them, the method implemented when the controller software and hardware matching relationship management program is executed can refer to the various embodiments of the controller software and hardware matching relationship management method of the present application, and will not be repeated here.

[0104] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0105] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0106] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0107] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0108] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0109] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0110] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A controller software and hardware matching relationship management method, characterized in that: The controller software and hardware matching relationship management method comprises: Construct the corresponding blocks for each technical solution under the same functional grouping; For each block, determine the controller assembly included in the block; For each controller assembly, set the structural relationship between the controller software and the controller assembly, and the structural relationship is parallel or under-hung; Based on the structural relationship, an association relationship between the controller software and the controller hardware is established.

2. The controller software and hardware matching relationship management method according to claim 1, characterized in that: The structural relationship between the controller software and the controller assembly includes: If the flashing operation execution location of the controller software is the target location, the structural relationship between the controller software and the controller assembly is set to be parallel; If the flashing operation of the controller software is performed at a non-target location, the structural relationship between the controller software and the controller assembly is set to a down-hanging type.

3. The controller software and hardware matching relationship management method according to claim 1, characterized in that: The establishing of the association relationship between the controller software and the controller hardware according to the structural relationship includes: If the structural relationship between the controller software and the controller assembly is a down-hanging type, the part number of the controller software and the part number of the controller hardware are associated.

4. The controller software and hardware matching relationship management method according to claim 1, characterized in that: The establishing of the association relationship between the controller software and the controller hardware according to the structural relationship includes: If there is only one set of controller software and controller assembly in a parallel structural relationship, the part number of the controller software and the part number of the controller hardware are associated.

5. The controller software and hardware matching relationship management method according to claim 1, characterized in that: The establishing of the association relationship between the controller software and the controller hardware according to the structural relationship includes: If there are more than one set of controller software and controller assembly in a parallel structural relationship, the part number of each controller software and the part number of its corresponding controller hardware are associated based on the specified operation.

6. A controller software and hardware matching relationship management device, characterized in that: The controller software and hardware matching relationship management device comprises: Building modules are used to build blocks corresponding to each technical solution under the same functional grouping; A determination module, used for determining, for each block, a controller assembly included in the block; A setting module is used to set the structural relationship between the controller software and the controller assembly for each controller assembly, and the structural relationship is parallel or under-hung; The association module is used to establish an association relationship between the controller software and the controller hardware according to the structural relationship.

7. The controller software and hardware matching relationship management device according to claim 6, characterized in that: Setup module for: If the flashing operation execution location of the controller software is the target location, the structural relationship between the controller software and the controller assembly is set to be parallel; If the flashing operation of the controller software is performed at a non-target location, the structural relationship between the controller software and the controller assembly is set to a down-hanging type.

8. The controller software and hardware matching relationship management device according to claim 6, characterized in that: Association modules for: If the structural relationship between the controller software and the controller assembly is a down-hung type, the part number of the controller software and the part number of the controller hardware are associated; If there is only one set of controller software and controller assembly in a parallel structural relationship, the part number of the controller software and the part number of the controller hardware are associated; If there are more than one set of controller software and controller assembly in a parallel structural relationship, the part number of each controller software and the part number of its corresponding controller hardware are associated based on the specified operation.

9. A controller software and hardware matching relationship management device, characterized in that: The controller software and hardware matching relationship management device includes a processor, a memory, and a controller software and hardware matching relationship management program stored in the memory and executable by the processor, wherein when the controller software and hardware matching relationship management program is executed by the processor, the steps of the controller software and hardware matching relationship management method as described in any one of claims 1 to 5 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a controller software and hardware matching relationship management program, wherein when the controller software and hardware matching relationship management program is executed by a processor, the steps of the controller software and hardware matching relationship management method according to any one of claims 1 to 5 are implemented.

Images