CN114465997A

CN114465997A - Data synchronization method and device, electronic equipment and storage medium

Info

Publication number: CN114465997A
Application number: CN202210237080.7A
Authority: CN
Inventors: 任珺; 李江
Original assignee: Shenzhen Sensetime Technology Co Ltd
Current assignee: Shenzhen Sensetime Technology Co Ltd
Priority date: 2022-03-11
Filing date: 2022-03-11
Publication date: 2022-05-10

Abstract

The disclosure relates to a data synchronization method and device, an electronic device and a storage medium, wherein the method comprises the following steps: acquiring edge data to be synchronized; and under the condition that the edge-end equipment is registered in the cloud-end equipment and the sending information of the edge-end data is not recorded by the edge-end equipment, sending the edge-end data to the cloud-end equipment through a broadcast channel, wherein the broadcast channel is an information transmission channel of the distributed publish-subscribe message system in a broadcast mode. The embodiment of the disclosure can realize concise and effective data synchronization.

Description

Data synchronization method and device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data synchronization method and apparatus, an electronic device, and a storage medium.

Background

At present, a large amount of edge devices and cloud devices are cooperatively operated in a cloud edge cooperation mode. In the related art, data synchronization between the edge device and the cloud device is usually achieved by using a hypertext transfer protocol HTTP and the like, so that a large amount of logic processing may be additionally added to ensure consistency of the synchronized data, and the extensibility is not high.

Disclosure of Invention

The present disclosure provides a data synchronization technical solution.

According to an aspect of the present disclosure, there is provided a data synchronization method applied to an edge device, including: acquiring edge data to be synchronized; and under the condition that the edge device is registered in a cloud device and does not record the sending information of the edge data, sending the edge data to the cloud device through a broadcast channel, wherein the broadcast channel is an information transmission channel of the distributed publish-subscribe message system in a broadcast mode.

In a possible implementation manner, the sending information includes a sending time of the data at the edge, and the method further includes: under the condition that the edge device is registered in the cloud device and the sending information is recorded by the edge device, judging whether the sending of the edge data is overtime or not according to the data sending time in the sending information; and under the condition that the data of the side end is sent overtime, the data of the side end is sent to the cloud end equipment again through the broadcast channel, and the data sending time in the sending information is updated.

In one possible implementation, the method further includes: responding to a received data updating request sent by the cloud end equipment, and judging whether a cloud end data identifier of cloud end data in the data updating request is matched with an edge end data identifier of the edge end equipment or not; and under the condition that the cloud data identification is not matched with the edge data identification, updating the edge data stored by the edge equipment according to the cloud data in the data updating request.

In one possible implementation, the method further includes: when the edge device is not registered in the cloud device, initiating a registration request to the cloud device; in response to receiving difference data returned by the cloud end device for the registration request, updating the edge end data stored by the edge end device according to the difference data, wherein the difference data comprises data of difference between the edge end data of the edge end device in the registration process and the cloud end data of the cloud end device.

According to an aspect of the present disclosure, a data synchronization method is provided, which is applied to a cloud device, and includes: in response to receiving the edge data sent by the edge device, determining whether the edge device is registered in the cloud device according to the identity information of the edge device; under the condition that the edge device is registered in the cloud device, processing the edge data according to the edge data identifier of the edge data to obtain a processing result of the edge data; and sending the processing result of the edge data to the edge device through a unicast channel corresponding to the edge device, wherein the unicast channel is an information transmission channel of the distributed publish-subscribe message system in a unicast mode.

In a possible implementation manner, the determining, in response to receiving the edge data sent by the edge device, whether the edge device is registered in the cloud device according to the identity information of the edge device includes: in response to receiving the edge data sent by the edge device, determining whether the identity information of the edge device exists in a registration list of the cloud device; confirming that the edge device is registered in the cloud device under the condition that the identity information of the edge device exists in the registration list; or, under the condition that the identity information of the edge device does not exist in the registration list, determining that the edge device is not registered in the cloud device.

In a possible implementation manner, the processing, according to the edge data identifier of the edge data, the edge data when the edge device is registered in the cloud device includes: processing the side end data according to the business processing requirement corresponding to the side end data under the condition that the side end equipment is registered in the cloud end equipment and the side end data is not processed based on the side end data identification; or, when the edge device is registered in the cloud device and it is determined that the edge data has been processed based on the edge data identifier, updating the communication state of the edge device recorded in the cloud device according to the data receiving time of the edge data, where the communication state includes normal communication or timeout communication.

In one possible implementation, the method further includes: responding to a data updating operation of the cloud end equipment, and determining cloud end data corresponding to the data updating operation; the method comprises the steps of respectively sending data updating requests to at least one registered edge device through a broadcast channel so as to update edge data of the at least one edge device, wherein the data updating requests comprise cloud data and cloud data identification of the cloud data.

In one possible implementation, the method further includes: in response to receiving a registration request sent by the edge device, judging whether identity information of the edge device exists in a registration list of the cloud device; and under the condition that the identity information of the edge device does not exist in the registration list, adding the identity information of the edge device into the registration list to complete the registration of the edge device.

In one possible implementation, the method further includes: under the condition that the identity information of the edge device exists in the registration list and the registration request comprises an edge data identifier, judging whether the edge data identifier in the registration request is matched with the cloud data identifier of the cloud device, wherein the edge data identifier is the data identifier of the edge data stored by the edge device; and under the condition that the edge data identification is not matched with the cloud data identification, sending difference data determined based on the difference between the cloud data and the edge data to the edge equipment through the unicast channel so as to update the edge data stored by the edge equipment.

According to an aspect of the present disclosure, there is provided a data synchronization apparatus applied to an edge device, including: the acquisition module is used for acquiring the data of the side end to be synchronized; the synchronization module is used for sending the edge data to the cloud device through a broadcast channel under the condition that the edge device is registered in the cloud device and the edge device does not record the sending information of the edge data, wherein the broadcast channel is an information transmission channel of the distributed publishing and subscribing message system in a broadcast mode.

In a possible implementation manner, the sending information includes a sending time of the data at the edge, and the apparatus further includes: the timeout judging module is used for judging whether the data of the side end is sent overtime according to the data sending time in the sending information under the condition that the side end equipment is registered in the cloud end equipment and the side end equipment records the sending information; and the data retransmission module is used for retransmitting the edge data to the cloud equipment through the broadcast channel and updating the data transmission time in the transmission information under the condition that the edge data is transmitted overtime.

In one possible implementation, the apparatus further includes: the updating request module is used for responding to a received data updating request sent by the cloud end equipment and judging whether a cloud end data identifier of cloud end data in the data updating request is matched with an edge end data identifier of the edge end equipment or not; and the first updating module is used for updating the edge data stored by the edge device according to the cloud data in the data updating request under the condition that the cloud data identification is not matched with the edge data identification.

In one possible implementation, the apparatus further includes: a registration request sending module, configured to initiate a registration request to the cloud device when the edge device is not registered in the cloud device; the second updating module is used for responding to difference data returned by the cloud end device aiming at the registration request, and updating the edge end data stored by the edge end device according to the difference data, wherein the difference data comprises the difference data between the edge end data of the edge end device in the registration process and the cloud end data of the cloud end device.

