CN113872994B

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

Info

Publication number: CN113872994B
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: 2024-08-09
Anticipated expiration: 2040-06-30
Also published as: CN113872994A

Abstract

The application relates to an organization architecture synchronization method, an organization architecture synchronization device, computer equipment 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 architecture state identification. And receiving organization architecture change information returned by the server, wherein the organization architecture change information is acquired by the server according to the matching property of the local organization architecture state identification and the server side organization architecture state identification. And sending a change node information synchronization request to the server according to the organization architecture change node state information and the organization architecture change node operation type in the organization architecture change information. And acquiring the change node information sent by the server according to the change node information synchronization request. And updating the local organization architecture corresponding to the local organization architecture state identifier according to the changed node information and replacing the local organization architecture state identifier with the server organization architecture state identifier. By adopting the method, the synchronization time and the bandwidth can be saved.

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 an organization architecture synchronization method, an apparatus, 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 completed. However, since the amount of the current complete organization architecture data is particularly large, a great amount of time and server bandwidth are required for synchronizing the organization architecture data, so that the instant messaging application cannot be normally used.

Disclosure of Invention

In view of the foregoing, it is desirable to provide an organization architecture synchronization method, apparatus, computer device, and storage medium that can save time for synchronizing organization architecture and server bandwidth.

An organization architecture synchronization method, the method comprising:

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

The method comprises the steps of receiving organization architecture change information returned by a server, wherein the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identifiers, and the organization architecture change information is acquired by the server according to the matching property of local organization architecture state identifiers and server side organization architecture state identifiers;

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

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

and updating the local organization architecture corresponding to the local organization architecture state identifier according to the changed node information and replacing the local organization architecture state identifier with the server organization architecture state identifier.

An organization architecture synchronization method, the method comprising:

receiving a query request sent by a terminal, wherein the query request carries a local organization architecture 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 accords with preset matching property; the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identification;

When the organization architecture change node state information accords with a preset increment synchronization condition, sending the organization architecture change information to a terminal;

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

And sending the changed node information to the terminal.

In one embodiment, after receiving the query request sent by the terminal, the query request carries the local architecture state identifier, the method further includes:

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

Returning inquiry request refusal information and first delay request time to the terminal;

The inquiry request sent by the terminal after the first delay request time is received.

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

Detecting whether a preset pressure bottleneck value is reached, and generating synchronous request rejection information of the changed node information and second delay request time when the preset pressure bottleneck value is reached;

returning the change node information synchronous request refusal 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 change node information transmitting terminal includes:

Detecting a current network state, stopping sending the change node information to the terminal when the current network state accords with a preset network interruption condition, and storing the change node information synchronization progress;

And when the current network state accords with the preset network recovery condition, sending unsynchronized change node information to the terminal according to the change node information synchronization progress.

An organizational architecture synchronization apparatus, the apparatus comprising:

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

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, organization architecture change node operation types and server side organization architecture state identifiers, and the organization architecture change information is acquired by the server according to the matching property of the local organization architecture state identifiers and the server side organization architecture state identifiers;

The synchronous request sending module is used for sending a synchronous request for changing node information to the server according to the organization architecture changing node state information and the organization architecture changing node operation type;

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

The updating module is used for updating the local organization architecture corresponding to the local organization architecture state identifier according to the changed node information and replacing the local organization architecture state identifier with the server organization architecture state identifier

An organizational architecture device, the device comprising:

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

The information acquisition module is used for acquiring the server side organization structure state identification, matching the server side organization structure state identification with the local organization structure state identification, and acquiring organization structure change information when the matching result accords with the preset matching property; the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identification;

The information sending module is used for sending the organization architecture change information to the terminal when the organization architecture change node state information accords with a preset increment synchronization condition;

The synchronous request receiving module is used for receiving a synchronous request of changing node information sent by the terminal according to the organization architecture changing node state information and the organization architecture changing node operation type, and obtaining corresponding changing node information according to the organization architecture changing node state information and the organization architecture changing node operation type;

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

A computer device comprising a memory storing a computer program and a processor which when executing the computer program performs the steps of:

And sending the changed node information to the terminal.

A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

And sending the changed node information to the terminal.

According to the organization structure synchronization method, the device, the computer equipment and the storage medium, the inquiry request is sent to the server through the terminal, the server acquires the server organization structure state identification when receiving the inquiry request, and matches the server organization structure state identification with the local organization structure state identification, when the matching result accords with the preset matching property, organization structure change information is acquired, then the organization structure change information is returned to the terminal, when the terminal receives the organization structure change information, the change node information synchronization request is sent to the server according to the organization structure change node state information and the organization structure change node operation type, 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 identification, so that the terminal can be synchronized to the change node information, synchronization of the whole amount of node information is avoided, the organization structure synchronization efficiency is improved, and the organization structure synchronization time is saved. Meanwhile, the terminal acquires the changed node information from the server, so that the acquisition of the total node information is not needed, and the bandwidth of the server is saved.

Drawings

FIG. 1 is an application environment diagram of an organization architecture synchronization method in one embodiment;

FIG. 2 is a flow diagram of an architecture synchronization method in one embodiment;

FIG. 3 is a flow diagram of status information reception in one embodiment;

FIG. 4 is a flow diagram of parallel requests in one embodiment;

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

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

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

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

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

FIG. 10 is a flow diagram of a conversational page display, according to one embodiment;

FIG. 11 is a flowchart of another embodiment of a method for synchronizing an organization structure;

FIG. 12 is a schematic diagram of a target change node information sending process according to one embodiment;

FIG. 13 is a flow diagram of query request transmission in one embodiment;

FIG. 14 is a flow diagram of a synchronization request transmission in one embodiment;

FIG. 15 is a flow chart of an organization architecture synchronization method in one embodiment;

FIG. 16 is a timing diagram of an organization architecture 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 of an organization architecture synchronization apparatus in another embodiment;

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

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

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

