CN110493319B - Data synchronization method, system and device - Google Patents

Abstract

The embodiment of the invention provides a data synchronization method, a data synchronization system and a data synchronization device. The method comprises the following steps: receiving user information sent by a first server and a type identifier associated with the user information, and judging whether the type identifier is a registration type; the user information is information which is received by a first server and sent by a client corresponding to the first server, the user information sent by the client is user information which is acquired by the client and input by a user on the client, a target server is a server which is determined by the first server from at least one second server, and the type identifier is a type identifier which is generated by the first server and is associated with the user information; in case the type identification is a registration type, user information is stored. Therefore, the user can register at the client only once, the first server can synchronize the user information to the target server, and the user can log in the client corresponding to the target server without re-registering the user information at the client corresponding to the target server.

Description

Data synchronization method, system and device

technical field

The invention relates to the field of communication, in particular to a data synchronization method, system and device.

Background technique

Video networking is an important milestone in network development, a more advanced form of the Internet, and a real-time network that can realize the real-time transmission of high-definition video across the entire network that cannot be achieved by the Internet at present, and push many Internet applications to high-definition video, high-definition face-to-face.

In order to provide support and management for the Internet of Things business, many system clients have been developed based on the Internet of Things, such as the Internet of Things conference management system (conference management client), the Internet of Things monitoring and management system (scheduling client), multimedia Multiple system clients such as the body information release management system (management client).

However, at present, after a user successfully registers in a system, he can only use the user information in the system to log in to the system to perform services. If the user wants to use another system, he needs to register again in the other system. For example, after a user successfully registers on the management client, the user can only use the user information on the management client to log in to the management client, but cannot use the user information to log in to other clients such as scheduling client, management client, etc. . As a result, the user information of a user cannot be shared among multiple systems, and the user needs to register separately on each system.

SUMMARY OF THE INVENTION

In view of the above problems, the embodiments of the present invention are proposed in order to provide a data synchronization method, system and apparatus that overcome the above problems or at least partially solve the above problems.

In order to solve the above problem, an embodiment of the present invention discloses a data synchronization method, which is applied to a system including a client, a first server corresponding to the client, and at least one second server; including:

The client obtains user information input by the user on the client;

sending, by the client, the user information to the first server;

The first server receives the user information, generates a type identifier associated with the user information, and stores the user information and the type identifier;

The first server sends the user information and the type identifier to a target server in the at least one second server;

The target server receives the user information and the type identifier, and determines whether the type identifier is a registration type;

If the type is identified as a registered type, the target server stores the user information to keep synchronization with the user information stored in the first server.

The embodiment of the present invention also discloses a data synchronization method, which is executed on the target server and includes:

Receive the user information sent by the first server and the type identifier associated with the user information, and determine whether the type identifier is a registered type; wherein, the user information is received by the first server and is associated with the first server. Corresponding information sent by the client, the user information sent by the client is the user information obtained by the client and input by the user on the client, and the target server is the first server from at least one The server determined in the second server, the type identifier is the type identifier associated with the user information generated by the first server;

If the type is identified as a registered type, the user information is stored to keep synchronized with the user information stored in the first server.

The embodiment of the present invention also discloses a data synchronization method, which is executed on the first server and includes:

Receive the user information sent by the client, generate a type identifier associated with the user information, and store the user information and the type identifier, where the user information is obtained by the client User information entered on;

Send the user information and the type identification to a target server in at least one second server, so that the target server receives the user information and the type identification, and judges whether the type identification is a registered type; In the case that the type identifier is a registration type, the target server is made to store the user information to keep synchronization with the user information stored in the first server.

The embodiment of the present invention also discloses a data synchronization system, comprising:

a client, for obtaining user information that the user registers on the client;

The client is further configured to send the user information to the first server;

the first server, configured to receive the user information, generate a type identifier associated with the user information, and store the user information and the type identifier;

The first server is further configured to send the user information and the type identifier to a target server in the at least one second server;

The target server, for receiving the user information and the type identification, and judging whether the type identification is a registration type;

The target server is further configured to store the user information in the case that the type identification is a registered type, so as to keep synchronization with the user information stored in the first server.

The embodiment of the present invention also discloses a data synchronization device, which is set on the target server and includes:

The receiving module is configured to receive the user information sent by the first server and the type identifier associated with the user information, and determine whether the type identifier is a registered type; wherein, the user information is received by the first server. Information sent by the client corresponding to the first server, the user information sent by the client is the user information obtained by the client and input by the user on the client, and the target server is the first A server determined by a server from at least one second server, and the type identifier is a type identifier associated with the user information generated by the first server;

A storage module, configured to store the user information if the target server does not store a first target identifier that matches the identifier in the user information, to keep the user information stored in the first server Synchronize.

An embodiment of the present invention further discloses a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the data synchronization method described above is implemented.

An embodiment of the present invention further discloses a data synchronization device, comprising a processor, a memory, and a computer program stored on the memory and running on the processor, and the computer program is implemented when executed by the processor The data synchronization method described above.

The embodiments of the present invention include the following advantages:

In the implementation of the present invention, the user information sent by the first server and the type identifier associated with the user information are received, and whether the type identifier is a registered type is determined; the user information is received by the first server and sent by the client corresponding to the first server. , the user information sent by the client is the user information obtained by the client and input by the user on the client, the target server is the server determined by the first server from at least one second server, and the type identifier is the user information generated by the first server and the user information. The associated type identifier; if the type identifier is a registered type, user information is stored. Therefore, the user only needs to register on the client once, the first server can synchronize the user information to the target server, and the user can log in to the client corresponding to the target server without re-registering the user information on the client corresponding to the target server.

