CN103024049B - Realize the system that browser data is synchronous - Google Patents

Abstract

The invention relates to a system for synchronizing browser data. The system includes: a cloud storage server, a push server, multiple browser clients, and a socket server, wherein: the cloud storage server is used for When updating, send condition information and command information to the push server; the push server is used to determine the target client among the plurality of browser clients according to the condition information, and send the command information to all browser clients. The socket server connected to the target client; and the target client is used to realize data synchronization with the cloud storage server according to the command information; the socket server is used to send the command information from the push server to the corresponding target client. The invention can realize high-efficiency transmission of synchronous data, shorten execution time, reduce resource consumption, improve system efficiency, and improve real-time performance of services.

Description

A system for synchronizing browser data

technical field

The invention relates to the field of information technology data synchronization, in particular to a system for realizing browser data synchronization.

Background technique

At present, with the development of network technology, the Internet, as a huge information resource, has become the most convenient and fast way for people to obtain information. At present, a user usually uses a personal computer to access the Internet (Internet), and accesses a webpage through a browser installed in the personal computer to obtain required information. With the development of mobile communication technologies, users can also access the Internet through mobile terminals supporting browser functions, such as mobile phones and personal digital assistants (Personal Digital Assistant, PDA for short).

However, whether it is a browser on a personal computer or a browser on a mobile terminal, generally no push service is provided, and the information interaction between the server and the client depends on the connection initiated by the client, and the server cannot actively send information to the client , so that real-time synchronization of information between the server and the browser client cannot be realized.

In the prior art, the most commonly used way to synchronize browser data between the browser client and the server is that the browser client sends a request to the server at a certain frequency, such as once a week or once a month. Updates to the information capture this information. However, the applicant found that this data synchronization method has the following technical defects: relatively low efficiency, takes up a lot of resources, and cannot achieve true real-time synchronous update of content.

In addition, in the prior art, a socket (socket) service is often used to establish a connection between the server and the client. The so-called socket is a communication method between the client and the server in the network. When the server and the client need to When establishing a connection and transmitting data, it is necessary to connect the server with the client (target client) that needs to be connected, and the socket can be regarded as the "docking number" of this connection, only the "docking number" between the server and the target client "Docking number" is the same, to be able to connect to transmit data. The socket service is a docking service for the server and the client. However, a common socket service adopts a synchronous scheduling method when implementing data push to multiple clients, that is, after the socket server sends a message to a client, it waits for the client to receive and confirm, and then down A client pushes messages. Moreover, the general socket service adopts the http protocol, which will occupy more system resources, and will cause rapid consumption of resources when the business volume is large, thereby reducing the real-time performance of data synchronization.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a system for implementing browser data synchronization that overcomes the above problems or at least partially solves the above problems.

The present invention proposes a system for synchronizing browser data. The system includes: a cloud storage server, a push server, multiple browser clients, and a socket server, wherein the cloud storage server is used to When updating, send condition information and command information to the push server; the push server is used to determine the target client among the plurality of browser clients according to the condition information, and send the command information to the The target client; and the target client, used to realize data synchronization with the cloud storage server according to the command information; the socket server is used to send the command information from the push server to the corresponding target client .

Optionally, the socket server includes a connection module configured to establish a socket connection with the browser client, wherein when the browser client initiates a connection with the socket server When connecting, the connection module accepts the connection and obtains the resource identifier of the connection.

According to a specific implementation manner of the present invention, the connection module is further configured to receive the connection identifier sent from the browser client via the connection; the socket server further includes a verification module, and the verification module The method is used for: when receiving the connection identifier sent from the browser client, querying the distribution information database to verify whether the connection identifier exists in the distribution information database.

According to a specific implementation manner of the present invention, the verification module is further configured to: when the connection identifier exists in the distribution information database, store the resource identifier in the distribution information database.

According to a specific implementation manner of the present invention, the verification module is further configured to: when the connection identifier does not exist in the distribution information database, instruct the connection module to disconnect the connection.

According to a specific embodiment of the present invention, the socket server further includes a query module, when the push server sends the condition information and command information to the socket server assigned to the target client, the query The module queries the distribution information database according to the condition information to determine the target client.

