CN113872994A

CN113872994A - Organization architecture synchronization method, device, computer equipment and storage medium

Info

Publication number: CN113872994A
Application number: CN202010613255.0A
Authority: CN
Inventors: 陈嘉鹏; 梁百怡
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-06-30
Filing date: 2020-06-30
Publication date: 2021-12-31

Abstract

The application relates to a method and a device for synchronizing a tissue architecture, a computer device and a storage medium. The method comprises the following steps: and sending a query request to the server, wherein the query request carries the local organization structure state identification. And receiving the organization architecture change information returned by the server, wherein the organization architecture change information is acquired by the server according to the matching of the local organization architecture state identifier and the server side organization architecture state identifier. And sending a node change information synchronization request to the server according to the state information of the organization architecture change node and the operation type of the organization architecture change node in the organization architecture change information. And acquiring the changed node information sent by the server according to the changed node information synchronization request. And updating the local organization structure corresponding to the local organization structure state identification according to the change node information and replacing the local organization structure state identification with the server organization structure state identification. The method can save synchronization time and bandwidth.

Description

Organization architecture synchronization method, device, computer equipment and storage medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for synchronizing an architecture, a computer device, and a storage medium.

Background

With the development of instant messaging technology, more and more enterprises begin to use instant messaging applications to communicate. At present, a user usually downloads complete enterprise organization architecture data from a server after logging in an instant messaging application client, and the instant messaging application can be normally used after the downloading is finished. However, because the amount of the current complete organization structure data is very large, a lot of time and server bandwidth are needed to synchronize the organization structure data, so that the instant messaging application cannot be normally used.

Disclosure of Invention

In view of the foregoing, there is a need to provide an organization architecture synchronization method, apparatus, computer device and storage medium capable of saving synchronization organization architecture time and server bandwidth.

A method of tissue architecture synchronization, the method comprising:

sending a query request to a server, wherein the query request carries a local organization structure state identifier;

receiving organization architecture change information returned by the server, wherein the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier, and the organization architecture change information is acquired by the server according to the matching of the local organization architecture state identifier and the service end organization architecture state identifier;

sending a node change information synchronization request to a server according to the state information of the organization structure change node and the operation type of the organization structure change node;

acquiring change node information sent by a server according to the change node information synchronization request;

and updating the local organization structure corresponding to the local organization structure state identification according to the change node information and replacing the local organization structure state identification with the server organization structure state identification.

A method of tissue architecture synchronization, the method comprising:

receiving an inquiry request sent by a terminal, wherein the inquiry request carries a local organization structure state identifier;

acquiring a server side organization structure state identifier, matching the server side organization structure state identifier with a local organization structure state identifier, and acquiring organization structure change information when a matching result meets preset matching; the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier;

when the state information of the organization architecture change node meets the preset increment synchronization condition, sending the organization architecture change information to a terminal;

a receiving terminal acquires corresponding change node information according to the state information of the organization structure change node and the operation type of the organization structure change node;

the node information change is transmitted to the terminal.

In one embodiment, after receiving an inquiry request sent by a terminal, where the inquiry request carries a local organization structure status identifier, the method further includes:

detecting whether a preset pressure bottleneck value is reached, and generating inquiry request refusing information and first delay request time when the preset pressure bottleneck value is reached;

returning the inquiry request rejection information and the first delay request time to the terminal;

and receiving the inquiry request sent by the terminal after the first delay request time.

In one embodiment, after receiving a change node information synchronization request sent by a terminal according to the state information of the organization architecture change node and the operation type of the organization architecture change node, the method further includes:

detecting whether a preset pressure bottleneck value is reached, and generating change node information synchronization request refusing information and second delay request time when the preset pressure bottleneck value is reached;

returning the information of the change node information synchronization request refusing information and the second delay request time to the terminal;

and receiving a change node information synchronization request sent by the terminal after the second delay request time.

In one embodiment, the node information change sending terminal includes:

detecting the current network state, stopping sending the change node information to the terminal when the current network state meets the preset network interruption condition, and storing the synchronous progress of the change node information;

and when the current network state meets the preset network recovery condition, sending unsynchronized changed node information to the terminal according to the changed node information synchronization progress.

A tissue architecture synchronization device, the device comprising:

the query request sending module is used for sending a query request to the server, wherein the query request carries a local organization structure state identifier;

the information receiving module is used for receiving organization architecture change information returned by the server, the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier, and the organization architecture change information is obtained by the server according to the matching of the local organization architecture state identifier and the service end organization architecture state identifier;

the synchronous request sending module is used for sending a node change information synchronous request to the server according to the state information of the organization structure change node and the operation type of the organization structure change node;

the node information acquisition module is used for acquiring the change node information sent by the server according to the change node information synchronous request;

an updating module for updating the local organization structure corresponding to the local organization structure state identifier according to the change node information and replacing the local organization structure state identifier with the server organization structure state identifier

An tissue architecture device, the device comprising:

the request receiving module is used for receiving a query request sent by a terminal, wherein the query request carries a local organization structure state identifier;

the information acquisition module is used for acquiring the organization structure state identification of the server, matching the organization structure state identification of the server with the state identification of the local organization structure, and acquiring organization structure change information when the matching result meets the preset matching property; the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier;

the information sending module is used for sending the organization architecture change information to the terminal when the state information of the organization architecture change node meets the preset increment synchronization condition;

the synchronous request receiving module is used for receiving a change node information synchronous request sent by the terminal according to the state information of the organization structure change node and the operation type of the organization structure change node and acquiring corresponding change node information according to the state information of the organization structure change node and the operation type of the organization structure change node;

and the node information sending module is used for sending the changed node information to the terminal.

A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:

the node information change is transmitted to the terminal.

A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:

the node information change is transmitted to the terminal.

The organization structure synchronization method, the device, the computer equipment and the storage medium send a query request to a server through a terminal, the server acquires a server organization structure state identifier when receiving the query request, matches the server organization structure state identifier with a local organization structure state identifier, acquires organization structure change information when a matching result accords with preset matching, then returns the organization structure change information to the terminal, when the terminal receives the organization structure change information, sends a change node information synchronization request to the server according to the organization structure change node state information and the operation type of the organization structure change node, the server receives the change node information synchronization request, acquires corresponding change node information, sends the change node information to the terminal, and the terminal receives the change node information to update the local organization structure and replace the organization structure state identifier, therefore, the terminal can be synchronized to the changed node information, the synchronization of the full amount of node information is avoided, the efficiency of synchronous organization architecture is improved, and the time of synchronous organization architecture is saved. Meanwhile, the terminal acquires the information of the changed nodes from the server, and does not need to acquire the information of the whole nodes, so that the bandwidth of the server is saved.

Drawings

FIG. 1 is a diagram of an application environment for the organizational structure synchronization method, according to one embodiment;

FIG. 2 is a flow diagram illustrating a method for organizational structure synchronization, according to one embodiment;

FIG. 3 is a flow diagram illustrating the receipt of status information in one embodiment;

FIG. 4 is a flow diagram illustrating a parallel request in one embodiment;

FIG. 5 is a timing diagram of concurrent synchronization of change node information in one embodiment;

FIG. 6 is a flow diagram illustrating the delayed transmission of a query request in one embodiment;

FIG. 7 is a timing diagram illustrating delayed transmission of a query request in one embodiment;

FIG. 8 is a flow diagram illustrating delayed transmission of a synchronization request in one embodiment;

FIG. 9 is a timing diagram illustrating delayed transmission of synchronization requests in one embodiment;

FIG. 10 is a flowchart illustrating display of a conversation page in one embodiment;

FIG. 11 is a flowchart illustrating a method for organizational structure synchronization according to another embodiment;

FIG. 12 is a flow diagram illustrating a process for sending information to a destination change node in an embodiment;

FIG. 13 is a flowchart illustrating query request transmission in one embodiment;

FIG. 14 is a flow diagram illustrating the sending of a synchronization request in one embodiment;

FIG. 15 is a flowchart illustrating a method for organizational structure synchronization in accordance with an embodiment;

FIG. 16 is a timing diagram of the organizational structure synchronization method in one embodiment;

