Deformation management method and system of vehicle CAN channel database, terminal and medium

Abstract

The invention belongs to the field of vehicle CAN channel management, and particularly discloses a vehicle CAN channel database variant management method and system, a terminal and a medium, after communication data building of controllers of a vehicle is completed, the incidence relation between variant units and controller CAN channels is established at the controller hierarchy of a model structure tree; a variant combination composed of all the target variant units is created according to the whole vehicle configuration requirement, and target controller CAN channels are selected for all the variant units in the variant combination; configuring an enabling state of a message associated with each controller CAN channel under the variant combination; the method comprises the following steps: selecting a target vehicle model variant in a platform database hierarchy to carry out consistency check, after publishing in a platform communication database, evaluating network segment load rates of vehicle models with different configurations, and exporting a multi-hierarchy communication matrix; according to the invention, convenient switching of vehicle type configuration is realized, the workload of network engineers is reduced, and the operation efficiency is improved.

Description

Technical Field

[0001] The invention belongs to the field of vehicle CAN channel management, and in particular relates to a variant management method, system, terminal and medium of a whole vehicle CAN channel database. Background Art

[0002] In the automotive industry, the mainstream solution for OEMs to manage vehicle communication databases is "one model, one database". Since SAE J1939 does not standardize the controller communication protocol used on new energy commercial vehicles, and commercial vehicles are user-ordered, a large part of the controllers used by different models are the same, so there will be a large amount of universal communication data in their communication databases, but there are also certain differences. The differences include but are not limited to the following situations: a controller will send messages with different IDs according to different calibration parameter items; the communication data related to the products of different suppliers of the same assembly controller cannot be guaranteed to be completely consistent, for example, the steering system has two configurations of electro-hydraulic emergency steering system and electric power steering system, and there are differences in their communication data; in order to reduce costs, multiple controllers distributed in different network segments are integrated into one controller; there are situations where different controllers on the same network segment send messages with the same ID. Using the above mainstream solutions in the automotive industry to manage the communication database will cause the workload of network engineers to increase exponentially due to certain configuration changes in vehicle models, increase management costs and be prone to errors. Summary of the invention

[0003] To solve the above problems, the present invention provides a variant management method, system, terminal and medium for a vehicle CAN channel database, which can realize convenient switching of vehicle configuration, reduce the workload of network engineers and improve work efficiency.

[0004] In a first aspect, the technical solution of the present invention provides a variant management method for a vehicle CAN channel database, comprising the following steps: S1, after completing the communication data construction of each controller of the vehicle, establish the association relationship between each variant unit and each controller CAN channel at the controller level of the model structure tree; S2, creating a variant combination consisting of various target variant units according to the vehicle configuration requirements, and selecting a target controller CAN channel for each variant unit in the variant combination; S3, the enable status of the messages associated with the CAN channels of each controller under the configuration variant combination; S4, select the target vehicle model variant for consistency check at the platform database level; S5, after the platform communication database is released, the network segment load rate of vehicles with different configurations is evaluated, and a multi-level communication matrix is ​​derived.

[0005] In an optional embodiment, the variant unit includes at least two variant unit items, each variant unit item is associated with at least one controller CAN channel, and the variant unit items of the variant unit are mutually exclusive.

[0006] In an optional embodiment, after selecting the target controller CAN channel for each variant unit in the variant combination, the following steps are also included: Renames a variant unit, variant unit item, and / or variant combination.

[0007] In an optional implementation, selecting a target vehicle model variant for consistency check at the platform database level specifically includes: Perform consistency check on message data; Perform consistency check on signal data; Perform consistency checks on common data.

[0008] In an optional implementation, the message data includes a message name, a message type, a message ID, a message sending type, a message period, and a message length; The signal data includes signal name, signal arrangement format, signal start byte, signal start bit, signal arrangement, signal transmission type, signal length, signal data type, signal precision, signal offset, signal physical minimum value, signal physical maximum value, signal bus minimum value, signal bus maximum value, signal bus initial value, signal bus invalid value, signal bus disabled value and signal value description; The general data includes the message fast sending cycle, the number of message fast sending times, the message delay time, the message sending controller node, the signal receiving controller node and the message / signal sending and receiving relationship.

[0009] In an optional embodiment, selecting a target vehicle model variant for consistency check at the platform database level further includes the following steps: Configure the priority of each content item of the consistency check, including configuring the message name, message type, message ID, message length, signal name, and signal length to priority 1 to priority 6; Perform consistency check on each content item in a round-robin manner according to priority; If any of the first six priority content items fails the consistency check, the consistency check is exited; If the consistency check of the content item fails, the alarm reminder level is set according to the check result.

