JP7625149B2 - Module processing method, device and storage medium for use in foreground/background separation system - Google Patents

Description

The present invention relates to the field of computer technology, and in particular to a module processing method, device, and storage medium for use in a foreground/background separation system.

A separate foreground/background system is one in which the foreground and background are independent of each other. The foreground may refer to the interface layer, and the background may refer to the functionality layer.

The foreground is used to provide an interactive interface that displays a flowchart containing multiple modules and allows the user to trigger operations on specific modules.

The background is used to perform the data logic functions corresponding to the operation and provide data storage functions.

After a user triggers an operation on a module in the foreground, there are often scenarios where the user needs to cancel the operation or re-run the operation after canceling it.

In the above scenario, how to undo or redo the operation may involve synchronization of foreground and background data, so there is a need to consider a module processing method for use in a separate foreground/background system that allows users to undo or redo operations on modules in the separate foreground/background system.

Embodiments of the present invention provide a module processing method, device, and storage medium for use in a foreground/background separation system, and can realize the undo or redo of a user operation in the foreground/background separation system.

According to a first aspect, there is provided a module processing method for a foreground/background separation system, the foreground/background separation system including a foreground and a background, an interactive interface is displayed in the foreground, the interactive interface is used to display a plurality of modules, a data center is disposed in the background, the data center is used to store module data of each of the plurality of modules, the module data includes a display method of the module, function data of the module, and a logical relationship between the module and each of the other modules;
In response to a target operation on a target module, the foreground controls the background to update data corresponding to the target module in the data center based on the target operation, and the foreground updates the interactive interface based on the data corresponding to the updated target module, the target module being one or more of the multiple modules;
When a cancellation command for the target operation is detected, the foreground controls the background to restore the data corresponding to the target module in the data center based on the cancellation command, and the foreground updates the interactive interface based on the data corresponding to the target module after restoration.

According to a second aspect, there is provided a module processing device for use in a foreground/background separation system, the foreground/background separation system including a foreground and a background, an interactive interface is displayed in the foreground, the interactive interface is used to display a plurality of modules, a data center is disposed in the background, the data center is used to store module data of each of the plurality of modules, the module data includes a display method of the module, function data of the module, and a logical relationship between the module and each of the other modules;
a first control module for, in response to a target operation on a target module, controlling the foreground to control the background to update data corresponding to the target module in the data center based on the target operation, and foreground to update the interactive interface based on the data corresponding to the updated target module, the target module being one or more of the plurality of modules;
A module processing device for use in a foreground and background separation system is provided, the module processing device including: when a cancellation command for the target operation is detected, a second control module for causing the foreground to control the background to restore the data corresponding to the target module in the data center based on the cancellation command, and for causing the foreground to update the interactive interface based on the data corresponding to the restored target module.

According to a third aspect, there is provided a method for controlling a multi-threaded data transfer system comprising:
a memory for storing processor executable instructions, said memory comprising:
There is provided a module processing device for use in a foreground/background separation system, wherein the processor is configured to execute any of the steps of the module processing method for use in a foreground/background separation system provided by the first aspect above.

According to a fourth aspect, there is provided a computer-readable storage medium having instructions stored therein, the instructions being executed by a processor to perform any of the steps in the module processing method for use in the foreground/background separation system provided by the first aspect.

According to a fifth aspect, there is provided a computer program product including instructions which, when executed on a computer, cause the computer to perform any of the steps of a module processing method for use in a foreground/background separation system provided by the first aspect above.

The beneficial effects of the technical solutions provided by the embodiments of the present invention include at least the following:

In the foreground and background separation system provided by the embodiment of the present invention, the module data stored in the data center of the background includes the display manner of the module, the function data of the module, and the logical relationship between the modules, that is, the foreground data and the background data are stored simultaneously in the background. As can be seen, in the embodiment of the present invention, the background functions as the data center of all data. In this way, when the foreground detects a target operation on a target module, it controls the background to update the foreground and background data, and when the target operation is canceled, it controls the background to update the foreground and background data in the same way, thereby ensuring the consistency between the content displayed on the foreground interactive interface during the execution of the target operation or the cancellation of the target operation, and the foreground and background data.
In order to more clearly describe the technical solutions in the embodiments of the present invention, the following will briefly describe the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative efforts.

1 is a schematic architecture diagram of a foreground and background separation system provided by an embodiment of the present invention; 4 is a flow chart of a module processing method for a foreground and background separation system provided by an embodiment of the present invention. FIG. 2 is a schematic diagram of a flow chart provided by an embodiment of the present invention. FIG. 4 is a schematic diagram of another flow chart provided by an embodiment of the present invention. FIG. 2 is a schematic diagram of a module deletion provided by an embodiment of the present invention; 4 is a flow chart of a module processing method for another foreground and background separation system provided by an embodiment of the present invention. FIG. 2 is a structural schematic diagram of a module processing device used in the foreground and background separation system provided by an embodiment of the present invention; FIG. 2 is a structural schematic diagram of a terminal provided according to an embodiment of the present invention; FIG. 2 is a structural schematic diagram of a server provided by an embodiment of the present invention;

To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be described in more detail below with reference to the drawings.

In a foreground/background separation system, the foreground is used to display the software interface and provide an interactive interface that the user can operate, while the background provides specific functional logic and recorded data. Typical C/S (client/server) and B/S (browser/server) systems both belong to the foreground/background separation system.

Currently, in the machine vision industry or other industries, several different functional modules (functional modules are also called functional units) are extracted in advance, and a certain combination function is realized by combining these functional modules. The process of arranging the functional modules in a certain order and setting the relationships between them is process setting. The software that provides the process setting function is a process setting system. Considering that the interactive interface provided by the foreground of the process setting system is usually a graphical flowchart, the process setting system is also called a graphical process setting system.

The process setting system is a typical foreground and background separation system. The module processing method provided by the embodiment of the present invention may be applied to the process setting system. Optionally, the module processing method provided by the embodiment of the present invention may also be applied to other foreground and background separation systems, and the embodiment of the present invention is not limited in this regard.

To facilitate the following discussion, we will briefly explain two concepts related to the embodiments of the present invention.

Undo: When a user interacts with a software system, it is up to the user's needs to restore the state of the software to the state before the last operation, which is a single undo. Undo can be serialized, i.e., multiple undos can be performed to restore the state before multiple operations.

Redo: The opposite of undo, if the software has reached a certain state through undo, redo is to advance the software state to the state before the last undo, at the user's request. Redo can also be serialized, i.e. redo multiple times to restore the state before multiple undos.

The purpose of Undo or Redo is to reset the state of the software to the state it was in after any operation between the last operation and the previous N operations, i.e. to give the user a chance to undo their actions.

In a foreground/background separated system, the foreground provides an interactive interface that users can operate, and the background provides data logic functions and storage. In such a system, how to realize undo or redo while ensuring synchronization of foreground and background data, and how to realize undo or redo of user-triggered operations when the process configuration system allows a change in a single functional module to cause changes in multiple functional modules are all hot topics of current research. The module processing method provided by the embodiment of the present invention can realize the above two techniques, and the specific implementation method will be described in detail in the subsequent embodiment.

Figure 1 is an architectural schematic diagram of a foreground and background separation system provided by an embodiment of the present invention. As shown in Figure 1, the foreground and background separation system includes a foreground and a background.

Here, the interactive interface provided by the foreground displays module 1 and module 2, and the connection relationship between module 1 and module 2. At the same time, module 1 is displayed based on a specific display manner, and module 2 is also displayed based on a specific display manner. FIG. 1 illustrates the display manner of module 2, which specifically includes that the position coordinates of the upper left corner of module 2 are (200, 300), the height of module 2 is 30, the width of module 2 is 90, and the color of module 2 is orange.

The display methods of the above modules 1 and 2 may be called foreground data. Here, the foreground data is also called interface data.

The background provides the concrete logical functions. As shown in Figure 1, the following codes are stored in the background:
(Process 0:
Functional data of module 1 Functional data of module 2 Connection relationship: module 1 points to module 2).

What this code means is that what is displayed in the foreground is one flowchart, which contains two functional modules, module 1 and module 2, and the connection is that module 1 points to module 2, i.e. the output of module 1 is the input of module 2.

The function data of module 1 in the above code indicates the internal execution logic of module 1, which is used to indicate how to obtain the output of module 1 based on the input of module 1. The function data of module 2 indicates the internal execution logic of module 2, which is used to indicate how to obtain the output of module 2 based on the input of module 2. The above code is usually called background data, that is, in the embodiment of the present invention, the background data indicates the function data of each module among the multiple modules displayed in the foreground interactive interface and the logical relationship between the multiple modules. Here, the background data is also called underlying data, and the background is also called the underlying layer.

