Vehicle development method and device, computer equipment, storage medium and program product
By obtaining software and hardware requirements data and determining the relationship between functional subsystems and configuration controllers, the problems of low efficiency and irregular processes of traditional electronic and electrical architecture development are solved, and efficient and reliable intelligent driving car development is achieved.
Patent Information
- Application Number
- CN202411071824.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-06
- Publication Date
- 2024-11-08
AI Technical Summary
Traditional electronic and electrical architectures have problems such as low development efficiency and irregular development processes in the development of intelligent driving cars, which cannot meet the needs of the automotive industry for intelligent development.
Provide a vehicle development method, by obtaining software requirements data and hardware requirements data, determining functional subsystems and building logical components, configuring controllers and establishing their association relationships, and then conducting overall modeling to achieve high efficiency and reliability vehicle development .
It realizes high-efficiency and high-reliability vehicle development, suitable for intelligent driving car development scenarios with complex functions, and improves development efficiency and process standardization.
Smart Images

Figure CN118916002A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of electronic and electrical architecture, and in particular to a vehicle development method, apparatus, computer equipment, storage medium and program product. Background Art
[0002] The electronic and electrical architecture is the main framework for automobile development, which can provide implementation solutions and regulatory guidance for the entire vehicle project. Therefore, the electronic and electrical architecture needs to be forward-looking, platform-based, and scalable.
[0003] At present, with the continuous development of intelligent driving technology, automobile functions are becoming increasingly complex. Traditional electronic and electrical architecture is developed based on documents, and has problems such as low development efficiency and irregular development process. Traditional development methods can no longer meet the automotive industry's needs for intelligent development. Summary of the invention
[0004] Based on this, it is necessary to provide a vehicle development method, device, computer equipment, storage medium and program product that can efficiently perform standardized design in response to the above technical problems.
[0005] In a first aspect, the present application provides a vehicle development method, comprising:
[0006] Obtain software and hardware requirement data for the vehicle to be developed;
[0007] According to the software requirement data, determine the functional subsystems of the vehicle to be developed, and build the corresponding logical components of each functional subsystem;
[0008] Configure each controller of the vehicle to be developed according to the hardware requirement data, and establish the association relationship between each configured controller and each logical component;
[0009] The vehicle to be developed is modeled according to the associated logical components and controllers to obtain the target modeling result.
[0010] In one embodiment, the software requirement data includes functional requirement data and standard requirement data. According to the software requirement data, each functional subsystem of the vehicle to be developed is determined, and logical components corresponding to each functional subsystem are constructed, including:
[0011] Create functional use cases for the vehicle to be developed based on functional requirement data;
[0012] Generate function definition data for the vehicle to be developed based on standard requirement data;
[0013] Determine the functional subsystems of the vehicle to be developed based on the functional use cases and functional definition data;
[0014] According to each functional subsystem and the relationship between each functional subsystem, the logical components corresponding to each functional subsystem are constructed.
[0015] In one embodiment, the functional subsystems of the vehicle to be developed are determined based on the functional use case and the functional definition data, including:
[0016] Determine the target functions required for the vehicle to be developed based on the functional use cases and functional definition data;
[0017] Corresponding functional subsystems are allocated to target functions, wherein each target function corresponds to at least two functional subsystems.
[0018] In one embodiment, each controller of the vehicle to be developed is configured according to the hardware requirement data, including:
[0019] Determine the network topology data of the vehicle to be developed based on the hardware requirement data; wherein the network topology data includes the controller area network CAN bus segment;
[0020] Configure each controller of the vehicle to be developed based on the hardware requirement data and network topology data.
[0021] In one embodiment, a vehicle to be developed is modeled according to associated logic components and controllers to obtain a target modeling result, including:
[0022] Model each logic component and each controller separately to obtain software modeling results and hardware modeling results;
[0023] According to the association between each logical component and each controller, the software modeling results and the hardware modeling results are matched to obtain the target modeling results of the vehicle to be developed.
[0024] In one embodiment, the method further comprises:
[0025] According to the vehicle model configuration information, select the target software from the software modeling results, and select the target hardware from the hardware modeling results;
[0026] Based on the selected target software and target hardware, determine the target modeling results of the vehicle to be developed under different models.
[0027] In a second aspect, the present application further provides a vehicle development device, comprising:
[0028] A data acquisition module, used to acquire software requirement data and hardware requirement data for the vehicle to be developed;
[0029] The software construction module is used to determine the functional subsystems of the vehicle to be developed based on the software requirement data and to construct the logical components corresponding to each functional subsystem;
[0030] A hardware construction module, used to configure each controller of the vehicle to be developed according to the hardware requirement data, and to establish an association relationship between each configured controller and each logical component;
[0031] The vehicle modeling module is used to model the vehicle to be developed according to the associated logical components and controllers to obtain the target modeling result.
[0032] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:
[0033] Obtain software and hardware requirement data for the vehicle to be developed;
[0034] According to the software requirement data, determine the functional subsystems of the vehicle to be developed, and build the corresponding logical components of each functional subsystem;
[0035] Configure each controller of the vehicle to be developed according to the hardware requirement data, and establish the association relationship between each configured controller and each logical component;
[0036] The vehicle to be developed is modeled according to the associated logical components and controllers to obtain the target modeling result.
[0037] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:
[0038] Obtain software and hardware requirement data for the vehicle to be developed;
[0039] According to the software requirement data, determine the functional subsystems of the vehicle to be developed, and build the corresponding logical components of each functional subsystem;
[0040] Configure each controller of the vehicle to be developed according to the hardware requirement data, and establish the association relationship between each configured controller and each logical component;
[0041] The vehicle to be developed is modeled according to the associated logical components and controllers to obtain the target modeling result.
[0042] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:
[0043] Obtain software and hardware requirement data for the vehicle to be developed;
[0044] According to the software requirement data, determine the functional subsystems of the vehicle to be developed, and build the corresponding logical components of each functional subsystem;
[0045] Configure each controller of the vehicle to be developed according to the hardware requirement data, and establish the association relationship between each configured controller and each logical component;
[0046] The vehicle to be developed is modeled according to the associated logical components and controllers to obtain the target modeling result.
[0047] The above-mentioned vehicle development method, apparatus, computer equipment, storage medium and program product obtain software requirement data and hardware requirement data for the vehicle to be developed, determine the functional subsystems of the vehicle to be developed according to the software requirement data, and construct the logical components corresponding to each functional subsystem, and then configure the controllers of the vehicle to be developed according to the hardware requirement data, and establish the association relationship between each configured controller and each logical component, and further, model the vehicle to be developed according to the associated logical components and controllers to obtain the target modeling result. The present application is based on a new electronic and electrical architecture model framework, and develops and designs the vehicle from the software level and the hardware level respectively, and then establishes the association relationship between each logical component on the software and each controller on the hardware, and models the vehicle as a whole, which can achieve high-efficiency and high-reliability vehicle development, and is suitable for vehicle development scenarios with increasingly complex vehicle functions. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0049] Figure 1 An application environment diagram of a vehicle development method in one embodiment;
[0050] Figure 2 A schematic flow chart of a vehicle development method in one embodiment;
[0051] Figure 3 A schematic diagram of a process for constructing a logic component in an embodiment;
[0052] Figure 4 A schematic diagram of a flow chart for configuring a controller in one embodiment;
[0053] Figure 5 A schematic diagram of a process for modeling a vehicle to be developed in one embodiment;
[0054] Figure 6 A schematic diagram of the electronic and electrical architecture of an embodiment;
[0055] Figure 7 It is a structural block diagram of a vehicle development device in one embodiment;
[0056] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0057] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0058] The vehicle development method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Specifically, the terminal 102 responds to the software requirement data and hardware requirement data for the vehicle to be developed input by the developer, and sends the software requirement data and hardware requirement data to the server 104, so that the server 104 obtains the software requirement data and hardware requirement data for the vehicle to be developed, and determines the functional subsystems of the vehicle to be developed according to the software requirement data, and constructs the logical components corresponding to the functional subsystems, and then configures the controllers of the vehicle to be developed according to the hardware requirement data, and establishes the association relationship between the configured controllers and the logical components, and further, according to the associated logical components and controllers, the vehicle to be developed is modeled to obtain the target modeling result, and the server 104 can send the target modeling result to the terminal 102, so that the terminal 102 shows the target modeling result to the developer.
[0059] The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. The server 104 may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.
[0060] In an exemplary embodiment, Figure 2 As shown, a vehicle development method is provided, which is applied to Figure 1 The following is an example of a server in the example, including:
[0061] S201, obtaining software requirement data and hardware requirement data for a vehicle to be developed.
[0062] Among them, software requirement data is used to characterize the specific requirements of the vehicle at the software level, which may include but is not limited to the requirements for various software functions; hardware requirement data is used to characterize the specific requirements of the vehicle at the hardware level, which may include but is not limited to the requirements for various hardware functions.
[0063] It is understandable that the design of a vehicle to be developed requires unification at the software and hardware levels. Software requirement data and hardware requirement data may be used to represent the demand for the same functions, such as the control requirements for driving functions, or the requirements for lighting functions.
[0064] Exemplarily, developers use the automobile development model provided in this embodiment, which is implemented based on a new electronic and electrical architecture and includes at least a platform library module at the software level and a product line module at the hardware level, and different modules correspond to the same or different data input interfaces. Developers can input software requirement data and hardware requirement data for the vehicle to be developed in the data input interface by manual input or by importing files.
[0065] Optionally, the software requirement data may include but is not limited to functional requirement data and standard requirement data. The functional requirement data may be Function List data (i.e., function list data), which is used to represent the requirements for vehicle software functions; the standard requirement data may be market-side standard data, which is used to represent the automotive industry's requirements for vehicle software standards, such as different lighting control standards for vehicles of different sizes and models.
[0066] Exemplarily, the platform library module includes a Product Goals module (i.e., a product goal module) and a Customer Features module (i.e., a custom function module). Developers can input functional requirement data in the corresponding data input interface of the Product Goals module, and input standard requirement data in the corresponding data input interface of the Customer Features module.
[0067] Exemplarily, pre-configured hardware requirement data may be directly obtained locally and displayed to developers on a data input interface so that the developers can select the required hardware requirement data.
[0068] Optionally, the software requirement data and hardware requirement data for the vehicle to be developed selected by the developer in the terminal are sent to the server for subsequent processing, and data is exchanged between the terminal and the server to realize a visualized vehicle development process.
[0069] S202, determining each functional subsystem of the vehicle to be developed according to the software requirement data, and constructing a logical component corresponding to each functional subsystem.
[0070] By dividing the vehicle system from the functional dimension, we can get multiple functional subsystems. A main function may require multiple functional subsystems to implement together, and there is data interaction between the functional subsystems.
[0071] The new electronic and electrical architecture adopted in this embodiment includes an A0 platform library and an A1-An product line, wherein the A0 platform library includes a requirement layer, a logic layer, a software layer and a communication layer, and the A1-An product line includes a communication layer, a component network layer and a variant management layer.
[0072] After the software requirement data is standardized at the A0 requirement layer, it is split and integrated in units of functional subsystems at the A0 logic layer to determine the functional subsystems to which the software requirement data points, and then each functional subsystem is split into corresponding logical components, namely LC (Logic Component) at the A0 software layer. A functional subsystem can correspond to multiple logical components, and multiple functional subsystems can also correspond to the same logical component.
[0073] Specifically, different software requirement data are integrated at the A0 requirement layer, such as the functional requirement data and standard requirement data, which are converted from function definition to function realization, and the functional subsystems of the vehicle to be developed are designed; the logic block diagram of the main function, the logic block diagram and interaction block diagram of each functional subsystem, and the graphic components that make up the logic block diagram are generated at the A0 logic layer; the interaction status between each logic component is designed according to the main function at the A0 software layer, and the interaction block diagram between the logic components corresponding to the functional subsystems under different main functions is generated, and the data exchange between each logic component is carried out through the Port interface (i.e., port).
[0074] Optionally, the A0 communication layer is divided into frame, PDU (Power Distribution Unit) and signal according to the AUTOSAR (AUTOmotive Open System Architecture) standard, and the communication function of the vehicle to be developed is designed based on the interaction status between each logical component in the A0 software layer.
[0075] S203, configuring each controller of the vehicle to be developed according to the hardware requirement data, and establishing an association relationship between each configured controller and each logical component.
[0076] After standardizing the hardware requirement data at the A1-An component network layer, determine the controllers to which the hardware requirement data points and the network topology to which each controller belongs, configure the connection relationships between each controller and each controller, and then, based on the configuration of each logical component, establish the association relationship between each controller and each logical component, thus completing the unification of vehicle development at the software and hardware levels.
[0077] Optionally, at the A1-An component network layer, the network topology and bus segment of the vehicle to be developed are designed, and the controllers at different levels of the central gateway, body domain, information domain, power domain, intelligent driving domain and chassis domain of the vehicle to be developed are designed, and the system block diagram of the corresponding network segment and the controller under the corresponding network segment is generated, and the network interface of the controller is configured. The power distribution scheme of the vehicle to be developed is configured, and the grounding point, power supply, fuse box and relay box are determined.
[0078] Furthermore, an association relationship is established between each controller and each logical component. For example, LC3 and LC6 are logical components corresponding to different functional subsystems, and the implementation of the controller ECU (Electronic Control Unit) 1 requires the simultaneous application of LC3 and LC6, and the association relationship between ECU1 and LC3 and LC6 is established.
[0079] Optionally, the configuration provided by the A0 communication layer is modified in the A1-An communication layer. The A0 communication layer provides selectable signal definitions of logical components, such as signal1 and signal2, where signal1 is sent from ECU1 to ECU2, and signal2 is sent from ECU1 to ECU4. The A0 communication layer also provides selectable PDU1 and PDU2, where PDU1 corresponds to signal1 and signal2, and PDU2 corresponds to signal3 and signal4. Accordingly, the A1-An communication layer can select signal1 and PDU1 to complete the communication configuration for the vehicle to be developed.
[0080] S204: Modeling the vehicle to be developed according to the associated logical components and controllers to obtain a target modeling result.
[0081] According to the design of the A0 software layer, the logical components of the vehicle to be developed are modeled, and the corresponding relationship between the configuration and the logical components is completed. According to the design of the A1-An component network layer, the controllers and sensors of the vehicle to be developed are modeled, and the use of each controller and sensor is simulated. Therefore, according to the associated logical components and controllers, the functional subsystems of the vehicle to be developed are simulated and implemented, and the corresponding software and hardware are selected to realize the modeling of the vehicle to be developed, and finally the target modeling result is obtained.
[0082] It is understandable that due to different selected software and hardware, multiple target modeling results can be obtained, and different target modeling results correspond to different vehicle models. The server can send all target modeling results to the terminal and display them to the developer through the result display interface, so that the developer can select the desired target modeling result from them.
[0083] In the above vehicle development method, the software requirement data and hardware requirement data for the vehicle to be developed are obtained, and the functional subsystems of the vehicle to be developed are determined according to the software requirement data, and the logical components corresponding to the functional subsystems are constructed, and then the controllers of the vehicle to be developed are configured according to the hardware requirement data, and the association relationship between the configured controllers and the logical components is established. Further, the vehicle to be developed is modeled according to the associated logical components and controllers to obtain the target modeling result. This embodiment is based on a new electronic and electrical architecture model framework, and the vehicle is developed and designed from the software level and the hardware level respectively, and then the association relationship between the logical components on the software and the controllers on the hardware is established, and the vehicle is modeled as a whole, which can achieve high-efficiency and high-reliability vehicle development, and is suitable for vehicle development scenarios with increasingly complex vehicle functions.
[0084] In an exemplary embodiment, the software requirement data includes functional requirement data and standard requirement data, such as Figure 3 As shown, the above S202 includes:
[0085] S301, creating a functional use case for the vehicle to be developed based on the functional requirement data.
[0086] In the FDR Use Case description (i.e., Functional Definition Use Case Description), the functional requirement data is decomposed according to the function of the Use Case (i.e., use case), and a corresponding functional use case is created for each function pointed to by the functional requirement data to describe the functional behavior and usage scenarios.
[0087] Among them, functional use cases are used to describe the functional requirements for the vehicle to be developed, and specifically can describe the system requirements of functional subsystems under different main functions.
[0088] S302: Generate function definition data for the vehicle to be developed according to the standard requirement data.
[0089] In Product Goals / Requirements / FDR input requirements (i.e., function definition input requirements), the standard requirement data is analyzed to extract the FDR input requirement data for the vehicle to be developed, i.e., function definition data.
[0090] S303: Determine the functional subsystems of the vehicle to be developed according to the functional use cases and the functional definition data.
[0091] In the FDR functional design requirements, the functional use cases and functional definition data are integrated to indicate the FR subsystem design requirements (i.e., the functional implementation subsystem design requirements). The main functions are split according to the functional subsystems. In the SRD (Software Requirements Document) LC design requirements, the functional subsystems are integrated as units to determine the functional subsystems of the vehicle to be developed.
[0092] Optionally, based on the functional use cases and the functional definition data, the target functions required for the vehicle to be developed are determined, and corresponding functional subsystems are allocated to the target functions.
[0093] The target function may be a main function of the vehicle system, and each target function corresponds to at least two functional subsystems, and different functional subsystems have different functional characteristics.
[0094] According to the functional use cases and functional definition data, the required target functions are determined, and then the whole vehicle system is divided into multiple functional subsystems. Different functional subsystems are assigned to different target functions, and based on the association between the target functions, the interaction logic between the functional subsystems is constructed.
[0095] In this way, for each target function required for the vehicle to be developed, the functional subsystem is created in a standardized manner to avoid the risk of internal functional logic of the functional subsystem being affected by the numerous functions of the entire vehicle.
[0096] S304: constructing logic components corresponding to each functional subsystem according to each functional subsystem and the association relationship between each functional subsystem.
[0097] In the SRD LC design requirements, the logical components corresponding to each functional subsystem are determined, and according to the association relationship between the functional subsystems, the association relationship between the logical components corresponding to each functional subsystem is designed, so as to construct the logical components corresponding to each functional subsystem.
[0098] Optionally, the integrated functional subsystems are split again to determine the logical components corresponding to each functional subsystem, so as to construct the logical components corresponding to each functional subsystem.
[0099] Optionally, in the FR subsystem design requirements, according to the split results of each functional subsystem, draw the interaction between the functional subsystems under different main functions, store the logic block diagram of each main function in the Logical Function Package, store the component types of the graphic components of the A0 logic layer in the Logical Types Package, and store the graphic components that make up the logic block diagram in the Logical Structure Package.
[0100] Optionally, the interaction between logical components is designed according to the functions in the A0 software layer, the component types are stored in Software Types (i.e., software types), and the interaction diagrams between logical components corresponding to different main functions are stored in the Root (i.e., root directory) level, which refines the Port interfaces between logical components, providing a corresponding basis for the design of the subsequent A0 communication layer.
[0101] In this embodiment, by processing the functional requirement data and standard requirement data at the A0 requirement layer, the functional subsystems and corresponding logical components of the vehicle to be developed are determined, and the software part of the vehicle to be developed is standardized from the common platform library to complete the transformation from scenario to requirement. Each step is implemented in the corresponding functional module, which can provide vehicle development requirement traceability and ensure the reliability of the vehicle development process.
[0102] In an exemplary embodiment, Figure 4 As shown, the above S203 includes:
[0103] S401, determining the network topology data of the vehicle to be developed according to the hardware requirement data.
[0104] The network topology data includes a CAN (Controller Area Network) bus segment.
[0105] According to the hardware requirement data, the network topology of the vehicle to be developed is designed and the network topology data is generated. In the network topology of the A1-An component network layer, the network topology and bus network segments of the vehicle under different models of the vehicle to be developed are stored.
[0106] S402, configuring each controller of the vehicle to be developed according to the hardware requirement data and the network topology data.
[0107] Specifically, according to the hardware requirement data and network topology data, the controllers at different levels of the central gateway, body domain, information domain, power domain, intelligent driving domain and chassis domain of the vehicle to be developed are configured, which stores the system block diagram and network interface of the corresponding network segments and the controllers under the corresponding network segments under different models of the vehicle to be developed.
[0108] In addition, the power distribution scheme of the vehicle to be developed is configured and the docking locations, power sources, fuse boxes and relay boxes are designed in the power distribution hierarchy.
[0109] In this embodiment, by processing the hardware requirement data at the A1-An component network layer, the controller of the vehicle to be developed is determined, and the hardware part of the vehicle to be developed is standardized from the personalized product line to complete the transformation from scenario to demand. This can provide a safe hardware design for the vehicle to be developed and ensure the reliability of the vehicle development process.
[0110] In an exemplary embodiment, Figure 5 As shown, the above S204 includes:
[0111] S501, modeling each logic component and each controller respectively to obtain software modeling results and hardware modeling results.
[0112] In the A0-An variant management layer, the software and hardware of the vehicle to be developed are modeled separately. The vehicle configuration provided by the A0 platform library is used as the standard, and it is modified in combination with the actual situation to determine the initial vehicle configuration of the vehicle to be developed.
[0113] Then, each logical component of the vehicle to be developed is modeled. Specifically, according to the initial vehicle configuration, the logical components designed by the A0 software layer are modeled under different vehicle configurations, and the mapping relationship between the vehicle configuration and the logical components is completed to obtain the software modeling results.
[0114] Model each controller of the vehicle to be developed. Specifically, based on the initial vehicle configuration, model the usage of each controller and sensor under different vehicle configurations to obtain hardware modeling results.
[0115] S502 , matching the software modeling result and the hardware modeling result according to the association relationship between each logical component and each controller, to obtain a target modeling result of the vehicle to be developed.
[0116] According to the association between each logical component and the controller, the software modeling results and the hardware modeling results are integrated to obtain the final target modeling results.
[0117] Specifically, under the initial vehicle model configuration, the software and hardware used in the vehicle to be developed are selected, the software variation and the hardware variation of the vehicle to be developed are completed, and the target vehicle model configuration is obtained.
[0118] Different hardware variant results are stored in the function allocation block diagram, the network interfaces of each functional subsystem are stored in the electrical component block diagram, the configuration files under the target vehicle configuration are stored in the variant space, and the domain controllers involved in the variant space are stored in the electronic and electrical system to provide auxiliary design.
[0119] Optionally, according to the vehicle model configuration information, target software is selected from the software modeling results, and target hardware is selected from the hardware modeling results; based on the selected target software and target hardware, target modeling results of the vehicle to be developed under different vehicle models are determined.
[0120] It is understandable that the same vehicle may need to develop multiple models at the same time. Based on the model configuration information, the initial model configuration is determined, such as model A and model B. Then, based on the software modeling results, different software is selected for model A and model B. Based on the hardware modeling results, different hardware is selected for model A and model B, which constitute the target modeling results corresponding to model A and model B respectively.
[0121] In this embodiment, the software variation and hardware variation of the vehicle to be developed are respectively completed in the A1-An product line, and the vehicle development process for the vehicle to be developed is realized, which can ensure the diversity of the target modeling results and is suitable for vehicle development scenarios with increasingly complex vehicle functions.
[0122] Based on the above embodiments, Figure 6 As shown, a new electronic and electrical architecture is provided, including ProductGoals module, logic layer / Logical Function Package module, software layer / Root module, platform communication layer, personalized communication layer, component network layer and product line.
[0123] Among them, the Feature List (i.e., functional requirement data) and various requirements (i.e., standard requirement data) in the Product Goals module are input into the FDR Use Case description through different channels. After the FDR functional design requirements, FR subsystem design requirements, and SRD LC design requirements, the main functions, such as Function 1 and Function 2, and the functional subsystems under the main functions, such as Subsystems 1-10, are determined. Then, the logical components corresponding to each functional subsystem, such as LC1-LC8, are determined. The logical components interact with each other through Port interfaces (such as Port1 and Port2).
[0124] The platform communication layer provides relevant communication configurations for the personalized communication layer to select and modify the communication configurations and determine the communication configurations of the vehicle to be developed.
[0125] The component network layer includes hardware-level design interfaces such as network topology, central gateway, and chassis domain, and designs each controller, such as ECU1-ECU5, and the interaction logic between each controller.
[0126] Furthermore, software variants and hardware variants are respectively performed on the models of the vehicles to be developed in the product line, wherein the corresponding configurations of the software variants, such as configuration 1, include LC3, LC4 and LC8, and the corresponding configurations of the hardware variants, such as configuration 1, include ECU1, ECU3 and ECU4. The electrical component block diagram, function allocation block diagram, deformation space and electronic system logic block diagram of the product line are used for auxiliary design of vehicle model configuration.
[0127] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0128] Based on the same inventive concept, the embodiment of the present application also provides a vehicle development device for implementing the vehicle development method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more vehicle development device embodiments provided below can refer to the limitations on the vehicle development method above, and will not be repeated here.
[0129] In an exemplary embodiment, Figure 7 As shown, a vehicle development device is provided, comprising: a data acquisition module 10, a software construction module 20, a hardware construction module 30 and a vehicle modeling module 40, wherein:
[0130] The data acquisition module 10 is used to acquire software requirement data and hardware requirement data for the vehicle to be developed.
[0131] The software construction module 20 is used to determine the functional subsystems of the vehicle to be developed according to the software requirement data, and to construct the logical components corresponding to the functional subsystems.
[0132] The hardware construction module 30 is used to configure each controller of the vehicle to be developed according to the hardware requirement data, and to establish an association relationship between each configured controller and each logical component.
[0133] The vehicle modeling module 40 is used to model the vehicle to be developed according to the associated logical components and controllers to obtain a target modeling result.
[0134] In one embodiment, the software requirement data includes functional requirement data and standard requirement data, and the software construction module 20 includes:
[0135] The use case creation unit is used to create functional use cases for the vehicle to be developed based on functional requirement data.
[0136] The data generation unit is used to generate function definition data for the vehicle to be developed according to the standard requirement data.
[0137] The system determination unit is used to determine the functional subsystems of the vehicle to be developed based on functional use cases and functional definition data.
[0138] The component construction unit is used to construct the logical components corresponding to each functional subsystem according to each functional subsystem and the association relationship between each functional subsystem.
[0139] In one embodiment, the system determination unit includes:
[0140] The function determination subunit is used to determine the target functions required for the vehicle to be developed based on the function use cases and function definition data.
[0141] The system allocation subunit is used to allocate corresponding functional subsystems to target functions.
[0142] Each target function corresponds to at least two functional subsystems.
[0143] In one embodiment, the hardware building block 30 includes:
[0144] The data determination unit is used to determine the network topology data of the vehicle to be developed according to the hardware requirement data.
[0145] The network topology data includes the CAN bus segment.
[0146] The controller configuration unit is used to configure each controller of the vehicle to be developed according to the hardware requirement data and the network topology data.
[0147] In one embodiment, the vehicle modeling module 40 includes:
[0148] The first modeling unit is used to model each logic component and each controller respectively to obtain software modeling results and hardware modeling results.
[0149] The second modeling unit is used to match the software modeling results and the hardware modeling results according to the association relationship between each logical component and each controller to obtain the target modeling result of the vehicle to be developed.
[0150] In one embodiment, the vehicle development device further includes:
[0151] A construction selection module is used to select target software from software modeling results and target hardware from hardware modeling results according to vehicle model configuration information.
[0152] The result determination module is used to determine the target modeling results of the vehicle to be developed under different models according to the selected target software and target hardware.
[0153] Each module in the above vehicle development device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
[0154] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 8 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as vehicle model configuration. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a vehicle development method is implemented.
[0155] Those skilled in the art will understand that Figure 8The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0156] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps of the vehicle development method provided in the above method embodiment are implemented.
[0157] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the vehicle development method provided by the above method embodiment are implemented.
[0158] In one embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps of the vehicle development method provided by the above method embodiment are implemented.
[0159] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.
[0160] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0161] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A vehicle development method, It is characterized in that The method comprises: Obtain software and hardware requirement data for the vehicle to be developed; Determine the functional subsystems of the vehicle to be developed according to the software requirement data, and construct logical components corresponding to the functional subsystems; According to the hardware requirement data, each controller of the vehicle to be developed is configured, and an association relationship between each configured controller and each logical component is established; The vehicle to be developed is modeled according to the associated logical components and controllers to obtain a target modeling result.
2. The method according to claim 1, It is characterized in that The software requirement data includes functional requirement data and standard requirement data. According to the software requirement data, each functional subsystem of the vehicle to be developed is determined, and logical components corresponding to each functional subsystem are constructed, including: Creating a functional use case for the vehicle to be developed based on the functional requirement data; Generating function definition data for the vehicle to be developed according to the standard requirement data; Determining each functional subsystem of the vehicle to be developed according to the functional use case and the functional definition data; According to each functional subsystem and the relationship between each functional subsystem, the logical components corresponding to each functional subsystem are constructed.
3. The method according to claim 2, It is characterized in that The step of determining the functional subsystems of the vehicle to be developed according to the functional use case and the functional definition data includes: Determining target functions required for the vehicle to be developed according to the functional use case and the functional definition data; Corresponding functional subsystems are allocated to the target functions, wherein each target function corresponds to at least two functional subsystems.
4. The method according to claim 1, It is characterized in that The configuring each controller of the vehicle to be developed according to the hardware requirement data includes: Determine the network topology data of the vehicle to be developed according to the hardware requirement data; wherein the network topology data includes a controller area network (CAN) bus segment; Each controller of the vehicle to be developed is configured according to the hardware requirement data and the network topology data.
5. The method according to claim 1, It is characterized in that The vehicle to be developed is modeled according to the associated logical components and controllers to obtain a target modeling result, including: Model each logic component and each controller separately to obtain software modeling results and hardware modeling results; According to the association relationship between each logical component and each controller, the software modeling result and the hardware modeling result are matched to obtain the target modeling result of the vehicle to be developed.
6. The method according to claim 5, It is characterized in that The method further comprises: Selecting target software from the software modeling results and selecting target hardware from the hardware modeling results according to the vehicle model configuration information; According to the selected target software and target hardware, target modeling results of the vehicle to be developed under different models are determined.
7. A vehicle development device, It is characterized in that The device comprises: A data acquisition module, used to acquire software requirement data and hardware requirement data for the vehicle to be developed; A software construction module, used to determine the functional subsystems of the vehicle to be developed according to the software requirement data, and to construct logical components corresponding to the functional subsystems; A hardware construction module, configured to configure each controller of the vehicle to be developed according to the hardware requirement data, and to establish an association relationship between each configured controller and each logical component; The vehicle modeling module is used to model the vehicle to be developed according to the associated logical components and controllers to obtain a target modeling result.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program. It is characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product comprising a computer program, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
