Model data synchronization method and device and storage medium

Abstract

The embodiment of the invention provides a model data synchronization method and device and a storage medium. In the model data synchronization method, a to-be-associated model and a target synchronization mode can be determined based on a model synchronization interface, and a synchronization trigger event for a target model in at least one model can be acquired by adopting an event acquisition mode corresponding to the target synchronization mode. And in response to the synchronization trigger event, synchronizing to-be-associated model data of the target model to the target engine, and sending a synchronization notification message corresponding to the target model to the target engine. Based on the implementation mode, a visual operation entry can be provided for the user by utilizing the model synchronization interface, and based on the operation entry, the user can realize automatic synchronization of the model data for the target model through simple synchronous configuration operation without manually executing the import and export operations of the model, so that the user experience is improved. And the model data synchronization efficiency is further improved on the basis of reducing the dependence of the model data synchronization operation on manpower.

Description

Technical Field

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

[0002] In the game development scenario, developers can use independent production software to create 3D models and provide the 3D models to the game engine for use. In some existing solutions, developers need to manually export model data files from the production software and manually import the model data files into the game engine. When the model faces multiple adjustments, it is necessary to repeat the operation of exporting from the production software and importing into the game engine multiple times. This method relies on manual operation and has high labor and time costs. Therefore, a new solution needs to be proposed. Summary of the invention

[0003] Multiple aspects of the present application provide a model data synchronization method, device and storage medium to achieve automatic synchronization of model data, thereby further improving synchronization efficiency while reducing reliance on manual operations.

[0004] An embodiment of the present application provides a model data synchronization method, including: displaying a model synchronization interface; displaying a model identifier of at least one model to be synchronized on the model synchronization interface; the at least one model is produced by model production software; according to the model synchronization configuration operation on the model synchronization interface, obtaining a synchronization trigger event for a target model in the at least one model; in response to the synchronization trigger event, synchronizing the model data to be synchronized of the target model to a target engine, and sending a synchronization notification message corresponding to the target model to the target engine.

[0005] Optionally, according to the model synchronization configuration operation on the model synchronization interface, a synchronization trigger event for a target model in the at least one model is obtained, including: responding to the configuration operation of the synchronization mode configuration control on the model synchronization interface to determine the target synchronization mode; the target synchronization mode includes: a delayed synchronization mode or a real-time synchronization mode; and using an event acquisition method corresponding to the target synchronization mode to obtain a synchronization trigger event for a target model in the at least one model.

[0006] Optionally, an event acquisition method corresponding to the target synchronization mode is adopted to acquire the synchronization trigger event of the target model, including: in the delayed synchronization mode, if a synchronization instruction issued by the user to the target model is monitored, it is determined that the synchronization trigger event of the target model is acquired; wherein the synchronization instruction is issued through a model synchronization control displayed on the model synchronization interface, or the synchronization instruction is issued through a voice instruction; in the real-time synchronization mode, an update operation of at least one model is detected, and when an update operation of the model making software on the target model in the at least one model is detected, it is determined that the synchronization trigger event corresponding to the target model is acquired.

[0007] Optionally, in the real-time synchronization mode, the update operation of the at least one model is detected, including: in the real-time synchronization mode, according to a set period, respectively obtaining the real-time model data of the at least one model and the historical model data at the time of the last synchronization; for any model of the at least one model, if the real-time model data of the model is inconsistent with the historical model data, determining that the model is a target model with an update operation.

[0008] Optionally, the model data to be synchronized of the target model is synchronized to the target engine, and a synchronization notification message corresponding to the target model is sent to the target engine, including: determining a data cache directory of the target engine; storing the model data to be synchronized of the target model in the data cache directory; and sending a synchronization notification message to the target engine indicating that the target model is updated.

[0009] Optionally, the model data to be synchronized of the target model is stored in the data cache directory, including: comparing the real-time model data of the target model with the historical model data at the time of the last synchronization; determining the updated data of the target model based on the comparison result; and storing the updated data of the target model in the data cache directory.

[0010] Optionally, the model synchronization interface also includes: a model adding control; displaying the model identification of at least one model to be synchronized on the model synchronization interface, including: responding to a triggering operation on the model adding control, determining at least one selected model; and displaying the model identification of the at least one model on the model synchronization interface.

[0011] An embodiment of the present application also provides a model synchronization method, including: displaying a model synchronization interface; according to a monitoring start operation initiated on the model synchronization interface for at least one model, monitoring synchronization notification messages sent by model production software corresponding to each of the at least one model; when monitoring a synchronization notification message of a target model in the at least one model, obtaining model data synchronized by the model production software corresponding to the target model, so as to update the target model according to the model data.

[0012] Optionally, according to a listening start operation initiated on the model synchronization interface for at least one model, the synchronization notification message sent by the model production software corresponding to the at least one model is listened to, including: responding to a triggering operation of adding a control to the model on the model synchronization interface, and displaying the model identifier of the at least one model on the model synchronization interface; responding to the listening start operation on the model synchronization interface, and listening to the synchronization notification message sent by the model production software corresponding to the at least one model.

[0013] Optionally, obtaining model data synchronized by a model making software corresponding to the target model includes: parsing a synchronization notification message of the target model to obtain a data cache directory carried by the synchronization notification message; and reading data according to the data cache directory to obtain the model data to be synchronized of the target model.

[0014] An embodiment of the present application also provides an electronic device, comprising: a memory and a processor; the memory is used to store one or more computer instructions; the processor is used to execute the one or more computer instructions to: execute the steps in the model data synchronization method provided in the embodiment of the present application.