According to an aspect of the present disclosure, a data synchronization apparatus is provided, which is applied to a cloud device, and includes: the receiving module is used for responding to the received edge data sent by the edge equipment and determining whether the edge equipment is registered in the cloud equipment or not according to the identity information of the edge equipment; the processing module is used for processing the side data according to the side data identifier of the side data under the condition that the side equipment is registered in the cloud equipment to obtain a processing result of the side data; and the sending module is used for sending the processing result of the edge data to the edge device through a unicast channel corresponding to the edge device, wherein the unicast channel is an information transmission channel of the distributed publish-subscribe message system in a unicast mode.

In one possible implementation manner, the receiving module includes: the identity information determining submodule is used for responding to the received frontier data sent by the frontier equipment and determining whether the identity information of the frontier equipment exists in a registration list of the cloud equipment or not; a registration confirmation submodule configured to confirm that the edge device is registered in the cloud device when the identity information of the edge device already exists in the registration list; or, the unregistered determining submodule is configured to determine that the edge device is not registered in the cloud device when the identity information of the edge device does not exist in the registration list.

In one possible implementation manner, the processing module includes: the processing submodule is used for processing the edge data according to the business processing requirement corresponding to the edge data under the condition that the edge equipment is registered in the cloud equipment and the edge data is not processed based on the edge data identification; or, the communication state updating sub-module is configured to update the communication state of the edge device recorded in the cloud device according to the data receiving time of the edge data when the edge device is registered in the cloud device and it is determined that the edge data has been processed based on the edge data identifier, where the communication state includes normal communication or timeout communication.

In one possible implementation, the apparatus further includes: the update data determining module is used for responding to data update operation of the cloud end equipment and determining cloud end data corresponding to the data update operation; the update request sending module is configured to send data update requests to at least one registered edge device through a broadcast channel, so as to update the edge data of the at least one edge device, where the data update requests include the cloud data and a cloud data identifier of the cloud data.

In one possible implementation, the apparatus further includes: the registration request receiving module is used for responding to a received registration request sent by the edge device and judging whether the identity information of the edge device exists in a registration list of the cloud device or not; and the registration module is used for adding the identity information of the edge device to the registration list under the condition that the identity information of the edge device does not exist in the registration list so as to complete the registration of the edge device.

In one possible implementation, the apparatus further includes: the identification judgment module is used for judging whether an edge data identification in the registration request is matched with a cloud end data identification of the cloud end equipment or not under the condition that the identity information of the edge equipment exists in the registration list and the registration request comprises the edge data identification, wherein the edge data identification is the data identification of the edge data stored by the edge equipment; and the difference data sending module is used for sending the difference data determined based on the difference between the cloud end data and the edge end data to the edge end equipment through the unicast channel under the condition that the edge end data identification is not matched with the cloud end data identification so as to update the edge end data stored by the edge end equipment.

According to an aspect of the present disclosure, there is provided an electronic device including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to invoke the memory-stored instructions to perform the above-described method.

According to an aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the above-described method.

In the embodiment of the disclosure, under the condition that the edge device is registered in the cloud device and the edge device does not record the sending information (that is, does not send the edge data to the cloud device), the edge data is sent through the broadcast channel for distributing the subscription message, so that data synchronization can be simply and effectively realized, data consistency is ensured, a large amount of edge devices can be accessed into the cloud device without additionally increasing too much logic processing, and the expandability is high.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure.

Fig. 1 shows a flow chart of a data synchronization method according to an embodiment of the present disclosure.

Fig. 2 shows a flow diagram of a data synchronization method according to an embodiment of the present disclosure.

Fig. 3 shows a schematic diagram of a data synchronization method according to an embodiment of the present disclosure.

Fig. 4 shows a schematic diagram of a data synchronization method according to an embodiment of the present disclosure.

Fig. 5 shows a schematic diagram of a data synchronization method according to an embodiment of the present disclosure.

Fig. 6 shows a block diagram of a data synchronization apparatus according to an embodiment of the present disclosure.

Fig. 7 shows a block diagram of a data synchronization apparatus according to an embodiment of the present disclosure.

Fig. 8 illustrates a block diagram of an electronic device 1900 in accordance with an embodiment of the disclosure.

Detailed Description

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.

Fig. 1 shows a flowchart of a data synchronization method according to an embodiment of the present disclosure, which may be applied to an edge device, which may be a User Equipment (UE), a mobile device, a User terminal, a cellular phone, a cordless phone, a Personal Digital Assistant (PDA), a handheld device, a computing device, an in-vehicle device, a wearable device, a server, or other electronic devices, and the method may be implemented by a processor calling computer readable instructions stored in a memory. As shown in fig. 1, the data synchronization method includes:

in step S11, frontend data to be synchronized is acquired.

The edge device can periodically or quantitatively send data generated by the software program, data collected by the sensor and the like as edge data to be synchronized to the cloud device according to business requirements, so that subsequent business processing is performed on the edge data in the cloud device, for example, the edge data is stored in a database, and the edge data is analyzed and processed. It is understood that the disclosed embodiments are not limited to the data type of the data at the edge.

For example, the data at the edge end may include a vehicle image acquired by an image sensor, and may also include processing results such as license plate characteristics, vehicle characteristics, license plate numbers, and the like obtained by processing the vehicle image by a license plate recognition program local to the edge end device; if the data at the side end is the vehicle image, the vehicle image can be processed by a license plate recognition program local to the cloud equipment to obtain processing results such as license plate characteristics, vehicle characteristics, license plate numbers and the like, and the processing results can be stored in a database; if the data at the side end is the processing result of the vehicle image, the processing results can be directly stored in the database.

It should be understood that the frontend data may be all data local to the frontend device, or may be partial data, and the embodiment of the present disclosure is not limited thereto.

In step S12, in a case where the edge device is registered in the cloud device and the edge device does not record the sending information of the edge data, the edge data is sent to the cloud device through the broadcast channel.

The edge device is registered in the cloud device, and it can be understood that the edge device is authorized to access the cloud device, or the cloud device allows the synchronous data of the edge device. By the method, the safety and consistency of data synchronization are improved.

The sending information of the edge data is not recorded by the edge device, and it can be understood that the edge device does not send the edge data to the cloud device. It should be understood that, while sending the edge data to the cloud device through the broadcast channel, the sending information of the edge data may be recorded in a memory of the edge device, for example, may be recorded in a file under a certain storage path, or may also be stored and recorded in a database, which is not limited to this embodiment of the disclosure. By the method, the probability of repeatedly sending the data of the side end can be effectively reduced, and the consistency of data synchronization can be guaranteed.

In a possible implementation manner, the sending information includes at least one of an edge data identifier of the edge data and a data sending time. The data identifier of the edge can be understood as the version number of the edge data, and the edge data identifiers can uniquely identify the edge data of different versions; the data sending time can be understood as the time for sending the frontend data to the cloud device, the data sending time can be represented as a timestamp, and whether the frontend data is sent overtime or not can be judged by recording the data sending time, so that the frontend data can be sent again under the condition of overtime sending, and the consistency of data synchronization is ensured.

It is known that the distributed publish-subscribe messaging system may be, for example, a kafka system, in which it is specified that a topic message can only be consumed by one Consumer (Consumer) in the same Consumer Group (Consumer Group), and a plurality of Consumer groups can simultaneously consume one message, and the kafka system has two message push modes, i.e., a broadcast mode and a unicast mode, and the broadcast mode may be understood as sending one topic message to all consumers, and the unicast mode may be understood as sending one topic message to one Consumer. Based on the above, the broadcast channel is an information transmission channel of the distributed publish-subscribe message system in the broadcast mode, and the unicast channel is an information transmission channel of the distributed publish-subscribe message system in the unicast mode.

