A vehicle-mounted bus communication data design method and device and a storage medium

Abstract

The application relates to a vehicle-mounted bus communication data design method and device and a storage medium. The application sequentially manages four levels of structures, signals, messages and communication data of vehicle communication to realize auxiliary vehicle-mounted bus communication data design. The levels and management tasks thereof include: constructing and managing a model structure tree of multi-level classification management at level L1; level L2 is responsible for managing a signal database, wherein signal type attributes and signal attributes are defined in the signal database; at level L3, messages and referenced signals are managed in a message database according to the implementation requirements of the whole vehicle function; and level L4 is responsible for managing communication data to generate a gateway routing database and export a communication database and a communication matrix of the whole vehicle level and the controller level. The application can solve the communication protocol version management problem in bus communication design, help improve the work efficiency of network designers and reduce the occurrence rate of human low-level errors.

Description

Technical Field

[0001] The present invention relates to the field of vehicle bus communication design auxiliary technology, and in particular to a vehicle bus communication data design method, device and storage medium. Background Art

[0002] Currently, bus communication protocols between OEMs and suppliers are still primarily documented in Office documents. These documents are inherently independent and easily modifiable, making it easy to discover that certain functions are not functioning properly during vehicle commissioning. When these issues arise, multiple rounds of troubleshooting are often required. This can be difficult to detect if the cause is a miscommunication between designers using Office documents to explain the communication protocol, or if a change in communication data on one side is not fully communicated. To avoid impacting vehicle delivery schedules, designers of affected controllers are forced to urgently provide temporary programs, which further leads to issues with controller software version management and increases the difficulty of designing vehicle bus communication data. Summary of the Invention

[0003] In order to solve the above technical problems or at least partially solve the above technical problems, the present invention provides a vehicle bus communication data design method, device and storage medium.

[0004] In a first aspect, the present invention provides a method for designing vehicle bus communication data, which manages the structure, signals, messages, and communication data of vehicle communication in an orderly manner at four levels to implement auxiliary vehicle bus communication data design. The levels and their management tasks include:

[0005] Construct and manage a multi-level classification management model structure tree at layer L1. The levels of the model structure tree include: network architecture, controller list, routing table, network topology map, and variant list;

[0006] Layer L2 is responsible for managing the signal database, in which signal type attributes and signal properties are defined;

[0007] At layer L3, messages and referenced signals are managed in the message database according to the vehicle function requirements;

[0008] Layer L4 is responsible for managing communication data, selecting and activating specific variant packages in the variant list to generate the gateway routing database for the dedicated car, and exporting the communication database and communication matrix at the vehicle level and controller level.

[0009] Furthermore, the construction of a multi-level classification management model structure tree at layer L1 includes the following steps:

[0010] S101: quickly create a model structure tree framework with one click, the framework including multiple levels of network architecture, controller list, routing table, network topology diagram and variant list;

[0011] S102: Design a platform-level communication database at the network architecture level, and design a dedicated car communication database suitable for dedicated cars at the variant list level;

[0012] S103: Manually create all network segments and controllers of the vehicle, and set the properties of the network segments and controllers;

[0013] S104: establishing an association relationship between the network segment and the CAN channel of the controller at a network segment level or a controller level;

[0014] S105: Displaying the association relationship between the network segment and the controller CAN channel in a graphical form in a network topology layer, so as to intuitively and conveniently verify the correctness of the association relationship in S104;

[0015] S106: Establishing an association relationship between the variant package and the controller in the variant list hierarchy.

[0016] Furthermore, the attributes of the network segment include the network segment name, protocol items, baud rate settings, network management settings, network segment version, associated ECU settings, signal arrangement method and first remarks; the attributes of the controller include: controller name, whether to support BootLoader, communication route settings, associated network segment settings and second remarks.

[0017] Furthermore, the layer L2 summarizes the communication requirements of all controllers, creates signal type attributes and signal attributes required by the communication requirements, and quickly adds corresponding signal attributes in the signal database by referencing the signal type attributes.

[0018] Furthermore, the signal type attributes include signal type name, length, unit, signal value type, precision, offset, signal value definition and a third remarks column; the signal attributes include signal name, referenced signal type, length, unit, signal value type, precision, offset, initial value, invalid value, signal value definition and a fourth remarks column.

[0019] Furthermore, the management of messages and referenced signals in the message database according to the vehicle function implementation requirements includes the following steps:

[0020] S301: Select the network segment where the sending controller is located, create the corresponding message and detailed attributes of the message;

[0021] S302: directly referencing the required target signal from the signal database and arranging the position of the target signal;

[0022] S303: Associating each message of the sending network segment with the target network segment according to the vehicle function implementation requirements;

[0023] S304: According to the communication requirements of the sending controller, the corresponding receiving controller information is added to the corresponding signal attributes.

