CN118842807A - Data synchronization module, data synchronization system and data synchronization method - Google Patents

Abstract

The present application provides a data synchronization module, a data synchronization system and a data synchronization method, wherein the data synchronization module includes a communication middleware, a view update unit and a view unit; wherein: the communication middleware is used to subscribe to first target data from other communication middleware; the view unit is used to display a user interface; the view update unit is used to subscribe to second target data from the communication middleware, and update the user interface displayed by the view unit according to the second target data, and the second target data includes the first target data. The data synchronization module can at least realize distributed MVVM across applications based on the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the prior art can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

Description

Data synchronization module, data synchronization system and data synchronization method

Technical Field

The present application relates to the field of data transmission, and in particular, to a data synchronization module, a data synchronization system, a data synchronization method, a computer-readable storage medium, and an electronic device.

Background Art

In the architecture related to UI (User Interface) development, MVC (Model-View-Controller), MVP (Model-View-Presenter), and MVVM (Model-View-ViewModel) are three commonly used architecture patterns. These three patterns separate the view and the business, effectively improving the development efficiency. These three architecture patterns are highly related, but also significantly different.

Among them, the MVP mode changes the Controller in the MVC mode to the Presenter, and changes the direction of communication, which further reduces business coupling, but the Presenter becomes heavier, and all business logic needs to go through the Presenter. The MVVM mode further changes the Presenter in the MVP mode to the ViewModel, reducing the complexity of developing and using control modules, and shifting from control-oriented development to data-oriented development, which completely decouples UI development and business logic development, greatly improving development efficiency.

However, the existing MVVM framework can only be implemented within one process, and cannot be implemented in multiple processes or across terminals. For example, the existing MVVM framework can only synchronize data between different interfaces of the same application, and cannot synchronize data between different interfaces and different applications or even distributed applications. In addition, the subscription/publishing and Watcher mechanisms of the existing MVVM framework are all private implementations of various MVVMs, which are strongly related to the programming language, and different programming languages cannot interact with each other.

Summary of the invention

The main purpose of the present application is to provide a data synchronization module, a data synchronization system, a data synchronization method, a computer-readable storage medium and an electronic device, so as to at least solve the problem that the prior art can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications.

In order to achieve the above-mentioned purpose, according to one aspect of the present application, a data synchronization module is provided, including a communication middleware, a view update unit and a view unit; wherein: the communication middleware is used to subscribe to first target data from other communication middleware; the view unit is used to display a user interface; the view update unit is used to subscribe to second target data from the communication middleware, and update the user interface displayed by the view unit according to the second target data, and the second target data includes the first target data.

Optionally, the data synchronization module also includes a monitoring unit and a model unit; wherein: the view unit is also used to receive interaction data based on the user interface; the monitoring unit is used to monitor the interaction data, and update the interaction data to the model unit when the interaction data is monitored; the model unit is used to process the interaction data to obtain processed data; the communication middleware is also used to monitor the processed data, and publish the processed data when the processed data is monitored.

Optionally, the communication middleware is specifically used to publish the processed data to the view update unit, the second target data also includes the processed data, and/or the communication middleware is specifically used to publish the processed data to other communication middleware that subscribes to the processed data; and/or the communication middleware adopts the DDS protocol.

According to another aspect of the present application, a data synchronization system is provided, comprising a first data synchronization module and a second data synchronization module, wherein the first data synchronization module and the second data synchronization module are data synchronization modules according to any one of the above; wherein: the first communication middleware included in the first data synchronization module is used to subscribe to first target data to the second communication middleware included in the second data synchronization module; and the second communication middleware is used to publish the first target data to the first communication middleware.

Optionally, the first data synchronization module and the second data synchronization module are different modules in the same application; or, the first data synchronization module and the second data synchronization module are different processes in the same device; or, the first data synchronization module and the second data synchronization module are different devices in the same distributed system.

