Model synchronous updating method and device, storage medium and electronic equipment

Abstract

The invention relates to a model synchronization updating method and device, a storage medium and electronic equipment. The method comprises the steps of obtaining to-be-synchronized data of a to-be-synchronized model; polling the target modification record list, and judging whether each record item in the target modification record list conflicts with the existing configuration condition of the sub-level model or not; if the conflict exists, further judging whether the conflict is an agreed conflict which can be processed or not; if not, outputting error reporting prompt information; if yes, performing agreed processing on the modification type of the corresponding parent model and the corresponding modification object parameter according to the processing mode corresponding to the agreed processable conflict; and if the conflict does not exist, updating the modification type of the parent model corresponding to the conflict and the corresponding modification object parameter into the child model, so that the synchronous updating efficiency of the model can be improved.

Description

Technical Field

[0001] The present invention relates to the field of industrial process application, and in particular to a model synchronization updating method, device, storage medium and electronic equipment. Background Art

[0002] The mid-term technological transformation of the process industry requires optimization analysis, program transformation and result comparison. In addition, the program transformation requires multiple changes to the existing core process model, such as adjusting the topological structure of the process, adding or reducing device models, and adjusting the material components of the input logistics. After making multiple changes, irregular unified adjustments will be made. In this process, comparative analysis and bottleneck identification will be carried out for the derived models in different directions at different stages to verify the impact of the transformation plan on the overall situation and determine the final transformation plan.

[0003] Furthermore, after determining the final transformation plan, the user needs to manually and repeatedly modify multiple models in sequence, so there is at least a problem of low efficiency. Summary of the invention

[0004] 1. Technical issues to be resolved In view of the above-mentioned shortcomings and deficiencies of the prior art, the present invention provides a model synchronization update method, device, storage medium and electronic device, which solve the technical problem of relatively low model synchronization efficiency in the prior art.

[0005] (II) Technical solution In order to achieve the above object, the main technical solutions adopted by the present invention include: In the first aspect, an embodiment of the present invention provides a model synchronization update method, comprising: obtaining data to be synchronized of a model to be synchronized; wherein the model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameters, and the modification object parameters include at least one of a module ID, a port ID and a stream ID; polling the target modification record list, and determining whether each record item in the target modification record list conflicts with the existing configuration of the child model; if there is a conflict, further determining whether the conflict is a conflict that can be handled by agreement; if the determination is no, outputting an error prompt message; if the determination is yes, performing agreed processing on the modification type of the corresponding parent model and its corresponding modification object parameters in accordance with the corresponding processing method for conflicts that can be handled by agreement; if there is no conflict, updating the modification type of the corresponding parent model and its corresponding modification object parameters to the child model.

[0006] In a possible embodiment, the process of obtaining the target modification record list includes: in the process of continuous modification of the parent model, generating a primary modification record list of the parent model based on the modification data of the parent model; after the modification of the parent model is completed, integrating the records of the primary modification record list to obtain a modification record list after the first integration; based on the modification record list after the first integration, obtaining the target modification record list.

[0007] In one possible embodiment, based on the modification record list after the first integration, a target modification record list is obtained, including: when the child model has the modification record list stored by the last parent model, the modification record list after the first integration and the final modification record list of the last model synchronization update process stored based on the last parent model are integrated to obtain the modification record list after the second integration; and the modification record list after the second integration is used as the target modification record list.

[0008] In a possible embodiment, the model synchronization update method further includes: in the case where there is a grandchild model under the child model, a modification record list of the child model is formed inside the child model based on each data item updated by the child model.

[0009] In a second aspect, an embodiment of the present invention provides a model synchronization and updating device, characterized in that it includes: an acquisition module, which is used to acquire the data to be synchronized of the model to be synchronized; wherein the model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameters, and the modification object parameters include at least one of a module ID, a port ID and a stream ID; a polling judgment module, which is used to poll the target modification record list, and judge whether each record item in the target modification record list conflicts with the existing configuration of the child model; an output processing module, which is used to further judge whether the conflict is a conflict that can be handled by agreement if there is a conflict; if the judgment is no, an error prompt message is output; if the judgment is yes, the modification type of the corresponding parent model and its corresponding modification object parameter are processed by agreement according to the corresponding processing method of the conflict that can be handled by agreement; an update module, which is used to update the modification type of the corresponding parent model and its corresponding modification object parameter to the child model if there is no conflict.

