Commercial vehicle electronic and electrical architecture generation method, device, equipment and storage medium

Abstract

The application discloses a commercial vehicle electronic and electrical architecture generation method, device and equipment and a storage medium. The method comprises: a commercial vehicle electronic and electrical architecture based on intelligent decision. Specifically, the method comprises: acquiring a vehicle use scenario, determining a plurality of electronic and electrical configuration items according to the vehicle use scenario; determining a plurality of function abstract classes according to a set of vehicle functions and a set of vehicle function execution hardware components; configuring a function inheritance class to correspondingly inherit a function abstract class, and assigning values to specified object parameters in the function inheritance class based on vehicle parameters; binding one or more specified function inheritance classes to one specified electronic and electrical configuration item according to a coupling relationship to obtain a plurality of corresponding function configuration items; binding one or more specified function configuration items to one vehicle domain controller according to a domain controller allocation strategy; and generating a communication network containing all vehicle domain controllers according to a communication form of the vehicle domain controller.

Description

Technical Field

[0001] The embodiments of the present invention relate to vehicle engineering technology, and more particularly to a method, apparatus, device and storage medium for generating electronic and electrical architecture for commercial vehicles. Background Technology

[0002] With the rapid development of new energy and intelligent connected vehicles, the complexity of electronic and electrical systems in commercial vehicles is increasing rapidly. The complex user scenarios and diverse user needs of commercial vehicles have led to the following problems facing the current electronic and electrical architecture of commercial vehicles:

[0003] Rapid iteration of vehicle functions leads to a sharp increase in the number of controllers, high functional coupling between controllers, and the need for multi-component collaboration in system functions; network load increases dramatically, and due to rapid functional iteration, unified planning is difficult in the early stages, requiring additional gateways and other routing controllers, increasing costs; the complexity of vehicle wiring harnesses increases, resulting in higher costs; there are many vehicle models, exacerbating product differentiation; and user scenarios are complex, with the same function being used in different scenarios, leading to different functional strategy allocations.

[0004] Based on the above, the design of electronic and electrical architecture for commercial vehicles suffers from problems such as high design difficulty, low versatility, and difficulty in iteration. Summary of the Invention

[0005] This invention provides a method, apparatus, device, and storage medium for generating electronic and electrical architecture for commercial vehicles, in order to solve at least one problem existing in the prior art.

[0006] In a first aspect, embodiments of the present invention provide a method for generating an electronic and electrical architecture for commercial vehicles, comprising:

[0007] Obtain the vehicle usage scenario and determine several electronic and electrical configuration items based on the vehicle usage scenario;

[0008] Obtain a set of vehicle functions, obtain a set of hardware components for executing vehicle functions, and determine several abstract functional classes based on the set of vehicle functions and the set of hardware components for executing vehicle functions.

[0009] Configure one of the aforementioned functional abstract classes to correspond to one or more of the vehicle function execution hardware components, and configure all the permutations and combinations of the aforementioned functional abstract classes to correspond to each of the vehicle functions;

[0010] Obtain vehicle parameters, configure several functional inheritance classes, configure one functional inheritance class to inherit one functional abstract class, and assign values ​​to specified object parameters in the functional inheritance class based on the vehicle parameters;

[0011] Obtain the coupling relationship between different functional inheritance classes, and bind one or more specified functional inheritance classes to a specified electronic and electrical configuration item according to the coupling relationship to obtain a number of corresponding functional configuration items;

[0012] Obtain a set of vehicle domain controllers, obtain a preset domain controller allocation policy, and bind one or more specified function configuration items to a vehicle domain controller according to the domain controller allocation policy;

[0013] Obtain the communication format of the vehicle domain controllers, and generate a communication network containing all the vehicle domain controllers based on the communication format of the vehicle domain controllers;

[0014] The electrical architecture comprises a communication network that includes all of the vehicle domain controllers.

[0015] Optionally, the set of vehicle functions includes: a first set of vehicle functions and a second set of vehicle functions;

[0016] The first vehicle function set includes a first electrical function set commonly found in multiple specified vehicle models;

[0017] The second vehicle function set includes a second electrical function set corresponding to the vehicle usage scenario;

[0018] The first set of electrical functions and the second set of electrical functions are mutually exclusive;

[0019] Several abstract functional classes corresponding to the first vehicle function set and several abstract functional classes corresponding to the second vehicle function set are generated respectively.

[0020] Optionally, determining several electronic and electrical configuration items based on the vehicle usage scenario also includes:

[0021] Based on the vehicle usage scenario, the electronic and electrical configuration items are divided into optional electronic and electrical configuration items and standard electronic and electrical configuration items.

[0022] Optionally, it also includes determining dependencies and / or mutual exclusions between different electronic and electrical configuration items;

[0023] The dependency and / or mutual exclusion relationships are used to determine the electronic and electrical configuration items that cannot be activated simultaneously.