According to another aspect of the present application, a data synchronization method is provided, and the data synchronization method is implemented based on the data synchronization module according to any one of the above, and the data synchronization method includes: a communication middleware subscribes to first target data from other communication middleware; a view update unit subscribes to second target data from the communication middleware, and updates the user interface displayed by the view unit according to the second target data, and the second target data includes the first target data.

Optionally, the data synchronization module also includes a monitoring unit and a model unit; the data synchronization method includes: the view unit receives interaction data based on the user interface; the monitoring unit monitors the interaction data and updates the interaction data to the model unit when the interaction data is monitored; the model unit processes the interaction data to obtain processed data; the communication middleware monitors the processed data and publishes the processed data when the processed data is monitored.

Optionally, the processing data is published when the processing data is monitored, including: the communication middleware publishes the processing data to the view update unit, the second target data also includes the processing data, and/or the communication middleware publishes the processing data to other communication middleware that subscribes to the processing data; and/or the communication middleware adopts the DDS protocol.

According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the data synchronization methods.

According to another aspect of the present application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include means for executing any one of the data synchronization methods.

Applying the technical solution of the present application, the above-mentioned data synchronization module includes a communication middleware, a view update unit and a view unit; wherein: the communication middleware is used to subscribe to the first target data from other communication middleware; the view unit is used to display the user interface; the view update unit is used to subscribe to the second target data from the communication middleware, and update the user interface displayed by the view unit according to the second target data, and the second target data includes the first target data. The data synchronization module can at least realize distributed MVVM across applications based on the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the prior art can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

FIG1 shows a schematic diagram of the structure of a data synchronization module provided according to an embodiment of the present application;

FIG2 shows a schematic diagram of the structure of another data synchronization module provided according to an embodiment of the present application;

FIG3 shows a schematic diagram of the structure of a data synchronization system provided according to an embodiment of the present application;

FIG4 shows a schematic diagram of the structure of another data synchronization system provided according to an embodiment of the present application;

FIG5 shows a schematic flow chart of a data synchronization method provided according to an embodiment of the present application.

The above drawings include the following reference numerals:

01. First data synchronization module; 02. Second data synchronization module; 10. Communication middleware; 11. First communication middleware; 12. Second communication middleware; 20. View update unit; 21. First view update unit; 22. Second view update unit; 30. View unit; 31. First view unit; 32. Second view unit; 40. Listening unit; 41. First listening unit; 42. Second listening unit; 50. Model unit; 51. First model unit; 52. Second model unit.

DETAILED DESCRIPTION

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

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

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

For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:

MVC: Model-View-Controller, Model-View-Controller, in which View provides the user with an interface and interacts directly with the user; Model is a data model designed according to business rules and carries data; Controller processes the user's request accordingly and returns the result calculated by Model to View. In the traditional MVC architecture, the view layer can access the Model.

MVP: Model-View-Presenter, Model-View-Coordinator, in which View and Model no longer interact directly, and all business logic needs to go through Presenter;

MVVM: Model-View-ViewModel, Model-View-ViewModel;

DDS: Data Distribution Service, data distribution service, DDS is a middleware standard and application program interface (API) released by the Object Management Group (OMG), using a distributed subscription/publishing architecture. DDS provides a low-latency, high-reliability, and scalable communication architecture standard for distributed systems. DDS is currently widely used in industry, medical care, transportation, energy, national defense, and other fields;

Qos: Quality Of Service, service quality, Qos refers to a network's ability to use various basic technologies to provide better service capabilities for specified network communications. It is a network security mechanism and a technology used to solve problems such as network delays and congestion. DDS provides up to 22 types of Qos, which can be used individually or in combination;

Vue - a progressive JavaScript framework for dynamically building user interfaces.

Angular: is a front-end framework for building user interfaces;

WPF: Windows Presentation Foundation, Windows Presentation Foundation, is a Windows-based user interface framework launched by Microsoft.

As introduced in the background technology, the existing MVVM framework can only be implemented within one process, and cannot implement a multi-process or cross-terminal MVVM framework. In order to solve the problem that the existing technology can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, the embodiments of the present application provide a data synchronization module, a data synchronization system, a data synchronization method, a computer-readable storage medium and an electronic device.