[0024] Furthermore, the routing table database content includes: a sending end communication data module, a receiving end communication data module and a general data module;

[0025] The contents of the transmitting end communication data module include: the sending network segment name, signal name, message name and message ID;

[0026] The content of the receiving end communication data module includes: receiving network segment name, signal name, message name and message ID;

[0027] The content of the general data module includes: routing mode and controller information; the routing mode includes direct message routing and signal routing.

[0028] In a second aspect, the present invention provides a vehicle bus communication data design device, comprising at least one processing unit, the processing unit being connected to at least one storage unit via a bus unit, the storage unit storing a computer program, and when the computer program is executed by the processing unit, the vehicle bus communication data design method is implemented.

[0029] In a third aspect, the present invention provides a computer-readable storage medium storing a computer program, wherein the computer program implements the vehicle bus communication data design method when executed by a processing unit.

[0030] The above technical solution provided by the embodiment of the present invention has the following advantages compared with the prior art:

[0031] The present invention relates to a method, device and storage medium for designing vehicle bus communication data. The present invention divides the structure, signals, messages and communication data of vehicle communication into four levels for orderly management to realize auxiliary vehicle bus communication data design. The levels and their management tasks include: constructing and managing a model structure tree for multi-level classification management at layer L1; layer L2 is responsible for managing the signal database, defining signal type attributes and signal attributes in the signal database; layer L3 manages messages and referenced signals in the message database according to the requirements of the whole vehicle function implementation; layer L4 is responsible for managing communication data to generate a gateway routing database, and derive the communication database and communication matrix at the whole vehicle level and controller level. The present invention can solve the problems of difficult version management of vehicle bus communication protocols, time-consuming and labor-intensive traditional troubleshooting methods when database signal conflicts occur, and at the same time, using the reuse and management functions of the network architecture platform database can improve the work efficiency of network designers and reduce the incidence of low-level human errors. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0033] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0034] Figure 1 An architectural diagram of a vehicle bus communication data design method provided by an embodiment of the present invention;

[0035] Figure 2 A flowchart of a model structure tree for constructing and managing multi-level classification management provided by an embodiment of the present invention;

[0036] Figure 3 A flowchart for managing messages and referenced signals in a message database according to vehicle function implementation requirements provided in an embodiment of the present invention;

[0037] Figure 4 A schematic diagram of a routing table in a routing table database provided in an embodiment of the present invention;

[0038] Figure 5 A schematic diagram of a vehicle bus communication data design device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0039] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative effort belong to the scope of protection of the present application.

[0040] It should be noted that in this document, the terms "comprises", "comprising", or any other variant thereof are intended to cover non-exclusive inclusions, so that a process, method, article, or apparatus that comprises a list of elements does not only include those elements, but also includes other elements not explicitly listed, or further includes inherent elements of such a process, method, article, or apparatus. Without more limitations, an element defined by the statement "comprises a" does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0041] Embodiment 1

[0042] The embodiments of the present application provide a vehicle-mounted bus communication data design method, which sequentially manages four levels of structures, signals, messages and communication data of vehicle communication to realize auxiliary vehicle-mounted bus communication data design and provide effective assistance for vehicle-mounted bus communication data design.

[0043] Referring to Figure 1 The vehicle-mounted bus communication data design method of the embodiments of the present application comprises:

[0044] At the layer L1, a model structure tree of multi-level classification management is constructed and managed, and the levels of the model structure tree comprise a network architecture, a controller list, a routing table, a network topology diagram and a variant list.

[0045] Referring to Figure 2 The construction of the model structure tree of multi-level classification management at the layer L1 specifically comprises the following steps:

[0046] S101: One-key quick creation of a framework of the model structure tree, wherein the framework comprises a network architecture, a controller list, a routing table, a network topology diagram and a variant list.

[0047] S102: Design of a platform-level communication database under the network architecture level and design of a special vehicle communication database suitable for a special vehicle under the level of the variant list.

[0048] S103: Manual creation of all network segments and controllers of the whole vehicle and setting of attributes of the network segments and the controllers.

[0049] The attribute of the network segment includes a network segment name, a protocol item to be followed, a baud rate setting, a network management setting, a network segment version, an associated ECU (Electronic Control Unit) setting, a signal arrangement mode, and a first remark. The protocol item to be followed includes a standard frame, an extended frame, and a J1939 option; the network management setting includes AUTOSAR (Automotive Open System Architecture) and OSEK (opensystems and the corresponding interfaces for automotive electronics); and the signal arrangement mode includes Intel and Motorola.

[0050] The attribute of the controller includes a controller name, whether BootLoader is supported, a communication route setting, an associated network segment setting, and a second remark.

[0051] S104: An association between the network segment and the CAN channel of the controller is established at the network segment level or the controller level.