It can be understood that in the process of sending the edge data to the cloud device through the broadcast channel, the edge device is a producer, the edge device can publish the edge data to a specified topic in the distributed publishing and subscribing message system, the cloud device is a consumer, the edge data is a topic message, and the edge data can be pushed to all the cloud devices subscribing the specified topic through the broadcast channel of the distributed publishing and subscribing message system, so that the edge data can be sent to the cloud device through the broadcast channel. By the method, based on the message queue characteristics in the distributed publish-subscribe message system, the related dimension work of a bandwidth load balancing function and a container self-balancing function is reduced, the data synchronization efficiency is improved, and the consistency of data synchronization is ensured.

In the embodiment of the disclosure, under the condition that the edge device is registered in the cloud device and the edge device does not record the sending information (that is, does not send the edge data to the cloud device), the edge data is sent through the broadcast channel for distributing the subscription message, so that data synchronization can be simply and effectively realized, meanwhile, data consistency is ensured, a large amount of edge devices can be accessed into the cloud device without additionally increasing too much logic processing, and the expandability is high.

Considering that, in an actual situation, there may be a case where a data synchronization timeout occurs due to a network connection condition becoming worse, where the data synchronization timeout may not be sent out, the data synchronization timeout may have been sent out, but a processing result of the cloud device returning the data synchronization timeout is not obtained after the timeout, and the like, in a possible implementation manner, the method further includes:

step S31, when the edge device is registered in the cloud device and the edge device has recorded the sending information, determining whether the sending of the edge data is overtime according to the data sending time in the sending information.

As described above, the sending information of the edge data is recorded by the edge device, and it can be considered that the edge device has sent the edge data to the cloud device but has not received the processing result of the edge data fed back by the cloud device, at this time, it can be determined whether the time difference between the data sending time and the current time exceeds the set threshold, that is, whether the sending of the edge data is overtime, according to the data sending time recorded in the sending information at which the edge data was sent last time. If the time difference between the data sending time and the current time exceeds a set threshold, the data at the side end is considered to be sent overtime; conversely, if the time difference between the data transmission time and the current time does not exceed the set threshold, the frontend data is considered not to be transmitted overtime. It should be understood that the specific value of the set threshold may be set according to actual requirements, for example, may be set to 1 minute, 5 minutes, etc., and the embodiment of the disclosure is not limited thereto.

Step S32, in the case that the data transmission time out, resends the data of the edge to the cloud device through the broadcast channel, and updates the data transmission time in the transmission information.

When the data of the side end is sent overtime, the data sending time in the sending information is updated, and the data of the side end is sent to the cloud end equipment again through the broadcast channel. By the method, the data of the side end can be sent to the cloud end equipment as far as possible without omission, and the consistency of data synchronization is guaranteed.

In a possible implementation manner, when the side data is not sent overtime, the side device may continue to wait for a period of time until a time difference between the data sending time and the current time exceeds a set threshold, where if the side device receives a processing result of the cloud device returning the side data within the waiting period, the side data does not need to be sent again, and if the side device does not receive the processing result of the cloud device returning the side data within the waiting period, the side data may be sent again.

In the embodiment of the present disclosure, the side data can be retransmitted under the condition that the data transmission is overtime, which is beneficial to ensuring the consistency of data synchronization.

As described above, after the edge data is sent to the cloud device, the cloud device may perform subsequent service processing on the edge data, and in order to better implement cloud-edge cooperative work (i.e., cooperative work between the cloud device and the edge device), the edge device may need to know whether the cloud device has received the edge data, whether the edge data has been processed, processing information of the edge data, and the like, in a possible implementation manner, after the edge data is sent to the cloud device through a broadcast channel, the method further includes: and in response to receiving the processing result of the returned side data of the cloud terminal equipment, deleting the recorded sending information and updating the processing result of the side data recorded in the side equipment.

In a possible implementation manner, the processing result may include at least one of the edge data received by the cloud device, whether the edge data has been processed by the cloud device, and processing information of the edge data (e.g., information of the identified license plate number, the extracted license plate feature, and the like). It should be understood that the embodiments of the present disclosure are not limited to the details of the processing results.

After receiving a processing result of the edge data returned by the cloud device, deleting the recorded sending information of the edge data, which can be understood as deleting the sending information of the edge data from the memory of the edge device; it should be understood that, the sending information of some side data still exists in the memory, which represents the processing result that the side has sent the side data but has not received the side data.

In a possible implementation manner, the processing result of the edge data may be recorded in a memory of the edge device, for example, may be recorded in a file of a specified storage path of the memory, and may also be recorded in a database, which is not limited to this embodiment of the disclosure. The updating of the processing result of the edge data recorded by the edge device may be understood as updating the processing result of the edge data recorded by the edge device to a processing result returned by the cloud device, for example, updating the processing result from "unprocessed by the cloud device" to "processed by the cloud device", or updating the processing result from "not received by the cloud device" to "received by the cloud device", so as to facilitate the realization of cooperative operation between the edge device and the cloud device.

In a possible implementation manner, after receiving a processing result of the edge data returned by the cloud device, it may be determined whether the processing result has been sent, where the processing result has been sent and can be understood as a processing result that the cloud device has sent the edge data, and the processing result has not been sent and can be understood as a processing result that the cloud device has not sent the edge data; if the processing result is sent, the processing result returned by the secondary cloud device can be ignored; if the processing result is not sent, the operations of deleting the recorded sending information and updating the processing result of the frontend data recorded in the frontend device in the embodiments of the present disclosure may be performed. By the method, the situation that the cloud equipment repeatedly sends the processing result of the edge data can be effectively solved, and the cooperative operation between the edge equipment and the cloud equipment is favorably realized.

In the embodiment of the present disclosure, by deleting the recorded sending information and updating the processing result of the edge data recorded in the edge device, not only the limited storage resource of the edge device can be fully utilized, but also the cooperative operation between the edge device and the cloud device can be favorably realized.

In view of the fact that in a scenario of cloud-edge collaboration, there may be a case where the cloud device synchronizes data to the edge device, or a case where the cloud device notifies the edge device of updating data, in a possible implementation manner, the method further includes:

step S51, in response to receiving the data update request sent by the cloud device, determines whether the cloud data identifier of the cloud data in the data update request matches the edge data identifier of the edge device.

Judging whether a cloud data identifier of the cloud data in the data updating request is matched with an edge data identifier of the edge device, wherein judging whether a version of the cloud data sent by the cloud device is the same as a version of the edge data locally stored by the edge device; if the cloud data is different from the locally stored frontier data in version, that is, the cloud data identifier is not matched with the frontier data identifier, the locally stored frontier data is updated according to the cloud data, and the implementation of cooperative operation between the frontier equipment and the cloud equipment is facilitated. The cloud data may be all data or partial data local to the cloud device, and the embodiment of the present disclosure is not limited thereto.

And step S52, under the condition that the cloud data identification is not matched with the edge data identification, updating the edge data stored in the edge device according to the cloud data in the data updating request.

In a possible implementation manner, the cloud data may include, for example, an update package of a software program, an operation log of a cloud database, and the like, and the embodiment of the present disclosure does not limit the type of the cloud data. It should be understood that the updating process for updating the client data is different based on different types of cloud data.

In a possible implementation manner, in a case that the cloud data includes an update package of a software program, the edge data may include the software program already deployed in the edge device, and then updating the edge data according to the cloud data in the data update request may include: and according to the update package in the data update request, performing software update on the deployed software program in the edge device.