FIG. 17 is a block diagram of an organization architecture synchronization apparatus in one embodiment;

FIG. 18 is a block diagram showing the structure of an organization structure synchronization apparatus according to another embodiment;

FIG. 19 is a diagram showing an internal structure of a computer device in one embodiment;

fig. 20 is an internal structural view of a computer device in another embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The organizational structure synchronization method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The terminal 102 sends a query request to the server 104, wherein the query request carries a local organization structure state identifier; the terminal 102 receives organization structure change information returned by the server 104, wherein the organization structure change information comprises organization structure change node state information, an organization structure change node operation type and a service end organization structure state identifier, and the organization structure change information is acquired by the server 104 according to the matching of the local organization structure state identifier and the service end organization structure state identifier; the terminal 102 sends a node change information synchronization request to the server 104 according to the state information of the organization structure change node and the operation type of the organization structure change node; the terminal 102 acquires the change node information sent by the server 104 according to the change node information synchronization request; the terminal 102 updates the local organization structure corresponding to the local organization structure state identifier according to the change node information and replaces the local organization structure state identifier with the server organization structure state identifier. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.

In one embodiment, as shown in fig. 2, a method for synchronizing a tissue architecture is provided, which is exemplified by applying the method to the terminal in fig. 1, and it is understood that the method can also be applied to a system comprising a server and a server, and is implemented by the interaction between the server and the server. In this embodiment, the method includes the following steps:

step 202, sending a query request to a server, where the query request carries a local organization structure status identifier.

The query request is used for querying whether the local organization structure state identification is matched with the server side organization structure state identification stored by the server. The organization architecture is the most basic structural basis for enterprise flow operation, department setting, functional planning and the like, and common organization architecture forms include central right collection system, partial right system, linear type, matrix type and the like. The organization architecture state identifier is used for uniquely identifying the state of the organization architecture, and the changed organization architecture state identifier is generated after the organization architecture is changed every time. The local organization structure state identifier refers to an organization structure state identifier stored in a terminal memory, and is used for identifying an organization structure state already stored in a terminal, and may be a version number, a name, a character string, and the like.

Specifically, the terminal sends a query request to the server, where the query request carries a terminal local, and when a user logs in the enterprise instant messaging application through the terminal, the terminal obtains a local organization structure state identifier from a local memory, and then sends the query request to the server. In one embodiment, the terminal may send the query request to the server at a fixed time, and the time interval of the fixed time may be customized, for example, the query request is sent to the server at every interval. In one embodiment, the organizational structure may also be that of a government agency, a social organization, or the like.

And 204, receiving organization structure change information returned by the server, wherein the organization structure change information comprises organization structure change node state information, an organization structure change node operation type and a service end organization structure state identifier, and the organization structure change information is acquired by the server according to the matching of the local organization structure state identifier and the service end organization structure state identifier.

The node refers to a node in an organization structure, for example, a node in an enterprise organization structure may be a user or a department. The organizational structure change node is a node in the organizational structure where data change occurs, where the data change includes, but is not limited to, updating node data, deleting node data, and adding node data, and the updating node data is to update old data of an original node to new data, for example, update a node name to a new name. Deleting node data refers to deleting data of an original node or directly deleting a node, for example, deleting a user mailbox of a user node or directly deleting the user node. The new node data is to add a new node to the data of the original node, for example, the user node does not store a user mailbox, and the user mailbox of the user node can be added newly. Or the user node does not exist in the organization structure, the user node is added. The state information of the organizational structure change node refers to the state information corresponding to the node with the data change, and includes but is not limited to the state identifier of the organizational structure change node. Each node with data change has corresponding state information. When the state information of the plurality of organization structure change nodes includes the state information of the plurality of organization structure change nodes, it is described that the data of the plurality of organization structure nodes is changed. The organizational structure change node state identifier is used for uniquely identifying a node state corresponding to the organizational structure change node, and may be a version number, a name, a number, a character string, and the like. For example, the status identifier corresponding to the change department may be a version number different from a version number corresponding to the department before the change, and the status identifier corresponding to the change user may be a status number, which is compared with the status number of the user before the change. In an embodiment, when node data changes, a corresponding node state identifier is generated, all changed node state identifiers and unchanged node state identifiers are obtained, an organization structure state identifier is generated according to the changed node state identifiers and the unchanged node state identifiers, the changed node state identifiers and the unchanged node state identifiers can be spliced to obtain an organization structure state identifier, and the changed node state identifiers and the unchanged node state identifiers can also be combined to obtain the organization structure state identifier.

In one embodiment, the organizational structure state information includes an organizational structure change node type and an organizational structure change node state identification. The organization architecture change node type refers to a category corresponding to a change node in an organization architecture, and comprises a user node type and a department node type.

The operation type of the organizational structure change node refers to a specific type for operating the change node, and includes, but is not limited to, a delete node operation, an update node operation, an add node operation, and the like. The node deleting operation refers to deleting the changed nodes, that is, deleting the node data corresponding to the changed nodes in the organization structure. The update node operation refers to updating node data of a change node. The operation of adding nodes refers to adding corresponding changed nodes in the organization structure. The matching is used for indicating whether the local organization structure state identification is consistent with the server organization structure state identification, when the local organization structure state identification is consistent with the server organization structure state identification, the matching is 1, and when the local organization structure state identification is inconsistent with the server organization structure state identification, the matching is 0.

Specifically, when receiving the query request, the server matches the local organization architecture state identifier with the server organization architecture state identifier, and when the local organization architecture state identifier matches the server organization architecture state identifier, the server directly returns the reminding information that the organization architecture is the latest to the terminal, and when receiving the reminding information that the returned organization architecture is the latest, the terminal does not process the reminding information. And when the matching is not consistent, the server acquires the stored organization structure updating record data, acquires the organization structure change information from the organization structure updating record number, and issues the organization structure change information to the terminal. And the terminal receives the organization structure change information sent by the server and stores the organization structure change information.

And step 206, sending a node change information synchronization request to the server according to the state information of the organization structure change node and the operation type of the organization structure change node.

The change node information synchronization request is used for synchronizing the change node information of the change node in the server. The change node information is information specific to the change node.

In one embodiment, the change node information includes an organization structure change node type and node data corresponding to the organization structure change node, for example, when the change node type is a user, the node data includes, but is not limited to, a user name, a user position, a user contact method, a user belonging department, user remark information, and the like. For example, when the node type is changed to be a department, the node data includes, but is not limited to, a name of the department, the number of users in the department, an arrangement order of users in the department, a bulletin of the department, a file of the department, and the like.

Specifically, the terminal may send a new node information synchronization request to the server according to the new node operation in the organizational structure change node operation type and the state information of the corresponding new node, where the new node information synchronization request only carries the new node operation and the state information of the corresponding new node. The terminal can also send an update node information synchronization request to the server according to the update node operation in the organization architecture change node operation type and the state information of the corresponding update node, wherein the update node information synchronization request only carries the update node operation and the state information of the corresponding update node. The terminal may also send a change node information synchronization request to the server according to the new node operation and the update node operation in the organization structure change node operation type and the corresponding organization structure change node state information, where the change node information synchronization request may carry the new node operation and the update node operation and the corresponding new node state information and update node state information.

And step 208, acquiring the changed node information sent by the server according to the changed node information synchronization request.

Specifically, when the server receives a change node information synchronization request, the server searches for corresponding change node information according to the organization structure change node state information and the organization structure change node operation type carried in the change node information synchronization request, and issues the change node information to the terminal, and the terminal obtains the change node information sent by the server according to the change node information synchronization request.

And step 210, updating the local organization structure corresponding to the local organization structure state identification according to the change node information and replacing the local organization structure state identification with the server organization structure state identification.

Specifically, the terminal searches for corresponding local node information from the local organization structure according to the change node information, replaces the local node information with the change node information, and completes the replacement of all the change node information, namely, completes the component structure synchronously. And when the component architecture is synchronously completed, replacing the local organization architecture state identification stored in the terminal with the server organization architecture state identification.