[0015] The embodiment of the present application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the model data synchronization method provided in the embodiment of the present application.

[0016] In the model data synchronization method provided in the embodiment of the present application, based on the model synchronization interface, the model identifier of the model to be synchronized can be displayed, and according to the model synchronization configuration operation on the model synchronization interface, the synchronization trigger event for the target model in the at least one model is obtained. In response to the synchronization trigger event, a synchronization notification message corresponding to the target model is sent to the target engine, and the model data to be synchronized of the target model is synchronized to the target engine. Based on this implementation, the model synchronization interface can be used to provide users with an intuitive operation entry. Based on the operation entry, the user can realize automatic synchronization of model data for the target model through simple synchronization configuration operations, without the need to manually perform model import and export operations, thereby further improving the model data synchronization efficiency on the basis of reducing the dependence of the model synchronization operation on manual work. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 A flowchart of a model data synchronization method on the model making software side provided by an exemplary embodiment of the present application;

[0019] Figure 2 A schematic diagram of a model data synchronization interface on a model making software side provided by an exemplary embodiment of the present application;

[0020] Figure 3 A flowchart of a model data synchronization method on a target engine side provided by another exemplary embodiment of the present application;

[0021] Figure 4 A schematic diagram of a model data synchronization interface on a target engine side provided for another exemplary embodiment of the present application;

[0022] Figure 5 A schematic diagram of the structure of an electronic device provided as an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. 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 making creative work are within the scope of protection of the present application.

[0024] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms "a", "said" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings, and "multiple" generally includes at least two, but does not exclude the inclusion of at least one.

[0025] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0026] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a product or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such a product or system. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the product or system including the elements.

[0027] In order to solve the technical problems of high labor cost and high time cost in the prior art, which relies on manual export of models from model making software and manual import of models into the target engine, a solution is provided in some embodiments of the present application. The technical solutions provided in each embodiment of the present application are described in detail below in conjunction with the accompanying drawings.

[0028] Figure 1 is a flow chart of a model data synchronization method provided by an exemplary embodiment of the present application. When the method is executed on the model making software side, it may include the following steps: Figure 1 Steps shown:

[0029] Step 101: Display the model synchronization interface.

[0030] Step 102: Displaying a model identifier of at least one model to be synchronized on the model synchronization interface; the at least one model is produced by model production software.

[0031] Step 103: According to the model synchronization configuration operation on the model synchronization interface, a synchronization trigger event for a target model in the at least one model is obtained.

[0032] Step 104: In response to the synchronization trigger event, synchronize the model data to be synchronized of the target model to the target engine, and send a synchronization notification message corresponding to the target model to the target engine.

[0033] The execution subject of this embodiment can be a model sending tool in the model making software, and the model sending tool can be implemented as an independent software form or a plug-in form. When implemented as a plug-in form, the plug-in can call the interface provided by the model making software, obtain the model data generated by the model making software, and automatically synchronize the model data to the target engine. Among them, the model making software can be a two-dimensional modeling software or a three-dimensional modeling software. Among them, the target engine can be a two-dimensional engine or a three-dimensional engine, which is not limited in this embodiment.

[0034] The model sending tool can detect the model synchronization operation, and respond to the model synchronization operation to display the model synchronization interface. The model synchronization operation can be triggered by the user. In some embodiments, the model sending tool and the model making software can be installed on the same device. After the model sending tool is installed, the model sending tool can display a quick start icon through the toolbar of the model making software. If the model sending tool detects a trigger operation for the quick start icon, it can be considered that the model synchronization operation is detected. The model sending tool can display a model synchronization interface. The model synchronization interface is used to configure the model to be synchronized and to perform the synchronization operation of the model.

[0035] The model synchronization interface may display the model identification of at least one model, where the at least one model is a model created by the model creation software and to be synchronized to the target engine. The model identification of any model may be the model number, file name, or thumbnail, etc., which is not limited in this embodiment.

[0036] In some exemplary embodiments, the model to be synchronized is selected by the user. That is, the model identifier of the at least one model displayed in the model synchronization interface can be added by the user. In this embodiment, the model synchronization interface can display a model adding control for the user to operate, such as Figure 2 The plus sign (+) button 201 is shown. The model sending tool can respond to the triggering operation of adding a control to the model, determine at least one selected model, and display the model identifier of the at least one model in the model synchronization interface.

[0037] In some exemplary embodiments, the model sending tool may respond to a trigger operation of adding a control to the model and display a model list of the model making software. Optionally, the model file storage address of the model making software may be pre-configured in the model sending tool. Furthermore, when the model synchronization control is triggered, the model sending tool may read the model list of the model making software based on the pre-configured model file storage address, and display the read model list for user selection. The model sending tool may determine at least one selected model based on the user's selection operation of the model in the model list, and display the model identifier of the at least one model in the model synchronization interface. Figure 2 Shown are the selected models a and b.

[0038] Optionally, in this implementation, the model sending tool may further obtain relevant information of the model to be synchronized from the target engine, such as the name of the model, a thumbnail of the model, etc. The model sending tool may provide the relevant information of the above model to the user, so that the user can add a model identifier in the model synchronization interface according to the above information. For example, in some optional embodiments, after the model sending tool obtains the relevant information of the model to be synchronized from the target engine, when displaying the read model list, a floating window may be used to display the relevant information of the model on the same screen, thereby guiding the user's model selection operation.

