Model data processing method, device, equipment and storage medium

Abstract

The present application discloses a model data processing method, device, equipment and storage medium. The method comprises: in response to a click query request after a model name is input in a browser, searching for a model file corresponding to the model name in a PB format file library; pushing the model to a front-end display interface for display; the multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options. The present application adopts Protocol Buffers technology, and the use of PB format files can improve access efficiency. Customers can use a browser to search for models based on the model name, which improves the customer experience.

Description

Technical Field

[0001] The present application relates to the field of software engineering technology, and in particular to a model data processing method, device, equipment and storage medium. Background Art

[0002] Although industrial design software in the form of a stand-alone client is widely used, it also has obvious disadvantages. It can only be used for design and development within the enterprise, and it is not convenient for customers to browse the company's product models. Summary of the invention

[0003] The main purpose of this application is to provide a model data processing method, device, equipment and storage medium to solve the above problems.

[0004] In order to achieve the above object, according to one aspect of the present application, a model data processing method is provided, the method comprising:

[0005] In response to a click query request after a model name is input in a browser, a model file corresponding to the model name is searched in a PB format file library;

[0006] Pushing the model to a front-end display interface for display;

[0007] The multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options;

[0008] In response to a click operation on a component option on a front-end display interface in a browser, searching a component model corresponding to the model name from a file library, and pushing the component model to the front-end display interface for display;

[0009] In response to a click operation on a description option on a front-end display interface in a browser, searching for description data corresponding to the model name from a file library; pushing the description data to the front-end display interface for display;

[0010] In response to a click operation on an icon option on a front-end display interface in a browser, searching for an icon corresponding to the name from a file library; pushing the icon to the front-end display interface for display;

[0011] In response to a click operation on a text option on a front-end display interface in a browser, searching for text corresponding to the name from a file library; pushing the text to the front-end display interface for display;

[0012] In response to a click operation on a variable option on a front-end display interface in a browser, a variable corresponding to the name is searched from a file library; and the variable is pushed to the front-end display interface for display.

[0013] In one implementation, after the variable is pushed to a front-end display page for display, the data types displayed on the front-end display page include: variable name, variable unit, and variable description.

[0014] In one embodiment, in response to a click query request after a model name is input in a browser, the method further includes:

[0015] Performing cross-domain access configuration in the server so that the browser can perform cross-domain access;

[0016] If the multiple data of the model are distributed and stored in different servers respectively, then the browser configured for cross-domain access is used to access each different server respectively to obtain all the data of the model.

[0017] In one embodiment, the model is a three-dimensional model established using modelica software.

[0018] In one implementation, the preparation of the PB format file includes:

[0019] The server cluster uses the open source Protocol Buffers compression technology to perform structured compression on each 3D model and related description parameters in the 3D model library to obtain a PB format file of each 3D model.

[0020] In one embodiment, for any one component, the component includes a plurality of three-dimensional solid models;

[0021] Each three-dimensional model is numbered and identified in advance;

[0022] The open source Protocol Buffers compression technology is used to perform structured compression on each three-dimensional model and related description parameters in the order of the number identification to obtain the PB file of the component.

[0023] In one embodiment, if the assembly includes a first subassembly and a second subassembly;

[0024] The first subcomponent is not processed by the Protocol Buffers compression technology;

[0025] The second subcomponent is processed by Protocol Buffers compression technology;

[0026] Establish a model library of the components, including:

[0027] For each three-dimensional model in the first sub-component, the open source Protocol Buffers compression technology is used in advance to perform structured compression on each three-dimensional model and related description parameters to obtain a PB file of the first sub-component;

[0028] Obtain the data storage location and model name of each three-dimensional model in the second subcomponent;

[0029] The data storage location and the model name are saved in the model library of the component.

[0030] In order to achieve the above object, according to another aspect of the present application, a model data processing device is provided; the device comprises:

[0031] A search module, for responding to a click query request after a model name is input in a browser, to search for a model file corresponding to the model name in a PB format file library;