The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

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 embodiments. The drawings are for the purpose of illustrating preferred embodiments only and are not to be considered limiting of the invention. Also, the same components are denoted by the same reference numerals throughout the drawings. In the attached image:

Fig. 1 is the networking schematic diagram of a kind of video network of the present invention;

2 is a schematic diagram of the hardware structure of a node server of the present invention;

3 is a schematic diagram of a hardware structure of an access switch of the present invention;

4 is a schematic diagram of the hardware structure of an Ethernet protocol conversion gateway of the present invention;

5 is an architectural diagram of a data synchronization system provided by an embodiment of the present invention;

6 is a flowchart of steps of a data synchronization method provided by an embodiment of the present invention;

FIG. 7 is a signaling flowchart of a data synchronization method provided by an embodiment of the present invention;

8 is a schematic structural diagram of a data synchronization system according to an embodiment of the present invention;

9 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of another data synchronization apparatus provided by an embodiment of the present invention.

Detailed ways

In order to make the above objects, features and advantages of the present invention more clearly understood, the present invention will be described in further detail below with reference to the accompanying drawings and specific embodiments.

It should be understood that the specific embodiments described herein are only used to explain the present invention, only a part of the embodiments of the present invention, but not all of the embodiments, and are not used to limit the present invention.

Video networking is an important milestone in network development. It is a real-time network that can realize real-time transmission of high-definition video, and push many Internet applications to high-definition video, high-definition face-to-face.

Video networking adopts real-time high-definition video switching technology, which can provide required services on a network platform, such as high-definition video conferencing, video surveillance, intelligent monitoring and analysis, emergency command, digital broadcast TV, delayed TV, online teaching, live broadcast , VOD on demand, TV mail, personal recording (PVR), intranet (self-organized) channels, intelligent video broadcast control, information release and other dozens of video, voice, picture, text, communication, data and other services are all integrated into one The system platform can realize high-definition video playback through TV or computer.

In order to make those skilled in the art better understand the embodiments of the present invention, video networking is introduced as follows:

Some of the technologies used in the Internet of Things are as follows:

Network Technology

The network technology innovation of the video network improves the traditional Ethernet (Ethernet) to face the potentially huge video traffic on the network. Different from pure network packet switching (Packet Switching) or network circuit switching (Circuit Switching), the Internet of View technology adopts Packet Switching to meet the requirements of Streaming. The Internet of Things technology has the flexibility, simplicity and low price of packet switching, and at the same time has the quality and security assurance of circuit switching, and realizes the entire network of switched virtual circuits and seamless connection of data formats.

Switching Technology

The Internet of Things adopts the asynchronous and packet switching advantages of Ethernet, and eliminates the defects of Ethernet under the premise of full compatibility. User data does not need any format conversion in the whole network. Video networking is a more advanced form of Ethernet. It is a real-time switching platform that can realize the real-time transmission of large-scale high-definition video across the entire network that cannot be achieved by the Internet, and push many network video applications to high-definition and unified.

Server Technology

The server technology on the video networking and unified video platform is different from the server in the traditional sense. Its streaming media transmission is based on connection-oriented, and its data processing capability has nothing to do with traffic and communication time. A single network layer can contain information. command and data transmission. For voice and video services, the complexity of video networking and unified video platform streaming media processing is much simpler than data processing, and the efficiency is greatly improved by more than 100 times compared to traditional servers.

Storage Technology

The ultra-high-speed storage technology of the unified video platform adopts the most advanced real-time operating system in order to adapt to the media content of large capacity and large flow, and maps the program information in the server instruction to the specific hard disk space, and the media content no longer passes through the server. It is directly delivered to the user terminal in an instant, and the general waiting time of the user is less than 0.2 seconds. The optimized sector distribution greatly reduces the mechanical movement of the hard disk head seeking, and the resource consumption only accounts for 20% of the same level of IP Internet, but it generates 3 times more concurrent traffic than traditional hard disk arrays, and the overall efficiency is increased by more than 10 times.

Network Security Technology

The structural design of the Internet of Things completely eliminates the network security problems that plague the Internet through separate licensing for each service and complete isolation of equipment and user data. Generally, anti-virus programs and firewalls are not required, and hackers and viruses are prevented from attacking. , to provide users with a structured worry-free safety network.

Service Innovation Technology

The unified video platform integrates services and transmission. Whether it is a single user, a private network user, or the aggregate of a network, it is just an automatic connection. User terminals, set-top boxes or PCs are directly connected to the unified video platform to obtain a variety of multimedia video services in various forms. The unified video platform adopts the "recipe-style" table matching mode to replace the traditional complex application programming. It can realize complex applications with very little code, and realize "unlimited" new business innovation.

The networking of the Internet of Things is as follows:

The Internet of Things is a centralized control network structure. The network can be a tree network, a star network, a ring network, etc., but on this basis, a centralized control node is required in the network to control the entire network.

As shown in Figure 1, the Internet of Things is divided into two parts: the access network and the metropolitan area network.

The equipment in the access network part can be mainly divided into three categories: node server, access switch, and terminal (including various set-top boxes, coding boards, memory, etc.). The node server is connected to the access switch, and the access switch can be connected to multiple terminals and can be connected to Ethernet.

The node server is a node in the access network that functions as a centralized control, and can control access switches and terminals. The node server can be directly connected to the access switch, or it can be directly connected to the terminal.

Similarly, the equipment in the metropolitan area network can also be divided into three categories: metropolitan area server, node switch, and node server. The metropolitan area server is connected with the node switch, and the node switch can be connected with multiple node servers.

The node server is the node server of the access network part, that is, the node server belongs to both the access network part and the metropolitan area network part.