[0039] In other exemplary embodiments, at least one model identifier displayed in the model synchronization interface can be obtained from the target engine. Optionally, the model sending tool can respond to the trigger operation of adding a control to the model, import the model list sent by the target engine, and determine at least one selected model based on the models in the model list. In some optional implementations, after obtaining the model list sent by the target engine, the model sending tool can determine whether the model identifier in the model list is consistent with the model identifier in the model making software. If they are consistent, the model list sent by the target engine can be imported in response to the trigger operation of adding a control to the model.

[0040] Optionally, at least one model identifier displayed on the model synchronization interface can be deleted according to user operations. The model synchronization interface can display a remove button, such as Figure 2 The minus (-) button 202 is shown. After the user selects one or more model identifiers displayed on the model synchronization interface, if the user triggers the remove button, the one or more model identifiers selected by the user can be deleted. Furthermore, based on the model synchronization interface, flexible and dynamic adjustment of the models to be synchronized is achieved.

[0041] After displaying the model identification of the at least one model, the model sending tool can obtain a synchronization trigger event for a target model in the at least one model according to the model synchronization configuration operation on the model synchronization interface, wherein the synchronization trigger event is used to trigger the synchronization operation of the model data.

[0042] Optionally, the model sending tool can provide multiple synchronization modes, and different synchronization modes have different ways of obtaining synchronization trigger events. Among them, the multiple synchronization modes may at least include: delayed synchronization mode and real-time synchronization mode. Among them, the delayed synchronization mode refers to a mode in which, after the model is updated, the synchronization operation is performed after waiting for the user to issue a synchronization instruction; the real-time synchronization mode refers to a mode in which, after the model is updated, the synchronization operation can be performed in real time without waiting for user instructions. It should be noted that in the real-time synchronization mode, when the production software successfully establishes a communication connection with the target engine for the first time, the model data corresponding to the at least one model at the time of the first successful connection can be synchronized to the target engine to achieve synchronization of the stock data. Furthermore, in the subsequent real-time synchronization mode, the stock data can be used as the basis for incremental synchronization of model data.

[0043] After displaying the model identification of at least one model based on the above implementation, the model sending tool can detect the user operation on the model synchronization interface. If the model synchronization configuration operation on the model synchronization interface is detected, the model sending tool can determine the target synchronization mode according to the model synchronization configuration operation.

[0044] In some optional embodiments, the model synchronization interface may display a synchronization mode configuration control. In response to the configuration operation of the synchronization mode configuration control, the model sending tool may determine a target synchronization mode. The target synchronization mode includes: a delayed synchronization mode or a real-time synchronization mode. Optionally, the synchronization mode configuration control may include multiple mode options and corresponding check boxes. Figure 2 As shown, the synchronization mode configuration control displayed in the model synchronization interface includes: a wait-to-send option 203 and its check box and a real-time send option 204 and its check box. If the check box of the wait-to-send option is selected, the synchronization mode is determined to be a delayed synchronization mode. If the check box of the real-time send option is selected, the synchronization mode is determined to be a real-time synchronization mode. In other embodiments, the synchronization mode configuration control may include a synchronization mode configuration item and a drop-down option for a configuration value. When the drop-down option is triggered, multiple configuration values ​​may be displayed for selection, which are no longer illustrated.

[0045] After determining the target synchronization mode, the model sending tool may adopt an event acquisition method corresponding to the target synchronization mode to obtain a synchronization trigger event for the target model in the at least one model. Wherein. The target model may be a partial model in the at least one model, or may be all models in the at least one model, and this embodiment does not impose any limitation. Wherein. The synchronization trigger event for the target model may be a user event, or may be an update event of the target model. In different synchronization modes, the method of obtaining the synchronization trigger event is different. An exemplary description will be given below.

[0046] In some exemplary embodiments, in the delayed synchronization mode, the model sending tool may monitor the synchronization instructions issued by the user. If the synchronization instruction issued by the user for the target model is monitored, it can be determined that the synchronization trigger event of the target model is obtained. Optionally, the synchronization instruction can be issued through the model synchronization control displayed on the model synchronization interface. Figure 2 As shown, the model synchronization interface may display a "Send to Engine" control 205. If the target model is selected, if the model sending tool detects a trigger operation on the "Send to Engine" control, it is determined that the synchronization trigger event of the target model is obtained. Optionally, the synchronization instruction may also be issued by the user through a voice instruction. For example, the voice instruction may be: send model a to the target engine. In other exemplary embodiments, in real-time synchronization mode, the model sending tool may detect the update operation of the at least one model, and when detecting the update operation of the model making software on the target model in the at least one model, it is determined that the synchronization trigger event corresponding to the target model is obtained.

[0047] Optionally, in real-time synchronization mode, the model sending tool can obtain the real-time model data of the at least one model and the historical model data at the last synchronization according to a set period. The last synchronization refers to the most recent synchronization operation relative to the current moment. For any model in the at least one model, if the real-time model data of the model is inconsistent with the historical model data, the model is determined to be a target model with an update operation. The set period can be 5 seconds, 10 seconds, 15 seconds or other durations, which is not limited in this embodiment.

[0048] For example, for any model of the at least one model, after each execution of the synchronization operation of the model data, the vertex data of the model during the current synchronization operation can be cached as the historical vertex data. Subsequently, the real-time vertex data of the model can be obtained every 5 seconds, and the real-time vertex data of the model can be compared with the historical vertex data. If the real-time vertex data is inconsistent with the historical vertex data, it can be determined that the model has been updated. If it is detected that the target model is updated, the synchronization trigger event of the target model can be automatically triggered. Thereby, it is convenient for the updated model to display the model effect in the target engine in a timely manner, which improves the efficiency of the transition from the model design stage to the model effect display stage, and makes the update display of the model more real-time.

