Vehicle terminal model digital binding method, device and equipment and storage medium

Abstract

The application provides a vehicle terminal model digital binding method and device, equipment and a storage medium. The method creates a component representation model based on a component description model, obtains a component representation list of each component description model, and a representation model structure space constraint list that constrains the spatial relationship between the component representation models, configures a preset attribute for the component representation model, obtains a preset attribute list of each component description model, writes the above three lists into a twin binding relationship configuration table, and binds to a vehicle terminal to be bound. When the subsequent vehicle terminal to be bound has a demand change, when the existing vehicle components need to be adjusted, at least one of the component representation list, the representation model structure space constraint list and the preset attribute list in the twin binding relationship configuration table can be directly adjusted, without adjusting the component description model, avoiding cross-domain changes, and not affecting the entire system.

Description

Technical Field

[0001] This invention relates to the field of vehicles, specifically to a method, apparatus, device, and storage medium for digitally binding vehicle terminal models. Background Technology

[0002] In the field of digital twin applications, 3D reconstruction of digital twin entities is a crucial means of data representation in digital twin systems and the final stage of the digital twin implementation process. A typical digital twin system comprises a five-layer architecture: user domain, digital twin domain, measurement and control entity, reality domain, and cross-domain entity. 3D reconstruction belongs to the user domain architecture, characterized by flexibility and realism. Meanwhile, the description model construction, as a vital component of the cross-domain entity, connects the other four domains and plays a crucial role in data interoperability and security, thus requiring stability. Both have different system objectives due to their different service targets.

[0003] In the process of 3D reconstruction, to make the representation results more intuitive and accurate, the requirements for 3D representation models are becoming increasingly refined, and the granularity of 3D representation features is becoming increasingly finer. This leads to higher demands on the variability of the representation. In the current component description model and component representation model binding scheme, the one-to-one binding structure between the description model component and the 3D representation model means that if there are changes such as different models, different spatial relationships, or functional adjustments to the same component, the component description model needs to be adjusted to achieve the desired result. This leads to cross-domain changes, which can affect the entire system, prolong the development cycle of new functions, and even cause conflicts between the old and new systems. This results in poor stability and reusability of the component description model. Summary of the Invention

[0004] In view of the shortcomings of the prior art described above, the present invention provides a method, device, equipment and storage medium for digital binding of vehicle terminal models, in order to solve the technical problem that when changes occur to the same component with different models, different spatial relationships, or functional adjustments, the component description model needs to be adjusted to achieve the desired result. This leads to cross-domain changes, which will affect the entire system, prolong the development cycle of new functions, and even cause conflicts between the old and new systems, resulting in poor stability and reusability of the component description model.

[0005] The present invention provides a method for digitally binding a vehicle terminal model, the method comprising: obtaining a component description model of a vehicle component, the component description model being generated based on a component representation model requirement list; creating a component representation model of the vehicle component based on the component description model, thereby obtaining a component representation model list of the component description model; establishing a representation model structural space constraint list based on the entity spatial constraint relationships of the entity components corresponding to all component representation models; configuring preset attributes for the component representation model, the preset attributes being determined based on the component representation model requirement list, thereby obtaining a preset attribute list of the component description model; establishing a twin binding relationship configuration table, writing the component representation model list, the representation model structural space constraint list, and the preset attribute list into the twin binding relationship configuration table, and binding the written twin binding relationship configuration table to the vehicle terminal to be bound, thereby performing model digital binding on the vehicle terminal to be bound.

[0006] In one embodiment of the present invention, creating a component representation model based on the component description model includes: obtaining a model entity object design drawing of a vehicle and determining the entity object space design; defining the description model representation requirements of the component description model according to the component description model and the entity object space design, and generating the representation model definition and description model representation design of the component representation model; integrating the description model component code, description model representation requirements, and representation model definition of the component representation model to generate a description definition association list representing the association relationship between the component description model and the representation model definition; and querying historical representation models from a preset art workflow based on the description definition association list and the description model representation design, and using the historical representation models as the component representation model.

[0007] In one embodiment of the present invention, a list of structural space constraints for representation models is established based on the entity space constraint relationships of the entity components corresponding to all component representation models. This includes: establishing model space constraint relationships between each component representation model based on the entity space constraint relationships of the entity components corresponding to all component representation models; applying model space constraints to each component representation model based on all the model space constraint relationships; and establishing a list of structural space constraints for representation models based on the constraint results of the model space constraints of each component representation model.

[0008] In one embodiment of the present invention, model space constraint relationships between component representation models are established based on the entity space constraint relationships of the entity components corresponding to all component representation models. Model space constraints are applied to each component representation model based on all said model space constraint relationships, including at least one of the following: if the entity space constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a positional constraint, an offset is added to the spatial position of the first component representation model to lock and cover the spatial position of the second component representation model; if the entity space constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a rotational constraint, an offset is added to the spatial orientation of the first component representation model to lock and cover the spatial orientation of the second component representation model. The second component represents the spatial attitude of the model. If the spatial constraint relationship between the first entity component corresponding to the first component representing the model and the second entity component corresponding to the second component representing the model is a scaling constraint, the spatial scaling of the first component representing the model is superimposed with an offset to lock and cover the spatial scaling of the second component representing the model. If the spatial constraint relationship between the first entity component corresponding to the first component representing the model and the second entity component corresponding to the second component representing the model is a parent-child constraint, the first component representing the model is set as the target model source. If the spatial constraint relationship between the first entity component corresponding to the first component representing the model and the second entity component corresponding to the second component representing the model is a target constraint, the spatial position of the first component representing the model is superimposed with an offset to lock the Z-axis of the second component representing the model pointing to the target.

[0009] In one embodiment of the present invention, after establishing a twin binding relationship configuration table and writing the component representation model list, the representation model structure space constraint list, and the preset attribute list into the twin binding relationship configuration table, the method further includes: publishing the written twin binding relationship configuration table to a preset server, and managing the twin binding relationship configuration table using the twin instance code of the twin binding relationship configuration table as the management primary key.