[0024] Optionally, the domain controller allocation strategy includes: determining the dependency and / or mutual exclusion relationship of corresponding functional configuration items based on the dependency and / or mutual exclusion relationship between the electronic and electrical configuration items;

[0025] Based on the dependencies and / or mutual exclusions of the feature configuration items, one or more of the specified feature configuration items are bound to a vehicle domain controller.

[0026] Optionally, it also includes determining the vehicle complexity and, based on the vehicle complexity, determining the number of vehicle domain controllers in the set of vehicle domain controllers.

[0027] Optionally, the communication method includes one or more of CAN, CANFD, LIN, Ethernet, and FlexRay.

[0028] Secondly, embodiments of the present invention also provide an electrical architecture generation apparatus, including an electrical architecture generation unit, the electrical architecture generation unit being used for:

[0029] Obtain the vehicle usage scenario and determine several electronic and electrical configuration items based on the vehicle usage scenario;

[0030] Obtain a set of vehicle functions, obtain a set of hardware components for executing vehicle functions, and determine several abstract functional classes based on the set of vehicle functions and the set of hardware components for executing vehicle functions.

[0031] Configure one of the aforementioned functional abstract classes to correspond to one or more of the vehicle function execution hardware components, and configure all the permutations and combinations of the aforementioned functional abstract classes to correspond to each of the vehicle functions;

[0032] Obtain vehicle parameters, configure each of the aforementioned functional abstract classes to inherit the vehicle parameters, and obtain several corresponding functional inheritance classes;

[0033] Obtain the coupling relationship between different vehicle functions, and bind one or more specified function inheritance classes to a specified electronic and electrical configuration item according to the coupling relationship to obtain a number of corresponding function configuration items;

[0034] Obtain the set of vehicle domain controllers, obtain the preset domain controller complexity, and bind one or more specified function configuration items to one of the vehicle domain controllers according to the domain controller complexity;

[0035] Obtain the communication format of the vehicle domain controllers, and generate a communication network containing all the vehicle domain controllers based on the communication format of the vehicle domain controllers;

[0036] The electrical architecture comprises a communication network that includes all of the vehicle domain controllers.

[0037] Thirdly, embodiments of the present invention also provide an electronic device, including at least one processor and a memory communicatively connected to the at least one processor;

[0038] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to execute any of the commercial vehicle electronic and electrical architecture generation methods described in the embodiments of the present invention.

[0039] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing computer instructions, which are used to cause a processor to execute any of the commercial vehicle electronic and electrical architecture generation methods described in the embodiments of the present invention.

[0040] Compared with existing technologies, the advantages of this invention are as follows: This invention proposes a method for generating electronic and electrical architecture for commercial vehicles. It determines functional abstract classes based on vehicle usage scenarios, and forms an electrical architecture based on these classes. The inherent characteristics of these abstract classes facilitate rapid iteration of electrical architecture functions under similar vehicle usage scenarios. It determines electronic and electrical configuration items based on vehicle usage scenarios, and configures functional inheritance classes that inherit from the functional abstract classes according to vehicle parameters for those scenarios. This allows the electrical architecture containing these inherited classes to quickly meet user configuration requirements. Based on the coupling relationships of these inherited classes, they are divided into different vehicle domain controllers, and a communication network containing all vehicle domain controllers is automatically generated according to a specified communication method, ensuring the communication reliability and security isolation of the electronic architecture. Using the commercial vehicle electronic and electrical architecture generation method proposed in this embodiment, electrical architectures for specified vehicle usage scenarios can be generated quickly, facilitating iteration and maintenance, and enabling rapid response to market demands. Attached Figure Description

[0041] Figure 1 This is a flowchart of the commercial vehicle electronic and electrical architecture generation method in the embodiment;

[0042] Figure 2 This is a block diagram of the vehicle electronic and electrical architecture generation method in the embodiment;

[0043] Figure 3 This is a flowchart of another method for generating electronic and electrical architecture for commercial vehicles in the embodiments;

[0044] Figure 4 This is a schematic diagram illustrating the generation of functional configuration items in the embodiment;

[0045] Figure 5 This is a schematic diagram of vehicle domain controller allocation in the embodiment;

[0046] Figure 6 This is a schematic diagram of the communication network generation in the embodiment;

[0047] Figure 7 This is a schematic diagram of the electronic device structure in the embodiment. Detailed Implementation

[0048] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0049] Example 1

[0050] Figure 1 This is a flowchart of the commercial vehicle electronic and electrical architecture generation method in the embodiment, for reference. Figure 1 The methods for generating the electronic and electrical architecture of commercial vehicles include:

[0051] S101. Obtain the vehicle usage scenario and determine several electronic and electrical configuration items based on the vehicle usage scenario.

[0052] In this embodiment, the vehicle usage scenario may include vehicle type and operating condition. For example, the vehicle usage scenario may be a pure electric vehicle tractor for high-speed freight, a hybrid vehicle for urban congestion, or a traditional fuel vehicle for high-speed cruising.