In a possible implementation manner, in a case that the cloud data includes an operation log of the cloud database, the frontend data may be the frontend database including the frontend device, and then, according to the cloud data in the data update request, updating the frontend data may include: and updating the side database according to the operation log in the data updating request, namely performing data synchronization between the cloud database and the side database according to the operation log sent by the cloud equipment.

It should be understood that, after receiving the data update request, the cloud data in the data update request may be stored in the cache space, so as to update the client data by using the cloud data; after the client data is updated according to the cloud data, the cloud data stored in the cache space can be deleted, so that the cache resources are fully utilized.

In the embodiment of the disclosure, under the condition that a data update request sent by the cloud device is received, the update of the edge data locally stored by the edge device is realized based on the cloud data and the cloud data identifier in the data update request, and the cooperative operation between the cloud device and the edge device is favorably realized.

In view of the fact that the edge device may not be registered in the cloud device, that is, the edge device is not authorized to access the cloud device, in a possible implementation manner, the method further includes: and under the condition that the edge device is not registered in the cloud device, sending a registration request to the cloud device through a broadcast channel, wherein the registration request is used for registering the edge device in the cloud device. By the method, the border device can be authorized to access the cloud device, so that the cloud device can process the border data sent by the border device.

In a possible implementation manner, a registration list may be set in the cloud device, and when a registration request sent by the edge device is received, identity information of the edge device, such as an IP Address (Internet Protocol Address) of the edge device, is characterized in the registration request, and is added to the registration list to complete registration of the edge device.

As described above, in a case where the edge device is not registered in the cloud device, the registration request may be sent to the cloud device through the broadcast channel. In one possible implementation, the method further includes: sending a registration request to the cloud device under the condition that the edge device is not registered in the cloud device; and in response to receiving difference data returned by the cloud end device for the registration request, updating the edge data stored by the edge device according to the difference data, wherein the difference data comprises the difference data between the edge data of the edge device in the registration process and the cloud end data of the cloud end device. By the method, the data synchronization times between the cloud equipment and the side equipment can be reduced, and the data synchronization efficiency is improved.

Considering that the edge device may have edge data locally before the edge device is not registered in the cloud device, the registration request may include an edge data identifier of the locally stored edge data, and the cloud device may determine difference data of a difference between the edge data of the edge device and the cloud data of the cloud device based on the edge data identifier in the registration request, so that the cloud device may directly send the difference data to the edge device, so that the edge device updates the edge data locally stored in the edge device based on the difference data. By the method, the data synchronization times between the cloud equipment and the side equipment can be reduced, and the data synchronization efficiency is improved.

In one possible implementation manner, the difference data may include an update package of a difference version of the software program, a difference operation log between the cloud database and the edge database, and the like, and the implementation of the present disclosure is not limited to the type of the difference data. In this embodiment of the present disclosure, the local edge data of the edge device may be updated according to the difference data, for example, software of the edge device may be updated according to an update package of a difference version; the frontend database of the frontend device may also be updated according to the difference operation log, and the like, which is not limited in this embodiment of the disclosure.

Fig. 2 is a flowchart illustrating a data synchronization method according to an embodiment of the present disclosure, where the data synchronization method may be applied to a cloud device, and the cloud device may be an electronic device such as a server or a server cluster, and the method may be implemented by executing computer readable instructions by the server. As shown in fig. 2, the data synchronization method includes:

in step S21, in response to receiving the edge data sent by the edge device, it is determined whether the edge device is registered in the cloud device according to the identity information of the edge device.

As described above, the edge device may send the edge data to the edge device through the broadcast channel of the distributed publish-subscribe message system. In a possible implementation manner, the identity information of the edge device includes information used for uniquely identifying different edge devices, such as an IP Address (Internet Protocol Address) of the edge device, a device identifier, and the like, and a registration list may be set in the cloud device, and the identity information of the edge device registered in the cloud device is stored in the registration list.

In one possible implementation manner, in response to receiving the edge data sent by the edge device, determining whether the edge device is registered in the cloud device according to the identity information of the edge device, includes: in response to receiving the edge data sent by the edge device, determining whether identity information of the edge device exists in a registration list of the cloud device; confirming that the edge device is registered in the cloud device under the condition that the identity information of the edge device exists in the registration list; or, in the case that the identity information of the edge device does not exist in the registration list, it is determined that the edge device is not registered in the cloud device. By the method, whether the edge device is authorized to access the cloud device can be quickly determined.

It should be understood that the frontend data sent by different frontend devices can be distinguished by the identity information of the frontend device. As described above, the edge device may be the edge data sent through the broadcast channel of the distributed publish-subscribe message system, so that when the edge device publishes the edge data to the specified topic subscribed by the cloud device, the distributed publish-subscribe message system may record the identity information of the edge device, and when pushing the edge data in the specified topic to the cloud device, may synchronously send the identity information corresponding to the edge data, that is, inform the cloud device of the source of the edge data, so that the cloud device processes the edge data.

In one possible implementation, the method further includes: and under the condition that the edge device is not registered in the cloud device, discarding the edge data. The method can be understood as that under the condition that the edge device is not authorized to access the cloud device, the edge data sent by the edge device is not processed, and the fact that the edge data sent by the edge device which is not authorized to access may be abnormal data is considered.

In step S22, when the edge device is registered in the cloud device, the edge data is processed according to the edge data identifier of the edge data, so as to obtain a processing result of the edge data.

As described above, the cloud device may perform subsequent service processing on the frontend data sent by the frontend device, for example, store the frontend data in a cloud database, perform a designated analysis task (for example, a feature extraction task, a classification recognition task, and the like) on the frontend data, and transmit the frontend data to a related service system (for example, a license plate recognition system, a violation detection system, a people flow rate statistics system, and the like). The processing result of the edge data may include at least one of whether the cloud device has received the edge data, whether the cloud device has processed the edge data, whether the edge data has been transmitted to a related business system, and an analysis result of a designated analysis task (e.g., information such as a recognized license plate number and extracted license plate features).

It should be understood that, based on different service processing requirements, the processing process of the edge data is different, and a person skilled in the art may develop different service processing logics in a customized manner according to different service processing requirements to process the edge data to obtain a processing result of the edge data, which is not limited in this embodiment of the disclosure.

Considering that in an actual situation, there may be a situation that the edge device repeatedly sends the same edge data, in a possible implementation manner, under a situation that the edge device is registered in the cloud device, processing the edge data according to the edge data identifier of the edge data may include: processing the edge data according to the business processing requirements corresponding to the edge data under the condition that the edge equipment is registered in the cloud equipment and the edge data is determined to be unprocessed based on the edge data identification; the business processing requirements comprise at least one of storing the edge data in a cloud database, executing a specified analysis task on the edge data, and transmitting the edge data to a related business system. By the method, the probability of repeatedly processing the edge data repeatedly sent by the edge equipment can be reduced, and the idempotent of data synchronization is favorably ensured.

As described above, the edge data identifier may uniquely identify edge data of different versions, and in a possible implementation manner, after receiving the edge data sent by the edge device each time, the cloud device may record, for example, receiving information such as the edge data identifier and the data receiving time of the edge data sent by the edge device each time based on a data synchronization log, so that in a case of receiving the edge data sent by the edge device each time, by looking up whether the edge data identifier exists in the data synchronization log, it is determined whether the currently received edge data has been synchronized, or whether the cloud device has received the edge data.

It should be understood that, if the data synchronization log records the edge data identifier of the currently sent edge data, it may be considered that the edge data is synchronized, that is, the cloud device has received the edge data, and in this case, the processing result of the edge data may be directly returned to the edge device; on the contrary, if the edge data identifier of the currently sent edge data is not recorded in the data synchronization log, it may be considered that the edge data is not synchronized, that is, the cloud device does not receive the edge data.