As shown in Figure 1, two modules are placed in the foreground interactive interface, where the upper left corner of module 2 is at coordinates (200, 300), the width is 90, the height is 30, and the color is orange. The background stores the logical relationships between the modules and the function data of each module. If module 2 is deleted, for the background, not only will the function data of module 2 be reduced from the background data, but one connection relationship will also be reduced. When performing the undo operation, in addition to needing to restore the function data of module 2 and the connection relationship between module 2 and module 1 in the background, the position, length, width, and color in the foreground interactive interface must also be restored to fully restore the state before the delete operation.

In such a scenario, if the foreground data is stored in the foreground and the background data is stored in the background, when canceling the delete operation, the foreground data and the functional data and the logical relationship must be restored in the foreground and in the background, respectively, which is likely to cause inconsistency between the foreground and background data. Therefore, in the embodiment of the present invention, all data is set to be stored in a single center, which is the background. In this way, the foreground data is also stored in the background, and when canceling, the data stored in the background is restored, and the foreground retrieves the foreground data from the background. That is, the foreground is only used to retrieve and display the foreground data from the background, and does not store data, which solves the problem that data inconsistency may occur. In the embodiment of the present invention, since both the foreground data and the background data are stored in the background, for the convenience of the following explanation, the data stored in the background is collectively referred to as module data. That is, the module data includes foreground data and background data. Specifically, the module data of any module includes the display method of the module, the functional data of the module, and the logical relationship between the module and each of the other modules.

Note that the foreground/background separation system shown in FIG. 1 is merely an example and does not limit the foreground/background separation system according to an embodiment of the present invention.

Figure 2 is a flow chart of a module processing method for a foreground/background separation system provided by an embodiment of the present invention. The method is applied to a foreground/background separation system including a foreground and a background. An interactive interface is displayed in the foreground, and the interactive interface is used to display a plurality of modules. A data center is disposed in the background, and the data center is used to store module data of each module among the plurality of modules, and the module data of any module includes a display method of the module, function data of the module, and a logical relationship between the module and each of the other modules. Specifically, as shown in Figure 2, the method includes the following steps:

In step 201, in response to a target operation on the target module, the foreground controls the background to update data corresponding to the target module in the data center based on the target operation, and the foreground updates the interactive interface based on the updated data corresponding to the target module, the target module being one or more modules among the multiple modules, and the target operation being any operation on the target module.

Here, the data corresponding to the target module includes the module data of the target module in the data center and data related to the target module in the module data of other modules, which will be described in more detail later and will not be described here.

The above-mentioned target operation may be a delete operation on the target module, an add operation on the target module, or a change operation on an attribute of the target module, such as its display color. Here, the delete operation specifically refers to deleting a target module displayed in the interactive interface, and the add operation specifically refers to adding a target module to the interactive interface.

Exemplarily, when the target operation is a delete operation on the target module, step 201 specifically refers to controlling the foreground to delete the module data of the target module in the data center and the data related to the target module in the module data of other modules based on the target operation, and redisplaying the interactive interface based on the data center from which the data is deleted.

As another example, when the target operation is an add operation for a target module, step 201 specifically refers to controlling the foreground to add module data of the target module to a data center and add data related to the target module to the module data of other modules based on the target operation, and redisplaying the interactive interface based on the data center to which the data is added.

In one possible embodiment, the interactive interface displays a module remove control and a module add control, and when the foreground detects a user selection operation on the module remove control and module add control, it may determine that a target operation on a target module has been detected, at which point the target operation can be executed by step 201.

After detecting the target operation, the foreground controls the background based on the target operation to update the data corresponding to the target module in the data center, and updates the interactive interface based on the updated data corresponding to the target module in the data center, thereby achieving consistency of the interactive interface, foreground and background data.

The data corresponding to the target module includes module data of the target module and data related to the target module in the module data of the other modules. Here, the module data of the target module includes functional data of the target module, a display method of the target module, and a logical relationship between the target module and each other module. The functional data of the target module indicates the internal execution logic of the target module, and the internal execution logic indicates how to obtain an output of the target module based on an input of the target module. The display method of the target module includes, for example, a display position, a display size, a display color, etc. of the target module. The data related to the target module in the module data of each other module includes a logical relationship between the other module and the target module.

In one possible embodiment, the logical relationship between the goal module and each other module includes a connection relationship between the goal module and the other modules. The connection relationship indicates a connection line relationship between the goal module and the other modules on the interactive interface, and the connection line relationship specifically indicates the execution order between the goal module and the other modules in the execution process of the flowchart. For example, if the goal module is module 1 shown in FIG. 1 and the other module is module 2, the connection relationship between the goal module and the other modules may indicate that the internal execution logic of module 1 is executed first, and then the internal execution logic of module 2 is executed.

Figure 3 is a schematic diagram of a flowchart provided by an embodiment of the present invention. When the foreground and background separation system is a process setting system, the flowchart seen in the foreground is usually shown in Figure 3. The connection relationship between each module in the flowchart shown in Figure 3 represents only the execution order, and there is data exchange between modules, and the output of the previous module must participate in the operation as the input or parameter of the subsequent module, otherwise this process is meaningless. When inputs and outputs and parameters of the modules themselves are added, the actual flowchart will be more complicated than the flowchart shown in Figure 3.

Figure 4 is a schematic diagram of another flowchart provided by an embodiment of the present invention. As shown in Figure 4, in addition to the connection relationships between modules, there are subscription relationships between internal complex parameters, inputs, and outputs. For example, the internal parameters of a module may be the output of a previous module in the execution order, and the output of the module may be the internal parameters of a next module in the execution order, or the output of a module may be the input of a next module in the execution order. That is, a module may subscribe to the input or output of a previous module. Therefore, a flowchart is a very complex unidirectional network. When a module is deleted, it not only affects the module itself, but also affects the subscription relationships between all subsequent modules in the flowchart and it and its predecessor modules.

Thus, in another possible embodiment, the logical relationship between the goal module and each other module may further include a subscription relationship between the goal module and the other module in addition to the connection relationship between the goal module and the other module. The subscription relationship indicates an association relationship between at least one of the internal parameters, inputs of the goal module and the output of the other module, and/or an association relationship between the output of the goal module and at least one of the internal parameters, inputs of the other module, and/or an association relationship between the input of the goal module and the output of the other module.

That is, in an embodiment of the present invention, for any module, the logical relationship between the module and the other module includes a connection relationship between the module and the other module, and a subscription relationship between the module and the other module. The connection relationship indicates a connection line relationship between the module and the other module on a display interface. The subscription relationship indicates an association relationship between an internal parameter of the module and an output of the other module, and/or an association relationship between an output of the module and an input of the other module, and/or an association relationship between an input of the module and an output of the other module. That is, the subscription relationship indicates an association relationship between at least one of the internal parameters or inputs of the module and the output of the other module, and/or an association relationship between the output of the module and at least one of the internal parameters or inputs of the other module.

Note that the number of internal parameters of each module may be one or more. Also, the number of outputs of each module may be one or more, and the number of inputs of each module may be one or more. The above-mentioned association relationship is a higher-level association relationship, and may include an association relationship between one specific parameter and another specific parameter, or may include an association relationship between each of the multiple parameters and another parameter. For example, the association relationship between the internal parameter of the target module and the output of the other module may be that one output of another module is one internal parameter of the target module, or that two outputs of another module are two internal parameters of the target module, or that one output of each of the two other modules is one of the two internal parameters of the target module. The above is merely an example, and does not limit the association relationship according to the embodiment of the present invention.

In step 202, if a cancel command for the target operation is detected, the foreground controls the background to restore data corresponding to the target module in the data center based on the cancel command, and the foreground updates the interactive interface based on the data corresponding to the restored target module.

In one possible embodiment, the interactive interface displays an undo operation control, and when the foreground detects a user selection operation on the undo operation control, it may determine that an undo command for the target operation has been detected, in which case an undo process for the target operation may be performed by step 202.

When the target operation is a delete operation for the target module, the above step 202 specifically refers to the foreground controlling the background to re-add the data corresponding to the target module to the data center based on the cancellation command.

When the target operation is an add operation to the target module, the above step 202 specifically refers to the foreground controlling the background to delete the data corresponding to the target module from the data center based on the cancellation command.

In an embodiment of the present invention, step 201 and step 202 may be specifically foreground-centered or background-centered. Here, foreground-centered refers to recording each specific operation that executes the target operation in the foreground, and background-centered refers to recording each specific operation that executes the target operation in the background; in other words, the difference between the two is whether the file that records the specific operation is saved in the foreground or background. Below, the two implementation methods will be explained separately.

(1) Focus on the foreground