[0032] A push module, used to push the model to the front-end display interface for display;

[0033] The multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options;

[0034] In response to a click operation on a component option on a front-end display interface in a browser, searching a component model corresponding to the model name from a file library, and pushing the component model to the front-end display interface for display;

[0035] In response to a click operation on a description option on a front-end display interface in a browser, searching for description data corresponding to the model name from a file library; pushing the description data to the front-end display interface for display;

[0036] In response to a click operation on an icon option on a front-end display interface in a browser, searching for an icon corresponding to the name from a file library; pushing the icon to the front-end display interface for display;

[0037] In response to a click operation on a text option on a front-end display interface in a browser, searching for text corresponding to the name from a file library; pushing the text to the front-end display interface for display;

[0038] In response to a click operation on a variable option on a front-end display interface in a browser, a variable corresponding to the name is searched from a file library; and the variable is pushed to the front-end display interface for display.

[0039] In one embodiment, it also includes a configuration module for performing cross-domain access configuration in the server in response to a click query request after the model name is entered in the browser, so that the browser performs cross-domain access; if multiple data of the model are distributed and stored in different servers, the browser configured for cross-domain access is used to access each different server separately to obtain all the data of the model.

[0040] In one embodiment, it also includes a PB file production module, which is used in the server cluster to use the open source Protocol Buffers compression technology to perform structured compression on each 3D model and related description parameters in the 3D model library to obtain a PB format file of each 3D model.

[0041] In one embodiment, the PB file making module is further used to number and identify each three-dimensional model in advance;

[0042] The open source Protocol Buffers compression technology is used to perform structured compression on each three-dimensional model and related description parameters in the order of the number identification to obtain the PB file of the component.

[0043] In one embodiment, the PB file production module is further used for, if the component includes a first subcomponent and a second subcomponent;

[0044] The first subcomponent is not processed by the Protocol Buffers compression technology;

[0045] The second subcomponent is processed by Protocol Buffers compression technology;

[0046] For each three-dimensional model in the first sub-component, the open source Protocol Buffers compression technology is used in advance to perform structured compression on each three-dimensional model and related description parameters to obtain a PB file of the first sub-component;

[0047] Obtain the data storage location and model name of each three-dimensional model in the second subcomponent;

[0048] The data storage location and the model name are saved in the model library of the component.

[0049] In order to achieve the above-mentioned purpose, according to the third aspect of the present application, an electronic device is provided; comprising at least one processor and at least one memory; the memory is used to store one or more program instructions; the processor is used to run one or more program instructions to execute any of the steps described above.

[0050] According to a fourth aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium contains one or more program instructions, and the one or more program instructions are used to execute any one of the steps described above.

[0051] The technical solution in this application, in response to a click query request after a model name is entered in a browser, searches for a model file corresponding to the model name in a PB format file library; pushes the model to a front-end display interface for display; the multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options. Users can search for models in a browser based on the model name. This application uses Protocol Buffers technology, and the use of PB format files can improve access efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The drawings constituting a part of this application are used to provide a further understanding of this application, so that other features, purposes and advantages of this application become more obvious. The schematic embodiment drawings and their descriptions of this application are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

[0053] Figure 1 is a flow chart of a model data processing method according to an embodiment of the present application;

[0054] Figure 2 is a schematic diagram of a component page according to an embodiment of the present application;

[0055] Figure 3 is a schematic diagram of an explanation page according to an embodiment of the present application;

[0056] Figure 4 is a schematic diagram of an icon page according to an embodiment of the present application;

[0057] Figure 5 is a schematic diagram of a text page according to an embodiment of the present application;

[0058] Figure 6 is a schematic diagram of a variable page according to an embodiment of the present application;

[0059] Figure 7 is a schematic diagram of a model data processing device according to an embodiment of the present application;