According to a specific implementation manner of the present invention, the connection module determines the target client by querying the resource identifier in the distribution information database according to the condition information.

According to a specific implementation manner of the present invention, when the socket server receives the command information and has determined the target client according to the condition information, and there are more than one target client, the connection module sends a After the command message, send the command message directly to the next client without waiting for its receipt confirmation.

According to a specific implementation manner of the present invention, the connection module uses the transmission control protocol to connect with the browser client and send command information.

Optionally, the system also includes a distributor for distributing socket servers connected to the browser client; the distributor also includes: a distribution information database for storing information related to socket server distribution

As can be seen from the foregoing technical solutions, the present invention has the following beneficial effects:

(1) Through the socket server, the distributor and the distribution information database, the connection between the cloud storage server, the push server and the target client is successfully realized;

(2) The socket server of the present invention adopts an asynchronous scheduling mode, thereby achieving efficient transmission of data, further shortening execution time, improving system efficiency and reducing the time difference between different clients receiving messages, and improving real-time performance of services.

(3) The present invention adopts a lower transmission control protocol (TransmissionControlProtocol) when realizing the socket server, so as to realize the reduction of resource consumption and improve the service processing capability of the system under the condition of limited resources.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same components. In the attached picture:

FIG. 1 is a schematic structural diagram of a system for realizing browser data synchronization according to an embodiment of the present invention;

2 is a schematic structural diagram of a system for realizing browser data synchronization according to another embodiment of the present invention;

Fig. 3 is a schematic diagram of the process of establishing a connection between the browser client and the socket server in the system for realizing browser data synchronization shown in Fig. 2;

Fig. 4 is a schematic diagram of the process of pushing information to the target client in the first type of scenario in the system for realizing browser data synchronization shown in Fig. 2;

Fig. 5 is a schematic diagram of the process of pushing information to the target client in the second type of scenario in the system for implementing browser data synchronization shown in Fig. 2;

Fig. 6 is a schematic diagram of the process of pushing information to the target client in the third type of scenario in the system for realizing browser data synchronization shown in Fig. 2;

7 is a flowchart of a method for implementing browser data synchronization according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a browser client implementing browser data synchronization according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a socket server according to an embodiment of the present invention;

FIG. 10 is a flowchart of a socket service method applied to a socket server according to an embodiment of the present invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

In an exemplary embodiment of the present invention, a system for implementing browser data synchronization is provided. As shown in FIG. 1 , the system for synchronizing browser data includes: a cloud storage server 1 , a push server 2 and multiple browser clients 3 and 4 . Among them, the cloud storage server 1 is used to send condition information and command information to the push server when there is data update; the push server 2 is used to determine the target client among multiple browser clients according to the condition information, and send The command information is pushed to the target client 3; the target client 3 is used to realize data synchronization between the target client and the cloud storage server according to the command information.

In the embodiment shown in Figure 1, by setting up a separate push server 2, when the data content stored at the cloud storage server end is updated, the command information is sent to the target client through the push server in time, so that it is simple, Efficiently realize the real-time synchronization of server-side information and client-side information.

As shown in FIG. 1 , multiple browser clients include an initiating client 4 and a target client 3 . Wherein, the initiating client 4 is used to update the data stored in the cloud storage server 1 . The initiating client 4 and the target client 3 may belong to the same user, or may belong to different users. The main application scenario where the initiating client 4 and the target client 3 belong to the same user is: the same user uses different devices (such as a mobile phone and a PC) to log in to the browser, and one of them (such as a PC) changes favorites, then it needs Sync that update to another device (phone) of the same user. An application scenario where the initiating client 4 and the target client 3 do not belong to the same user is, for example, information communication between different browser clients.

Of course, in the present invention, the cloud storage server itself can also initiate an update of the data content. In this case, the initiating browser client 4 in FIG. 1 may not exist. The scenario of this situation is, for example: the system pushes news messages or weather forecasts to all browser clients; or the system initiates an update instruction to all browser clients of a certain version.