[0010] In an optional embodiment, the derived multi-level communication matrix includes vehicle-level, network-segment-level, and controller-level communication matrices.

[0011] In a second aspect, the technical solution of the present invention provides a variant management system for a vehicle CAN channel database, comprising: The association configuration module is used to establish the association between each variant unit and each controller CAN channel at the controller level of the model structure tree after the communication data of each controller of the vehicle is established; A variant combination building module is used to create a variant combination consisting of various target variant units according to the vehicle configuration requirements, and select a target controller CAN channel for each variant unit in the variant combination; The message enable state configuration module is used to configure the enable state of the message associated with the CAN channel of each controller under the variant combination; A consistency check module, which is used to select target vehicle model variants for consistency check at the platform database level; The network segment load rate evaluation module is used to evaluate the network segment load rates of vehicle models with different configurations after the platform communication database is released, and to derive a multi-level communication matrix.

[0012] In a third aspect, the technical solution of the present invention provides a terminal, including: A memory, used for storing a variant management program of a vehicle CAN channel database; A processor is used to implement the steps of the variant management method of the whole vehicle CAN channel database as described in any one of the above items when executing the variant management program of the whole vehicle CAN channel database.

[0013] In a fourth aspect, the technical solution of the present invention provides a computer-readable storage medium, on which a variation management program for a complete vehicle CAN channel database is stored. When the variation management program for the complete vehicle CAN channel database is executed by a processor, the steps of the variation management method for the complete vehicle CAN channel database as described in any one of the above items are implemented.

[0014] A variant management method, system, terminal and medium of a whole vehicle CAN channel database provided by the present invention have the following beneficial effects compared with the prior art: after completing the communication data construction of each controller of the whole vehicle, an association relationship between a variant unit and a controller CAN channel is established, and then a variant combination composed of variant units is created according to the vehicle configuration requirements to realize the configuration management of the vehicle CAN communication. The present invention realizes the CAN communication configuration of different vehicle models according to the variant units, which is convenient for network engineers to switch vehicle model configurations freely. At the same time, based on different vehicle model configurations, consistency checks on network segment communication data, load rate evaluations and communication matrix exports are performed, which supports the development of vehicle models and assembly controllers, and can effectively improve the work efficiency of network engineers and reduce the error rate. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0015] Figure 1 It is a flow chart of a variant management method of a vehicle CAN channel database provided by an embodiment of the present invention.

[0016] Figure 2 is a schematic diagram of a variant unit.

[0017] Figure 3 This is a diagram of message configuration.

[0018] Figure 4 It is a schematic block diagram of a variant management structure of a vehicle CAN channel database provided by an embodiment of the present invention.

[0019] Figure 5 It is a schematic diagram of the structure of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the scheme of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in the specification of the present invention herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0022] Figure 1 This is a flow chart of a variant management method of a vehicle CAN channel database provided by an embodiment of the present invention. Figure 1 The execution subject may be a variant management system of a vehicle CAN channel database. The variant management method of a vehicle CAN channel database provided by an embodiment of the present invention is executed by a computer device, and accordingly, the variant management system of the vehicle CAN channel database runs in the computer device. According to different requirements, the order of the steps in the flowchart can be changed, and some can be omitted.

[0023] like Figure 1 As shown, the method includes the following steps.

[0024] S1, after completing the communication data establishment of each controller of the vehicle, establish the association relationship between each variant unit and each controller CAN channel at the controller level of the model structure tree.

[0025] Figure 2 is a schematic diagram of a variant unit. In this embodiment, the variant unit includes at least two variant unit items, each variant unit item is associated with at least one controller CAN channel, and the variant unit items of the variant unit are mutually exclusive.

[0026] For an electronic and electrical architecture platform, variant units are used in the following situations: 1) The same configuration is selected from different manufacturers, resulting in different controller communication data, and needs to be managed by two controllers, such as the steering system is divided into domestic manufacturer versions and foreign manufacturer versions. 2) When the vehicle configuration is divided into high and low configurations, the controller communication data is different, such as some ordered vehicles use ABS, and some ordered vehicles require EBS. For the second situation, the variant unit is the braking system, variant unit item 1 can be defined as ABS, and variant unit item 2 can be defined as EBS. ABS and EBS are mutually exclusive and cannot be installed on the same vehicle.