In this case, the implementation process of step 201 above may involve the foreground sending one or more first data update commands to the background based on the target operation, any one of the one or more first data update commands being used to instruct the background to update a portion of the data corresponding to the target module, and the foreground generating an operation record based on the sending of the one or more first data update commands.

For example, if the target operation is a module deletion or a module addition, the foreground sends a first logical relationship update command and a first module update command to the background, and generates an operation record for sending the first logical relationship update command and the first module update command. The first logical relationship update command is used to instruct the background to update the logical relationship between the other modules and the target module in the module data of each other module in the data center based on the target operation, and the first module update command is used to instruct the background to update the module data of the target module in the data center based on the target operation.

The operation record is used to indicate the order in which each first data update command was sent and the data change status indicated by each command.

In this case, the realization process of step 202 above may be such that the foreground sends one or more second data update instructions to the background based on the inverse operation of the target operation instructed by the operation record, and any one of the one or more second data update instructions is used to instruct the background to restore the logical relationship between the other module and the target module in the module data of each other module to the state before the target operation was executed, or to restore the module data of the target module to the state before the target operation was executed.

For example, in a scenario where the target operation is a module deletion or a module addition, the foreground sends a second logical relationship update command and a second module update command to the background based on the inverse operation of the target operation indicated by the operation record. The second logical relationship update command is used to instruct the background to restore the logical relationship between the target module and each other module in the module data of the other modules in the data center to the state before the target operation was executed, and the second module update command is used to instruct the background to restore the module data of the target module in the data center to the state before the target operation was executed, so that the foreground can then obtain data corresponding to the updated target module from the background and update the interactive interface based on the data corresponding to the updated target module.

Specifically, when the target operation is a delete operation on the target module, when executing the target operation, the foreground first sends a first logical relationship update command to the background, and then sends a first module update command. In this way, the background can be controlled to first delete the logical relationship between the target module and the other modules in the module data of each other module, and then delete the module data of the target module, and generate an operation record of first sending the first logical relationship update command and then sending the first module update command. When canceling the target operation, based on the reverse operation of the target operation indicated by the operation record, the foreground first sends a second module update command to the background, and then sends a second logical relationship update command. In this way, the background can be controlled to first restore the module data of the target module in the data center, and then restore the logical relationship between the target module and the other modules in the module data of each other module.

Similarly, if the target operation is an add operation for the target module, when executing the target operation, the foreground first sends a first module update command to the background, and then sends a first logical relationship update command. In this way, the background can be controlled to first add module data of the target module to the data center, and then add logical relationships between the target module and the other modules to the module data of each other module in the data center, and generate an operation record that first sends a first module update command and then sends a first logical relationship update command. When canceling the target operation, based on the reverse operation of the target operation indicated by the operation record, the foreground first sends a second logical relationship update command to the background, and then sends a second module update command. In this way, the background can be controlled to first delete the logical relationships between the target module and the other modules in the module data of each other module in the data center, and then delete the module data of the target module in the data center.

The purpose of sending commands in the above order is to allow the foreground to cancel the target operation based entirely on the inverse of the target operation, avoiding the inability to return to the state before the target operation was executed.

For example, if the target operation is a delete operation on module 2 shown in FIG. 1, the specific process of steps 201 and 202, centered on the foreground, is as follows:

When performing a target operation, several processes are involved:

1) The foreground sends a module data acquisition command to the background, and the foreground receives data corresponding to the target module sent from the background, and the data corresponding to the target module includes the module data of the target module and data related to the target module in the module data of each other module.

2) The foreground analyzes the acquired data corresponding to the target module, and determines that in order to delete the target module, it is necessary to first delete the logical relationship between the target module and the other modules in the module data of each other module, and then delete the module data of the target module. Based on the analysis result, the foreground sends a connection line deletion command to the background, i.e., sends the above-mentioned first logical relationship update command to instruct the background to delete the logical relationship between the target module and the other modules in the module data of the other modules in the data center, and generates an operation record corresponding to the sending of the first logical relationship update command, and for the convenience of the following description, the operation record is referred to as the first operation record. Here, when deleting the logical relationship, the background first backs up the connection data related to the target module to another storage location, i.e., backs up the logical relationship between the target module and each other module, and then deletes the connection data related to the target module in the background data, so that the deleted data can be quickly restored later.

3) The foreground sends a module deletion command to the background, i.e., sends the above-mentioned first module update command to instruct the background to delete the module data of the target module, and generates an operation record corresponding to the sending of the first module update command, which is referred to as a second operation record for the convenience of the following explanation. Here, when deleting the module data of the target module, the background backs up the module data of the target module to another memory location and then deletes the module data of the target module in the background data, so that the deleted data can be quickly restored later.

Canceling a target operation involves several processes:

1) Because the first operation record is generated before the second operation record, in order to realize the inverse operation of the above target operation, the foreground first sends a module import command to the background based on the second operation record, i.e., sends the above second module update command, instructing the background to add the module data of the target module to the data center.

2) Then, based on the first operation record, the foreground sends a connection establishment command between module 1 and module 2 to the background, i.e., sends the second logical relationship update command described above, instructing the background to add a logical relationship between the target module and each of the other modules to the module data of the other modules in the data center.

3) The foreground retrieves from the background module interface data, which is the display format of the goal module in the module data of the goal module, and redisplays the goal module in the interactive interface based on the retrieved display format.

The entire process above is driven by the foreground, with the background responding passively and providing the basic interface for data acquisition and import.

Currently, sending a command from the foreground to the background is realized by invoking an interface of the background, that is, the background provides a set of interfaces. When the foreground needs to send a command, it calls an interface of the background to send the command and controls the background to perform a specific operation. For example, the background provides a logical relationship deletion interface and a module deletion interface. In such a scenario, if the target operation is module deletion, the first logical relationship update command sent from the foreground to the background can be realized by invoking the logical relationship deletion interface, and the first module update command sent from the foreground to the background can be realized by invoking the module deletion interface.

In the above foreground-centric implementation method, the foreground is the one that knows best about the specific operation procedures and scope of impact, while the background only provides an interface and does not need to be involved in specific tasks, making the system more stable during the cancellation process.

(2) Focus on the background

In this case, the implementation process of the above step 201 may be that the foreground updates the interactive interface based on the target operation, and the foreground sends an update command to the background, which is used to instruct the background to update the logical relationship between the other modules and the target module in the module data of each other module in the data center based on the target operation, and the module data of the target module in the data center. At the same time, the background generates an operation record corresponding to each of the above operations.

Accordingly, the implementation process of the above step 202 may be that the foreground sends a restoration command to the background, and the restoration command is used to instruct the background to restore the logical relationship between the other modules in the module data of each other module in the data center and the target module, and the module data of the target module in the data center, to a state before the target operation is executed, based on the inverse operation of the target operation instructed by the locally stored operation record. The foreground obtains the display method in the module data of the target module after the update from the background, and updates the interactive interface based on the updated display method.

For example, if the target operation is a delete operation on module 2 shown in FIG. 1, the specific process of steps 201 and 202, focusing on the background, is as follows:

When performing a target operation, several processes are involved:

1) When the foreground detects a module cleanup command, it first deletes the target module on the interactive interface, and then sends a module deletion command including the identifier of the target module to the background.

2) After receiving a module deletion command, the background first backs up the connection data related to the target module in the module data of each other module to another storage location, then deletes the connection data related to the target module in the module data of each other module in the data center, generates an operation record corresponding to the deletion operation of the connection data, and marks it as a third operation record. Here, the connection data related to the target module in the module data of each other module indicates the logical relationship between the target module and the other module.

3) The background backs up the module data of the target module to another storage location, deletes the module data of the target module in the data center, generates an operation record corresponding to the deletion operation of the module data, and marks it as the fourth operation record.

When cancelling a target operation, several processes are involved:

1) The foreground sends a cancel command to the background.

2) The background queries the operation records, and based on the fourth operation record, determines that the last operation is to delete the module data of the module, and performs the inverse operation of deleting the module data of the module, i.e., imports the module data of the target module from the backed up data to the data center.

3) The background queries the operation records, and based on the third operation records, determines that the operation before deleting the module data is to delete the module connection data, and performs the reverse operation of deleting the module connection data, i.e., adds the connection data related to the target module in the module data of each other module from the backed up data to the data center.

4) The background notifies the foreground that the cancellation is complete, and the foreground retrieves the latest target module display state from the background and updates the interactive interface.

The whole process is driven by commands sent from the foreground, and the background provides all data recording and reverse operations to realize data deletion and restoration. The foreground queries and updates data. In addition, in the above foreground-centric implementation method, the foreground is most familiar with the specific operation procedures and scope of impact, which is convenient for developers to always grasp and control the actual processing status of the target operation. Therefore, when an embodiment of the present invention is applied, it is preferable to adopt the foreground-centric implementation method.