[0049] After obtaining the synchronization trigger event of the target model, the model sending tool can respond to the synchronization trigger event, send the model data to be synchronized of the target model to the target engine, and send the synchronization notification message corresponding to the target model to the target engine. After the model data is successfully sent, the model sending tool can output a prompt message of successful sending to provide effective feedback to the user.

[0050] In some exemplary embodiments, the model sending tool may establish a communication link with the target engine in advance, and send the model data to be synchronized of the target model to the target engine through the communication link.

[0051] In other exemplary embodiments, the model sending tool may determine the data cache directory of the target engine, and store the model data to be synchronized of the target model in the data cache directory. After the storage is completed, the model sending tool may send a synchronization notification message to the target engine that the target model is updated. In some optional embodiments, the model sending tool may send a synchronization notification message to the target engine based on the data cache directory, so that the target engine reads the model data to be synchronized of the target model from the data cache directory according to the synchronization notification message. That is, the synchronization notification message carries the address of the data cache directory, so that the target engine can quickly read the model data from the data cache directory according to the synchronization notification message. In other optional embodiments, the model sending tool may agree on a data synchronization method when establishing a communication connection with the target engine, and the data synchronization method includes the address of the data cache directory. Furthermore, the synchronization notification message sent by the model sending tool may not carry the address of the data cache directory. After receiving the synchronization notification message, the target engine may read the model data from the pre-agreed data cache directory. In some other embodiments, the target engine side may be configured with a default data cache address relative to each model. Upon receiving a synchronization notification message sent by a model sending tool, the target engine directly obtains corresponding data from the default data cache address to update the model.

[0052] In this implementation, the data to be synchronized of the target model is stored in the data cache directory of the target engine, so that after receiving the synchronization notification message, the target engine can quickly read the model data from the data cache directory without establishing a long link through the model sending tool and transmitting data through the long link, thereby reducing the time cost and transmission cost required for model synchronization.

[0053] Of course, in some optional embodiments, the model sending tool may determine the remote storage directory agreed with the target engine, and store the model data to be synchronized of the target model in the remote storage directory. The remote storage directory may be located on a local server, or may be located on a cloud server, or may be located on other third-party devices, and this example is not limited. The model sending tool may send a synchronization notification message to the target engine based on the remote storage directory, so that the target engine reads the model data to be synchronized of the target model from the remote storage directory according to the synchronization notification message. Based on this implementation, the remote storage directory may be provided to the distributed target engine for sharing, thereby further reducing the synchronization cost of the model.

[0054] It is worth noting that, in some exemplary embodiments, the model data synchronized by the model making software to the target engine is the updated data of the model. The updated data refers to the data generated by the modification of the model after the last synchronization, and this part of the data has not yet been synchronized to the target engine. Optionally, the model sending tool can compare the real-time model data of the target model with the historical model data at the time of the last synchronization. According to the result of the comparison, the updated data of the target model is determined, and the updated data of the target model can be stored in the data cache directory.

[0055] For example, for any model of the at least one model, after each execution of the model data synchronization operation, the vertex data of the model during the current synchronization operation can be cached as historical vertex data. Subsequently, the real-time vertex data of the model can be obtained every 5 seconds, and the real-time vertex data of the model can be compared with the historical vertex data. If the real-time vertex data is inconsistent with the historical vertex data, it can be determined that the model has been updated. At this time, the updated data of the model can be determined based on the difference between the real-time vertex data and the historical vertex data, and the updated data of the model can be written to the specified data cache directory. Based on this implementation, only the model data that has changed can be synchronized without synchronizing the full amount of model data, which reduces the amount of data to be synchronized and further improves the efficiency of model synchronization.

[0056] In this embodiment, the target engine can use the plug-in model receiving tool to communicate and exchange data with the model sending tool on the model making software side. The model making software can create a subprocess corresponding to the model sending tool, and the target engine can create a subprocess corresponding to the model receiving tool. The subprocess corresponding to the model sending tool and the subprocess corresponding to the model receiving tool can establish a communication connection based on a network transmission protocol to achieve model synchronization through the communication connection. The network transmission protocol can be a Socket protocol.

[0057] In some embodiments, the subprocess of the model sending tool is used as the client, the subprocess corresponding to the model receiving tool is used as the server, and a communication connection is established between the client and the server based on the network transmission protocol, so that data interaction between the model sending tool and the model receiving tool can be achieved. In this embodiment, the subprocess corresponding to the model sending tool is used as the client, and a communication request can be initiated based on the Socket protocol; the subprocess corresponding to the model receiving tool is used as the server, and the communication request can be received and a response message can be returned based on the Socket protocol. Based on the communication request and the response message, a communication connection can be established between the model sending tool and the model receiving tool.

[0058] In other embodiments, the subprocess of the model sending tool is used as the server, the subprocess corresponding to the model receiving tool is used as the client, and a communication connection is established between the client and the server based on the network transmission protocol, so that data interaction between the model sending tool and the model receiving tool can be achieved. In this embodiment, the subprocess corresponding to the model receiving tool is used as the client, and can initiate a communication request based on the Socket protocol; the subprocess corresponding to the model sending tool is used as the server, and can receive the communication request and return a response message based on the Socket protocol. Based on the communication request and the response message, a communication connection can be established between the model sending tool and the model receiving tool.