The metropolitan area server is a node with centralized control function in the metropolitan area network, which can control the node switch and the node server. The metropolitan area server can be directly connected to the node switch or directly connected to the node server.

It can be seen that the entire VisionLink network is a network structure controlled by layers and centralized, and the network controlled by the node server and the metro server can be tree, star, ring and other structures.

Figuratively, the access network part can form a unified video platform (the part in the dashed circle), and multiple unified video platforms can form a video network; each unified video platform can be interconnected through the metro and wide-area video networks.

Classification of Internet-connected devices

1.1 The devices in the video networking according to the embodiment of the present invention can be mainly divided into three categories: servers, switches (including Ethernet gateways), and terminals (including various set-top boxes, coding boards, memories, etc.). As a whole, the Internet of Views can be divided into a metropolitan area network (or a national network, a global network, etc.) and an access network.

1.2 The equipment in the access network part can be mainly divided into three categories: node server, access switch (including Ethernet gateway), terminal (including various set-top boxes, coding boards, memory, etc.).

The specific hardware structure of each access network device is as follows:

Node server:

As shown in FIG. 2 , it mainly includes a network interface module 201, a switching engine module 202, a CPU module 203, and a disk array module 204;

Among them, the incoming packets from the network interface module 201, the CPU module 203, and the disk array module 204 all enter the switching engine module 202; the switching engine module 202 performs an operation of looking up the address table 205 for the incoming packets, thereby obtaining the packet guidance information; and according to The steering information of the packet stores the packet into the queue of the corresponding packet buffer 206; if the queue of the packet buffer 206 is close to full, it is discarded; the switching engine module 202 polls all the packet buffer queues, and forwards if the following conditions are met: 1) The port sending buffer is not full; 2) The queue packet counter is greater than zero. The disk array module 204 mainly realizes the control of the hard disk, including the initialization, reading and writing of the hard disk, etc.; (including the downlink protocol packet address table, the uplink protocol packet address table, and the data packet address table) configuration, and the configuration of the disk array module 204.

Access switch:

As shown in FIG. 3 , it mainly includes a network interface module (downlink network interface module 301, uplink network interface module 302), a switching engine module 303 and a CPU module 304;

Wherein, the incoming packet (uplink data) from the downlink network interface module 301 enters the packet detection module 305; the packet detection module 305 detects whether the destination address (DA), source address (SA), data packet type and packet length of the packet meet the requirements, if If it matches, the corresponding stream identifier (stream-id) is allocated and entered into the switching engine module 303, otherwise it is discarded; the incoming packet (downlink data) from the upstream network interface module 302 enters the switching engine module 303; the incoming data packet from the CPU module 204 Enter the switching engine module 303; the switching engine module 303 performs the operation of looking up the address table 306 for the incoming packet, thereby obtaining the orientation information of the packet; if the packet entering the switching engine module 303 is from the downlink network interface to the uplink network interface, then combine The stream identifier (stream-id) stores the packet into the queue of the corresponding packet buffer 307; if the queue of the packet buffer 307 is close to full, it is discarded; if the packet entering the switching engine module 303 is not the downstream network interface, it is upstream If the data packet goes to the network interface, the data packet is stored in the queue of the corresponding packet buffer 307 according to the direction information of the packet; if the queue of the packet buffer 307 is nearly full, it is discarded.

The switching engine module 303 polls all packet buffer queues, and in this embodiment of the present invention, there are two situations:

If the queue is from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) The port sending buffer is not full; 2) The queue packet counter is greater than zero; 3) The token generated by the rate control module is obtained ;

If the queue is not from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) the sending buffer of the port is not full; 2) the packet counter of the queue is greater than zero.

The rate control module 308 is configured by the CPU module 304, and generates tokens for the packet buffer queues going from all the downlink network interfaces to the uplink network interfaces within a programmable interval, so as to control the rate of uplink forwarding.

The CPU module 304 is mainly responsible for the protocol processing with the node server, the configuration of the address table 306 , and the configuration of the rate control module 308 .

Ethernet protocol conversion gateway :

As shown in Figure 4, it mainly includes a network interface module (downlink network interface module 401, uplink network interface module 402), switching engine module 403, CPU module 404, packet detection module 405, rate control module 408, address table 406, packet The buffer 407 and the MAC adding module 409 and the MAC deleting module 410.

Among them, the data packets coming from the downlink network interface module 401 enter the packet detection module 405; the packet detection module 405 detects the Ethernet MAC DA, Ethernet MAC SA, Ethernet length or frame type, video network destination address DA, video network Whether the source address SA, network data packet type and packet length meet the requirements, if so, assign the corresponding stream identifier (stream-id); then, the MAC deletion module 410 subtracts the MAC DA, MAC SA, length or frame type (2byte), and enter the corresponding receive buffer, otherwise discard;

The downlink network interface module 401 detects the transmission buffer of the port, and if there is a packet, learns the Ethernet MAC DA of the corresponding terminal according to the network destination address DA of the packet, and adds the Ethernet MAC DA of the terminal, the MACSA of the Ethernet protocol conversion gateway, Ethernet length or frame type, and send.

The functions of other modules in the Ethernet protocol conversion gateway are similar to that of the access switch.

terminal:

Mainly includes network interface module, service processing module and CPU module; for example, set-top box mainly includes network interface module, video and audio codec engine module, CPU module; encoding board mainly includes network interface module, video and audio encoding engine module, CPU module; memory It mainly includes network interface module, CPU module and disk array module.

1.3 The equipment in the metropolitan area network can be mainly divided into two categories: node server, node switch, and metropolitan area server. Among them, the node switch mainly includes a network interface module, a switching engine module and a CPU module; the metropolitan area server mainly includes a network interface module, a switching engine module and a CPU module.