In some scenarios, the edge data received by the cloud device may need to be sent to different service systems for processing, and then the processing result of the edge data by the different service systems may be obtained by using a customized callback function in a manner of interface call, which is not limited in the embodiment of the present disclosure.

Considering that in a scenario of cloud-edge collaboration, it is generally further required to record a communication state between the cloud device and the edge device, in a possible implementation manner, the method further includes: and under the condition that the edge device is registered in the cloud device and the edge data is determined to be processed based on the edge data identifier, updating the communication state of the edge device recorded in the cloud device according to the data receiving time of the edge data, wherein the communication state comprises normal communication or overtime communication. Through this mode, can effectively record the communication state between high in the clouds equipment and the limit end equipment.

The timeout communication may be understood as that the edge device has exceeded a certain time length and has not communicated with the cloud device, that is, the edge device has exceeded the certain time length and has not synchronized data with the cloud device, or a time difference between the current sending of the edge data by the edge device and the last sending of the edge data exceeds the certain time length; correspondingly, the normal communication can be understood as that the time difference between the current sending of the edge data and the last sending of the edge data by the edge device does not exceed a certain time length, that is, the edge device does not exceed the certain time length to synchronize data to the cloud device. The communication state of the edge device may also be recorded in the data synchronization log, for example, and the recording manner of the communication state is not limited in the embodiment of the present disclosure.

In a possible implementation manner, updating the communication state of the edge device recorded in the cloud device according to the data receiving time of the edge data may include: judging whether the time difference exceeds a certain time threshold or not according to the time difference between the data receiving time of the edge side data sent by the edge side equipment locally and the data receiving time of the edge side data sent by the edge side equipment last time; if the time difference exceeds a certain time threshold, updating the communication state of the edge device recorded in the cloud device into overtime communication; if the time difference does not exceed a certain time threshold, the communication state of the edge device recorded in the cloud device can be updated to be normal communication.

In step S23, the processing result of the edge data is sent to the edge device through a unicast channel corresponding to the edge device, where the unicast channel is an information sending channel of the distributed publish-subscribe message system in the unicast mode.

As described above, the unicast mode may be understood as sending a theme message to a consumer, when the cloud device sends a processing result to the edge device, the cloud device may be understood as a publisher, the processing result may be understood as a theme message, the edge device may be understood as a consumer, the cloud device may publish the processing result to a specified theme corresponding to the edge device (for example, a theme in which an IP address of the edge device is used as a flag), and then the distributed publish-subscribe message system may push the processing result in the specified theme to the edge device subscribing to the specified theme, that is, the processing result of sending the edge data to the edge device through a unicast channel corresponding to the edge device is also achieved.

In the embodiment of the disclosure, under the condition that the edge device is registered in the cloud device, the edge data sent by the cloud device is processed, and the processing result of the edge data is sent to the edge device through the unicast channel for distributing the subscription message, so that data synchronization can be simply and effectively realized, data consistency is ensured, a large amount of edge devices can be accessed into the cloud device without extra logic processing, and the expandability is high.

step S41: in response to a data update operation for the cloud device, cloud data corresponding to the data update operation is determined.

As described above, in a possible implementation manner, the data update operation for the cloud device may be understood as an update operation for cloud local data stored locally by the cloud device, and the cloud local data may include a cloud database, so the update operation for the cloud local data, for example, may be an operation of adding, deleting, modifying, and the like to the cloud database, where the update operation for the cloud database may be abstracted into an operation log, or the update operation for the cloud database is recorded by the operation log, so as to obtain the cloud data corresponding to the update operation.

In a possible implementation manner, the cloud data may include a software program, and then, for a data update operation of the cloud device, for example, an upgrade development operation on the software program may be performed to obtain an update package for performing software update on the software program, that is, to obtain the cloud data corresponding to the data update operation.

Step S42: and respectively sending a data updating request to the registered at least one edge device through a broadcast channel so as to update the edge data of the at least one edge device, wherein the data updating request comprises cloud data and a cloud data identifier of the cloud data.

As described above, the broadcast channel is an information transmission channel of the distributed publish-subscribe messaging system in a broadcast mode, the broadcast mode may be understood as sending a topic message to all consumers, when the cloud device sends a data update request to at least one edge device through the broadcast channel, the cloud device may publish the data update request to a specified topic, and push the data update request in the specified topic to at least one edge device subscribing to the specified topic through the broadcast mode by using the distributed publish-subscribe messaging system, so as to update the edge data of at least one edge device.

In this embodiment, the manner of updating the edge data of the edge device in the embodiment of the present disclosure may be referred to, and the edge data of at least one edge device is updated according to the cloud data in the data update request and the data identifier of the cloud data, which is not described herein again.

In the embodiment of the disclosure, under the condition that the edge local data of the cloud device is updated, the data update request can be respectively sent to at least one registered edge device through the broadcast channel, so that the edge local data of each edge device can be updated, and the cooperative operation between the cloud device and the edge device can be favorably realized.

As described above, the edge device may send a registration request to the cloud device to authorize access to the cloud device. In one possible implementation, the method further includes: in response to receiving a registration request sent by the edge device, judging whether identity information of the edge device exists in a registration list of the cloud device; and under the condition that the identity information of the edge device does not exist in the registration list, adding the identity information of the edge device into the registration list to complete the registration of the edge device. By the method, the registration of a large number of edge devices can be efficiently realized, and the expandability is high.

As described above, if the identity information of the edge device already exists in the registration list, it means that the edge device is already registered in the cloud device, which may be a case where a reconnection is interrupted (for example, the edge device is powered off and restarted) in a communication between the edge device and the cloud device, and the edge device may send a registration request to the cloud device through a broadcast channel of the distributed subscription and publication message system, and may also subscribe to a specified topic, and the like, so as to recover a communication connection with the cloud device.

Correspondingly, if the identity information of the edge device does not exist in the registration list, it means that the edge device is not registered in the cloud device, and after receiving the registration request sent by the edge device, the identity information of the edge device, such as the IP address of the edge device, in the registration request may be added to the registration list to complete the registration of the edge device.

As described above, considering that the edge device may have edge local data locally before the edge device is not registered in the cloud device, the registration request may include an edge local data identifier of the edge local data, and the cloud device may determine difference data of a difference between the edge local data of the edge device and the cloud local data of the cloud device based on the edge local data identifier in the registration request, so that the cloud device may directly send the difference data to the edge device, so that the edge device updates the edge local data of the edge device based on the difference data.

In one possible implementation, the method further includes: under the condition that the identity information of the edge device exists in the registration list and the registration request comprises an edge data identifier, judging whether the edge data identifier in the registration request is matched with the cloud data identifier of the cloud device or not, wherein the edge data identifier is a data identifier of the edge data stored by the edge device; and under the condition that the edge data identification is not matched with the cloud data identification, sending difference data determined based on the difference between the cloud data and the edge data to the edge equipment through a unicast channel so as to update the edge data stored by the edge equipment. By the method, the data synchronization times between the cloud equipment and the side equipment can be reduced, and the data synchronization efficiency is improved.

The identity information of the edge device already exists in the registration list, and the edge data identifier of the edge device is included in the registration request, so that the fact that the edge device is authorized to access the cloud device can be understood, the edge data is locally stored in the edge device, the edge data identifier of the locally stored edge data is sent to the cloud device, the difference data determined by the cloud device can be directly sent to the edge device through unicast information, and the data synchronization efficiency is improved.

