Communication design method and device for multi-variant vehicle model network

Abstract

The invention discloses a communication design method and device for a multi-variant vehicle type network, and the method comprises the steps: building an ECU variant of each ECU use scene according to each ECU of the vehicle type and the corresponding ECU use scene for each vehicle type; based on each ECU variant, each variant unit corresponding to each vehicle type is established; based on each variant unit corresponding to each vehicle type, establishing each variant combination corresponding to each vehicle type; and under each variant combination, configuring an effective sending message and an effective receiving signal corresponding to each ECU of each vehicle type to obtain each target variant combination corresponding to each vehicle type, and storing the target variant combination in a pre-constructed redundant database. Therefore, each ECU is divided and managed in a unified manner according to different use scenes under different vehicle types, and the problem that the error rate of network design is high is effectively reduced.

Description

Technical Field

[0001] The present application relates to the field of intelligent network automobile technology, and in particular to a communication design method and device for a multi-variant vehicle model network. Background Art

[0002] At present, in order to meet market demand, major car companies have basically launched high, medium and low-end versions of vehicles, which has also led to the design scenario of multiple model variants under each model. Among them, model variants refer to the same model series, although there will be the same platform and design, there will be different models or versions in some aspects. However, for different variants of the same model, there will be the following characteristics: the basic architecture of the in-vehicle network design and network communication are basically the same, and some functions are adaptively increased or reduced according to different variant models.

[0003] Therefore, in response to scenarios with different variants of vehicle models, network engineers generally need to design a complete network communication solution for each variant of the vehicle model when doing communication design, and then reflect the functional design for the current variant of the vehicle model in each communication solution, which easily leads to a large amount of duplication of work between different variants of the vehicle model. In addition, the common functional design of the variant models needs to be redesigned once in each communication solution, and if a common functional design needs to be modified, it needs to be modified in each variant of the vehicle model. This undoubtedly increases the workload and energy of network engineers, and also increases the error rate of network design. Summary of the invention

[0004] Based on the above-mentioned deficiencies of the prior art, the present application provides a communication design method and device for a multi-variant vehicle model network to solve the problem of high error rate in network design.

[0005] In order to achieve the above objectives, this application provides the following technical solutions:

[0006] The first aspect of the present application provides a communication design method for a multi-variant vehicle model network, comprising:

[0007] For each vehicle type, respectively, according to each ECU of the vehicle type and its corresponding ECU usage scenario, establish ECU variants of each ECU usage scenario;

[0008] Based on each of the ECU variants, establishing variant units corresponding to each of the vehicle type;

[0009] Based on each variant unit corresponding to each vehicle type, establishing each variant combination corresponding to each vehicle type; wherein the variant combination at least includes any one variant unit in the ECU variant;

[0010] Under each of the variant combinations, configure a valid sending message and a valid receiving signal corresponding to each of the ECUs of each vehicle type, to obtain each target variant combination corresponding to each of the vehicle type;

[0011] Each target variant combination corresponding to each vehicle type is stored in a pre-constructed redundant database.

[0012] Optionally, in the above-mentioned communication design method for a multi-variant vehicle model network, the method for constructing the redundant database includes:

[0013] Get communication data for each vehicle type;

[0014] Establishing a communication relationship between each of the vehicle types according to the communication data of each of the vehicle types;

[0015] Based on the communication relationship between each of the vehicle types, a redundant database is established.

[0016] Optionally, in the above-mentioned communication design method for a multi-variant vehicle model network, the step of establishing each variant unit corresponding to each vehicle model type based on each ECU variant includes:

[0017] Obtaining the differentiating features between each of the vehicle types;

[0018] Under each of the ECU variants, variant units corresponding to each of the vehicle types are established according to the differential functions existing between each of the vehicle types.

[0019] Optionally, in the above-mentioned communication design method for a multi-variant vehicle model network, under each of the variant combinations, configuring a valid sending message and a valid receiving signal corresponding to each of the ECUs of each of the vehicle model types to obtain each target variant combination corresponding to each of the vehicle model types includes:

[0020] Under each of the variant combinations, according to the differential functions between each of the vehicle types, determining the valid sending message and the valid receiving signal corresponding to each of the ECUs of each of the vehicle types;

