Communication matrix management method and device

Abstract

The present invention discloses a communication matrix management method and device, relating to the field of communication matrix technology. After the current communication matrix is ​​released, the present invention obtains the actual release time of the current communication matrix and the version number of the previous communication matrix. Based on the actual release time of the current communication matrix, the present invention automatically updates the version number by automatically updating one of the phase bit, baseline bit, and revision bit of the previous communication matrix version number. This method is highly efficient and error-prone.

Description

Technical Field

[0001] The present invention relates to the technical field of communication matrices, and in particular to a communication matrix management method and device. Background Art

[0002] The vehicle communication matrix is ​​the external interface of the vehicle's electronic control unit (ECU). During ECU software development, developers need to update the communication matrix version number every time they modify the communication matrix in order to manage all communication matrices. However, currently, updating the communication matrix version number is done manually by developers, which is inefficient and prone to errors. Summary of the Invention

[0003] The present invention solves the technical problems in the prior art of low efficiency and easy error in updating the communication matrix version number by providing a communication matrix management method and device.

[0004] On the one hand, the present invention provides the following technical solutions:

[0005] A communication matrix management method, comprising:

[0006] After the current communication matrix is ​​released, the actual release time of the current communication matrix and the version number of the previous communication matrix are obtained;

[0007] If the actual release time is one of the preset stage release times, the stage bit of the version number of the previous version of the communication matrix is ​​updated to obtain the version number of the current communication matrix;

[0008] If the actual release time is one of the preset baseline release times, updating the baseline bit of the version number of the previous communication matrix to obtain the version number of the current communication matrix;

[0009] If the actual release time is neither one of the stage release times nor one of the baseline release times, the revision bit of the version number of the previous communication matrix is ​​updated to obtain the version number of the current communication matrix.

[0010] Preferably, the communication matrix management method further includes:

[0011] Read the message name in the current communication matrix;

[0012] Searching for the message name in the previous version of the communication matrix;

[0013] If the message name is not found, the new message description will be written into the communication matrix change record table. The new message description includes the field "new message", the message name, the field "a send" and the field "b receive", where a is the sending ECU name corresponding to the message name in the current communication matrix, and b is the receiving ECU name corresponding to the message name in the current communication matrix.

[0014] Preferably, the communication matrix management method further includes:

[0015] Read the message name in the previous version of the communication matrix;

[0016] Searching for the message name in the current communication matrix;

[0017] If the message name is not found, the message deletion description is written into the communication matrix change record table. The message deletion description includes the field "delete message", the message name, the field "c cancel sending" and the field "d cancel receiving", where c is the sending ECU name corresponding to the message name in the previous version of the communication matrix, and d is the receiving ECU name corresponding to the message name in the previous version of the communication matrix.

[0018] Preferably, the communication matrix management method further includes:

[0019] Read all sending ECU names and all receiving ECU names corresponding to the same message name in the current communication matrix and the previous version of the communication matrix;

[0020] If the sending ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, a message sender change description is written into the communication matrix change record table, wherein the message sender change description includes the field "message sender change", the same message name, the sending ECU name corresponding to the same message name in the previous version of the communication matrix, and the sending ECU name corresponding to the same message name in the current communication matrix;

[0021] If the receiving ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, the message recipient change description is written into the communication matrix change record table, and the message recipient change description includes the field "message recipient change", the same message name, the receiving ECU name corresponding to the same message name in the previous version of the communication matrix, and the receiving ECU name corresponding to the same message name in the current communication matrix.

[0022] Preferably, the communication matrix management method further includes:

[0023] Reading attributes corresponding to the same message name and the same signal name in the current communication matrix and the previous version of the communication matrix;

[0024] If the attributes corresponding to the same signal name in the current communication matrix and the previous version of the communication matrix are different, the signal attribute modification description is written into the communication matrix change record table, and the signal attribute modification description includes the field "modify signal", the same message name, the same signal name, the attribute name corresponding to the same signal name, the field "e send" and the field "f receive", where e is the sending ECU name corresponding to the same signal name in the current communication matrix, and f is the receiving ECU name corresponding to the same signal name in the current communication matrix.

[0025] Preferably, the communication matrix management method further includes:

[0026] Read the signal name in the message of the current communication matrix; search for the signal name in the same message of the previous version of the communication matrix; if the signal name is not found, write the newly added signal description into the communication matrix change record table, wherein the newly added signal description includes a field "newly added signal", the message name to which the signal name belongs, the signal name, a field "g send" and a field "h receive", where g is the name of the sending ECU corresponding to the signal name in the current communication matrix, and h is the name of the receiving ECU corresponding to the signal name in the current communication matrix;

[0027] Read the signal name in the message of the previous version of the communication matrix; search for the signal name in the same message of the current communication matrix; if the signal name is not found, write the deletion signal description into the communication matrix change record table, wherein the deletion signal description includes the field "delete signal", the message name to which the signal name belongs, the signal name, the field "i cancels sending" and the field "j cancels receiving", where i is the sending ECU name corresponding to the signal name in the previous version of the communication matrix, and j is the receiving ECU name corresponding to the signal name in the previous version of the communication matrix.

[0028] Preferably, the communication matrix management method further includes:

[0029] Reading the receiving ECU name corresponding to the signal name in the message of the current communication matrix; searching for the receiving ECU name in the same message and the same signal of the previous version of the communication matrix; if the receiving ECU name is not found, writing a newly added signal recipient description into the communication matrix change record table, the newly added signal recipient description including the field "newly added signal recipient", the same message name, the same signal name, and the receiving ECU name;

[0030] Read the receiving ECU name corresponding to the signal name in the message of the previous version of the communication matrix; search for the receiving ECU name in the same message and the same signal of the current communication matrix; if the receiving ECU name is not found, write the description of the deleted signal recipient into the communication matrix change record table, and the description of the deleted signal recipient includes the field "deleted signal recipient", the same message name, the same signal name, and the receiving ECU name.

[0031] On the other hand, the present invention also provides the following technical solutions:

[0032] A communication matrix management device, comprising:

[0033] A data acquisition module is used to obtain the actual release time of the current communication matrix and the version number of the previous version of the communication matrix after the current communication matrix is ​​released;

[0034] A version number updating module is configured to update the phase bit of the version number of the previous version of the communication matrix to obtain the version number of the current communication matrix if the actual release time is one of the preset phase release times;

[0035] The version number updating module is further configured to update the baseline bit of the version number of the previous version of the communication matrix to obtain the version number of the current communication matrix if the actual release time is one of the preset baseline release times;

[0036] The version number updating module is further configured to update the revision bit of the version number of the previous version of the communication matrix to obtain the version number of the current communication matrix if the actual release time is neither one of the stage release times nor one of the baseline release times.

[0037] On the other hand, the present invention also provides the following technical solutions:

[0038] An electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements any of the above-mentioned communication matrix management methods when executing the program.

[0039] On the other hand, the present invention also provides the following technical solutions:

[0040] A computer-readable storage medium stores a computer program, which implements any of the above-mentioned communication matrix management methods when executed by a processor.

[0041] One or more technical solutions provided by the present invention have at least the following technical effects or advantages:

[0042] After the current communication matrix is ​​released, the present invention obtains the actual release time of the current communication matrix and the version number of the previous version of the communication matrix. According to the actual release time of the current communication matrix, one of the stage bit, baseline bit and revision bit of the version number of the previous version of the communication matrix can be automatically updated to automatically update the version number. The update efficiency of the version number is high and it is not easy to make mistakes. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0044] Figure 1 Flowchart of a communication matrix management method according to an embodiment of the present invention;

[0045] Figure 2 A partial schematic diagram of a communication matrix in an embodiment of the present invention;

[0046] Figure 3 Schematic diagram of the structure of a communication matrix management device in an embodiment of the present invention. DETAILED DESCRIPTION

[0047] The embodiments of the present invention solve the technical problems in the prior art of low efficiency and easy error in updating the version number of a communication matrix by providing a communication matrix management method and device.

[0048] In order to better understand the technical solution of the present invention, the technical solution of the present invention will be described in detail below with reference to the accompanying drawings and specific implementation methods.

[0049] like Figure 1 As shown, the communication matrix management method of this embodiment includes:

[0050] Step S1: After the current communication matrix is ​​released, the actual release time of the current communication matrix and the version number of the previous communication matrix are obtained;

[0051] Step S2: if the actual release time is one of the preset stage release times, the stage bit of the version number of the previous communication matrix is ​​updated to obtain the version number of the current communication matrix;