2. Definition of Internet Data Packets

2.1 Definition of Access Network Data Packets

The data packet of the access network mainly includes the following parts: destination address (DA), source address (SA), reserved bytes, payload (PDU), and CRC.

As shown in the table below, the data packets of the access network mainly include the following parts:

DA SA Reserved Payload CRC

in:

The destination address (DA) consists of 8 bytes (byte), the first byte indicates the type of the data packet (such as various protocol packets, multicast data packets, unicast data packets, etc.), there are up to 256 possibilities, The second to sixth bytes are the metropolitan area network address, and the seventh and eighth bytes are the access network address;

The source address (SA) is also composed of 8 bytes (byte), and the definition is the same as the destination address (DA);

Reserved bytes consist of 2 bytes;

The payload part has different lengths according to different types of datagrams. If it is a variety of protocol packets, it is 64 bytes. If it is a single multicast data packet, it is 32+1024=1056 bytes. Of course, it is not limited to Above 2 kinds;

The CRC consists of 4 bytes, and its calculation method follows the standard Ethernet CRC algorithm.

2.2 MAN Data Packet Definition

The topology of the metropolitan area network is a graph. There may be two or even more than two connections between two devices, that is, there may be more than two connections between node switches and node servers, between node switches and node switches, and between node switches and node servers. kind of connection. However, the metropolitan area network address of the metropolitan area network equipment is unique. In order to accurately describe the connection relationship between the metropolitan area network equipment, a parameter: label is introduced in the embodiment of the present invention to uniquely describe a metropolitan area network equipment.

The definition of labels in this specification is similar to the definition of MPLS (Multi-Protocol Label Switch, Multi-Protocol Label Switch) labels. Assuming that there are two connections between device A and device B, the data packets from device A to device B have 2 labels, packets from device B to device A also have 2 labels. Labels are divided into incoming labels and outgoing labels. Assuming that the label (incoming label) of the data packet entering device A is 0x0000, the label (outgoing label) of the data packet when it leaves device A may become 0x0001. The network access process of the metropolitan area network is a network access process under centralized control, which means that the address allocation and label allocation of the metropolitan area network are dominated by the metropolitan area server, and the node switches and node servers are all passively executed. Different from MPLS label assignment, MPLS label assignment is the result of mutual negotiation between switches and servers.

As shown in the table below, the data packets of the metropolitan area network mainly include the following parts:

DA SA Reserved Label Payload CRC

Namely destination address (DA), source address (SA), reserved bytes (Reserved), label, payload (PDU), CRC. Among them, the format of the label can refer to the following definition: the label is 32 bits, of which the upper 16 bits are reserved, and only the lower 16 bits are used, and its position is between the reserved bytes of the data packet and the payload.

This embodiment provides a data synchronization method, which is applied to a system including a client, a first server corresponding to the client, and at least one second server. The first server may be any one of video network servers, such as a streaming media server, a management server, an operation and maintenance server, and a scheduling server. In this embodiment, two second servers are used as an example for introduction, and the two second servers are any two different Internet of View servers other than the first server in the above-mentioned Internet of View servers. Referring to FIG. 5, FIG. 5 is an architecture diagram of a data synchronization system provided by an embodiment of the present invention. For example, the client is a streaming media client 501, the first server is a streaming media server 502, and a second server is a management server. 503. Another second server is a scheduling server 504. Based on the architecture diagram of the data synchronization system shown in FIG. 5 , this embodiment provides a data synchronization method, which includes:

The client obtains the user information registered by the user on the client; the client sends the user information to the first server; the first server receives the user information and stores the user information; the first server sends the user information to the target server in the at least one second server user information; the target server receives the user information, generates a type identifier associated with the user information, and stores the user information and type identifier; the first server sends the user information and type identifier to the target server in at least one second server; the target server receives the user information information and type identifier, and determine whether the type identifier is a registered type; if the type identifier is a registered type, the target server stores the user information to keep synchronization with the user information stored in the first server.

When the user enters user information through the client for registration, if the client is a streaming media client, the user can open the registration interface provided by the streaming media client, and enter the user information on the registration interface to register. After the user enters the user information, click the register button, the streaming media client can obtain the user information input by the user, and send the user information to the first server (if the client is a streaming media client, the first server is a streaming media server. ; if the client is a managed client, the first server is a managed server).

After the first server receives the user information, if the user clicks the registration button, the first server can determine that the type identifier of the received user information is the registration type, so that the generated type identifier associated with the user information is the registration type. Afterwards, the first server stores the user information and the type identifier, and sends the user information and the type identifier to the target server in the at least one second server. It should be noted that, for example, the first server may first send the user information and the type identifier to a second server, and then send the user information and the type identifier to the other server after the sending; Send user information and type identification. If it is sent to one second server first, the target server is one of the two second servers; if the user information is sent to two second servers at the same time, the target server is the two second servers.

After receiving the user information and the type identifier, the target server can judge whether the user information is a registered type according to the type identifier, and in the case that the user information is a registered type, the user information can be directly stored to keep the user information stored in the first server. Synchronize. Therefore, after the user only needs to register at one client, the first server corresponding to the client can synchronize the user information input by the user to other servers (for example, if the target server is a meeting server) The management server and the scheduling server can synchronize the user information registered by the user in the streaming media client to the management server and the scheduling server).