[0010] In one embodiment of the present invention, managing the twin binding relationship configuration table includes: obtaining the twin instance code and reconstruction requirements of the terminal model to be rebuilt; querying multiple twin binding relationship configuration tables stored in the preset server through the twin instance code of the terminal model to be rebuilt to obtain a target twin binding relationship configuration table; and reconstructing and adjusting the target twin binding relationship configuration table according to the reconstruction requirements.

[0011] In one embodiment of the present invention, the reconstruction and adjustment of the target twin binding relationship configuration table according to the reconstruction requirements includes at least one of the following: determining the model addresses of multiple component representation models based on the target twin binding relationship configuration table, retrieving the resources of the target component representation model from the model addresses, and loading them into memory to adjust the target component representation model according to the reconstruction requirements; determining a representation model structure space constraint list based on the target twin binding relationship configuration table to adjust the representation model structure space constraint list according to the reconstruction requirements; and determining preset attributes of multiple component representation models based on the target twin binding relationship configuration table to adjust the preset attributes of at least one component representation model according to the reconstruction requirements.

[0012] In one embodiment of the present invention, before reconstructing and adjusting the target twin binding relationship configuration table according to the reconstruction requirements, the method further includes: if the reconstruction requirements include new component requirements, generating a new component description model based on the new component requirements, and a new component representation model, a list of new component representation models, a list of new preset attributes, and a list of new representation model structural space constraints of the new component description model, so that the twin binding relationship configuration table can be adjusted based on the list of new component representation models, the list of new preset attributes, the list of new representation model structural space constraints, and the preset attributes of each of the new component representation models.

[0013] In one embodiment of the present invention, binding the written twin binding relationship configuration table to the vehicle terminal to be bound includes: obtaining the terminal binding requirements of multiple optional vehicle terminals; if the terminal binding requirements match the component representation model requirement list, determining the optional vehicle terminal as the vehicle terminal to be bound; and binding the written twin binding relationship configuration table to the vehicle terminal to be bound.

[0014] This invention provides a vehicle terminal model digital binding device, comprising: an acquisition module for acquiring component description models of vehicle components, the component description models being generated based on a component representation model requirement list; a component representation model list generation module for creating component representation models of the vehicle components based on the component description models, thereby obtaining a component representation model list of the component description models; a representation model structure space constraint list generation module for establishing a representation model structure space constraint list based on the entity space constraint relationships of the entity components corresponding to all component representation models; a preset attribute list generation module for configuring preset attributes for the component representation models, the preset attributes being determined based on the component representation model requirement list, thereby obtaining a preset attribute list of the component description models; and a binding module for establishing a twin binding relationship configuration table, writing the component representation model list, the representation model structure space constraint list, and the preset attribute list into the twin binding relationship configuration table, and binding the written twin binding relationship configuration table to the vehicle terminal to be bound, thereby performing model digital binding on the vehicle terminal to be bound.

[0015] An electronic device provided in this invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device enables the method described in any of the above embodiments.

[0016] The present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer processor, causes the computer to perform the method described in any of the above embodiments.

[0017] The beneficial effects of this invention are as follows: The vehicle terminal model digital binding method, device, equipment, and storage medium provided by this invention create a component representation model based on a component description model, obtaining a component representation list for each component description model, and a representation model structure space constraint list that constrains the spatial relationship between each component representation model based on the entity space constraint relationship of the entity components corresponding to all component representation models. Preset attributes are configured for each component representation model, obtaining a preset attribute list for each component description model. These three lists are written into a twin binding relationship configuration table and bound to the vehicle terminal to be bound. This allows for adjustments to existing vehicle components when the requirements of the vehicle terminal to be bound change. Adjustments can be made directly by modifying at least one of the component representation list, representation model structure space constraint list, and preset attribute list in the twin binding relationship configuration table, without needing to adjust the component description model. This avoids cross-domain changes, does not affect the entire system, reduces the development time of new functions, improves the stability and reusability of the component description model, and avoids the potential risk of conflicts between old and new systems due to adjustments to the component description model.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0020] Figure 1 A schematic diagram illustrating a 3D representation model structure in a related art, as shown in an exemplary embodiment of this application;

[0021] Figure 2 A schematic diagram illustrating a novel 3D representation model structure for an exemplary embodiment of this application;

[0022] Figure 3 This is a flowchart illustrating a vehicle terminal model digital binding method in an exemplary embodiment of this application;

[0023] Figure 4 A schematic diagram illustrating the structure of a 3D representation model in another related art, as shown in an exemplary embodiment of this application;

[0024] Figure 5 When the 3D model representing changes, Figure 2 and Figure 4 The diagram shows two ways to adjust the structure of the 3D representation model.

[0025] Figure 6 A schematic diagram illustrating the relationship between the 3D representation model structure generation configuration content and data association provided in an embodiment of this application, as shown in an exemplary embodiment of this application;

[0026] Figure 7 A schematic diagram illustrating the cross-domain system design principles provided in an embodiment of this application, for an exemplary embodiment of this application;

[0027] Figure 8 This is a block diagram illustrating a vehicle terminal model digital binding device in an exemplary embodiment of this application;

[0028] Figure 9 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0029] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0030] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0031] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0032] Please see Figure 1 , Figure 1 A schematic diagram illustrating a 3D representation model structure in a related art, as shown in an exemplary embodiment of this application, is provided. Figure 1 As shown, the current 3D binding method establishes a description model based on a specific model within a specific vehicle series. Figure 1 The description model (1) in the figure includes Component 1, Component 2, Component 3, etc., and is classified accordingly. It is organized and managed using components as the basic unit, and types can have subclasses. During 3D binding, there is a one-to-one relationship between the model and the component. When a model is associated with a component, the component's attributes are bound to the 3D model. It is evident that, given the needs of communication and the granularity of business decomposition, the description model cannot infinitely refine the component hierarchy. However, to achieve a more refined representation, a more granular representation model is required to express the representational features. Different models of the same component have different representational granularities, spatial relationships, and representational expressions. For a single component description model, it is not scalable. To achieve different levels, different spatial relationships, and different expressions, the description model needs to be adjusted in reverse, which would lead to cross-domain changes, affecting the entire system and rendering the description model component library unusable.