The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

An embodiment of the present application provides a data synchronization module, as shown in Figure 1, including a communication middleware 10, a view update unit 20 and a view unit 30; wherein: the above-mentioned communication middleware 10 is used to subscribe to first target data from other communication middleware; the above-mentioned view unit 30 is used to display a user interface; the above-mentioned view update unit 20 is used to subscribe to second target data from the above-mentioned communication middleware 10, and update the above-mentioned user interface displayed by the above-mentioned view unit 30 according to the above-mentioned second target data, and the above-mentioned second target data includes the above-mentioned first target data.

Currently, mainstream front-end frameworks such as Vue, Angular, and Microsoft's WPF (Windows Presentation Foundation) use the MVVM architecture. The implementation principles of MVVM are similar. Take Vue as an example: MVVM is used as the entry point for data binding, integrating Observer, Compile, and Watcher. Observer is used to monitor changes in model data, Compile is used to parse and compile template instructions, and Watcher is used to build a communication bridge between Observer and Compile, achieving a two-way binding effect from data changes to view updates and from view interaction changes (input) to data model changes.

Implement compile: compile the template, including compiling elements (instructions), compiling text, etc., to achieve the purpose of initializing the view, and also need to bind the update function;

Implement Observer: monitor all data and issue notifications for changed data;

Implement watcher: As a hub, it receives notifications from observer and executes the corresponding update method in compile.

However, the existing MVVM framework can only be implemented within the process, and cannot be implemented as a multi-process or cross-host MVVM framework. For example, the existing MVVM framework can only synchronize data between different interfaces of the same application, and cannot synchronize data between different applications or even distributed applications. In addition, the subscription/publishing and Watcher mechanisms of the existing framework are all private implementations of various MVVMs, which are strongly related to the programming language, and different programming languages cannot interact with each other.

The above-mentioned data synchronization module of the present application includes a communication middleware, a view update unit and a view unit; wherein: the communication middleware is used to subscribe to the first target data from other communication middleware; the view unit is used to display the user interface; the view update unit is used to subscribe to the second target data from the communication middleware, and update the user interface displayed by the view unit according to the second target data, and the second target data includes the first target data. The data synchronization module can at least realize distributed MVVM across applications based on the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the prior art can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

In some instances, as shown in FIG. 2 , the data synchronization module further includes a monitoring unit 40 and a model unit 50; wherein: the view unit 30 is also used to receive interaction data based on the user interface; the monitoring unit 40 is used to monitor the interaction data, and update the interaction data to the model unit 50 when the interaction data is monitored; the model unit 50 is used to process the interaction data to obtain processed data; the communication middleware 10 is also used to monitor the processed data, and publish the processed data when the processed data is monitored.

Specifically, the monitoring unit is used to monitor the interactive data, which can ensure the real-time performance of data transmission.

The data synchronization module adopts the MVVM architecture, namely the model-view-viewmodel architecture, and the combination of at least a monitoring unit, a view updating unit and a communication middleware in this example provides a new view model design.

In some instances, as shown in FIG. 2 , the communication middleware 10 is specifically used to publish the processed data to the view update unit 20, the second target data also includes the processed data, and/or the communication middleware 10 is specifically used to publish the processed data to other communication middlewares 10 that subscribe to the processed data; and/or the communication middleware 10 adopts the DDS protocol.

Among them, the communication middleware will publish the processed data to other communication middleware that subscribes to the processed data through DDS, which can break through the limitations within the process and realize data transmission within the process, between processes, and across hosts (terminals).

Specifically, DDS uses a variety of transmission mechanisms to ensure communication services between entities, including: User Datagram Protocol (UDP), Transmission Control Protocol (TCP), Shared Memory (SHM) transmission, Data-sharing (data sharing) and in-process delivery. UDP/TCP is generally used for transmission between different hosts. SHM transmission is used for shared memory communication between entities running on the same host. Data-sharing uses shared memory and zero-copy technology to speed up communication between entities in the same host, avoiding any overhead designed in the transport layer. In-process delivery is for the publisher to directly call the subscriber's receiving function, completely avoiding the copying or sending operations of the transmission, and at the same time avoiding the confirmation mechanism.