In addition, there are various possible methods for actually deleting the data corresponding to the above-mentioned target module. As shown in Figure 4, the actual flowchart is very complicated. In this case, when the target operation is a delete operation on the target module, there are two types of policies for the scenario of performing a relatively complicated delete and then canceling it in order to deal with the cancellation and redoing in such a complicated relationship.

1) Temporary deletion policy. When deleting a target module based on a target operation, the module data of the target module is only marked for deletion, but is not actually deleted, and the logical relationships between each other module and the deleted target module are cleaned up. When canceling the target operation, the deletion mark is removed, and the logical relationships between each other module in the data center and the target module are restored.

That is, in the provisional deletion policy, a specific implementation method in which the foreground sequentially sends one or more first data update commands to the background based on the target operation may be that the foreground first sends a first logical relationship update command to the background, then sends a first module update command, and then when the background receives the first logical relationship update command, the background deletes the logical relationship between the other module and the target module in the module data of each other module, and when the background receives the first module update command, a deletion mark is added to the module data of the target module in the data center.

Accordingly, a specific implementation manner of the foreground sequentially sending one or more second data update commands to the background based on the inverse operation of the target operation instructed by the operation record may be that the foreground first sends a second module update command to the background, and then sends a second logical relationship update command based on the inverse operation of the target operation instructed by the operation record, and when the background receives the second module update command, it deletes the deletion mark in the module data of the target module, and when the background receives the second logical relationship update command, it adds the logical relationship between the other module and the target module to the module data of each of the other modules.

2) Export-import policy. When deleting a goal module based on a goal operation, export the data corresponding to the goal module, and then clean up the data corresponding to the goal module. When canceling, import the module data of the goal module, and restore the connection and subscription relationship between each other module and the goal module based on the previously exported data. That is, when deleting data, export the related data first, and then directly delete the related data in the data center.

That is, in the export-import policy, a specific implementation manner in which the foreground sequentially sends one or more first data update commands to the background based on the target operation may be that the foreground first sends a first logical relationship update command to the background, and then sends a first module update command, so that the background first deletes the logical relationship between the target module and the other modules in the module data of each other module in the data center, and then deletes the module data of the target module.

Accordingly, a specific implementation method of the foreground sequentially sending one or more second data update commands to the background based on the inverse operation of the target operation instructed by the operation record may be to control the foreground to first send a second module update command to the background and then send a second logical relationship update command based on the inverse operation of the target operation instructed by the operation record, so that the background first restores the module data of the target module in the data center, and then restores the logical relationship between the target module and the other modules in the module data of each of the other modules.

In addition, in the above temporary deletion policy, in order to synchronize foreground and background data, if the foreground and background only delete marks after deleting one module, special processing must be performed on the mark deletion module to ignore it and not trigger execution when executing the entire flowchart. If such special data becomes too large, it will affect the maintainability of the foreground and background data and cause instability. Therefore, when an embodiment of the present invention is applied, it is preferable to adopt an export/import policy to delete the target module.

In addition, in the above export-import policy, in order to facilitate rapid restoration of deleted data later, the foreground may first send a first logical relationship update command to the background, and then before sending the first module update command, the foreground may control the background to export data corresponding to the target module in the data center and back it up to a reference storage location. After this, the foreground first sends a second module update command to the background, and then after sending the second logical relationship update command, in response to the received second module update command, the background imports the module data of the target module from the reference storage location to the data center, and in response to the received second logical relationship update command, the background imports the logical relationships between the target module and each of the other modules from the reference storage location to the data center.

In addition, in an embodiment of the present invention, when the target operation is a module deletion operation, the same target operation may be performed simultaneously on multiple modules, i.e., a scenario exists in which a bulk deletion operation is performed. When a bulk deletion operation is performed, the number of target modules in steps 201 and 202 is multiple.

In such a scenario, there may be two policies to achieve the execution and cancellation of the target operations: one is operation-centric and the other is data-centric.

First policy: Focus on operations.

Here, operation-centric refers to dividing a target operation into multiple sub-operations for a single module when executing a target operation for multiple target modules; that is, each sub-operation is for only one module, and the target operation for multiple target modules is realized by sequentially executing the multiple sub-operations according to the execution order of the multiple sub-operations. When executing target operations for multiple target modules, each time a sub-operation is executed, an operation record for that sub-operation is generated and stored. When canceling a target operation for multiple target modules, the cancellation is completed by following the reverse operation of the sub-operation indicated by the stored operation record.

In the operation-centric policy, the specific implementation manner in which the foreground first sends the first logical relationship update command to the background is as follows: the foreground sends a subscription relationship deletion command A to the background, and the subscription relationship deletion command A is used to instruct the background to delete the subscription relationships between the post-execution module and each of the post-execution module and the target module, the post-execution module being a module executed after the target module in the flowchart displayed in the foreground, and the pre-execution module being a module executed before the target module in the flowchart; the foreground sends a subscription relationship deletion command B to the background, and the subscription relationship deletion command B is used to instruct the background to delete the subscription relationships between multiple target modules; The foreground may send a subscription relationship deletion command C to the background, which is used to instruct the background to delete the subscription relationship between each goal module and the previous execution module, the foreground may send a connection relationship deletion command A to the background, which is used to instruct the background to delete the connection relationship between the next execution module and each of the goal modules, the foreground may send a connection relationship deletion command B to the background, which is used to instruct the background to delete the connection relationship between multiple goal modules, and the foreground may send a connection relationship deletion command C to the background, which is used to instruct the background to delete the connection relationship between each goal module and the previous execution module.

After sending the first logical relationship update command in the above implementation method, the foreground sends a first module update command to the background, controlling the background to delete remaining data in the module data of each of the multiple target modules.

In other words, in the operation-centric policy, the foreground first analyzes the subscription relationships and connection line relationships between multiple target modules and between each target module and each other module among the multiple target modules, deletes these subscription relationships and connection line relationships by multiple first logical relationship update commands, and then deletes the module data of each target module.

Second policy: Data is at the center.

Data-centric means that when executing a target operation on multiple target modules, the multiple target modules are treated as a whole, and if it is necessary to delete the multiple target modules at this time, the module data of the multiple target modules is deleted as a whole, and then the logical relationships between the edge target modules and other modules in the multiple target modules are updated. An edge target module is a target module among the multiple target modules that has a logical relationship with other modules. An operation record is generated in the same way when updating the module data and the logical relationships, and when canceling a target operation on the multiple target modules, the cancellation is completed by following the reverse operation of the target operation instructed by the stored operation record.

In the data-centric policy, the specific implementation manner of the foreground first sending the first logical relationship update command to the background and then sending the first module update command may be: the foreground sending the first subscription relationship delete command to the background, the first subscription relationship delete command is used to instruct the background to delete the subscription relationship between the other module and the edge target module in the module data of each other module; the foreground sending the first connection relationship delete command to the background, the first connection relationship delete command is used to instruct the background to delete the connection relationship between the other module and the edge target module in the module data of each other module; the foreground sending the first module delete command to the background, the first module delete command is used to instruct the background to delete the module data of multiple target modules.

In other words, in the data-centric policy, the foreground analyzes the subscription relationships and connection line relationships between edge target modules and other modules in multiple target modules, deletes these subscription relationships and connection line relationships through multiple first logical relationship update commands, and then deletes the module data of each target module. Since there is no need to delete the subscription relationships or connection line relationships inside each target module one by one, the time required for target operations is saved.

Figure 5 is a schematic diagram of deleting a module provided by an embodiment of the present invention, which applies to a delete operation, canceling an add operation, redoing a delete operation, etc. As shown in Figure 5, there are two types of policies when deleting modules 2 to 5 in the flowchart.

1. Focusing on the operation, we break down the bulk operation into a combination of sub-operations for a single module, and each sub-operation is specifically as follows:

1) Delete the subscription relationships between modules 6 to 10 and modules 1 to 5 in order, i.e., delete the subscription relationships between each of modules 6 to 10 and each of modules 1 to 5.

2) Delete the subscription relationships between modules 3-5 and modules 1-2 in sequence, i.e., delete the subscription relationships between each of modules 3-5 and each of modules 1-2.

3) Delete the subscription relationship between module 2 and module 1.

4) Sequentially delete the connection lines between modules 6 and 3, between modules 7 and 4, and between modules 8 and 5, i.e., delete the connection between modules 6 and 3, between modules 7 and 4, and between modules 8 and 5.

5) Sequentially delete the connection lines between modules 3 to 5 and module 2, i.e., delete the connection relationships between each of modules 3 to 5 and module 2.