In one embodiment, the terminal stores the changed node information in the memory, deletes the node information corresponding to the local organization structure, and replaces the local organization structure state identifier with the server organization structure state identifier. When the terminal needs to use the changed node information, the changed node information is directly obtained from the memory for use.

In one embodiment, the terminal stores the change node information in the form of a relationship pair, including the relationship between the user node and the relationship between the department node and the user node. For example, if the user a belongs to the department C, the user a and the department C are stored in the form of (department C, relationship a). As another example, user A and user B are affiliated with department C. User a and user B are stored in the form of (user a, user B). And when the terminal needs to display the organization structure, directly searching the stored change node information relation pair, and displaying the organization structure according to the change node information relation pair.

In the organization structure synchronization method, a query request is sent to a server through a terminal, the server acquires a server organization structure state identifier when receiving the query request, matches the server organization structure state identifier with a local organization structure state identifier, acquires organization structure change information when a matching result meets preset matching, then returns the organization structure change information to the terminal, when the terminal receives the organization structure change information, sends a change node information synchronization request to the server according to the organization structure change node state information and the operation type of the organization structure change node, the server receives the change node information synchronization request, acquires corresponding change node information, sends the change node information to the terminal, and the terminal receives the change node information to update the local organization structure and replace the organization structure state identifier, thereby enabling the terminal to be synchronized to the change node information, the synchronization of the full node information is avoided, the efficiency of the synchronous organization framework is improved, and the time of the synchronous organization framework is saved. Meanwhile, the terminal acquires the information of the changed nodes from the server, and does not need to acquire the information of the whole nodes, so that the bandwidth of the server is saved.

In one embodiment, after step 204, after receiving the organization architecture change information returned by the server, where the organization architecture change information includes the organization architecture change node state information, the operation type of the organization architecture change node, and the service-side organization architecture state identifier, and the organization architecture change information is obtained by the server according to the matching between the local organization architecture state identifier and the service-side organization architecture state identifier, the method further includes:

and acquiring the state information of the local organization architecture node, and detecting the state information of the organization architecture change node and the operation type of the organization architecture change node according to the state information of the local organization architecture node.

The local organization structure node state information refers to state information corresponding to each node in an organization structure stored in a terminal memory.

Specifically, the terminal acquires the state information of the local organization structure node from the memory, and then the operation type of the organization structure change node is matched with the state information of the organization structure change node by using the state information of the local organization structure node. When the operation type of the organizational structure change node is the deletion node operation and the consistent organizational structure change node state information is matched in the local organizational structure node state information, the deletion node operation and the corresponding organizational structure change node state information are detected. For example, the same organization structure change node state number is matched in the local organization structure node state numbers, and when the same organization structure change node state number is matched, the node operation and the corresponding organization structure change node state information are detected through deletion.

When the operation type of the organization architecture change node is the operation of the new node and the consistent state information of the organization architecture change node is not matched in the state information of the local organization architecture node, the operation of the new node and the state information of the corresponding organization architecture change node are detected. When the operation type of the organization architecture change node is the update node operation and the consistent organization architecture change node state information is matched in the local organization architecture node state information, the state information of the organization architecture change node is detected through the update node operation and the corresponding organization architecture change node state information.

Step 206, sending a node change information synchronization request to a server according to the state information of the organization structure change node and the operation type of the organization structure change node, including:

and when the state information of the organization architecture change node and the operation type of the organization architecture change node pass the detection, sending a change node information synchronization request to the server according to the state information of the organization architecture change node and the operation type of the organization architecture change node.

Specifically, when all the state information of the organization structure change node and the operation type of the organization structure change node are detected to pass, it is indicated that the obtained state information of the organization structure change node and the operation type of the organization structure change node are correct. And sending a node change information synchronization request to the server according to the state information of the organization architecture change node and the operation type of the organization architecture change node. When detecting that the state information of the organizational structure change node and the operation type of the organizational structure change node fail, indicating that the acquired state information of the organizational structure change node and the operation type of the organizational structure change node have errors, and acquiring the state information of the organizational structure change node and the operation type of the organizational structure change node again from the server.

In the embodiment, the obtained state information of the organization structure change node and the operation type of the organization structure change node are detected by using the state information of the local organization structure node, and when the detection is passed, a synchronization request is sent to the server, so that wrong node data is prevented from being synchronized, and the accuracy of data synchronization is ensured.

In one embodiment, as shown in fig. 3, step 206, sending a change node information synchronization request to a server according to the state information of the organization architecture change node and the operation type of the organization architecture change node, includes:

step 302, when the state information of the organization structure change node is detected and the operation type of the organization structure change node fails, the state information of the detection fail node is obtained, and a re-obtaining request of the state information of the fail node is sent to a server according to the state information of the detection fail node.

And step 304, receiving the target node state information corresponding to the failed node state information returned by the server.

The detecting of the failed node state information refers to detecting the organization structure change node state information and the organization structure change node state information of which the corresponding operation type of the organization structure change node fails in the organization structure change node state information. The target node state information refers to node state information corresponding to the newly acquired failed node state information.

Specifically, when detecting that the state information of the organization structure change node and the operation type of the organization structure change node fail, it indicates that the state information of the organization structure change node and the corresponding operation type of the organization structure change node have errors, and at this time, it is necessary to obtain correct state information of the organization structure change node and the corresponding operation type of the organization structure change node from the server. And then, sending a failed node state information reacquiring request to a server, searching a corresponding node in an organization structure node of a server according to the failed node state information when the server receives the failed node state information reacquiring request, acquiring target node state information of the node and a corresponding target node operation type, returning the target node state information and the corresponding target node operation type to the terminal, acquiring the target node state information corresponding to the failed node state information and the corresponding target node operation type returned by the server by the terminal, and then detecting the target node state information and the corresponding target node operation type again. And performing subsequent processing until the detected target node state information and the corresponding target node operation type pass, so as to ensure the accuracy of data synchronization. For example, when the new node operation and the corresponding node state information are detected, the same node state information is matched in the local organization structure node state information, which indicates that the terminal has the new node, and indicates that the new node operation and the corresponding node state information have an error, at this time, a reacquisition request is sent to the server according to the new node operation and the corresponding node state information, then a target node operation corresponding to the node having the error and the corresponding target node state information are obtained, and the target node operation and the corresponding target node state information are re-detected. For another example, when the node deleting operation and the corresponding node state information are detected, the same node state information is not matched in the local organization structure node state information, which indicates that the corresponding node has been deleted in the terminal. And when the error occurs in the deleted node operation and the corresponding node state information, sending the target node operation and the corresponding target node state information to the server according to the deleted node operation and the corresponding node state information, then acquiring the target node operation corresponding to the node with the error and the corresponding target node state information, and re-detecting the target node operation and the corresponding target node state information. For example, when the update node operation and the corresponding node state information are detected, the same node state information is matched in the local organization structure node state information, and at this time, the node in the terminal is updated and does not need to be updated, which indicates that an error occurs in the update node operation and the corresponding node state information. At this time, the terminal sends a reacquisition request to the server according to the updated node operation and the corresponding node state information, then acquires the target node operation corresponding to the node with the error and the corresponding target node state information, and re-detects the target node operation and the corresponding target node state information.

In the above embodiment, when it is detected that the state information of the organization structure change node and the operation type of the organization structure change node fail, the state information of the target node corresponding to the state information of the failed node is obtained from the server again, and then subsequent data synchronization is performed, so that the accuracy of data synchronization can be ensured.

In one embodiment, the type of the operation of the fabric change node includes at least one of a delete node operation, an add node operation, and an update node operation, as shown in fig. 4, and step 206, sending a synchronization request of the change node information to the server according to the state information of the fabric change node and the type of the operation of the fabric change node includes:

step 402, when the operation type of the organizational structure change node includes a new node operation and/or an update node operation, obtaining the state information of the organizational structure change node corresponding to the new node operation and/or the update node operation.

The new node adding operation refers to adding a new node in the organization structure, for example, adding a new department node or a new user node to the enterprise organization structure. The update node operation is to update a node in an organization architecture, for example, update department node information including, but not limited to, update department user number, update department name, update department location, and the like, and update user node information including, but not limited to, update user name, update user location, update user contact method, update user position, update user affiliated department, and the like.