DDS provides up to 22 types of QoS, which can be used individually or in combination. DDS also includes a DDS Discovery mechanism, which exchanges information between different DDS entities through multicast or discovery servers to achieve mutual subscription and publishing functions.

Therefore, the DDS-based MVVM architecture in Figure 2 greatly simplifies the distributed system with View display and the complexity of multi-terminal development, allowing different systems, different programming languages, and different terminals to interact with each other based on the same data model.

An embodiment of the present application provides a data synchronization system, as shown in Figures 3 and 4, including a first data synchronization module 01 and a second data synchronization module 02, wherein the first data synchronization module 01 and the second data synchronization module 02 are based on any one of the above-mentioned data synchronization modules; wherein: the first communication middleware 11 included in the first data synchronization module 01 is used to subscribe to the first target data from the second communication middleware 12 included in the second data synchronization module 02; the second communication middleware 12 is used to publish the first target data to the first communication middleware 11.

The above-mentioned data synchronization system of the present application includes a first data synchronization module and a second data synchronization module, and the first data synchronization module and the second data synchronization module are data synchronization modules according to any one of them; wherein: the first communication middleware included in the first data synchronization module is used to subscribe the first target data to the second communication middleware included in the second data synchronization module; the second communication middleware is used to publish the first target data to the first communication middleware. The data synchronization system can at least realize distributed MVVM across applications based on the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the prior art can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

As shown in Figure 4, the first data synchronization module 01 includes a first communication middleware 11, a first view update unit 21, a first view unit 31, a first listening unit 41 and a first model unit 51, and the second data synchronization module 02 includes a second communication middleware 12, a second view update unit 22, a second view unit 32, a second listening unit 42 and a second model unit 52.

In some instances, the first data synchronization module and the second data synchronization module are different modules in the same application; or, the first data synchronization module and the second data synchronization module are different processes in the same device; or, the first data synchronization module and the second data synchronization module are different devices in the same distributed system.

Specifically, this can realize distributed MVVM across applications, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, solving the problem that the existing technology can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, greatly reducing the development cost of the distributed architecture.

Among them, the first data synchronization module and the second data synchronization module discover each other in advance through the DDSDiscovery mechanism and subscribe to the data of interest. If the first data synchronization module and the second data synchronization module are in different local area networks, they can broadcast/listen through the proxy server to establish a connection with each other, so that distributed MVVM data synchronization across terminals can be realized, which greatly simplifies the complexity of multi-terminal development and enables different systems and different programming languages to interact with each other based on the same data model.

As shown in FIG4 , the first data synchronization module 01 and the second data synchronization module 02 in the figure represent different hosts in different distributed systems, or different processes on the same host, or different modules in the same application. The ModeView mechanism in the second data synchronization module 02 is consistent with that in the first data synchronization module 01, but does not limit the programming language, that is, the first data synchronization module 01 and the second data synchronization module 02 can be different programming languages. Both the first data synchronization module 01 and the second data synchronization module 02 are MVVM architectures. The first view unit 31 is the View in the MVVM architecture of the first data synchronization module 01, the first listening unit 41, the first view update unit 21, and the first communication middleware 11 together constitute the ModelView in the MVVM architecture of the first data synchronization module 01, and the first model unit 51 is the Model in the MVVM architecture of the first data synchronization module 01; the second view unit 32 is the View in the MVVM architecture of the second data synchronization module 02, the second listening unit 42, the second view update unit 22, and the second communication middleware 12 together constitute the ModelView in the MVVM architecture of the second data synchronization module 02, and the second model unit 52 is the Model in the MVVM architecture of the second data synchronization module 02.

The embodiment of the present application also provides a data synchronization method, which is implemented based on any of the above data synchronization modules. FIG5 is a flow chart of the data synchronization method according to the embodiment of the present application. As shown in FIG5, the data synchronization method includes the following steps:

Step S201, the communication middleware subscribes to the first target data from other communication middleware;

Step S202: the view updating unit subscribes to second target data from the communication middleware, and updates the user interface displayed by the view unit according to the second target data, wherein the second target data includes the first target data.

In some instances, the data synchronization module further includes a monitoring unit and a model unit; the data synchronization method includes: the view unit receives interaction data based on the user interface; the monitoring unit monitors the interaction data, and updates the interaction data to the model unit when the interaction data is monitored; the model unit processes the interaction data to obtain processed data; the communication middleware monitors the processed data, and publishes the processed data when the processed data is monitored.

Among them, the monitoring unit monitors the data in real time to ensure the real-time nature of the data, and stores the data in the model unit in real time to ensure that the data will not be lost.

Among them, the interactive data is the data that changes accordingly when the View in the data synchronization module changes. When the View in the data synchronization module changes, multiple data will change. The interactive data is the data content that needs to be synchronized that was set in the early stage.

The view update unit updates the view in the view unit by reading and processing data, thereby ensuring the real-time nature of data update.

For example, a mobile phone and a tablet open the same application, and some operations are performed on the mobile phone to change the screen of the application, then the background data of the application will also change accordingly, and the user wants the screen of the application on the tablet to change synchronously with the screen of the application on the mobile phone, then the data corresponding to the changed screen will be determined as interactive data and transmitted from the mobile phone to the tablet so that the screen on the tablet changes synchronously with the mobile phone, thus realizing data synchronization between different terminals.

In some instances, the processing data is published when it is monitored, including: the communication middleware publishes the processing data to the view update unit, the second target data also includes the processing data, and/or the communication middleware publishes the processing data to other communication middlewares that subscribe to the processing data; and/or the communication middleware adopts the DDS protocol.

Specifically, the communication middleware transmits the processed data to another terminal or to another process through DDS, which can break through the limitations within the process and realize data transmission within the process, between processes, and across hosts (terminals).

Wherein, based on the data synchronization system shown in FIG4 , the embodiment of the present application further includes the following steps:

Step S301, according to the data transmission condition of the first data synchronization module, determining that the service quality transmission strategy that meets the data transmission condition is the first service quality transmission strategy, the data transmission condition includes data transmission accuracy and data transmission speed, and the first service quality transmission strategy is the service quality transmission strategy of the first communication middleware;

Step S302, according to the service quality transmission strategy of the first communication middleware, determining that the service quality transmission strategy corresponding to the first service quality transmission strategy is a second service quality transmission strategy, and the second service quality transmission strategy is the service quality transmission strategy of the second communication middleware;

Step S303, using the above-mentioned data distribution service mechanism to control the above-mentioned first communication middleware to send the above-mentioned first target data to the above-mentioned second communication middleware based on the above-mentioned first service quality transmission strategy, and control the above-mentioned second communication middleware to receive the above-mentioned first target data based on the above-mentioned second service quality transmission strategy, so as to synchronize the above-mentioned first target data from the above-mentioned first data synchronization module to the second data synchronization module.

Specifically, the first quality of service transmission strategy and the second quality of service transmission strategy can be the same quality of service transmission strategy or different quality of service transmission strategies, and the QoS strategy set by DDS can maximize the stability of distributed MVVM.

In some examples, based on the data synchronization system shown in FIG. 4 , the first data synchronization module adopts a first programming language, the second data synchronization module adopts a second programming language, and the method further includes the following steps:

Step S401, controlling the first communication middleware to run the data distribution service mechanism to convert the programming language of the first target data from the first programming language to the target programming language to obtain target language data, and controlling the first communication middleware to run the data distribution service mechanism to send the target language data to the second communication middleware;

Step S402, controlling the second communication middleware to run the data distribution service mechanism to identify the target language data and convert the programming language of the target language data into the second programming language, so that the target language data is synchronized from the first data synchronization module to the second data synchronization module.