[0033] To address the aforementioned issues, this application provides a method that replaces the unit representation model with a set of multiple 3D representation models in the 3D representation layer. When the representation form of a component changes, the variability of the representation itself and the stability of the description model are addressed by directly modifying the set of 3D representation models and their relationships within the set in the 3D representation layer. The improved 3D binding design scheme can be found in [reference needed]. Figure 2 , Figure 2 This is a schematic diagram illustrating a novel 3D representation model structure as an exemplary embodiment of this application. Figure 2 As shown, in the new binding relationship, the description model (i.e., the component description model) remains stable, and a component (vehicle component) is simultaneously associated with both the representation 3D model queue (component representation association list) and the component attribute list (component attribute association list); the representation 3D model queue ( Figure 2 The list of models and the list of associated component representations) simultaneously associate a variable number of 3D representation models. Figure 2 The model components (part representation models) are decoupled from the component attribute list and the representation 3D model list, and there is no association between them; for the spatial constraints of the representation 3D model, a new full-vehicle representation 3D model constraint relationship table is added (i.e., Figure 2 The model component relationship list (representing the spatial constraints of the model structure) is used for representation. This structure ensures that changes in the 3D representation structure will not be reflected back to the definition of the describing model; the spatial constraint relationships of the 3D representation model nodes do not affect the structure of the describing model itself.

[0034] It should be noted that the method of this embodiment can also be implemented by other devices known to those skilled in the art. The specific implementation method is not limited here. The above is only an example. The specific implementation method can be selected by those skilled in the art as needed.

[0035] Please see Figure 3 , Figure 3 This is a flowchart illustrating a vehicle terminal model digital binding method as shown in an exemplary embodiment of this application. Figure 3 As shown, in an exemplary embodiment, the vehicle terminal model digital binding method includes at least steps S301 to S304, which are described in detail below:

[0036] Step S301: Obtain the component description model of the vehicle component.

[0037] The component description model can be generated based on the component representation model requirement list, and there can be one or more component description models. For example, a component description model can be generated for a specific vehicle component, such as a door, seat, or windshield wiper. The component representation model requirement list can be generated in a manner known to those skilled in the art, and includes requirements such as the connection method, rotation method, and color of the vehicle components. The component description model can also be generated using other methods known to those skilled in the art, and no limitation is made here.

[0038] The component description model can be set for each car series or for each model, depending on whether there are differences in the overall component between different car series or different models.

[0039] Step S302: Create a component representation model of the vehicle component based on the component description model, and obtain a list of component representation models of the component description model.

[0040] In one embodiment, creating a component representation model based on a component description model includes:

[0041] Obtain the model entity object design drawing of the vehicle and determine the spatial design of the entity object. The model entity object design drawing includes the design drawings of the aforementioned vehicle components. Based on the model entity object design drawing, information such as the spatial relationship between multiple vehicle components can be known.

[0042] Based on the component description model and the entity object space design, define the description model representation requirements of the component description model, and generate the representation model definition and description model representation design of the component representation model.

[0043] Integrate the description model component code, description model representation requirements, and representation model definition of the component representation model to generate a list of description definition associations between the representation component description model and the representation model definition;

[0044] Based on the description definition association list and description model representation design, the historical representation model is obtained from the preset art workflow and used as the component representation model.

[0045] Each vehicle component's component description model is pre-configured with a corresponding description model component code, and the component representation model generated based on this description model also possesses this description model component code. This description model component code can also represent all component representation models and preset attributes corresponding to a particular vehicle component.

[0046] For a component description model of a vehicle part, one or more component representation models can be created. For example, for a car door, two, four or more car door representation models can be created.

[0047] An example of creating a component representation model based on a component description model is as follows: Obtain the defined twin instance description model (component description model) D-Model from the twin system, and obtain the physical object space design (entity object space design) W-Design from the physical object design drawing (model entity object design drawing) corresponding to the twin instance. Combine the twin instance description model D-Model and the physical object space design W-Design to define the representation requirements of each description model component, generating the description model representation design DS-Design, thus obtaining the representation model definition of the component representation model. Define one or more required representation 3D models (component representation models) VD-3DModel according to the component's representation requirements. Integrate the description model component code, description model representation requirements, and representation 3D models VD-3DModel to generate a mapping list (description definition association list) DS-ModelList between the component description model and the 3D representation model. Output the part description model and 3D representation model mapping list DS-ModelList and the description model representation design DS-Design to the art workflow (preset art workflow). Obtain the original representation 3D model VD-3DModel resource set from the part description model and 3D representation model mapping list DS-ModelList, that is, obtain the historical representation model, and use these historical representation models as part representation models.

[0048] In one embodiment, the generation of the component representation model list includes: establishing a mapping relationship between the description model and the 3D representation model based on the component description model and 3D representation model mapping list DS-ModelList, thereby obtaining the component representation model list. Each description model is configured with a component representation model list, which includes one or more component representation model lists.

[0049] Step S303: Establish a list of structural space constraints for the representation model based on the entity space constraint relationships of the entity components corresponding to all component representation models.

[0050] In one embodiment, a list of structural space constraints for the representation model is established based on the entity space constraint relationships of the entity components corresponding to all component representation models, including:

[0051] Establish model space constraints between component representation models based on the entity space constraints of the entity components corresponding to all component representation models;

[0052] Model space constraints are applied to the representation models of each component based on all model space constraints.

[0053] A list of structural space constraints for the representation model is established based on the constraint results of the model space constraints of each component representation model.

[0054] In one embodiment, when multiple component representation models exist, model space constraint relationships between each component representation model can be established based on the entity space constraint relationships of the entity components corresponding to all component representation models. Model space constraints are applied to each component representation model based on all model space constraint relationships, including at least one of the following:

[0055] If the spatial constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a positional constraint, the spatial position of the first component representation model is superimposed with an offset to lock and cover the spatial position of the second component representation model.

[0056] If the spatial constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a rotation constraint, the spatial attitude of the first component representation model is superimposed with an offset to lock and cover the spatial attitude of the second component representation model.

[0057] If the entity space constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a scaling constraint, the space of the first component representation model is scaled and superimposed with an offset to lock and cover the scaling of the space of the second component representation model.

[0058] If the entity space constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a parent-child constraint, then set the first component representation model as the target model source.

[0059] If the spatial constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is the target constraint, the spatial position of the first component representation model is superimposed with an offset to lock the Z-axis of the second component representation model pointing to the target.

[0060] The first component representation model and the second component representation model mentioned above can be any two of multiple component representation models.

[0061] The offsets in the above embodiments can be the same, or different offsets can be set according to different entity space constraint relationships. The specific offsets can be set by those skilled in the art as needed, and are not limited here.

[0062] Entity space constraints and model space constraints include at least one of the following: position constraints, rotation constraints, scaling constraints, parent-child constraints, target constraints, etc.

[0063] By establishing a list of structural space constraints for the representation model, if the difference between the new list of component representation model requirements and the original list of component representation model requirements is only a change in the spatial relationship between a few components, such as changing the door from a folding type to a front-opening type, then it is only necessary to adjust the model space constraint relationship between the component representation models of the corresponding vehicle components in the list of structural space constraints for the representation model. This can complete the overall adjustment of the model, and it is no longer necessary to achieve the final model adjustment by modifying the component description models.

[0064] Step S304: Configure preset attributes for the component representation model. The preset attributes are determined based on the component representation model requirement list, thus obtaining the preset attribute list of the component description model.

[0065] Each component representation model, or all component representation models belonging to the same component description model, has its corresponding attribute configurations, such as color, size, and shape, based on the component representation model requirement list. If subsequent adjustments to the vehicle component are only required in terms of attributes, such as color, then the preset attribute list corresponding to that vehicle component can be adjusted directly without modifying the component description model.

[0066] Step S305: Establish a twin binding relationship configuration table, write the component representation model list, the representation model structural space constraint list, and the preset attribute list into the twin binding relationship configuration table, and bind the written twin binding relationship configuration table to the vehicle terminal to be bound, so as to perform model digital binding on the vehicle terminal to be bound.

[0067] The twin binding relationship configuration table can be filled in according to the rules set by those skilled in the art. This table includes at least a list of component representation models, a list of structural space constraints for each vehicle component, and a list of preset attributes, as specified by those skilled in the art. For each twin instance, there is a corresponding list of component representation model requirements. Based on this list, multiple component description models can be generated. Each component description model can also create one or more component representation models. For each twin instance, a unique twin instance code is pre-set. This code identifies the component representation models generated based on the component representation model requirements list of that twin instance, as well as the subsequently obtained twin binding relationship configuration table. This allows locating the corresponding data for a specific twin instance through the twin instance code. By setting the twin instance code, it is convenient to subsequently adjust the relevant preset attributes and component representation models for a particular vehicle component.

[0068] When writing the component representation model list, the representation model structural space constraint list, and the preset attribute list into the twin binding relationship configuration table, the component representation model list and the preset attribute list of a certain vehicle component can be stored together, which facilitates subsequent querying and modification.

[0069] In one embodiment, after establishing a twin binding relationship configuration table and writing the component representation model list, the representation model structural space constraint list, and the preset attribute list into the twin binding relationship configuration table, the method further includes:

[0070] The twin binding relationship configuration table is identified by the twin instance code corresponding to the component representation model requirement list. The written twin binding relationship configuration table is published to the preset server. The twin instance code of the twin binding relationship configuration table is used as the management primary key to manage the twin binding relationship configuration table.

[0071] In this embodiment, the twin instance code is used as the management primary key to manage the twin binding relationship configuration table, including: obtaining the twin instance code of the terminal model to be rebuilt and the reconstruction requirements; querying multiple twin binding relationship configuration tables stored in the preset server through the twin instance code of the terminal model to be rebuilt to obtain the target twin binding relationship configuration table; and reconstructing and adjusting the target twin binding relationship configuration table according to the reconstruction requirements.

[0072] In this embodiment, the target twin binding relationship configuration table is rebuilt and adjusted according to the reconstruction requirements, including at least one of the following:

[0073] Based on the target twin binding relationship configuration table, the model addresses of multiple component representation models are determined, the resources of the target component representation model are pulled from the model addresses and loaded into memory, so as to adjust the target component representation model according to the reconstruction requirements;

[0074] The list of constraints for the representation model structure space is determined based on the target twin binding relationship configuration table, and the list of constraints for the representation model structure space is adjusted according to the reconstruction requirements.

[0075] Based on the target twin binding relationship configuration table, the preset attributes of multiple component representation models are determined so that the preset attributes of at least one component representation model can be adjusted according to the reconstruction requirements.

[0076] It is evident that when the component representation model requirement list is adjusted due to any of the following: the entity space constraint relationship of the vehicle component is adjusted, the attribute of the vehicle component is adjusted, or the number of vehicle components is adjusted, it is only necessary to adjust the representation model structure space constraint list, the preset attribute list of the vehicle component, and the number and representation form of the component representation model in the twin binding relationship configuration table corresponding to the component representation model requirement list. No adjustment to the component description model is required.

[0077] In this embodiment, before reconstructing and adjusting the target twin binding relationship configuration table according to the reconstruction requirements, the method further includes:

[0078] If the reconstruction requirements include new component requirements, then a new component description model, a new component representation model, a new component representation model list, a new preset attribute list, and a new representation model structure space constraint list are generated based on the new component requirements. These are used by the twin binding relationship configuration table to adjust based on the new component representation model list, the new preset attribute list, and the new representation model structure space constraint list.

[0079] In other words, if the reconstruction requirements include the requirement for new components, it means that new components are needed. A description model for new components can be generated based on the requirements for new components. According to the method provided in the above implementation, a new representation model for new components, a list of new representation models for new components, a list of new preset attributes, and a list of new representation model structural space constraints can be generated. Then, the above information is updated to the twin binding relationship configuration table to realize the adjustment of the model.

[0080] However, if the reconstruction requirements do not include new component requirements, but only adjustments to the attributes, spatial relationships, or number of existing vehicle components, then it is not necessary to adjust the component description model. Only one of the following needs adjustment: the component representation model, the component representation model list, the preset attribute list, and the representation model structural space constraint list. Adjust the corresponding model or list based on which part of the information being adjusted is represented.

[0081] In one embodiment, there may be many vehicles that need to be digitally bound to a model. Therefore, it is necessary to select the vehicles to be bound first, and then bind them. One example of binding the written twin binding relationship configuration table to the terminal of the vehicle to be bound includes:

[0082] Obtain the terminal binding requirements for multiple selectable vehicle terminals;

[0083] If the terminal binding requirement matches the component representation model requirement list, the optional vehicle terminal will be identified as the vehicle terminal to be bound.

[0084] Bind the written twin binding relationship configuration table to the vehicle terminal to be bound.

[0085] The following is an exemplary embodiment illustrating a specific method for digitally binding a vehicle terminal model. This method mainly consists of the following six steps: defining the 3D representation model (component representation model) structure, acquiring 3D representation model resources, binding the description model to the 3D representation model (establishing a resource mapping relationship between the component description model and the representation 3D model VD-3DModel, i.e., the component representation model list of the component description model), defining the spatial constraint relationship of the 3D representation model (representation model structural spatial constraint list), associating description model attributes (preset attribute list of the component description model), and reconstructing and applying the 3D representation model relationship. Wherein:

[0086] The process of defining the 3D representation model structure and representation model follows the twin instance description model. Based on the component-level representation requirements, the component representation model is decomposed and defined, generating a mapping list between the component description model and the 3D representation model, a list of 3D representation model structural space constraints, and a list of component representation model requirements. For example, the defined twin instance description model (D-Model) can be obtained from the twin system. The physical object space design (W-Design) is obtained from the physical object design drawing corresponding to the twin instance. Combining the twin instance description model (D-Model) and the physical object space design (W-Design), the representation requirements for each description model component are defined, generating the description model representation design (DS-Design). One or more required representation 3D models (VD-3DModel) are defined according to the component's representation requirements. The description model component code, description model representation requirements, and representation 3D models (VD-3DModel) are integrated to generate the mapping list between the component description model and the 3D representation model (DS-ModelList).

[0087] 3D representation model resource acquisition can obtain a full set of 3D representation model resources from the resource input side based on the component representation model requirement list. For example, the output component description model and 3D representation model mapping list DS-ModelList, and the description model representation design DS-Design are given to the art workflow. From the art workflow results, the original representation 3D model VD-3DModel resource set that can be obtained from the component description model and 3D representation model mapping list DS-ModelList is obtained.

[0088] The binding of description models to 3D representation models can establish a mapping relationship between description models and 3D representation models based on the mapping list of component description models and 3D representation models. That is, for each component description model, a component representation model is created, generating a component representation model list. The component description models are then associated with the component representation model list to obtain the component description model to 3D representation model mapping list. For example, a twin binding configuration table DV-BindTable can be established. Based on the component description model to 3D representation model mapping list DS-ModelList, the mapping relationship between description models and 3D representation models is established and written to the twin binding configuration table DV-BindTable.

[0089] The spatial constraints of 3D representation models can be defined based on a list of structural spatial constraints for each 3D representation model, creating a table of structural spatial constraints. For example, based on the description model representation design (DS-Design) and the twin binding configuration table (DV-BindTable), the required constraints for all 3D representation models that make up the twin instance virtual body are determined. These constraints include: position constraints: locking the source model's spatial position to cover the target model's spatial position after adding an offset; transformation constraints: locking the source model's spatial pose to cover the target model's spatial pose after adding an offset; scaling constraints: locking the source model's spatial scaling to cover the target model's spatial scaling after adding an offset; parent-child constraints: setting the source model as the source of the target model; target constraints: locking the source model's spatial position to point to the target model's Z-axis after adding an offset. Then, the set of 3D representation model constraints (DV-ModelConstrain) is written into the twin binding configuration table (DV-BindTable).

[0090] The description model attribute association can define an attribute tree based on the twin object description model definition, associate the data layer and representation layer states, and generate a 3D representation model representation state mapping table and a 3D representation model representation state definition table for vehicle condition data. For example, the dynamic attribute code D-PropertyCode is obtained from the twin instance description model D-Model. Based on the twin binding relationship configuration table DV-BindTable, the specified description model component code representation design is extracted from the model twin representation design DS-Design, and the dynamic attribute code D-PropertyCode and dynamic attribute 3D representation model are configured to match. The performance of the matched model is designed. Component representation attribute settings DV-PropertySetting are generated. The component representation attribute settings DV-PropertySetting are written to the twin binding relationship configuration table DV-BindTable. The twin binding relationship configuration table DV-BindTable is published to the cloud server, managed using the twin instance code as the management primary key, and the specified twin binding relationship configuration table DV-BindTable is distributed to specific terminals according to terminal requirements.

[0091] The 3D representation model relationship reconstruction application can reconstruct digital twin 3D representation instances on the terminal by applying 3D representation model resources, mapping relationships between description models and 3D representation models, representation model structural space constraint relationship tables, vehicle condition data 3D representation model representation state mapping tables, and 3D representation model representation state definition tables. For example, using the twin instance code as the query input parameter, the twin binding relationship configuration table DV-BindTable is retrieved from the cloud server. A new instantiated object of the description model D-Model is reconstructed on the application side and applied to queries using description model relationships as paths. The twin binding relationship configuration table DV-BindTable is parsed to obtain the mapping list DS-ModelList between description models and 3D representation models, and the addresses of all 3D representation models are parsed. Resources are retrieved from the addresses and loaded into memory. DS-Models mapped in the mapping list DS-ModelList are instantiated to the 3D scene, generating all models DS-Model-3D in the scene. Based on the twin binding configuration table DV-BindTable and the mapping list of description models and 3D representation models DS-ModelList, the relationship between the description model and the 3D representation model is established, which is applied to the data transfer from the description model layer to the 3D representation layer. The twin binding configuration table DV-BindTable is parsed to obtain the constraint relationship set DV-ModelConstrain. Based on this, the parent-child relationship and spatial component constraint relationship between models DS-Model-3D scene in all scenes of the 3D scene are reconstructed, mainly applied to the logical expression of the 3D world based on spatial constraint relationships. The twin binding configuration table DV-BindTable is also parsed to obtain the component representation attribute settings DV-PropertySetting. Based on this, the relationship between the description model attributes and the representation state of the 3D representation model is established, which affects the feedback representation of the 3D representation model to the twin instance description model data layer.

[0092] The following is an illustrative example of the above-described vehicle terminal model digital binding method through another specific embodiment. In a vehicle digital twin system, for a stable component, only a unified component description model needs to be defined and managed. All changes in other 3D representation layers are bound to the 3D representation model set according to feature requirements during 3D representation binding. This achieves the stability and reuse of the component description model and the polymorphism of the representation layer. For example, for car taillights, there are through-type or non-through-type taillights. For these two types and structures of components, only the "taillight" component needs to be defined in the description model, and the attributes and behaviors of the "taillight" component need to be managed. During 3D representation model binding, for non-through-type taillights, two 3D representation model sets, "left taillight model" and "right taillight model," are configured to the "taillight" component. At the same time, the "left taillight model" and "right taillight model" are set with spatial constraints to form positional constraints with the "frame" component representation model. For the continuous taillight, three 3D representation models—"left taillight model," "continuous taillight model," and "right taillight model"—are configured into the "taillight" component. Simultaneously, the 3D representation models of the "left taillight model" and "right taillight model" are set to form positional constraints with the "frame" component representation model, while the 3D representation model of the "continuous taillight model" is set to form a parent-child constraint with the "rear trunk" component representation model. Therefore, using the method provided in this application embodiment, for both types of taillights, it is not necessary to change the component description model; only the component representation models need to be configured into the taillight component, and the model space constraint relationships of the corresponding representation model structural space constraint list need to be adjusted accordingly.

[0093] The following is an illustrative description of the above-mentioned vehicle terminal model digital binding method through another specific embodiment. In the vehicle wiper representation process, there is a multi-morphological representation structure similar to the through-type taillight in the above embodiment, including single-group and double-group wiper structures. A stable description model structure, "wiper," is maintained in the description model. The single-group wiper structure 3D representation model set includes "wiper drive" and "wiper blade," where the "wiper drive" representation model imposes parent-child constraints on the "wiper blade" representation model, and the "frame" component representation model imposes positional constraints on the "wiper drive" representation model. The double-group wiper structure 3D representation model set includes "left wiper drive," "left wiper blade," "right wiper drive," and "right wiper blade." The "left wiper drive" representation model imposes parent-child constraints on the "left wiper blade" representation model, and the "right wiper drive" representation model imposes parent-child constraints on the "right wiper blade" representation model. The "frame" component representation model imposes positional constraints on the "left wiper drive" and "right wiper drive" representation models. As can be seen, using the method provided in this application embodiment, adding a windshield wiper does not require changing the component description model; only a corresponding component representation model needs to be added, and the structural space constraint list of the representation model needs to be modified accordingly. Below, another specific embodiment will be used to exemplarily illustrate the above-mentioned vehicle terminal model digital binding method. When representing a vehicle seat, a description model "seat" is established. Corresponding to the description model, 3D representation models for "seat base," "seat back," and "seat leg rest" (optional) are established. Positional constraints are applied to the "seat back" 3D representation model using the "seat base" 3D representation model, and parent-child constraints are applied to the "seat back" 3D representation model using the "seat base" 3D representation model. It can be seen that for one component description model, multiple component representation models can be created. By applying spatial constraints to each component representation model in the structural space constraint list of the representation model, different forms of seat representation can be achieved.

[0094] The following is an exemplary description of the above-mentioned vehicle terminal model digital binding method through another specific embodiment. When representing the vehicle wheels, description models for "brake" and "wheel" are established. The "brake" component is represented by a 3D "brake pad" model, and the "wheel" component is represented by a 3D "rim" model and a 3D "tire" model. The 3D "rim" model is used to apply rotational constraints to the 3D "tire" model, and the 3D "rim" model is also used to apply rotational constraints to the 3D "brake pad" model.

[0095] The following is an illustrative description of the above-described vehicle terminal model digital binding method through another specific embodiment. When representing the vehicle ambient lighting, a description model called "ambient lighting" is established. The "ambient lighting" component is represented by a set of multiple "light beads" 3D representation models. Based on the physical attachment objects of the light beads, parent-child constraints are applied to the first light bead representation model using the 3D representation model of the attachment objects. Attribute control is performed on each light bead in the attribute list.

[0096] See Figure 4 , Figure 4 A schematic diagram illustrating the structure of a 3D representation model in another related art, as shown in an exemplary embodiment of this application, is as follows: Figure 4 As shown, in related technologies, the design spatial relationship description is simple and mixed with the description model structure. When the spatial structure and the description model structure are inconsistent, data chaos occurs. If the relationship is reconstructed based on the spatial relationship, the description model relationship will be affected, resulting in dirty data.

[0097] See Figure 5 , Figure 5 When the 3D model representing changes, Figure 2 and Figure 4 The diagrams shown illustrate the two methods for adjusting the structure of the 3D representation model. Figure 5 As shown, the structures in related technologies require backtracking to and modifying the description model, which violates the principle of system isolation and causes a surge in the description model library, making the description model component library unusable and unmanageable. In contrast, the structure provided in this application only requires adding a new representation model during the binding process, without generating dirty data.

[0098] See Figure 6 , Figure 6 This diagram illustrates, for an exemplary embodiment of this application, the configuration content and data association relationship of the 3D representation model structure generation provided in this application. For example... Figure 6 As shown, the twin binding relationship configuration table should at least include a list of mappings between component description models and 3D representation models. Figure 6 The mapping list between the description model and the 3D representation model (i.e., the component representation model list of each component description model) represents the mapping relationship between the description model components and the 3D representation model; the list of structural space constraints of the 3D representation model ( Figure 6 The set of constraints on the representation model (i.e., the list of constraints on the representation model's structural space) represents the mapping relationship between the model representation design and the spatial relationship of the 3D representation model; the list of requirements for the component representation model ( Figure 6 The component representation attribute settings (i.e., the list of preset attributes for each component description model) are used to set the representation state of the 3D representation model based on the description model attributes.

[0099] Figure 7 , Figure 7 A schematic diagram illustrating the cross-domain system design principles provided in an embodiment of this application, as shown in an exemplary embodiment of this application, is provided. Figure 7 As shown, the system maintains the variability of subsystem functions by combining subsystems in a combined manner, and the system information flow maintains a stable structure to keep the system clean.

[0100] As can be seen, the vehicle terminal model digital binding method provided in the above embodiments can be applied to more general system designs with greater stability and variability. For a complete system, each subsystem achieves functional diversity and system polymorphism through combination. At the same time, the system information flow remains relatively stable to maintain the stability and maintainability of the overall system structure and avoid pollution of related systems.

[0101] The method provided in the above embodiments is applied to the implementation process of digital twin 3D reconstruction. Specifically, it is reflected in a set of related data structures and specific usage methods to realize the reconstruction logic of the digital twin component-based representation model. In the process of implementation, it aims to protect the stability of the description model and adapt to the variability of the structure of the digital twin vehicle components.

[0102] By replacing the unit representation model with multiple sets of 3D representation models in the 3D representation layer, when the representation form of a component changes, the variability of the representation itself and the stability of the description model can be solved by directly modifying the 3D representation model set and its relationships in the 3D representation layer.

[0103] In the new binding relationship, the component description model remains stable, and a component is simultaneously associated with both the representation 3D model queue and the component attribute list; the representation 3D model queue is simultaneously associated with a variable number of representation 3D models; the component attribute list and the representation 3D model list are decoupled and do not have any association relationship; for the spatial constraints of the representation 3D models, a new full-vehicle representation 3D model constraint relationship table is added. This structure ensures that changes in the 3D representation structure will not be reflected back to the definition of the description model; the spatial constraint relationship settings of 3D representation model nodes do not affect the structure of the description model itself.

[0104] In summary, the vehicle terminal model digital binding method provided in the above embodiments creates a component representation model based on the component description model, obtains a component representation list for each component description model, and establishes a representation model structure space constraint list based on the entity space constraint relationship of the entity components corresponding to all component representation models to constrain the spatial relationship between each component representation model. It also configures preset attributes for the component representation model, obtaining a preset attribute list for each component description model. These three lists are written into a twin binding relationship configuration table and bound to the vehicle terminal to be bound. This allows for adjustments to existing vehicle components when the needs of the vehicle terminal change, directly by adjusting at least one of the component representation list, representation model structure space constraint list, and preset attribute list in the twin binding relationship configuration table. This eliminates the need to adjust the component description model, avoids cross-domain changes, does not affect the entire system, reduces the development time of new functions, improves the stability and reusability of the component description model, and avoids the potential risk of conflicts between old and new systems due to adjustments to the component description model.

[0105] Please see Figure 8 , Figure 8 This is a block diagram illustrating a vehicle terminal model digital binding device, as shown in an exemplary embodiment of this application. Figure 8 As shown, the exemplary vehicle terminal model digital binding device 800 includes: an acquisition module 801, used to acquire component description models of vehicle components, the component description models being generated based on a component representation model requirement list; a component representation model list generation module 802, used to create component representation models of vehicle components based on the component description models, obtaining a component representation model list of component description models; a representation model structure space constraint list generation module 803, used to establish a representation model structure space constraint list based on the entity space constraint relationships of the entity components corresponding to all component representation models; a preset attribute list generation module 804, used to configure preset attributes for the component representation models, the preset attributes being determined based on the component representation model requirement list, obtaining a preset attribute list of component description models; and a binding module 805, used to establish a twin binding relationship configuration table, write the component representation model list, the representation model structure space constraint list, and the preset attribute list into the twin binding relationship configuration table, and bind the written twin binding relationship configuration table to the vehicle terminal to be bound, so as to perform model digital binding on the vehicle terminal to be bound.

[0106] In one embodiment, the device further includes a reconstruction module for publishing the written twin binding relationship configuration table to a preset server, and managing the twin binding relationship configuration table using the twin instance code of the twin binding relationship configuration table as the management primary key.

[0107] It should be noted that the vehicle terminal model digital binding device provided in the above embodiments and the method provided in the above embodiments belong to the same concept. The specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here. In practical applications, the device provided in the above embodiments can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. This is not a limitation here.

[0108] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the methods provided in the above embodiments.

[0109] Figure 9 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 9 The computer system 1100 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0110] like Figure 9 As shown, the computer system 1100 includes a Central Processing Unit (CPU) 1101, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 1102 or programs loaded from storage portion 1108 into Random Access Memory (RAM) 1103. The RAM 1103 also stores various programs and data required for system operation. The CPU 1101, ROM 1102, and RAM 1103 are interconnected via a bus 1104. An Input / Output (I / O) interface 1105 is also connected to the bus 1104.

[0111] The following components are connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to I / O interface 1105 as needed. Removable media 1111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1110 as needed so that computer programs read from them can be installed into storage section 1108 as needed.

[0112] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1109, and / or installed from removable medium 1111. When the computer program is executed by central processing unit (CPU) 1101, it performs the various functions defined in the apparatus of this application.

[0113] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0114] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, apparatuses, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0115] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0116] Another aspect of this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer's processor, causes the computer to perform the methods provided in the above embodiments. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0117] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various embodiments described above.