The organization architecture synchronization method provided by the application can be applied to an application environment shown in figure 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 architecture state identifier; the terminal 102 receives organization architecture change information returned by the server 104, wherein the organization architecture change information comprises organization architecture change node state information, an organization architecture change node operation type and a server side organization architecture state identifier, and the organization architecture change information is acquired by the server 104 according to the matching property of the local organization architecture state identifier and the server side organization architecture state identifier; the terminal 102 sends a node changing information synchronization request to the server 104 according to the organization architecture changing node state information and the organization architecture changing node operation type; 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 architecture corresponding to the local organization architecture state identifier according to the changed node information and replaces the local organization architecture state identifier with the server organization architecture state identifier. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices, and the server 104 may be implemented by a stand-alone server or a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 2, an organization architecture synchronization method is provided, and the method is applied to the terminal in fig. 1 for illustration, it is to be understood that the method may also be applied to a system including a server and a server, and implemented through interaction between the server and the server. In this embodiment, the method includes the following steps:

step 202, a query request is sent to a server, wherein the query request carries a local organization architecture state identifier.

The query request is used for querying whether the local organization architecture state identifier is matched with the server-side organization architecture state identifier stored by the server. The organization architecture refers to the most basic structural basis of enterprise flow operation, department setting, function planning and the like, and common organization architecture forms comprise a central set weight system, a split weight system, a linear system, a matrix system and the like. The organization structure state identifier is used for uniquely identifying the state of the organization structure, and each time the organization structure is changed, the changed organization structure state identifier is generated. The local architecture state identifier refers to an architecture state identifier stored in a terminal memory, and is used for identifying an architecture state already stored in the terminal, and may be a version number, a name, a character string, etc., for example, the local architecture state identifier is a version number and is a first version.

Specifically, the terminal sends a query request to the server, wherein the query request carries the local of the terminal, and when a user logs in an enterprise instant messaging application through the terminal, the terminal acquires a local organization architecture 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 regular intervals, which may be customized, e.g., the query request is sent to the server every other interval. In one embodiment, the organization architecture may also be an organization architecture of a government department, an organization architecture of a social organization, or the like.

Step 204, receiving the organization architecture modification information returned by the server, where the organization architecture modification information includes organization architecture modification node status information, an organization architecture modification node operation type, and a server side organization architecture status identifier, and the organization architecture modification information is obtained by the server according to the matching between the local organization architecture status identifier and the server side organization architecture status identifier.

The nodes refer to nodes in an organization structure, for example, the nodes in an enterprise organization structure can be users and departments. The organization architecture change node refers to a node in the organization architecture, where a data change occurs, and the data change includes, but is not limited to, updating node data, deleting node data, and adding node data, where the updating node data refers to updating old data of an original node to new data, for example, updating a node name to a new name. Deleting node data refers to deleting data of an original node or deleting a node directly, for example, deleting a user mailbox of a user node or deleting a user node directly. The new node data refers to that the original node data is added or a node is added, for example, the user node does not store a user mailbox, and the user mailbox of the user node can be added. Or if there is no user node in the organization architecture, the user node is added. The organization architecture change node state information refers to state information corresponding to a node with data change, including but not limited to organization architecture change node state identification. Each node that changes data has corresponding state information. When the organization structure changing node state information includes state information of a plurality of organization structure changing nodes, it is indicated that data of a plurality of organization structure nodes is changed. The organization architecture change node state identifier is used for uniquely identifying the node state corresponding to the organization architecture change node, and can 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, which is different from the 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 different from the status number of the user before the change. In one embodiment, when node data changes, corresponding node state identifiers are generated, all the 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 unchanged node state identifiers, the changed node state identifiers and unchanged node state identifiers can be spliced to obtain an organization structure state identifier, and the changed node state identifiers and unchanged node state identifiers can be combined to obtain the organization structure state identifier.

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

The organization architecture change node operation type refers to a specific type of operation on the change node, including but not limited to delete node operation, update node operation, and add node operation. The node deleting operation is to delete the changed node, that is, delete the node data corresponding to the changed node in the organization architecture. The update node operation refers to updating node data of the change node. The newly added node operation refers to newly adding a corresponding changed node in the organization architecture. The matching property is used for indicating whether the local organization architecture state identification is consistent with the server organization architecture state identification, when the local organization architecture state identification is consistent with the server organization architecture state identification, the matching property is 1, and when the local organization architecture state identification is inconsistent with the server organization architecture state identification, the matching property is 0.

Specifically, when the server receives the query request, the local organization structure state identifier is matched with the server side organization structure state identifier, when the matching is consistent, the terminal directly returns the reminding information that the organization structure is up to date, and when the terminal receives the reminding information that the returned organization structure is up to date, the terminal does not process the reminding information. When the matching is inconsistent, the server acquires the stored organization structure updating record data, acquires organization structure changing information from the organization structure updating record data, and issues the organization structure changing information to the terminal. The terminal receives the organization structure changing information issued by the server and stores the organization structure changing information.

Step 206, sending a change node information synchronization request to the server according to the organization architecture change node state information and the organization architecture change node operation type.

The change node information synchronization request is used for synchronizing 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 architecture change node type and node data corresponding to the organization architecture change node, for example, when the change node type is user, the node data includes, but is not limited to, a user name, a user position, a user contact method, a department to which the user belongs, user remark information, and the like. For example, when the node type is changed to a department, the node data includes, but is not limited to, a department name, the number of department users, a department user arrangement order, a department bulletin, a department file, 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 organization architecture 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 can also send a request for synchronizing the change node information to the server according to the new node operation and the update node operation in the organization architecture change node operation type and the corresponding organization architecture change node state information, wherein the request for synchronizing the change node information can carry the new node operation and the update node operation and the corresponding new node state information and the corresponding update node state information.

Step 208, obtaining the change node information sent by the server according to the change node information synchronization request.

Specifically, when receiving the request for synchronizing the change node information, the server searches corresponding change node information according to the organization architecture change node state information and the organization architecture change node operation type carried in the request for synchronizing the change node information, and issues the change node information to the terminal, and the terminal acquires the change node information sent by the server according to the request for synchronizing the change node information.

Step 210, updating the local organization architecture corresponding to the local organization architecture state identifier according to the changed node information and replacing the local organization architecture state identifier with the server organization architecture state identifier.

Specifically, the terminal searches the corresponding local node information from the local organization architecture 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 the component architecture is synchronously completed. When the component architecture synchronization is completed, the local organization architecture state identifier stored in the terminal is replaced by the server organization architecture state identifier.

