Vehicle variant data generation method, apparatus, device, and storage medium

Abstract

The application discloses a vehicle variant data generation method and device, electronic equipment and a storage medium. The vehicle variant data generation method comprises the following steps: obtaining a target vehicle model matched with an initial vehicle model variant component and a target vehicle model variant attribute corresponding to the target vehicle model; traversing all system fields where the initial vehicle model variant component is located, obtaining all vehicle model variant components matched with the target vehicle model variant attribute as target vehicle model variant components; capturing the target vehicle model variant components, entering a variant unit corresponding to the initial vehicle model variant component in a department field where the initial vehicle model variant component is located, and forming a target variant unit; and generating vehicle model variant data according to the target vehicle model and the target variant unit. According to the system fields and the department fields obtained according to the set system boundary and the department boundary, other components matched with the vehicle model are automatically obtained, manual selection of other vehicle model components is not needed, and vehicle model variant data can be created more efficiently and accurately.

Description

Technical Field

[0001] This application relates to the field of vehicle management technology, and more specifically, to a method, apparatus, electronic device, and storage medium for generating vehicle variant data. Background Technology

[0002] In vehicle variant management, a platform model is typically built using Electrical / Electronic Architecture (EEA) tools. Variant units are then generated by manually dragging and dropping or automatically capturing hardware and software components. These variant units are then associated with vehicle model configurations to generate, match, and manage vehicle variant data. However, both dragging and dropping and automatic capture can lead to mismatches between vehicle variant data and variant units, and can easily result in incomplete or redundant vehicle variant data. Summary of the Invention

[0003] In view of the above problems, this application proposes a method, apparatus, electronic device and storage medium for generating vehicle variant data.

[0004] In a first aspect, embodiments of this application provide a method for generating vehicle variant data. The method includes: based on the determination operation of an initial vehicle variant component, obtaining a target vehicle model matching the initial vehicle variant component and a target vehicle variant attribute corresponding to the target vehicle model; traversing all system domains where the initial vehicle variant component is located, obtaining all vehicle variant components matching the target vehicle variant attribute, and using them as target vehicle variant components; capturing the target vehicle variant component, entering the variant unit corresponding to the initial vehicle variant component in the department domain where the initial vehicle variant component is located, and forming a target variant unit; and generating vehicle variant data corresponding to the initial vehicle variant component based on the target vehicle model and the target variant unit.

[0005] In one optional embodiment, the step of grasping the target vehicle variant component, entering the variant unit corresponding to the initial vehicle variant component in the departmental domain where the initial vehicle variant component is located, and forming the target variant unit includes: if the variant unit corresponding to the initial vehicle variant component already exists, grasping the target vehicle variant component, entering the variant unit corresponding to the initial vehicle variant component in the departmental domain where the initial vehicle variant component is located, and forming the target variant unit; if the variant unit corresponding to the initial vehicle variant component does not exist, creating a blank variant unit, grasping the target vehicle variant component, entering the blank variant unit, and forming the target variant unit.

[0006] In one optional embodiment, the step of creating a blank variant unit if the variant unit corresponding to the initial vehicle variant component does not exist, capturing the target vehicle variant component, entering the blank variant unit, and forming the target variant unit includes: if the variant unit corresponding to the initial vehicle variant component does not exist, creating a blank variant unit with the department domain name as a name prefix, capturing the target vehicle variant component, entering the blank variant unit, and forming the target variant unit.

[0007] In one optional embodiment, the system domain refers to multiple system domain boundaries set for the vehicle functions based on functional requirements, and the vehicle functions are divided into multiple system domains according to the multiple system domain boundaries; the department domain refers to multiple department domain boundaries set for the vehicle software based on the vehicle project architecture, and the vehicle software is divided into multiple department domains according to the multiple department domain boundaries.

[0008] In an optional embodiment, the determination operation based on the initial vehicle variant component, obtaining the target vehicle model matching the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle model, includes: obtaining the target vehicle model matching the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle model according to an attribute matching table, wherein the attribute matching table includes the matching relationship between the component variant attributes corresponding to the vehicle variant component and the vehicle variant attributes corresponding to the vehicle model.