[0010] In one possible embodiment, the acquisition module is specifically used to: generate a primary modification record list of the parent model based on the modification data of the parent model during the continuous modification of the parent model; after the modification of the parent model is completed, integrate the records of the primary modification record list to obtain a modification record list after the first integration; and obtain a target modification record list based on the modification record list after the first integration.

[0011] In one possible embodiment, the acquisition module is specifically used to: when the child model has a modification record list stored by the last parent model, record and integrate the modification record list after the first integration and the final modification record list of the last model synchronization update process based on the last parent model storage to obtain the modification record list after the second integration; and use the modification record list after the second integration as the target modification record list.

[0012] In a possible embodiment, the model synchronization update device further includes: a list forming module, which is used to form a modification record list of the child model within the child model based on each item of data updated by the child model when there is a grandchild model under the child model.

[0013] In a third aspect, an embodiment of the present application provides a storage medium having a computer program stored thereon, and the computer program is executed by a processor to execute the method described in the first aspect or any optional implementation of the first aspect.

[0014] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the method described in the first aspect or any optional implementation method of the first aspect is performed.

[0015] In a fifth aspect, the present application provides a computer program product, which, when running on a computer, enables the computer to execute the method in the first aspect or any possible implementation of the first aspect.

[0016] (III) Beneficial effects The beneficial effects of the present invention are: The embodiments of the present application provide a model synchronization update method, device, storage medium and electronic device, which obtain the data to be synchronized of the model to be synchronized; wherein the model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameters, and the modification object parameters include module ID, port ID and / or stream ID; polling the target modification record list, and judging whether each record item in the target modification record list conflicts with the existing configuration of the child model; if there is a conflict, further judging whether the conflict is a conflict that can be handled by agreement; if the judgment is no, outputting an error prompt message; if the judgment is yes, performing agreed processing on the modification type of the corresponding parent model and its corresponding modification object parameters according to the corresponding processing method of the conflict that can be handled by agreement; if there is no conflict, updating the modification type of the corresponding parent model and its corresponding modification object parameters to the child model, which can improve the model synchronization efficiency compared with the prior art.

[0017] In order to make the above-mentioned objectives, features and advantages to be achieved by the embodiments of the present application more obvious and understandable, the following specifically cites preferred embodiments and describes them in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1 A schematic diagram showing the process of an existing mid-term transformation; Figure 2 An overview diagram showing the relationship between a parent model, a child model, and a grandchild model provided by an embodiment of the present application; Figure 3 A schematic diagram of a parent model provided in an embodiment of the present application is shown; Figure 4 A schematic diagram of a parent model modification provided by an embodiment of the present application is shown; Figure 5 A schematic diagram of a sub-level model provided in an embodiment of the present application is shown; Figure 6 A schematic diagram of sub-level model synchronization provided by an embodiment of the present application is shown; Figure 7 . A flowchart showing a model synchronization update method provided in an embodiment of the present application is shown; Figure 8 A structural block diagram of a model synchronization updating device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0020] In order to better explain the present invention and facilitate understanding, the present invention is described in detail below through specific implementation modes in conjunction with the accompanying drawings.

[0021] See also Figure 1 , Figure 1 A schematic diagram of the existing mid-term transformation process is shown. Figure 1 As shown, the process includes: step S110, performing bottleneck analysis on the existing core process model to find out multiple optimization directions; step S120, performing multiple isolated model transformations according to the optimization directions; step S130, running these derived models according to different working conditions, and exporting the results to a table file; step S140, combing and comparing the table files to find out the optimization directions in several cases; step S150, returning to step S120 for transformation again, and iterating to obtain the final feasible best solution.

[0022] However, the existing solution is a single-model engineering configuration, independent configuration and operation, without the association and interaction between multiple solutions, and manual comparison of operation results is required. The disadvantage of this solution is that it is inefficient and prone to errors. The reason is that the transformation of the model is isolated, and the configuration actions of each model need to be completely closed until the results can be obtained. It is very likely that most of the configurations in multiple optimization directions are exactly the same, and only a small part is different. This means that there are many repeated actions for users and they must always pay attention to different places to avoid making mistakes. In addition, if the mid-term transformation process is long and there are many ideas, there will be many rounds of reciprocating iterations, which increases the frequency of repetitive work. Another disadvantage is the result comparison. Because the isolated models are independent of each other, the analysis of the advantages and disadvantages of the solutions also requires the sorting of tabular result files and manual comparison, which is very easy to make mistakes.