In one embodiment, the terminal stores the changed node information in the memory, deletes the node information corresponding to the local organization architecture, and replaces the local organization architecture state identifier with the server organization architecture state identifier. When the terminal needs to use the change node information, the change 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 a relationship between user nodes and a relationship between department nodes and user nodes. 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). For another example, user A and user B are affiliated to department C. The user a and the user B are stored in the form of (user a, user B). When the terminal needs to display the organization structure, the stored change node information relation pair is directly searched, and the organization structure is displayed according to the change node information relation pair.

In the organization structure synchronization method, a terminal sends a query request to a server, 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 the matching result accords with preset matching property, returns the organization structure change information to the terminal, sends a change node information synchronization request to the server according to the organization structure change node state information and the organization structure change node operation type when the terminal receives the organization structure change information, 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, so that the terminal can be synchronized to the change node information, synchronization of the whole quantity of node information is avoided, efficiency of synchronizing the organization structure is improved, and time for synchronizing the organization structure is saved. Meanwhile, the terminal acquires the changed node information from the server, so that the acquisition of the total node information is not needed, and the bandwidth of the server is saved.

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

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

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

Specifically, the terminal acquires the local organization architecture node state information from the memory, and then the organization architecture change node operation type is matched with the organization architecture change node state information by using the local organization architecture node state information. When the organization architecture change node operation type is the delete node operation, detecting the delete node operation and the corresponding organization architecture change node state information when the consistent organization architecture change node state information is matched in the local organization architecture node state information. For example, the local organization structure node state numbers are used for matching the same organization structure change node state numbers, and when the same organization structure change node state numbers are matched, node operation deleting and corresponding organization structure change node state information are detected.

When the operation type of the organization architecture change node is newly added node operation, detecting the node state information changed by the newly added node operation and the corresponding organization architecture when the consistent organization architecture change node state information is not matched in the local organization architecture node state information. When the organization architecture change node operation type is the update node operation, detecting the update node operation and the corresponding organization architecture change node state information when the consistent organization architecture change node state information is matched in the local organization architecture node state information.

Step 206, sending a request for synchronizing the change node information to the server according to the organization architecture change node state information and the organization architecture change node operation type, including:

When the organization architecture change node state information and the organization architecture change node operation type pass through detection, a change node information synchronization request is sent to a server according to the organization architecture change node state information and the organization architecture change node operation type.

Specifically, when all the organization architecture change node state information and the organization architecture change node operation types are detected to pass, the obtained organization architecture change node state information and the organization architecture change node operation types are correct. And sending a change node information synchronization request to the server according to the organization architecture change node state information and the organization architecture change node operation type. When the state information of the organization structure change node and the operation type of the organization structure change node are detected to be failed, the obtained state information of the organization structure change node and the operation type of the organization structure change node are indicated to have errors, and the organization structure change node and the operation type of the organization structure change node are re-obtained from the server.

In the above embodiment, the detection of the obtained organization architecture change node state information and the operation type of the organization architecture change node is performed by using the local organization architecture node state information, and when the detection is passed, a synchronization request is sent to the server, so that the synchronization to the wrong node data is prevented, and the accuracy of the data synchronization is ensured.

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

Step 302, when detecting that the organization architecture change node state information and the organization architecture change node operation type are not passed, acquiring the detection non-passing node state information, and sending a non-passing node state information re-acquisition request to the server according to the detection non-passing node state information.

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

The detection of the failed node state information refers to detection of the organization architecture change node state information and the organization architecture change node state information which does not pass the corresponding organization architecture change node operation type in the organization architecture change node state information. The target node state information refers to the node state information corresponding to the failed node state information which is acquired again.

Specifically, when the state information of the organization architecture change node and the operation type of the organization architecture change node are detected to fail, it is indicated that an error occurs in the state information of the organization architecture change node and the operation type of the corresponding organization architecture change node, and at this time, the correct state information of the organization architecture change node and the operation type of the corresponding organization architecture change node need to be obtained from the server. At this time, a request for reacquiring failed node state information is sent to the server, when the server receives the request for reacquiring failed node state information, the server searches for a corresponding node in an organization architecture node of the server according to the failed node state information, acquires target node state information and a corresponding target node operation type of the node, returns the target node state information and the corresponding target node operation type to the terminal, acquires the target node state information and the corresponding target node operation type corresponding to the failed node state information returned by the server, and then detects the target node state information and the corresponding target node operation type again. And performing subsequent processing until the state information of the target node and the corresponding operation type of the target node are detected to pass, so that the accuracy of data synchronization is ensured. For example, when the newly added node operation and the corresponding node state information are detected, the same node state information is matched in the node state information of the local organization architecture, the fact that the terminal has the newly added node is indicated, the fact that the newly added node operation and the corresponding node state information are wrong is indicated, at the moment, a re-acquisition request is sent to a server according to the newly added node operation and the corresponding node state information, then the target node operation and the corresponding target node state information corresponding to the wrong node are acquired, and the target node operation and the corresponding target node state information are re-detected. For another example, when the deleting node operation and the corresponding node state information are detected, the same node state information is not matched in the local organization architecture node state information, which indicates that the corresponding node is deleted in the terminal. And indicating that the deleting node operation and the corresponding node state information are wrong, sending the target node operation and the corresponding target node state information to the server according to the deleting node operation and the corresponding node state information, then acquiring the target node operation and the corresponding target node state information corresponding to the wrong node, 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 architecture node state information, and at this time, the node in the terminal is updated and does not need to be updated, which indicates that the update node operation and the corresponding node state information have errors. At this time, the terminal transmits a re-acquisition request to the server according to the updated node operation and the corresponding node state information, and then acquires the target node operation and the corresponding target node state information corresponding to the node with the error, and re-detects the target node operation and the corresponding target node state information.

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

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

Step 402, when the organization architecture change node operation type includes the newly added node operation and/or the updated node operation, obtaining organization architecture change node state information corresponding to the newly added node operation and/or the updated node operation.

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

Specifically, when the organization architecture change node operation type includes an added node operation and an updated node operation, the terminal obtains organization architecture change node state information corresponding to the added node operation and the updated node operation. In one embodiment, when the organization architecture change node operation type includes a new node operation, the terminal obtains organization architecture change node state information corresponding to the new node operation. In one embodiment, when the organization architecture change node operation type includes an update node operation, the terminal obtains organization architecture change node state information corresponding to the update node operation.