[0021] Based on the valid sending messages and valid receiving signals corresponding to each ECU of each vehicle type, each variant combination corresponding to each vehicle type is configured to obtain each target variant combination corresponding to each vehicle type.

[0022] Optionally, in the above-mentioned communication design method for a multi-variant vehicle model network, the method further includes:

[0023] When receiving a vehicle model editing request, display the editing interface to the user;

[0024] According to the vehicle type selected in the editing interface, the target variant combination of the current vehicle type is switched to each of the target variant combinations of the vehicle type.

[0025] A second aspect of the present application provides a communication design device for a multi-variant vehicle model network, comprising:

[0026] A variant establishing unit, for establishing, for each vehicle type, ECU variants of each ECU usage scenario according to each ECU of the vehicle type and its corresponding ECU usage scenario;

[0027] A first establishing unit, configured to establish, based on each of the ECU variants, each variant unit corresponding to each of the vehicle type;

[0028] A combination establishing unit, used for establishing each variant combination corresponding to each vehicle type based on each variant unit corresponding to each vehicle type; wherein the variant combination at least includes any one variant unit in the ECU variant;

[0029] A configuration unit, configured to configure, under each of the variant combinations, a valid sending message and a valid receiving signal corresponding to each of the ECUs of each of the vehicle type, to obtain each target variant combination corresponding to each of the vehicle type;

[0030] The storage unit is used to store each target variant combination corresponding to each vehicle type in a pre-constructed redundant database.

[0031] Optionally, in the above-mentioned communication design device for a multi-variant vehicle model network, it further includes:

[0032] A data acquisition unit, used to acquire communication data of each vehicle type;

[0033] A relationship establishing unit, used for establishing a communication relationship between each of the vehicle type types according to the communication data of each of the vehicle type types;

[0034] The second establishing unit is used to establish a redundant database based on the communication relationship between each of the vehicle types.

[0035] Optionally, in the above-mentioned communication design device for a multi-variant vehicle model network, the first establishing unit includes:

[0036] A function acquisition unit, used for acquiring the differential functions between each type of vehicle;

[0037] The third establishing unit is used to establish each variant unit corresponding to each vehicle type according to the differential functions existing between each vehicle type under each ECU variant.

[0038] Optionally, in the above-mentioned communication design device for a multi-variant vehicle model network, the configuration unit includes:

[0039] A determination unit, configured to determine, under each of the variant combinations, a valid transmission message and a valid reception signal corresponding to each of the ECUs of each of the vehicle types according to the differential functions between the vehicle types;

[0040] The message configuration unit is used to configure each variant combination corresponding to each vehicle type based on the valid sending message and the valid receiving signal corresponding to each ECU of each vehicle type, so as to obtain each target variant combination corresponding to each vehicle type.

[0041] Optionally, in the above-mentioned communication design device for a multi-variant vehicle model network, it further includes:

[0042] A display unit, used to display an editing interface to a user when a vehicle model editing request is received;

[0043] A switching unit is used to switch the target variant combination of the current vehicle type to each of the target variant combinations of the vehicle type according to the vehicle type selected in the editing interface.

[0044] The present application provides a communication design method for a multi-variant vehicle network, which establishes ECU variants of each ECU usage scenario for each vehicle type according to each ECU of the vehicle type and its corresponding ECU usage scenario, then establishes each variant unit corresponding to each vehicle type based on each ECU variant, then establishes each variant combination corresponding to each vehicle type based on each variant unit corresponding to each vehicle type, wherein the variant combination includes at least any one variant unit in the ECU variant, and then configures each ECU of each vehicle type under each variant combination to send a valid message and receive a valid signal, obtain each target variant combination corresponding to each vehicle type, and finally stores each target variant combination corresponding to each vehicle type in a pre-built redundant database. Thus, by dividing and uniformly managing each ECU according to different usage scenarios under different vehicle types, it also realizes the configuration of common public data between different vehicle types, thereby effectively reducing the use of users with different configuration vehicle design requirements, and greatly reducing the workload and time of network engineers, and effectively reducing the problem of high error rate in network design. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in 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 embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0046] Figure 1 A flow chart of a communication design method for a multi-variant vehicle model network provided in an embodiment of the present application;