It should be noted that, in the case where the type identifier is not a registered type, it is determined whether the target server stores a first target identifier that matches the identifier in the registration information; the target server stores a first target identifier that matches the identifier in the registration information. In the case of the target identifier, the user information is used to update the target user information associated with the first target identifier to keep synchronization with the user information stored in the first server. In the case where the type identifier is not a registered type (for example, the type identifier is an update type, that is, the user information needs to be updated), the target server needs to determine whether the first target identifier that matches the identifier in the user information is stored locally. When the first target identifier matching the identifier in the registration information is stored, the target server uses the user information to update the target user information associated with the first target identifier to keep synchronization with the user information stored in the first server. Therefore, if the user has registered user information on the client, if the user modifies the user information registered by the user on the client, the first server can also synchronize the modified user information to the target server.

It is understandable that if the user clicks the register button on the management client corresponding to the management server to register user information, the management server (in this case, the management server is the first server) can obtain the information from the management client. User information and synchronize the user information to the streaming media server and the scheduling server (if the streaming media server and the scheduling server are the target servers); if the user clicks the register button on the scheduling client corresponding to the scheduling server to register the user information, the scheduling server (The scheduling server is the first server) can obtain user information from the scheduling client and synchronize the user information to the streaming media server and the managed server (if the streaming media server and the managed server are target servers).

The following example describes the process of the first server synchronizing the user information modified by the user to the target server. For example, the user can log in to the client and click the Modify button to modify the previously registered user information. After the user clicks the Modify button, an interface will pop up for the user to input new user information. The identifier of the new user information needs to be the same as the previously registered user information. The identifier of the user information is used to uniquely identify a piece of user information, and other user information can be modified, such as modifying the user's address, age and other information. After inputting new user information, the user clicks the update button, the client can obtain the new user information, generate a type identifier associated with the new user information, and associate the new user information with the new user information The type identifier is sent to the first server. In this case, the generated type identifier is the update type. That is, when the first server receives the type identifier sent by the client as an update type, the first server determines whether the first server stores an identifier matching the identifier of the new user information, and if there is an identifier that matches the identifier of the new user information If the identifier matches the identifier, the previously stored user information is updated with the new user information, and the new user information and the type identifier associated with the new user information are sent to the target server. The type identifier received by the target server is an update type. Likewise, the target server determines whether the target server stores a first target identifier that matches the identifier of the new user information, and if the first target identifier that matches the identifier of the new user information is stored ID, the previously stored user information associated with the first target ID is updated with the new user information.

In order to introduce the embodiment of the present invention in detail, the following description is made with reference to FIG. 6 . Referring to FIG. 6, FIG. 6 is a flowchart of steps of a data synchronization method provided by an embodiment of the present invention. The data synchronization method provided by this embodiment is executed on a target server, and the method includes the following steps:

Step 601: Receive user information and a type identifier associated with the user information sent by the first server, and determine whether the type identifier is a registered type.

The user information is the information received by the first server and sent by the client corresponding to the first server, the user information sent by the client is the user information obtained by the client and input by the user on the client, and the target server is the first server from For at least one server determined in the second server, the type identifier is the type identifier associated with the user information generated by the first server.

The type ID can be a registration type or an update type. For example, when a user newly registers user information, the generated type identifier is the registration type. When the user updates the user information that the user once registered, the generated type is identified as the update type.

Step 602: In the case that the type identifier is a registered type, store the user information to keep synchronization with the user information stored in the first server.

In the data synchronization method provided in this embodiment, after receiving the user information and the type identifier, the target server can determine whether the user information is of the registered type according to the type identifier, and in the case that the user information is of the registered type, the user information can be stored directly to Keeping synchronization with the user information stored in the first server. Therefore, after the user only needs to register at one client, the first server corresponding to the client can synchronize the user information input by the user to other servers (for example, if the target server is a meeting server) The management server and the scheduling server can synchronize the user information registered by the user in the streaming media client to the management server and the scheduling server).

Referring to FIG. 7, FIG. 7 is a signaling flowchart of a data synchronization method provided by an embodiment of the present invention, and the method includes the following steps:

Step 701: The client obtains user information input by the user on the client.

Step 702: The client sends user information to the first server.

Step 703: The first server receives the user information, generates a type identifier associated with the user information, and stores the user information and the type identifier.

Step 704: The first server sends the user information and the type identifier to the target server in the at least one second server.

Step 705: The target server receives the user information and the type identifier, and determines whether the type identifier is a registered type.

Step 706: In the case that the type identifier is a registered type, the target server stores the user information to keep synchronization with the user information stored in the first server.

It should be noted that, in the case where the type identifier is not a registered type, it is determined whether the target server stores a first target identifier that matches the identifier in the registration information; the target server stores a first target identifier that matches the identifier in the registration information. In the case of the target identifier, the user information is used to update the target user information associated with the first target identifier to keep synchronization with the user information stored in the first server. For the specific process, reference may be made to the embodiment shown in FIG. 5 , which is not described in detail here to avoid repetition.

Step 707: The target server generates a status code of the user information, stores the status code, and sends the status code to the first server, where the status code is used to indicate the synchronization state of the user information.

Correspondingly, the first server may receive the status code sent by the target server, and store the status code. After the first server saves the state code, the client obtains the state code from the first server, and can display the synchronization state of the user information according to the state code.

If the synchronization state of the user information indicated by the status code is a synchronization failure state, step 708 may be executed. It should be noted that, taking the client as the streaming media client as an example, the operation and maintenance staff can log in to the streaming media client, enter the user management interface, and select the user information to be synchronized. The operation and maintenance staff can select one or more pieces of user information. After selecting, they can click the sync button (by clicking the sync button to send synchronization data signaling to the target server) to synchronize the selected one or more pieces of user information to the target server. The first server can also synchronize according to a preset time, for example, the preset time is 3:00 am every day, and the first server can automatically send synchronization data signaling to the target server at the preset time, that is, the first server can automatically send synchronization data signaling to the target server according to each The status code of the user information, filter out the user information that has not been synchronized to the target server or the user information that failed to be synchronized before, and perform the synchronization operation at the preset time.