Judging whether the edge data identifier in the registration request is matched with the cloud data identifier of the cloud device, wherein judging whether the version of the edge data locally stored by the edge device is the same as the version of the cloud data locally stored by the cloud device; if the versions of the edge data and the cloud data are different, namely the edge data identifier is not matched with the cloud data identifier, determining difference data between the cloud data and the edge data, and sending the difference data to the edge device through a unicast channel; if the edge data and the cloud data have the same version, that is, the edge data identifier matches the cloud data identifier, sending a registration result to the edge device through a unicast channel, where the registration result may include a registration success or a registration failure, and for example, when the cloud device considers that the edge device is abnormal, the identity information of the edge device is not added to the registration list of the cloud device.

As described above, the difference data may include an update package of a difference version of the software program, a difference operation log between the cloud database and the edge database, and the like, and the disclosure is not limited to the type of the difference data. In reference to the implementation manner of updating the edge data of the edge device according to the cloud data in the embodiment of the present disclosure, the edge data of the edge device is updated according to the difference data, for example, software of a software program of the edge device may be updated according to an update package of the difference version; the frontend database of the frontend device may also be updated according to the difference operation log, and the like, which is not limited in this embodiment of the present disclosure.

In one possible implementation, the method further includes: under the condition that the identity information of the edge device exists in the registration list and the registration request does not include the edge data identifier, the cloud data can be used as difference data and sent to the edge device through a unicast channel so as to update the edge data of the edge device. By the method, the data synchronization times between the cloud equipment and the side equipment can be reduced, and the data synchronization efficiency is improved.

The identity information of the edge device already exists in the registration list and the registration request does not include the edge data identifier, which can be understood that the edge device is authorized to access the cloud device and the edge device does not have edge data locally, meaning that the edge device may be a new device, no related software program is deployed locally, no data is stored in the edge database, and the like, and the cloud data can be directly used as difference data and directly sent to the edge device through unicast information, so that the data synchronization efficiency is improved, for example, a data packet of a latest version of the software program in the cloud device is used as the difference data, or all operation logs of the cloud database are used as the difference data, and the like, and the embodiment of the present disclosure is not limited.

In order to better implement cloud-side cooperative work, the cloud end device may feed back a registration result to the edge end device, so that the edge end device may execute subsequent business logic after receiving the registration result, for example, send edge end data to be synchronized to the cloud end device, and in one possible implementation, the method further includes: and sending a registration result to the edge device through a unicast channel under the condition that the edge data identifier is matched with the cloud data identifier or the difference data is sent to the edge device. By the method, the cooperative operation between the cloud equipment and the edge equipment can be better realized.

The registration result may include that the registration is successful, which means that the edge device authorizes to access the cloud device; the registration failure may also be included, which means that the edge device is not authorized to access the cloud device, for example, if the cloud device considers that the edge device is abnormal, the identity information of the edge device is not added to the registration list of the cloud device.

Fig. 3 shows a schematic diagram of a data synchronization method according to an embodiment of the present disclosure, as shown in fig. 3, the data synchronization method includes:

the method comprises the steps that edge-end equipment determines edge-end data to be synchronized and generates edge-end data identification of the edge-end data; judging whether the side data identifier is recorded in the memory of the side equipment, namely judging whether the sending information of the side data is recorded in the memory; if the data identification of the side end is not recorded in the memory, recording the sending information of the side end data in the memory, and sending the side end data to the cloud end equipment through a broadcast channel;

if the data identification of the side end is recorded in the memory, judging whether the time difference between the data sending time of the last sending of the side end data and the current time exceeds a set threshold value or not; if the time difference between the data sending time of the last sending of the data of the side end and the current time does not exceed the set threshold, waiting for a period of time until the time difference between the data sending time of the last sending and the current time exceeds the set threshold; if the time difference between the last sending time of the side data and the current time exceeds a set threshold, updating the data sending time of the side data in the record sending information in the memory, and resending the side data to the cloud equipment through a broadcast channel;

after receiving the edge data sent by the edge device, the cloud device can analyze the edge data and judge whether the identity information of the edge device exists in a registration list of the cloud device; if the identity information of the edge-side equipment does not exist in the registration list of the cloud-side equipment, discarding the edge-side data; if the identity information of the edge device exists in the registration list of the cloud device, judging whether the edge data are synchronized; if the data of the side end is synchronized, the communication state of the side end equipment recorded in the cloud end equipment can be directly updated, and the processing result of the data of the side end is sent to the side end equipment through a unicast channel;

if the data of the side end is not synchronized, the data synchronization log can be updated, that is, the side end data identification, the data receiving time and other receiving information of the side end data are recorded in the data synchronization log, a user-defined callback function is executed to obtain the processing result of the side end data, and the processing result is sent to the side end equipment through a unicast channel;

after receiving and analyzing the processing result fed back by the cloud end device, the edge end device can judge whether the processing result is sent; if the processing result is sent, the processing result returned by the secondary cloud device can be ignored; and if the processing result is not sent, deleting the sending information of the edge data recorded in the memory, and updating the processing result of the edge data recorded in the edge equipment.

The data synchronization method of the embodiment of the present disclosure can be briefly described as follows: when the edge device reports data, determining the reported edge data and sending information such as an edge data identifier, the sending time, a processing result and the like of the reported edge data, recording the sending information into a storage system of a memory, and transmitting the edge data to the cloud device through a broadcast channel; after the cloud end equipment receives the reported side end data, judging whether the reported side end data is consumed by the cloud end equipment (namely whether the reported side end data is synchronized) according to the side end data identification, ensuring the idempotent of data synchronization, if the side end data is not consumed, processing the side end data, and returning a processing result to the side end equipment; after the edge device receives the processing result, whether the processing result is sent or not is judged through the edge data identifier in the processing result, if the processing result is sent, the processing result is ignored, and if the processing result is not sent, the processing result of the edge data recorded by the edge device is updated; and judging whether the sending of the data of the side end is overtime according to the sending time corresponding to the data identification of the side end, and if the sending of the data of the side end is overtime, resending the data of the side end, so as to ensure the consistency of data synchronization.

In the embodiment of the disclosure, data synchronization can be simply and effectively realized, data consistency is ensured, a large amount of edge devices can be accessed to the cloud device without extra logic processing, and the expandability is high.

Fig. 4 shows a schematic diagram of a data synchronization method according to an embodiment of the present disclosure, as shown in fig. 4, the data synchronization method includes:

the method comprises the steps that updating operation exists in cloud local data of a cloud device, and cloud data identification corresponding to the updating operation are determined; sending a data updating request to at least one registered edge device through a broadcast channel, wherein the data updating request comprises cloud data and a cloud data identifier; after receiving the data updating request, the edge device can analyze the data updating request, judge whether a cloud data identifier in the data updating request is the same as an edge local data identifier of edge local data local to the edge device, ignore the data updating request if the cloud local data identifier is the same as the edge local data identifier, and delete the cached cloud data; and if the cloud local data identification is different from the edge local data identification, updating the edge local data according to the cloud data, and deleting the cached cloud data.

The data synchronization method of the embodiment of the present disclosure can be briefly described as follows: when the cloud end equipment updates local cloud end local data, the cloud end equipment is informed to synchronously update the data; the cloud end equipment informs the registered edge end equipment of the updated cloud end data and the corresponding cloud end data identification through a broadcast channel; after receiving the update notification (namely, the data update request), the edge device judges whether the cloud data identifier in the data update request is the same as the local edge local data identifier of the edge device, and if not, the edge device updates the local edge local data of the edge device according to the cloud data; and after the data is updated, if cached cloud data exists, deleting the cached cloud data, wherein the caching position of the cloud data is configured through a configuration file.