Take a document review project as an example. The requirements are to display and operate on different terminals such as PC, iPad, iOS, and Android. Using the above DDS-based MVVM architecture, based on the same data model, developers only need to focus on how the View is presented on different terminals, and then bind the data of interest through ViewModel and Model, set the DDS service discovery mechanism and QoS strategy, and basically complete the development of a multi-terminal distributed system. The review on one terminal will be immediately updated to other terminals, greatly reducing the development of distributed document review projects. By adding the DDS standard protocol to ModelView, the MVVM framework breaks through the limitations of the process and realizes a distributed MVVM framework. The rich QoS strategies of DDS effectively solve the problem of complex communication in the distributed system, and the independence of programming languages between different MVVM entities is achieved through DDS.

The above-mentioned data synchronization method of the present application is implemented based on any one of the above-mentioned data synchronization modules, and the data synchronization method includes: the communication middleware subscribes to the first target data from other communication middleware; the view update unit subscribes to the second target data from the above-mentioned communication middleware, and updates the above-mentioned user interface displayed by the view unit according to the above-mentioned second target data, and the above-mentioned second target data includes the above-mentioned first target data. This method can at least realize distributed MVVM across applications based on the design of the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the existing technology can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the data synchronization method of the present application will be described in detail below in combination with specific embodiments.

This embodiment relates to a data synchronization method. As shown in FIG4 , the first data synchronization module 01 and the second data synchronization module 02 represent different hosts in different distributed systems, or different processes on the same host, or different modules in the same application. Taking the change of View in the first data synchronization module 01 as an example, firstly, the first data synchronization module 01 and the second data synchronization module 02 discover each other through the DDSDiscovery mechanism and subscribe to the data of interest. Then, the first view unit 31 in the first data synchronization module 01 changes according to the user operation, and the first monitoring unit 41 monitors the change of the data in the first view unit 31, that is, the changed data is updated to the first model unit 51. The first communication middleware 11 obtains the target data in the first model unit 51 by monitoring the data in the first model unit 51. Then, the public DDS protocol publishes the changed data to the second communication middleware 12, and the second view update unit 22 obtains the target data obtained by the second communication middleware 12, and updates the view in the second view unit 32 according to the target data, so as to realize data synchronization within the process, between processes, and across terminals.

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

The data synchronization module also includes a processor and a memory. The communication middleware and the like are stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions. The modules are all located in the same processor; or, the modules are located in different processors in any combination.

The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the kernel parameters can be adjusted to solve the problem that the existing technology can only synchronize data between different interfaces of the same application, but cannot synchronize data between different applications.

The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the data synchronization method.

An embodiment of the present invention provides a processor, and the processor is used to run a program, wherein the data synchronization method is executed when the program is running.

An embodiment of the present invention provides a device, which includes a processor, a memory, and a program stored in the memory and executable on the processor.

The devices in this article can be servers, PCs, PADs, mobile phones, etc.

The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes at least the steps of the data synchronization method.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

The present application is described with reference to the flowchart and/or block diagram of the method, device (system) and computer program product according to the embodiment of the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, and the combination of the process and/or box in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

In a typical configuration, a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.

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

Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

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

From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

1) The above-mentioned data synchronization module of the present application includes a communication middleware, a view update unit and a view unit; wherein: the communication middleware is used to subscribe to the first target data from other communication middleware; the view unit is used to display the user interface; the view update unit is used to subscribe to the second target data from the communication middleware, and update the user interface displayed by the view unit according to the second target data, and the second target data includes the first target data. The data synchronization module can at least realize distributed MVVM across applications based on the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the existing technology can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

2) The above-mentioned data synchronization system of the present application includes a first data synchronization module and a second data synchronization module, and the first data synchronization module and the second data synchronization module are data synchronization modules according to any one of them; wherein: the first communication middleware included in the first data synchronization module is used to subscribe the first target data to the second communication middleware included in the second data synchronization module; the second communication middleware is used to publish the first target data to the first communication middleware. The data synchronization system can at least realize distributed MVVM across applications based on the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the prior art can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