6) Delete the connection line between module 2 and module 1, i.e., delete the connection relationship between module 2 and module 1.

7) Delete modules 3 to 5 in sequence, i.e., delete the module data for each of modules 3 to 5.

8) Delete module 2, i.e., delete the module data for module 2.

When canceling, execute steps 8) to 1) in the reverse order to add module data, connection relationships, and subscription relationships one by one, thereby canceling the deletion operations for modules 2 to 5.

Second, a data-centric bulk import/export policy.

1) Collect the module data from modules 2 to 5 in the data center, export it, and back it up to a reference location.

2) In the module data of modules 6-10, the subscription relationships between modules 1-5 are deleted, and an operation record is generated. That is, modules 6-10 are treated as a whole, and modules 1-5 are also treated as a whole, and in the module data of all modules 6-10, the subscription relationships between modules 1-5 as a whole are deleted, and specifically, these subscription relationships are the subscription relationships between edge modules 3/4/5 in modules 2-5 and the other modules 6-10.

3) Delete the connections between modules 2 to 5 in the module data of other modules, delete the module data of modules 2 to 5, and generate an operation record.

When cancelled

1) Import the module data for modules 2 to 5 all at once.

2) The connection lines between other modules and modules 2 to 5 are restored based on the operation records. Specifically, this includes the connection relationships between modules 2 to 5 in the module data of module 1, and the connection relationships between modules 2 to 5 in the module data of any of modules 6 to 10.

3) The subscription relationships between modules 6-10 and modules 1-5 are restored based on the operation records. Specifically, this includes the subscription relationships between modules 2-5 in the module data of module 1, and the subscription relationships between modules 2-5 in the module data of any of modules 6-10.

In the first policy above, the problem with converting a bulk operation into multiple single operations is that the processing order determines the undo order, and if the order is wrong, an error will occur when restoring the connections if the modules have not been restored yet. Even if everything is restored, the flowchart cannot be fully restored to its previous state because the connections between some modules may be missing. In the second policy above, the bulk import/export policy only needs to record the relationships between the exported whole and its surroundings, and the internal relationships of the exported whole are included in the module data of the exported module. When undoing or redoing, the module data of the module can be imported first, and the surrounding relationships of each other module to the whole can be restored.

Also, in an embodiment of the present invention, the policy centered on the operation of the first policy applies to undo and redo scenarios where the data of a single module is changed. For example, after changing the position or color of a module, performing the reverse operation of the position or color change is the most economical and efficient way.

Thus, in one possible embodiment, when the number of target modules is one, before the foreground sends one or more first data update commands to the background based on the target operation, the foreground may divide the target operation into one or more sub-operations. In this scenario, the one or more first data update commands correspond to one or more sub-operations, respectively, and the background completes the target operation based on the one or more sub-operations. That is, by dividing the target operation into multiple sub-operations, and sequentially executing the multiple sub-operations to generate an operation record, the target operation can then be canceled based on the operation records of the multiple sub-operations.

Optionally, after the undo operation, the user may undo the undo operation, i.e., perform the operation again. In this case, the redo process described above can be realized by step 203 shown in FIG. 6.

In step 203, if a replay command for the target operation is detected, the foreground controls the background to update data corresponding to the target module in the data center based on the target operation, and the foreground updates the interactive interface based on the updated data corresponding to the target module.

The specific implementation method of step 203 is essentially the same as the implementation method of step 201, so a detailed explanation is omitted here.

As described above, in the foreground/background separation system provided by the embodiment of the present invention, the module data stored in the background data center includes the display method of the module, the functional data of the module, and the logical relationship between the modules, i.e., foreground data and background data are stored simultaneously in the background. As can be seen from this, in the embodiment of the present invention, the background functions as a data center for all data. In this way, when the foreground detects a target operation on a target module, it controls the background to update the foreground and background data, and when the target operation is canceled, it controls the background to similarly update the foreground and background data, thereby ensuring the consistency between the content displayed on the foreground interactive interface during the execution of the target operation or the cancellation of the target operation, and the foreground and background data.

The technical effects provided by the embodiments of the present invention are summarized below.

The innovation of the present embodiment is that it proposes some realistic and feasible policies for undoing or redoing a foreground/background separation system.

1) If you have data in both the foreground and background, you can adopt a data single center policy and store all data in the background.

2) If the foreground and background are separate, the foreground may be the center of the operation record. When undoing or redoing, the foreground will lead the entire undo process.

3) For complex and highly interrelated flowcharts, the deletion/cancellation scenario can adopt a data export/import approach instead of a temporary deletion policy.

4) When deleting or canceling data collectively in a complex flowchart with many relationships, you can use the data export/import method instead of the operation combination method.

5) In a flowchart, you can adopt an operation-centric policy for single data changes.

The above policies allow for better undo/redo support for a separate foreground/background system, balancing implementation complexity, memory consumption, and system stability.

All the optional technical solutions described above can be combined in any way to form optional embodiments of the present invention, which will not be described one by one in the embodiments of the present invention.

Figure 7 is a structural schematic diagram of a module processing device used in a foreground/background separation system provided by an embodiment of the present invention, which may be realized by software, hardware, or a combination thereof. The device is applied to a foreground/background separation system including a foreground and a background. An interactive interface is displayed in the foreground, and the interactive interface is used to display a plurality of modules. A data center is disposed in the background, and the data center is used to store module data of each module among the plurality of modules, and the module data of any module includes the display method of the module, the function data of the module, and the logical relationship between the module and each of the other modules.

As shown in FIG. 7, the device 700 includes the following modules:

The first control module 701 is used to, in response to a target operation on a goal module, control the foreground to update the data corresponding to the goal module in the data center based on the target operation, and to cause the foreground to update the interactive interface based on the updated data corresponding to the goal module, the goal module being one or more of the multiple modules, and the target operation being any operation on the goal module.

The second control module 702 is used to, when a cancel command for the target operation is detected, control the foreground to cause the background to restore data corresponding to the target module in the data center based on the cancel command, and to cause the foreground to update the interactive interface based on the data corresponding to the restored target module.

Based on the above device, in one possible embodiment, as shown in FIG. 7, the device further includes a third control module 703 for controlling the foreground to update the data corresponding to the goal module in the data center based on the target operation when a replay command for the goal operation is detected, and for causing the foreground to update the interactive interface based on the updated data corresponding to the goal module.

Based on the above device, in one possible embodiment, the first control module comprises:
causing the foreground to send one or more first data update instructions to the background based on the target operation;
A first data update command is used to instruct the foreground to generate an operation record based on the transmission of the one or more data update commands, and any one of the one or more first data update commands is used to instruct the background to update a part of data corresponding to the target module;
In response, the second control module:
The second data update command is used to cause the foreground to sequentially send one or more second data update commands to the background based on an inverse operation of a target operation instructed by the operation record, and any one of the one or more second data update commands is used to instruct the background to restore a portion of the data corresponding to the target module in the data center to a state before the target operation was executed.

Based on the above device, in one possible embodiment, if the target operation is an add operation for the target module, the first control module:
The foreground is used to make the background first send a first module update command, and then send a first logical relationship update command, so that the background first adds module data of the target module to the data center, and then adds logical relationships between the target module and the other modules to the module data of each other module;
In response, the second control module:
It is used to cause the foreground to first send a second logical relationship update command to the background based on the inverse operation of the target operation instructed by the operation record, and then send a second module update command, so as to control the background to first delete the logical relationship between the target module and the other modules in the module data of each other module in the data center, and then delete the module data of the target module in the data center.

Based on the above device, in one possible embodiment, if the target operation is a delete operation on the target module, the first control module:
The foreground is used to make the background first send a first logical relationship update command, and then send a first module update command, so that the background first deletes the logical relationship between the target module and the other modules in the module data of each other module in the data center, and then deletes the module data of the target module in the data center;
In response, the second control module:
It is used to cause the foreground to first send a second module update command and then send a second logical relationship update command based on the inverse operation of the target operation instructed by the operation record, so as to control the background to first restore the module data of the target module in the data center, and then restore the logical relationships between the target module and the other modules in the module data of each other module.

Based on the above device, in one possible embodiment, if the target operation is a delete operation on the target module, the first control module:
The foreground is used to control the background to first send a first logical relationship update command, and then send a first module update command, so as to delete the logical relationship between the other modules and the target module in the module data of each other module in the data center when the background receives the first logical relationship update command, and to control the background to add a deletion mark to the module data of the target module in the data center when the background receives the first module update command;
In response, the second control module:
This is used to cause the foreground to first send a second module update command and then send a second logical relationship update command based on the inverse operation of the target operation instructed by the operation record, to control the background to delete a deletion mark in the module data of the target module in the data center when the background receives the second module update command, and to control the background to add a logical relationship between the other modules and the target module to the module data of each other module in the data center when the background receives the second logical relationship update command.