[0052] Step S3: If the actual release time is one of the preset baseline release times, the baseline bit of the version number of the previous communication matrix is ​​updated to obtain the version number of the current communication matrix;

[0053] Step S4: If the actual release time is neither one of the stage release times nor one of the baseline release times, the revision bit of the version number of the previous communication matrix is ​​updated to obtain the version number of the current communication matrix.

[0054] The development cycle of vehicle ECU software is long, sometimes lasting up to a year. This development cycle is divided into multiple phases, each of which can last several months. Communication matrix management requires that communication matrix builders release a version of the communication matrix at the beginning of each phase. For example, if ECU software development begins on January 1st of a given year and the development cycle is divided into four months for Phase 1, four months for Phase 2, and four months for Phase 3, technicians will need to release a version of the communication matrix on January 1st, May 1st, and September 1st. These are the phase release times in step S2. In each phase, project management or architecture developers may require communication matrix builders to release a version of the communication matrix at a specific time point within the phase, called a baseline version. For example, if Phase 1 runs from January 1st to April 30th, project management or architecture developers may require communication matrix builders to release a version of the communication matrix on February 1st and March 1st. These two dates are the baseline release times in step S3. After the baseline version is released, it may be necessary to add missing ECU requirements or correct typos, and the communication matrix builders will also release it after revising the communication matrix.

[0055] The version number of a communication matrix is ​​typically formatted like "V1.0.0," consisting of three digits separated by the letter "V" and two periods. The first digit represents the phase, the second represents the baseline, and the third represents the revision. Traditionally, communication matrix management requires manual updating of the version number for each release by the matrix builders, increasing the burden on technical personnel and making them prone to errors.

[0056] In this embodiment, it is assumed that the version number of the first version of the communication matrix released on January 1 is V1.0.0, and the second version of the communication matrix is ​​the baseline version. The actual release time should be February 1. The version number of the previous version of the communication matrix after the release of the second version of the communication matrix is ​​V1.0.0. Since February 1 is the preset baseline release time, step S3 will add 1 to the baseline bit of the version number V1.0.0 to obtain the version number V1.1.0 of the second version of the communication matrix. Next, if the communication matrix constructor proactively revised the communication matrix between February 1st and February 15th and released the third version of the communication matrix on February 15th, the actual release date of the third version of the communication matrix is ​​February 15th. The version number of the communication matrix before the release of the third version of the communication matrix is ​​V1.1.0. Since February 15th is neither a phase release date nor a baseline release date, and each version update only updates one of the three digits in the version number, step S4 will increment the revision bit of version number V1.1.0 by 1, resulting in version number V1.1.1 for the third version of the communication matrix. Next, the fourth version of the communication matrix is ​​also a baseline version, and its actual release date should be March 1st. The version number of the communication matrix before the release of the fourth version of the communication matrix is ​​V1.1.1. Since March 1st is the preset baseline release date, step S3 will increment the baseline bit of version number V1.1.1 by 1, and the revision bit needs to be cleared after each baseline bit update, resulting in version number V1.2.0 for the fourth version of the communication matrix. Next, the actual release date of the fifth version of the communication matrix should be May 1st. The version number of the previous version of the communication matrix after the release of the fifth version of the communication matrix is ​​V1.2.0. Since May 1st is the preset stage release date, step S2 will increment the stage bit of version number V1.2.0 by 1. After each stage bit update, both the baseline bit and the revision bit need to be cleared simultaneously, resulting in version number V2.0.0 for the fifth version of the communication matrix. It will be appreciated that this embodiment can automatically update the version number by automatically updating one of the stage bit, baseline bit, and revision bit of the previous version of the communication matrix based on the actual release date of the current communication matrix. This makes version number updates efficient and error-prone.

[0057] The communication matrix of this embodiment can be as follows Figure 2 As shown in the figure, the communication matrix consists of multiple messages, each of which includes multiple signals. The communication matrix records the name of each message, the name of the ECU that sends the message, the name of the ECU that receives the message, the name of each signal, the attributes of the signal, the name of the ECU that sends the signal, the name of the ECU that receives the signal, etc. Figure 2In the first row, the "GW" column and subsequent columns are all ECU names. The letter "r" represents receiving, and the letter "s" represents sending. Generally, only one ECU will send a message. Generally, communication matrix management also includes recording the content of each version update in the communication matrix change record table to facilitate subsequent tracing. In the early days, communication matrix change records were manually compared between the previous and next versions of the communication matrix to determine the updated content and record it. This was also inefficient and prone to errors. To achieve automatic generation of communication matrix change records, the communication matrix management method of this embodiment may also include:

[0058] Read the message name in the current communication matrix; search for the message name in the previous version of the communication matrix; if the message name is not found, write the new message description into the communication matrix change record table. The new message description includes the field "new message", the message name, the field "a send" and the field "b receive", where a is the name of the sending ECU corresponding to the message name in the current communication matrix, and b is the name of the receiving ECU corresponding to the message name in the current communication matrix; the format of the new message description can be as follows: "new message (the message name), a send, b receive";

[0059] Read the message name in the previous version of the communication matrix; search for the message name in the current communication matrix; if the message name is not found, write the deletion message description into the communication matrix change record table, the deletion message description includes the field "delete message", the message name, the field "c cancel sending" and the field "d cancel receiving", c is the sending ECU name corresponding to the message name in the previous version of the communication matrix, d is the receiving ECU name corresponding to the message name in the previous version of the communication matrix; the format of the deletion message description can be as follows: "delete message (the message name), c cancel sending, d cancel receiving";

[0060] Read all sending ECU names and all receiving ECU names corresponding to the same message name in the current communication matrix and the previous version of the communication matrix;

[0061] If the sending ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, the message sender change description is written into the communication matrix change record table. The message sender change description includes the field "message sender change", the same message name, the sending ECU name corresponding to the same message name in the previous version of the communication matrix, and the sending ECU name corresponding to the same message name in the current communication matrix; the format of the message sender change description can be as follows: "message sender change (the same message name), the sending ECU name corresponding to the same message name in the previous version of the communication matrix -> the sending ECU name corresponding to the same message name in the current communication matrix";

[0062] If the receiving ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, the message receiver change description is written into the communication matrix change record table. The message receiver change description includes the field "message receiver change", the same message name, the receiving ECU name corresponding to the same message name in the previous version of the communication matrix, and the receiving ECU name corresponding to the same message name in the current communication matrix; the format of the message receiver change description can be as follows: "message receiver change (the same message name), the sending ECU name corresponding to the same message name in the previous version of the communication matrix -> the sending ECU name corresponding to the same message name in the current communication matrix";

[0063] Read the attributes corresponding to the same message name and the same signal name in the current communication matrix and the previous version of the communication matrix; if the attributes corresponding to the same signal name in the current communication matrix and the previous version of the communication matrix are different, write the signal attribute modification description into the communication matrix change record table, and the signal attribute modification description includes the field "modify signal", the same message name, the same signal name, the attribute name corresponding to the same signal name, the field "e send" and the field "f receive", where e is the sending ECU name corresponding to the same signal name in the current communication matrix, and f is the receiving ECU name corresponding to the same signal name in the current communication matrix; the format of the signal attribute modification description can be as follows: "modify signal (the same message name: the same signal name) the attribute name corresponding to the same signal name, e send, f receive";

[0064] Read the signal name in the message of the current communication matrix; search for the signal name in the same message of the previous version of the communication matrix; if the signal name is not found, write the newly added signal description into the communication matrix change record table, the newly added signal description includes the field "new signal", the message name to which the signal name belongs, the signal name, the field "g send" and the field "h receive", where g is the name of the sending ECU corresponding to the signal name in the current communication matrix, and h is the name of the receiving ECU corresponding to the signal name in the current communication matrix; the format of the newly added signal description can be as follows: "new signal (message name to which the signal name belongs: the signal name), g send, h receive";

[0065] Read the signal name in the message of the previous version of the communication matrix; search for the signal name in the same message of the current communication matrix; if the signal name is not found, write the deletion signal description into the communication matrix change record table, the deletion signal description includes the field "delete signal", the message name to which the signal name belongs, the signal name, the field "i cancels sending" and the field "j cancels receiving", i is the name of the sending ECU corresponding to the signal name in the previous version of the communication matrix, and j is the name of the receiving ECU corresponding to the signal name in the previous version of the communication matrix; the format of the deletion signal description can be as follows: "delete signal (message name to which the signal name belongs: the signal name), i cancels sending, j cancels receiving";