[0059] It is worth noting that in this embodiment, in order to ensure that the model sending operation has a high success rate, after starting the model sending tool, it is also possible to test whether there is any abnormality in the communication connection between the model sending tool and the model receiving tool. Optionally, the model synchronization interface may display a test connection button, such as Figure 2 The test button 206 shown. If the user triggers the test connection button, the model sending tool can send a test data packet to the model receiving tool through the network transmission protocol. If the confirmation data returned by the model receiving tool according to the test data packet is received, it can be determined that there is a good data connection status between the model sending tool and the model receiving tool. When the test is successful, the model synchronization interface can also display a prompt message of the test success, which is no longer shown in the figure.

[0060] In this embodiment, based on the model synchronization interface, the model identification of the model to be synchronized can be displayed, and according to the model synchronization configuration operation on the model synchronization interface, the synchronization trigger event for the target model in the at least one model is obtained. In response to the synchronization trigger event, the model data to be synchronized of the target model is synchronized to the target engine, and a synchronization notification message corresponding to the target model is sent to the target engine. Based on this embodiment, the model synchronization interface can be used to provide users with an intuitive operation entry. Based on the operation entry, the user can realize automatic synchronization of model data for the target model through simple synchronization configuration operations, without manually performing model import and export operations, and further improve the synchronization efficiency of model data on the basis of reducing the dependence of model synchronization operations on manual labor.

[0061] In addition to the above-mentioned embodiments, the present application also provides a model data synchronization method, which can be executed on the target engine side. Figure 3 As shown, when the method is executed on the target engine side, it mainly includes the following steps:

[0062] Step 301: Display the model synchronization interface.

[0063] Step 302: According to the monitoring start operation initiated on the model synchronization interface for at least one model, monitor the synchronization notification message sent by the model making software corresponding to each of the at least one model.

[0064] Step 303: when a synchronization notification message of a target model in the at least one model is monitored, the model data synchronized by the model making software corresponding to the target model is obtained to update the target model according to the model data.

[0065] The execution subject of this embodiment may be a model receiving tool in the target engine. The model receiving tool may be implemented as a plug-in. The plug-in may call an interface provided by the target engine to provide model synchronization services to users of the target engine.

[0066] The model receiving tool can detect the model synchronization operation, and respond to the model synchronization operation to display the model synchronization interface. The model synchronization operation can be triggered by the user. In some embodiments, the model receiving tool and the target engine can be installed on the same device. After the model receiving tool is installed, the model receiving tool can display a quick start icon through the toolbar of the target engine. If the model receiving tool detects a trigger operation for the quick start icon, it can be considered that the model synchronization operation is detected. The model receiving tool can display a model synchronization interface. The model synchronization interface is used to configure the model to be synchronized and to perform the synchronization operation of the model.

[0067] The model synchronization interface can provide users with the start and close operations of the model synchronization service. According to the monitoring start operation initiated on the model synchronization interface for at least one model, the model receiving tool can monitor the synchronization notification message sent by the model making software corresponding to the at least one model. The at least one model can be a model specified by the user to be synchronized to the target engine. The at least one model can be provided by the same model making software, or can be provided by different model making software.

[0068] In some exemplary embodiments, the model receiving tool may first obtain at least one model to be synchronized, and display the model identifier of the at least one model to the user. Thereafter, in response to the user's monitoring start operation of the at least one model, the model making software corresponding to the at least one model is entered into a monitoring state.

[0069] Optionally, in this embodiment, the model synchronization interface may display a model adding control, such as Figure 4The plus sign (+) control 401 shown. The model receiving tool may respond to a trigger operation on the model adding control on the model synchronization interface to display the model identification of at least one model on the model synchronization interface. In some optional embodiments, the model receiving tool may respond to a trigger operation on the model adding control on the model synchronization interface to display a model list. The model list may be provided by a resource management panel of the target engine, and the resource management panel may display a model list for selection. The model receiving tool may determine at least one model to be synchronized based on the user's selection operation on the model list, and may display the model identification of the at least one model on the model synchronization interface. In other optional embodiments, the model receiving tool may respond to a trigger operation on the model adding control on the model synchronization interface to import a model list, and the model list includes the model identification of at least one model. After importing the model list, the model receiving tool may display the model identification of the at least one model on the model synchronization interface.

[0070] Optionally, the model synchronization interface can display a listener startup control, such as Figure 4 The start button 402 is shown. In response to the triggering operation of the monitoring start control on the model synchronization interface, the model receiving tool can monitor the synchronization notification message sent by the model making software corresponding to the at least one model.

[0071] In some other optional embodiments, the model receiving tool may first respond to the user's monitoring start operation of the at least one model and enter the monitoring state. Afterwards, according to the user's operation on the model synchronization interface, at least one model to be synchronized is obtained, the model making software corresponding to the at least one model is monitored, and the model identifier of the at least one model is displayed to the user, which will not be described in detail.

[0072] Optionally, at least one model identifier displayed on the model synchronization interface can be deleted according to user operations. The model synchronization interface can display a remove button, such as Figure 4 The minus (-) button 403 is shown. After the user selects one or more model identifiers displayed on the model synchronization interface, if the user triggers the remove button, the one or more model identifiers selected by the user can be deleted. Thus, the models to be synchronized are flexibly and dynamically adjusted.

[0073] Accordingly, the model synchronization interface can also display a close listener control, such as Figure 4 The pause button 404 is shown. In response to the triggering operation of the close monitoring control, the model receiving tool can end the synchronous monitoring state.