Based on the above device, in one possible embodiment, the device further comprises:
an export module for causing the foreground to control the background to first send the first logical relationship update command to the background, and then, before sending the first module update command, to export data corresponding to the target module in the data center and back it up to a reference storage location, the data corresponding to the target module including module data of the target module and logical relationships between the target module and the other modules in the module data of each of the other modules;
The foreground includes an import module for first transmitting the second module update command to the background, and then transmitting the second logical relationship update command, and then, in response to the received second module update command, causing the background to import module data of the target module from the reference memory location to the data center, and, in response to the received second logical relationship update command, causing the background to import the logical relationships between the target module and each of the other modules from the reference memory location to the data center.

Based on the above-mentioned device, in one possible embodiment, the logical relationship between any one of the multiple modules and each of the other modules includes a connection relationship between any one of the multiple modules and each of the other modules, and a subscription relationship between any one of the multiple modules and each of the other modules. The connection relationship indicates a connection line relationship between any one of the multiple modules and each of the other modules on the interactive interface, and the subscription relationship indicates an association relationship between at least one of the internal parameters or inputs of any one of the multiple modules and an output of each of the other modules, and/or an association relationship between the output of any one of the multiple modules and at least one of the internal parameters or inputs of each of the other modules.

Based on the above device, in one possible embodiment, when the number of the target modules is plural, the first control module:
causing the foreground to send a first subscription relationship deletion command to the background;
causing the foreground to transmit a first connection relationship deletion command to the background;
used to cause the foreground to send a first module removal command to the background;
The first subscription relationship deletion command is used to instruct the background to delete a subscription relationship between the other module and an edge target module in the module data of each other module, and the edge target module is a target module among a plurality of target modules that has a logical relationship with the other module;
The first connection relationship deletion command is used to instruct the background to delete a connection relationship between the other module and an edge target module in the module data of each other module;
The first module deletion command is used to instruct the background to delete module data of the plurality of target modules.

Based on the above device, in one possible embodiment, when the number of the target modules is plural, the first control module:
causing the foreground to transmit a subscription deletion command A to the background;
causing the foreground to transmit a subscription deletion command B to the background;
causing the foreground to transmit a subscription deletion command C to the background;
causing the foreground to transmit a connection relationship deletion command A to the background;
causing the foreground to transmit a connection relationship deletion command B to the background;
having the foreground transmit a connection relationship deletion command C to the background;
used to cause the foreground to send a first module removal command to the background;
The subscription relationship deletion command A is used to instruct the background to delete, for each of the target modules, a subscription relationship between a post-execution module and each of the target modules, the post-execution module being a module executed after the target module in a flowchart displayed in the foreground, and the pre-execution module being a module executed before the target module in a flowchart;
The subscription relationship deletion command B is used to instruct the background to delete a subscription relationship between multiple target modules;
The subscription relationship deletion command C is used to instruct the background to delete the subscription relationship between each of the target modules and the previous execution module;
The connection relationship deletion command A is used to instruct the background to delete the connection relationship between the post-execution module and each of the target modules;
the connection relationship deletion command B is used to instruct the background to delete the connection relationships between the plurality of target modules;
The connection relationship deletion command C is used to instruct the background to delete the connection relationship between each of the target modules and the previous execution module;
The first module deletion command is used to instruct to delete remaining data in the module data of the plurality of target modules.

As described above, in the foreground/background separation system provided by the embodiment of the present invention, the module data stored in the background data center includes the display method of the module, the functional data of the module, and the logical relationship between the modules, i.e., foreground data and background data are stored simultaneously in the background. As can be seen from this, in the embodiment of the present invention, the background functions as a data center for all data. In this way, when the foreground detects a target operation on a target module, it controls the background to update the foreground and background data, and when the target operation is canceled, it controls the background to similarly update the foreground and background data, thereby ensuring the consistency between the content displayed on the foreground interactive interface during the execution of the target operation or the cancellation of the target operation, and the foreground and background data.

The module processing device used in the foreground/background separation system provided in the above embodiment is described as an example only of the division of each of the above functional modules when processing operations on the modules. In actual applications, the above functions are assigned to different functional modules as necessary, that is, the internal structure of the device is divided into different functional modules to realize all or part of the above functions. In addition, the module processing device used in the foreground/background separation system provided in the above embodiment and the embodiment of the module processing method used in the foreground/background separation system belong to the same concept, and the specific realization process is described in detail in the embodiment of the method, so the description will be omitted here.

Figure 8 is a structural schematic diagram of a terminal 800 provided by an embodiment of the present invention. The foreground in the above embodiment can be realized by the structure shown in Figure 8. The terminal 800 can be a smartphone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV) player, a notebook computer, or a desktop computer. The terminal 800 can also be called by other names such as a user device, a mobile terminal, a laptop terminal, a desktop terminal, etc.

Typically, the terminal 800 includes a processor 801 and a memory 802.

The processor 801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 801 may be realized in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), or a PLA (Programmable Logic Array). The processor 801 may further include a main processor and a coprocessor, where the main processor is a processor for processing data in a wake state and is also called a CPU (Central Processing Unit), and the coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 801 may include a Graphics Processing Unit (GPU) for rendering and drawing content to be displayed on the display. In some embodiments, the processor 801 may further include an Artificial Intelligence (AI) processor for processing computational operations related to machine learning.

Memory 802 may include one or more computer-readable storage media, which may be non-transitory. Memory 802 may further include high-speed random access memory and non-volatile memory, such as one or more disk storage devices, flash memory storage devices, etc. In some embodiments, the non-transitory computer-readable storage media in memory 802 is used to store at least one instruction executed by processor 801 to perform a modular processing method for a foreground and background separation system provided by an embodiment of the method of the present invention.

In some embodiments, the terminal 800 optionally further includes a peripheral device interface 803 and at least one peripheral device. The processor 801, the memory 802, and the peripheral device interface 803 may be connected to each other via a bus or signal lines. Each peripheral device may be connected to the peripheral device interface 803 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of a radio frequency circuit 804, a display 805, a camera component 806, an audio circuit 807, a positioning component 808, and a power source 809.

The peripheral device interface 803 is used to connect at least one peripheral device associated with I/O (Input/Output) to the processor 801 and the memory 802. In some embodiments, the processor 801, the memory 802, and the peripheral device interface 803 are integrated on the same circuit module or circuit board, and in some other embodiments, any one or two of the processor 801, the memory 802, and the peripheral device interface 803 may be realized on separate circuit modules or circuit boards, and this embodiment is not limited thereto.