[0060] Figure 8 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0062] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0063] In addition, some of the above terms may be used to express other meanings in addition to indicating a direction or position relationship. For example, the term "on" may also be used to express a certain dependency or connection relationship in some cases. For those of ordinary skill in the art, the specific meanings of these terms in the present invention can be understood according to specific circumstances.

[0064] In addition, the terms "installed", "set", "provided with", "connected", "connected", and "socketed" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral structure; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or it can be an internal connection between two devices, elements, or components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0065] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0066] See attached Figure 1 The flowchart of a model data processing method shown in FIG. 1 includes the following steps S101 to S107:

[0067] Step S101, in response to a click query request after a model name is input in a browser, searching a model file corresponding to the model name in a PB format file library;

[0068] Preferably, the model is a three-dimensional model established using modelica software.

[0069] Step S102, pushing the model to a front-end display interface for display;

[0070] The multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options;

[0071] Step S103, in response to a click operation on a component option on the front-end display interface in the browser, searching a component model corresponding to the model name from a file library, and pushing the component model to the front-end display interface for display;

[0072] See attached Figure 2 A schematic diagram of a component page is shown; in the page, a component model is displayed, and the component model includes multiple parts.

[0073] Step S104, in response to a click operation on a description option on the front-end display interface in the browser, searching for description data corresponding to the model name from a file library; and pushing the description data to the front-end display interface for display;

[0074] See attached Figure 3 A schematic diagram of an instruction page is shown; in this page, the parameter content includes: type, name, default value, unit, and description.

[0075] Step S105, in response to a click operation on an icon option on the front-end display interface in the browser, searching for an icon corresponding to the name from a file library; and pushing the icon to the front-end display interface for display;

[0076] See attached Figure 4 A schematic diagram of an icon page is shown. The icon is a two-dimensional picture of a mechanical model.

[0077] Step S106, in response to a click operation on a text option on the front-end display interface in the browser, searching for text corresponding to the name from a file library; and pushing the text to the front-end display interface for display;

[0078] See attached Figure 5 A schematic diagram of a text page is shown.

[0079] Step S107, in response to a click operation on a variable option on the front-end display interface in the browser, searching for a variable corresponding to the name from a file library; and pushing the variable to the front-end display interface for display.

[0080] It is worth emphasizing that the above steps S102 to S107 are not executed in a strict order, and the order of execution can be flexibly adjusted according to actual conditions.

[0081] From the above description, it can be seen that the present invention achieves the following technical effects: after the user logs in to the website through the browser, when querying the model, after entering the name of the model and clicking the query button, the three-dimensional model is displayed on the browser web page.

[0082] After the variable is pushed to the front-end display page for display, the data types displayed on the front-end display page include: variable name, variable unit, and variable description.

[0083] See attached Figure 6 A schematic diagram of a variable page is shown.

[0084] The name is mload, the default value is 15, the unit is kg, and the description is Mass of load.

[0085] In one embodiment, in response to a click query request after a model name is input in a browser, a cross-domain access configuration is performed in a server so that the browser performs cross-domain access;

[0086] If the multiple data of the model are distributed and stored in different servers respectively, then the browser configured for cross-domain access is used to access each different server respectively to obtain all the data of the model.

[0087] Specifically, the generated model metadata are stored on different servers. There are cross-domain problems when the browser accesses these model metadata. The Springboot Cors method is used to solve the cross-domain problem.

[0088] Specifically, one method is to use the @CrossOrigin annotation

[0089] Use the @CrossOrigin annotation on the Controller, and all interfaces under this class can be accessed across domains

[0090] @RequestMapping(" / demo2")

[0091] 2@RestController

[0092] 3 / / @CrossOrigin / / All domain names can access all interfaces under this class

[0093] Preferably, another method is to create a new cross-domain configuration class: CorsConfig.java; this application preferably adopts this method.

[0094] For example, some codes are as follows:

[0095]

[0096]

[0097] twenty one}

[0098] twenty two}

[0099] After configuration in the server and passing the test, the browser can access different servers across domains.