Fig. 5 shows a schematic diagram of a data synchronization method according to an embodiment of the present disclosure, as shown in fig. 5, the data synchronization method includes:

the method comprises the steps that an edge device sends a registration request to a cloud device through a broadcast channel; the cloud end equipment analyzes the registration request and judges whether the identity information of the side end equipment exists in the registration list or not; if the identity information of the edge device does not exist in the registration list, adding the identity information of the edge device into the registration list to complete the registration of the edge device; judging whether the registration request contains the edge local data identifier of the edge local data local to the edge device or not under the condition that the identity information of the edge device exists in the registration list or the identity information of the edge device is added to the registration list;

if the registration request does not contain the edge local data identifier, the cloud local data is used as difference data and sent to the edge device through a unicast channel; if the registration request contains the edge local data identifier, judging whether the edge local data identifier in the registration request is the same as the cloud local data identifier of the cloud device; if the edge local data identifier in the registration request is the same as the cloud local data identifier, directly sending a registration result to the edge device through a unicast channel, and executing a self-defined service logic after the edge device receives the registration result;

if the edge local data identifier in the registration request is different from the cloud local data identifier, sending differential data determined based on the difference between the cloud local data and the edge local data to the edge device through a unicast channel, and sending a registration result to the edge device through the unicast channel; and the edge device updates the local data of the edge based on the received difference data.

The data synchronization method of the embodiment of the present disclosure can be briefly described as follows: the method comprises the steps that the edge device sends a registration request to the cloud device through a broadcast channel, wherein the registration request can comprise an edge local data identifier of edge local data local to the edge device; the cloud end equipment adds the identity information of the edge end equipment into a registration list, or adds the identity information into an edge end management database, simultaneously checks whether an edge end local data identifier in a registration request is the same as a cloud end local data identifier, directly feeds back a registration result if the edge end local data identifier is the same as the cloud end local data identifier, and transmits the difference data of the latest version to the edge end equipment by using a unicast channel corresponding to the edge end equipment if the edge end local data identifier is not the same as the cloud end local data identifier; and after receiving the latest difference data, the edge terminal updates the data and executes a self-defined callback function to complete the subsequent service logic.

The data synchronization method can be applied to an expressway charge auditing system, and can be understood that in an expressway charge auditing scene, the data of vehicle pictures shot by a toll station every day is huge, and the processing amount of further analyzing the vehicle characteristics and the license plate characteristics to be stored in a characteristic library is larger; according to the data synchronization method disclosed by the embodiment of the disclosure, a user can modify an original single-machine system into a cloud-side cooperative framework, a plurality of side ends are distributed in different toll booths, images acquired by a camera are sent to side-end equipment, the side-end equipment analyzes and processes the images and sends analysis and processing results to cloud-end equipment, and the processing effect of the whole highway charging audit system is favorably improved.

According to the embodiment of the disclosure, a small amount of code modification can be performed on a single system, so that the single system is expanded to a cloud side cooperative system, namely cooperative operation between cloud side equipment and a large amount of side end equipment is realized; the expandability and the processing performance of the whole data synchronization system can be improved;

according to the embodiment of the disclosure, the kafka system is used for data communication, so that the data loss rate in the communication process is reduced, the data consistency is ensured without adding excessive retransmission mechanisms, the code change rate is reduced, and the data synchronization consistency and the idempotent are ensured;

it is understood that the above-mentioned method embodiments of the present disclosure can be combined with each other to form a combined embodiment without departing from the logic of the principle, which is limited by the space, and the detailed description of the present disclosure is omitted. Those skilled in the art will appreciate that in the above methods of the specific embodiments, the specific order of execution of the steps should be determined by their function and possibly their inherent logic.

In addition, the present disclosure also provides a data synchronization apparatus, an electronic device, a computer-readable storage medium, and a program, which can be used to implement any data synchronization method provided by the present disclosure, and the corresponding technical solutions and descriptions and corresponding descriptions in the method section are not repeated.

Fig. 6 is a block diagram illustrating a data synchronization apparatus according to an embodiment of the present disclosure, which may be applied to an edge device, as shown in fig. 6, the apparatus including:

an obtaining module 101, configured to obtain edge data to be synchronized;

the synchronization module 102 is configured to send the edge data to the cloud device through a broadcast channel when the edge device is registered in the cloud device and the edge device does not record sending information of the edge data, where the broadcast channel is an information transmission channel of a distributed publish-subscribe message system in a broadcast mode.

Fig. 7 is a block diagram of a data synchronization apparatus according to an embodiment of the present disclosure, as shown in fig. 7, the data synchronization apparatus may be applied to a cloud device, and the apparatus includes:

the receiving module 201 is configured to, in response to receiving edge data sent by an edge device, determine whether the edge device is registered in the cloud device according to identity information of the edge device;

the processing module 202 is configured to, when the edge device is registered in the cloud device, process the edge data according to an edge data identifier of the edge data, so as to obtain a processing result of the edge data;

a sending module 203, configured to send the processing result of the edge data to the edge device through a unicast channel corresponding to the edge device, where the unicast channel is an information transmission channel of the distributed publish-subscribe message system in a unicast mode.

In a possible implementation manner, the receiving module 201 includes: the identity information determining submodule is used for responding to the received frontier data sent by the frontier equipment and determining whether the identity information of the frontier equipment exists in a registration list of the cloud equipment or not; a registration confirmation submodule configured to confirm that the edge device is registered in the cloud device when the identity information of the edge device already exists in the registration list; or, the unregistered determining submodule is configured to determine that the edge device is not registered in the cloud device when the identity information of the edge device does not exist in the registration list.

In a possible implementation manner, the processing module 202 includes: the processing submodule is used for processing the edge data according to the business processing requirement corresponding to the edge data under the condition that the edge equipment is registered in the cloud equipment and the edge data is not processed based on the edge data identification; or, the communication state updating sub-module is configured to update the communication state of the edge device recorded in the cloud device according to the data receiving time of the edge data when the edge device is registered in the cloud device and it is determined that the edge data has been processed based on the edge data identifier, where the communication state includes normal communication or timeout communication.

In some embodiments, functions of or modules included in the apparatus provided in the embodiments of the present disclosure may be used to execute the method described in the above method embodiments, and specific implementation thereof may refer to the description of the above method embodiments, and for brevity, will not be described again here.

Embodiments of the present disclosure also provide a computer-readable storage medium having stored thereon computer program instructions, which when executed by a processor, implement the above-mentioned method. The computer readable storage medium may be a volatile or non-volatile computer readable storage medium.

An embodiment of the present disclosure further provides an electronic device, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to invoke the memory-stored instructions to perform the above-described method.

The disclosed embodiments also provide a computer program product comprising computer readable code or a non-transitory computer readable storage medium carrying computer readable code, which when run in a processor of an electronic device, the processor in the electronic device performs the above method.

The electronic device may be provided as an edge device, a cloud device, or other form of device.

Fig. 8 illustrates a block diagram of an electronic device 1900 in accordance with an embodiment of the disclosure. For example, electronic device 1900 may be provided as an edge device or a cloud device. Referring to fig. 8, electronic device 1900 includes a processing component 1922 further including one or more processors and memory resources, represented by memory 1932, for storing instructions, e.g., applications, executable by processing component 1922. The application programs stored in memory 1932 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1922 is configured to execute instructions to perform the above-described method.