3) The above-mentioned data synchronization method of the present application is implemented based on any one of the above-mentioned data synchronization modules, and the data synchronization method includes: the communication middleware subscribes to the first target data from other communication middleware; the view update unit subscribes to the second target data from the above-mentioned communication middleware, and updates the above-mentioned user interface displayed by the view unit according to the above-mentioned second target data, and the above-mentioned second target data includes the above-mentioned first target data. This method can at least realize distributed MVVM across applications based on the design of the communication middleware, and can basically complete the development of a distributed system. The data on one application can be synchronized and updated to other applications, which solves the problem that the existing technology can only realize data synchronization between different interfaces of the same application, but cannot realize data synchronization between different applications, and greatly reduces the development cost of the distributed architecture.

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

Claims (10)

1. A data synchronization module, characterized by comprising a communication middleware, a view update unit and a view unit; in: The communication middleware is used to subscribe to the first target data from other communication middleware; The view unit is used to display a user interface; The view updating unit is used to subscribe second target data to the communication middleware, and update the user interface displayed by the view unit according to the second target data, where the second target data includes the first target data. 2. The data synchronization module according to claim 1, characterized in that the data synchronization module further comprises a monitoring unit and a model unit; wherein: The view unit is also used to receive interaction data based on the user interface; The monitoring unit is used to monitor the interaction data, and update the interaction data to the model unit when the interaction data is monitored; The model unit is used for processing the interaction data to obtain processed data; The communication middleware is further used for monitoring the processing data and publishing the processing data when the processing data is monitored. 3. The data synchronization module according to claim 2, characterized in that the communication middleware is specifically used to publish the processed data to the view update unit, the second target data also includes the processed data, and/or the communication middleware is specifically used to publish the processed data to other communication middleware that subscribes to the processed data; and/or, The communication middleware adopts the DDS protocol. 4. A data synchronization system, characterized in that it comprises a first data synchronization module and a second data synchronization module, wherein the first data synchronization module and the second data synchronization module are the data synchronization modules according to any one of claims 1 to 3; wherein: The first communication middleware included in the first data synchronization module is used to subscribe to the first target data from the second communication middleware included in the second data synchronization module; The second communication middleware is used to publish the first target data to the first communication middleware. 5. The data synchronization system according to claim 4, characterized in that the first data synchronization module and the second data synchronization module are different modules in the same application; or, The first data synchronization module and the second data synchronization module are different processes in the same device; or, The first data synchronization module and the second data synchronization module are different devices in the same distributed system. 6. A data synchronization method, characterized in that the data synchronization method is implemented based on the data synchronization module according to any one of claims 1 to 3, and the data synchronization method comprises: The communication middleware subscribes to the first target data from other communication middleware; The view updating unit subscribes to second target data from the communication middleware, and updates the user interface displayed by the view unit according to the second target data, wherein the second target data includes the first target data. 7. The data synchronization method according to claim 6, characterized in that the data synchronization module further comprises a monitoring unit and a model unit; the data synchronization method comprises: The view unit receives interaction data based on the user interface; The monitoring unit monitors the interaction data, and updates the interaction data to the model unit when the interaction data is monitored; The model unit processes the interaction data to obtain processed data; The communication middleware monitors the processing data and publishes the processing data when the processing data is monitored. 8. The data synchronization method according to claim 7, characterized in that the step of publishing the processed data when the processed data is monitored comprises: The communication middleware publishes the processing data to the view update unit, the second target data also includes the processing data, and/or the communication middleware publishes the processing data to other communication middlewares that subscribe to the processing data; and/or, The communication middleware adopts the DDS protocol. 9. A computer-readable storage medium, characterized in that the computer-readable storage medium includes a stored program, wherein when the program is running, the device where the computer-readable storage medium is located is controlled to execute the data synchronization method described in any one of claims 6 to 8. 10. An electronic device, characterized in that it comprises: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include a method for executing the data synchronization method described in any one of claims 6 to 8.