[0023] In other words, the existing mid-term transformation methods have the following problems: repeated editing of the same configuration, excessive repetitive work; the complexity of differentiated configuration in multiple optimization directions; the comparison results require manual comparison of spreadsheet files separately, which may lead to misjudgment; and multiple optimization steps increase the complexity of the configuration exponentially.

[0024] Based on this, an embodiment of the present application provides a model synchronization update method, device, storage medium and electronic device, by obtaining the data to be synchronized of the model to be synchronized; wherein the model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameters, and the modification object parameters include module ID, port ID and / or stream ID; polling the target modification record list, and judging whether each record item in the target modification record list conflicts with the existing configuration of the child model; if there is a conflict, further judging whether the conflict is a conflict that can be handled by agreement; if the judgment is no, outputting an error prompt message; if the judgment is yes, performing agreed processing on the modification type of the corresponding parent model and its corresponding modification object parameters according to the corresponding processing method of the conflict that can be handled by agreement; if there is no conflict, updating the modification type of the corresponding parent model and its corresponding modification object parameters to the child model. Compared with the prior art, it not only does not need to export the table file for manual comparison separately, thus reducing misjudgment, but also can avoid repeated configuration and reduce labor costs.

[0025] In order to better understand the above technical solution, exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to enable a clearer and more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0026] In order to facilitate understanding of the embodiments of the present application, some terms involved in the present application are explained as follows: “Process simulation software”: it is a tool used to simulate and analyze various business processes, and these software usually provide a visual interface that allows users to create, edit and execute different process models; "Engineering Configuration": The user forms the simulation information data corresponding to the actual device through simple UI operation and configuration of related settings; "Topology": In steady-state process simulation software, it refers to the structure or configuration formed by the connection relationship between modules, and it describes the location, connection method and relationship between modules and streams; "Derive": This means creating a new model from an existing model. The child model inherits the engineering configuration information of the parent model and expands or modifies part of the configuration inherited from the parent model. "Parent model / child model": Here it specifically refers to the parent-child relationship of the derived relationship of the engineering configuration of the process simulation. Correspondingly, "child model / grandchild model" is similar, please refer to the relevant description of "parent model / child model" for details.

[0027] For further information, see Figure 2 , Figure 2 FIG. 1 shows an overview of the relationship between a parent model, a child model, and a grandchild model provided by an embodiment of the present application. Figure 2 As shown, these models have strict parent-child and descendant relationships, and the synchronization direction of this application is downward synchronization, seeking common ground while reserving differences. In addition, the parent model allows multiple child models to be derived, and the inheritance relationship between them is set, and the child model can be derived again.

[0028] like Figure 3 , Figure 4 , Figure 5 and Figure 6 As shown, when the parent model (i.e. the original model) includes a shell and tube heat exchanger (selected by a blue box) and several heaters, the technical transformation requirement is to change the shell and tube heat exchanger to a tower device, both with 2 inlets and 2 outlets. In this way, the original model is the parent model, and the model that replaces the tower equipment is its subordinate child model. Most of the configuration information is an inheritance relationship.

[0029] It should be noted here that although Figure 3 , Figure 4 , Figure 5 and Figure 6 However, it should be understood that the device models are merely exemplary and do not have specific meanings. They are only used to facilitate understanding.

[0030] On this basis, replace their common heaters with real heat exchangers. At this time, corresponding modifications need to be made to the parent model, such as deleting heaters, adding heat exchangers, changing heat exchanger names, changing stream names, and rewiring, and other series of configuration operations.

[0031] The embodiment of the present application provides a method for synchronously updating a model based on inheritance, in which a child model does not need to be repeatedly modified like a parent model. When a child model is opened, a series of operations performed by the parent (selected by a blue box) are synchronized to the child model without any difference, while the differences between the shell and tube heat exchanger and tower equipment (selected by a red box) between the two remain unchanged. The two are then run to compare the results to find bottlenecks and view optimization effects.

[0032] In addition, the main steps of the mid-term transformation operation of this application are: to envision the direction of technical transformation and possible bottlenecks for existing model cases; to derive multiple models from the existing model based on the previous assumptions, and to perform differentiated optimization and transformation on each model; to maintain its multi-case structure, and when performing common transformations later, changes need to be made in the original parent model case, and other derived child models will be synchronized according to the method described in this application; to perform many rounds of operation result comparisons between multiple models to clarify the advantages and disadvantages of each solution; or to synthesize multiple solutions to form a new derived model solution, and then conduct rigorous result comparison, and finally determine the final solution for the technical transformation.