[0047] Figure 2 A flowchart of a method for establishing a variant unit provided in an embodiment of the present application;

[0048] Figure 3 A flowchart of a method for configuring a target variant combination provided in an embodiment of the present application;

[0049] Figure 4 A flowchart of a method for constructing a redundant database provided in an embodiment of the present application;

[0050] Figure 5 A flowchart of a display method of a variant combination provided in another embodiment of the present application;

[0051] Figure 6 A schematic diagram of a message and signal design provided in an embodiment of the present application;

[0052] Figure 7 A schematic structural diagram of a communication design device for a multi-variant vehicle model network provided in another embodiment of the present application. DETAILED DESCRIPTION

[0053] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0054] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0055] The present application embodiment provides a communication design method for a multi-variant vehicle model network, such as Figure 1 As shown, the specific steps include:

[0056] S101. For each vehicle type, according to each ECU of the vehicle type and its corresponding ECU usage scenario, establish an ECU variant for each ECU usage scenario.

[0057] It is understandable that in the embodiments of the present application, the communication design is mainly for high-end models, medium-end models and low-end models. It should be noted that in the process of network design, different ECUs have different functions. Therefore, when designing models, appropriate ECU variants will be selected according to the needs and positioning of different models to achieve various functions and performance requirements of the vehicle. Therefore, in high-end, medium-end and low-end models, each ECU and its corresponding usage scenarios may have different configurations. Therefore, it is necessary to establish ECU variants for each ECU usage scenario based on each ECU of different vehicle types and their corresponding ECU usage scenarios.

[0058] Among them, ECU variants refer to the functional differences between different electronic control units on the vehicle.

[0059] For example, in the use scenario of the window control system, the ECU that controls the automatic lifting window is usually called PWCU, and the ECU that controls the anti-pinch protection is usually called APCU. Assuming that high-end models support automatic lifting window PWCU and anti-pinch protection APCU, while mid-range and low-end models only support automatic lifting window PWCU, the ECU variants of high-end models in the use scenario of the window control system are PWCU and APCU, and the ECU variants of mid-range and low-end models in the use scenario of the window control system are PWCU.

[0060] For example, in the use scenario of the automatic cruise control system, the ECU of the automatic cruise control is usually called ACC. Mid- and high-end models generally have the function of automatic cruise control, while low-end models do not have the function of automatic cruise control. At this time, according to the variant design, an automatic cruise variant needs to be established, under which there is a variant unit called ACC, indicating that the automatic cruise function is supported. Therefore, the ECU variant of high-end and mid-end models in the use scenario of the automatic cruise control system is ACC, and low-end models do not have ECU variants in the use scenario of the automatic cruise control system.

[0061] S102: Based on each ECU variant, establish each variant unit corresponding to each vehicle type.

[0062] Specifically, in the process of multi-variant network design, it is precisely because of different ECU variants that the configurations of high-end, mid-end and low-end models are different. Therefore, in the embodiment of the present application, it is necessary to establish respective variant units according to the various ECU variants in the same ECU usage scenario of high-end, mid-end and low-end models.

[0063] Based on the example in S101 above, reference may be made to the different variants and their variant units shown in Table 1:

[0064] Table 1

[0065]

[0066]

[0067] It should be noted that the contents shown in Table 1 are only for illustration.

[0068] Therefore, combined with the contents shown in Table 1, it can be seen that in the use scenario of the window control system, the ECU variants involved in the high-end models are PWCU and APCU, and the ECU variants involved in the mid-end and low-end models are only PWCU. Therefore, the variant unit of the high-end models in the use scenario of the window control system is PWCU+APCU, while the variant unit of the mid-end and low-end models in the use scenario of the window control system is only PWCU. In the use scenario of the automatic cruise control system, the ECU variant of the high-end and mid-end models in the use scenario of the automatic cruise control system is ACC, and the low-end models have no ECU variant in the use scenario of the automatic cruise control system. Therefore, the variant unit of the high-end and mid-end models in the use scenario of the automatic cruise control system is ACC, while the low-end models have no variant unit in the use scenario of the automatic cruise control system, and only PWCU.