[0053] In particular, the electronic architecture generation method proposed in this embodiment is more suitable for generating electronic and electrical architectures for commercial vehicles.

[0054] Vehicle usage scenarios are related to user needs, and vehicle usage scenarios can be obtained by reading pre-stored vehicle usage scenario-related data.

[0055] For example, in this embodiment, when the vehicle model is determined, the electronic and electrical configuration items that the vehicle can be configured with are a number of specified fixed items. Further, based on the operating conditions, one or more electronic and electrical configuration items corresponding to the operating conditions are selected from all the above-mentioned electronic and electrical configuration items.

[0056] For example, in this embodiment, the term "electronic and electrical configuration item" is used to represent the (automatic) electronic control system of the vehicle (which can be configured).

[0057] S102. Obtain the set of vehicle functions, obtain the set of hardware components for executing vehicle functions, and determine several abstract functional classes based on the set of vehicle functions and the set of hardware components for executing vehicle functions.

[0058] S103. Configure a functional abstract class to correspond to one or more vehicle function execution hardware components, and configure all permutations and combinations of functional abstract classes to correspond to each vehicle function.

[0059] In this embodiment, combining steps S102 and S103, vehicle function refers to the electronic control function unit configured in the vehicle.

[0060] The aforementioned electronic control system may include a collection of one or more electronic control functional units, which constitute the (software) functional modules in the electronic control system.

[0061] For example, in this embodiment, the basis for obtaining the set of vehicle functions is not limited. For instance, preset vehicle functions corresponding to the vehicle model can be obtained, or preset vehicle functions corresponding to the operating conditions can be obtained.

[0062] In this embodiment, the vehicle function execution hardware component corresponds to the vehicle function, and the vehicle function execution hardware component is set to serve as the (hardware) execution component of one or more designated electronic control function units.

[0063] In this embodiment, all functional abstract classes are defined to correspond to all vehicle functions in the set, wherein different functional abstract classes satisfy the following conditions:

[0064] When dividing abstract functional classes, ensure that the interfaces between abstract functional classes are relatively independent; when dividing abstract functional classes, ensure that the responsibilities and functions of no abstract functional class are obvious; an abstract functional class can correspond to one or a group of vehicle function execution hardware components.

[0065] For example, in this embodiment, the meaning of the functional abstract class is the same as that of the abstract class (in software), and its conceptual definition will not be described in detail.

[0066] S104. Obtain vehicle parameters, configure several functional inheritance classes, configure one functional inheritance class to inherit one functional abstract class, and assign values ​​to the specified object parameters in the functional inheritance class based on the vehicle parameters.

[0067] In this embodiment, the vehicle parameters are related to the vehicle usage scenario. Depending on the vehicle usage scenario, the vehicle parameters may include speed limit, whether it is bound to a vehicle networking module, whether it is a tractor, etc.

[0068] For example, in this embodiment, different functional inheritance classes may include the same or different vehicle parameters. For instance, each functional inheritance class may be configured to include all vehicle parameters.

[0069] For example, in this embodiment, the class structure of each functional inheritance class is not limited, and it can be freely set according to requirements.

[0070] S105. Obtain the coupling relationship between different functional inheritance classes, and bind one or more specified functional inheritance classes to a specified electronic and electrical configuration item according to the coupling relationship to obtain the corresponding functional configuration items.

[0071] For example, in this embodiment, the method for determining the coupling relationship between different functional inheritance classes is not limited;

[0072] For example, the presence of identical or corresponding defined methods can be used to determine whether two functional inheritance classes are coupled; or, the presence of identical or corresponding object parameters can be used to determine whether two functional inheritance classes are coupled.

[0073] In this embodiment, the function inheritance class bound to the electronic and electrical configuration item must at least satisfy the following: the function inheritance class is used to implement the software function or related control logic corresponding to the electronic and electrical configuration item.

[0074] S106. Obtain the set of vehicle domain controllers, obtain the preset domain controller allocation policy, and bind one or more specified function configuration items to a vehicle domain controller according to the domain controller allocation policy.

[0075] For example, in this embodiment, the vehicle domain controller may include all vehicle domain controllers configured in the vehicle, or a portion of the vehicle domain controllers within a specified area;

[0076] The preset domain controller allocation strategy can be: determine the vehicle domain controller that is closest to the vehicle function execution hardware component of the software method corresponding to the function configuration item, and bind the one or more function configuration items to the vehicle domain controller.

[0077] Alternatively, one or more specified functional configuration items can be bound to a vehicle domain controller based on the complexity of the software method corresponding to the functional configuration item, so that the (software) complexity of the vehicle domain controller is less than the preset complexity.

[0078] S107. Obtain the communication format of the vehicle domain controllers, and generate a communication network containing all vehicle domain controllers based on the communication format of the vehicle domain controllers.