[0033] In the case of a multi-case project with a parent-child relationship, continue to refer to Figure 7 , Figure 7 A flow chart of a model synchronization update method provided by an embodiment of the present application is shown. It should be understood that the model synchronization update method can be executed by a model synchronization update device, and the specific device of the model synchronization update device can be set according to actual needs, and the embodiment of the present application is not limited thereto. For example, the model synchronization update device can be a computer, or a server, etc. Specifically, the model synchronization update method includes: Step S710, obtaining the data to be synchronized of the model to be synchronized. The model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameter, and the modification object parameter includes at least one of a module ID, a port ID, and a stream ID.

[0034] It should be understood that the process of obtaining the target modification record list can be set according to actual needs, and the embodiments of the present application are not limited to this.

[0035] Optionally, the process of obtaining the target modification record list includes: in the process of continuous modification of the parent model, based on the modification data of the parent model, generating a primary modification record list of the parent model; after the modification of the parent model is completed, recording and integrating the primary modification record list to obtain a modification record list after the first integration; based on the modification record list after the first integration, obtaining the target modification record list. In the process of record integration, the integration needs to be carried out from the front to the back according to the record time. And, if there are multiple child models, there will be multiple modification record lists.

[0036] And, the target modification record list is obtained based on the modification record list after the first integration, including: when the child model has a final modification record list based on the modification record list stored by the last parent model, the modification record list after the first integration and the final modification record list of the last model synchronization update process stored by the last parent model are recorded and integrated to obtain the modification record list after the second integration; and the modification record list after the second integration is used as the target modification record list. In addition, when the child model does not have a modification record list stored by the last parent model, the modification record list after the first integration is directly used as the target modification record list.

[0037] Among them, the final modification record list of the last model synchronization update process stored in the last parent model is the first integrated modification record list obtained by integrating the modification record list of the last parent model (that is, it is the second model synchronization update, and the first model synchronization update is to directly use the first integrated modification record list sent by the parent model to perform model synchronization update), or it is the second integrated modification record list obtained by integrating the first integrated modification record list corresponding to the last parent model and the final second integrated modification record list stored in the child model (that is, it is after the third model synchronization update).

[0038] For ease of understanding, the list of related modification records can be found in Table 1 below.

[0039] Table 1

[0040] It should be noted here that the unique identification of each object entity must be guaranteed, which is represented by ID here, and models or flows with the same ID at the parent-child or descendant level indicate that they are in an inheritance relationship.

[0041] It should also be noted here that a flow stream has only one entrance and one exit; a module has multiple ports, which can be configured to be added or deleted; a port ID is unique within a module; modules cannot be connected to modules, only to flow streams; and flow streams cannot be connected to flow streams, only to modules.

[0042] It should also be understood that the specific rules for record integration can be set according to actual needs, and the embodiments of the present application are not limited to this.

[0043] Optionally, as shown in Table 2 below, it shows the rules for record integration.

[0044] Table 2

[0045] In Table 2, U represents a module ID, S represents a stream ID, and P represents a port ID.

[0046] It should be noted here that the four types of modification modules-XX U in Table 2 refer to the modification modules-internal items, modification modules-names, modification modules-port additions and modification modules-port deletions in Table 1; the three types of modification streams-XX S in Table 2 refer to the modification streams-names, modification streams-input ports and modification streams-output ports in Table 1.

[0047] It should also be noted that U0 and U1 in Table 2 represent different modules; P0 and P1 represent different ports. Also, Modify Module-Port Add (U, P) + Modify Module-Port Delete (U, P) represents two cases: Modify Module-Port Add (U) + Modify Module-Port Delete (U), and Modify Module-Port Add (P) + Modify Module-Port Delete (P). Other cases in Table 2 are similar and will not be repeated here.

[0048] Step S720, polling the target modification record list, and determining whether each record item in the target modification record list conflicts with the existing configuration of the child model.

[0049] Step S730: If there is a conflict, it is further determined whether the conflict is a conflict that can be handled by agreement; if it is determined to be no, an error message is output; if it is determined to be yes, the modification type of the corresponding parent model and its corresponding modification object parameters are handled by agreement according to the corresponding handling method of the conflict that can be handled by agreement. In the case of no, in addition to outputting an error message to prompt manual handling, it can also roll back to the original configuration.