[0009] In an optional embodiment, the step of determining the initial vehicle variant component and obtaining the target vehicle model matching the initial vehicle variant component and the target vehicle variant attribute corresponding to the target vehicle model further includes: modifying the matching relationship between the vehicle variant attribute and the component variant attribute in the attribute matching table based on the modification instruction to obtain the latest attribute matching table; and obtaining the target vehicle model matching the initial vehicle variant component and the target vehicle variant attribute corresponding to the target vehicle model based on the latest attribute matching table.

[0010] In one optional embodiment, the step of grasping the target vehicle variant component, entering the variant unit corresponding to the initial vehicle variant component in the departmental field where the initial vehicle variant component is located, and forming the target variant unit further includes: grasping the module component, hardware component, and communication component corresponding to the target variant unit according to the secondary grasping instruction, and entering the target variant unit.

[0011] Secondly, embodiments of this application provide a vehicle variant data generation apparatus, the apparatus comprising: a target vehicle model information acquisition module, configured to acquire a target vehicle model matching the initial vehicle model variant component and a target vehicle model variant attribute corresponding to the target vehicle model based on an initial vehicle model variant component determination operation; a target vehicle model variant component acquisition module, configured to traverse all system domains where the initial vehicle model variant component is located, acquire all vehicle model variant components matching the target vehicle model variant attribute, and use them as target vehicle model variant components; a target variant unit acquisition module, configured to capture the target vehicle model variant component, enter the variant unit corresponding to the initial vehicle model variant component in the department domain where the initial vehicle model variant component is located, and form a target variant unit; and a vehicle model variant data generation module, configured to generate vehicle model variant data corresponding to the initial vehicle model variant component based on the target vehicle model and the target variant unit.

[0012] Thirdly, embodiments of this application provide an electronic device, including: one or more processors; a memory; and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, and the one or more application programs are configured to perform the vehicle variant data generation method provided in the first aspect above.

[0013] Fourthly, embodiments of this application provide a computer-readable storage medium storing program code, which can be invoked by a processor to execute the method for generating vehicle variant data provided in the first aspect above.

[0014] The solution provided in this application first matches the corresponding vehicle model and vehicle model attributes to the initial vehicle model variant components, and then automatically obtains other components that match the vehicle model based on the system domain and department domain obtained from the set system boundary and department boundary. This eliminates the need for users to manually select other vehicle model components, thereby creating vehicle model variant data more efficiently and accurately. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 A flowchart illustrating a method for generating vehicle variant data according to an embodiment of this application is shown.

[0017] Figure 2 A schematic diagram of system domain division according to an embodiment of this application is shown.

[0018] Figure 3 A schematic diagram of departmental division in one embodiment of this application is shown.

[0019] Figure 4 A schematic diagram of the module component connection in a blank variant unit model of this application is shown.

[0020] Figure 5 A schematic diagram of the hardware system in a blank variant unit model of one embodiment of this application is shown.

[0021] Figure 6 A structural block diagram of a vehicle variant data generation apparatus provided in an embodiment of this application is shown.

[0022] Figure 7 A structural block diagram of an electronic device for performing a power regulation method according to an embodiment of the present application is shown. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0024] In response to the technical problems raised in the background art, the inventors proposed a method, device, electronic device, and storage medium for generating vehicle variant data. First, the initial vehicle variant components are matched with corresponding vehicle models and vehicle model attributes. Then, based on the system domain and department domain obtained from the set system boundary and department boundary, other components that match the vehicle model are automatically obtained. Users do not need to manually select other vehicle model components, thus creating vehicle variant data more efficiently and accurately.

[0025] Please see Figure 1 , Figure 1 A flowchart illustrating a method for generating vehicle variant data according to an embodiment of this application is shown. In a specific embodiment, the method for generating vehicle variant data is applied to, for example... Figure 6 The vehicle variant data generation device 300 shown, and the device equipped with the vehicle variant data generation device 300 Figure 7 The electronic device 100 shown.

[0026] The following will address Figure 1 The process shown will be described in detail. The method for generating vehicle variant data may specifically include the following steps:

[0027] Step S110: Based on the determination operation of the initial vehicle variant component, obtain the target vehicle that matches the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle.

[0028] Vehicle model variant components refer to components that need to be modified to fit different vehicle models during the processing of a certain automotive component.

[0029] The confirmation operation can be a user's click confirmation operation on the initial vehicle model variant component via the human-computer interaction interface, or a user's input operation on the initial vehicle model variant component via the human-computer interaction interface. In the embodiments of this application, no specific limitation is made to the confirmation operation.

[0030] A variant attribute refers to the attribute corresponding to the vehicle model it is adapted to. This variant attribute is a custom attribute, and it's important to know that the component variant attribute should correspond to the vehicle model variant attribute of the adapted vehicle. For example, a component may have variant attributes of Level 1, Level 2, and Level 3. In this case, the vehicle model variant attribute adapted to the component variant attribute corresponding to the Level 1 component is a Level 1 vehicle model, the vehicle model variant attribute adapted to the component variant attribute corresponding to the Level 2 component is a Level 2 vehicle model, and the vehicle model variant attribute adapted to the component variant attribute corresponding to the Level 3 component is a Level 3 vehicle model. It's understandable that variant attributes can also be represented using letters, etc., and the specific representation method is not specifically limited here.

[0031] The component variation attributes of vehicle model variant components can be automatically inherited from the parent component attributes or annotated by referring to existing variant component attributes. Therefore, the component variation attributes of vehicle model variant components can be automatically generated based on the parent component attributes. This reduces the error rate of component variation attribute definition and improves work efficiency to a certain extent. For example, the variant components of the temperature control parent component are a level 1 temperature control variant component and a level 2 temperature control variant component. The temperature control parent component corresponds to the level 1 vehicle model variation attributes and the level 2 vehicle model variation attributes. When the level 1 temperature control variant component and the level 2 temperature control variant component inherit the attributes corresponding to the temperature control parent component, both the level 1 temperature control variant component and the level 2 temperature control variant component can correspond to the level 1 vehicle model variation attributes and the level 2 vehicle model variation attributes.

[0032] In some implementations, a target vehicle model matching the initial vehicle model variant component and the target vehicle model variant attributes corresponding to the target vehicle model can be obtained based on an attribute matching table.

[0033] The attribute matching table includes the matching relationships between the component variation attributes corresponding to the vehicle model variation components and the vehicle model variation attributes corresponding to the vehicle model. The attribute matching table can be obtained from the cloud or the internal storage of the EEA tool.

[0034] The attribute matching table can be shown in the following table:

[0035]

[0036] Table 1

[0037] Table 1 shows that vehicle model variant components with only Level 1 component attributes can only match Level 1 vehicle models. Similarly, vehicle model variant components with only Level 2 component attributes can only match Level 2 vehicle models. || indicates "can," meaning Level 1 || Level 2 means the component can match both Level 1 and Level 2 vehicle models, and must exist in either Level 1 or Level 2 vehicle models. & indicates "must," meaning Level 1 & Level 2 means the component must match both Level 1 and Level 2 vehicle models. Optional indicates the component can match any vehicle model or not; the component variant attributes are not limited.

[0038] In other implementations, based on modification instructions, the matching relationship between vehicle variant attributes and component variant attributes in the attribute matching table can be modified to obtain the latest attribute matching table; according to the latest attribute matching table, the target vehicle model matching the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle model can be obtained.

[0039] When a user modifies the matching relationship between vehicle variant attributes and component variant attributes in the attribute matching table, subsequent vehicle model matching and component matching methods are verified based on the latest attribute matching table. The matching operation based on the latest attribute matching table is described in the above embodiment and will not be repeated here. The latest attribute matching table can be synchronized to multiple terminals via the cloud to ensure that multiple matching terminals obtain the latest attribute matching table, thus guaranteeing the correctness of the matching.

[0040] Step S120: Traverse all system domains where the initial vehicle variant component is located, and obtain all vehicle variant components that match the target vehicle variant attributes, as the target vehicle variant component.