[0118] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A method for digitally binding a vehicle terminal model, characterized in that, The method includes: Obtain component description models for vehicle components, which are generated based on a component representation model requirement list; Based on the component description model, a component representation model of the vehicle component is created, resulting in a component representation model list. This involves: acquiring the vehicle's model entity object design drawing and determining the entity object space design; defining the description model representation requirements of the component description model based on the component description model and the entity object space design, and generating the representation model definition and description model representation design of the component representation model; integrating the component code of the description model, the description model representation requirements, and the representation model definition to generate a description definition association list representing the relationship between the component description model and the representation model definition; and retrieving historical representation models from a preset art workflow based on the description definition association list and the description model representation design, and using these historical representation models as the component representation models. Establish a list of structural space constraints for the representation model based on the entity space constraints of the entity components corresponding to all component representation models; Configure preset attributes for the component representation model, the preset attributes being determined based on the component representation model requirement list, to obtain the preset attribute list of the component description model; A twin binding relationship configuration table is established, and the component representation model list, the representation model structure space constraint list, and the preset attribute list are written into the twin binding relationship configuration table. The written twin binding relationship configuration table is then bound to the vehicle terminal to be bound, so as to perform model digital binding on the vehicle terminal to be bound.

2. The vehicle terminal model digital binding method as described in claim 1, characterized in that, Based on the entity space constraint relationships of all component representation models, establish a list of structural space constraints for the representation models, including: Establish model space constraints between component representation models based on the entity space constraints of the entity components corresponding to all component representation models; Based on all the aforementioned model space constraint relationships, model space constraints are applied to the characterization models of each component; A list of structural space constraints for the representation model is established based on the constraint results of the model space constraints of each component representation model.