[0079] In this embodiment, generating the communication network for all vehicle domain controllers includes: determining the communication connection relationships between each vehicle domain controller, the communication connection relationships between each vehicle domain controller and the communication backbone network, and the communication connection relationships between each vehicle domain controller and the vehicle function execution hardware components, etc.

[0080] For example, in this embodiment, the communication form of the vehicle domain controller includes wired or wireless communication, and the type of communication protocol used during communication.

[0081] S108. Use the communication network, which includes all vehicle domain controllers, as the electrical architecture.

[0082] For example, in this embodiment, the electrical architecture serves as the basic basis for designing the vehicle's electronic and electrical architecture. This allows for the orderly integration of various electronic systems through specific logic and specifications, forming an organic whole that realizes complex functions. Ultimately, this integrates various sensors, electronic control units, wiring harness topologies, and electronic and electrical distribution systems in the vehicle to complete tasks such as computation, power, and energy distribution.

[0083] This embodiment proposes a method for generating the electronic and electrical architecture of commercial vehicles. It determines functional abstract classes based on vehicle usage scenarios, and forms the electrical architecture based on these classes. The inherent characteristics of these abstract classes facilitate rapid functional iteration of the electrical architecture under similar vehicle usage scenarios. Electronic and electrical configuration items are determined based on the vehicle usage scenarios, and functional inheritance classes that inherit from the functional abstract classes are configured according to the vehicle parameters for those scenarios. This allows the electrical architecture containing these inherited classes to quickly meet user configuration requirements. Based on the coupling relationships of the inherited classes, they are divided into different vehicle domain controllers, and a communication network containing all vehicle domain controllers is automatically generated according to a specified communication method, ensuring the communication reliability and security isolation of the electronic architecture. Using the commercial vehicle electronic and electrical architecture generation method proposed in this embodiment, the electrical architecture for a specified vehicle usage scenario can be generated quickly, facilitating iteration and maintenance, and enabling rapid response to market demands.

[0084] exist Figure 1 Based on the scheme shown, in one possible implementation, the set of vehicle functions includes: a first set of vehicle functions and a second set of vehicle functions;

[0085] The first vehicle function set includes a first electrical function set commonly found in multiple specified vehicle models;

[0086] The second vehicle function set includes a second electrical function set corresponding to the vehicle usage scenario;

[0087] The first set of electrical functions and the second set of electrical functions are mutually exclusive;

[0088] Generate several abstract functional classes corresponding to the first set of vehicle functions and several abstract functional classes corresponding to the second set of vehicle functions.

[0089] For example, in this solution, the vehicle type may include traditional fuel vehicles, hybrid vehicles, pure electric vehicles, intelligent vehicles, etc., and the first electrical function corresponds to the basic electrical function that is included in different vehicle types.

[0090] For example, in this solution, the second electrical function corresponds only to the special electrical functions that exist only in the currently selected vehicle usage scenario.

[0091] In this scheme, a first electrical function set and a second electrical function set are generated. Several abstract functional classes are then generated based on the first electrical function set and several abstract functional classes are generated based on the second electrical function set. This reduces the difficulty of generating abstract functional classes and makes it easier for them to meet certain requirements. Figure 1 The corresponding conditions set in the scheme shown improve the efficiency of method execution.

[0092] exist Figure 1 Based on the illustrated scheme, in one possible implementation, the electronic and electrical configuration items, determined according to the vehicle usage scenario, further include:

[0093] Based on the vehicle's usage scenario, electronic and electrical configuration items are divided into optional electronic and electrical configuration items and standard electronic and electrical configuration items.

[0094] For example, in this solution, the optional electronic and electrical configuration items correspond to electronic and electrical functions that can be activated, while the standard electronic and electrical configuration items correspond to electronic and electrical functions that are activated by default at the factory.

[0095] The electrical configuration items are divided into optional and standard electronic and electrical configuration items, which can meet the needs of different users for electronic and electrical functions under the same vehicle usage scenario and improve the flexibility of vehicle use.

[0096] Based on the scheme of dividing electronic and electrical configuration items into optional electronic and electrical configuration items and standard electronic and electrical configuration items, in one possible implementation scheme, it also includes determining the dependency and / or mutual exclusion relationship between different electronic and electrical configuration items;

[0097] Dependency and / or mutual exclusion relationships are used to determine electronic and electrical configuration items that cannot be activated simultaneously.

[0098] For example, in this solution, determining the dependencies and mutual exclusions between different electronic and electrical configuration items can prevent the simultaneous activation of electronic and electrical configuration items that cannot be implemented simultaneously, or prevent the lack of activation of electronic and electrical configuration items that need to be implemented simultaneously, so as to ensure the stability of the implementation of electronic and electrical functions.

[0099] For example, the selection, standard configuration, dependency, and mutual exclusion relationships of electronic and electrical configuration items can be represented by the scheme shown in Table 1:

[0100] Table 1