[0041] By analyzing user functional requirements, the functions of the whole vehicle are divided into several logical domains. By further analyzing and decomposing the functions in the logical domains, the logical domains are further decomposed into multiple system domains.

[0042] Please see Figure 2 , Figure 2 This diagram illustrates a system domain division according to an embodiment of this application. Based on functional requirements, multiple system domain boundaries are defined for the vehicle's functions. According to these multiple system domain boundaries, the vehicle's functions are divided into multiple system domains. For example, vehicle functions include, but are not limited to, control functions and interaction functions; the control functions and interaction functions are each defined as a domain. The system domains within the control domain include the driver's side air conditioning control system, the passenger's side air conditioning control system, the parking system, and the driving control system. The system domains within the interaction domain include, but are not limited to, the human-machine interaction system and the vehicle interaction system.

[0043] A single vehicle model variant component can be used in multiple system domains. For example, a Level 1 component can be applied not only to the driver's side air conditioning control system but also to the parking system and driving control system, while a Level 2 component can be used in the driver's side air conditioning control system, passenger side air conditioning control system, parking system, and driving control system. By iterating through the driver's side air conditioning control system, parking system, and driving control system, all vehicle model variant components matching the vehicle model attributes corresponding to the Level 1 component are obtained and used as the target vehicle model variant component. The specific acquisition table is as follows:

[0044]

[0045] Table 2

[0046] As shown in Table 2, the component attributes corresponding to vehicle variant components matching Level 1 vehicle models can be vehicle variant components that only match Level 1 component attributes, vehicle variant components that match Level 1||Level 2 component attributes, vehicle variant components that match both Level 1 and Level 2 component attributes, or even vehicle variant components with optional component attributes. It's important to note that when the component attributes are Level 1||Level 2 and optional, it means that both Level 1 and Level 2 vehicle model attributes match. In this case, vehicle variant components with Level 1||Level 2 and optional attributes will not be automatically retrieved; they need to be retrieved manually. The retrieval method could be that when traversing all system domains containing the initial vehicle variant component, if a vehicle variant component with Level 1||Level 2 and optional attributes is found, feedback information is sent to the user, allowing the user to determine whether such a component should be used as the target vehicle variant component. The specific method of sending feedback information is not limited here. In the embodiments of this application, multiple vehicle model variant components obtained from multiple system domains can be placed in a data cache area for subsequent retrieval and other operations. The data cache area can be a virtual data cache area or a physical cache area, such as a physical cache area like Random Access Memory (RAM). The type of data cache area is not specifically limited here.

[0047] Step S130: Grab the target vehicle variant component, enter the variant unit corresponding to the initial vehicle variant component in the departmental field where the initial vehicle variant component is located, and form the target variant unit.

[0048] Based on the overall vehicle project architecture, and combined with the project architecture and the ownership of system components, the vehicle software is divided into several professional domain components by department; then, through departmental nesting, a large professional domain is broken down into smaller granular technical professional domain components, until it is decomposed into software and hardware components. For example, the vehicle project is divided into the electronic and electrical department domain, the drive department domain, and the human-machine interaction department domain.

[0049] Specifically, based on the overall vehicle project architecture, multiple departmental domain boundaries are set for the vehicle software; and the vehicle software is divided into multiple departmental domains according to the multiple departmental domain boundaries.

[0050] Please see Figure 3 , Figure 3 This illustration shows a schematic diagram of departmental domain division in one embodiment of this application. Departmental domain boundaries are set according to the vehicle project architecture. Each domain within its boundary is considered a single departmental domain. These departmental domains can be further subdivided to obtain specific components. The project architecture includes, but is not limited to, electronic and electrical architecture, drive architecture, and human-machine interface architecture. For example, the vehicle project architecture can be divided into an electronic and electrical departmental domain and a drive departmental domain. Further subdivision of the electronic and electrical departmental domain yields vehicle-specific components such as the driver's side air conditioning switch and the passenger side air conditioning switch.

[0051] In some implementations, if the variant unit corresponding to the initial vehicle variant component already exists, the target vehicle variant component is retrieved, and the variant unit corresponding to the initial vehicle variant component in the departmental domain where the initial vehicle variant component is located is entered to form the target variant unit.