[0100] In one embodiment, when making a PB format file, the server cluster uses the open source Protocol Buffers compression technology to perform structured compression on each 3D model and related description parameters in the 3D model library to obtain a PB format file of each 3D model.

[0101] Among them, Protocol Buffers (PB) is a commonly used data storage and communication protocol technology. Compared with traditional XML, PB is simpler; the data description file only needs 1 / 10 to 1 / 3 of the original, and the parsing speed is 20 to 100 times the original; it reduces ambiguity; and generates data access classes that are easier to use in programming and support multiple programming languages.

[0102] Based on the efficiency and cross-platform nature of PB, Modelica models and component information are stored in PB files. The MWorks.Syslink server parses the PB files and returns the data to the browser for rendering. Model data is saved in pb files instead of databases. Compared with database storage, it ensures query efficiency, simplifies system complexity, and increases software stability.

[0103] In one embodiment, for any one component, the component includes a plurality of three-dimensional solid models;

[0104] Each three-dimensional model is numbered and identified in advance;

[0105] The open source Protocol Buffers compression technology is used to perform structured compression on each three-dimensional model and related description parameters in the order of the number identification to obtain the PB file of the component.

[0106] When a model library references another model library, it does not directly generate the metadata of the referenced model library. By recording the storage location and model name of the referenced model, the metadata information of the model can be uniquely obtained. This perfectly improves the efficiency of generating metadata and enhances user experience. If the model metadata of all model libraries is generated, the generation time is the sum of the generation time of multiple models. The more model libraries are referenced, the longer it takes. This will seriously increase the user's waiting time and affect the user experience.

[0107] So in one embodiment, if the assembly includes a first subassembly and a second subassembly;

[0108] The first subcomponent is not processed by the Protocol Buffers compression technology;

[0109] The second subcomponent is processed by Protocol Buffers compression technology;

[0110] When establishing the model library of the component, for each three-dimensional model in the first sub-component, the open source Protocol Buffers compression technology is used in advance to perform structured compression on each three-dimensional model and related description parameters to obtain a PB file of the first sub-component;

[0111] Obtain the data storage location and model name of each three-dimensional model in the second subcomponent;

[0112] The data storage location and the model name are saved in the model library of the component.

[0113] When searching, you only need to search according to the data storage location and model name. The data file itself does not need to be saved in the model library. This will shorten the generation and establishment time of the model library and improve the construction efficiency of the model library.

[0114] Exemplarily, based on model entities and component entity classes, Mworks.Sysplorer is used to parse the Modelica model library to obtain the syntax tree of the Modelica model library and each model instance tree, and the parsed syntax tree and instance tree are written to the instantiated objects of each entity class respectively. The model instantiation objects and component instantiation objects are respectively stored in independent linear lists, and the linear lists are stored in the ModelicaModelInfo.pb file on disk with the help of writeTo(outputpath) provided by PB; model icons, views, texts and descriptions are directly stored on disk.

[0115] The Mworks.Syslink server reads the ModelicaModelInfo.pb file, converts the linear table into a tree structure and returns it to the Syslink front end. After a series of processing and rendering, the Syslink front end realizes the demand for online browsing of the Modelica model.

[0116] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0117] According to an embodiment of the present invention, a model data processing device is also provided. Figure 7 As shown, the device comprises:

[0118] A search module 71 is used to search for a model file corresponding to the model name in a PB format file library in response to a click query request after a model name is input in a browser;

[0119] A push module 72 is used to push the model to a front-end display interface for display;

[0120] The multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options;

[0121] In response to a click operation on a component option on a front-end display interface in a browser, searching a component model corresponding to the model name from a file library, and pushing the component model to the front-end display interface for display;

[0122] In response to a click operation on a description option on a front-end display interface in a browser, searching for description data corresponding to the model name from a file library; pushing the description data to the front-end display interface for display;

[0123] In response to a click operation on an icon option on a front-end display interface in a browser, searching for an icon corresponding to the name from a file library; pushing the icon to the front-end display interface for display;