[0074] Optionally, in different states, the model synchronization interface can display corresponding status prompt information. For example, in the synchronous listening state, the model synchronization interface can display the prompt information of "started". When the synchronous listening state is not entered, the model synchronization interface can display the prompt information of "not started". Figure 4 As shown, a "not started" prompt message may be displayed in the status prompt bar 406. Based on the prompt message, the real-time status information of the model receiving tool may be displayed to the user for user use.

[0075] Among them, the model making software can synchronize model data to the target engine based on the model sending tool. For details, please refer to the records of the aforementioned embodiment, which will not be repeated here. After entering the synchronization listening state, when the synchronization notification message of the target model in the at least one model is listened, the model receiving tool in the target engine can obtain the model data to be synchronized of the target model synchronized by the model making software corresponding to the target model. Among them, the target model can be one or more models in the at least one model, which is not limited in this embodiment.

[0076] The model receiving tool can determine whether the model corresponding to the synchronization notification message is the model to be synchronized each time it receives the synchronization notification message sent by the model making software. That is, it determines whether the identifier of the model requested for synchronization is located in the model identifier displayed on the model synchronization interface. If yes, the model data of the model is obtained according to the synchronization notification message.

[0077] In some optional embodiments, the model making software may send the model data to the target engine through a communication connection established between the target engine and the target engine, and after receiving the model data, the target engine may write the model data into a persistent storage space or a cache space.

[0078] In other optional embodiments, the model making software synchronizes the model data to the target engine by writing the model data into the cache of the target engine. Optionally, in this embodiment, the model receiving tool can obtain the synchronization notification message of the target model sent by the model making software, and the synchronization notification message carries a specified data cache directory. The data cache directory can be located in the memory space allocated to the target engine, so that the target engine can quickly read the model data. The model receiving tool can parse the synchronization notification message of the target model, obtain the data cache directory carried by the synchronization notification message, and read the data according to the data cache directory to obtain the model data to be synchronized of the target model. Among them, the read model data can be used to update the target model. When the target model is updated, the target model can be rendered, mapped and other operations can be performed in the target engine, which will not be repeated here.

[0079] It should be noted that, in some optional embodiments, after the model receiving tool obtains the model data of the target model, if it is identified that the model data does not meet the specified requirements, the model receiving tool may not perform the update operation of the target model and may delete the model data. The specified requirements may include: at least one of the following: content adjustment requirements, format requirements, validity period requirements, and updater authority requirements, which are not described in detail here.

[0080] Wherein, when the target model includes multiple models, the multiple models can be provided by multiple different model making software. The target engine can realize data interaction with multiple model making software based on the model receiving tool. In some optional embodiments, the target engine can establish a communication connection with a single model making software at the same time, and each data interaction can support the model data of a single model synchronized by a single model making software. That is, the target engine can support the modification operation of a single model by a single model making software at the same time. When multiple models are provided by multiple different model making software (or multiple different user terminals of the same software), multiple different model making software can establish communication connections with the target engine at different time periods. In other optional embodiments, the target engine can establish a communication connection with multiple model making software at the same time, and each data interaction can support the model data of a single model synchronized by a single model making software. The subprocess corresponding to the model receiving tool can establish a communication connection with the respective subprocesses of multiple model sending tools. Wherein, when the subprocess of a model sending tool performs the synchronization operation of the model data, the respective subprocesses of the remaining other model sending tools enter the suspended operation state. In this embodiment, a mapping relationship between multiple models and multiple different model making software can be established in advance. When the model receiving tool receives synchronization notification messages sent by multiple model sending tools for the same model, it can determine the model making software corresponding to the model based on the mapping relationship and read the model data synchronized by the model sending tool of the model making software. In this way, the risk of errors caused by multiple model making software modifying the same model at the same time can be reduced.

[0081] Among them, multiple model making software can be run on different terminals. In some actual application scenarios, multiple model making software can be used by different users, and the models designed and made by different users can be provided to the target engine for use, realizing collaborative work between multiple users or multiple departments.

[0082] In this embodiment, the model receiving tool in the target engine can display the model synchronization interface, and according to the monitoring start operation initiated on the model synchronization interface for at least one model, monitor the synchronization notification message sent by the model making software corresponding to the at least one model. When the synchronization notification message of the target model in the at least one model is monitored, the model data to be synchronized of the target model synchronized by the model making software corresponding to the target model is obtained. Based on this embodiment, the model synchronization interface can be used to provide users with an intuitive operation entry. Based on the operation entry, users can realize automatic synchronization of model data for the target model through simple synchronization configuration operations, without the need to manually perform model import and export operations, thereby reducing the dependence of model synchronization operations on manual operations.

[0083] It should be noted that the execution subject of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 101 to 104 can be device A; for another example, the execution subject of steps 101 and 102 can be device A, and the execution subject of step 103 can be device B; and so on.

[0084] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or executed in parallel, and the sequence numbers of the operations, such as 101, 102, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit the "first" and "second" to be different types.

[0085] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0086] Figure 5 A schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application is shown. Figure 5 As shown, the electronic device includes: a memory 501 and a processor 502.

[0087] The memory 501 is used to store computer programs and can be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application program or method operating on the electronic device.

[0088] In some embodiments, Figure 5 The illustrated electronic device can be used to execute a model data synchronization method on the model making software side, wherein a processor 502, coupled to a memory 501, is used to execute a computer program in the memory 501, for: displaying a model synchronization interface; displaying a model identifier of at least one model to be synchronized on the model synchronization interface; the at least one model is produced by the model making software; obtaining a synchronization trigger event for a target model in the at least one model according to a model synchronization configuration operation on the model synchronization interface; synchronizing the model data to be synchronized of the target model to a target engine in response to the synchronization trigger event, and sending a synchronization notification message corresponding to the target model to the target engine.