[0069] Therefore, in the embodiment of the present application, the variant units under each variant scenario can be divided and set according to steps S101 and S102, and different variant units under multiple scenarios such as window control systems and automatic cruise control systems can be obtained. Therefore, by designing a combination of variants and the variant units under them, and then configuring the variant units according to the requirements of different vehicle models, it is possible to very conveniently manage variant schemes under high, medium and low-end vehicle models, thereby reducing the problem of high error rate in network design.

[0070] Optionally, in another embodiment of the present application, a specific implementation of step S102 is as follows: Figure 2 As shown, the following steps are included:

[0071] S201. Obtain the differential functions between each vehicle type.

[0072] It should be noted that since different vehicle types have some differences in the functions of their ECU variant units, in the embodiment of the present application, different variant units are established based on the differential functions existing in high-end, mid-end and low-end vehicle types. Therefore, it is necessary to obtain the differential functions between each vehicle type in advance.

[0073] For example, in the air-conditioning control system, high-end models have the functions of automatic temperature control system ZDCU and advanced filter AACU, while mid-range and low-end models only have the function of manual temperature control system SDCU.

[0074] S202: Under each ECU variant, establish variant units corresponding to each vehicle type according to the differential functions existing between each vehicle type.

[0075] Specifically, since high-end, mid-end and low-end models have different functions in the same scenario, the combinations of ECU variants used in the same scenario are different. Therefore, in order to very conveniently manage the variant schemes under high, medium and low-end models and make the network design flexible and convenient, in an embodiment of the present application, each variant unit corresponding to each model type will be established according to the differential functions between each model type.

[0076] For example, for the example in step S201 above, in the use scenario of the air-conditioning control system, the variant unit of the high-end model is ZDCU+AACU, and the variant unit of the mid-end and low-end models is SDCU.

[0077] S103: Based on each variant unit corresponding to each vehicle type, establish each variant combination corresponding to each vehicle type.

[0078] The variant combination may include any variant unit in the ECU variant.

[0079] It should be emphasized that the configuration variants and variant units are used to distinguish the differences in ECUs for high-end, mid-end and low-end models in different functional scenarios. Therefore, for the differences in ECUs, the embodiments of the present application are based on a combination of multiple variants and their variant units to form a "variant combination" for high-end, mid-end and low-end models. Therefore, the "variant combination" is based on the level of models with different configurations. Different variant units are configured for models with different configurations, thereby forming a complete model variant combination with differences.

[0080] For example, for the example in step S101 above, the functions supported by high-end models are automatic window lifting + anti-pinch protection + automatic cruise control in the window control system, the functions supported by mid-end models are automatic window lifting + automatic cruise control in the window control system, and the function supported by low-end models is automatic window lifting in the window control system.

[0081] Therefore, the main purpose of the variant combination is to combine the variant units under each vehicle model to form a complete vehicle model configuration. Therefore, after the combination of different variant units, the example in the above step S101 can obtain three sets of variant combination solutions as shown in Table 2:

[0082] Table 2

[0083]

[0084]

[0085] It should be noted that the contents shown in Table 1 are only for illustration. Therefore, combined with the contents shown in Table 2, three sets of variant combination schemes can be obtained, corresponding to the three models of high, medium and low configurations: high configuration model: PWCU+APCU+ACC, medium configuration model: PWCU+ACC, low configuration model: PWCU.

[0086] Since low-end models do not have the automatic cruise function, when selecting the automatic cruise variant, the automatic cruise ECU can be omitted for the combination of low-end models.

[0087] Therefore, it should be noted that by configuring different variant combinations of high, medium and low-end models, in the subsequent design of the on-board communication database, direct switching of high, medium and low-end models and configuration of specific ECUs and data for each model can be achieved. As a result, network engineers no longer need to maintain multiple copies of data, and the communication design of network data can be realized directly under one engineering database, thereby greatly improving engineers' database management work for different models and different configurations.

[0088] S104. Under each variant combination, configure a valid sending message and a valid receiving signal corresponding to each ECU of each vehicle type to obtain each target variant combination corresponding to each vehicle type.