Since the cloud storage server 1, the target client 3 and the initiating client 4 within the dotted line box in Figure 1 are existing in the existing browser system, adding a push server on this basis can effectively utilize the original system Architecture, reducing the cost of implementing the present invention.

In order to realize the connection of the cloud storage server 1, the push server 2 and the target client 3, as shown in Figure 2, the system for realizing data synchronization between the browser client and the cloud storage server can also include multiple socket servers (socketserver ),Distributor.

According to the present invention, in order to improve the data synchronization efficiency between the browser client and the cloud storage server, a socket server dedicated to providing socket services between the push server and the cloud storage server is proposed. The socket server is used to establish a socket connection with multiple browser clients, and when receiving condition information and command information, determine the target client from multiple browser clients according to the condition information, and send the command The information is sent to the target client.

The socket server is a virtual server, which can be implemented by configuring the existing server providing socket services, or can be realized by software or software modules with independent functions.

The distributor is configured to allocate a corresponding socket server and a connection identifier to the client after receiving the connection request, and store the user identification information and the connection identifier in the distribution information database. The detailed connection establishment process is shown in Figure 3, including:

Step S301, the browser client submits a connection request to the distributor. The connection request includes at least user identification information. For a logged-in user, the user identification information may include a user name; for a non-login user, the user identification Information may include a user's machine identification.

For a logged-in user, the user identification information may be a character string. Wherein, in addition to the username of the logged-in user, the character string also includes information such as login time and verification characters. The username is the user's unique identification number, which is a number used to represent a user. The verification character is generated according to the user name, and it can be determined whether the user identification information has been changed through the verification character.

For non-login users, the user identification information may include the machine identification of the non-login user, where the machine identification is a unique identification of the machine, which is generated by the client through the hash of the user's machine hardware and system configuration.

In addition, for subsequent target client screening, the connection request may also include user feature information, such as IP address information, browser version information, or user feature information such as user classification information. Wherein, user characteristic information such as browser version number, user classification information, or IP address information can be used for subsequent client screening.

Step S302, the distributor calculates a value based on the user identification information using a preset algorithm, and assigns a socket server to the browser client that submits the connection request according to the value; the value is globally unique, that is, the connection identifier; The distributor sends the connection information such as the IP address and port of the socket server and the connection identifier to the browser client that submitted the request;

In this step, a preset algorithm is used to calculate the above value based on the username of the logged-in user. For a non-login user, the above-mentioned value is directly calculated using the machine identifier of the non-login user, and the algorithm may be a cyclic redundancy check (CRC) 32 algorithm.

Step S303, the browser client establishes a connection with the corresponding socket server according to the received IP address and port number of the socket server, and the connection may be a Transmission Control Protocol (TCP, Transmission Control Protocol) connection. When the browser client establishes a connection with the socket server, the socket server obtains a resource identifier identifying the connection relationship between the socket server and the browser client. The browser client transmits the received connection identifier to the socket server using the established connection.

Step S304, after the socket server receives the connection identifier, it verifies the connection identifier to the distributor, if the verification is successful, it maintains the connection established with the browser client, and if the verification is unsuccessful, it disconnects connection already established.

Step S305, the distributor stores the user identification information (the user name of the login user or the machine identification of the non-login user), user characteristic information (if any) and the connection identifier in the distribution information database, and the socket server also The resulting resource identifier is stored in the distribution information database.

It should be noted that, in order to prevent allocation confusion caused by server-side changes, the browser client needs to re-execute steps S301-step S304 to connect after a period of time.

In addition, for each socket server, there is a corresponding separate data table in the distribution information database, so as to reduce the size of the data table and speed up the query speed of the socket server in the subsequent information push stage.

By increasing the distributor and socket server, and setting the distribution information database in the distributor, so that user identification information, connection identifier, resource identifier and user characteristic information can be stored in the distribution information database during the connection establishment phase, Thus, the push server can push the data content of the preset target client.

In the information push phase: the push server is used to send condition information and command information to the socket server; the socket server is used to forward the information pushed by the push server to the corresponding target client. The detailed information push process is described in detail in the following three types of scenarios.