[0052] S105: An association between the network segment and the CAN channel of the controller is displayed in a graphical form at the network topology graph level, so as to intuitively and conveniently check the correctness of the association in S104.

[0053] S106: An association between a variant package and a controller is established at the variant list level.

[0054] The layer L2 is responsible for managing a signal database, and the management includes defining signal type attributes and signal attributes in the signal database. In a specific implementation process, communication requirements of all controllers are summarized, signal type attributes and signal attributes required by the communication requirements are created, and corresponding signal attributes are quickly added in the signal database by referencing the signal type attributes.

[0055] The layer L2 is mainly responsible for defining signal type attributes and signal attributes in the signal database. The signal type attributes include a signal type name, a length, a unit, a signal value type, an accuracy, an offset, a signal value definition, and a third remark column; and the signal attributes include a signal name, a referenced signal type, a length, a unit, a signal value type, an accuracy, an offset, an initial value, an invalid value, a signal value definition, and a fourth remark column. The signal value type option includes a signed type, an unsigned type, a single-precision floating-point type, and a double-precision floating-point type.

[0056] The layer L3 is responsible for managing the message database, and the management includes: managing the messages and the referenced signals in the message database according to the implementation requirements of the whole vehicle functions;

[0057] In the implementation process, referring to Figure 3 As shown in the layer L3, the messages and the referenced signals in the message database are managed according to the implementation requirements of the whole vehicle functions, and the specific steps include the following steps:

[0058] S301: Selecting the sending controller in the network segment in the message database, creating the corresponding message and the detailed attributes of the message; wherein the detailed attributes of the message include: message name, message type, message ID, data field length, sending type, sending period, sending controller, network management message flag, diagnostic message type and the fifth note column. Wherein the message type includes: standard frame message, extended frame message and J1939 message; the sending type represents the condition of triggering sending, including: periodic sending, event type sending, enabling type sending, periodic enabling type sending and periodic event type sending; the diagnostic message type includes: non-diagnostic message, diagnostic request message, diagnostic response message and function addressing message.

[0059] S302: Directly referencing the required target signal from the signal database, and arranging the position of the target signal.

[0060] S303: According to the implementation requirements of the whole vehicle functions, associating each message of the sending network segment to the target network segment;

[0061] S304: According to the communication requirements of the sending controller, adding the information of the corresponding receiving controller in the corresponding signal attribute.

[0062] Preferably, the network segment and the controller support one-key mirroring function, which is used to copy the message definition of the existing network segment and controller to the new vehicle model.

[0063] The layer L4 is responsible for managing the communication data, and the management tasks include: generating the routing table database of the gateway type controller, and exporting the communication database and the communication matrix of the whole vehicle level and the controller level.

[0064] In the layer L4, after selecting and activating the specific variant package in the variant list, the routing table database of the gateway type controller is generated, and the export of the communication database and the communication matrix is supported.

[0065] As shown in the figure, Figure 4 The content of the routing table database includes: sending end communication data module, receiving end communication data module and general data module;

[0066] The content of the sending end communication data module includes: sending network segment name, signal name, message name and message ID;

[0067] The content of the receiving end communication data module includes: receiving network segment name, signal name, message name and message ID;

[0068] The content of the general data module includes: routing mode and controller information; the routing mode includes direct message routing and signal routing.

[0069] The communication database and communication matrix are divided into vehicle-level and controller-level. The vehicle-level communication database serves as the basis for communication between internal designers; the controller-level communication database is used to guide controller suppliers in development.

[0070] Example 2

[0071] An embodiment of the present invention provides a vehicle bus communication data design device, comprising: at least one processing unit, the processing unit being connected to at least one storage unit via a bus unit, the storage unit storing a computer program, wherein the computer program, when executed by the processing unit, implements the vehicle bus communication data design method, wherein communication structure, signal, message and communication data are managed in an orderly manner in four levels, and the levels and management tasks include: constructing and managing a multi-level classification management model structure tree at layer L1, wherein the levels of the model structure tree include: network architecture, controller list, routing table, network topology diagram and variant list; layer L2 is responsible for managing a signal database, wherein signal type attributes and signal attributes are defined in the signal database; layer L3 manages messages and referenced signals in a message database according to the requirements of vehicle function implementation; layer L4 is responsible for managing communication data to generate a gateway routing database, and derive vehicle-level and controller-level communication databases and communication matrices.

[0072] Example 3

[0073] An embodiment of the present invention provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processing unit, the vehicle bus communication data design method is implemented, and communication structure, signal, message and communication data are managed in an orderly manner at four levels. The levels and management tasks include: constructing and managing a model structure tree for multi-level classification management at layer L1, and the levels of the model structure tree include: network architecture, controller list, routing table, network topology diagram and variant list; layer L2 is responsible for managing a signal database, and defining signal type attributes and signal attributes in the signal database; at layer L3, messages and referenced signals are managed in a message database according to the requirements of vehicle function implementation; layer L4 is responsible for managing communication data to generate a gateway routing database, and derive vehicle-level and controller-level communication databases and communication matrices.