[0050] It should be understood that the agreed upon conflicts that can be handled and their corresponding handling methods can be set according to actual needs, and the embodiments of the present application are not limited to this.

[0051] Optionally, please refer to Table 3 below, which shows the conflict situations that can be handled by the agreement and their corresponding handling methods.

[0052] Table 3

[0053] Step S740: If there is no conflict, the modification type of the corresponding parent model and its corresponding modification object parameters are updated to the child model.

[0054] In addition, the model synchronization update method further includes: in the case where there is a grandchild model under the child model, a modification record list of the child model must be formed inside the child model based on each item of data updated by the child model, and the model synchronization update process of the child model and the grandchild model can refer to the model synchronization update process of the parent model and the child model mentioned above, and will not be repeated here.

[0055] Therefore, compared with the prior art, the present application has the following effects: avoiding repeated configuration and reducing labor costs; for differentiated solutions, only focusing on differentiated configuration content, which is user-friendly; there are clear model comparison results, and there is no need to export table files for manual comparison separately, reducing misjudgment; multiple optimization steps can perform multiple derivations of sub-models to form an effective tree overview diagram, which can effectively trace back the ideas of its technical transformation and is more conducive to obtaining the best final solution.

[0056] It should be understood that the above-mentioned model synchronization update method is only exemplary, and those skilled in the art may make various modifications based on the above-mentioned method, and the modified scheme also belongs to the protection scope of this application.

[0057] See also Figure 8 , Figure 8 The structural block diagram of a model synchronization update device 800 provided in an embodiment of the present application is shown. It should be understood that the model synchronization update device 800 can execute each step in the above method embodiment. The specific functions of the model synchronization update device 800 can be found in the description above. To avoid repetition, the detailed description is appropriately omitted here. The model synchronization update device 800 includes at least one software function module that can be stored in a memory in the form of software or firmware or solidified in the operating system (OS) of the model synchronization update device 800. Specifically, the model synchronization update device 800 includes: The acquisition module 810 is used to acquire the data to be synchronized of the model to be synchronized; wherein the model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameter, and the modification object parameter includes at least one of a module ID, a port ID and a stream ID; A polling judgment module 820 is used to poll the target modification record list and judge whether each record item in the target modification record list conflicts with the existing configuration of the child model; Output processing module 830 is used to further determine whether the conflict is a conflict that can be handled by agreement if there is a conflict; if it is not, output an error message; if it is yes, perform agreed processing on the modification type of the corresponding parent model and its corresponding modification object parameters according to the corresponding processing method of the conflict that can be handled by agreement; The updating module 840 is used to update the modification type of the corresponding parent model and its corresponding modification object parameters to the child model if there is no conflict.

[0058] In one possible embodiment, the acquisition module 810 is specifically used to: generate a primary modification record list of the parent model based on the modification data of the parent model during the continuous modification of the parent model; after the modification of the parent model is completed, integrate the records of the primary modification record list to obtain a modification record list after the first integration; and obtain a target modification record list based on the modification record list after the first integration.

[0059] In one possible embodiment, the acquisition module 810 is specifically used to: when the child model has a modification record list stored by the last parent model, record and integrate the modification record list after the first integration and the final modification record list of the last model synchronization update process based on the last parent model storage to obtain the modification record list after the second integration; and use the modification record list after the second integration as the target modification record list.

[0060] In a possible embodiment, the model synchronization update device 800 further includes: a list forming module (not shown), which is used to form a modification record list of the child model within the child model based on each item of data updated by the child model when there is a grandchild model under the child model.

[0061] Since the device described in the above embodiment of the present invention is a device used to implement the method of the above embodiment of the present invention, based on the method described in the above embodiment of the present invention, a person skilled in the art can understand the specific structure and deformation of the device, so it is not described here. All devices used in the method of the above embodiment of the present invention belong to the scope of protection of the present invention.

[0062] The present application provides a storage medium having a computer program stored thereon. The computer program is executed by a processor to execute the method described in the embodiment.

[0063] The present application also provides a computer program product, which, when executed on a computer, enables the computer to execute the method described in the method embodiment.

[0064] It should be understood 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 aspects. Moreover, 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, optical storage, etc.) containing computer-usable program code.

[0065] 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 box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions.