[0089] It should be emphasized that in order to be more adaptable to high and medium configuration models, different messages under the same ECU may send different data, and each data represents a different data meaning, and the same ECU may also receive different signals, and each signal also represents a unique physical meaning. Even if high and medium configuration models can already distinguish different usage scenarios at the ECU level, for the data sent and received under the same ECU, there may be differences in the sent and received data under different configuration models. These differences are also the key to whether the functions of the ECU under different vehicle configurations are the same. Therefore, for this situation, in the embodiment of the present application, it is possible to rely on the above-mentioned established variant combination to directly implement variant distinction for the sent messages and received signals under the ECU for different vehicle configurations, that is, under different variant combinations, it is possible to configure which specific signals a certain ECU under the current variant combination can send or receive. Therefore, the message that is not configured to be sent under the current variant combination will not be sent under the vehicle model corresponding to the current variant combination, and the signal under the message will not be sent by the ECU, so that the effective sending message and effective receiving signal that have been configured under different variant combinations of high, medium and low configuration models can be obtained.

[0090] Optionally, in another embodiment of the present application, a specific implementation of step S104 is as follows: Figure 3 As shown, the following steps are included:

[0091] S301. Under each variant combination, according to the differential functions between each vehicle type, determine the valid sending message and the valid receiving signal corresponding to each ECU of each vehicle type.

[0092] It should be noted that the same ECU may exist for high-end and medium-end models, but the message sent and the received signal of the same ECU may be different according to the differential functions between high-end, medium-end and low-end models. Therefore, in the embodiment of the present application, under each variant combination corresponding to high-end, medium-end and low-end models, the valid message sent and the valid received signal corresponding to each ECU of each model type are determined according to the differential functions between each model type.

[0093] For example, under the variant combination of audio system control, based on the audio difference functions between high, medium and low configurations, it can be determined that the valid transmission message corresponding to the high configuration model can be temperature setting, wind speed setting, etc., and the valid receiving signal can be indoor temperature, humidity, etc. The valid transmission message corresponding to the medium configuration model can be temperature setting, wind speed setting, and the valid receiving signal can be indoor temperature. The valid transmission message corresponding to the low configuration model can be temperature setting, and there is no valid receiving signal.

[0094] S302. Based on the valid sending messages and valid receiving signals corresponding to each ECU of each vehicle type, each variant combination corresponding to each vehicle type is configured to obtain each target variant combination corresponding to each vehicle type.

[0095] It can be understood that after determining the valid sending messages and valid receiving signals corresponding to each ECU of each vehicle type, it is possible to configure each variant combination based on the valid sending messages and valid receiving signals corresponding to each ECU of high, medium and low configurations. When the configuration is completed, the vehicle model corresponding to each variant combination will only receive the configured signals and send the configured messages under each ECU. For the signals that the ECU under each variant combination does not need to receive and the messages that it does not need to send, the ECU under each variant combination will not receive or send them.

[0096] Therefore, through variant control at the message and signal levels, network engineers can effectively realize the control and management of multi-variant vehicle models at the level of ECU sending messages and receiving signals. Network engineers no longer need to establish ECUs for sending and receiving different message signals for separate processing, which can effectively improve the efficiency of engineers in designing network communications.

[0097] S105: Store each target variant combination corresponding to each vehicle type in a pre-built redundant database.

[0098] Specifically, after designing the target variant combination, i.e., the network data, under different vehicle models, the designed target variant components need to be stored in a pre-built redundant database, so that the required database files can be exported under different vehicle models, wherein the database files may include the designed target variant components, variant units and variants.

[0099] Optionally, the present application embodiment provides a method for constructing a redundant database, such as Figure 4 As shown, the following steps are included:

[0100] S401. Acquire communication data of each vehicle type.

[0101] Specifically, the communication data may include data such as network segments, messages, and signal libraries. Since there are differences between each type of vehicle, and the communication data of different models may change over time, in order to better provide data support for different vehicles, in an embodiment of the present application, it is necessary to obtain the communication data of each type of vehicle in advance to understand the communication status between each ECU.

[0102] S402: Establish a communication relationship between each vehicle type based on the communication data of each vehicle type.

[0103] Specifically, by establishing a communication relationship between each vehicle type, information sharing and interconnection can be achieved, and the communication relationship between different vehicle types can achieve system optimization and collaborative work.

[0104] S403: Establish a redundant database based on the communication relationship between each vehicle type.