(1) When the real-time synchronization is initiated by the initiating client, and the initiating client and the receiving client belong to the same user, the condition information includes user identification information. For example, as shown in Figure 4, the information push process includes:

Step S401, initiating the client to update the data stored in the cloud storage server;

In this step, the data stored on the cloud storage server side includes one of the following: favorites information, history information, browser configuration information, note information, login manager information, message reminder information, key information, and other possible information.

Step S402, the cloud storage server sends condition information and command information to the push server, the condition information includes user identification information, such as the user name of the logged-in user or the machine hardware identifier of the user who is not logged in, and the condition information also includes the identification of the initiator the resource identifier of the client's connection to its corresponding socket server;

Step S403, the push server uses the same algorithm as in the distributor to calculate a value based on the user identification information, so as to obtain the socket server assigned to the target client. This value is globally unique, that is, the connection identifier, and the condition Information and command information are sent to the socket server allocated for the target client;

Step S404, the socket server queries the distribution information database in the distributor according to the user identification information in the condition information, and determines the resource identifier corresponding to the target client, excluding those identifying the originating client and its corresponding socket server the resource identifier for the connection;

Step S405, the socket server sends the command information to the target client (one or more) in connection with the target client according to the resource identifier.

(2) When the real-time synchronization is initiated by the initiating client, and the initiating client and the receiving client belong to different login users, that is, the condition information includes user identification information, as shown in Figure 5, the information push process includes:

Step S501, the initiating client initiates updating the data stored in the cloud storage server;

In this step, the data stored on the cloud storage server side includes one of the following: favorites information, history information, browser configuration information, note information, login manager information, message reminder information, key information, news information and/or user Generated information and more.

Step S502, the cloud storage server sends condition information and command information to the push server, where the condition information may include user identification information, such as the user name of a logged-in user or the machine hardware identifier of a non-logged-in user;

Step S503, the push server uses the same algorithm as in the distributor to calculate a value based on the user identification information, so as to obtain the socket server allocated for the target client. This value is globally unique, that is, the connection identifier, and sets the condition Information and command information are sent to the socket server allocated for the target client;

Step S504, the socket server queries the distribution information database in the distributor according to the user identification information in the condition information, and determines the resource identifier of the target client;

Step S505, according to the resource identifier, the corresponding socket server sends the notification message to the target client (one or more) in connection with the client, so far, the information pushing process ends.

(3) When the real-time synchronization is actively initiated by the cloud storage server, and the condition information includes the characteristic screening information of the target client, but does not include the user identification information, wherein the characteristic screening information can also be empty,

In this case, during the connection establishment phase, the connection request submitted by the browser client to the distributor also includes feature screening information, which corresponds to the user feature information stored in the distribution information database as before.

As shown in Figure 6, the information push process includes:

Step S601, the cloud storage server sends condition information and command information to the push server, the condition information includes feature screening information of the target client (such as the version number of a certain browser), and the command information is, for example, an instruction to notify the user to upgrade;

Step S602, the push server pushes the condition information and command information to all socket servers;

Step S603, each socket server submits a query request to the distribution information database of the distributor respectively, and the query request includes characteristic screening information; the distribution information database queries the user characteristic information of each browser client in the distribution information database according to the characteristic screening condition, Determine the resource identifier of the target client satisfying the characteristic filter condition, and return the resource identifier to each socket server that initiates the query;

Step S604, each socket server sends command information to the corresponding client according to the received resource identifier, so far, the information pushing process ends.

Based on the system for realizing browser data synchronization shown in FIG. 1 and FIG. 2 , the present invention further provides a method for realizing browser data synchronization. As shown in Figure 7, the method for implementing browser data synchronization includes:

Step S710, the cloud storage server sends condition information and command information to the push server when there is data update;

Step S720, the push server determines the target client among multiple browser clients according to the condition information, and sends the command information to the target client;

In step S730, the target client implements data synchronization with the cloud storage server according to the command information.

Further, before step S710, a socket connection is established between the browser client and the socket server, and the establishment process of the connection is shown in FIG. 3 , which will not be repeated here.

