KR102655685B1 - System for sharing data - Google Patents

Abstract

The present invention relates to a data sharing system including a core server providing a predetermined cloud service, an edge server connected to the core server, and a plurality of local terminals connected to the edge server, wherein the edge server is connected to the plurality of local terminals. It includes a remote data cache module that holds edge data shared by at least two local terminals among the terminals, and a remote synchronization module that is connected to each local terminal and transmits and receives the edge data, wherein the remote data cache module stores the edge data. Provides a data sharing system that includes location information, data information, dirty flag information, and shared list information corresponding to

Description

Data sharing system{SYSTEM FOR SHARING DATA}

The present invention relates to a system that provides data sharing between local terminals.

Due to advances in processor, memory, and network technology, the computing environment is a form of cloud computing that does not depend on the independent hardware performance of each terminal but utilizes all computing resources on the network to provide services according to the request of the terminal. is evolving into

Cloud computing service can be defined as 'on demand outsourcing service of computing resources' through information and communication networks such as the Internet. In other words, cloud computing service is a method in which service providers provide services needed by users by integrating data centers dispersed in various locations in a cloud computing environment using virtualization technology.

According to this cloud computing, each local terminal must access the Core Server to share data with other local terminals. As a result, as the data shared between local terminals increases, the load on the core server increases exponentially. In other words, since each local terminal can share data with other local terminals through the core server, there is a problem that communication resources and processing time consumed for data sharing between local terminals increase. As a result, in the case of automated equipment implemented based on cloud computing, there are limitations in securing speed and stability.

The present invention provides a data sharing system that can reduce processing time and communication resources consumed for data sharing between local terminals.

The objects of the present invention are not limited to the objects mentioned above, and other objects and advantages of the present invention that are not mentioned can be understood by the following description and will be more clearly understood by the examples of the present invention. Additionally, it will be readily apparent that the objects and advantages of the present invention can be realized by the means and combinations thereof indicated in the patent claims.

In order to solve this problem, an example of the present invention includes a core server that provides a predetermined cloud service, an edge server connected to the core server, and a plurality of local terminals connected to the edge server, wherein the edge The server includes a remote data cache module that holds edge data shared by at least two local terminals among the plurality of local terminals, and a remote synchronization module that is connected to each local terminal and transmits and receives the edge data. A data sharing system. to provide. Here, the remote data cache module includes location information, data information, dirty flag information, and shared list information corresponding to the edge data. The location information corresponds to the identifier of the edge data, and the data information corresponds to the data value of the edge data. The dirty flag information corresponds to whether the edge data has been changed, and the shared list information includes the ID of at least one local terminal including software that uses the edge data.

The location information includes the ID of the local terminal that supplies the edge data, the ID of the software that processes the edge data, and the ID of the data for data identification within the software.

The edge server may further include a main data cache module that holds main data shared with the core server among the edge data of the remote data cache module, and a main synchronization module that is connected to the core server and transmits and receives the main data. there is. The main data cache module includes location information and data information corresponding to each main data.

Each local terminal has a local data cache module that holds local data for execution of at least one software installed in each local terminal among the edge data of the remote data cache module, and the remote synchronization module of the edge server. It includes a local synchronization module that transmits and receives edge data. Here, the local data cache module includes location information and data information corresponding to each local data.

When new edge data is generated during execution of the at least one software, the local data cache module transmits the location information and data information of the new edge data to the local synchronization module, and the local synchronization module transmits the new edge data A data registration request including location information and data information is transmitted to the remote synchronization module. The remote synchronization module transmits the data registration request to the remote data cache module, and the remote data cache module sets dirty flag information of new edge data corresponding to the data registration request to a reset state, It further retains dirty flag information, location information, and data information of new edge data in response to data registration requests.

When new local data is generated during execution of the at least one software, the local data cache module of any one of the plurality of local terminals transmits location information of the new local data to the local synchronization module, and performs the local synchronization. The module transmits a data provision request including location information of the new local data to the remote synchronization module. The remote synchronization module transmits the data provision request to the remote data cache module, and the remote data cache module detects call edge data corresponding to the location information of the data provision request among the edge data, and transmits the data provision request. The ID of the local terminal corresponding to is added to the shared list information of the call edge data, and the location information and data information of the call edge data are transmitted to the remote synchronization module. The remote synchronization module transmits a data provision response including location information and data information of the call edge data to the local synchronization module of the local terminal corresponding to the data provision request. The local synchronization module transmits the data provision response to the local data cache module, and the local data cache module changes data information of the new local data based on the data information in the data provision response. Here, new local data of a local terminal refers to new local data added by a local terminal among edge data held in the edge server.