[0105] Specifically, establishing a redundant database based on communication relationships can effectively ensure the security and availability of communication data between different vehicle types, improve the stability and reliability of the system, ensure that vehicle data will not be lost or damaged during communication, and ensure the normal operation of the vehicle system, thereby improving user experience and service quality.

[0106] Optionally, after configuring each variant combination of vehicle type, each variant combination of vehicle type can also be displayed on the system to obtain specific configuration information of each vehicle type. Therefore, in another embodiment of the present application, a method for displaying variant combinations is also provided, such as Figure 5 The content shown includes the following steps:

[0107] S501: When a vehicle model editing request is received, an editing interface is displayed to the user.

[0108] It is understandable that when a network engineer receives an editing request for a high, medium or low-end vehicle model, an editing interface can be displayed to the user, which may include the target variant combination, variant unit, variant and basic vehicle model information.

[0109] S502 . According to the vehicle type selected in the editing interface, the target variant combination of the current vehicle type is switched to each target variant combination of the vehicle type.

[0110] Specifically, after the editing interface is displayed to the network engineer, the network engineer can select different vehicle models in the drop-down box. At this time, the system will respond according to the vehicle model type selected by the network engineer in the editing interface, that is, the target variant combination of the current vehicle model type will be switched to the target variant combinations of the vehicle model type selected by the network engineer for display, so that the network engineer can make corresponding edits.

[0111] Optionally, the vehicle type selection can be presented on the editing interface in the form of a form, drop-down menu, checkbox, etc., and the network engineer can edit the vehicle type accordingly as needed. The editing interface should be designed to be simple and intuitive, easy for users to operate, and provide a button to confirm submission after the user completes the editing to ensure that the user's editing operations can be correctly saved and updated.

[0112] Therefore, based on the above-provided method, when network engineers are designing the network for high, medium and low-end models, they can switch and manage the data of different variant models at will, without having to maintain multiple copies of data for different configuration models, which greatly facilitates the maintenance and design costs of the vehicle database. For example, the existing window control system supports the functions of automatic window lifting (corresponding ECU is PWCU) and anti-pinch protection (corresponding ECU is APCU), and the automatic cruise system supports the function of adaptive cruise (corresponding ECU is ACC, where ACC sends Msg1 to indicate basic ACC, sends Msg2 to indicate full-speed ACC, receives sig1 to indicate support for automatic following, and receives sig2 to indicate support for automatic following). The functions supported by high-end models are automatic window lifting + anti-pinch protection + full-speed ACC + automatic following, the functions supported by mid-end models are automatic window lifting + basic ACC + no support for automatic following, and the low-end models support automatic window lifting.

[0113] Then the designs of the variants and variant units provided in the embodiments of the present application are as follows:

[0114] Variant 1: Window control system, its variant units are: variant unit 1 (PWCU+APCU), variant unit 2 (PWCU).

[0115] Variant 2: Automatic cruise control system, whose variant units are: Variant unit 1 (ACC).

[0116] According to the designed variant units, different variant combinations of different models are established by selecting different variant units, as follows:

[0117] Variant combination 1: For high-end models, the selected variant units are: variant unit 1 of the window control system + variant unit 1 of the automatic cruise control system.

[0118] Variant combination 2: For mid-range models, the selected variant units are: variant unit 2 of the window control system + variant unit 1 of the automatic cruise control system.

[0119] Variant combination three: low-end model, the selected variant units are: variant unit 2 of the window control system, and variant unit without the automatic cruise system.

[0120] According to the above requirements, for the automatic cruise control systems of high-end and mid-end models, due to the differences in different configuration functions, it is necessary to make special configurations for the ECU receiving and sending signals of high-end and mid-end models. Specifically, in the variant combination of high-end models, it is set to send message Msg2, not send message Msg1, receive signal sig1, and not receive signal sig2. In the variant combination of mid-end models, it is set to send message Msg1, not send Msg2, receive signal sig2, and not receive signal sig1. For specific configurations of sending messages and receiving signals, please refer to Figure 6 shown.