Step 708: The first server sends synchronization data signaling to the target server, where the synchronization data signaling includes user information.

It should be noted that the synchronization data signaling may include one piece of user information or multiple pieces of user information. In this embodiment, a piece of user information included in the synchronization data signaling is taken as an example. For example, in step 706, if the target server fails to store the user information successfully, the synchronization state of the user information indicated by the status code of the user information is a synchronization failure state. In this step, the first server may send the synchronization data signaling including the piece of user information to the target server to perform the synchronization operation again.

Step 709: In response to the synchronization data signaling, the target server matches the first identifier of each first user information in the user information list stored in the target server with the identifier in the user information to obtain the target user information list, the target user information. The information list includes a first target identification obtained from the user information list that is different from the identification of the user information;

Step 710: The target server sends the target user information list to the first server.

For step 709 and step 710. For example, the identification of user information is the user name, which is uniquely identified by the user name. The identifier of the user information received by the target server is zhangsan, and the user names in the user information list include three user names: lisi123, zhaoping, and wanggang445. Since zhangsan is different from any of the three user names, the target user information list includes The three usernames, each of which is the first target ID. The target server will send the target user information list including the three user names to the first server.

It should be noted that, if an identifier matching the identifier in the user information is stored in the target server, the target server sends the first target identifier different from the identifier in the user information to the first server. For example, the user names in the user information list include three user names: zhangsan, zhaoping, and wanggang445, then the first target identifier stored in the target server is zhangsan, and the target server only needs to list the target user information including the two user names of zhaoping and wanggang445. Sent to the first server, that is, the two user names of zhaoping and wanggang445 are different from the user name of zhangsan, and the target user information list includes two first target identifiers of zhaoping and wanggang445.

Step 711: The first server receives the target user information list sent by the target server, and matches the second identifier in the second user information stored in the first server with each first target identifier, so as to obtain the information from each first target identifier. A second target identification different from the second identification is obtained.

Taking the second identifiers in the second user information stored in the first server including zhangsan and zhaowu145, and the target user information list including two first target identifiers of zhaoping and wanggang445 as examples, each first target identifier is different from the second identifier. , therefore, the second target identifications obtained from each first target identification that are different from the second identifications include zhaoping and wanggang445.

Step 712: The first server synchronizes the first user information associated with the second target identifier to the first server.

With reference to the example introduced in step 711, the first server synchronizes zhaoping and wanggang445 to the first server. If the first server successfully synchronizes zhaoping and wanggang445, in step 713, the status code of the first user information associated with zhaoping may be sent to the target server, and the status code of the first user information associated with wanggang445 may be sent to the target. server.

Step 713: The first server sends the status code of the first user information associated with the second target identifier to the target server.

Step 714: The target server receives the status code of the first user information associated with the second target identification sent by the first server, and updates the status code associated with the second target identification according to the status code of the first user information associated with the second target identification. The synchronization status of the first user information.

The data synchronization method provided by this embodiment can synchronize the registration information input by a user on a client to other servers that are communicatively connected to the server through the server corresponding to the client, so that the user only needs to register on one client You can use the user information registered on the client to log in to the corresponding clients of other servers, so users do not need to register separately on each system. And, in the case where the target server fails to synchronize the user information sent by the first server, the first server can send the synchronization data signaling containing the user information to the target server, so that the target server can not only store the user information again, It is synchronized with the user information in the first server, and the first identifier in the target server can be matched with the identifier in the user information to obtain the target user information list, and send the target information list to the first server. The first server matches the second identification stored in the first server with each first target identification in the target information list to obtain a second target identification different from the second identification from each first target identification, the first The server synchronizes the first user information associated with the second target identifier to the first server. Thus, the data in the first server and the target server are kept synchronized. That is, the user information stored in the first server is the same as the user information stored in the target server.

8 is a schematic structural diagram of a data synchronization system according to an embodiment of the present invention, where the data synchronization system includes:

The client 801 is used to obtain the user information registered by the user on the client; the client 801 is also used to send the user information to the first server; the first server 802 is used to receive the user information, and generate a type identifier associated with the user information, And store user information and type identification; The first server 802 is also used to send user information and type identification to the target server in at least one second server; The target server 803 is used to receive user information and type identification, and judge whether the type identification is The registration type; the target server is further configured to store the user information in the case that the type identification is the registration type, so as to keep synchronization with the user information stored in the first server.

The data synchronization system provided in this embodiment can realize that the user only needs to input user information on one client to register, that is, the user information can be synchronized from the first server to the target server, without the need for the user to register again on the client corresponding to the target server, That is, you can use the user information to log in to the client corresponding to the target server.

FIG. 9 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present invention. The data synchronization apparatus is usually implemented in hardware and/or software. The data synchronization apparatus 900 includes the following modules: a receiving module 901 and a storage module 902 .

The receiving module 901 is used to receive the user information sent by the first server and the type identifier associated with the user information, and determine whether the type identifier is a registered type; wherein, the user information is received by the first server and sent by the client corresponding to the first server The user information sent by the client is the user information obtained by the client and input by the user on the client, the target server is the server determined by the first server from at least one second server, and the type identifier is the same as that generated by the first server. The type identifier associated with the user information; the storage module 902 is configured to store the user information if the target server does not store the first target identifier matching the identifier in the user information, so as to maintain synchronization with the user information stored in the first server.