[0066] Read the receiving ECU name corresponding to the signal name in the message of the current communication matrix; search for the receiving ECU name in the same message and the same signal of the previous version of the communication matrix; if the receiving ECU name is not found, write the newly added signal receiver description into the communication matrix change record table, and the newly added signal receiver description includes the fields "newly added signal receiver", the same message name, the same signal name, and the receiving ECU name; the format of the newly added signal receiver description can be as follows: "newly added signal receiver (the same message name: the same signal name) the receiving ECU name";

[0067] Read the receiving ECU name corresponding to the signal name in the message of the previous version of the communication matrix; search for the receiving ECU name in the same message and the same signal of the current communication matrix; if the receiving ECU name is not found, write the description of the deleted signal recipient into the communication matrix change record table, and the description of the deleted signal recipient includes the field "delete signal recipient", the same message name, the same signal name, and the receiving ECU name; the format of the description of the deleted signal recipient can be as follows: "delete signal recipient (the same message name: the same signal name) the receiving ECU name".

[0068] It can be seen that this embodiment can automatically write the changes in the message sender, the changes in the message receiver, the newly added message / signal content, the deleted message / signal content, the modified content of the signal attributes, the newly added signal receiver content, the deleted signal receiver content, etc. into the communication matrix change record table, which improves efficiency and is less prone to errors.

[0069] like Figure 3 As shown, this embodiment also provides a communication matrix management device, including:

[0070] The data acquisition module is used to obtain the actual release time of the current communication matrix and the version number of the previous communication matrix after the current communication matrix is ​​released;

[0071] A version number updating module is configured to update the phase bit of the version number of the previous communication matrix to obtain the version number of the current communication matrix if the actual release time is one of the preset phase release times;

[0072] The version number updating module is further configured to update the baseline bit of the version number of the previous communication matrix to obtain the version number of the current communication matrix if the actual release time is one of the preset baseline release times;

[0073] The version number updating module is further configured to update the revision bit of the version number of the previous communication matrix to obtain the version number of the current communication matrix if the actual release time is neither one of the stage release times nor one of the baseline release times.

[0074] Furthermore, the communication matrix management device may further include:

[0075] The change record generation module is used to read the message name in the current communication matrix; search for the message name in the previous version of the communication matrix; if the message name is not found, the new message description is written into the communication matrix change record table. The new message description includes the field "new message", the message name, the field "a send" and the field "b receive", where a is the sending ECU name corresponding to the message name in the current communication matrix, and b is the receiving ECU name corresponding to the message name in the current communication matrix.

[0076] Furthermore, the change record generation module can also be used to read the message name in the previous version of the communication matrix; search for the message name in the current communication matrix; if the message name is not found, the message deletion description is written into the communication matrix change record table, and the message deletion description includes the field "delete message", the message name, the field "c cancel sending" and the field "d cancel receiving", where c is the sending ECU name corresponding to the message name in the previous version of the communication matrix, and d is the receiving ECU name corresponding to the message name in the previous version of the communication matrix.

[0077] Furthermore, the change record generation module can also be used to read all sending ECU names and all receiving ECU names corresponding to the same message name in the current communication matrix and the previous version of the communication matrix; if the sending ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, then the message sender change description is written into the communication matrix change record table, and the message sender change description includes the field "message sender change", the same message name, the sending ECU name corresponding to the same message name in the previous version of the communication matrix, and the sending ECU name corresponding to the same message name in the current communication matrix;

[0078] If the receiving ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, the message receiver change description is written into the communication matrix change record table. The message receiver change description includes the field "message receiver change", the same message name, the receiving ECU name corresponding to the same message name in the previous version of the communication matrix, and the receiving ECU name corresponding to the same message name in the current communication matrix.

[0079] Furthermore, the change record generation module can also be used to read the attributes corresponding to the same message name and the same signal name in the current communication matrix and the previous version of the communication matrix; if the attributes corresponding to the same signal name in the current communication matrix and the previous version of the communication matrix are different, the signal attribute modification description is written into the communication matrix change record table, and the signal attribute modification description includes the field "modify signal", the same message name, the same signal name, the attribute name corresponding to the same signal name, the field "e send" and the field "f receive", where e is the sending ECU name corresponding to the same signal name in the current communication matrix, and f is the receiving ECU name corresponding to the same signal name in the current communication matrix.