3. The vehicle terminal model digital binding method as described in claim 2, characterized in that, Based on the entity space constraint relationships of the corresponding entity components in all component representation models, establish model space constraint relationships between each component representation model, and apply model space constraints to each component representation model based on all the aforementioned model space constraint relationships, including at least one of the following: If the spatial constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a positional constraint, the spatial position of the first component representation model is superimposed with an offset to lock and cover the spatial position of the second component representation model. If the spatial constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a rotation constraint, the spatial attitude of the first component representation model is superimposed with an offset to lock and cover the spatial attitude of the second component representation model. If the entity space constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a scaling constraint, the space of the first component representation model is scaled and superimposed with an offset to lock and cover the scaling of the space of the second component representation model. If the entity space constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is a parent-child constraint, then set the first component representation model as the target model source. If the spatial constraint relationship between the first entity component corresponding to the first component representation model and the second entity component corresponding to the second component representation model is the target constraint, the spatial position of the first component representation model is superimposed with an offset to lock the Z-axis of the second component representation model pointing to the target.

4. The vehicle terminal model digital binding method as described in any one of claims 1-3, characterized in that, After establishing a twin binding relationship configuration table and writing the component representation model list, the representation model structural space constraint list, and the preset attribute list into the twin binding relationship configuration table, the method further includes: The written twin binding relationship configuration table is published to a preset server, and the twin instance code of the twin binding relationship configuration table is used as the management primary key to manage the twin binding relationship configuration table.