[0027] S2, creates a variant combination consisting of various target variant units according to the vehicle configuration requirements, and selects a target controller CAN channel for each variant unit in the variant combination.

[0028] In this embodiment, the variant combination can select the variant unit item corresponding to the variant unit according to the vehicle configuration. The variant combination can redefine the name and support any combination of Chinese, English, numbers and underscores. The variant unit and the variant unit item can redefine the name and support any combination of Chinese, English, numbers and underscores.

[0029] It should be noted that the variant combination can be compared to the optional package 1, optional package 2, etc. seen when buying a car at a 4S store. One vehicle configuration corresponds to a variant combination, and the variant combination selects a variant unit item in each variant unit to form a specific configuration of a vehicle model.

[0030] This embodiment manages variant units based on the controller CAN channel as the smallest object, allowing network engineers to freely configure according to the actual needs of the vehicle, shortening the communication data construction management cycle. In addition, the application variant combination associates the variant unit and the vehicle model configuration, allowing network engineers to freely configure as needed, realizing efficient utilization of platform communication data.

[0031] S3, the enable status of the messages associated with the CAN channels of each controller under the configuration variant combination.

[0032] Figure 3It is a schematic diagram of message configuration. In this embodiment, the messages associated with the controller CAN channel include sending messages and receiving messages. The configuration enable state refers to setting the sending message and receiving message signal enable or disable under this variant combination for the selected controller CAN channel. That is, under a specific variant combination, the message sent or received by each controller CAN channel is set to whether it should be transmitted under this variant combination.

[0033] This embodiment uses the variant combination as an object to configure the CAN channel of the controller under the variant to send and receive messages, so as to achieve the situation where the CAN channel of the same controller is compatible with inconsistent sending and receiving messages for different vehicle models, thereby ensuring the accuracy of work such as load rate evaluation during the design stage.

[0034] S4, select the target vehicle model variant at the platform database level for consistency check.

[0035] The consistency check content of this embodiment includes message data, signal data and general data. It is necessary to perform consistency check on message data, consistency check on signal data and consistency check on general data.

[0036] Message data includes message name, message type, message ID, message sending type, message cycle and message length; signal data includes signal name, signal arrangement format, signal starting byte, signal starting bit, signal arrangement, signal sending type, signal length, signal data type, signal precision, signal offset, signal physical minimum value, signal physical maximum value, signal bus minimum value, signal bus maximum value, signal bus initial value, signal bus invalid value, signal bus non-enabled value and signal value description; general data includes message fast sending cycle, message fast sending times, message delay time, message sending controller node, signal receiving controller node and message / signal sending and receiving relationship.

[0037] In an optional implementation, the consistency check will give priority to checking the message name, message type, message ID, message length, signal name and signal length. If the above check items are illegal, the next check will not be performed and the system will directly return to exit. If legal, the remaining items will continue to be checked. Specifically, the following steps are included.

[0038] Step 1: Configure the priority of each content item of the consistency check, including configuring the message name, message type, message ID, message length, signal name, and signal length to priority 1 to priority 6.

[0039] Step 2: Perform a consistency check on each content item in a round-robin manner according to the priority.

[0040] Step 3: If any of the first 6 priority content items fails the consistency check, then the consistency check is exited.

[0041] Step 4: If the consistency check of the content item fails, an alarm reminder level is set according to the check result.

[0042] In this implementation, a consistency check is performed on each content item in a polling manner, and each content item has specific correct requirements. If the requirements exceed the normal range, an error is reported. Exemplarily, the message name and signal name can only be numbers, letters and underscores, and the first character must be a letter. The length of the message name and the signal name cannot exceed the threshold. Message types include CAN standard frames, CAN extended frames, CAN network management, CAN diagnostic frames, CANFD standard frames, CANFD extended frames, CANFD network management and CANFD diagnostic frames. The message / signal transceiver relationship includes: if the message has a receiving controller node, the receiving controller node must receive at least one signal under the message, if the message is not sent or the receiving controller node, the signal cannot have a node transceiver relationship, and the message sending controller node is consistent with the subordinate signal sending controller node.

[0043] In an optional implementation, the consistency check results include three levels of reminders: error, warning, and information, which facilitate network engineers to prioritize solving serious problems.

[0044] S5, after the platform communication database is released, the network segment load rate of vehicles with different configurations is evaluated, and a multi-level communication matrix is ​​derived.