Specifically, when the operation type of the organizational structure change node includes a new node operation and an update node operation, the terminal acquires state information of the organizational structure change node corresponding to the new node operation and the update node operation. In one embodiment, when the operation type of the organizational structure change node includes a new node operation, the terminal acquires the state information of the organizational structure change node corresponding to the new node operation. In one embodiment, when the operation type of the organizational structure change node includes an update node operation, the terminal obtains the state information of the organizational structure change node corresponding to the update node operation.

In one embodiment, when the operation type of the organization structure change node includes a delete node operation, the terminal obtains the state information of the organization structure change node corresponding to the delete node operation, searches the state information of the node corresponding to the state information of the organization structure change node in the state information of the local organization structure node, and performs delete processing.

And step 404, generating each parallel change node information synchronization request according to the state information of the organization structure change node corresponding to the newly added node operation and/or the updated node operation.

The parallel change node information synchronization request is used for requesting to change node information, and the parallel change node information refers to change node information which is obtained in parallel according to organization structure change node state information corresponding to newly added node operation and/or updated node operation.

Specifically, the terminal determines the number or size of the changed node information to be synchronized according to the new node operation and the state information of the organization structure changed node corresponding to the updated node operation. And dividing according to the number or the size of the change node information needing to be synchronized to obtain the number or the size of the change node information needing to be synchronized in each request. For example, the total number of the change node information to be synchronized is 5 ten thousand, at this time, 5 ten thousand pieces of the change node information are divided into 10 pieces, and the number of the change node information to be synchronized per request is 1 ten thousand, that is, the terminal generates 10 parallel change node information synchronization requests, and the number of the change node information of the request corresponding to each parallel change node information synchronization request is 1 ten thousand. The division may be performed according to the size of the change node information, for example, if the size of the change node information which needs to be synchronized in total is 1GB (Gigabyte, a decimal information measure unit), and the size of the change node information which needs to be synchronized is 128MB (MByte, a storage unit in a computer) when the 1GB change node information is divided into 8 parts. That is, the terminal generates 8 parallel change node information synchronization requests, and the change node information size of the request corresponding to each parallel change node information synchronization request is 128 MB.

In one embodiment, the terminal generates each parallel change node information synchronization request according to the state information of the organization structure change node corresponding to the operation of the newly added node. The method comprises the steps of determining the size or the quantity of parallel change node information needing to be synchronized according to state information of organization structure change nodes corresponding to newly added node operation, dividing according to the size or data, determining the quantity or the quantity of the change node information needing to be synchronized for each request, and then generating corresponding synchronization requests of each parallel change node information.

In one embodiment, the terminal generates each parallel change node information synchronization request according to the state information of the organization architecture change node corresponding to the update node operation. The method comprises the steps of determining the size or the quantity of parallel change node information needing to be synchronized according to state information of organization structure change nodes corresponding to update node operation, dividing according to the size or data, determining the quantity or the size of the change node information needing to be synchronized for each request, and then generating each corresponding parallel change node information synchronization request.

Step 406, sending each parallel change node information synchronization request to the server in parallel.

Specifically, the terminal sends each parallel change node information synchronization request to the server in parallel, the server receives each parallel change node information synchronization request in parallel and returns each parallel change node information in parallel, and the terminal receives and stores each parallel change node information returned by the server. In a specific embodiment, as shown in fig. 5, a timing chart of parallel synchronization of the parallel change node information is shown, in which the user terminal sends a parallel synchronization request of the parallel change node information to the server, the server returns the parallel change node information to the user terminal in parallel according to the parallel synchronization request of the parallel change node information, and the user terminal receives and stores the parallel change node information.

In the embodiment, the parallel acquisition of the change node information is enabled by sending each parallel change node information synchronization request to the server in parallel, so that the efficiency of data synchronization is improved.

In an embodiment, as shown in fig. 6, after step S202, that is, after sending the query request to the server, the query request carries the local organization structure status identifier, the method further includes:

step 602, receiving query request rejection information and a first delay request time returned by the server.

The query request rejection information is used to rapidly reject the query request sent by the terminal, and may be a reminder information, such as "the server is busy, please try again later". The first delay request time refers to how long later the terminal can resend the inquiry request. In one embodiment, the first delay request time may be preset, such as setting the fixed delay request time to 5 seconds. In one embodiment, the first delay request time may also be calculated by the server according to the bandwidth usage of the server. For example, if the server calculates that 3 seconds later, there is enough server bandwidth to use, the first delay request time is 3 seconds.

Specifically, when the terminal sends an inquiry request to the server and the server receives the inquiry request, the server encounters a pressure bottleneck, for example, the number of processable requests reaches a maximum upper limit, and the inquiry request cannot be processed, and at this time, the server generates inquiry request rejection information and a first delay request time. And returning the query request rejection information and the first delay request time to the terminal, and displaying the query request rejection information and the first delay request time received by the terminal. For example, a message "server is busy, please try again after 5 seconds" is shown.

Step 604, obtaining a first current time point, and determining a first target time point according to the first current time point and the first delay request time.

Step 606, a query request is sent to the server at the first target point in time.

The first current time point is a time point when the terminal receives the inquiry request rejection information and the first delay request time. The first target time point refers to a time point at which the inquiry request is made again.

Specifically, the terminal obtains a first current time point, calculates a first target time point according to the first current time point and the first delay request time, that is, adds the first delay request time to the first current time point to obtain the first target time point, and then sends an inquiry request to the server at the first target time point. In one embodiment, the terminal may also send the query request to the server after the first target point in time has elapsed.

In a specific embodiment, as shown in fig. 7, a timing chart of query request resending is shown, in which a user terminal sends a query request to a server, the server detects that a pressure bottleneck is encountered, at this time, request rejection information and a request delay time are sent to the user terminal, and the user terminal resends the query request to the server after the request delay time.

In one embodiment, as shown in fig. 8, after step S206, that is, after sending the change node information synchronization request to the server according to the organizational structure change node state information and the organizational structure change node operation type, the method further includes:

step 802, receiving the change node information synchronization request rejection information and the second delay request time returned by the server.

The change node information synchronization request rejection information is used to rapidly reject the change node information synchronization request sent by the terminal, and may be a reminding information such as "the server is busy, please try again later" and the like. The second delay request time refers to how long later the terminal can transmit the change node information synchronization request. In one embodiment, the first delay request time may be preset, such as setting the fixed delay request time to 5 seconds. In one embodiment, the first delay request time may also be calculated according to the bandwidth usage of the server. For example, if the server calculates that 3 seconds later, there is enough server bandwidth to use, the second delay request time is 3 seconds.

Specifically, when the server receives a change node synchronization request sent by the terminal and cannot process the change node synchronization request in time, change node information synchronization request rejection information and second delay request time are generated and sent to the terminal, and the terminal receives and stores the change node information synchronization request rejection information and the second delay request time returned by the server.

And step 804, acquiring a second current time point, and determining a second target time point according to the second current time point and the second delay request time.

Step 806, sending a change node information synchronization request to the server at the second target time point.

The second current time point is a time point when the terminal receives the change node information synchronization request rejection information and the second delay request time sent by the server. The second target time point is a time point at which the change node information synchronization request is retransmitted.

Specifically, the terminal obtains a second current time point, and calculates a second target time point according to the second current time point and the second delay request time, that is, calculates the sum of the second current time point and the second delay request time to obtain the second target time point. And then the terminal sends a node information change synchronization request to the server at a second target time point. In one embodiment, the terminal may also send a change node information synchronization request to the server after the second target time point.

In a specific embodiment, as shown in fig. 9, a timing chart of the change node information synchronization request retransmission is shown, in which a user terminal transmits a change node information synchronization request to a server, the server detects that the number of synchronization requests exceeds a processing range, at this time, the server transmits request rejection information and a delay request time to the user terminal, and the user terminal retransmits the change node information synchronization request to the server after the delay request time.

In the above embodiment, when the terminal receives the request rejection information and the request delay time, the terminal retransmits the request after the request delay time, so that the server load can be effectively adjusted, and the terminal cannot update the organization.