5. The vehicle terminal model digital binding method as described in claim 4, characterized in that, Managing the twin binding relationship configuration table includes: Obtain the twin instance code and reconstruction requirements of the terminal model to be reconstructed; The target twin binding relationship configuration table is obtained by querying multiple twin binding relationship configuration tables stored in the preset server using the twin instance code of the terminal model to be reconstructed. The target twin binding relationship configuration table is rebuilt and adjusted according to the reconstruction requirements.

6. The vehicle terminal model digital binding method as described in claim 5, characterized in that, The target twin binding relationship configuration table is rebuilt and adjusted according to the reconstruction requirements, including at least one of the following: Based on the target twin binding relationship configuration table, the model addresses of multiple component representation models are determined, the resources of the target component representation model are pulled from the model addresses and loaded into memory, so as to adjust the target component representation model according to the reconstruction requirements; Based on the target twin binding relationship configuration table, a list of representation model structure space constraints is determined, and the list of representation model structure space constraints is adjusted according to the reconstruction requirements. Based on the target twin binding relationship configuration table, preset attributes of multiple component representation models are determined, so that the preset attributes of at least one component representation model can be adjusted according to reconstruction requirements.

7. The vehicle terminal model digital binding method as described in claim 6, characterized in that, Before reconstructing and adjusting the target twin binding relationship configuration table according to the reconstruction requirements, the method further includes: If the reconstruction requirements include new component requirements, a new component description model is generated based on the new component requirements, along with a new component representation model, a list of new component representation models, a list of new preset attributes, and a list of new representation model structural space constraints. This allows the twin binding relationship configuration table to be adjusted based on the list of new component representation models, the list of new preset attributes, the list of new representation model structural space constraints, and the preset attributes of each new component representation model.