[0080] Furthermore, the change record generation module can also be used to read the signal name in the message of the current communication matrix; search for the signal name in the same message of the previous version of the communication matrix; if the signal name is not found, write the newly added signal description into the communication matrix change record table, and the newly added signal description includes the field "newly added signal", the message name to which the signal name belongs, the signal name, the field "g send" and the field "h receive", where g is the name of the sending ECU corresponding to the signal name in the current communication matrix, and h is the name of the receiving ECU corresponding to the signal name in the current communication matrix;

[0081] Read the signal name in the message of the previous version of the communication matrix; search for the signal name in the same message of the current communication matrix; if the signal name is not found, write the deletion signal description into the communication matrix change record table. The deletion signal description includes the field "delete signal", the message name to which the signal name belongs, the signal name, the field "i cancels sending" and the field "j cancels receiving", where i is the sending ECU name corresponding to the signal name in the previous version of the communication matrix, and j is the receiving ECU name corresponding to the signal name in the previous version of the communication matrix.

[0082] Furthermore, the change record generation module can also be used to read the receiving ECU name corresponding to the signal name in the message of the current communication matrix; search for the receiving ECU name in the same message and the same signal of the previous version of the communication matrix; if the receiving ECU name is not found, write the description of the newly added signal recipient into the communication matrix change record table, and the description of the newly added signal recipient includes the field "newly added signal recipient", the same message name, the same signal name, and the receiving ECU name;

[0083] Read the receiving ECU name corresponding to the signal name in the message of the previous version of the communication matrix; search for the receiving ECU name in the same message and the same signal of the current communication matrix; if the receiving ECU name is not found, write the description of the deleted signal recipient into the communication matrix change record table, and the description of the deleted signal recipient includes the field "delete signal recipient", the same message name, the same signal name, and the receiving ECU name.

[0084] Based on the same inventive concept as the communication matrix management method described above, this embodiment also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and runnable on the processor, wherein when the processor executes the program, the steps of any one of the communication matrix management methods described above are implemented.

[0085] Among them, the bus architecture (represented by the bus), the bus can include any number of interconnected buses and bridges, and the bus links together various circuits including one or more processors represented by the processor and memory represented by the memory. The bus can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter can be the same component, namely a transceiver, which provides a unit for communicating with various other devices on a transmission medium. The processor is responsible for managing the bus and general processing, while the memory can be used to store data used by the processor when performing operations.

[0086] Since the electronic device described in this embodiment is used to implement the communication matrix management method in the embodiment of the present invention, those skilled in the art will be able to understand the specific implementation and various variations of the electronic device in this embodiment based on the communication matrix management method described in the embodiment of the present invention. Therefore, how the electronic device implements the method in the embodiment of the present invention will not be described in detail here. As long as those skilled in the art can implement the electronic device used in the communication matrix management method in the embodiment of the present invention, it falls within the scope of protection of the present invention.

[0087] Based on the same inventive concept as the above-mentioned communication matrix management method, the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements any of the above-mentioned communication matrix management methods.

[0088] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0089] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, 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 processor, or other programmable data processing device to produce 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 flowcharts and / or block diagrams. 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.

[0090] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work 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 The function specified in one or more boxes.

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

[0092] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0093] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

Claims

1. A communication matrix management method, characterized in that: include: After the current communication matrix is ​​released, the actual release time of the current communication matrix and the version number of the previous communication matrix are obtained; If the actual release time is one of the preset stage release times, the stage bit of the version number of the previous version of the communication matrix is ​​updated to obtain the version number of the current communication matrix; If the actual release time is one of the preset baseline release times, updating the baseline bit of the version number of the previous communication matrix to obtain the version number of the current communication matrix; If the actual release time is neither one of the stage release times nor one of the baseline release times, the revision bit of the version number of the previous communication matrix is ​​updated to obtain the version number of the current communication matrix.

2. The communication matrix management method according to claim 1, wherein: Also includes: Read the message name in the current communication matrix; Searching for the message name in the previous version of the communication matrix; If the message name is not found, the newly added message description will be written into the communication matrix change record table. The newly added message description includes the field "new message", the message name, the field "a send" and the field "b receive", where a is the sending ECU name corresponding to the message name in the current communication matrix, and b is the receiving ECU name corresponding to the message name in the current communication matrix.