In one embodiment, the step 208 of obtaining the change node information sent by the server according to the change node information synchronization request includes the steps of:

and when the information synchronization of the change nodes is interrupted, acquiring the information synchronization progress of the current change nodes, and storing the information synchronization progress of the current change nodes. And when the changed node information is resynchronized, acquiring unsynchronized changed node information from the server according to the synchronization progress of the current changed node information.

The interruption of the synchronization of the change node information means that the server cannot continue to synchronize the change node information due to network connection failure or the server actively stops synchronizing the change node information due to load pressure. The current change node information synchronization progress refers to the node which has completed the change node information synchronously. For example, change node information corresponding to the nodes 1, 2, and 3 needs to be synchronized, when the synchronization node 1 and the node 2 are completed, synchronization of the change node information is interrupted, and at this time, information of the synchronized node 1 and the synchronized node 2 is obtained, so that the synchronization progress of the previous change node information is obtained. The re-synchronization of the change node information means that the server continues to transmit the change node information to the terminal. The unsynchronized change node information is change node information that is not acquired from the server.

Specifically, in the synchronization process, when the terminal detects that the information synchronization of the change node is interrupted, the information synchronization progress of the current change node is obtained, and the information synchronization progress of the current change node is stored. And when the changed node information is resynchronized, acquiring unsynchronized changed node information from the server according to the synchronization progress of the current changed node information.

In the embodiment, the unsynchronized changed node information is acquired from the server according to the synchronization progress of the current changed node information, so that the synchronized data does not need to be synchronized again, the efficiency is improved, and the network resources are saved.

In one embodiment, as shown in fig. 10, the organizational structure synchronization method further comprises:

step 1002, receiving a session request with a target user, and searching node information of the target user according to the session request; and when the target user node information is not found, sending a target user node information synchronization request to the server.

And step 1004, receiving the target user node information returned by the server, and displaying the session page according to the target user node information.

The target user refers to a user for a terminal to perform a session in the instant messaging application. For example, user a sends a session request to user B through the computing instant messaging application. The node information of the target user refers to node information corresponding to the target user. And the terminal can normally carry out conversation with the target user only when the enterprise organization architecture stored in the terminal stores the node information of the target user.

Specifically, the terminal receives a session request with a target user through a computing communication application, searches node information of the target user according to the session request, indicates that the terminal does not synchronize the node information of the target user when the node information of the target user is not searched, and immediately sends a node information synchronization request of the target user to the server at the moment. And when receiving the target user node information synchronization request, the server searches the target user node information and returns the target user node information to the terminal. And the terminal displays a session page according to the node information of the target user and carries out session communication with the target user through the session page. Namely, the session can be realized without waiting for the synchronous completion of all the organizational structures, so that the waiting time of the user is reduced, and the use by the user is facilitated.

In one embodiment, as shown in fig. 11, there is provided a method for synchronizing a tissue architecture, which is described by taking the method as an example applied to the server in fig. 1, and includes the following steps:

step 1102, receiving a query request sent by a terminal, where the query request carries a local organization structure status identifier.

Specifically, the server receives an inquiry request sent by a terminal, where the inquiry request carries a local organization structure state identifier, and the server may receive inquiry requests sent by different terminals, where the inquiry requests carry local organization structure state identifiers corresponding to the terminals.

Step 1102, acquiring a server organization structure state identifier, matching the server organization structure state identifier with a local organization structure state identifier, and acquiring organization structure change information when a matching result meets preset matching; the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier.

The preset matching is a matching result that the preset server organization structure state identification is inconsistent with the local organization structure state identification.

Specifically, the server obtains the server side organization structure state identifier, matches the server side organization structure state identifier with the local organization structure state identifier, and returns a prompt message that the organization structure is latest to the corresponding terminal when the matching result is that the server side organization structure state identifier is consistent with the local organization structure state identifier. And when the matching result is that the server side organization structure state identification is inconsistent with the local organization structure state identification, the server acquires organization structure change information according to the server side organization structure state identification and the local organization structure state identification. And the server searches a node change record between the organization structure state identifier of the server and the organization structure state corresponding to the local organization structure state identifier, and acquires the organization structure change information from the node change record.

In one embodiment, the server side organizational structure state identifier and the local organizational structure state identifier are adjacent organizational structure state identifiers, for example, the server side organizational structure state identifier is a second version, and the local organizational structure state identifier is a first version.

In an embodiment, the server fabric state identifier and the local fabric state identifier may also be non-adjacent fabric state identifiers, for example, the server fabric state identifier is a third version, and the local fabric state identifier is a first version. And the server records the node change records corresponding to each organization structure state, merges the node change records corresponding to each organization structure state to obtain a final node change record, and acquires the organization structure change information from the final node change record. The merging of the node change records corresponding to each organization structure state refers to merging change records of the same node in the node change records corresponding to the second organization structure state in the node change records corresponding to the first organization structure state, for example, the second organization structure state deletes the node a, the third organization structure state adds the node a, and merges records of the deleted node a and the added node a, so that the final node change record has no change record of the node a, which is equivalent to no change of the node a.

Step 1102, when the state information of the organizational structure change node meets the preset increment synchronization condition, sending the organizational structure change information to a terminal.

The preset incremental synchronization condition is a preset condition for sending the organization structure change information, and may be that the number of change nodes corresponding to the state information of the organization structure change nodes does not exceed a preset threshold, for example, the number of change nodes does not exceed 10 ten thousand nodes, or that information that all nodes need to be synchronized does not exist in the state information of the organization structure change nodes. For example, the identity of the organizational structure that indicates whether the user is online may need to be updated.

Specifically, the server judges that when the state information of the organization architecture change node meets the preset increment synchronization condition, the organization architecture change information is sent to the terminal.

Step 1102, the receiving terminal obtains corresponding change node information according to the state information of the organization structure change node and the operation type of the organization structure change node.

Step 1102 is to transmit the changed node information to the terminal.

Specifically, when the server receives a change node information synchronization request sent by the terminal according to the state information of the organization structure change node and the operation type of the organization structure change node, the server searches the corresponding change node information from the server organization structure according to the state information of the organization structure change node and the operation type of the organization structure change node. And then sending the searched change node information to the terminal. For example, the state of the new department a is the 3 rd version, and at this time, the department a information corresponding to the 3 rd version of the department a is found in the server organization structure. And sending the department A information to a terminal.

In the above embodiment, by matching the server organization structure state identifier with the local organization structure state identifier, when the matching result meets the preset matching property, the organization structure change information is obtained, and when the organization structure change node state information meets the preset increment synchronization condition, the organization structure change information is sent to the terminal, the change node information synchronization request is received, and the corresponding change node information is obtained according to the organization structure change node state information and the operation type of the organization structure change node. The changed node information sending terminal can enable the server to update the changed node information in an incremental mode, so that the information of all nodes is prevented from being updated in a full mode, the efficiency of organization and architecture synchronization is improved, the bandwidth of the server is reduced, and the server resources are saved.

In one embodiment, as shown in fig. 12, the organizational structure synchronization method further comprises:

step 1202, when the state information of the organizational structure change node does not meet the preset increment synchronization condition, the state information of the organizational structure full-scale node is sent to the terminal, so that the terminal compares the state information of the organizational structure full-scale node with the state information of the local organizational structure full-scale node according to the state information of the organizational structure full-scale node, and the state information of the target organizational structure change node and the operation type of the target organizational structure change node are obtained.

The state information of the organization architecture full nodes refers to state information corresponding to all nodes in the organization architecture stored by the server, and the state information of the local organization architecture full nodes refers to state information corresponding to all nodes in the organization architecture stored by the terminal. The target organization architecture change node state information refers to state information of changed nodes obtained by comparing organization architecture full-scale node state information with local organization architecture full-scale node state information in a terminal. The operation type of the target organization architecture change node refers to the operation type of the changed node obtained after comparing the state information of the organization architecture full amount node with the state information of the local organization architecture full amount node in the terminal, and the operation type includes but is not limited to node deleting operation, node adding operation and node updating operation. Each node sending a change has a corresponding operation type.