8. The vehicle terminal model digital binding method as described in any one of claims 1-3, characterized in that, Bind the written twin binding relationship configuration table to the vehicle terminal to be bound, including: Obtain the terminal binding requirements for multiple selectable vehicle terminals; If the terminal binding requirement matches the component representation model requirement list, the optional vehicle terminal will be identified as the vehicle terminal to be bound. The written twin binding relationship configuration table is then bound to the vehicle terminal to be bound.

9. A digital binding device for a vehicle terminal model, characterized in that, The device includes: The acquisition module is used to acquire the component description model of the vehicle component, which is generated based on the component representation model requirement list; The component representation model list generation module is used to create component representation models of the vehicle components based on the component description model, and obtain a component representation model list of the component description model; wherein, the module obtains the model entity object design drawing of the vehicle and determines the entity object space design; defines the description model representation requirements of the component description model according to the component description model and the entity object space design, and generates the representation model definition and description model representation design of the component representation model; integrates the description model component code, description model representation requirements and the representation model definition of the component representation model to generate a description definition association list representing the relationship between the component description model and the representation model definition; and retrieves historical representation models from a preset art workflow based on the description definition association list and the description model representation design, and uses the historical representation models as the component representation models; The representation model structure space constraint list generation module is used to generate a representation model structure space constraint list based on the entity space constraint relationships of the entity components corresponding to all component representation models. A preset attribute list generation module is used to configure preset attributes for the component representation model. The preset attributes are determined based on the component representation model requirement list to obtain the preset attribute list of the component description model. The binding module is used to establish a twin binding relationship configuration table, write the component representation model list, the representation model structure space constraint list, and the preset attribute list into the twin binding relationship configuration table, and bind the written twin binding relationship configuration table to the vehicle terminal to be bound, so as to perform model digital binding on the vehicle terminal to be bound.

10. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to perform the method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by the computer's processor, causes the computer to perform the method according to any one of claims 1 to 8.

Images