The electronic device 1900 may also include a power component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input/output (I/O) interface 1958. The electronic device 1900 may operate based on an operating system, such as the Microsoft Server operating system (Windows Server), stored in the memory 1932^TM) Apple Inc. of the present application based on the graphic user interface operating System (Mac OS X)^TM) Multi-user, multi-process computer operating system (Unix)^TM) Free and open native code Unix-like operating System (Linux)^TM) Open native code Unix-like operating System (FreeBSD)^TM) Or the like.

In an exemplary embodiment, a non-transitory computer readable storage medium, such as the memory 1932, is also provided that includes computer program instructions executable by the processing component 1922 of the electronic device 1900 to perform the above-described methods.

The present disclosure may be systems, methods, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement various aspects of the present disclosure.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted over electrical wires.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry that can execute the computer-readable program instructions implements aspects of the present disclosure by utilizing the state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The computer program product may be embodied in hardware, software or a combination thereof. In an alternative embodiment, the computer program product is embodied in a computer storage medium, and in another alternative embodiment, the computer program product is embodied in a Software product, such as a Software Development Kit (SDK), or the like.

If the technical scheme of the application relates to personal information, a product applying the technical scheme of the application clearly informs personal information processing rules before processing the personal information, and obtains personal independent consent. If the technical scheme of the application relates to sensitive personal information, a product applying the technical scheme of the application obtains individual consent before processing the sensitive personal information, and simultaneously meets the requirement of 'express consent'. For example, at a personal information collection device such as a camera, a clear and significant identifier is set to inform that the personal information collection range is entered, the personal information is collected, and if the person voluntarily enters the collection range, the person is regarded as agreeing to collect the personal information; or on the device for processing the personal information, under the condition of informing the personal information processing rule by using obvious identification/information, obtaining personal authorization by modes of popping window information or asking a person to upload personal information of the person by himself, and the like; the personal information processing rule may include information such as a personal information processor, a personal information processing purpose, a processing method, and a type of personal information to be processed.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or improvements to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A data synchronization method is applied to an edge device, and comprises the following steps:

acquiring edge data to be synchronized;

and under the condition that the edge device is registered in a cloud device and does not record the sending information of the edge data, sending the edge data to the cloud device through a broadcast channel, wherein the broadcast channel is an information transmission channel of the distributed publish-subscribe message system in a broadcast mode.

2. The method of claim 1, wherein the sending information comprises a sending time of the frontend data, and wherein the method further comprises:

under the condition that the edge device is registered in the cloud device and the sending information is recorded by the edge device, judging whether the sending of the edge data is overtime or not according to the data sending time in the sending information;

and under the condition that the data of the side end is sent overtime, the data of the side end is sent to the cloud end equipment again through the broadcast channel, and the data sending time in the sending information is updated.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

responding to a received data updating request sent by the cloud end equipment, and judging whether a cloud end data identifier of cloud end data in the data updating request is matched with an edge end data identifier of the edge end equipment or not;

and under the condition that the cloud data identification is not matched with the edge data identification, updating the edge data stored by the edge equipment according to the cloud data in the data updating request.

4. The method according to any one of claims 1-3, further comprising:

when the edge device is not registered in the cloud device, initiating a registration request to the cloud device;

in response to receiving difference data returned by the cloud end device for the registration request, updating the edge end data stored by the edge end device according to the difference data, wherein the difference data comprises data of difference between the edge end data of the edge end device in the registration process and the cloud end data of the cloud end device.

5. A data synchronization method is applied to cloud equipment and comprises the following steps:

in response to receiving the edge data sent by the edge device, determining whether the edge device is registered in the cloud device according to the identity information of the edge device;

under the condition that the edge device is registered in the cloud device, processing the edge data according to the edge data identifier of the edge data to obtain a processing result of the edge data;

and sending the processing result of the edge data to the edge device through a unicast channel corresponding to the edge device, wherein the unicast channel is an information transmission channel of the distributed publish-subscribe message system in a unicast mode.

6. The method of claim 5, wherein the determining whether the edge device is registered with the cloud device according to the identity information of the edge device in response to receiving the edge data sent by the edge device comprises:

in response to receiving the edge data sent by the edge device, determining whether the identity information of the edge device exists in a registration list of the cloud device;

confirming that the edge device is registered in the cloud device under the condition that the identity information of the edge device exists in the registration list; or the like, or, alternatively,

and under the condition that the identity information of the edge device does not exist in the registration list, confirming that the edge device is not registered in the cloud device.

7. The method according to claim 5 or 6, wherein the processing the frontend data according to the frontend data identifier of the frontend data in a case that the frontend device is registered in the cloud device includes:

processing the side end data according to the business processing requirement corresponding to the side end data under the condition that the side end equipment is registered in the cloud end equipment and the side end data is not processed based on the side end data identification; or the like, or, alternatively,

and under the condition that the edge device is registered in the cloud device and the edge data is determined to be processed based on the edge data identifier, updating the communication state of the edge device recorded in the cloud device according to the data receiving time of the edge data, wherein the communication state comprises normal communication or overtime communication.

8. The method according to any one of claims 5-7, further comprising:

responding to a data updating operation of the cloud end equipment, and determining cloud end data corresponding to the data updating operation;

the method comprises the steps of respectively sending data updating requests to at least one registered edge device through a broadcast channel so as to update edge data of the at least one edge device, wherein the data updating requests comprise cloud data and cloud data identification of the cloud data.

9. The method according to any one of claims 5-8, further comprising:

in response to receiving a registration request sent by the edge device, judging whether identity information of the edge device exists in a registration list of the cloud device;

and under the condition that the identity information of the edge device does not exist in the registration list, adding the identity information of the edge device into the registration list to complete the registration of the edge device.

10. The method of claim 9, further comprising:

under the condition that the identity information of the edge device exists in the registration list and the registration request comprises an edge data identifier, judging whether the edge data identifier in the registration request is matched with the cloud data identifier of the cloud device, wherein the edge data identifier is the data identifier of the edge data stored by the edge device;

and under the condition that the edge data identification is not matched with the cloud data identification, sending difference data determined based on the difference between the cloud data and the edge data to the edge equipment through the unicast channel so as to update the edge data stored by the edge equipment.

11. A data synchronization device is applied to an edge device and comprises

The acquisition module is used for acquiring the data of the side end to be synchronized;

the synchronization module is used for sending the edge data to the cloud device through a broadcast channel under the condition that the edge device is registered in the cloud device and the edge device does not record the sending information of the edge data, wherein the broadcast channel is an information transmission channel of the distributed publishing and subscribing message system in a broadcast mode.

12. The utility model provides a data synchronizer, its characterized in that is applied to high in the clouds equipment, includes:

the receiving module is used for responding to the received edge data sent by the edge equipment and determining whether the edge equipment is registered in the cloud equipment or not according to the identity information of the edge equipment;

the processing module is used for processing the side data according to the side data identifier of the side data under the condition that the side equipment is registered in the cloud equipment to obtain a processing result of the side data;

and the sending module is used for sending the processing result of the edge data to the edge device through a unicast channel corresponding to the edge device, wherein the unicast channel is an information transmission channel of the distributed publish-subscribe message system in a unicast mode.

13. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to invoke the memory-stored instructions to perform the method of any one of claims 1 to 10.

14. A computer readable storage medium having computer program instructions stored thereon, which when executed by a processor implement the method of any one of claims 1 to 10.