This embodiment provides a data synchronization device, which can synchronize the user information registered by the first server to the target server, so that the user only needs to input user information on one client for registration, that is, the user information can be synchronized from the first server to the target server. , the user can use the user information to log in to the client terminal corresponding to the target server without re-registering at the client terminal corresponding to the target server.

Optionally, it can also include:

a judging module for judging whether the target server stores a first target identifier that matches the identifier in the registration information when the type identifier is not a registered type;

The updating module is used to update the target user information associated with the first target identifier by using user information to match the user information stored in the first server when the target server stores a first target identifier that matches the identifier in the registration information. Information stays in sync.

Optionally, it can also include:

The sending module is used to generate the status code of the user information and store the status code, and send the status code to the first server, the status code is used to indicate the synchronization state of the user information, so that the first server receives the status code sent by the target server, and sends the status code to the first server. Save the status code.

Optionally, it can also include:

The receiving module 901 is further configured to receive the synchronization data signaling sent by the first server when the synchronization state of the user information indicated by the status code is a synchronization failure state, and the synchronization data signaling includes user information; in response to the synchronization data signaling, The first identification of each first user information in the user information list stored in the target server is matched with the identification of the user information to obtain a target user information list, and the target user information list includes the user information obtained from the user information list. The identifiers of the first target identifiers are different;

The sending module is further configured to send the target user information list to the first server.

FIG. 10 is a schematic structural diagram of another data synchronization apparatus provided by an embodiment of the present invention. The data synchronization apparatus is usually implemented in hardware and/or software. The data synchronization apparatus 1000 includes the following modules: a receiving module 1001 and a sending module 1002 .

The receiving module 1001 is used to receive the user information sent by the client, generate a type identifier associated with the user information, and store the user information and the type identifier, wherein the user information is the user information obtained by the client and input by the user on the client;

The sending module 1002 is used to send user information and type identification to the target server in at least one second server, so that the target server receives user information and type identification, and judges whether the type identification is a registration type; in the case that the type identification is a registration type In the next step, the target server is made to store the user information to keep synchronization with the user information stored in the first server.

Optionally, the receiving module 1001 is further configured to receive the status code of the user information sent by the target server, and save the status code, where the status code is used to represent the synchronization state of the user information;

The sending module 1002 is further configured to send synchronization data signaling to the target server when the synchronization state of the user information indicated by the status code is a synchronization failure state, where the synchronization data signaling includes user information.

Optionally, the receiving module 1001 is further configured to receive the user information list sent by the target server, and match the second identifier in the second user information stored in the first server with each first identifier, so as to obtain information from each first identifier. Obtaining a second target identification different from the second identification in the identification; wherein, the user information list includes the respective first identifications of at least one first user information; Synchronizing the first user information associated with the second target identification to the first server;

The sending module 1002 is further configured to send the status code of the first user information associated with the second target identification to the target server, so that the target server receives the status code of the first user information associated with the second target identification, and according to the status code of the first user information associated with the second target identification The status code of the first user information associated with the target identifier updates the synchronization state of the first user information associated with the second target identifier.

In addition, an embodiment of the present invention also provides a data synchronization device, the data synchronization device includes a processor, a memory, and a computer program stored in the memory and running on the processor, the computer program being executed by the processor to implement the above implementation Each process of the data synchronization method embodiment of the example, and can achieve the same technical effect, in order to avoid repetition, it is not repeated here.

Embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, each process of the above-mentioned data synchronization method embodiment can be achieved, and can achieve the same The technical effect, in order to avoid repetition, will not be repeated here. The computer-readable storage medium may be a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, or an optical disk.

For the product embodiments, since the technical solutions of the above-mentioned device embodiments are applied, the description is relatively simple, and reference may be made to the partial descriptions of the device embodiments for related points.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments may be referred to each other.

It should be understood by those skilled in the art that the embodiments of the embodiments of the present invention may be provided as a method, an apparatus, or a computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media having computer-usable program code embodied therein, including but not limited to disk storage, CD-ROM, optical storage, and the like.

Embodiments of the present invention are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present invention. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal equipment to produce a machine that causes the instructions to be executed by the processor of the computer or other programmable data processing terminal equipment Means are created for implementing the functions specified in the flow or flows of the flowcharts and/or the blocks or blocks of the block diagrams.

These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing terminal equipment to operate in a particular manner, such that the instructions stored in the computer readable memory result in an article of manufacture comprising instruction means, the The instruction means implement the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing terminal equipment, so that a series of operational steps are performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby executing on the computer or other programmable terminal equipment The instructions executed on the above provide steps for implementing the functions specified in the flowchart or blocks and/or the block or blocks of the block diagrams.

Although preferred embodiments of the embodiments of the present invention have been described, additional changes and modifications to these embodiments may be made by those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications that fall within the scope of the embodiments of the present invention.

Finally, it should also be noted that in this document, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply these entities or that there is any such actual relationship or sequence between operations. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or terminal device comprising a list of elements includes not only those elements, but also a non-exclusive list of elements. other elements, or also include elements inherent to such a process, method, article or terminal equipment. Without further limitation, an element defined by the phrase "comprises a..." does not preclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

A data synchronization method and a data synchronization device provided by the present invention have been introduced in detail above. The principles and implementations of the present invention are described with specific examples in this paper. The descriptions of the above embodiments are only used to help Understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and application scope. In conclusion, the contents of this description should not be understood to limit the present invention.

Claims (9)

1. A data synchronization method is characterized by being applied to a system comprising a client, a first server corresponding to the client and at least one second server; the method comprises the following steps:

the client acquires user information input by a user on the client;

the client sends the user information to the first server;