[0101] 1 EE configuration 1 Standard configuration 2 EE configuration 2 Mutual exclusion with configuration 1 Optional 3 EE configuration 3 Dependencies with Configuration 4 Optional 4 EE configuration 4 Optional 5 EE configuration 5 Mutual exclusion with configuration 6 Standard configuration 6 EE configuration 6 Standard configuration

[0102] exist Figure 1 Based on the scheme shown, in one possible implementation, the domain controller allocation strategy optionally includes: determining the dependency and / or mutual exclusion relationship of the corresponding functional configuration items based on the dependency and / or mutual exclusion relationship between electronic and electrical configuration items;

[0103] Based on the dependencies and / or mutual exclusions of the feature configuration items, bind one or more specified feature configuration items to a vehicle domain controller.

[0104] In this scheme, the dependencies and / or mutual exclusion relationships between electronic and electrical configuration items and their corresponding functional configuration items are set to be the same.

[0105] For example, in this solution, binding one or more specified function configuration items to a vehicle domain controller based on the dependencies and / or mutual exclusions of the function configuration items can be as follows:

[0106] If there is a mutual exclusion relationship between the function configuration items, and there is at least one standard function configuration item and one optional function configuration item, then the standard function configuration item and the optional function configuration item with mutual exclusion relationship will be assigned to one vehicle domain controller.

[0107] Standard and / or optional features that have dependencies are grouped into a single vehicle domain controller.

[0108] Different standard configuration items with mutually exclusive relationships are assigned to different vehicle domain controllers.

[0109] Furthermore, in one possible implementation, after determining the functional configuration items included in different vehicle domain controllers, determining the communication method of the vehicle domain controllers includes:

[0110] The type of communication bus and the type of communication protocol are determined based on the amount of communication data.

[0111] For example, in this scheme, the communication data volume includes: the data throughput of communication when a vehicle domain controller containing one or more specified functional inheritance classes communicates with other vehicle domain controllers containing one or more functional inheritance classes.

[0112] For example, in this solution, when the amount of communication data is large, a parallel bus can be used to transmit the data; otherwise, a serial bus can be used to transmit the data.

[0113] exist Figure 1 Based on the scheme shown, in one possible implementation, the method further includes determining the vehicle complexity and, based on the vehicle complexity, determining the number of vehicle domain controllers in the set of vehicle domain controllers.

[0114] For example, in this solution, vehicle complexity can be used to represent the total number of electronic and electrical configuration items that the vehicle can be configured with, as well as the ease or difficulty of implementing each electronic and electrical configuration item;

[0115] Generally, for a given vehicle usage scenario, 3 to 5 vehicle domain controllers are set up specifically for that usage scenario.

[0116] exist Figure 1 Based on the scheme shown, in one possible implementation, the communication form includes one or more of CAN, CANFD, LIN, Ethernet, and FlexRay.

[0117] Figure 2 This is a module diagram of the vehicle electronic and electrical architecture generation method in the embodiment. Figure 3 This is a flowchart of another commercial vehicle electronic and electrical architecture generation method in the embodiment, for reference. Figure 2 and Figure 3 In one possible implementation, the method for generating the electronic and electrical architecture of a commercial vehicle includes:

[0118] S201. Obtain the vehicle usage scenario and determine several electronic and electrical configuration items based on the vehicle usage scenario.

[0119] S202. Based on the vehicle usage scenario, electronic and electrical configuration items are divided into optional electronic and electrical configuration items and standard electronic and electrical configuration items.

[0120] S203. Determine the dependencies and mutual exclusions between different electronic and electrical configuration items.

[0121] In this solution, steps S201 to S203 can correspond to Figure 2 User scenario creation can specifically include: collecting (user) vehicle usage scenario requirements, and determining the vehicle's electronic and electrical configuration and parameters.

[0122] The vehicle's electronic and electrical configuration can be determined based on user usage scenario requirements. According to the vehicle model, product, and scenario requirements, the electronic and electrical configuration can be defined as standard and optional, and the dependency or mutual exclusion relationship between different configurations can be established.

[0123] Based on user needs and usage scenarios, the determined vehicle parameters can include, for example, {scenario description, speed limit, parameters required by local regulations, etc.}.

[0124] S204. Obtain the first vehicle function set and the second vehicle function set, and generate several abstract function classes corresponding to the first vehicle function set and several abstract function classes corresponding to the second vehicle function set, respectively.

[0125] In this solution, part of step S204 (obtaining the first vehicle function set and the second vehicle function set) corresponds to... Figure 2 Feature data reading in the process can specifically include:

[0126] Based on the electronic and electrical functions and characteristics of traditional fuel vehicles, new energy vehicles, and intelligent vehicles, a basic electronic and electrical function set (first vehicle function set) and an extended electronic and electrical function set (second vehicle function set) are established.

[0127] Analyze the commonalities among various vehicle platforms and establish a basic set of electronic and electrical functions for each vehicle platform;