[0089] Optionally, when the processor 502 obtains the synchronization trigger event for the target model in the at least one model according to the model synchronization configuration operation on the model synchronization interface, it is specifically used to: respond to the configuration operation of the synchronization mode configuration control on the model synchronization interface to determine the target synchronization mode; the target synchronization mode includes: delayed synchronization mode or real-time synchronization mode; adopt an event acquisition method corresponding to the target synchronization mode to obtain the synchronization trigger event for the target model in the at least one model.

[0090] Optionally, when the processor 502 adopts the event acquisition method corresponding to the target synchronization mode to obtain the synchronization trigger event of the target model, it is specifically used to: in the delayed synchronization mode, if a synchronization instruction issued by the user to the target model is monitored, it is determined that the synchronization trigger event of the target model is obtained; wherein the synchronization instruction is issued through the model synchronization control displayed on the model synchronization interface, or the synchronization instruction is issued through a voice instruction; in the real-time synchronization mode, the update operation of at least one model is detected, and when the update operation of the model making software on the target model in the at least one model is detected, it is determined that the synchronization trigger event corresponding to the target model is obtained.

[0091] Optionally, when the processor 502 detects an update operation of the at least one model in the real-time synchronization mode, it is specifically used to: in the real-time synchronization mode, obtain the real-time model data of the at least one model and the historical model data at the time of the last synchronization according to a set period; for any model of the at least one model, if the real-time model data of the model is inconsistent with the historical model data, determine that the model is a target model with an update operation.

[0092] Optionally, when synchronizing the model data to be synchronized of the target model to the target engine and sending a synchronization notification message corresponding to the target model to the target engine, the processor 502 is specifically used to: determine the data cache directory of the target engine; store the model data to be synchronized of the target model in the data cache directory; and send a synchronization notification message to the target engine that the target model is updated. Optionally, the processor 502 may send a synchronization notification message corresponding to the target model to the target engine based on the data cache directory, so that the target engine reads the model data to be synchronized of the target model from the data cache directory based on the synchronization notification message.

[0093] Optionally, when storing the model data to be synchronized of the target model in the data cache directory, the processor 502 is specifically used to: compare the real-time model data of the target model with the historical model data at the time of the last synchronization; determine the updated data of the target model based on the comparison result; and store the updated data of the target model in the data cache directory.

[0094] Optionally, the model synchronization interface also includes: a model adding control; when the processor 502 displays the model identification of at least one model to be synchronized on the model synchronization interface, it is specifically used to: respond to a triggering operation on the model adding control, determine at least one selected model; and display the model identification of the at least one model on the model synchronization interface.

[0095] In this embodiment, based on the model synchronization interface, the model identifier of the model to be synchronized can be displayed, and according to the model synchronization configuration operation on the model synchronization interface, the synchronization trigger event for the target model in the at least one model is obtained. In response to the synchronization trigger event, a synchronization notification message corresponding to the target model is sent to the target engine, and the model data to be synchronized of the target model is synchronized to the target engine. Based on this embodiment, the model synchronization interface can be used to provide users with an intuitive operation entry. Based on the operation entry, the user can realize automatic synchronization of model data for the target model through simple synchronization configuration operations, without the need to manually perform model import and export operations, thereby reducing the model synchronization operation's dependence on manual labor.

[0096] In other embodiments, Figure 5The illustrated electronic device can be used to execute a model data synchronization method on a target engine side, wherein a processor 502 is coupled to a memory 501 and is used to execute a computer program in the memory 501, so as to: display a model synchronization interface; according to a monitoring start operation initiated on the model synchronization interface for at least one model, monitor synchronization notification messages sent by model making software corresponding to each of the at least one model; when a synchronization notification message of a target model in the at least one model is monitored, obtain model data synchronized by the model making software corresponding to the target model, so as to update the target model according to the model data.

[0097] Optionally, when the processor 502 listens to the synchronization notification message sent by the model production software corresponding to the at least one model according to the listening start operation initiated on the model synchronization interface for at least one model, it is specifically used to: respond to the triggering operation of adding controls to the model on the model synchronization interface, and display the model identifier of the at least one model on the model synchronization interface; respond to the listening start operation on the at least one model on the model synchronization interface, and listen to the synchronization notification message sent by the model production software corresponding to the at least one model.

[0098] Optionally, when the processor 502 obtains the model data synchronized by the model making software corresponding to the target model, it is specifically used to: parse the synchronization notification message of the target model to obtain the data cache directory carried by the synchronization notification message; read data according to the data cache directory to obtain the model data to be synchronized of the target model.

[0099] In this embodiment, the model receiving tool in the target engine can display the model synchronization interface, and according to the monitoring start operation initiated on the model synchronization interface for at least one model, monitor the synchronization notification message sent by the model making software corresponding to the at least one model. When the synchronization notification message of the target model in the at least one model is monitored, the model data to be synchronized of the target model synchronized by the model making software corresponding to the target model is obtained. Based on this embodiment, the model synchronization interface can be used to provide users with an intuitive operation entry. Based on the operation entry, users can realize automatic synchronization of model data for the target model through simple synchronization configuration operations, without the need to manually perform model import and export operations, thereby reducing the dependence of model synchronization operations on manual operations.

[0100] Further, if Figure 5 As shown, the electronic device also includes: a communication component 503, a power component 504, a display component 505, an audio component 506 and other components. Figure 5 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 5 Components shown.