3. The communication matrix management method according to claim 1, wherein: Also includes: Read the message name in the previous version of the communication matrix; Searching for the message name in the current communication matrix; If the message name is not found, the message deletion description is written into the communication matrix change record table. The message deletion description includes the field "delete message", the message name, the field "c cancel sending" and the field "d cancel receiving". c is the sending ECU name corresponding to the message name in the previous version of the communication matrix, and d is the receiving ECU name corresponding to the message name in the previous version of the communication matrix.

4. The communication matrix management method according to claim 1, wherein: Also includes: Read all sending ECU names and all receiving ECU names corresponding to the same message name in the current communication matrix and the previous version of the communication matrix; If the sending ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, a message sender change description is written into the communication matrix change record table, wherein the message sender change description includes the field "message sender change", the same message name, the sending ECU name corresponding to the same message name in the previous version of the communication matrix, and the sending ECU name corresponding to the same message name in the current communication matrix; If the receiving ECU name corresponding to the same message name in the current communication matrix and the previous version of the communication matrix is ​​different, the message recipient change description is written into the communication matrix change record table. The message recipient change description includes the field "message recipient change", the same message name, the receiving ECU name corresponding to the same message name in the previous version of the communication matrix, and the receiving ECU name corresponding to the same message name in the current communication matrix.

5. The communication matrix management method according to claim 1, wherein: Also includes: Reading attributes corresponding to the same message name and the same signal name in the current communication matrix and the previous version of the communication matrix; If the attributes corresponding to the same signal name in the current communication matrix and the previous version of the communication matrix are different, the signal attribute modification description is written into the communication matrix change record table, and the signal attribute modification description includes the field "modify signal", the same message name, the same signal name, the attribute name corresponding to the same signal name, the field "e send" and the field "f receive", where e is the sending ECU name corresponding to the same signal name in the current communication matrix, and f is the receiving ECU name corresponding to the same signal name in the current communication matrix.

6. The communication matrix management method according to claim 1, wherein: Also includes: Reading a signal name in a message of the current communication matrix; Searching for the signal name in the same message of the previous version of the communication matrix; If the signal name is not found, the newly added signal description is written into the communication matrix change record table. The newly added signal description includes the field "new signal", the message name to which the signal name belongs, the signal name, the field "g send" and the field "h receive", where g is the name of the sending ECU corresponding to the signal name in the current communication matrix, and h is the name of the receiving ECU corresponding to the signal name in the current communication matrix; Read the signal name in the message of the previous version of the communication matrix; search for the signal name in the same message of the current communication matrix; if the signal name is not found, write a deletion signal description into the communication matrix change record table, where the deletion signal description includes a field "delete signal", the message name to which the signal name belongs, the signal name, a field "i cancels sending" and a field "j cancels receiving", where i is the name of the sending ECU corresponding to the signal name in the previous version of the communication matrix, and j is the name of the receiving ECU corresponding to the signal name in the previous version of the communication matrix.

7. The communication matrix management method according to claim 1, wherein: Also includes: Read the receiving ECU name corresponding to the signal name in the message of the current communication matrix; Searching for the receiving ECU name in the same message and the same signal of the previous version of the communication matrix; if the receiving ECU name is not found, writing a description of the newly added signal recipient into the communication matrix change record table, wherein the description of the newly added signal recipient includes the field "newly added signal recipient", the same message name, the same signal name, and the receiving ECU name; Read the receiving ECU name corresponding to the signal name in the message of the previous version of the communication matrix; search for the receiving ECU name in the same message and the same signal of the current communication matrix; if the receiving ECU name is not found, write the deleted signal recipient description into the communication matrix change record table, the deleted signal recipient description including the field "deleted signal recipient", the same message name, the same signal name, and the receiving ECU name.

8. A communication matrix management device, characterized in that: include: A data acquisition module is used to obtain the actual release time of the current communication matrix and the version number of the previous version of the communication matrix after the current communication matrix is ​​released; A version number updating module is configured to update the phase bit of the version number of the previous version of the communication matrix to obtain the version number of the current communication matrix if the actual release time is one of the preset phase release times; The version number updating module is further configured to update the baseline bit of the version number of the previous version of the communication matrix to obtain the version number of the current communication matrix if the actual release time is one of the preset baseline release times; The version number updating module is further configured to update the revision bit of the version number of the previous version of the communication matrix to obtain the version number of the current communication matrix if the actual release time is neither one of the stage release times nor one of the baseline release times.

9. An electronic device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the communication matrix management method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the communication matrix management method according to any one of claims 1 to 7 is implemented.

Images