[0124] In response to a click operation on a text option on a front-end display interface in a browser, searching for text corresponding to the name from a file library; pushing the text to the front-end display interface for display;

[0125] In response to a click operation on a variable option on a front-end display interface in a browser, a variable corresponding to the name is searched from a file library; and the variable is pushed to the front-end display interface for display.

[0126] In one embodiment, it also includes a configuration module 73, which is used to perform cross-domain access configuration in the server in response to a click query request after the model name is input in the browser, so that the browser performs cross-domain access; if multiple data of the model are distributed and stored in different servers, then the browser configured for cross-domain access is used to access each different server respectively to obtain all the data of the model.

[0127] In one embodiment, it also includes a PB file production module 74, which is used in the server cluster to use the open source Protocol Buffers compression technology to perform structured compression on each 3D model and related description parameters in the 3D model library to obtain a PB format file of each 3D model.

[0128] In one embodiment, the PB file making module 74 is also used to number and identify each three-dimensional model in advance;

[0129] The open source Protocol Buffers compression technology is used to perform structured compression on each three-dimensional model and related description parameters in the order of the number identification to obtain the PB file of the component.

[0130] In one embodiment, the PB file making module 74 is further used for, if the component includes a first subcomponent and a second subcomponent;

[0131] The first subcomponent is not processed by the Protocol Buffers compression technology;

[0132] The second subcomponent is processed by Protocol Buffers compression technology;

[0133] For each three-dimensional model in the first sub-component, the open source Protocol Buffers compression technology is used in advance to perform structured compression on each three-dimensional model and related description parameters to obtain a PB file of the first sub-component;

[0134] Obtain the data storage location and model name of each three-dimensional model in the second subcomponent;

[0135] The data storage location and the model name are saved in the model library of the component.

[0136] According to a third aspect of the present application, an electronic device is provided. Figure 8The structural diagram of the electronic device shown in the figure comprises at least one processor 81 and at least one memory 82; the memory 82 is used to store one or more program instructions; the processor 81 is used to run one or more program instructions to execute any one of the above methods.

[0137] In a fourth aspect, the present application further proposes a computer-readable storage medium, which contains one or more program instructions, and the one or more program instructions are used to execute any of the methods described above.

[0138] The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present invention can be directly embodied as a hardware decoding processor for execution, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The processor reads the information in the storage medium and completes the steps of the above method in combination with its hardware.

[0139] The storage medium may be a memory, which may be, for example, a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memory.

[0140] Among them, the non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.

[0141] The volatile memory may be a random access memory (RAM) which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDRSDRAM), enhanced synchronous DRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus DRAM (DRRAM).

[0142] The storage media described in the embodiments of the present invention are intended to include, but are not limited to, these and any other suitable types of memory.

[0143] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the present invention can be implemented using a combination of hardware and software. When software is used, the corresponding functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media can be any available media that can be accessed by general or special-purpose computers.