the first server receives the user information, generates a type identifier associated with the user information, and stores the user information and the type identifier;

the first server sends the user information and the type identification to a target server in the at least one second server;

the target server receives the user information and the type identification and judges whether the type identification is a registration type;

in the case that the type identifier is a registration type, the target server stores the user information so as to keep synchronization with the user information stored in the first server;

under the condition that the type identification is not a registration type, the target server judges whether a first target identification matched with the identification in the user information is stored or not;

and under the condition that the target server stores a first target identifier matched with the identifier in the user information, updating the target user information associated with the first target identifier by adopting the user information so as to keep synchronization with the user information stored in the first server.

2. A data synchronization method, implemented in a target server, includes:

receiving user information sent by a first server and a type identifier associated with the user information, and judging whether the type identifier is a registration type; the user information is information which is received by the first server and sent by a client corresponding to the first server, the user information sent by the client is user information which is acquired by the client and input by a user on the client, the target server is a server which is determined by the first server from at least one second server, and the type identifier is a type identifier which is generated by the first server and is associated with the user information;

in the case that the type identifier is a registration type, storing the user information to keep synchronization with the user information stored in the first server;

under the condition that the type identification is not a registration type, judging whether a first target identification matched with the identification in the user information is stored in the target server or not;

and under the condition that the target server stores a first target identifier matched with the identifier in the user information, updating the target user information associated with the first target identifier by adopting the user information so as to keep synchronization with the user information stored in the first server.

3. The method of claim 2, further comprising, after said storing said user information:

and the target server generates a state code of the user information, stores the state code and sends the state code to the first server, wherein the state code is used for representing the synchronous state of the user information, so that the first server receives the state code sent by the target server and stores the state code.

4. The method of claim 3, further comprising, after said sending the status code to the first server:

receiving a synchronous data signaling sent by the first server under the condition that the synchronous state of the user information represented by the state code is a synchronous failure state, wherein the synchronous data signaling comprises the user information;

in response to the synchronous data signaling, matching a first identifier of each first user information in a user information list stored in the target server with an identifier of the user information to obtain a target user information list, wherein the target user information list comprises a first target identifier which is obtained from the user information list and is different from the identifier of the user information;

and sending the target user information list to the first server.

5. A data synchronization method, performed on a first server, comprising:

receiving user information sent by a client, generating a type identifier associated with the user information, and storing the user information and the type identifier, wherein the user information is user information which is acquired by the client and input by a user on the client;

sending the user information and the type identifier to a target server in at least one second server, so that the target server receives the user information and the type identifier and judges whether the type identifier is a registration type; in the case that the type identifier is a registration type, causing the target server to store the user information so as to keep synchronization with the user information stored in the first server; under the condition that the type identification is not the registration type, the target server judges whether a first target identification matched with the identification in the user information is stored or not; and under the condition that the target server stores a first target identifier matched with the identifier in the user information, enabling the target server to adopt the user information and update the target user information associated with the first target identifier so as to keep synchronization with the user information stored in the first server.

6. The method of claim 5, further comprising, after said sending the user information to a target server of the at least one second server:

receiving a state code of the user information sent by the target server, and storing the state code, wherein the state code is used for representing the synchronous state of the user information;

and sending a synchronous data signaling to the target server under the condition that the synchronous state of the user information represented by the state code is a synchronous failure state, wherein the synchronous data signaling comprises the user information.

7. The method of claim 6, further comprising, after said sending synchronization data signaling to said target server:

receiving a user information list sent by the target server, and matching a second identifier in second user information stored in the first server with each first identifier to obtain a second target identifier different from the second identifier from each first identifier; the user information list comprises respective first identifications of at least one first user information;

synchronizing the first user information associated with the second target identification to the first server;

and sending the status code of the first user information associated with the second target identifier to the target server so that the target server receives the status code of the first user information associated with the second target identifier, and updating the synchronization state of the first user information associated with the second target identifier according to the status code of the first user information associated with the second target identifier.

8. A data synchronization system, comprising:

the client is used for acquiring user information registered by a user on the client;

the client is further used for sending the user information to the first server;

the first server is used for receiving the user information, generating a type identifier associated with the user information, and storing the user information and the type identifier;

the first server is further used for sending the user information and the type identifier to a target server in at least one second server;

the target server is used for receiving the user information and the type identifier and judging whether the type identifier is a registration type;

the target server is further used for storing the user information to keep synchronization with the user information stored in the first server under the condition that the type identifier is a registration type;

the target server is further used for judging whether the target server stores a first target identifier matched with the identifier in the user information or not under the condition that the type identifier is not a registration type;

the target server is further configured to, in a case that the target server stores a first target identifier matching an identifier in the user information, update, with the user information, target user information associated with the first target identifier to keep synchronization with the user information stored in the first server.

9. A data synchronization device, provided in a target server, includes:

the receiving module is used for receiving user information sent by a first server and a type identifier associated with the user information and judging whether the type identifier is a registration type; the user information is information which is received by the first server and sent by a client corresponding to the first server, the user information sent by the client is user information which is acquired by the client and input by a user on the client, the target server is a server determined by the first server from at least one second server, and the type identifier is a type identifier which is generated by the first server and is associated with the user information;

the storage module is used for storing the user information to keep synchronization with the user information stored in the first server if the target server does not store a first target identifier matched with the identifier in the user information;

the judging module is used for judging whether the target server stores a first target identifier matched with the identifier in the user information or not under the condition that the type identifier is not a registration type;

and the updating module is used for updating the target user information associated with the first target identifier by adopting the user information under the condition that the target server stores the first target identifier matched with the identifier in the user information so as to keep synchronization with the user information stored in the first server.

Images