The radio frequency circuit 804 is used to receive and transmit RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 804 communicates with communication networks and other communication devices by electromagnetic signals. The radio frequency circuit 804 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals into electrical signals. Optionally, the radio frequency circuit 804 includes an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a coding and decoding circuit module set, a subscriber identity module card, and the like. The radio frequency circuit 804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to, metropolitan area networks, mobile communication networks of various generations (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuitry 804 may further include circuitry related to NFC (Near Field Communication), although the present invention is not limited thereto.

The display 805 is used to display a UI (User Interface). The UI may include graphics, text, icons, videos, and any combination thereof. If the display 805 is a touch display, the display 805 is further capable of collecting touch signals on or above the surface of the display 805. The touch signals may be input as control signals to the processor 801 for processing. In this case, the display 805 is further used to provide virtual buttons and/or virtual keyboards, also called soft buttons and/or soft keyboards. In some embodiments, the display 805 may be one and is installed on the front panel of the terminal 800, and in other embodiments, the display 805 may be at least two and each may be installed on a different surface of the terminal 800 or designed to be folded, and in other embodiments, the display 805 may be a flexible display installed on a curved or folded surface of the terminal 800. Furthermore, the display 805 may be installed to have an irregular shape other than a rectangle, i.e., an irregular screen. The display 805 can be made using materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

The camera component 806 is used to collect images or videos. Optionally, the camera component 806 includes a front camera and a back camera. Typically, the front camera is installed on the front panel of the terminal, and the back camera is installed on the back of the terminal. In some embodiments, there are at least two back cameras, each of which is one of a main camera, a depth of field camera, a wide-angle camera, and a telephoto camera, thereby realizing a background blur function by combining the main camera and the depth of field camera, a panoramic shooting and a VR (Virtual Reality) shooting function by combining the main camera and the wide-angle camera, or a shooting function by other fusion. In some embodiments, the camera component 806 may further include a flash lamp. The flash lamp may be a single color temperature flash lamp or a two-color temperature flash lamp. A two-color temperature flash lamp is a combination of a warm white flash lamp and a cool white flash lamp, and may be used for light correction at different color temperatures.

The audio circuit 807 may include a microphone and a speaker. The microphone is used to collect sound waves of the user and the environment, convert the sound waves into electrical signals, and input them to the processor 801 for processing, or to the radio frequency circuit 804 to enable voice communication. For the purpose of stereo sound collection or noise reduction, the microphones may be multiple and installed at different locations on the terminal 800. The microphone may also be an array microphone or an omnidirectional sound collection microphone. The speaker is used to convert the electrical signal from the processor 801 or the radio frequency circuit 804 into sound waves. The speaker may be a conventional thin-film speaker or a piezoelectric ceramic speaker. If the speaker is a piezoelectric ceramic speaker, it can not only convert the electrical signal into sound waves that can be heard by humans, but also convert the electrical signal into sound waves that cannot be heard by humans for applications such as distance measurement. In some embodiments, the audio circuit 807 may further include a headphone jack.

The positioning component 808 is used to determine the current geographical location of the terminal 800 to enable navigation or LBS (Location Based Services).

The power source 809 is used to supply power to each component in the terminal 800. The power source 809 may be an AC power source, a DC power source, a primary battery, or a secondary battery. If the power source 809 includes a secondary battery, the secondary battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charging technology.

In some embodiments, the terminal 800 further includes one or more sensors 810. The one or more sensors 810 include, but are not limited to, an acceleration sensor 811, a gyro sensor 812, a pressure sensor 813, a fingerprint sensor 814, an optical sensor 815, and a proximity sensor 816.

The acceleration sensor 811 can detect the magnitude of acceleration in three coordinate axes of a coordinate system established by the terminal 800. For example, the acceleration sensor 811 is used to detect components of gravitational acceleration in three coordinate axes. Based on the gravitational acceleration signal collected by the acceleration sensor 811, the processor 801 can control the display 805 to display the user interface in a horizontal view or a vertical view. The acceleration sensor 811 can further be used to collect game or user motion data.

The gyro sensor 812 can detect the direction and rotation angle of the main body of the terminal 800, and in cooperation with the acceleration sensor 811, can collect the user's 3D motion relative to the terminal 800. Based on the data collected by the gyro sensor 812, the processor 801 can realize functions such as motion detection (such as changing the UI by the user's tilt operation), image stabilization during shooting, game control, and inertial navigation.

The pressure sensor 813 may be installed on the side frame of the terminal 800 and/or on the lower layer of the display 805. When the pressure sensor 813 is installed on the side frame of the terminal 800, it can detect a grip signal from the user to the terminal 800, and the processor 801 distinguishes between left and right hands or performs shortcut operations based on the grip signal collected by the pressure sensor 813. When the pressure sensor 813 is installed on the lower layer of the display 805, the processor 801 realizes control over operable controls on the UI screen in response to a pressing operation on the display 805 by the user. The operable controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

The fingerprint sensor 814 is used to collect a user's fingerprint, and the processor 801 identifies the user's identity based on the fingerprint collected by the fingerprint sensor 814, or identifies the user's identity based on the fingerprint collected by the fingerprint sensor 814. Once the user's identity is identified as a trustworthy identity, the user is permitted by the processor 801 to perform related confidential operations, including unlocking the screen, viewing encrypted information, downloading software, making payments, and changing settings. The fingerprint sensor 814 may be installed on the front, back, or side of the terminal 800. If a physical button or manufacturer's logo is installed on the terminal 800, the fingerprint sensor 814 may be integrated with the physical button or manufacturer's logo.

The optical sensor 815 is used to collect the intensity of the ambient light. In one embodiment, the processor 801 can control the display brightness of the display 805 based on the intensity of the ambient light collected by the optical sensor 815. Specifically, when the intensity of the ambient light is high, the display brightness of the display 805 is increased, and when the intensity of the ambient light is low, the display brightness of the display 805 is decreased. In another embodiment, the processor 801 can further dynamically adjust the shooting parameters of the camera component 806 based on the intensity of the ambient light collected by the optical sensor 815.

The proximity sensor 816 is also called a distance sensor and is typically installed on the front panel of the terminal 800. The proximity sensor 816 is used to collect the distance between the user and the front of the terminal 800. In one embodiment, when the proximity sensor 816 detects that the distance between the user and the front of the terminal 800 is gradually decreasing, the processor 801 controls the display 805 to switch from a screen-on state to a screen-off state, and when the proximity sensor 816 detects that the distance between the user and the front of the terminal 800 is gradually increasing, the processor 801 controls the display 805 to switch from a screen-off state to a screen-on state.

The structure shown in FIG. 8 does not constitute a limitation on terminal 800, and one skilled in the art will appreciate that the terminal may include more or fewer components than shown, or may combine certain components or employ different component arrangements.

An embodiment of the present invention further provides a non-transitory computer-readable storage medium, and when instructions in the storage medium are executed by a processor of a terminal, the terminal can execute a module processing method for use in the foreground and background separation system provided by the above embodiment.

An embodiment of the present invention further provides a computer program product including instructions that, when executed on a terminal, cause the terminal to execute a module processing method for use in the foreground/background separation system provided by the above embodiment.

Figure 9 is a structural schematic diagram of a server provided by an embodiment of the present invention. The background in the above embodiment can be realized by the structure shown in Figure 9. The server may be a server in a background server cluster. Specifically, it is as follows:

The server 900 includes a central processing unit (CPU) 901, a system memory 904 including a random access memory (RAM) 902 and a read only memory (ROM) 903, and a system bus 905 connecting the system memory 904 and the central processing unit 901. The server 900 further includes a basic input/output system (I/O system) 906 that supports information transmission between each device in the computer, and a mass storage device 907 for storing an operating system 913, applications 914, and other program modules 915.

The basic input/output system 906 includes a display 908 for displaying information and input devices 909, such as a mouse and keyboard, for a user to input information. The display 908 and input devices 909 are connected to the central processing unit 901 through an input/output controller 910, which is connected to the system bus 905. The basic input/output system 906 may further include an input/output controller 910 for receiving and processing input from a number of other devices, such as a keyboard, a mouse, or an electronic stylus pen. Similarly, the input/output controller 910 provides output to a display, a printer, or other type of output device.

The mass storage device 907 is connected to the central processing unit 901 via a mass storage controller (not shown) connected to the system bus 905. The mass storage device 907 and its associated computer-readable media provide non-volatile storage for the server 900. That is, the mass storage device 907 may include a computer-readable medium (not shown) such as a hard drive or a CD-ROM drive.

Without loss of generality, computer readable media may include computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM, EEPROM, flash memory or other solid state storage technology, CD-ROM, DVD or other optical storage, tape cartridges, magnetic tape, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that computer storage media is not limited to some of the above. The above system memory 904 and mass storage device 907 may be collectively referred to as memory.

According to various embodiments of the present invention, the server 900 may be connected to a remote computer on a network, such as the Internet, and operate in that network. That is, the server 900 may be connected to a network 912 via a network interface unit 911 connected to the system bus 905, or may be connected to another type of network or remote computer system (not shown) using the network interface unit 911.

The memory further includes one or more programs, the one or more programs being stored in the memory and configured to be executed by the CPU. The one or more programs include those for executing a module processing method for use in a foreground/background separation system provided by an embodiment of the present invention.

An embodiment of the present invention further provides a non-transitory computer-readable storage medium, the instructions of which, when executed by a processor of a server, enable the server to execute a modular processing method for use in the foreground and background separation system provided by the embodiment.

An embodiment of the present invention further provides a computer program product including instructions that, when executed on a server, cause the server to execute a module processing method for use in the foreground and background separation system provided by the embodiment above.

A person skilled in the art can understand that all or part of the steps for implementing the above embodiment may be completed by hardware, or may be completed by a program instructing related hardware, and the above program may be stored in a computer-readable storage medium, and the above storage medium may be a read-only memory, a magnetic disk, an optical disk, etc.

The above are merely preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

700 Modular processing device for use in foreground and background separation system 701 First control module 702 Second control module 703 Third control module 800 Terminal 801 Processor 802 Memory 803 Peripheral device interface 804 Radio frequency circuit 805 Display 806 Camera component 807 Audio circuit 808 Positioning component 809 Power supply 810 Sensor 811 Acceleration sensor 812 Gyro sensor 813 Pressure sensor 814 Fingerprint sensor 815 Optical sensor 816 Proximity sensor 900 Server 901 Central processing unit 902 Random access memory 903 Read only memory 904 System memory 905 System bus 906 Basic input/output system 907 Mass storage device 908 Display 909 Input device 910 Input/output controller 911 Network interface unit 912 Network 913 Operating system 914 Applications 915 Other program modules