[0128] Analyze and determine the extended electronic and electrical function sets for traditional fuel vehicles, new energy vehicles, and intelligent vehicles.

[0129] S205. Obtain vehicle parameters, configure several functional inheritance classes, configure one functional inheritance class to inherit one functional abstract class, and assign values ​​to the specified object parameters in the functional inheritance class based on the vehicle parameters.

[0130] In this solution, some parts of step S204 (generating several abstract functional classes corresponding to the first vehicle function set and several abstract functional classes corresponding to the second vehicle function set) correspond to step S205. Figure 2 Functional abstraction and user scenario-based inheritance and encapsulation of functional features;

[0131] Functional abstraction can be specifically achieved by further dividing the function into several subsystems (functional abstract classes) for coordinated implementation.

[0132] The principles for subsystem division are as follows:

[0133] When dividing into subsystems, it is necessary to ensure that the interfaces between subsystems remain stable and that the interfaces are independent of the specific form of the sensors and actuators.

[0134] When dividing into subsystems, it should be ensured that the responsibilities and functions of each subsystem are clearly defined and that they conform to the logical requirements of the built-in components;

[0135] Subsystems can be created based on one or a set of physical components;

[0136] When dividing a subsystem, the functional responsibilities of its constituent components should be considered.

[0137] The inheritance and encapsulation of user-scenario-based functional features can be specifically described as follows: a functional abstract class is combined with vehicle parameters {such as scenario description, speed limit, local regulatory requirements, etc.}, and inherited and encapsulated to obtain a set of user-scenario-based functional features.

[0138] S206. Obtain the coupling relationship between different functional inheritance classes, and bind one or more specified functional inheritance classes to a specified electronic and electrical configuration item according to the coupling relationship to obtain the corresponding functional configuration items.

[0139] S207. Determine the vehicle complexity, and based on the vehicle complexity, determine the number of vehicle domain controllers in the set of vehicle domain controllers.

[0140] S208. Bind one or more specified functional configuration items to a vehicle domain controller based on the dependencies and mutual exclusions of the functional configuration items.

[0141] In this solution, steps S206 to S208 correspond to some content in the inheritance and encapsulation of functional characteristics based on user scenarios and the creation of intelligent decision-making.

[0142] Among them, the part corresponding to the inheritance and encapsulation of user scenario-based functional characteristics is: according to the functional coupling dependency relationship, the user scenario-based functional characteristics are divided into different electronic and electrical configurations.

[0143] Intelligent decision creation specifically includes: making comprehensive intelligent decisions based on factors such as user scenario characteristics, functional coupling, communication data volume, area control, and security isolation, so as to allocate functional inheritance classes to different domain controllers;

[0144] The number of domain controllers is determined based on the complexity of the vehicle. The domain controllers use chips and software architectures with advantageous resources, and the input / output layer uses nearby data acquisition and driving.

[0145] S209. Determine the communication bus type and communication protocol type based on the amount of communication data, and generate a communication network containing all vehicle domain controllers based on the communication bus and communication protocol types.

[0146] In this solution, step S209 corresponds to part of the intelligent decision creation process and the intelligent decision output.

[0147] Among them, the part corresponding to the creation of intelligent decision-making is: further dividing each electronic and electrical configuration into different domain control network segments, and determining the communication method according to the communication data volume of each network segment;

[0148] The intelligent decision output can be specifically as follows: determine the communication form of the domain control backbone network based on the communication volume of each domain control, and finally obtain a commercial vehicle electronic and electrical architecture based on intelligent decision.

[0149] S210. The communication network, which includes all vehicle domain controllers, is used as the electrical architecture.

[0150] Figure 4 This is a schematic diagram illustrating the generation of functional configuration items in the embodiment. Figure 5 This is a schematic diagram of vehicle domain controller allocation in the embodiment. Figure 6 This is a schematic diagram of the communication network generation in the embodiment, for reference. Figures 4 to 6 As one possible implementation method, the vehicle usage scenario is determined to be a pure electric traction high-speed freight scenario;

[0151] Referring to Table 1, the electronic and electrical configuration items include EE configuration 1 to EE configuration 6. EE configuration 1, EE configuration 5, and EE configuration 6 are set as standard electronic and electrical configuration items, and the rest are optional electronic and electrical configuration items.

[0152] Set EE configuration 1 and EE configuration 2 to be mutually exclusive, EE configuration 3 to depend on EE configuration 4, and EE configuration 5 and EE configuration 6 to be mutually exclusive.

[0153] Based on the electronic and electrical functions and characteristics of traditional fuel vehicles, new energy vehicles and intelligent vehicles, we analyze the commonalities between vehicle platforms and establish a basic electronic and electrical function set (FB) for each vehicle platform as the first vehicle function set.

[0154] Analyze and determine the electronic and electrical function set FT for a pure electric traction high-speed freight scenario, as the second vehicle function set;