[0052] Determining whether a variant unit corresponding to the initial vehicle model variant component exists can be done by searching for a variant unit named after the initial vehicle model variant component among existing variant units. If a variant unit named after the initial vehicle model variant component exists, then the variant unit corresponding to that initial vehicle model variant component is determined to exist. The target vehicle model variant component in the cache is then retrieved into the variant unit, thereby forming the target variant unit. In the embodiments of this application, the target variant unit refers to the set of all vehicle model variant components that match the vehicle model attributes corresponding to a certain vehicle model in one or more system domains.

[0053] In other embodiments, if the variant unit corresponding to the initial vehicle variant component does not exist, a blank variant unit is created, the target vehicle variant component is captured, and the blank variant unit is entered to form the target variant unit.

[0054] If the variant unit corresponding to the initial vehicle model variant component does not exist, a blank variant unit is created, and the target vehicle model variant component in the buffer area is captured and entered into the blank variant unit to form the target variant unit. If the variant unit already contains one or more vehicle model variant components, and the existing vehicle model variant components overlap with the components of the target vehicle model variant component, only the non-overlapping target vehicle model variant components can be captured and entered into the variant unit to form the target variant unit. Alternatively, the target vehicle model variant component can be directly captured and entered into the variant unit, maintaining the existence of the original vehicle model variant components in the variant unit, and overlapping vehicle model variant components do not affect each other. The formation of the target variant unit is not specifically limited here.

[0055] Specifically, if the variant unit corresponding to the initial vehicle variant component does not exist, a blank variant unit with the department / domain name as the name prefix is ​​created, the target vehicle variant component is captured, and the blank variant unit is entered to form the target variant unit.

[0056] To better identify and query the blank variant unit in subsequent use, it can be named using the department / domain name as a prefix, combined with preset naming rules. Then, the target vehicle variant component in the cache is retrieved and added to the named blank variant unit to form the target variant unit. For example, if the initial vehicle variant component is the driver's side air conditioning control switch, and this initial vehicle variant component exists in both the driver's side air conditioning control system and the vehicle air conditioning control system, then according to the attribute matching table, all vehicle variant components in the driver's side air conditioning control system and the vehicle air conditioning control system that match the vehicle attributes corresponding to the initial vehicle variant component are retrieved to form the target vehicle variant component. Since the initial vehicle variant component also exists in the electronics / electrical department domain, it is first determined whether a variant unit for the initial vehicle variant component exists in the electronics / electrical department. If the variant unit exists, the target vehicle variant component is retrieved and added to that variant unit to form the target variant unit. If the variant unit does not exist, a new blank variant unit is created, named using the department / domain name as a prefix, for example, "Electronics / Electrical_Driver's Side Air Conditioning Control Switch". After naming the blank variant unit, the target vehicle variant component is captured and entered into the blank variant unit to form the target variant unit.

[0057] In some other implementations, according to the secondary capture instruction, the module components, hardware components and communication components corresponding to the target variant unit are captured, and the target variant unit is entered.

[0058] A module component refers to a module component encapsulated from multiple control instruction module components or execution instructions. This module component is a software module and is also equipped with connection ports to facilitate the connection of multiple module components.

[0059] Hardware components refer to hardware simulation components obtained by integrating actual hardware modules. These hardware components simplify the pins of the actual hardware into connection ports, facilitating the connection of multiple hardware components. Hardware components include, but are not limited to, electronic control units (ECUs) and connectors.

[0060] A communication component is a simulated component that has a communication function. A communication component can enable communication between multiple module components.

[0061] In the EEA tool, users can create a new blank variant unit model and then select the target variant unit by dragging and dropping. After obtaining the target variant unit, the module component containing the target variant unit, the corresponding hardware component, the implementing module component, and the communication component of the hardware component can be dragged and dropped. On the blank variant unit model, the module components are first connected via connection ports. Then, based on the connection logic of the module components, a corresponding software system diagram is formed. The hardware components corresponding to the module components are connected using the same connection logic. Finally, the communication components corresponding to the module components are obtained manually or through mapping relationships, thereby realizing communication between the module components and forming a hardware system diagram corresponding to the software system diagram. Hardware components can communicate directly via port connections or through communication components. Mapping relationships refer to mapping relationships; different control instruction module components can map to different or the same communication components. The mapping relationship between control instruction module components and communication components is not limited here.