[0101] Among them, the memory 501 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0102] The communication component 503 is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as Wi-Fi (wireless network communication technology), 2G (such as Global System for Mobile Communications (GSM)), 3G (such as Wideband Code Division Multiple Access (WCDMA), 4G (such as Long Term Evolution (LTE)), 4G+ (such as upgraded Long Term Evolution (LTE-Advanced, LTE-A)) or 5G (Fifth Generation Mobile Communication Technology), or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component can be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

[0103] The power supply component 504 is used to provide power to various components of the device where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components that are synchronized with generating, managing and distributing power to the device where the power supply component is located.

[0104] The display component 505 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor can not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0105] The audio component 506 may be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal may be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0106] Correspondingly, an embodiment of the present application also provides a computer-readable storage medium storing a computer program, which, when executed, can implement the various steps that can be executed by the electronic device in the above-mentioned model data synchronization method embodiment.

[0107] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM (Compact Disc Read-Only Memory, read-only optical disc read-only memory), optical storage, etc.) containing computer-usable program codes.

[0108] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0109] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0110] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0111] In a typical configuration, a computing device includes one or more processors (Central Processing Unit, CPU), input / output interface, network interface and memory.

[0112] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0113] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, Parallel Random Access Machine (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, Digital Video Disc (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0114] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0115] The above is only an 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 changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A model data synchronization method, characterized in that: include: Display the model synchronization interface; Displaying a model identifier of at least one model to be synchronized on the model synchronization interface; The at least one model is made by model making software; Acquire a synchronization trigger event for a target model in the at least one model according to a model synchronization configuration operation on the model synchronization interface; In response to the synchronization trigger event, the model data to be synchronized of the target model is synchronized to the target engine, and a synchronization notification message corresponding to the target model is sent to the target engine.

2. The method according to claim 1, characterized in that: Acquiring a synchronization trigger event for a target model in the at least one model according to a model synchronization configuration operation on the model synchronization interface includes: In response to the configuration operation of the synchronization mode configuration control on the model synchronization interface, a target synchronization mode is determined; the target synchronization mode includes: a delayed synchronization mode or a real-time synchronization mode; An event acquisition method corresponding to the target synchronization mode is adopted to acquire a synchronization trigger event for a target model in the at least one model.

3. The method according to claim 2, characterized in that Acquiring the synchronization trigger event of the target model by adopting the event acquisition method corresponding to the target synchronization mode, including: In the delayed synchronization mode, if a synchronization instruction issued by the user for the target model is monitored, it is determined that a synchronization trigger event of the target model is obtained; wherein the synchronization instruction is issued through a model synchronization control displayed on the model synchronization interface, or the synchronization instruction is issued through a voice instruction; In the real-time synchronization mode, an update operation of the at least one model is detected, and when an update operation of the model making software on a target model in the at least one model is detected, it is determined that a synchronization trigger event corresponding to the target model is obtained.

4. The method according to claim 3, characterized in that In the real-time synchronization mode, detecting the update operation of the at least one model includes: In the real-time synchronization mode, real-time model data of the at least one model and historical model data at the last synchronization are respectively obtained according to a set period; For any model among the at least one model, if the real-time model data of the model is inconsistent with the historical model data, the model is determined to be a target model for which an update operation exists.

5. The method according to any one of claims 1 to 4, characterized in that: Synchronizing the model data to be synchronized of the target model to the target engine, and sending a synchronization notification message corresponding to the target model to the target engine, including: Determine the data cache directory of the target engine; Storing the model data to be synchronized of the target model in the data cache directory; A synchronization notification message is sent to the target engine indicating that the target model is updated.

6. The method according to claim 5, characterized in that Storing the model data to be synchronized of the target model in the data cache directory includes: Comparing the real-time model data of the target model with the historical model data at the last synchronization; Determining update data of the target model according to the comparison result; The updated data of the target model is stored in the data cache directory.

7. The method according to any one of claims 1 to 4, characterized in that: The model synchronization interface further includes: a model adding control; and displaying a model identifier of at least one model to be synchronized on the model synchronization interface, including: In response to a triggering operation of adding a control to the model, determining at least one model to be selected; On the model synchronization interface, a model identifier of the at least one model is displayed.

8. A model data synchronization method, characterized in that: include: Display the model synchronization interface; According to the monitoring start operation initiated on the model synchronization interface for at least one model, monitoring the synchronization notification message sent by the model making software corresponding to each of the at least one model; When a synchronization notification message of a target model in the at least one model is monitored, model data synchronized by the model making software corresponding to the target model is obtained to update the target model according to the model data.

9. The method according to claim 8, characterized in that According to the monitoring start operation initiated on the model synchronization interface for at least one model, monitoring the synchronization notification message sent by the model making software corresponding to the at least one model includes: In response to a triggering operation of adding a control to a model on the model synchronization interface, displaying a model identifier of the at least one model on the model synchronization interface; In response to a monitoring start operation on the at least one model on the model synchronization interface, a synchronization notification message sent by a model making software corresponding to the at least one model is monitored.

10. The method according to claim 8 or 9, characterized in that: Acquiring model data synchronized with the model making software corresponding to the target model, including: Parsing the synchronization notification message of the target model to obtain the data cache directory carried by the synchronization notification message; Data is read according to the data cache directory to obtain the model data to be synchronized of the target model.

11. An electronic device, characterized in that: include: Memory processor; The memory is used to store one or more computer instructions; The processor is used to execute the one or more computer instructions to: execute the steps in the model data synchronization method according to any one of claims 1-10.

12. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, it can implement the model data synchronization method described in any one of claims 1 to 10.

Images