[0066] It should be noted that the word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention may be implemented by means of hardware comprising a number of different components and by means of a suitably programmed computer. Among the several means listed, several of these means may be embodied by the same hardware. The use of the words first, second, third, etc., is for convenience of expression only and does not indicate any order. These words may be understood as part of the name of the component.

[0067] In addition, it should be noted that, in the description of this specification, the description of the terms "one embodiment", "some embodiments", "embodiment", "example", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are contradictory.

[0068] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments after knowing the basic creative concept. Therefore, the technical solution should be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present invention.

[0069] Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention belong to the scope of the technical solution of the present invention and its equivalent technology, the present invention should also include these modifications and variations.

Claims

1. A model synchronization update method, characterized in that: include: Acquire the data to be synchronized of the model to be synchronized; wherein the model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameter, and the modification object parameter includes at least one of a module ID, a port ID and a stream ID; Polling the target modification record list, and determining whether each record item in the target modification record list conflicts with the existing configuration of the child model; If there is a conflict, it is further determined whether the conflict is a conflict that can be handled by agreement; if it is determined to be not, an error message is output; if it is determined to be yes, the modification type of the corresponding parent model and its corresponding modification object parameters are handled by agreement according to the corresponding handling method of the conflict that can be handled by agreement; If there is no conflict, the modification type of the corresponding parent model and its corresponding modification object parameters are updated to the child model.

2. The model synchronization updating method according to claim 1, characterized in that: The process of obtaining the target modification record list includes: In the process of continuous modification of the parent model, generating a primary modification record list of the parent model based on the modification data of the parent model; After the modification of the parent model is completed, the primary modification record list is integrated to obtain a modification record list after the first integration; Based on the modification record list after the first integration, the target modification record list is obtained.

3. The model synchronization updating method according to claim 2, characterized in that: The step of obtaining the target modification record list based on the modification record list after the first integration includes: In the case where the child model has a modification record list stored by the parent model last time, the modification record list after the first integration and the final modification record list based on the last model synchronization update process stored by the parent model last time are integrated to obtain a modification record list after the second integration; The modification record list after the second integration is used as the target modification record list.

4. The model synchronization updating method according to claim 1, characterized in that: The model synchronization updating method further comprises: In the case that there is a grandchild model under the child model, a modification record list of the child model shall be formed inside the child model based on each item of data updated by the child model.

5. A model synchronization updating device, characterized in that: include: An acquisition module, used for acquiring data to be synchronized of a model to be synchronized; wherein the model to be synchronized includes a parent model and its subordinate child models; the data to be synchronized includes a target modification record list of the child model, and the target modification record list includes the modification type of the parent model and its corresponding modification object parameter, and the modification object parameter includes at least one of a module ID, a port ID and a stream ID; A polling judgment module, used for polling the target modification record list, and judging whether each record item in the target modification record list conflicts with the existing configuration of the sub-level model; The output processing module is used to further determine whether the conflict is a conflict that can be handled by agreement if there is a conflict; if it is not, output an error message; if it is yes, perform agreed processing on the modification type of the corresponding parent model and its corresponding modification object parameters according to the corresponding processing method of the conflict that can be handled by agreement; The updating module is used to update the modification type and the corresponding modification object parameters of the corresponding parent model to the child model if there is no conflict.

6. The model synchronization updating device according to claim 5, characterized in that: The acquisition module is specifically used to: generate a primary modification record list of the parent model based on the modification data of the parent model during the continuous modification of the parent model; after the modification of the parent model is completed, record and integrate the primary modification record list to obtain a modification record list after the first integration; Based on the modification record list after the first integration, the target modification record list is obtained.

7. The model synchronization updating device according to claim 6, characterized in that: The acquisition module is specifically used to: when the child model has a modification record list stored by the parent model last time, record and integrate the modification record list after the first integration and the final modification record list based on the last model synchronization update process stored by the parent model last time, to obtain a modification record list after the second integration; The modification record list after the second integration is used as the target modification record list.

8. The model synchronization updating device according to claim 5, characterized in that: The model synchronization updating device further comprises: A list forming module is used to form a modification record list of the child model within the child model based on each item of data updated by the child model when there is a grandchild model under the child model.

9. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the model synchronization updating method as described in any one of claims 1 to 4 is executed.

10. An electronic device comprising a processor, a memory and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the model synchronization update method as described in any one of claims 1-4.

Images