[0045] In this embodiment, when evaluating the network segment load rate of different configuration models, first select different model variants at the platform database level, then select the CAN network segment of the specific model variant, execute the load rate calculation program, the load rate program calculates according to the load rate calculation formula, and evaluates according to the calculation results. It includes CAN bus ideal load rate calculation, CAN bus worst load rate calculation, CANFD bus ideal load rate calculation, and CANFD bus worst load rate calculation.

[0046] In this embodiment, the export of vehicle-level, network-segment-level, and controller-level communication matrices is supported, and the communication matrix does not contain communication data specific to other vehicle model variants, thereby ensuring the accuracy of communication data transmission.

[0047] The communication matrix is ​​a customized Excel template. For example, if you choose to export a certain controller communication matrix, you just need to find the send and receive message signals related to the controller from the communication database and fill them into the Excel template. Network engineers are responsible for managing the vehicle-level communication database and need to export communication matrices of different levels according to different work requirements. The uses are as follows: 1) When connecting with component engineers and component suppliers, it is necessary to export the relevant controller-level communication matrix. Communication data not related to the component will not be exported for the purpose of design confidentiality; 2) The network segment-level and vehicle-level communication matrices are mainly used for bench testing, test vehicle debugging, etc., to facilitate the analysis of changes in signals required for the actual vehicle.

[0048] The above describes in detail an embodiment of a variant management method for a complete vehicle CAN channel database. Based on the variant management method for a complete vehicle CAN channel database described in the above embodiment, an embodiment of the present invention also provides a variant management system for a complete vehicle CAN channel database corresponding to the method.

[0049] Figure 4 It is a schematic block diagram of a variant management structure of a vehicle CAN channel database provided by an embodiment of the present invention. In this embodiment, the variant management system 400 of the vehicle CAN channel database can be divided into multiple functional modules according to the functions it performs. The module referred to in the present invention refers to a series of computer program segments that can be executed by at least one processor and can complete fixed functions, which are stored in a memory.

[0050] The association configuration module 410 is used to establish the association between each variant unit and each controller CAN channel at the controller level of the model structure tree after completing the communication data construction of each controller of the whole vehicle.

[0051] The variant combination building module 420 is used to create a variant combination consisting of various target variant units according to the vehicle configuration requirements, and select a target controller CAN channel for each variant unit in the variant combination.

[0052] The message enable state configuration module 430 is used to configure the enable state of the message associated with the CAN channel of each controller under the variant combination.

[0053] The consistency check module 440 is used to select a target vehicle model variant for consistency check at the platform database level.

[0054] The network segment load rate evaluation module 450 is used to evaluate the network segment load rates of vehicle models with different configurations after the platform communication database is released, and to derive a multi-level communication matrix.

[0055] The variant management system of the vehicle CAN channel database of this embodiment is used to implement the aforementioned variant management method of the vehicle CAN channel database. Therefore, the specific implementation method of the system can be seen in the embodiment part of the variant management method of the vehicle CAN channel database in the previous text. Therefore, its specific implementation method can refer to the description of the corresponding embodiments of each part, which will not be elaborated here.

[0056] In addition, since the variant management system of the vehicle CAN channel database of this embodiment is used to implement the aforementioned variant management method of the vehicle CAN channel database, its function corresponds to that of the aforementioned method and will not be repeated here.

[0057] Figure 5 A schematic diagram of the structure of a terminal 500 provided in an embodiment of the present invention includes: a processor 510, a memory 520 and a communication unit 530. The processor 510 is used to implement the following steps when implementing the variant management program of the vehicle CAN channel database stored in the memory 520: S1, after completing the communication data construction of each controller of the vehicle, establish the association relationship between each variant unit and each controller CAN channel at the controller level of the model structure tree; S2, creating a variant combination consisting of various target variant units according to the vehicle configuration requirements, and selecting a target controller CAN channel for each variant unit in the variant combination; S3, the enable status of the messages associated with the CAN channels of each controller under the configuration variant combination; S4, select the target vehicle model variant for consistency check at the platform database level; S5, after the platform communication database is released, the network segment load rate of vehicles with different configurations is evaluated, and a multi-level communication matrix is ​​derived.

[0058] The present invention also provides a computer storage medium, wherein the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM).

[0059] The computer storage medium stores a variant management program of the vehicle CAN channel database, and when the variant management program of the vehicle CAN channel database is executed by the processor, the following steps are implemented: S1, after completing the communication data construction of each controller of the vehicle, establish the association relationship between each variant unit and each controller CAN channel at the controller level of the model structure tree; S2, creating a variant combination consisting of various target variant units according to the vehicle configuration requirements, and selecting a target controller CAN channel for each variant unit in the variant combination; S3, the enable status of the messages associated with the CAN channels of each controller under the configuration variant combination; S4, select the target vehicle model variant for consistency check at the platform database level; S5, after the platform communication database is released, the network segment load rate of vehicles with different configurations is evaluated, and a multi-level communication matrix is ​​derived.