[0121] The present application provides a communication design method for a multi-variant vehicle network, which establishes ECU variants of each ECU usage scenario for each vehicle type according to each ECU of the vehicle type and its corresponding ECU usage scenario, then establishes each variant unit corresponding to each vehicle type based on each ECU variant, then establishes each variant combination corresponding to each vehicle type based on each variant unit corresponding to each vehicle type, wherein the variant combination includes at least any one variant unit in the ECU variant, and then configures each ECU of each vehicle type under each variant combination to send a valid message and receive a valid signal, obtain each target variant combination corresponding to each vehicle type, and finally stores each target variant combination corresponding to each vehicle type in a pre-built redundant database. Thus, by dividing and uniformly managing each ECU according to different usage scenarios under different vehicle types, it also realizes the configuration of common public data between different vehicle types, thereby effectively reducing the use of users with different configuration vehicle design requirements, and greatly reducing the workload and time of network engineers, and effectively reducing the problem of high error rate in network design.

[0122] Another embodiment of the present application provides a communication design device for a multi-variant vehicle model network, such as Figure 7 As shown, it includes the following units:

[0123] The variant establishing unit 701 is used to establish ECU variants of each ECU usage scenario for each vehicle type according to each ECU of the vehicle type and its corresponding ECU usage scenario.

[0124] The first establishing unit 702 is used to establish each variant unit corresponding to each vehicle type based on each ECU variant.

[0125] The combination establishing unit 703 is used to establish each variant combination corresponding to each vehicle type based on each variant unit corresponding to each vehicle type, wherein the variant combination at least includes any variant unit in the ECU variant.

[0126] The configuration unit 704 is used to configure the valid sending message and the valid receiving signal corresponding to each ECU of each vehicle type under each variant combination, so as to obtain each target variant combination corresponding to each vehicle type.

[0127] The storage unit 705 is used to store each target variant combination corresponding to each vehicle type in a pre-built redundant database.

[0128] It should be noted that the specific working process of the above-mentioned units in the embodiment of the present application can refer to steps S101 to S105 in the above-mentioned method embodiment, and will not be repeated here.

[0129] Optionally, in another embodiment of the present application, a communication design device for a multi-variant vehicle model network further includes:

[0130] The data acquisition unit is used to acquire the communication data of each vehicle type.

[0131] The relationship establishing unit is used to establish a communication relationship between each vehicle type according to the communication data of each vehicle type.

[0132] The second establishing unit is used to establish a redundant database based on the communication relationship between each vehicle type.

[0133] Optionally, in a communication design device for a multi-variant vehicle model network provided by another embodiment of the present application, the first establishing unit 702 includes:

[0134] The function acquisition unit is used to acquire the differential functions between each vehicle type.

[0135] The third establishing unit is used to establish each variant unit corresponding to each vehicle type according to the differential functions existing between each vehicle type under each ECU variant.

[0136] Optionally, in a communication design device for a multi-variant vehicle model network provided in another embodiment of the present application, the configuration unit 704 includes:

[0137] The determination unit is used to determine the valid sending message and the valid receiving signal corresponding to each ECU of each vehicle type under each variant combination according to the differential functions between each vehicle type.

[0138] The message configuration unit is used to configure each variant combination corresponding to each vehicle type based on the valid sending message and the valid receiving signal corresponding to each ECU of each vehicle type, so as to obtain each target variant combination corresponding to each vehicle type.

[0139] Optionally, in another embodiment of the present application, a communication design device for a multi-variant vehicle model network further includes:

[0140] The display unit is used to display the editing interface to the user when receiving a vehicle model editing request.

[0141] The switching unit is used to switch the target variant combination of the current vehicle type to each target variant combination of the vehicle type according to the vehicle type selected in the editing interface.

[0142] It should be noted that the specific working process of each unit provided in the above embodiments of the present application can refer to the corresponding steps in the above method embodiments, and will not be repeated here.

[0143] In summary, another embodiment of the present application provides a communication design device for a multi-variant vehicle model network. By dividing the ECU and unifying the data management under different configuration vehicle models, it is achieved that there is common public data between different configuration vehicle models, and different vehicle model variant data can be managed separately, thereby greatly reducing the problem of high error rate in network design, reducing the time and energy of network engineers in communication data design, and improving work efficiency.