In one embodiment, when the organization architecture change node operation type includes a deletion node operation, the terminal acquires the organization architecture change node state information corresponding to the deletion node operation, searches the node state information corresponding to the organization architecture change node state information in the local organization architecture node state information, and performs deletion processing.

Step 404, 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.

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

Specifically, the terminal determines the quantity or the size of the changed node information to be synchronized according to the changed node state information of the organization architecture corresponding to the newly added node operation and the updated node operation. Dividing according to the quantity or the size of the change node information to be synchronized, and obtaining the quantity or the size of the change node information to be synchronized for each request. For example, the number of pieces of change node information required to be synchronized is 5 ten thousand, at this time, 5 ten thousand pieces of change node information required to be synchronized is divided into 10 copies on average, and 1 ten thousand pieces of change node information required to be synchronized for each request are obtained, that is, the terminal generates 10 parallel change node information synchronization requests, and the number of pieces of change node information of the request corresponding to each parallel change node information synchronization request is 1 ten thousand pieces. The division may be performed according to the size of the change node information, for example, the size of the change node information that needs to be synchronized in total is 1GB (Gigabyte, a decimal information measurement unit), and the 1GB change node information is divided into 8 parts, and the size of the change node information that needs to be synchronized per request is 128MB (MByte, a storage unit in a computer). That is, the terminal generates 8 parallel change node information synchronization requests, and the change node information of the request corresponding to each parallel change node information synchronization request is 128MB.

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

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

And step 406, transmitting 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, each parallel change node information is returned in parallel, and each parallel change node information returned by the server is received by the terminal and stored. In a specific embodiment, as shown in fig. 5, for synchronizing the timing diagram of each parallel change node information in parallel, where the user terminal wants the server to send a parallel request for synchronizing each parallel change node information, the server returns each parallel change node information to the user terminal in parallel according to the parallel request for synchronizing the parallel change node information, and the user terminal receives each parallel change node information in parallel and stores the parallel change node information.

In the above embodiment, by sending each parallel change node information synchronization request to the server in parallel, the change node information can be obtained in parallel, and the efficiency of data synchronization is improved.

In one embodiment, as shown in fig. 6, after step S202, that is, after sending a query request to the server, the query request carries the local architecture state identifier, the method further includes:

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

The inquiry request rejection information is used for rapidly rejecting the inquiry request sent by the terminal, and may be reminding information, for example, "the server is busy, and try again later. The first delay request time refers to how long the terminal can retransmit the query request after. In one embodiment, the first delay request time may be preset, such as setting a 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 there is enough server bandwidth available for use after 3 seconds, the first delay request time is 3 seconds.

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

Step 604, a first current time point is acquired, and a first target time point is determined according to the first current time point and the first delay request time.

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

The first current time point refers to 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 when the query request is made again.

Specifically, the terminal acquires a first current time point, calculates a first target time point according to the first current time point and the first delay request time, namely, the first current time point is added with the first delay request time to obtain the first target time point, and then sends a query request to the server at the first target time point. In one embodiment, the terminal may also send a 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 diagram of query request retransmission is shown, where the user terminal sends a query request to the server, and the server detects that a pressure bottleneck is encountered, at this time, sends request rejection information and delay request time to the user terminal, and after the delay request time, the user terminal retransmits the query request to the server.

In one embodiment, as shown in fig. 8, after step S206, that is, after sending a request for synchronizing change node information to the server according to the organization architecture change node state information and the organization architecture 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 for rapidly rejecting the change node information synchronization request sent by the terminal, and may be reminding information such as "the server is busy, please retry later", and the like. The second delay request time refers to how long the terminal can send the change node information synchronization request. In one embodiment, the first delay request time may be preset, such as setting a fixed delay request time to 5 seconds. In one embodiment, the first delay request time may also be calculated based on server bandwidth usage. For example, if the server calculates that there is enough server bandwidth available for use after 3 seconds, the second delay request time is 3 seconds.

Specifically, when the server receives the change node synchronization request sent by the terminal, and when the change node synchronization request cannot be processed in time, change node information synchronization request rejection information and second delay request time are generated and sent to the terminal, and the change node information synchronization request rejection information and the second delay request time returned by the terminal receiving server are stored.

Step 804, a second current time point is acquired, and a second target time point is determined 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 synchronization request rejection information of the change node information sent by the server and the second delay request time. The second target time point refers to a time point when the change node information synchronization request is retransmitted.

Specifically, the terminal acquires a second current time point, calculates a second target time point according to the second current time point and the second delay request time, i.e. calculates the time sum of the second current time point and the second delay request time, and obtains the second target time point. And then the terminal sends a change node information 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 point in time.

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

In the above embodiment, when the terminal receives the request rejection information and delays the request time, the request is resent after the delay of the request time, so that the server load can be effectively adjusted, and the situation that the terminal cannot update the organization is avoided.

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

When the synchronization of the change node information is interrupted, the current change node information synchronization progress is obtained, and the current change node information synchronization progress is saved. And when the change node information is re-synchronized, the unsynchronized change node information is acquired from the server according to the current change node information synchronization progress.

The interruption of the synchronization of the change node information means that the server fails to synchronize the change node information due to network connection failure or that the server actively stops the synchronization of the change node information due to load pressure. The current synchronization progress of the changed node information refers to the node which has completed the synchronization of the changed node information. For example, the node 1,2 and 3 are required to be synchronized with corresponding changed node information, when the synchronization of the node 1 and the node 2 is completed, the synchronization of the changed node information is interrupted, and at this time, the information of the synchronized completed node 1 and node 2 is obtained, so as to obtain the synchronization progress of the previous changed node information. The change node information resynchronization means that the server continues to send the change node information to the terminal. The unsynchronized change node information refers to change node information that is not acquired from the server.

Specifically, when the terminal detects that the synchronization of the information of the change node is interrupted in the synchronization process, the current synchronization progress of the information of the change node is obtained, and the current synchronization progress of the information of the change node is saved. And when the change node information is re-synchronized, the unsynchronized change node information is acquired from the server according to the current change node information synchronization progress.

In the above embodiment, the unsynchronized change node information is obtained from the server according to the current change node information synchronization progress, so that the synchronized data do 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 organization architecture synchronization method further includes:

Step 1002, receiving a session request with a target user, and searching target user node information 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 target user node information returned by the server, and displaying a session page according to the target user node information.

The target user refers to a user who is about to perform a session in the instant messaging application. For example, user a sends a session request to user B through a computing instant messaging application. The target user node information refers to node information corresponding to the target user. Only when the enterprise organization architecture stored in the terminal stores the target user node information, the session with the target user can be normally performed.

Specifically, the terminal receives a session request with a target user through the computing communication application, searches the target user node information according to the session request, and when the target user node information is not searched, the terminal indicates that the target user node information is not synchronized yet, and at the moment, immediately sends a target user node information synchronization request to the server. When the server receives 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 performs session communication with the target user through the session page. The session can be realized without waiting for synchronous completion of all organization structures, so that the waiting time of the user is reduced, and the user can use the session conveniently.

In one embodiment, as shown in fig. 11, an organization architecture synchronization method is provided, and the method is applied to the server in fig. 1 for illustration, and includes the following steps:

In step 1102, a query request sent by a terminal is received, where the query request carries a local architecture state identifier.

Specifically, the server receives a query request sent by the terminal, wherein the query request carries a local organization architecture state identifier, and the server can receive the query request sent by different terminals, and the query request carries the local organization architecture state identifier corresponding to the terminal.

Step 1102, obtaining a server side organization structure state identifier, matching the server side organization structure state identifier with a local organization structure state identifier, and obtaining organization structure change information when a matching result accords with preset matching property; the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identification.

The preset matching performance refers to a matching result that the preset server side organization structure state identifier is inconsistent with the local organization structure state identifier.

Specifically, the server acquires 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 reminding message of 'the latest organization structure' 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. 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. The server searches the node change record between the organization structure states corresponding to the server side organization structure state identification and the local organization structure state identification, and obtains 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, e.g., the server side organizational structure state identifier is a second version and the local organizational structure state identifier is a first version.

In one embodiment, the server-side architecture state identifier and the local architecture state identifier may also be non-adjacent architecture state identifiers, for example, the server-side architecture state identifier is a third version, and the local architecture state identifier is a first version. 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 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 the 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 the records deleted and added with the node a are merged, so that the final node change record is the change record without the node a, which is equivalent to that without the change to the node a.

And step 1102, when the organization structure changing node state information accords with the preset increment synchronization condition, the organization structure changing information is sent to the terminal.

The preset incremental synchronization condition refers to a preset condition for sending the organization architecture change information, and may be that the number of change nodes corresponding to the organization architecture change node state information 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 organization architecture change node state information. For example, an identity in the organization architecture that indicates whether a user is online needs to be updated.

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

Step 1102, receiving a request for synchronizing change node information sent by the terminal according to the organization architecture change node state information and the organization architecture change node operation type, and obtaining corresponding change node information according to the organization architecture change node state information and the organization architecture change node operation type.

Step 1102, the node information is changed to the transmitting terminal.

Specifically, when receiving a request for synchronizing change node information sent by a terminal according to organization architecture change node state information and organization architecture change node operation type, the server searches corresponding change node information from a server side organization architecture according to the organization architecture change node state information and the organization architecture change node operation type. And then the searched changed node information is sent to the terminal. For example, the state of the newly added department a is version 3, and at this time, department a information corresponding to the department a of version 3 is found in the server side organization structure. And transmitting the department A information to the terminal.

In the above embodiment, the server side organization structure state identifier is matched with the local organization structure state identifier, when the matching result accords with the preset matching property, organization structure change information is obtained, when the organization structure change node state information accords with the preset increment synchronization condition, the organization structure change information sending terminal receives a change node information synchronization request, and corresponding change node information is obtained according to the organization structure change node state information and the organization structure change node operation type. The node information change sending terminal can enable the server to update the node information in an increment mode, so that the information of all nodes is prevented from being updated in a full amount, 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 organization architecture synchronization method further includes:

And 1202, when the organization architecture change node state information does not accord with the preset increment synchronization condition, sending the organization architecture full-quantity node state information to a terminal, so that the terminal compares the organization architecture full-quantity node state information with the local organization architecture full-quantity node state information according to the organization architecture full-quantity node state information to obtain target organization architecture change node state information and target organization architecture change node operation type.

The organization architecture full-quantity node state information refers to state information corresponding to all nodes in an organization architecture stored by a server, and the local organization architecture full-quantity node state information refers to state information corresponding to all nodes in the organization architecture stored by a terminal. The target organization architecture change node state information refers to state information of a changed node obtained by comparing organization architecture full-quantity node state information with local organization architecture full-quantity node state information in a terminal. The target organization architecture change node operation type refers to an operation type of a changed node obtained by comparing organization architecture full-quantity node state information with local organization architecture full-quantity node state information in a terminal, and the operation type includes, but is not limited to, a deleted node operation, a newly added node operation and an updated node operation. Each node sending a change has a corresponding operation type.

Specifically, when the organization architecture change node state information does not meet a preset increment synchronization condition, the organization architecture full-quantity node state information sending terminal compares the received organization architecture full-quantity node state information with the stored local organization architecture full-quantity node state information to obtain target organization architecture change node state information and target organization architecture change node operation type, and sends a target change node information synchronization request to the server according to the target organization architecture change node state information and the target organization architecture change node operation type.

In 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 architecture change node state information and the target organization architecture change node operation type.

And 1206, transmitting the target 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 changes after the organization architecture total node state information is compared with the local organization architecture total node state information in the terminal.

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

In the above embodiment, when the organization architecture change node status information does not meet the preset incremental synchronization condition, the organization architecture full-quantity node status information is sent to the terminal, so that the terminal compares the organization architecture full-quantity node status information with the local organization architecture full-quantity node status information to obtain the target organization architecture change node status information and the target organization architecture change node operation type, and then uses the target organization architecture change node status information and the target organization architecture change node operation type to perform organization architecture synchronization, thereby saving server resources and improving organization architecture synchronization efficiency.

In one embodiment, as shown in fig. 13, after step 1102, after receiving a query request sent by a terminal, the query request carries a local 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, query request reject information and a first delay request time are returned to the terminal.

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

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