[0060] The above disclosure is only a preferred embodiment of the present invention, but the present invention is not limited thereto. Any non-creative changes that can be thought of by a person skilled in the art, as well as several improvements and modifications made without departing from the principle of the present invention, should fall within the protection scope of the present invention.

Claims

1. A variant management method for a vehicle CAN channel database, characterized in that: The following steps are involved: S1, after completing the communication data construction of each controller of the vehicle, establish the association relationship between each variant unit and each controller CAN channel at the controller level of the model structure tree; S2, creating a variant combination consisting of various target variant units according to the vehicle configuration requirements, and selecting a target controller CAN channel for each variant unit in the variant combination; S3, the enable status of the messages associated with the CAN channels of each controller under the configuration variant combination; S4, select the target vehicle model variant for consistency check at the platform database level; S5, after the platform communication database is released, the network segment load rate of vehicles with different configurations is evaluated, and a multi-level communication matrix is ​​derived.

2. The variant management method of the vehicle CAN channel database according to claim 1 is characterized in that: The variant unit includes at least two variant unit items, each variant unit item is associated with at least one controller CAN channel, and the variant unit items of the variant unit are mutually exclusive.

3. The variant management method of the vehicle CAN channel database according to claim 2 is characterized in that: After selecting the target controller CAN channel for each variant unit in the variant combination, the following steps are also included: Renames a variant unit, variant unit item, and / or variant combination.

4. The variant management method of the vehicle CAN channel database according to claim 1 is characterized in that: Select the target vehicle variant at the platform database level for consistency check, including: Perform consistency check on message data; Perform consistency check on signal data; Perform consistency checks on common data.

5. The variant management method of the vehicle CAN channel database according to claim 4 is characterized in that: The message data includes message name, message type, message ID, message sending type, message period and message length; The signal data includes signal name, signal arrangement format, signal start byte, signal start bit, signal arrangement, signal transmission type, signal length, signal data type, signal precision, signal offset, signal physical minimum value, signal physical maximum value, signal bus minimum value, signal bus maximum value, signal bus initial value, signal bus invalid value, signal bus disabled value and signal value description; The general data includes the message fast sending cycle, the number of message fast sending times, the message delay time, the message sending controller node, the signal receiving controller node and the message / signal sending and receiving relationship.

6. The variant management method of the vehicle CAN channel database according to claim 5 is characterized in that: Selecting the target vehicle variant for consistency check at the platform database level also includes the following steps: Configure the priority of each content item of the consistency check, including configuring the message name, message type, message ID, message length, signal name, and signal length to priority 1 to priority 6; Perform consistency check on each content item in a round-robin manner according to priority; If any of the first six priority content items fails the consistency check, the consistency check is exited; If the consistency check of the content item fails, the alarm reminder level is set according to the check result.

7. The variant management method of the vehicle CAN channel database according to claim 1 is characterized in that: The exported multi-level communication matrix includes vehicle-level, network-segment-level, and controller-level communication matrices.

8. A variant management system for a vehicle CAN channel database, characterized in that: include: The association configuration module is used to establish the association between each variant unit and each controller CAN channel at the controller level of the model structure tree after the communication data of each controller of the vehicle is established; A variant combination building module is used to create a variant combination consisting of various target variant units according to the vehicle configuration requirements, and select a target controller CAN channel for each variant unit in the variant combination; The message enable state configuration module is used to configure the enable state of the message associated with the CAN channel of each controller under the variant combination; A consistency check module, which is used to select target vehicle model variants for consistency check at the platform database level; The network segment load rate evaluation module is used to evaluate the network segment load rates of vehicle models with different configurations after the platform communication database is released, and to derive a multi-level communication matrix.

9. A terminal, characterized in that: include: A memory, used for storing a variant management program of a vehicle CAN channel database; A processor is used to implement the steps of the vehicle CAN channel database variation management method as described in any one of claims 1-7 when executing the vehicle CAN channel database variation management program.

10. A computer-readable storage medium, characterized in that: The readable storage medium stores a variation management program for the vehicle CAN channel database. When the variation management program for the vehicle CAN channel database is executed by the processor, the steps of the variation management method for the vehicle CAN channel database as described in any one of claims 1 to 7 are implemented.

Images