[0144] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A model data processing method, characterized in that: The method comprises: In response to a click query request after a model name is input in a browser, a model file corresponding to the model name is searched in a PB format file library; Pushing the model to a front-end display interface for display; The multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options; In response to a click operation on a component option on a front-end display interface in a browser, searching a component model corresponding to the model name from a file library, and pushing the component model to the front-end display interface for display; In response to a click operation on a description option on a front-end display interface in a browser, searching for description data corresponding to the model name from a file library; pushing the description data to the front-end display interface for display; In response to a click operation on an icon option on a front-end display interface in a browser, searching for an icon corresponding to the name from a file library; pushing the icon to the front-end display interface for display; In response to a click operation on a text option on a front-end display interface in a browser, searching for text corresponding to the name from a file library; pushing the text to the front-end display interface for display; In response to a click operation on a variable option on a front-end display interface in a browser, searching a variable corresponding to the name from a file library; pushing the variable to the front-end display interface for display; In response to a click query request after the model name is input in the browser, the method further includes: Performing cross-domain access configuration in the server so that the browser can perform cross-domain access; If the multiple data of the model are distributed and stored in different servers respectively, then use the browser configured for cross-domain access to access each different server respectively to obtain all the data of the model; For any component, the component includes a plurality of three-dimensional solid models; Each three-dimensional model is numbered and identified in advance; Using open source Protocol Buffers compression technology to perform structured compression on each three-dimensional model and related description parameters in the order of the number identification, to obtain a PB file of the component; If the assembly includes a first subassembly and a second subassembly; The first subcomponent is not processed by the Protocol Buffers compression technology; The second subcomponent is processed by Protocol Buffers compression technology; Establish a model library of the components, including: For each three-dimensional model in the first sub-component, the open source Protocol Buffers compression technology is used in advance to perform structured compression on each three-dimensional model and related description parameters to obtain a PB file of the first sub-component; Obtain the data storage location and model name of each three-dimensional model in the second subcomponent; The data storage location and the model name are saved in the model library of the component.

2. The model data processing method according to claim 1, characterized in that: After the variable is pushed to the front-end display page for display, the data types displayed on the front-end display page include: variable name, variable unit, and variable description.

3. The model data processing method according to claim 1, characterized in that: The model is a three-dimensional model established using modelica software.

4. The model data processing method according to claim 3, characterized in that: The preparation of the PB format file includes: The server cluster uses the open source Protocol Buffers compression technology to perform structured compression on each 3D model and related description parameters in the 3D model library to obtain a PB format file of each 3D model.

5. A model data processing device, characterized in that: include: A search module, for responding to a click query request after a model name is input in a browser, to search for a model file corresponding to the model name in a PB format file library; A push module, used to push the model to the front-end display interface for display; The multiple options on the front-end display interface include: text options, component options, description options, icon options, and variable options; In response to a click operation on a component option on a front-end display interface in a browser, searching a component model corresponding to the model name from a file library, and pushing the component model to the front-end display interface for display; In response to a click operation on a description option on a front-end display interface in a browser, searching for description data corresponding to the model name from a file library; pushing the description data to the front-end display interface for display; In response to a click operation on an icon option on a front-end display interface in a browser, searching for an icon corresponding to the name from a file library; pushing the icon to the front-end display interface for display; In response to a click operation on a text option on a front-end display interface in a browser, searching for text corresponding to the name from a file library; pushing the text to the front-end display interface for display; In response to a click operation on a variable option on a front-end display interface in a browser, searching a variable corresponding to the name from a file library; pushing the variable to the front-end display interface for display; In response to a click query request after a model name is input in a browser, the method further includes: Performing cross-domain access configuration in the server so that the browser can perform cross-domain access; If the multiple data of the model are distributed and stored in different servers respectively, then use the browser configured for cross-domain access to access each different server respectively to obtain all the data of the model; For any component, the component includes a plurality of three-dimensional solid models; Each three-dimensional model is numbered and identified in advance; Using open source Protocol Buffers compression technology to perform structured compression on each three-dimensional model and related description parameters in the order of the number identification, to obtain a PB file of the component; If the assembly includes a first subassembly and a second subassembly; The first subcomponent is not processed by the Protocol Buffers compression technology; The second subcomponent is processed by Protocol Buffers compression technology; Establish a model library of the components, including: For each three-dimensional model in the first sub-component, the open source Protocol Buffers compression technology is used in advance to perform structured compression on each three-dimensional model and related description parameters to obtain a PB file of the first sub-component; Obtain the data storage location and model name of each three-dimensional model in the second subcomponent; The data storage location and the model name are saved in the model library of the component.

6. An electronic device, characterized in that: include: at least one processor and at least one memory; The memory is used to store one or more program instructions; The processor is used to run one or more program instructions to execute the method according to any one of claims 1-4.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes one or more program instructions, and the one or more program instructions are used to execute the method according to any one of claims 1 to 4.

Images