Specifically, the server obtains the current CPU utilization rate, the memory utilization rate, the input/output consumption rate and other data, calculates a current load value according to the current CPU utilization rate, the memory utilization rate and the input/output consumption rate, judges whether the current load value exceeds a preset pressure bottleneck value, and when the current load value exceeds the preset pressure bottleneck value, cannot normally process a query request, and at this time, generates query request rejection information and a first delay request time. The server returns the inquiry request rejection information and the first delay request time to the terminal. Then the server receives the inquiry request sent by the terminal after the first delay request time, and performs subsequent processing.

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

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

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

in step 1406, a request for synchronizing the change node information is received, the request being sent by the terminal after the second delay request time.

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 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, cannot normally process a change node information synchronization request, and generates change node information synchronization request rejection information and a second delay request time. 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 information synchronization request of the change node sent by the terminal after the second delay request time, and performs subsequent processing.

In a specific embodiment, the server receives requests sent by 5 terminals simultaneously, and the maximum number of requests that the server can load is 4. At this time, the server will generate request rejection information and delay request time corresponding to one of the terminal requests, return to the corresponding terminal, and process the requests sent by the other 4 terminals.

In the above embodiment, when the request is received, the server detects whether the preset pressure bottleneck value is reached, and when the preset pressure bottleneck value is reached, generates the request rejection information and the delay request time, and returns the request rejection information and the delay request time to the terminal, so that the terminal resends the request after the delay request time, and the load can be effectively regulated, thereby avoiding the incapability of synchronization by the organization architecture.

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

Detecting the current network state, stopping sending the change node information to the terminal when the current network state accords with the preset network interruption condition, and storing the change node information synchronization progress. And when the current network state accords with the preset network recovery condition, sending unsynchronized change node information to the terminal according to the change node information synchronization progress.

The current network state refers to the current network state of the server, including but not limited to a network connection state and a network traffic usage state. The preset network interruption condition refers to a condition that the preset terminal sends the change node information to the terminal, and includes that the network connection state is in an unstable state, for example, the network is continuously disconnected and reconnected, or the network traffic usage suddenly increases, for example, the current network traffic usage suddenly increases to a preset threshold value. The preset network recovery condition refers to a preset condition for sending changed node 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 the current network state is detected to meet the preset network interruption condition, and stores the corresponding change node information synchronization progress of the terminal, so that the problem of the change node information sending is avoided, and the inaccuracy of the change node information received by the terminal is avoided. When the network state of the server is recovered to be normal, namely when the current network state is detected to be in accordance with the preset network recovery condition, the unsynchronized change node information is sent to the terminal according to the change node information synchronization progress, so that the terminal is ensured to acquire the accurate change node information.

In a specific embodiment, as shown in fig. 15, an organization architecture synchronization method is provided, which specifically includes the following steps:

in step 1502, the terminal sends a query request to the server, where the query request carries a local architecture state identifier.

Step 1504, the server receives a query request sent by the terminal, acquires a server side organization structure state identifier, matches the server side organization structure state identifier with a local organization structure state identifier, and acquires organization structure change information when a matching result accords with preset matching property; the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identification.

In step 1506, when the organization architecture change node status information meets the preset incremental synchronization condition, the server sends the organization architecture change information to the terminal.

In step 1508, the terminal receives the architecture change information returned by the server, obtains the local architecture node status information, and detects the architecture change node status information and the architecture change node operation type according to the local architecture node status information.

In step 1510, when detecting that the organization architecture change node status information and the organization architecture change node operation type pass, the terminal obtains the organization architecture change node status information corresponding to the newly added node operation and the updated node operation.

In step 1512, the terminal generates each parallel change node information synchronization request according to the organization architecture change node state information corresponding to the newly added node operation and the updated node operation, and sends each parallel change node information synchronization request to the server in parallel.

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

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

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

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

The application also provides an application scene, which applies the organization architecture synchronization method. Specifically, the application of the organization architecture synchronization method in the application scene is as follows:

Fig. 16 is a timing chart of the method for synchronizing the organization structure in the application scenario. Specifically:

when the user A logs in the enterprise instant messaging application, the enterprise organization architecture is synchronized, and at the moment, the user A terminal sends a query request to the server, wherein the query request carries a state identifier of 1.1.3. When the server receives the query request, the state identifier 1.2.1 stored by the server is obtained, the state identifier 1.1.3 and the state identifier 1.2.1 are compared and detected to obtain inconsistent detection results, and at the moment, the server obtains a state update record, for example, the state identifier 1.2.1 is compared with the state identifier 1.1.3, the department A is newly added, the user M of the department C is deleted, and the user H of the department F is updated. At this time, the server acquires the organization architecture change information, including the new 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 changing information returned by the server, acquires the local organization structure node state information, and detects the organization structure changing node state information and the organization structure changing node operation type in the organization structure changing information according to the local organization structure node state information. When detecting that the organization architecture change node state information and the organization architecture change node operation type pass, the terminal acquires the organization architecture change node state information corresponding to the newly added node operation and the updated node operation, namely, acquires the newly added department A and the corresponding department state identifier 1.2.1.A and the updated user H and the corresponding user state identifier 1.2.1.F.h. The terminal generates 2 change node information synchronous requests, namely a synchronous request for a change department A and a synchronous request for an update user H, and sends the synchronous 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 status identifier 1.2.1.A and the synchronization request of the updated user H and the corresponding user status identifier 1.2.1.F.h, searches the detailed information of the department A according to the newly added department A and the corresponding department status identifier 1.2.1.A, including the name of the department, the number of people in the department, the position of the department, the name of the user of the department and the like, and returns the detailed information of the department A to the user terminal. Meanwhile, the server searches the detailed information of the user A according to the synchronous request for updating the user H and the corresponding user state identifier 1.2.1.F.h, wherein the detailed information comprises a user name, a user contact method, including but not limited to a telephone and a mailbox, a user company position, department information to which the user belongs and the like, and sends the detailed information of the user A to the user terminal.

After receiving the detailed information of the department a and the detailed information of the user a, the user terminal uses the detailed information of the department a and the detailed information of the user a to update the component architecture stored in the terminal, i.e. to add the detailed information of the department a and replace the detailed information of the user a. And simultaneously, deleting the detailed information of the user M of the department C. When synchronization is completed, the organization architecture identification in the terminal is replaced by 1.2.1.