Claims (12)

A module processing method for a foreground/background separation system, the foreground/background separation system including a foreground and a background, an interactive interface is displayed in the foreground, the interactive interface is used to display a plurality of modules, a data center is disposed in the background, the data center is used to store module data for each of the plurality of modules, the module data includes a display method of the module, function data of the module, and a logical relationship between the module and each of the other modules, the foreground/background separation system includes a process setting system, the process setting system is used to provide a function of process setting, the process setting is a process of ordering functional modules and setting a relationship between each of the functional modules,
In response to a target operation on a target module, the foreground controls the background to update data corresponding to the target module in the data center based on the target operation, and the foreground updates the interactive interface based on the data corresponding to the updated target module, the target module being one or more of the multiple modules;
When a cancellation command for the target operation is detected, the foreground controls the background to restore the data corresponding to the target module in the data center based on the cancellation command, and the foreground updates the interactive interface based on the data corresponding to the restored target module.
11. A modular processing method for use in a foreground/background separation system, comprising: After the foreground controls the background to restore the data corresponding to the target module in the data center based on the cancellation command,
When a replay command for the target operation is detected, the foreground controls the background to update the data corresponding to the target module in the data center based on the target operation, and the foreground updates the interactive interface based on the data corresponding to the updated target module.
2. The method of claim 1 . The step of controlling the foreground to update the data corresponding to the target module in the data center based on the target operation by the background includes:
The foreground sends one or more first data update instructions to the background based on the target operation, and any one of the one or more first data update instructions is used to instruct the background to update a part of data corresponding to the target module;
generating an operation record by the foreground based on the transmission of the one or more first data update commands;
The step of controlling the foreground to restore the data corresponding to the target module in the data center based on the cancellation command by the background includes:
The method includes a step of transmitting one or more second data update instructions to the background based on an inverse operation of the target operation instructed by the operation record by the foreground, wherein any one of the one or more second data update instructions is used to instruct the background to restore the part of the data corresponding to the target module in the data center to a state before the target operation was executed.
2. The method of claim 1 . If the target operation is an add operation on the target module,
The step of transmitting one or more first data update commands to the background by the foreground based on the target operation includes:
The method includes a step of: the foreground first sends a first module update command to the background, and then sends a first logical relationship update command to control the background to first add the module data of the target module to the data center, and then add the logical relationship between the target module and the other modules to the module data of each of the other modules;
The step of transmitting one or more second data update commands to the background based on an inverse operation of the target operation indicated by the operation record by the foreground,
The foreground first transmits a second logical relationship update command to the background, and then transmits a second module update command to control the background to first delete the logical relationship between the target module and the other modules in the module data of each of the other modules in the data center, and then delete the module data of the target module in the data center;
4. The method according to claim 3 . If the target operation is a delete operation on the target module,
The step of transmitting one or more first data update commands to the background by the foreground based on the target operation includes:
The foreground first sends a first logical relationship update command to the background, and then sends a first module update command to control the background to first delete the logical relationship between the target module and the other modules in the module data of each of the other modules in the data center, and then delete the module data of the target module in the data center; or
The foreground includes a step of first transmitting a first logical relationship update command to the background, and then transmitting a first module update command to control the background to delete the logical relationship between the other modules and the target module in the module data of each of the other modules in the data center when the background receives the first logical relationship update command, and controlling the background to add a deletion mark to the module data of the target module in the data center when the background receives the first module update command;
The step of transmitting one or more second data update commands to the background based on an inverse operation of the target operation indicated by the operation record by the foreground,
The foreground first sends a second module update command to the background, and then sends a second logical relationship update command to control the background to first restore the module data of the target module in the data center, and then restore the logical relationship between the target module and the other modules in the module data of each of the other modules; or
The foreground includes a step of first transmitting a second module update command to the background, and then transmitting a second logical relationship update command to control the background to delete the deletion mark of the module data of the target module in the data center when the background receives the second module update command, and to add the logical relationship between the other modules and the target module to the module data of each of the other modules in the data center when the background receives the second logical relationship update command.
4. The method according to claim 3 . before the foreground first transmits the first logical relationship update command and then transmits the first module update command to the background,
The foreground controls the background to export the data corresponding to the target module in the data center and back it up to a reference storage location, the data corresponding to the target module including module data of the target module and the logical relationship between the target module and the other modules in the module data of each of the other modules;
the foreground first transmits the second module update command to the background, and then transmits the second logical relationship update command to the background, and then
In response to the received second module update command, the background imports the module data of the target module from the reference storage location to the data center, and in response to the received second logical relationship update command, the background imports the logical relationships between the target module and each of the other modules from the reference storage location to the data center.
6. The method of claim 5 . the logical relationship between the module and each of the other modules includes a connection relationship between the module and each of the other modules, and a subscription relationship between the module and each of the other modules;
the connection relationship indicates a connection line relationship between the module and each of the other modules on the interactive interface;
the subscription relationship indicates an association relationship between at least one of the internal parameters, inputs of the module and an output of each of the other modules, and/or an association relationship between an output of the module and at least one of the internal parameters, inputs of each of the other modules;
4. The method according to claim 3 . When the number of the target modules is more than one,
The step of transmitting a plurality of first data update commands to the background based on the target operation by the foreground includes:
A step of the foreground sending a first subscription relationship deletion command to the background, the first subscription relationship deletion command being used to instruct the background to delete a subscription relationship between the other module and an edge target module in the module data of each of the other modules, the edge target module being a target module among a plurality of target modules that has a logical relationship with the other module;
a step of the foreground transmitting a first connection relationship deletion command to the background, the first connection relationship deletion command being used to instruct the background to delete a connection relationship between the other module and the edge target module in the module data of each of the other modules;
The foreground sends a first module deletion command to the background, the first module deletion command being used to instruct the background to delete the module data of the plurality of target modules;
Or,
a step of transmitting a subscription relationship deletion command A from the foreground to the background, the subscription relationship deletion command A being used to instruct the background to delete, for each of the target modules, a subscription relationship between a post-execution module and each of the target modules, the post-execution module being a module executed after the target module in a flowchart displayed in the foreground, and the pre-execution module being a module executed before the target module in a flowchart;
A step of the foreground sending a subscription relationship deletion command B to the background, the subscription relationship deletion command B being used to instruct the background to delete a subscription relationship between a plurality of target modules;
A step of the foreground sending a subscription relationship deletion command C to the background, the subscription relationship deletion command C being used to instruct the background to delete a subscription relationship between each of the target modules and the previously executed module;
a step of transmitting a connection relationship deletion command A from the foreground to the background, the connection relationship deletion command A being used to instruct the background to delete a connection relationship between the post-execution module and each of the target modules;
a step of transmitting a connection relationship deletion command B from the foreground to the background, the connection relationship deletion command B being used to instruct the background to delete the connection relationships between the plurality of target modules;
a step of the foreground transmitting a connection relationship deletion command C to the background, the connection relationship deletion command C being used to instruct the background to delete a connection relationship between each of the target modules and the previously executed module;
The foreground sends a first module deletion command to the background, the first module deletion command being used to instruct the background to delete remaining data in the module data of the plurality of target modules.
8. The method of claim 7. A module processing device for use in a foreground/background separation system, the foreground/background separation system including a foreground and a background, an interactive interface is displayed in the foreground, the interactive interface is used to display a plurality of modules, a data center is disposed in the background, the data center is used to store module data for each of the plurality of modules, the module data includes a display method of the module, function data of the module, and a logical relationship between the module and each of the other modules, the foreground/background separation system includes a process setting system, the process setting system is used to provide a function of process setting, the process setting is a process of ordering functional modules and setting a relationship between each of the functional modules,
a first control module for, in response to a target operation on a target module, controlling the foreground to control the background to update data corresponding to the target module in the data center based on the target operation, and foreground to update the interactive interface based on the data corresponding to the updated target module, the target module being one or more of the plurality of modules;
a second control module for controlling the foreground to restore the data corresponding to the target module in the data center based on the cancellation command when a cancellation command for the target operation is detected, and for controlling the foreground to update the interactive interface based on the data corresponding to the restored target module;
13. A module processing device for use in a foreground/background separation system, comprising: A processor;
a memory for storing processor executable instructions, said memory comprising:
The processor is configured to execute the steps of the method according to any one of claims 1 to 8.
13. A module processing device for use in a foreground/background separation system, comprising: A non-volatile computer readable storage medium having instructions stored thereon that, when executed by a processor, perform the steps of the method according to any one of claims 1 to 8.
A non-volatile computer readable storage medium comprising: A computer program comprising instructions which, when executed on a computer, cause the computer to carry out the steps of the method according to any one of claims 1 to 8.
A computer program comprising:

Images