[0144] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0145] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may 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 the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A communication design method for a multi-variant vehicle model network, characterized in that: include: For each vehicle type, respectively, according to each ECU of the vehicle type and its corresponding ECU usage scenario, establish ECU variants of each ECU usage scenario; Based on each of the ECU variants, establishing variant units corresponding to each of the vehicle type; Based on each variant unit corresponding to each vehicle type, establishing each variant combination corresponding to each vehicle type; wherein the variant combination at least includes any one variant unit in the ECU variant; Under each of the variant combinations, configure a valid sending message and a valid receiving signal corresponding to each of the ECUs of each vehicle type, to obtain each target variant combination corresponding to each of the vehicle type; Each target variant combination corresponding to each vehicle type is stored in a pre-constructed redundant database.

2. The method according to claim 1, characterized in that The method for constructing the redundant database comprises: Get communication data for each vehicle type; Establishing a communication relationship between each of the vehicle types according to the communication data of each of the vehicle types; Based on the communication relationship between each of the vehicle types, a redundant database is established.

3. The method according to claim 1, characterized in that The step of establishing each variant unit corresponding to each vehicle type based on each ECU variant includes: Obtaining the differentiating features between each of the vehicle types; Under each of the ECU variants, variant units corresponding to each of the vehicle types are established according to the differential functions existing between each of the vehicle types.

4. The method according to claim 3, characterized in that The method of configuring, under each of the variant combinations, a valid sending message and a valid receiving signal corresponding to each of the ECUs of each vehicle type to obtain each target variant combination corresponding to each of the vehicle type includes: Under each of the variant combinations, according to the differential functions between each of the vehicle types, determining the valid sending message and the valid receiving signal corresponding to each of the ECUs of each of the vehicle types; Based on the valid sending messages and valid receiving signals corresponding to each ECU of each vehicle type, each variant combination corresponding to each vehicle type is configured to obtain each target variant combination corresponding to each vehicle type.

5. The method according to claim 1, characterized in that: Also includes: When receiving a vehicle model editing request, display the editing interface to the user; According to the vehicle type selected in the editing interface, the target variant combination of the current vehicle type is switched to each of the target variant combinations of the vehicle type.

6. A communication design device for a multi-variant vehicle network, characterized in that: include: A variant establishing unit, for establishing, for each vehicle type, ECU variants of each ECU usage scenario according to each ECU of the vehicle type and its corresponding ECU usage scenario; A first establishing unit, configured to establish, based on each of the ECU variants, each variant unit corresponding to each of the vehicle type; A combination establishing unit, used for establishing each variant combination corresponding to each vehicle type based on each variant unit corresponding to each vehicle type; wherein the variant combination at least includes any one variant unit in the ECU variant; A configuration unit, configured to configure, under each of the variant combinations, a valid sending message and a valid receiving signal corresponding to each of the ECUs of each of the vehicle type, to obtain each target variant combination corresponding to each of the vehicle type; The storage unit is used to store each target variant combination corresponding to each vehicle type in a pre-constructed redundant database.

7. The device according to claim 6, characterized in that Also includes: A data acquisition unit, used to acquire communication data of each vehicle type; A relationship establishing unit, used for establishing a communication relationship between each of the vehicle type types according to the communication data of each of the vehicle type types; The second establishing unit is used to establish a redundant database based on the communication relationship between each of the vehicle types.

8. The device according to claim 6, characterized in that The first establishing unit comprises: A function acquisition unit, used for acquiring the differential functions between each type of vehicle; The third establishing unit is used to establish each variant unit corresponding to each vehicle type according to the differential functions existing between each vehicle type under each ECU variant.

9. The device according to claim 8, characterized in that The configuration unit comprises: A determination unit, configured to determine, under each of the variant combinations, a valid transmission message and a valid reception signal corresponding to each of the ECUs of each of the vehicle types according to the differential functions between the vehicle types; The message configuration unit is used to configure each variant combination corresponding to each vehicle type based on the valid sending message and the valid receiving signal corresponding to each ECU of each vehicle type, so as to obtain each target variant combination corresponding to each vehicle type.

10. The device according to claim 6, characterized in that Also includes: A display unit, used to display an editing interface to a user when a vehicle model editing request is received; A switching unit is used to switch the target variant combination of the current vehicle type to each of the target variant combinations of the vehicle type according to the vehicle type selected in the editing interface.

Images