When data information of the local data is changed during execution of the at least one software, the local data cache module transmits location information and data information of the changed local data to the local synchronization module, and the local synchronization module transmits the changed location information and data information to the local synchronization module. A data change request including location information and data information of local data is transmitted to the remote synchronization module. The remote synchronization module transmits the data change request to the remote data cache module, and the remote data cache module detects change edge data corresponding to the location information of the data change request among the edge data, and the change edge data The dirty flag information of is changed to the set state, and the data information of the change edge data is changed based on the data information of the data change request.

When a predetermined edge synchronization period arrives, the remote data cache module detects target edge data with the dirty flag information set among the edge data, and sends the location information, data information, and shared list information of the target edge data to the remote device. transmits to the synchronization module, and the remote synchronization module transmits the location information of the target edge data to the local synchronization module of at least one local terminal corresponding to the ID of at least one local terminal included in the shared list information of the target edge data, and Sends an edge synchronization request including data information. The local synchronization module transmits the edge synchronization request to the local data cache module, and the local data cache module detects target local data corresponding to the location information of the edge synchronization request among the local data, and the edge synchronization request Change the data information of the target local data based on the data information.

The data sharing system as described above includes a core server that provides cloud services, an edge server connected to the core server, and a plurality of local terminals connected to the edge server.

The edge server includes a remote data cache module that holds edge data shared by at least two local terminals among a plurality of local terminals.

The remote data cache module includes location information, data information, dirty flag information, and shared list information corresponding to edge data. Here, the location information corresponds to the identifier of the edge data, the data information corresponds to the data value of the edge data, the dirty flag information corresponds to whether the edge data has been changed, and the shared list information includes software that uses edge data. Contains the ID of at least one local terminal.

Accordingly, data sharing between multiple local terminals can be handled by the edge server rather than the core server. As a result, each local terminal does not need to be connected to the core server to share data with other local terminals, and the core server providing cloud services can handle data sharing between multiple local terminals connected to any one edge server. no need. Therefore, communication resources and processing time consumed for data sharing can be reduced. If this data sharing system is applied, it can be advantageous to ensure the speed and stability of automated equipment.

Figure 1 is a diagram showing a data sharing system according to an embodiment of the present invention.
FIG. 2 is an example of edge data held in the remote data cache module of the edge server of FIG. 1.
FIG. 3 is an example of local data held in a local data cache module of a first local terminal among a plurality of local terminals in FIG. 1.
FIG. 4 is an example of main data held in the main data cache module of the edge server of FIG. 1.
FIG. 5 is a flowchart showing a process in which a local terminal and an edge server synchronize new edge data in the data sharing system of FIG. 1.
FIG. 6 is an example of a step of transmitting new edge data of FIG. 5 to the local data cache module of the first local terminal of FIG. 3.
FIG. 7 is an example of a step of transmitting new edge data of FIG. 5 to the remote data cache module of FIG. 2.
FIG. 8 is a flowchart showing a process by which one local terminal and an edge server synchronize new local data in the data sharing system of FIG. 1.
FIG. 9 is an example of a step of transmitting new local data of FIG. 8 to the local data cache module in the local data held in the local data cache module of the third local terminal among the plurality of local terminals of FIG. 1.
FIG. 10 is an example of a step of transmitting shared list information of the detected edge data of FIG. 8 to a remote data cache module in the edge server of FIG. 2.
FIG. 11 is an example of a step of transmitting changed data information of new local data of FIG. 8 to the local data cache module of the third local terminal of FIG. 9.
FIG. 12 is a flowchart showing a process of synchronizing edge data changed by one local terminal to the edge server in the data sharing system of FIG. 1.
FIG. 13 is an example of a step of transmitting the changed local data of FIG. 12 to the local data cache module of the first local terminal of FIG. 3.
FIG. 14 is an example of a step of transmitting the changed edge data of FIG. 12 to the remote data cache module of FIG. 2.
FIG. 15 is a flowchart showing a process of synchronizing edge data of an edge server to a plurality of local terminals in the data sharing system of FIG. 1.
FIG. 16 is an example of a step of detecting target edge data of FIG. 15 in the remote data cache module of FIG. 14.
FIG. 17 is an example of a step of transmitting the target local data of FIG. 15 to the local data cache module of the third local terminal of FIG. 11.