Further, in step S710, in the step where the cloud storage server sends condition information and command information to the push server when there is data update, if the condition information includes the user name of the logged-in user of the target client or the machine identifier of the non-login user, the following are included: Two situations:

Situation 1: The originating client and the receiving client belong to the same user, and the user uses different devices (such as a mobile phone and a PC) to log in to the browser, and one of them (such as a PC) changes favorites, then the update needs to be synchronized to the same user's another device (mobile phone);

In this case, the initiating client first initiates modification of information about configurations, functions, or favorites or other information stored in the cloud storage server. Then the cloud storage server sends conditional information and command information to the push server, the command information includes content messages and notification messages, and the push server sends the command information to the target client through the socket server according to the condition information, wherein the target client side excludes the originating client. The information pushing process in this case is shown in FIG. 4 , which will not be repeated here.

Case 2: The initiating client and the receiving client do not belong to the same user, so that information exchange between different users through the client is realized.

Specifically, a user's client sends condition information and content messages to the cloud storage server, and the cloud storage server sends the condition information and related notification messages to the pusher, and the pusher sends the notification message to the destination according to the condition information. The client, and then the target client can access the cloud storage server to obtain content. The information pushing process in this case is shown in FIG. 5 , and will not be repeated here.

In addition, if the conditional information does not include the user identification information of the target client, but may include characteristic screening information, the following situations are also included:

Situation 3: The cloud storage server itself has data updates, and the browser client needs to synchronize data with the cloud storage server. The cloud storage server actively sends condition information and command information to the push server, for example:

1. The cloud storage server sends an update instruction to all browser clients of a certain version, so that all browser clients of this version can be upgraded to a new version, where the command information is a notification message for upgrading to a new version, and the condition is a certain The client version of the browser, that is, the feature filtering information is the version number of the browser client. Then, the push server sending the command information to the target client among the plurality of browser clients according to the condition information includes: the push server sends a notification message of upgrading to a new version to all browser clients of a certain version.

2. The cloud storage server pushes news messages to all browser clients, where the condition is all browser clients, that is, the feature screening information is empty, and the command information is content messages containing news messages; then the push server will send The sending of the command information to the target client among the plurality of browser clients includes: the push server sends the content message including the news message to all the browser clients. It should be understood that what is sent may also be a notification message.

3. The cloud storage server pushes the weather forecast to the browser clients in different regions, where the condition is the browser client in a certain region, that is, the feature screening information is the IP segment corresponding to the certain region, and the command information contains the weather forecast The push server sends the command information to the target client among the plurality of browser clients according to the condition information, including: the push server sends the content message containing the weather forecast to the browser client in a certain area. It should be understood that what is sent may also be a notification message.

The information pushing process in this case is shown in FIG. 6 , which will not be repeated here.

Based on the system for realizing browser data synchronization shown in FIG. 1 and FIG. 2 , the present invention further provides a browser client for realizing browser data synchronization. As shown in Figure 8, the browser client includes: a connection module, used to establish a connection relationship with the socket server through the distributor, and receive command information from the corresponding socket server; Information, execute its corresponding application operation. Wherein, the command information is a notification message or a content message.

As shown in Figure 8, the connection module further includes: a distributor connection submodule, which is used to submit a connection request to the distributor, the connection request at least includes user identification information, and receives the allocated socket returned by the distributor The connection information of the word server and the connection identifier; the socket connection submodule is used to establish a socket connection with the corresponding socket server according to the received connection information of the socket server and the connection identifier, and Receive command information from the corresponding socket server through the socket connection. Wherein, the user identification information is a user name of a login user or a machine hardware identification of a non-login user.

As shown in FIG. 8 , the browser client may further include: a cloud storage communication module, configured to communicate with the cloud storage server in response to an application operation of the application module.

As mentioned above, the socket server can play a key role in realizing the information push between the cloud storage server and the target client. FIG. 9 is a schematic structural diagram of a socket server according to an embodiment of the present invention. As shown in FIG. 9 , the socket server generally needs to include a connection module, which is used to establish socket connections with multiple browser clients, and perform information exchange with the browser clients that establish connections.