It should be understood that, although the steps in the flowcharts of fig. 2-4, 6, 8, and 10-15 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps of FIGS. 2-4, 6, 8, and 10-15 may include multiple steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the steps or stages are performed necessarily occur sequentially, but may be performed alternately or alternately with other steps or at least a portion of the steps or stages in other steps.

In one embodiment, as shown in fig. 17, an architecture synchronization apparatus 1700 is provided, which may employ software modules or hardware modules, or a combination of both, as part of a computer device, the apparatus specifically comprising: a query request sending module 1702, an information receiving module 1704, a synchronization request sending module 1706, a node information acquiring module 1708, and an updating module 1710, wherein:

the query request sending module 1702 is configured to send a query request to a server, where the query request carries a local organization architecture state identifier;

The information receiving module 1704 is configured to receive the organization architecture modification information returned by the server, where the organization architecture modification information includes organization architecture modification node state information, an organization architecture modification node operation type, and a server side organization architecture state identifier, and the organization architecture modification information is acquired by the server according to the matching between the local organization architecture state identifier and the server side organization architecture state identifier;

the synchronization request sending module 1706 is configured to send a synchronization request for changing node information to the server according to the organization architecture changing node state information and the organization architecture changing node operation type;

The node information obtaining module 1708 is configured to obtain changed node information sent by the server according to the changed node information synchronization request;

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

In one embodiment, 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 node data corresponding to the organization architecture change node type and the organization architecture change node.

In one embodiment, the organization architecture synchronization apparatus 1700 further comprises:

the local detection module is used for acquiring local organization architecture node state information, detecting organization architecture change node state information and organization architecture change node operation types according to the local organization architecture node state information;

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

In one embodiment, the synchronization request sending module 1706 is further configured to, when detecting that the organization architecture change node state information and the organization architecture change node operation type fail, obtain detection fail node state information, and send a fail node state information reacquiring request to the server according to the detection fail node state information; and receiving 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 organization architecture change node corresponding to the newly added node operation and/or the updated node operation when the organization architecture change node operation type comprises the newly added node operation and/or the updated node operation;

the request generation unit is used for 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 update node operation;

And the parallel sending unit is used for sending each parallel change node information synchronization request 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 a 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 changed 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 a second delay request time; and sending a change node information synchronization request to the server at a second target time point.

In one embodiment, the node information obtaining module 1708 is further configured to obtain a current synchronization progress of changing node information when the synchronization of the changing node information is interrupted, and save the current synchronization progress of changing node information; and when the change node information is re-synchronized, the unsynchronized change node information is acquired from the server according to the current change node information synchronization progress.

In one embodiment, the organization architecture synchronization apparatus 1700 is further configured to receive a session request with a target user, and search for target user node information 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, an architecture synchronization apparatus 1800 is provided, which may employ software modules or hardware modules, or a combination of both, as part of a computer device, the apparatus specifically comprising: a request receiving module 1802, an information obtaining module 1804, an information transmitting module 1806, a synchronization request receiving module 1808, and a node information transmitting module 1810, wherein:

the request receiving module 1802 is configured to receive a query request sent by a terminal, where the query request carries a local architecture state identifier;

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

An information sending module 1806, configured to send the organization architecture change information to the terminal when the organization architecture change node status information meets a preset incremental synchronization condition;

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

the node information sending module 1810 is 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 organization architecture full-scale node status information to the terminal when the organization architecture change node status information does not meet the preset incremental synchronization condition, so that the terminal compares the organization architecture full-scale node status information with the local organization architecture full-scale node status information according to the organization architecture full-scale node status information to obtain the target organization architecture change node status information and the target organization architecture change node operation type; receiving a target change node information synchronization request sent by the terminal according to the target organization architecture change node state information and the target organization architecture change node operation type, 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.

In one embodiment, the organizational structure 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 inquiry request refusal information and first delay request time to the terminal; the inquiry request sent by the terminal after the first delay request time is received.

In one embodiment, the organization architecture synchronization apparatus 1800 is further configured to detect whether a preset pressure bottleneck value is reached, and when the preset pressure bottleneck value is reached, generate change node information synchronization request rejection information and a second delay request time; returning the change node information synchronous request refusal 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 sending module 1810 is further configured to detect a current network state, stop sending the changed node information to the terminal when the current network state meets a preset network interruption condition, and save a synchronization progress of the changed node information; when the current network state accords with the preset network recovery condition, sending unsynchronized change node information to the terminal according to the change node information synchronization progress

For specific limitations of the organizational structure synchronization apparatus, reference may be made to the above limitation of the organizational structure synchronization method, and no further description is given here. The above-described individual modules in the organizational structure synchronization device may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which 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 includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing organization architecture data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements an organizational structure synchronization method.

In one embodiment, a computer device is provided, which may be a terminal, and an internal structure diagram thereof 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 includes a non-volatile 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 the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements an organizational structure synchronization method. 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, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structures shown in fig. 18 or 19 are merely block diagrams of portions of structures associated with the present inventive arrangements and are not limiting of the computer device to which the present inventive arrangements may be implemented, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In an embodiment, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, storing a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in the above-described method embodiments.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.

Claims

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

The method comprises the steps of receiving organization architecture change information returned by a server, wherein the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identifiers, and the organization architecture change information is acquired by the server according to the matching property of the local organization architecture state identifiers and the server side organization architecture state identifiers;

acquiring local organization architecture node state information, and detecting whether the organization architecture change node state information and the organization architecture change node operation type are correct or not according to the local organization architecture node state information;

when detecting that the organization architecture change node state information and the organization architecture change node operation type are correct, sending a change node information synchronization request to the server according to the organization architecture change node state information and the organization architecture change node operation type;

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

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

3. The method of claim 1, wherein sending a change node information synchronization request to the server according to the organization architecture change node state information and the organization architecture change node operation type comprises:

When detecting that the organization architecture change node state information and the organization architecture change node operation type are not passed, obtaining detection non-passing node state information, and sending a non-passing node state information re-obtaining request to the server according to the detection non-passing node state information;

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