[0062] The modular components, hardware components, and communication components are in one-to-one correspondence, so that each modular component corresponds to a hardware component and a corresponding communication component. This not only allows for the simulation of hardware connection and communication in the variant unit, but also enables wireless communication by relying on the communication component.

[0063] For example, please see Figure 4 , Figure 4 The diagram illustrates the connection of module components in a blank variant unit model according to one embodiment of this application. The control command module component is the main driver's side temperature control switch, the corresponding main control module component is the main driver's side temperature control_main control, and the corresponding execution module component is the main driver's side temperature damper motor. The control command module component, the main control module component, and the execution module component are connected sequentially through corresponding ports.

[0064] This application also provides a voice control signal scheme, which acquires the user's input voice signal for setting the driver's side temperature, sends the voice signal to the driver's side temperature control main control module, and outputs the voice control signal through the driver's side temperature control main control module. Other module components then perform further voice control signal recognition, thereby controlling the execution module to work according to the voice control signal.

[0065] For example, please see Figure 5 , Figure 5This diagram illustrates the hardware system in a blank variant unit model according to one embodiment of this application. The control command hardware component corresponding to the driver's side temperature control switch module is the air conditioning switch panel_0, the main control hardware component corresponding to the driver's side temperature control_main control module is the hardware AC, and the execution module component corresponds to the execution hardware component of the damper motor hardware. The hardware system diagram corresponding to the module component is formed by connecting the KA_air conditioning switch panel_0 port to the KA_AC_1 port of the hardware AC, and then connecting the KA_AC_0 port to the KA_driver's side temperature damper motor_0 port of the damper motor hardware.

[0066] Step S140: Generate vehicle variant data corresponding to the initial vehicle variant component based on the target vehicle model and the target variant unit.

[0067] Vehicle variant data refers to data composed of multiple vehicle models and their corresponding variant attributes, multiple variant components and their corresponding component variant attributes.

[0068] Based on the target vehicle model matched with the initial vehicle model variant component and the target variant unit corresponding to the initial vehicle model variant component, vehicle model variant data corresponding to the initial vehicle model variant component is generated. In the EEA tool, different vehicle model variant data are quickly generated based on different initial vehicle model variant components. Then, multiple vehicle model variant schemes for the same vehicle model are formulated based on different vehicle model variant data, improving the efficiency of variant scheme formulation. It can also determine specific vehicle model variant components according to user needs, thereby quickly generating specific vehicle model variant data based on those specific components, and thus quickly and accurately completing the formulation of specific vehicle model schemes to improve the user experience.

[0069] In this embodiment, the corresponding vehicle model and vehicle model attributes are first matched to the initial vehicle model variant components. Then, based on the system domain and department domain obtained from the set system boundary and department boundary, other components that match the vehicle model are automatically obtained. Users do not need to manually select other vehicle model components, thus creating vehicle model variant data more efficiently and accurately.

[0070] Please see Figure 6This document illustrates a structural block diagram of a vehicle variant data generation device 300 provided in an embodiment of this application. The vehicle variant data generation device 300 is applied to a vehicle 100 and includes: a target vehicle model information acquisition module 310, used to acquire a target vehicle model matching the initial vehicle model variant component and the target vehicle model variant attributes corresponding to the target vehicle model based on an initial vehicle model variant component determination operation; a target vehicle model variant component acquisition module 320, used to traverse all system domains where the initial vehicle model variant component is located and acquire all vehicle model variant components matching the target vehicle model variant attributes, as target vehicle model variant components; a target variant unit acquisition module 330, used to capture the target vehicle model variant component, enter the variant unit corresponding to the initial vehicle model variant component in the department domain where the initial vehicle model variant component is located, and form a target variant unit; and a vehicle model variant data generation module 340, used to generate vehicle model variant data corresponding to the initial vehicle model variant component based on the target vehicle model and the target variant unit.