The above-mentioned objects, features, and advantages will be described in detail later with reference to the attached drawings, so that those skilled in the art will be able to easily implement the technical idea of the present invention. In describing the present invention, if it is determined that a detailed description of known technologies related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description will be omitted. Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the attached drawings. In the drawings, identical reference numerals are used to indicate identical or similar components.

Hereinafter, with reference to the attached drawings, a data sharing system and a data sharing method thereof according to an embodiment of the present invention will be described.

First, a data sharing system according to an embodiment of the present invention will be described with reference to FIGS. 1 to 4.

Figure 1 is a diagram showing a data sharing system according to an embodiment of the present invention.

FIG. 2 is an example of edge data held in the remote data cache module of the edge server of FIG. 1. FIG. 3 is an example of local data held in a local data cache module of a first local terminal among the plurality of local terminals in FIG. 1. FIG. 4 is an example of main data held in the main data cache module of the edge server of FIG. 1.

As shown in Figure 1, the data sharing system according to an embodiment of the present invention includes a core server (CS; Core Server) that provides a predetermined cloud service, an edge server (EG; Edge Gateway) connected to the core server, and a plurality of local terminals (LT1, LT2, LT3, LT4, LT5; Local Terminal; hereinafter collectively referred to as “LT”) connected to the edge server.

Here, each local terminal (LT) may be comprised of any one of a PLC (Programmable Logic Controller), HMI (Human-Machine Interface), sensor, relay, and other communication modules for the implementation of automation equipment. In this case, data sharing The system may be intended to share various industrial automation data for the implementation of automation equipment to two or more local terminals (LT).

The edge server (ES) is a remote data cache module 110 that holds edge data shared by at least two local terminals among a plurality of local terminals (LT), and is connected to each local terminal (LT) and transmits and receives edge data. Includes a remote synchronization module 120.

Here, edge data is data shared by at least two local terminals among a plurality of local terminals (LT) connected to the edge server (ES).

The remote data cache module 110 holds a database corresponding to edge data and can process data sharing between local terminals (LT) based on an operating system that operates an edge server (ES).

And, the remote synchronization module 120 transfers the data received from the remote data cache module 110 to at least one local terminal (LT), and transmits the data received from the local terminal (LT) to the remote data cache module 110. deliver it to

In addition, the edge server (ES) is connected to the main data cache module 130, which holds main data shared with the core server (CS) among the edge data of the remote data cache module 110, and the core server (CS), and is connected to the main It may further include a main synchronization module 140 that transmits and receives data.

Here, the main data is at least part of the edge data of the remote data cache module 110 and is data shared with the core server (CS).

As an example, the main data cache module 130 may hold a database corresponding to main data and process data sharing with the core server (CS) based on the operating system that operates the edge server (ES).

Taking the first local terminal LT1, which is one of a plurality of local terminals LT, as an example, each local terminal LT includes a local data cache module 210 and a local synchronization module 220.

The local data cache module 210 holds a database corresponding to local data and executes at least one software installed in each local terminal LT1. Here, the local data is at least part of the edge data of the remote data cache module 110 and is data for executing at least one software installed in each local terminal LT1.

As shown in FIG. 2, the remote data cache module 120 may hold a database including at least one edge data. Here, the database of the remote data cache module 110 includes location information corresponding to edge data, dirty flag (DF) information, data information, and shared list information.

Location information corresponds to the identifier of edge data. In other words, location information is information for identification of edge data. This location information includes the ID of the local terminal supplying edge data (Local_ID), the ID of the software running on the local terminal of the data source and processing edge data (SW_ID), and data for data identification within the software that is the subject of data processing. It may include ID (Data_ID).