Specifically, when the state information of the organizational structure change node does not meet the preset increment synchronization condition, the state information of the organizational structure full-scale node is sent to the terminal, the terminal receives the state information of the organizational structure full-scale node and compares the state information with the stored state information of the local organizational structure full-scale node to obtain the state information of the target organizational structure change node and the operation type of the target organizational structure change node, and a target change node information synchronization request is sent to the server according to the state information of the target organizational structure change node and the operation type of the target organizational structure change node.

Step 1204, the receiving terminal obtains corresponding target change node information according to the target change node information synchronization request sent by the target organization structure change node state information and the target organization structure change node operation type.

Step 1206, transmitting the destination change node information to the terminal.

The target change node information refers to node information corresponding to a node which needs to be synchronized and changed after the state information of the organization architecture full-scale node is compared with the state information of the local organization architecture full-scale node in the terminal.

Specifically, the server receives a target change node information synchronization request sent by the terminal according to the state information of the target organization structure change node and the operation type of the target organization structure change node, searches corresponding target change node information in the organization structure of the server according to the state information of the target organization structure change node and the operation type of the target organization structure change node, and then synchronizes the organization structure with the searched target change node information sending terminal.

In the above embodiment, when the state information of the fabric change node does not meet the preset incremental synchronization condition, the state information of the fabric full-scale node is sent to the terminal, so that the terminal compares the state information of the fabric full-scale node with the state information of the local fabric full-scale node to obtain the state information of the target fabric change node and the operation type of the target fabric change node, and then the state information of the target fabric change node and the operation type of the target fabric change node are used to synchronize the fabric, thereby saving server resources and improving the synchronization efficiency of the fabric.

In an embodiment, as shown in fig. 13, after step 1102, after receiving an inquiry request sent by a terminal, where the inquiry request carries a local organization architecture state identifier, the method further includes:

step 1302, detecting whether a preset pressure bottleneck value is reached, and generating query request rejection information and a first delay request time when the preset pressure bottleneck value is reached.

In step 1304, the inquiry request rejection information and the first delay request time are returned to the terminal.

In step 1306, an inquiry request sent by the terminal after the first delay request time is received.

The preset pressure bottleneck value is a preset upper limit value of the server load, and may also be calculated according to the service condition of the server, for example, the preset pressure bottleneck value may be calculated according to a CPU (central processing unit) usage rate, a memory usage rate, an input/output consumption rate, and the like of the server.

Specifically, the server acquires data such as the current CPU utilization rate, the memory utilization rate, the input/output consumption rate, and the like, calculates a current load value according to the current CPU utilization rate, the memory utilization rate, and the input/output consumption rate, determines whether the current load value exceeds a preset pressure bottleneck value, and when the current load value exceeds the preset pressure bottleneck value, the query request cannot be normally processed, and at this time, generates query request rejection information and first delay request time. The server returns the inquiry request rejection information and the first delay request time to the terminal. And then the server receives the query request sent by the terminal after the first delay request time, and performs subsequent processing.

In an embodiment, as shown in fig. 14, after step 1108, that is, after receiving a change node information synchronization request sent by a terminal according to the state information of the organization architecture change node and the operation type of the organization architecture change node, the method further includes:

step 1402, detecting whether a preset pressure bottleneck value is reached, and generating change node information synchronization request rejection information and second delay request time when the preset pressure bottleneck value is reached;

step 1404, returning the information of the change node information synchronization request rejection and the second delay request time to the terminal;

in step 1406, the change node information synchronization request transmitted by the terminal after the second delay request time is received.

Specifically, the server obtains data such as a current CPU utilization rate, a memory utilization rate, and an Input/Output (IO) consumption rate, calculates a current load value according to the current CPU utilization rate, the memory utilization rate, and the IO consumption rate, determines whether the current load value exceeds a preset pressure bottleneck value, and when the current load value exceeds the preset pressure bottleneck value, the change node information synchronization request cannot be normally processed, and at this time, generates change node information synchronization request rejection information and a second delay request time. And the server returns the change node information synchronization request rejection information and the first delay request time to the terminal. And then the server receives the change node information synchronization request sent by the terminal after the second delay request time, and carries out subsequent processing.

In a specific embodiment, the server receives the requests sent by 5 terminals at the same time, and the maximum number of requests that the server can load is 4. At this time, the server generates request rejection information and delay request time corresponding to one terminal request, returns to the corresponding terminal, and processes the requests sent by other 4 terminals.

In the embodiment, when the request is received, the server detects whether the preset pressure bottleneck value is reached, when the preset pressure bottleneck value is reached, the request rejection information and the delay request time are generated, and the request rejection information and the delay request time are returned to the terminal, so that the terminal resends the request after the request time is delayed, the load can be effectively adjusted, and the problem that the organization framework cannot be synchronized is avoided.

In one embodiment, step 1110, the sending the change node information to the terminal includes:

and detecting the current network state, stopping sending the change node information to the terminal when the current network state meets the preset network interruption condition, and storing the synchronous progress of the change node information. And when the current network state meets the preset network recovery condition, sending unsynchronized changed node information to the terminal according to the changed node information synchronization progress.

The current network state refers to the current network state of the server, and includes but is not limited to a network connection state and a network traffic usage state. The preset network interruption condition refers to a preset condition that the terminal sends the node change information to the terminal, and includes a condition that the network connection state is in an unstable state, such as continuous disconnection and reconnection of the network, or a condition that the network traffic usage is suddenly increased, such as that the current network traffic usage is suddenly increased to a preset threshold. The preset network recovery condition refers to a preset condition for sending the node change information to the terminal, and includes but is not limited to normal network connection state and normal network traffic usage.

Specifically, the server monitors the current network state, stops sending the change node information to the terminal when detecting that the current network state meets the preset network interruption condition, and stores the synchronous progress of the change node information corresponding to the terminal, so that the problem of sending the change node information is avoided, and the change node information received by the terminal is inaccurate. When the network state of the server returns to normal, namely when the current network state is detected to accord with the preset network recovery condition, unsynchronized changed node information is sent to the terminal according to the synchronous progress of the changed node information, so that the terminal is ensured to obtain accurate and correct changed node information.

In a specific embodiment, as shown in fig. 15, a method for synchronizing a tissue architecture is provided, which specifically includes the following steps:

step 1502, the terminal sends a query request to the server, where the query request carries the status identifier of the local organization architecture.

Step 1504, the server receives the query request sent by the terminal, acquires the server organization structure state identifier, matches the server organization structure state identifier with the local organization structure state identifier, and acquires organization structure change information when the matching result meets the preset matching; the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier.

And step 1506, when the state information of the organization structure change node meets the preset increment synchronization condition, the server sends the organization structure change information to the terminal.

Step 1508, the terminal receives the organization structure change information returned by the server, obtains the local organization structure node state information, and detects the organization structure change node state information and the organization structure change node operation type according to the local organization structure node state information.

In step 1510, when the state information of the organization structure change node is detected and the operation type of the organization structure change node passes, the terminal acquires the state information of the organization structure change node corresponding to the operation of the new node and the operation of the update node.

In step 1512, the terminal generates each parallel change node information synchronization request according to the new node operation and the state information of the organization structure change node corresponding to the update node operation, and sends each parallel change node information synchronization request to the server in parallel.

Step 1514, the server receives each parallel change node information synchronization request in parallel, acquires corresponding each parallel change node information according to each parallel change node information synchronization request, and returns each parallel change node information to the terminal.

Step 1516, the terminal obtains the information of each parallel change node sent by the server according to the synchronous request of the information of each parallel change node.

And 1518, updating the local organization structure corresponding to the local organization structure state identifier according to the parallel change node information, and deleting the corresponding node in the local organization structure according to the delete node operation and the organization structure change node state information corresponding to the delete node operation.

Step 1520, replace the local organization structure status identifier with the server organization structure status identifier.

The application also provides an application scenario applying the organization framework synchronization method. Specifically, the application of the organization structure synchronization method in the application scenario is as follows:

fig. 16 is a timing chart of the organizational structure synchronization method in the application scenario. Specifically, the method comprises the following steps:

when a user A logs in the enterprise instant messaging application, the enterprise organization architecture is synchronized, and at the moment, a user A terminal sends a query request to a server, wherein the query request carries a state identifier 1.1.3. When the server receives the query request, the server acquires the state identifier 1.2.1 stored in the server, compares and detects the state identifier 1.1.3 and the state identifier 1.2.1 to obtain inconsistent detection results, and at the moment, the server acquires a state update record, for example, the state identifier 1.2.1 adds a department A and deletes a user M of the department C compared with the state identifier 1.1.3, and updates a user H of the department F. At this time, the server acquires the organizational structure change information, including the newly added department a and the corresponding department status identifier 1.2.1.a, deletes the user M and the corresponding user status identifier 1.1.3.c.m, and updates the user H and the corresponding user status identifier 1.2.1. f.h. And sending the organization architecture change information to the user terminal. The user terminal receives the organization structure change information returned by the server, acquires the state information of the local organization structure node, and detects the state information of the organization structure change node and the operation type of the organization structure change node in the organization structure change information according to the state information of the local organization structure node. When the state information of the organization structure change node and the operation type of the organization structure change node are detected to pass, the terminal acquires the state information of the organization structure change node corresponding to the operation of the new addition node and the operation of the update node, namely acquires a new addition department A and a corresponding department state identifier 1.2.1.a, and an update user H and a corresponding user state identifier 1.2.1. f.h. The terminal generates 2 change node information synchronization requests, namely a synchronization request for a change department A and a synchronization request for an update user H, and sends the synchronization requests to the server in parallel.

The server receives the synchronization request, namely the synchronization request of the newly added department A and the corresponding department state identifier 1.2.1.a and the synchronization request of the updated user H and the corresponding user state identifier 1.2.1.f.h, finds the detailed information of the department A including the name of the department, the number of people in the department, the position of the department, the name of the user in the department and the like according to the newly added department A and the corresponding department state identifier 1.2.1.a, and returns the detailed information of the department A to the user terminal. Meanwhile, the server searches the detailed information of the user A, including the user name, the user contact method including but not limited to the telephone and the mailbox, the position of the user company, the information of the department to which the user belongs and the like, according to the synchronization request for updating the user H and the corresponding user state identifier 1.2.1.f.h, and sends the detailed information of the user A to the user terminal.

After the user terminal receives the detailed information of the department A and the detailed information of the user A, the component architecture stored in the terminal is updated by using the detailed information of the department A and the detailed information of the user A, namely, the detailed information of the department A is added and the detailed information of the user A is replaced. And at the same time, delete the detailed information of the user M of the department C. When the synchronization is completed, the organizational structure identification in the terminal is replaced with 1.2.1.

It should be understood that although the various steps in the flowcharts of fig. 2-4, 6, 8, and 10-15 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-4, 6, 8, and 10-15 may include multiple steps or phases that are not necessarily performed at the same time, but may be performed at different times, and the order of execution of the steps or phases is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the other steps or phases.

In one embodiment, as shown in fig. 17, there is provided an organization architecture synchronization apparatus 1700, which may be a part of a computer device using a software module or a hardware module, or a combination of the two, and specifically includes: a query request sending module 1702, an information receiving module 1704, a synchronization request sending module 1706, a node information obtaining module 1708, and an updating module 1710, wherein:

a query request sending module 1702, configured to send a query request to a server, where the query request carries a local organization structure status identifier;

an information receiving module 1704, configured to receive organization structure change information returned by the server, where the organization structure change information includes state information of an organization structure change node, an operation type of the organization structure change node, and a service-side organization structure state identifier, and the organization structure change information is obtained by the server according to matching between the local organization structure state identifier and the service-side organization structure state identifier;

a synchronization request sending module 1706, configured to send a change node information synchronization request to the server according to the state information of the organization structure change node and the operation type of the organization structure change node;

a node information obtaining module 1708, configured to obtain change node information sent by the server according to the change node information synchronization request;

an updating module 1710, configured to update the local organization architecture corresponding to the local organization architecture state identifier according to the change node information and replace the local organization architecture state identifier with the server organization architecture state identifier.

In one embodiment, the organization structure change node state information includes an organization structure change node type and an organization structure change node state identifier, and the change node information includes an organization structure change node type and node data corresponding to the organization structure change node.

In one embodiment, the fabric synchronization apparatus 1700 further comprises:

the local detection module is used for acquiring the state information of the local organization structure node and detecting the state information of the organization structure change node and the operation type of the organization structure change node according to the state information of the local organization structure node;

the synchronization request sending module 1706 is further configured to send a change node information synchronization request to the server according to the state information of the organization structure change node and the operation type of the organization structure change node when detecting that the state information of the organization structure change node and the operation type of the organization structure change node pass.

In an embodiment, the synchronization request sending module 1706 is further configured to, when detecting that the state information of the organization structure change node and the operation type of the organization structure change node fail, obtain the state information of the detected failed node, and send a reacquisition request of the state information of the failed node to the server according to the state information of the detected failed node; and receiving the target node state information corresponding to the failed node state information returned by the server.

In one embodiment, the synchronization request sending module 1706 includes:

the information acquisition unit is used for acquiring the state information of the organizational structure change node corresponding to the newly added node operation and/or the updated node operation when the type of the organizational structure change node operation comprises the newly added node operation and/or the updated node operation;

the request generating unit is used for generating each parallel change node information synchronization request according to the state information of the organization architecture change node corresponding to the newly added node operation and/or the updated node operation;

and the parallel sending unit is used for sending the parallel change node information synchronization requests to the server in parallel.

In one embodiment, the organization architecture synchronization apparatus 1700 is further configured to receive query request rejection information and a first delay request time returned by the server; acquiring a first current time point, and determining a first target time point according to the first current time point and the first delay request time; a query request is sent to a server at a first target point in time.

In one embodiment, the organization architecture synchronization apparatus 1700 is further configured to receive the change node information synchronization request rejection information and the second delay request time returned by the server; acquiring a second current time point, and determining a second target time point according to the second current time point and the second delay request time; and sending a change node information synchronization request to the server at the second target time point.

In one embodiment, the node information obtaining module 1708 is further configured to, when synchronization of the change node information is interrupted, obtain a current change node information synchronization progress, and store the current change node information synchronization progress; and when the changed node information is resynchronized, acquiring unsynchronized changed node information from the server according to the synchronization progress of the current changed node information.

In one embodiment, the organizational structure synchronization device 1700 is further configured to receive a session request with a target user, and search node information of the target user according to the session request; when the target user node information is not found, sending a target user node information synchronization request to a server; and receiving target user node information returned by the server, and displaying a session page according to the target user node information.

In one embodiment, as shown in fig. 18, there is provided an organization architecture synchronization apparatus 1800, which may be a part of a computer device by using a software module or a hardware module, or a combination of the two, specifically comprising: a request receiving module 1802, an information obtaining module 1804, an information sending module 1806, a synchronization request receiving module 1808, and a node information sending module 1810, wherein:

a request receiving module 1802, configured to receive a query request sent by a terminal, where the query request carries a local organization structure status identifier;

the information obtaining module 1804 is configured to obtain the server-side architecture state identifier, match the server-side architecture state identifier with the local architecture state identifier, and obtain the organization architecture change information when a matching result meets preset matching; the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier;

an information sending module 1806, configured to send the organization structure change information to a terminal when the state information of the organization structure change node meets a preset increment synchronization condition;

a synchronization request receiving module 1808, configured to receive a change node information synchronization request sent by a terminal according to the state information of the organization structure change node and the operation type of the organization structure change node, and obtain corresponding change node information according to the state information of the organization structure change node and the operation type of the organization structure change node;

a node information sending module 1810, configured to send the changed node information to the terminal.

In one embodiment, the organization architecture synchronization apparatus 1800 is further configured to send the state information of the organization architecture complete node to the terminal when the state information of the organization architecture change node does not meet the preset incremental synchronization condition, so that the terminal compares the state information of the organization architecture complete node with the state information of the local organization architecture complete node according to the state information of the organization architecture complete node to obtain the state information of the target organization architecture change node and the operation type of the target organization architecture change node; receiving a target change node information synchronization request sent by a terminal according to the state information of the target organization structure change node and the operation type of the target organization structure change node, and acquiring corresponding target change node information according to the target change node information synchronization request; and sending the target change node information to a terminal.