[0155] Abstract classes S1, S3, S5, and S7 are generated based on FB, and abstract classes S2, S4, S6, S8, S9, and S10 are generated based on FT.

[0156] Obtain vehicle parameters, including {mainline traction (a), speed limit 89km / h (b), and binding of vehicle networking module (c)};

[0157] Based on the abstract class and vehicle parameters, functional inheritance classes S1(a, b, c)~S10(a, b, c) are generated;

[0158] Based on the coupling relationship of the functional inheritance classes, functional inheritance classes S1(a, b, c) and S3(a, b, c) are bound to EE configuration 1, functional inheritance class S2(a, b, c) is bound to EE configuration 2, functional inheritance class S6(a, b, c) is bound to EE configuration 3, functional inheritance classes S7(a, b, c) and S8(a, b, c) are bound to EE configuration 4, functional inheritance class S9(a, b, c) is bound to EE configuration 5, and functional inheritance classes S4(a, b, c), S5(a, b, c) and S10(a, b, c) are bound to EE configuration 6.

[0159] The bound EE configurations 1 through EE configurations 6 are respectively designated as function configuration item 1, function configuration item 2, function configuration item 3, function configuration item 4, function configuration item 5, and function configuration item 6.

[0160] Based on the complexity of the vehicles, three vehicle domain controllers are selected: vehicle domain controller 1 to vehicle domain controller 3. The vehicle domain controllers adopt chips and software architectures with advantageous resources, and the input / output layers adopt local data acquisition and driving.

[0161] Based on the mutual exclusion and dependency relationships of the functional inheritance classes, as well as the optional and standard attributes of the functional configuration items, functional configuration item 1 and functional configuration item 2 are assigned to vehicle domain controller 1, functional configuration items 3 to 5 are assigned to vehicle domain controller 2, and functional configuration item 6 is assigned to functional configuration item 6.

[0162] Based on the amount of communication data, the communication protocols to be used include CANFD, CAN, and Ethernet, and the vehicle domain controllers are configured to communicate via the CANFD bus.

[0163] Vehicle domain controller 1 communicates with function configuration item 1 and function configuration item 2 via CANFD protocol; vehicle domain controller 2 communicates with function configuration items 3-5 via CAN protocol; and vehicle domain controller 3 communicates with function configuration item 6 via Ethernet protocol.

[0164] Example 2

[0165] This embodiment proposes an electrical architecture generation device, including an electrical architecture generation unit, which is used for:

[0166] Obtain vehicle usage scenarios and determine several electronic and electrical configuration items based on those scenarios;

[0167] Get the set of vehicle functions, get the set of hardware components that execute vehicle functions, and determine several abstract functional classes based on the set of vehicle functions and the set of hardware components that execute vehicle functions.

[0168] Configure a functional abstract class to correspond to one or more vehicle function execution hardware components, and configure all permutations and combinations of functional abstract classes to correspond to each of the vehicle functions;

[0169] Obtain vehicle parameters, configure each functional abstract class to inherit vehicle parameters, and obtain several corresponding functional inheritance classes;

[0170] Obtain the coupling relationship between different vehicle functions, and bind one or more specified function inheritance classes to a specified electronic and electrical configuration item according to the coupling relationship to obtain several corresponding function configuration items;

[0171] Get the set of vehicle domain controllers, get the preset domain controller complexity, and bind one or more specified function configuration items to a vehicle domain controller based on the domain controller complexity.

[0172] Obtain the communication format of the vehicle domain controllers, and generate a communication network containing all the vehicle domain controllers based on the communication format of the vehicle domain controllers;

[0173] The communication network, which includes all vehicle domain controllers, is used as the electrical architecture.

[0174] For example, in this embodiment, the electrical architecture generation unit can be configured to implement any of the commercial vehicle electronic and electrical architecture generation methods described in Embodiment 1. The implementation method is the same as the corresponding scheme described in Embodiment 1, and the beneficial effects are also the same. The specific details will not be repeated.

[0175] Example 3

[0176] Figure 7 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0177] like Figure 7 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0178] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0179] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the commercial vehicle electronic and electrical architecture generation method.

[0180] In some embodiments, the commercial vehicle electrical and electronic architecture generation method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the commercial vehicle electrical and electronic architecture generation method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the commercial vehicle electrical and electronic architecture generation method by any other suitable means (e.g., by means of firmware).