Dirty flag information corresponds to whether edge data has been changed. For example, when the dirty flag information (DF) is in a reset state (R; Reset), the corresponding edge data may remain unchanged. On the other hand, when the dirty flag information (DF) is set (S), the corresponding edge data may be in a changed state. Here, the reset state (R) and the set state (S) can be expressed as binary codes of 0 and 1.

In this case, when the data information of the edge data is changed, the dirty flag information (DF) is set to the set state (S), and when the data information of the edge data is synchronized, the dirty flag information (DF) is set to the reset state (R). can be set.

Data information corresponds to the data value of each edge data. In other words, data information is the actual data value generated according to the execution of software.

The shared list information includes the ID of at least one local terminal including software that uses each edge data. That is, the shared list information of each edge data includes the IDs of local terminals that share each edge data.

As shown in FIG. 3, the local data cache module 210 of one local terminal LT1 holds a database containing at least one local data.

Here, the database of the local data cache module 210 includes location information and data information corresponding to each local data.

Like the location information of edge data, the location information of local data includes the ID (Local_ID) of the local terminal that is the source of each local data, the ID (SW_ID) of the software that runs on the local terminal of the data source and processes each local data, and the data It may include the ID (Data_ID) of the data to identify the data within the software that is the subject of processing.

Data information is the data value of local data.

As shown in FIG. 4, the main data cache module 130 holds a database containing at least one main data.

Here, the database of the main data cache module 130 includes location information and data information corresponding to each main data.

Unlike the location information of edge data, the location information of main data may further include the ID of the edge server. In other words, the location information of the main data includes the ID of the edge server, the ID of the local terminal that is the source of each main data (Local_ID), the ID of the software that runs on the local terminal of the data source and processes each main data (SW_ID), and the data processing. It may include a data ID (Data_ID) for data identification within the subject software.

As such, according to an embodiment of the present invention, the edge server (ES) disposed between the core server (CS) providing a cloud service and a plurality of local terminals (LT) is shared by at least two local terminals (LT). It includes a remote data cache module 110 that holds edge data. Accordingly, data sharing between local terminals (LT) connected to the same edge server (ES) can be performed on the edge server (ES) rather than the core server (CS), thereby reducing the processing load on the core server (CS). , the consumption of communication resources can be reduced.

Next, a method for sharing data between local terminals in the data sharing system according to an embodiment of the present invention will be described.

First, a method for registering edge data will be described with reference to FIGS. 5, 6, and 7.

FIG. 5 is a flowchart showing a process in which a local terminal and an edge server synchronize new edge data in the data sharing system of FIG. 1. FIG. 6 is an example of a step of transmitting new edge data of FIG. 5 to the local data cache module of the first local terminal of FIG. 3. FIG. 7 is an example of a step of transmitting new edge data of FIG. 5 to the remote data cache module of FIG. 2.

As shown in FIG. 5, in a first local terminal (LT1), which is one of a plurality of local terminals (LT1), new edge data is generated while running at least one software installed in the first local terminal (LT1). It can happen. (S110) Here, new edge data refers to data that is generated in each local terminal (LT1) and must be transmitted to the edge server (ES) to be shared with other local terminals (LT).

At this time, the local data cache module 210 may hold the data information and location information of the new edge data as local data or may be updated to hold more.

When new edge data is generated in this way, the local data cache module 210 transmits the location information and data information of the new edge data to the local synchronization module 220. (S111)

The local synchronization module 220 transmits a data registration request including location information and data information of new edge data to the remote synchronization module 120 of the edge server (ES). (S112)

The remote synchronization module 120 transmits the data registration request to the remote data cache module 110. (S120)

The remote data cache module 110 sets the dirty flag information of new edge data corresponding to the data registration request to a reset state. (S121) Additionally, the remote data cache module 110 further holds dirty flag information, location information, and data information of new edge data corresponding to the data registration request. (S122)