[0074] Those skilled in the art can clearly understand the present application by the description of the above embodiments, the present application can be realized by software and necessary general hardware, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as a floppy disk, a read-only memory (ROM), a random access memory (RAM), a FLASH, a hard disk or an optical disk, etc., including a plurality of instructions to make an electronic device (which can be a mobile phone, a personal computer, a server or a network device, etc.) execute the method described in each embodiment of the present application.

[0075] In the embodiments provided by the present application, it should be understood that the disclosed structure and method can be implemented in other ways. For example, the above-described structural embodiments are only schematic. The division of the units is only a logical function division. There can be another division manner in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, structures or units, and can be electrical, mechanical or in other forms.

[0076] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0077] In addition, each functional unit in the various embodiments of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of software functional unit.

[0078] The above description is only a specific embodiment of the present application, which enables those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to these embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A vehicle bus communication data design method, characterized in that: The structure, signals, messages, and communication data of vehicle communications are managed in an orderly manner at four levels to assist in the design of vehicle bus communication data. The levels and their management tasks include: Construct and manage a multi-level classification management model structure tree at layer L1. The levels of the model structure tree include: network architecture, controller list, routing table, network topology map, and variant list; Layer L2 is responsible for managing the signal database, in which signal type attributes and signal properties are defined; At layer L3, messages and referenced signals are managed in the message database according to the vehicle function requirements; Layer L4 is responsible for managing communication data, selecting and activating specific variant packages in the variant list to generate the gateway routing database for the dedicated car, and exporting the communication database and communication matrix at the vehicle level and controller level.

2. The vehicle bus communication data design method according to claim 1, characterized in that: The construction of a multi-level classification management model structure tree at layer L1 includes the following steps: S101: quickly create a model structure tree framework with one click, the framework including multiple levels of network architecture, controller list, routing table, network topology diagram and variant list; S102: Design a platform-level communication database at the network architecture level, and design a dedicated car communication database suitable for dedicated cars at the variant list level; S103: Manually create all network segments and controllers of the vehicle, and set the properties of the network segments and controllers; S104: establishing an association relationship between the network segment and the CAN channel of the controller at a network segment level or a controller level; S105: Displaying the association relationship between the network segment and the controller CAN channel in a graphical form in a network topology layer, so as to intuitively and conveniently verify the correctness of the association relationship in S104; S106: Establishing an association relationship between the variant package and the controller in the variant list hierarchy.

3. The vehicle bus communication data design method according to claim 2, characterized in that: The attributes of the network segment include the network segment name, protocol items, baud rate settings, network management settings, network segment version, associated ECU settings, signal arrangement method and first note; the attributes of the controller include: controller name, whether to support BootLoader, communication route settings, associated network segment settings and second note.

4. The vehicle bus communication data design method according to claim 1, characterized in that: The layer L2 summarizes the communication requirements of all controllers, creates the signal type attributes and signal attributes required by the communication requirements, and quickly adds the corresponding signal attributes in the signal database by referencing the signal type attributes.

5. The vehicle bus communication data design method according to claim 4, characterized in that: The signal type attributes include signal type name, length, unit, signal value type, precision, offset, signal value definition and the third remarks column; the signal attributes include signal name, referenced signal type, length, unit, signal value type, precision, offset, initial value, invalid value, signal value definition and the fourth remarks column.

6. The vehicle bus communication data design method according to claim 1, characterized in that: The management of messages and referenced signals in the message database according to the vehicle function implementation requirements includes the following steps: S301: Select the network segment where the sending controller is located, create the corresponding message and detailed attributes of the message; S302: directly referencing the required target signal from the signal database and arranging the position of the target signal; S303: Associating each message of the sending network segment with the target network segment according to the vehicle function implementation requirements; S304: According to the communication requirements of the sending controller, the corresponding receiving controller information is added to the corresponding signal attributes.

7. The vehicle bus communication data design method according to claim 1, characterized in that: The routing table database content includes: sending end communication data module, receiving end communication data module and general data module; The contents of the transmitting end communication data module include: the sending network segment name, signal name, message name and message ID; The content of the receiving end communication data module includes: receiving network segment name, signal name, message name and message ID; The content of the general data module includes: routing mode and controller information; the routing mode includes direct message routing and signal routing.

8. A vehicle bus communication data design device, characterized in that: The vehicle bus communication data design method comprises at least one processing unit connected to at least one storage unit via a bus unit, wherein the storage unit stores a computer program, and when the computer program is executed by the processing unit, the vehicle bus communication data design method according to any one of claims 1 to 7 is implemented.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processing unit, the vehicle bus communication data design method according to any one of claims 1 to 7 is implemented.

Images