As mentioned above, the connection module is used to establish a socket connection with the browser client, specifically, when the browser client initiates a connection with the socket server, the connection module accepts the connection and obtains The resource identifier of the connection, the resource identifier is an identifier generated by the socket server system for identifying the connection between the browser client and the socket server.

In a specific implementation, the browser client submits a connection request to the distributor. The connection request includes at least user identification information. The distributor calculates a value based on the user identification information using a preset algorithm. The browser client of the connection request allocates a socket server, which is globally unique, that is, the connection identifier; the distributor then sends the connection information and connection identifier of the socket server to the browser client that submits the connection request , the browser client submitting the connection request establishes a connection with the connection module of the corresponding socket server according to the received connection information and connection identifier of the socket server.

As mentioned above, a distribution information database may be set in the browser data synchronization system. According to a specific implementation manner, when the system includes a distributor, the distribution information database may be set in the distributor. User identification information is stored in the distribution information database. During the above-mentioned process of establishing a socket connection, the browser client submitting the request can also transmit the connection to the corresponding socket server according to the received connection information of the socket server. identifier. At this time, the socket server may also include a verification module to verify the received connection identifier. When verifying, the verification module queries the connection identifier in the distribution information database to verify whether the connection identifier exists in the distribution information database, thereby verifying that the request performs a socket connection with the socket server Whether the browser client is legitimate.

When the verification module verifies that the connection identifier exists in the distribution information database, the socket server stores the resource identifier in the distribution information database. When the verification module verifies that the connection identifier does not exist in the distribution information database, the verification module instructs the connection module to disconnect the browser client.

As mentioned above, when the push server sends the condition information and command information to the socket server assigned to the target client, the socket server queries the distribution information database according to the condition information to determine the target client. When the condition information includes user identification information, the socket server performs a query according to the user identification information. When the resource identifier is stored in the distribution information database, the socket server searches the distribution information database for the resource identifier according to the condition information to determine the target client. At this time, the socket server also includes a query module, which completes the above query process. The socket server of the present invention adopts an asynchronous scheduling mode when sending command information to a target client. That is to say, after receiving the command information and determining the target client according to the condition information, the socket server sends the command information to the target client in an asynchronous manner. The so-called asynchronous mode means that when there are more than one target client, after the connection module sends a command message to one of the clients, it directly sends the command message to the next client without waiting for its receipt confirmation. This process is carried out continuously to achieve efficient sending, thereby shortening the execution time, improving system efficiency and reducing the time difference between messages received by different clients, and improving the real-time performance of the business.

The specific implementation of the socket service method applied to the socket server will be described in detail below with reference to FIG. 10 . According to the above description of the socket server, the socket service method applied to the socket server of the present invention includes at least step S1010: when the browser client initiates a connection with the socket server, the socket The socket server accepts the connection and obtains the connection's resource identifier.

According to a specific implementation manner of the present invention, after step S1010, the socket service method further includes step S1020: the socket server receives the connection identifier sent from the browser client via the connection, and queries the distributed information database to verify that the connection identifier exists in the distribution information database. After step S1020, preferably, the socket service method further includes step S1030: when the connection identifier exists in the distribution information database, the socket server stores the resource identifier into the distribution information database; When the connection identifier does not exist in the distribution information database, the socket server disconnects the connection.

According to another embodiment of the present invention, the socket service method further includes step S1040: when the push server sends the condition information and command information to the socket server assigned to the target client, the socket server according to The condition information queries the distribution information database to determine the target client.

Step S1040 is preferably: the socket server searches the distribution information database for the resource identifier according to the condition information to determine the target client.

According to another embodiment of the present invention, the socket service method further includes: when the socket server receives the command information and has determined the target client according to the condition information, and there are more than one target client, the socket server After sending a command message to one of the clients, the command message is directly sent to the next client without waiting for its receipt confirmation. It can be seen from the foregoing description that a socket server in the present invention may be connected to multiple browser clients at the same time, and the connection status between each browser client and the socket server may also be different. Moreover, target clients specified by different condition information may also be different. Therefore, in the socket service method of the present invention, for each different browser client, different steps may be executed in response to different condition information and command information from the push server.