For example, as indicated by shading in FIG. 6, in step S110 in which new edge data is generated, the local data cache module (LT1_210') of the first local terminal (LT1) provides location information and data information of the new edge data. is updated to add new labels, including , to the database of local data.

And, as indicated by shading in FIG. 7, in the step of further retaining new edge data (S122), the remote data cache module 110a of the edge server (ES) generates a dirty flag of the new edge data corresponding to the data registration request. An update is performed to add a new label including information, location information, and data information to the edge data database. At this time, the dirty flag information of the new edge data corresponding to the data registration request is the reset state (R), which is the initial value of the dirty flag information corresponding to the new edge data. Additionally, the shared list information of new edge data may be blank.

Next, referring to FIGS. 8 to 11, a method of registering any one of edge data as new local data will be described.

FIG. 8 is a flowchart showing a process by which one local terminal and an edge server synchronize new local data in the data sharing system of FIG. 1. FIG. 9 is an example of a step of transmitting new local data of FIG. 8 to the local data cache module in the local data held in the local data cache module of the third local terminal among the plurality of local terminals of FIG. 1. FIG. 10 is an example of a step of transmitting shared list information of the detected edge data of FIG. 8 to a remote data cache module in the edge server of FIG. 2. FIG. 11 is an example of a step of transmitting changed data information of new local data of FIG. 8 to the local data cache module of the third local terminal of FIG. 9.

As shown in FIG. 8, in the third local terminal LT3, which is one of the plurality of local terminals LT, new local data is stored while running at least one software installed in the third local terminal LT3. It can happen. (S130) Here, new local data refers to what a local terminal (LT) adds as its own local data among the edge data held in the edge server (ES).

At this time, the local data cache module 210 may further retain location information and data information of new local data.

When new local data is generated in this way, the local data cache module 210 may set the data information of the new local data to a predetermined initial value. (S131) Then, the local data cache module 210 transmits the location information of new local data to the local synchronization module 220. (S132)

The local synchronization module 220 transmits a data provision request including location information of new local data to the remote synchronization module 120 of the edge server (ES). (S133)

The remote synchronization module 133 transmits the data provision request to the remote data cache module 110. (S140)

The remote data cache module 110 detects call edge data corresponding to the location information of the data provision request among edge data. (S141)

And, the remote data cache module 110 adds the ID of the local terminal (LT3) corresponding to the data provision request to the shared list information of the call edge data. (S142)

Subsequently, the remote data cache module 110 transmits the location information and data information of the call edge data to the remote synchronization module 120.

The remote synchronization module 120 transmits a data provision response including location information and data information of the detected edge data to the local synchronization module 220 of the local terminal LT3 in response to the data provision request. (S144)

The local synchronization module 220 transmits the data provision response to the local data cache module 210. (S150)

The local data cache module 210 changes data information of new local data based on the data information of the data provision response. (S151)

For example, as shown in shading in FIG. 9, in step S130 in which new local data is generated, the local data cache module (LT3_210) of the third local terminal (LT3) provides location information and data information of the new local data. It is updated to add new labels, including new labels, to the database of local data. At this time, the data information of the new local data may be an initial value corresponding to the execution of at least one program installed in the third local terminal LT3.

As shown in shading in FIG. 10, in the step of adding the ID of the local terminal corresponding to the data provision request to the shared list information of the call edge data (S142), the call edge held in the database of the remote data cache module 110b The shared list information of the data (L01.SW01.D001) further includes the ID (L03) of the local terminal (LT3) corresponding to the data provision request.

And, as indicated by shading in FIG. 11, in the step of changing the data information of the new local data (S151), the new local data held in the database of the local data cache module (LT3_210') of the third local terminal (LT3) The data information is not the initial value, but is changed to the data information (AFED00) of the data provision response.

Next, referring to FIGS. 12 to 14, a method of changing data information of edge data held in the edge server (ES) will be described.

FIG. 12 is a flowchart showing a process of synchronizing edge data changed by one local terminal to the edge server in the data sharing system of FIG. 1. FIG. 13 is an example of a step of transmitting the changed local data of FIG. 12 to the local data cache module of the first local terminal of FIG. 3. FIG. 14 is an example of a step of transmitting the changed edge data of FIG. 12 to the remote data cache module of FIG. 2.

As shown in FIG. 12, in the first local terminal LT1, which is one of the plurality of local terminals LT, data information of at least one local data may be changed while executing at least one software. (S160)

In this case, the local data cache module 210 transmits the location information of the changed local data and the changed data information to the local synchronization module 220. (S161)

The local synchronization module 220 transmits a data change request including location information and data information of the changed local data to the remote synchronization module 120 of the edge server (ES). (S162)

The remote synchronization module 120 transmits the data change request to the remote data cache module 110. (S170)

The remote data cache module 110 detects change edge data corresponding to the location information of the data change request among the edge data held in the remote data cache module 110. (S171)

Then, the remote data cache module 110 changes the data information of the change edge data based on the data information of the data change request and changes the dirty flag information of the change edge data to the set state. (S172)

That is, as indicated in shading in FIG. 13, in the step (S160) in which the data information of the local data is changed, at least one of the local data held in the database of the local data cache module (L1_210") of the first local terminal (LT1) Any one data information is changed. That is, in the database of the local data cache module (L1_210"), the data information of the changed local data (L01.SW01.D001) changes from the old value (AFED00) to the new value (232323). do.

As shown in shading in FIG. 14, in the step of changing the dirty flag information and data information of the change edge data (S172), the remote data cache module 110c changes the data information of the change edge data to the data information of the data change request. Updated to change. That is, in the database of the updated remote data cache module 110c, the data information of the change edge data (L01.SW01.D001) is changed to data information (AFED00 → 232323) according to the data change request, and the change edge data (L01) The dirty flag information of .SW01.D001) changes from reset state to set state (R → S).

Next, with reference to FIGS. 15 to 17, a method of providing changed edge data among edge data held in the edge server (ES) to the local terminal (LT) will be described.

FIG. 15 is a flowchart showing a process of synchronizing edge data of an edge server to a plurality of local terminals in the data sharing system of FIG. 1. FIG. 16 is an example of a step of detecting target edge data of FIG. 15 in the remote data cache module of FIG. 14. FIG. 17 is an example of a step of transmitting the target local data of FIG. 15 to the local data cache module of the third local terminal of FIG. 11.

As shown in FIG. 15, when the edge synchronization period arrives (S180), the remote data cache module 110 of the edge server (ES) selects the target edge whose dirty flag information (DF) is in the set state (S) among the edge data. Detect data. (S181)

And, the remote data cache module 110 transmits the location information, data information, and shared list information of the target edge data to the remote synchronization module 120. (S182)

The remote synchronization module 120 provides location information and data information of the target edge data to the local synchronization module 220 of at least one local terminal corresponding to the ID of at least one local terminal included in the shared list information of the target edge data. Send edge synchronization request including. (S183)

The local synchronization module 220 transmits the edge synchronization request to the local data cache module 210. (S190)

The local data cache module 210 detects target local data corresponding to the location information of the edge synchronization request among local data. (S191)

And, the local data cache module 210 changes the data information of the target local data based on the data information of the edge synchronization request. (S192)

That is, as indicated by shading in FIG. 16, in the step (S181) of detecting the target edge data, the remote data cache module 110d detects the target edge data whose dirty flag information (DF) is in the set state (S) among the edge data. Detect (L01.SW01.D001).

In this case, the remote synchronization module 120 uses the second, fourth, fifth, and third IDs (L02, L04, L05, L03) of at least one local terminal included in the shared list information of the target edge data. An edge synchronization request including location information and data information of the target edge data (L01.SW01.D001) is transmitted to the local synchronization module 220 of the local terminal (LT2, LT4, LT5, LT3).

As shown in shading in FIG. 17, in the step of changing the data information of the target local data (S192), the target local data (L01. The data information of SW01.D001) is changed to the data information of the edge synchronization request (AFED00 → 232323).

In addition, although not separately shown, the remote data cache module 110 of the edge server (ES) uses the main synchronization module 140 to synchronize the main data cache module 130 when a predetermined main synchronization period arrives. Data can be delivered to the core server (CS).

As described above, the data sharing system according to an embodiment of the present invention is not a core server (CS) that provides cloud services, but an edge server (ES) disposed between the core server (CS) and a plurality of local terminals (LT). ) is used to process data sharing between multiple local terminals (LT). As a result, each local terminal (LT) does not need to be connected to the core server (CS) to share data between a plurality of local terminals (LT), so the consumption of communication resources can be reduced and processing speed can be improved. . As a result, it can be more advantageous to implement automated equipment.