[0071] In some embodiments of this application, the target variant unit acquisition module 330 includes: a target vehicle variant component grabbing module, used to grab the target vehicle variant component if the variant unit corresponding to the initial vehicle variant component already exists, enter the variant unit corresponding to the initial vehicle variant component in the department field where the initial vehicle variant component is located, and form a target variant unit; and a blank variant unit creation module, used to create a blank variant unit if the variant unit corresponding to the initial vehicle variant component does not exist, grab the target vehicle variant component, enter the blank variant unit, and form a target variant unit.

[0072] In some embodiments of this application, the blank variant unit creation module includes: a naming module, used to create a blank variant unit with the department domain name as the name prefix if the variant unit corresponding to the initial vehicle variant component does not exist, capture the target vehicle variant component, enter the blank variant unit, and form a target variant unit.

[0073] In some embodiments of this application, the vehicle variant data generation device 300 further includes: a system domain boundary setting module, used to set multiple system domain boundaries for vehicle functions based on functional requirements; a system domain division module, used to divide the vehicle functions into multiple system domains according to the multiple system domain boundaries; a department domain boundary setting module, used to set multiple department domain boundaries for vehicle software based on the vehicle project architecture; and a department domain division module, used to divide the vehicle software into multiple department domains according to the multiple department domain boundaries.

[0074] In some embodiments of this application, the variant unit component module includes: a matching module, used to obtain a target vehicle model that matches the initial vehicle model variant component and a target vehicle model variant attribute corresponding to the target vehicle model according to an attribute matching table, wherein the attribute matching table includes the matching relationship between the component variant attribute corresponding to the vehicle model variant component and the vehicle model variant attribute corresponding to the vehicle model.

[0075] In some embodiments of this application, the matching module includes: a modification module, used to modify the matching relationship between vehicle variant attributes and component variant attributes in the attribute matching table based on modification instructions, and obtain the latest attribute matching table; and a latest attribute matching table matching module, used to obtain the target vehicle model that matches the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle model according to the latest attribute matching table.

[0076] In some embodiments of this application, the vehicle variant data generation device 300 further includes: a secondary capture module, used to capture the module components, hardware components and communication components corresponding to the target variant unit according to the secondary capture instructions, and enter the target variant unit.

[0077] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described device and module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0078] In the several embodiments provided in this application, the coupling between modules can be electrical, mechanical, or other forms of coupling.

[0079] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0080] Please refer to Figure 7 This document illustrates a structural block diagram of an electronic device provided in an embodiment of this application. The electronic device 100 can be a switch, a computer, or a control unit with data transmission capabilities. The electronic device 100 in this application may include one or more of the following components: a processor 110, a memory 120, and one or more application programs. The one or more application programs may be stored in the memory 120 and configured to be executed by one or more processors 110. The one or more programs are configured to perform the methods described in the foregoing method embodiments.

[0081] Processor 110 may include one or more processing cores. Processor 110 connects to various parts within the electronic device 100 using various interfaces and lines, and performs various functions and processes data of the electronic device 100 by running or executing instructions, programs, code sets, or instruction sets stored in memory 120, and by calling data stored in memory 120. Optionally, processor 110 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 110 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into processor 110 and may be implemented separately using a communication chip.

[0082] The memory 120 may include random access memory (RAM) or read-only memory (ROM). The memory 120 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 120 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch functionality, sound playback functionality, image playback functionality, etc.), and instructions for implementing the various method embodiments described below. The data storage area may also store data created by the electronic device 100 during use (such as phonebook data, audio and video data, chat log data, etc.).

[0083] This application also provides a computer-readable storage medium storing program code, which can be called by a processor to execute the methods described in the above method embodiments.

[0084] Computer-readable storage media can be electronic storage devices such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. Optionally, computer-readable storage media includes non-transitory computer-readable storage medium. The computer-readable storage medium has storage space for program code that performs any of the method steps described above. This program code can be read from or written to one or more computer program products. The program code can be compressed, for example, in a suitable form.