4. The method of claim 1, wherein the organization architecture change node operation type includes at least one of a delete node operation, a add node operation, and an update node operation, wherein the sending a change node information synchronization request to the server according to the organization architecture change node state information and the organization architecture change node operation type includes:

When the organization architecture change node operation type comprises a newly added node operation and/or an updated node operation, obtaining organization architecture change node state information 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 update node operation;

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

5. The method of claim 1, further comprising, after said sending a query request to a server, said query request carrying a local organizational structure status identifier:

receiving inquiry request refusal 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.

6. The method of claim 1, further comprising, after said sending a change node information synchronization request to said server according to said organization architecture change node state information and said organization architecture change node operation type:

receiving change node information synchronous request refusal information and 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.

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

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

And when the change node information is re-synchronized, acquiring unsynchronized change node information from the server according to the current change node information synchronization progress.

8. The method according to claim 1, wherein the method further comprises:

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

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

9. A method of organizing 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 accords with preset matching property; the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identification;

When the organization architecture change node state information accords with a preset increment synchronization condition, sending the organization architecture change information to the terminal so that the terminal obtains local organization architecture node state information, and detecting whether the organization architecture change node state information and the organization architecture change node operation type are correct or not according to the local organization architecture node state information;

receiving a request for synchronizing the change node information sent by the terminal according to the organization architecture change node state information and the organization architecture change node operation type when the terminal detects that the organization architecture change node state information and the organization architecture change node operation type are correct or not, and acquiring corresponding change node information according to the organization architecture change node state information and the organization architecture change node operation type;

and sending the change node information to the terminal.

10. The method according to claim 9, wherein the method further comprises:

When the organization architecture change node state information does not accord with a preset increment synchronization condition, transmitting the organization architecture full-quantity node state information to the terminal, so that the terminal compares the organization architecture full-quantity node state information with local organization architecture full-quantity node state information according to the organization architecture full-quantity node state information to obtain target organization architecture change node state information and target organization architecture change node operation type;

Receiving a target change node information synchronization request sent by the terminal according to the target organization architecture change node state information and the target organization architecture change node operation type, 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.

11. The method according to claim 9, wherein after the query request sent by the receiving terminal, the query request carries a local organization architecture version identifier, the method further comprises:

Returning the inquiry request refusal 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.

12. The method according to claim 9, further comprising, after said receiving a change node information synchronization request sent by said terminal according to said organization architecture change node version information and said organization architecture change node operation type:

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

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

13. The method of claim 9, wherein the sending the change node information to the terminal comprises:

And when the current network state accords with a preset network recovery condition, sending unsynchronized change node information to the terminal according to the change node information synchronization progress.

14. An organizational structure synchronization apparatus, the apparatus comprising:

The local detection module is used for acquiring local organization architecture node state information, and detecting whether the organization architecture change node state information and the organization architecture change node operation type are correct or not according to the local organization architecture node state information;

The synchronous request sending module is used for sending a synchronous request for changing node information to the server according to the organization architecture changing node state information and the organization architecture changing node operation type when detecting that the organization architecture changing node state information and the organization architecture changing node operation type are correct and correct;

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

and the updating module is used for updating the local organization architecture corresponding to the local organization architecture state identifier according to the changed node information and replacing the local organization architecture state identifier with the server organization architecture state identifier.

15. The apparatus of claim 14, wherein the fabric change node state information comprises a fabric change node type and a fabric change node state identification, and wherein the change node information comprises node data corresponding to the fabric change node type and the fabric change node.

16. The apparatus of claim 14, wherein the synchronization request sending module is further configured to obtain failed node status information when the organization architecture change node status information and the organization architecture change node operation type are detected to be failed, and send a failed node status information reacquiring request to the server according to the failed node status information; and receiving the target node state information corresponding to the failed node state information returned by the server.

17. The apparatus of claim 14, wherein the organization architecture changes node operation types including at least one of a delete node operation, an add node operation, and an update node operation, the synchronization request sending module 1706 comprising:

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

18. The apparatus of claim 14, wherein the apparatus 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; and sending the query request to the server at the first target time point.

19. The apparatus of claim 14, wherein the apparatus is further configured to receive change node information synchronization request rejection information and a 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.

20. The apparatus of claim 14, wherein the node information acquisition module is further configured to acquire a current change node information synchronization progress and save the current change node information synchronization progress when the change node information synchronization is interrupted; and when the change node information is re-synchronized, acquiring unsynchronized change node information from the server according to the current change node information synchronization progress.

21. The apparatus of claim 14, wherein the apparatus is further configured to receive a session request with a target user, and to find target user node information based on the session request; when the target user node information is not found, sending a target user node information synchronization request to the server; and receiving the target user node information returned by the server, and displaying a session page according to the target user node information.

22. An organizational structure synchronization apparatus, the apparatus comprising:

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 accords with preset matching property; the organization architecture change information comprises organization architecture change node state information, organization architecture change node operation types and server side organization architecture state identification;

The information sending module is used for sending the organization architecture change information to the terminal when the organization architecture change node state information accords with a preset increment synchronization condition so as to enable the terminal to acquire local organization architecture node state information, and detecting whether the organization architecture change node state information and the organization architecture change node operation type are correct or not according to the local organization architecture node state information;

the synchronous request receiving module is used for receiving a change node information synchronous request sent by the terminal according to the organization architecture change node state information and the organization architecture change node operation type when detecting that the organization architecture change node state information and the organization architecture change node operation type are correct and correct, and obtaining corresponding change node information according to the organization architecture change node state information and the organization architecture change node operation type;

23. The apparatus of claim 22, wherein the apparatus is further configured to send the fabric total node state information to the terminal when the fabric change node state information does not meet a preset incremental synchronization condition, so that the terminal compares the fabric total node state information with local fabric total node state information to obtain target fabric change node state information and a target fabric change node operation type; receiving a target change node information synchronization request sent by the terminal according to the target organization architecture change node state information and the target organization architecture change node operation type, 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.

24. The apparatus of claim 22, wherein the apparatus is further configured to

25. The apparatus of claim 22, further comprising, after said receiving a change node information synchronization request sent by said terminal according to said organization architecture change node version information and said organization architecture change node operation type:

26. The apparatus of claim 22, wherein the sending the change node information to the terminal comprises:

27. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 13 when the computer program is executed.

28. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method of any one of claims 1 to 13.