When implementing the above-mentioned socket server with asynchronous scheduling mode and its socket service method, javascript language can be used to develop NodeJS socket server in Linux-CentOS environment, and the connection module of socket server adopts transmission control The protocol (TCP) connects with the browser client and sends command information. Compared with the websocket that usually uses the http protocol, the use of the Tcp protocol can reduce the resource consumption of the system and improve the business processing capability of the system.

In order to further save system resources, the command information pushed by the push server 2 to the browser client 3 is a notification message. In this case, the browser client is also used to establish a connection with the cloud storage server after receiving the notification message pushed by the push server, and download the updated data content from the cloud storage server. Synchronize local data content. By transmitting notification messages, the amount of transmitted data can be reduced, and the occupation of system resources can be reduced.

Of course, the command information pushed by the push server to the target client can also be a content message, that is, the content message contains updated data content. In this case, after the target client receives the content message pushed by the push server, The updated data content is extracted from the content message, and the local data content is synchronized according to the extracted data content. The content message can be directly pushed to the client by transmitting the content message, and the information transmission is fast and the steps are simple.

In order to support multiple languages and call texts conveniently, an HTTP interface is used between the push server and the cloud storage server, or other suitable interfaces, which are not limited in the present invention.

To sum up, the system for synchronizing browser data provided by the present invention, by setting up a separate push server, can timely send command information through The push server sends to the target client among the multiple browser clients, which solves the problem that the data of the browser client and the cloud storage server cannot be synchronized in real time simply and effectively, thus realizing the browser client and the cloud storage server in a simple and efficient manner. Data synchronization on the cloud storage server side. Therefore, on the basis of the original architecture, the browser client can efficiently, proactively, and resource-savingly synchronize information with the cloud storage server in real time. The system and method can also be implemented on the basis of the original system architecture, effectively utilize the original architecture, and realize cost effectiveness.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in related devices according to the embodiments of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

Claims (8)

1. realize the system that browser data is synchronous, this system comprises: cloud storage server end, distributor, push server and multiple browser client and socket server, wherein:

Described cloud storage server end is used for issuing conditional information and command information when there being Data Update to described push server;

Described push server is used in described multiple browser client, determining destination client according to this conditional information, and described command information is sent to the socket server be connected with described destination client; And

Described destination client is for realizing the data syn-chronization of itself and cloud storage server end according to described command information;

Described distributor, for after receiving the connection request of browser client, for it distributes corresponding socket server and connection identifier (CID; Described distributor also comprises: distribution information database, distributes relevant information for storing to socket server;

Described socket server is used for the command information from push server to send to corresponding destination client; Described socket server comprises link block, and this link block is used for setting up socket with described browser client and is connected; Wherein, described link block is also for connecting via described the connection identifier (CID receiving and send from described browser client; Described socket server also comprises authentication module, and described authentication module is used for: when receiving the connection identifier (CID sent from described browser client, and inquiry distribution information database is to verify whether this connection identifier (CID is present in this distribution information database.

2. the system as claimed in claim 1, wherein, when described browser client initiates the connection with described socket server, described link block accepts this connection, and obtains the resource identifier of this connection.

3. system as claimed in claim 2, wherein, described authentication module also for:

When described connection identifier (CID is present in this distribution information database, by described resource identifier stored in described distribution information database.

4. the system as claimed in claim 1, wherein, described authentication module also for:

When described connection identifier (CID is not present in this distribution information database, described link block is indicated to disconnect described connection.

5. the system as claimed in claim 1, wherein, described socket server also comprises an enquiry module, when conditional information and command information to be sent to the socket server distributed into destination client by described push server, described enquiry module according to described conditional information inquiry distribution information database to determine destination client.

6. system as claimed in claim 5, wherein, this link block determines destination client according to conditional information query resource identifier in distribution information database.

7. system as claimed in claim 2, wherein, have received command information when described socket server and determine destination client according to conditional information, and during more than one of destination client, described link block does not wait for that its confirmation of receipt just sends command messages directly to next client after sending command messages to one of them client.

8. system as claimed in claim 2, wherein, described link block adopts transmission control protocol and described browser client to carry out being connected the transmission with command information.