In one embodiment, the organization architecture synchronization device 1800 is further configured to detect whether a preset pressure bottleneck value is reached, and when the preset pressure bottleneck value is reached, generate query request rejection information and a first delay request time; returning the inquiry request rejection information and the first delay request time to the terminal; and receiving the inquiry request sent by the terminal after the first delay request time.

In one embodiment, the organization architecture synchronization apparatus 1800 is further configured to detect whether a preset pressure bottleneck value is reached, and generate change node information synchronization request rejection information and a second delay request time when the preset pressure bottleneck value is reached; returning the information of the change node information synchronization request refusing information and the second delay request time to the terminal; and receiving the change node information synchronization request sent by the terminal after the second delay request time.

In one embodiment, the node information sending module 1810 is further configured to detect a current network state, stop sending the change node information to the terminal when the current network state meets a preset network interruption condition, and store a synchronization progress of the change node information; when the current network state meets the preset network recovery condition, sending unsynchronized changed node information to the terminal according to the changed node information synchronization progress

For specific limitations of the tissue architecture synchronization apparatus, reference may be made to the above limitations of the tissue architecture synchronization method, which are not described herein again. The modules in the above described organizational structure synchronization device can be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 19. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is for storing organizational structure data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of tissue architecture synchronization.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 20. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a method of tissue architecture synchronization. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the configurations shown in fig. 18 or 19 are only block diagrams of some of the configurations relevant to the present application, and do not constitute a limitation on the computer apparatus to which the present application is applied, and a particular computer apparatus may include more or less components than those shown in the drawings, or may combine some components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The computer instructions are read by a processor of a computer device from a computer-readable storage medium, and the computer instructions are executed by the processor to cause the computer device to perform the steps in the above-mentioned method embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1.A method of tissue architecture synchronization, the method comprising:

sending a query request to a server, wherein the query request carries a local organization architecture state identifier;

sending a node change information synchronization request to the server according to the state information of the organization architecture change node and the operation type of the organization architecture change node;

acquiring the change node information sent by the server according to the change node information synchronous request;

2. The method according to claim 1, wherein the organization architecture change node state information includes an organization architecture change node type and an organization architecture change node state identifier, and the change node information includes an organization architecture change node type and node data corresponding to the organization architecture change node.

3. The method according to claim 1, wherein after the receiving organization architecture change information returned by the server, the organization architecture change information including organization architecture change node state information, an organization architecture change node operation type, and a server side organization architecture state identifier, the organization architecture change information being obtained by the server according to a matching property of the local organization architecture state identifier and the server side organization architecture state identifier, further comprising:

acquiring local organization architecture node state information, and detecting the organization architecture change node state information and the operation type of the organization architecture change node according to the local organization architecture node state information;

sending a node change information synchronization request to the server according to the state information of the organization architecture change node and the operation type of the organization architecture change node, wherein the node change information synchronization request comprises the following steps:

and when the state information of the organization architecture change node and the operation type of the organization architecture change node are detected to pass, sending a change node information synchronization request to the server according to the state information of the organization architecture change node and the operation type of the organization architecture change node.

4. The method of claim 3, wherein sending a change node information synchronization request to the server based on the organizational change node state information and the organizational change node operation type comprises:

when detecting that the state information of the organization architecture change node and the operation type of the organization architecture change node fail, acquiring the state information of the detected fail node, and sending a request for reacquiring the state information of the fail node to the server according to the state information of the detected fail node;

and receiving the target node state information corresponding to the failed node state information returned by the server.

5. The method of claim 1, wherein the type of the fabric change node operation comprises at least one of a delete node operation, an add node operation, and an update node operation, and wherein sending a change node information synchronization request to the server based on the fabric change node state information and the type of the fabric change node operation comprises:

when the operation type of the organizational structure change node comprises a newly added node operation and/or an updated node operation, acquiring state information of the organizational structure change node corresponding to the newly added node operation and/or the updated node operation;

generating each parallel change node information synchronization request according to the organization architecture change node state information corresponding to the newly added node operation and/or the updated node operation;

and sending the information synchronization request of each parallel change node to the server in parallel.

6. The method according to claim 1, wherein after said sending a query request to a server, said query request carrying a local organization architecture state identifier, further comprising:

receiving inquiry request rejection information and first delay request time returned by the server;

acquiring a first current time point, and determining a first target time point according to the first current time point and the first delay request time;

and sending the query request to the server at the first target time point.

7. The method of claim 1, after sending a change node information synchronization request to the server according to the organizational change node state information and the organizational change node operation type, further comprising:

receiving the change node information synchronization request rejection information and the second delay request time returned by the server;

acquiring a second current time point, and determining a second target time point according to the second current time point and the second delay request time;

and sending the change node information synchronization request to the server at the second target time point.

8. The method according to claim 1, wherein the obtaining of the change node information sent by the server according to the change node information synchronization request comprises:

when the information synchronization of the change nodes is interrupted, acquiring the information synchronization progress of the current change nodes, and storing the information synchronization progress of the current change nodes;

and when the changed node information is resynchronized, acquiring unsynchronized changed node information from the server according to the synchronization progress of the current changed node information.

9. The method of claim 1, further comprising:

receiving a conversation request with a target user, and searching node information of the target user according to the conversation request; when the target user node information is not found, sending a target user node information synchronization request to the server;

and receiving target user node information returned by the server, and displaying a session page according to the target user node information.

10. A method of tissue architecture synchronization, the method comprising:

acquiring a server side organization structure state identifier, matching the server side organization structure state identifier with the local organization structure state identifier, and acquiring organization structure change information when a matching result meets preset matching; the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier;

when the state information of the organization architecture change node meets a preset increment synchronization condition, sending the organization architecture change information to the terminal;

receiving a change node information synchronization request sent by the terminal according to the state information of the organization architecture change node and the operation type of the organization architecture change node, and acquiring corresponding change node information according to the state information of the organization architecture change node and the operation type of the organization architecture change node;

and sending the information of the changed nodes to the terminal.

11. The method of claim 10, further comprising:

when the state information of the organizational structure change node does not meet the preset increment synchronization condition, the state information of the organizational structure full-scale node is sent to the terminal, so that the terminal compares the state information of the organizational structure full-scale node with the state information of the local organizational structure full-scale node according to the state information of the organizational structure full-scale node to obtain the state information of a target organizational structure change node and the operation type of the target organizational structure change node;

receiving a target change node information synchronization request sent by the terminal according to the state information of the target organization structure change node and the operation type of the target organization structure change node, and acquiring corresponding target change node information according to the target change node information synchronization request;

and sending the target change node information to the terminal.

12. A tissue architecture synchronization device, the device comprising:

the information receiving module is used for receiving organization architecture change information returned by the server, wherein the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier, and the organization architecture change information is obtained by the server according to the matching of the local organization architecture state identifier and the service end organization architecture state identifier;

a synchronization request sending module, configured to send a change node information synchronization request to the server according to the state information of the organization structure change node and the operation type of the organization structure change node;

the node information acquisition module is used for acquiring the changed node information sent by the server according to the changed node information synchronous request;

and the updating module is used for updating the local organization structure corresponding to the local organization structure state identification according to the change node information and replacing the local organization structure state identification with the server organization structure state identification.

13. A tissue architecture synchronization device, the device comprising:

a request receiving module, configured to receive a query request sent by a terminal, where the query request carries a local organization structure status identifier;

the information acquisition module is used for acquiring a server side organization structure state identifier, matching the server side organization structure state identifier with the local organization structure state identifier and acquiring organization structure change information when a matching result meets preset matching; the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a service end organization architecture state identifier;

the information sending module is used for sending the organization structure change information to the terminal when the state information of the organization structure change node meets the preset increment synchronization condition;

a synchronous request receiving module, configured to receive a change node information synchronous request sent by the terminal according to the state information of the organization structure change node and the operation type of the organization structure change node, and obtain corresponding change node information according to the state information of the organization structure change node and the operation type of the organization structure change node;

14. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 12.

15. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 12.