The above-described present invention may be subject to various substitutions, modifications, and changes without departing from the technical spirit of the present invention to those skilled in the art to which the present invention pertains. It is not limited by .

CS: Core Server
ES: Edge Server
LT: Local terminal
DF: Dirty flag information

Claims (8)

A core server that provides certain cloud services;
An edge server connected to the core server; and
Includes a plurality of local terminals connected to the edge server,
The edge server is
a remote data cache module that holds edge data shared by at least two local terminals among the plurality of local terminals; and
It includes a remote synchronization module that is connected to each local terminal and transmits and receives the edge data,
The remote data cache module includes location information, data information, dirty flag information, and shared list information corresponding to the edge data,
Each local terminal is
a local data cache module that holds local data for executing at least one software installed in each local terminal among the edge data of the remote data cache module; and
Comprising a local synchronization module that transmits and receives the edge data to the remote synchronization module of the edge server,
The local data cache module includes location information and data information corresponding to each local data,
The location information corresponds to the identifier of the edge data,
The data information corresponds to the data value of the edge data,
The dirty flag information corresponds to whether the edge data has been changed,
The shared list information includes the ID of at least one local terminal including software that uses the edge data,
If the dirty flag information is in a reset state, the edge data indicates an unchanged state, and if the dirty flag information is in a set state, the edge data indicates a changed state,
The remote data cache module sets the dirty flag information of the new edge data corresponding to the data registration request to a reset state, and sets the dirty flag information, location information, and data information of the new edge data corresponding to the data registration request. A data sharing system that holds more.
According to claim 1,
A data sharing system wherein the location information includes an ID of a local terminal that supplies the edge data, an ID of software that processes the edge data, and an ID of data for data identification within the software.
According to claim 2,
The edge server is
a main data cache module that holds main data shared with the core server among the edge data of the remote data cache module; and
Further comprising a main synchronization module connected to the core server and transmitting and receiving the main data,
The main data cache module is a data sharing system that includes location information and data information corresponding to each main data.
delete According to claim 1,
When new edge data is generated while executing the at least one software, the local data cache module transmits location information and data information of the new edge data to the local synchronization module,
The local synchronization module transmits a data registration request including location information and data information of the new edge data to the remote synchronization module,
The remote synchronization module is a data sharing system that transmits the data registration request to the remote data cache module.
According to claim 1,
When new local data is generated during execution of the at least one software, the local data cache module of any one of the plurality of local terminals transmits location information of the new local data to the local synchronization module,
The local synchronization module transmits a data provision request including location information of the new local data to the remote synchronization module,
The remote synchronization module transmits the data provision request to the remote data cache module,
The remote data cache module detects call edge data corresponding to the location information of the data provision request among the edge data, and adds the ID of the local terminal corresponding to the data provision request to the shared list information of the call edge data. , transmitting the location information and data information of the call edge data to the remote synchronization module,
The remote synchronization module transmits a data provision response including location information and data information of the call edge data to the local synchronization module of the local terminal corresponding to the data provision request,
The local synchronization module transmits the data provision response to the local data cache module,
A data sharing system in which the local data cache module changes data information of the new local data based on data information of the data provision response.
According to claim 1,
When data information of the local data is changed during execution of the at least one software, the local data cache module transmits location information and data information of the changed local data to the local synchronization module,
The local synchronization module transmits a data change request including location information and data information of the changed local data to the remote synchronization module,
The remote synchronization module transmits the data change request to the remote data cache module,
The remote data cache module detects change edge data corresponding to the location information of the data change request among the edge data, changes dirty flag information of the change edge data to a set state, and A data sharing system that changes data information of the changed edge data based on data information.
According to claim 7,
When a predetermined edge synchronization period arrives, the remote data cache module detects target edge data with the dirty flag information set among the edge data, and sends the location information, data information, and shared list information of the target edge data to the remote device. Pass it to the synchronization module,
The remote synchronization module performs edge synchronization including location information and data information of the target edge data in a local synchronization module of at least one local terminal corresponding to the ID of at least one local terminal included in the shared list information of the target edge data. forwarding the request,
The local synchronization module transmits the edge synchronization request to the local data cache module,
The local data cache module detects target local data corresponding to the location information of the edge synchronization request among the local data, and changes data information of the target local data based on the data information of the edge synchronization request. A data sharing system .

Images