[0181] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0182] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0183] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0184] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0185] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0186] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0187] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A method for generating an electronic and electrical architecture for commercial vehicles, characterized in that, include: Obtain the vehicle usage scenario and determine several electronic and electrical configuration items based on the vehicle usage scenario; Obtain a set of vehicle functions, obtain a set of hardware components for executing vehicle functions, and determine several abstract functional classes based on the set of vehicle functions and the set of hardware components for executing vehicle functions. Configure one of the aforementioned functional abstract classes to correspond to one or more of the vehicle function execution hardware components, and configure all the permutations and combinations of the aforementioned functional abstract classes to correspond to each of the vehicle functions; Obtain vehicle parameters, configure several functional inheritance classes, configure one functional inheritance class to inherit one functional abstract class, and assign values ​​to specified object parameters in the functional inheritance class based on the vehicle parameters; Obtain the coupling relationship between different functional inheritance classes, and bind one or more specified functional inheritance classes to a specified electronic and electrical configuration item according to the coupling relationship to obtain a number of corresponding functional configuration items; Obtain a set of vehicle domain controllers, obtain a preset domain controller allocation policy, and bind one or more specified function configuration items to a vehicle domain controller according to the domain controller allocation policy; Obtain the communication format of the vehicle domain controllers, and generate a communication network containing all the vehicle domain controllers based on the communication format of the vehicle domain controllers; The electrical architecture comprises a communication network that includes all of the vehicle domain controllers. The set of vehicle functions includes: a first set of vehicle functions and a second set of vehicle functions; The first vehicle function set includes a first electrical function set commonly found in multiple specified vehicle models; The second vehicle function set includes a second electrical function set corresponding to the vehicle usage scenario; The first set of electrical functions and the second set of electrical functions are mutually exclusive; Several abstract functional classes corresponding to the first vehicle function set and several abstract functional classes corresponding to the second vehicle function set are generated respectively.

2. The method for generating the electronic and electrical architecture of a commercial vehicle as described in claim 1, characterized in that, Based on the vehicle usage scenario, several electronic and electrical configuration items also include: Based on the vehicle usage scenario, the electronic and electrical configuration items are divided into optional electronic and electrical configuration items and standard electronic and electrical configuration items.

3. The method for generating the electronic and electrical architecture of a commercial vehicle as described in claim 2, characterized in that, It also includes determining the dependencies and / or mutual exclusions between different electronic and electrical configuration items; The dependency and / or mutual exclusion relationships are used to determine the electronic and electrical configuration items that cannot be activated simultaneously.

4. The method for generating the electronic and electrical architecture of a commercial vehicle as described in claim 3, characterized in that, The domain controller allocation strategy includes: determining the dependency and / or mutual exclusion relationships of corresponding functional configuration items based on the dependency and / or mutual exclusion relationships between the electronic and electrical configuration items; Based on the dependencies and / or mutual exclusions of the feature configuration items, one or more of the specified feature configuration items are bound to a vehicle domain controller.

5. The method for generating the electronic and electrical architecture of a commercial vehicle as described in claim 1, characterized in that, It also includes determining the vehicle complexity and, based on the vehicle complexity, determining the number of vehicle domain controllers in the set of vehicle domain controllers.

6. The method for generating the electronic and electrical architecture of a commercial vehicle as described in claim 1, characterized in that, The communication methods include one or more of CAN, CANFD, LIN, Ethernet, and FlexRay.

7. An electrical architecture generation device, characterized in that, Includes an electrical architecture generation unit, the electrical architecture generation unit being used for: Obtain the vehicle usage scenario and determine several electronic and electrical configuration items based on the vehicle usage scenario; Obtain a set of vehicle functions, obtain a set of hardware components for executing vehicle functions, and determine several abstract functional classes based on the set of vehicle functions and the set of hardware components for executing vehicle functions. Configure one of the aforementioned functional abstract classes to correspond to one or more of the vehicle function execution hardware components, and configure all the permutations and combinations of the aforementioned functional abstract classes to correspond to each of the vehicle functions; Obtain vehicle parameters, configure several functional inheritance classes, configure one functional inheritance class to inherit one functional abstract class, and assign values ​​to specified object parameters in the functional inheritance class based on the vehicle parameters; Obtain the coupling relationship between different vehicle functions, and bind one or more specified function inheritance classes to a specified electronic and electrical configuration item according to the coupling relationship to obtain a number of corresponding function configuration items; Obtain the set of vehicle domain controllers, obtain the preset domain controller complexity, and bind one or more specified function configuration items to one of the vehicle domain controllers according to the domain controller complexity; Obtain the communication format of the vehicle domain controllers, and generate a communication network containing all the vehicle domain controllers based on the communication format of the vehicle domain controllers; The electrical architecture comprises a communication network that includes all of the vehicle domain controllers. The set of vehicle functions includes: a first set of vehicle functions and a second set of vehicle functions; The first vehicle function set includes a first electrical function set commonly found in multiple specified vehicle models; The second vehicle function set includes a second electrical function set corresponding to the vehicle usage scenario; The first set of electrical functions and the second set of electrical functions are mutually exclusive; Several abstract functional classes corresponding to the first vehicle function set and several abstract functional classes corresponding to the second vehicle function set are generated respectively.

8. An electronic device, characterized in that, It includes at least one processor and a memory communicatively connected to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the commercial vehicle electronic and electrical architecture generation method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the method for generating the electronic and electrical architecture of a commercial vehicle as described in any one of claims 1-6.

Images