[0085] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for generating vehicle variant data, characterized in that, The method includes: Based on the determination operation of the initial vehicle variant component, the target vehicle that matches the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle are obtained; Traverse all system domains where the initial vehicle variant component is located, and obtain all vehicle variant components that match the target vehicle variant attributes, as the target vehicle variant component; Grab the target vehicle variant component, enter the variant unit corresponding to the initial vehicle variant component in the departmental field where the initial vehicle variant component is located, and form the target variant unit; Based on the target vehicle model and the target variant unit, generate vehicle variant data corresponding to the initial vehicle variant component.

2. The method as described in claim 1, characterized in that, The process of grasping the target vehicle variant component, entering the variant unit corresponding to the initial vehicle variant component in the departmental field where the initial vehicle variant component is located, and forming the target variant unit includes: If the variant unit corresponding to the initial vehicle variant component already exists, grab the target vehicle variant component, enter the variant unit corresponding to the initial vehicle variant component in the department field where the initial vehicle variant component is located, and form the target variant unit; If the variant unit corresponding to the initial vehicle variant component does not exist, a blank variant unit is created, the target vehicle variant component is captured, and it enters the blank variant unit to form the target variant unit.

3. The method as described in claim 2, characterized in that, If the variant unit corresponding to the initial vehicle variant component does not exist, a blank variant unit is created, the target vehicle variant component is retrieved, and the blank variant unit is entered to form the target variant unit, including: If the variant unit corresponding to the initial vehicle variant component does not exist, a blank variant unit with the department domain name as the name prefix is ​​created, the target vehicle variant component is captured, and the blank variant unit is entered to form the target variant unit.

4. The method as described in claim 1, characterized in that, The system domain refers to the multiple system domain boundaries set for the functions of the whole vehicle based on functional requirements, and the vehicle functions are divided into multiple system domains according to the multiple system domain boundaries; The term "department domain" refers to the multiple department domain boundaries set for the vehicle software based on the vehicle project architecture, and the vehicle software being divided into multiple department domains according to these multiple department domain boundaries.

5. The method as described in claim 1, characterized in that, The determination operation based on the initial vehicle variant component obtains the target vehicle model matching the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle model, including: According to the attribute matching table, the target vehicle model that matches the initial vehicle model variant component and the target vehicle model variant attributes corresponding to the target vehicle model are obtained. The attribute matching table includes the matching relationship between the component variant attributes corresponding to the vehicle model variant component and the vehicle model variant attributes corresponding to the vehicle model.

6. The method as described in claim 5, characterized in that, The determination operation based on the initial vehicle variant component, which obtains the target vehicle matching the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle, further includes: Based on the modification command, the matching relationship between vehicle variant attributes and component variant attributes in the attribute matching table is modified to obtain the latest attribute matching table; Based on the latest attribute matching table, obtain the target vehicle model that matches the initial vehicle model variant component and the target vehicle model variant attributes corresponding to the target vehicle model.

7. The method as described in claim 1, characterized in that, The step of grasping the target vehicle variant component, entering the variant unit corresponding to the initial vehicle variant component in the departmental field where the initial vehicle variant component is located, and forming the target variant unit, further includes: According to the secondary capture instruction, the module components, hardware components and communication components corresponding to the target variant unit are captured, and the target variant unit is entered.

8. A device for generating vehicle variant data, characterized in that, The device includes: The target vehicle information acquisition module is used to acquire the target vehicle that matches the initial vehicle variant component and the target vehicle variant attributes corresponding to the target vehicle based on the determination operation of the initial vehicle variant component; The target vehicle variant component acquisition module is used to traverse all system domains where the initial vehicle variant component is located, and acquire all vehicle variant components that match the target vehicle variant attributes, as the target vehicle variant component; The target variant unit acquisition module is used to capture the target vehicle variant component, enter the variant unit corresponding to the initial vehicle variant component in the department field where the initial vehicle variant component is located, and form a target variant unit; The vehicle model variant data generation module is used to generate vehicle model variant data corresponding to the initial vehicle model variant component based on the target vehicle model and the target variant unit.

9. An electronic device, characterized in that, include: One or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications being configured to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium contains program code that can be invoked by a processor to execute the method as described in any one of claims 1-7.

Images