Organizational structure updating method and device, computer readable medium and electronic device

Abstract

The application belongs to the technical field of computers, and particularly relates to an organization architecture updating method and device, a computer readable medium and an electronic device. The organization architecture updating method comprises the following steps: acquiring an update flow table of a remote organization architecture; taking a first preset number as a maximum value of a node number of each batch, and pulling nodes corresponding to preset update records on the update flow table in batches until all nodes corresponding to the preset update records are pulled; and updating the nodes pulled in each batch to a local organization architecture. Based on the method, the response speed of node pulling can be improved through incremental pulling in batches, the local organization architecture can be prevented from being unresponsive for a long time, and the message acquisition speed can be improved, so that the organization architecture can be updated with high efficiency and responsiveness.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of computer, and particularly relates to an organization architecture updating method and device, a computer readable medium and an electronic device. BACKGROUND

[0002] Organization architecture is the basis for administrative and personnel management of various types of social organizations, such as governments, non-governmental organizations, enterprises and institutions, schools, hospitals, and the like. Various organizations describe the attributes of internal departments and members, the ordering relationship between them, and the relationship with the outside world through organization architecture, and determine the post responsibilities, rights and obligations between them on this basis. Therefore, organization architecture is the basis for management of various organizations.

[0003] A problem is that a large organization architecture file generally has a large capacity, and it takes more time to download to the local in a network environment congestion. During the downloading process, if the client views the organization architecture, a blank interface is displayed. In some application scenarios, for example, during the organization architecture downloading process, the user application program is switched to the background, and the mobile operating system kills the application program process, and then the next application program needs to be downloaded again, and the process may be killed again, and so on. Therefore, the large organization architecture file downloaded to the local has the problems of long time consumption and slow response.

[0004] It should be noted that the information disclosed in the above background section is only used to strengthen the understanding of the background of the present application, and therefore can include information that does not constitute prior art known to those of ordinary skill in the art. SUMMARY

[0005] The purpose of the present application is to provide an organization architecture updating method and device, a computer readable medium and an electronic device. At least to some extent, the technical problem of long time consumption and slow response of a large organization architecture file downloaded to the local in the related art is overcome.

[0006] Other characteristics and advantages of the present application will become apparent from the following detailed description, or will be learned by practice of the present application.

[0007] According to an aspect of an embodiment of the present application, an organization architecture updating method is provided. The organization architecture updating method comprises:

[0008] Obtaining an update flow table of a remote organization architecture, the update flow table being used to store a node corresponding to each update record of the remote organization architecture and an update timestamp;

[0009] The first preset number is a maximum value of a number of nodes pulled in each batch, and the preset update records on the update log are pulled in batches until all nodes corresponding to the preset update records are pulled, wherein the preset update records include update records on the update log with update timestamps after a preset timestamp;

[0010] The nodes pulled in each batch are updated into the local organization architecture.

[0011] According to an aspect of an embodiment of the present application, an organization architecture updating device is provided. The organization architecture updating device comprises:

[0012] An update log obtaining module is configured to obtain an update log of a remote organization architecture, wherein the update log is used to store nodes and update timestamps corresponding to each update record of the remote organization architecture;

[0013] A node batch pulling module is configured to take a first preset number as a maximum value of a number of nodes pulled in each batch, and pull nodes corresponding to preset update records on the update log in batches until all nodes corresponding to the preset update records are pulled, wherein the preset update records include update records on the update log with update timestamps after a preset timestamp;

[0014] A node updating module is configured to update the nodes pulled in each batch into a local organization architecture.

[0015] In some embodiments of the present application, based on the above technical solutions, the node batch pulling module comprises:

[0016] A preset timestamp determining unit is configured to take a timestamp of the last time when the local organization architecture is pulled as the preset timestamp;

[0017] A node to be pulled determining unit is configured to take update records with update timestamps after the preset timestamp as preset update records, and take nodes corresponding to each update record in the preset update records as nodes to be pulled;

[0018] A node pulling unit is configured to take the first preset number as a maximum value of a number of nodes pulled in each batch, and pull the nodes to be pulled in batches until all the nodes to be pulled are pulled.

[0019] In some embodiments of the present application, based on the above technical solutions, the node pulling unit comprises:

[0020] The to-be-pulled node acquisition subunit is configured to acquire the to-be-pulled nodes corresponding to the update records in sequence from old to new according to the update timestamps of the update records in the preset update records.

[0021] The quasi-pulled node determination subunit is configured to detect whether the to-be-pulled nodes meet the filtering rules one by one, and take the to-be-pulled nodes meeting the filtering rules as quasi-pulled nodes.

[0022] The first quasi-pulled node pulling unit is configured to calculate the total number of the quasi-pulled nodes, and pull the first preset number of quasi-pulled nodes when the total number of the quasi-pulled nodes reaches the first preset number.

[0023] In some embodiments of the present application, based on the above technical solutions, the node pulling unit further includes:

[0024] The to-be-pulled node calculation subunit is configured to calculate the number of the detected to-be-pulled nodes.

[0025] The second quasi-pulled node pulling unit is configured to pull the second preset number of quasi-pulled nodes meeting the filtering rules from the second preset number of to-be-pulled nodes when the number of the detected to-be-pulled nodes reaches the second preset number.

[0026] In some embodiments of the present application, based on the above technical solutions, the node pulling unit further includes:

[0027] The third quasi-pulled node pulling unit is configured to pull all the quasi-pulled nodes meeting the filtering rules from all the to-be-pulled nodes when all the to-be-pulled nodes are detected.

[0028] In some embodiments of the present application, based on the above technical solutions, the organizational structure updating apparatus further includes:

[0029] The preset timestamp acquisition subunit is configured to take the update timestamp of the to-be-pulled node detected last as the preset timestamp.

[0030] In some embodiments of the present application, based on the above technical solutions, the node updating module includes:

[0031] The first node updating unit is configured to cover the original node with the pulled node when the pulled node has a corresponding original node in the local organizational structure.

[0032] The second node updating unit is configured to newly build a corresponding node at a corresponding position in the local organizational structure according to the parent node information and the child node information associated with the pulled node when the pulled node does not have a corresponding original node in the local organizational structure.

[0033] In some embodiments of the present application, based on the above technical solution, the organization architecture updating apparatus further comprises:

[0034] a node data pulling unit configured to pull node data corresponding to the pulled node from the remote organization architecture according to the pulled node;

[0035] a node data updating unit configured to update the node data into the local organization architecture.

[0036] In some embodiments of the present application, based on the above technical solution, the node data comprises summary data and detailed data, and the node data updating unit comprises:

[0037] a summary data updating unit configured to update the summary data of the node data into the corresponding node of the local organization architecture;

[0038] a detailed data updating unit configured to read detailed data corresponding to each summary data in the remote organization architecture in batches, and update the detailed data into the corresponding node of the local organization architecture.

[0039] According to an aspect of an embodiment of the present application, there is provided a computer readable medium having stored thereon a computer program, which, when executed by a processor, implements the organization architecture updating method in the above technical solution.

[0040] According to an aspect of an embodiment of the present application, there is provided an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the organization architecture updating method in the above technical solution via execution of the executable instructions.

[0041] According to an aspect of an embodiment of the present application, there is provided a computer program product or computer program, comprising computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the organization architecture updating method in the above technical solution.

[0042] In the technical solution provided in the embodiments of the present application, the update flow table of the remote organization architecture is acquired, the first preset number is taken as the maximum of the node number of each batch, the nodes corresponding to the preset update records on the update flow table are pulled in batches until all the nodes corresponding to the preset update records are pulled, and then the nodes pulled in each batch are updated into the local organization architecture. In this way, the nodes corresponding to the preset update records on the update flow table are pulled in batches until all the nodes corresponding to the preset update records are pulled, so that the response speed of node pulling is improved through incremental pulling in batches, and the local organization architecture is updated with high efficiency and responsiveness.

[0043] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0044] The drawings incorporated into the specification and forming part of the specification, show embodiments consistent with the present application, and together with the specification, serve to explain the principles of the present application. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0045] Figure 1 An exemplary device architecture block diagram to which the technical solution of the present application is applied is schematically shown.

[0046] Figure 2 The step flow of the organization architecture updating method provided in the embodiments of the present application is schematically shown.

[0047] Figure 3 The step flow of the organization architecture updating method provided in the embodiments of the present application is schematically shown.

[0048] Figure 4 The step flow of the organization architecture updating method provided in the embodiments of the present application is schematically shown.

[0049] Figure 5 The step flow of the organization architecture updating method provided in the embodiments of the present application is schematically shown.

[0050] Figure 6 The step flow of the organization architecture updating method provided in the embodiments of the present application is schematically shown.

[0051] Figure 7 The step flow of updating the nodes pulled from each batch to the local organization architecture in the embodiments of the present application is schematically shown.

[0052] Figure 8 The step flow of updating the node data to the local organization architecture in the embodiments of the present application is schematically shown.

[0053] Figure 9 The structural block diagram of the organization architecture updating apparatus provided by the embodiments of the present application is schematically shown.

[0054] Figure 10 The structural block diagram of the electronic device for implementing the embodiments of the present application is schematically shown. DETAILED DESCRIPTION

[0055] Example implementations will now be described more fully with reference to the accompanying drawings. Example implementations may, however, be implemented in many different forms and should not be construed as limited to the examples set forth herein; rather, these implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of example implementations to those skilled in the art.

[0056] Moreover, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the

[0057] The block diagrams shown in the accompanying drawings are merely functional entities, and do not necessarily have to correspond to physically independent entities. That is, these functional entities can be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0058] The flowcharts shown in the accompanying drawings are merely exemplary illustrations, and do not necessarily include all contents and operations / steps, nor do they have to be executed in the order described. For example, some operations / steps can be further decomposed, and some operations / steps can be combined or partially combined, so the actual execution order can be changed according to actual conditions.

[0059] Before the technical solutions of the organization architecture updating method, organization architecture updating apparatus, etc. provided by the embodiments of the present application are described in detail, the blockchain technology involved in some embodiments of the present application is briefly introduced.

[0060] Blockchain is a new application mode of distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm and other computer technologies. Blockchain, in essence, is a decentralized database, which is a chain of data blocks associated using cryptographic methods, each data block containing information of a batch of network transactions, used to verify the validity of the information (anti-fake) and generate the next block. The blockchain can include a blockchain underlying platform, a platform product service layer, and an application service layer.

[0061] The blockchain underlying platform can include user management, basic services, smart contracts, and operation monitoring processing modules. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining the generation of public and private keys (account management), key management, and the maintenance of the correspondence between the real identity and the blockchain address (permission management), etc., and in the case of authorization, auditing the transaction of certain real identities, providing risk control rule configuration (risk audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests, and after consensus, the valid requests are recorded on the storage. For a new business request, the basic service first performs interface adaptation analysis and authentication processing (interface adaptation), then encrypts the business information through a consensus algorithm (consensus management), and after encryption, the complete and consistent transmission is transmitted to the shared ledger (network communication) and recorded and stored; the smart contract module is responsible for the registration and issuance of contracts, the triggering and execution of contracts, and developers can define contract logic through a certain programming language, publish it to the blockchain (contract registration), call keys or other events to trigger execution according to the logic of the contract terms, complete the contract logic, and also provide contract upgrade and cancellation functions; the operation monitoring module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation during product release, and real-time state visualization output during product operation, such as alarm, monitoring network conditions, monitoring node device health status, etc.

[0062] The platform product service layer provides basic capabilities and implementation frameworks for typical applications, and developers can stack business characteristics based on these basic capabilities to complete the blockchain implementation of business logic. The application service layer provides application services based on the blockchain scheme for business participants to use.

[0063] The organization architecture updating method and device provided by the present application will be described in detail below in conjunction with specific embodiments.

[0064] Figure 1 An exemplary device architecture block diagram to which the technical solutions of the present application are applied is schematically shown.

[0065] As Figure 1As shown, the device architecture 100 can include a terminal device 110, a network 120 and a server 130. The terminal device 110 can include various electronic devices such as a smartphone, a tablet computer, a notebook computer, a desktop computer, etc. The server 130 can be a standalone physical server, or a server cluster composed of multiple physical servers or a distributed device, or a cloud server providing cloud computing services. The network 120 can be a communication medium of various connection types capable of providing a communication link between the terminal device 110 and the server 130, for example, a wired communication link or a wireless communication link.

[0066] According to implementation needs, the device architecture in the embodiments of the present application can have any number of terminal devices, networks and servers. For example, the server 130 can be a server group composed of multiple server devices. In addition, the technical solutions provided by the embodiments of the present application can be applied to the terminal device 110, or can be applied to the server 130, or can be jointly implemented by the terminal device 110 and the server 130, and the present application does not make special limitations on this.

[0067] For example, a remote organization architecture can be deployed on the server 130, and each node of the remote organization architecture, an update stream table and node data corresponding to each node are stored on the server 130. When the terminal device 110 needs to request the server 130 for an update organization architecture, the terminal device 110 can execute the organization architecture update method provided by the present application to obtain the update stream table of the remote organization architecture, take the first preset number as the maximum value of the number of nodes pulled in each batch, pull the nodes corresponding to the preset update records on the update stream table in batches until all the nodes corresponding to the preset update records are pulled, and then update the nodes pulled in each batch to the local organization architecture, so as to improve the response speed of node pulling, avoid that the local organization architecture cannot be responded for a long time, and thus realize the update of the organization architecture with high efficiency and responsiveness.

[0068] In the following description of the present application, the terminal device pulls the nodes stored in the remote organization architecture of the server to realize the update of the local organization architecture in the terminal device, but the present application is not limited to this implementation manner.

[0069] Figure 2 The steps of the organization architecture update method provided by the embodiments of the present application are schematically shown. The execution subject of the organization architecture update method can be a terminal device or a server. The terminal device includes but is not limited to a mobile phone, a computer, a smart voice interactive device, a smart home appliance, a vehicle-mounted terminal, etc. As shown, Figure 2 The organization architecture update method can mainly include the following steps S210-S230.

[0070] S210. Obtain an update log of the remote organization structure. The update log is used to store the nodes and update time stamps corresponding to each update record of the remote organization structure.

[0071] Specifically, the update log of the remote organization structure can be stored together with the remote organization structure on the remote server, or the update log of the remote organization structure can be stored together with the remote organization structure on the remote terminal, which is not limited in the present application. The update log includes a plurality of update records, each of which is used to record each update in the history of the remote organization structure. In each update record, the updated node in the update is recorded, and the time of the update is recorded as the corresponding update time stamp. For example, a corresponding log record of the addition, deletion or change of a node in the remote organization structure can be recorded in an update record, and the time of the update is recorded as the corresponding update time stamp.

[0072] In a specific embodiment, the remote organization structure can be an enterprise directory, which includes data recording enterprise member information and architecture relationship composed of members, departments, tags and their organization structure relationship in the enterprise. Among them, the department can contain multiple members and multiple sub-departments. The member can correspond to an employee or a service account in the enterprise. Alternatively, the enterprise directory can include tree-shaped organization structure relationship composed of departments and members in the enterprise, as well as attributes, mutual ordering relationship of departments and members, and mutual visibility rules between departments and members.

[0073] When the information of the member or the department is updated, the update log is added with an update record about the corresponding node of the information update and the corresponding update time stamp. When the member or the department moves in the organization structure, the update log is added with an update record about the moved member or the department and all nodes under it and the corresponding update time stamp. When the member or the department is deleted, the update log is added with a time stamp about the deleted member or the department and all nodes under it.

[0074] S220. Take the first preset number as the maximum value of the number of nodes pulled in each batch, and pull the nodes corresponding to the preset update records on the update log in batches until all nodes corresponding to the preset update records are pulled. Among them, the preset update records include the update records with update time stamps after the preset time stamp on the update log.

[0075] Figure 3 The step flow of taking the first preset number as the maximum value of the number of nodes pulled in each batch, and pulling the nodes corresponding to the preset update records on the update log in batches until all nodes corresponding to the preset update records are pulled in the embodiment of the present application is schematically shown. As shown in FIG. 2B, the step of pulling the nodes corresponding to the preset update records on the update log in batches until all nodes corresponding to the preset update records are pulled is performed. Figure 3As shown, on the basis of the above embodiments, in some embodiments, the step S220 of pulling the nodes corresponding to the preset update records on the update log in batches with the first preset number as the maximum number of nodes pulled in each batch until all the nodes corresponding to the preset update records are pulled can further include the following steps S310-S330:

[0076] S310. Take the timestamp of the last time the local organization architecture pulls the organization architecture as the preset timestamp.

[0077] S320. Take the update records with the update timestamps after the preset timestamp as the preset update records, and take the nodes corresponding to each update record in the preset update records as the nodes to be pulled.

[0078] S330. Pull the nodes to be pulled in batches with the first preset number as the maximum number of nodes pulled in each batch until all the nodes to be pulled are pulled.

[0079] Take the timestamp of the last time the local organization architecture pulls the organization architecture as the preset timestamp; when the local organization architecture is pulled for the first time, set the preset timestamp before the earliest update timestamp in the update log. That is, take all the update records in the update log as the preset update records.

[0080] Take the update records with the update timestamps after the preset timestamp as the preset update records, and take the nodes corresponding to each update record in the preset update records as the nodes to be pulled, which can make the update timestamps of the pulled nodes all after the timestamp of the last time the organization architecture is pulled, can realize incremental update of the local organization architecture, and can reduce the number of nodes pulled in each organization architecture update, thereby realizing efficient update of the organization architecture.

[0081] Therefore, the nodes to be pulled are pulled in batches with the first preset number as the maximum number of nodes pulled in each batch until all the nodes to be pulled are pulled. Specifically, the first preset number can be carried as a parameter limit_cnt in the organization architecture update request sent by the terminal to the server, and the batch pulling of the nodes to be pulled is realized through the cooperation of the sender and the receiver.

[0082] It can be understood that the large organization architecture file generally has a large capacity, and in the case of network congestion, it takes a long time to download to the local, thereby making the loading efficiency of the large organization architecture file loaded to the local low. Moreover, due to the large amount of data, the stability of the pulling service is poor. In the above embodiments of the present application, the update record with the update timestamp after the preset timestamp is taken as the preset update record, and the node corresponding to each update record in the preset update record is taken as the to-be-pulled node. The to-be-pulled nodes are pulled in batches until all the to-be-pulled nodes are pulled, with the first preset number as the maximum value of the number of nodes pulled in each batch, thereby making the local, when pulling the organization architecture for the first time, can improve the response speed of node pulling in a batch-incremental pulling manner, avoid the local being unresponsive for a long time, and realize the update of the organization architecture with high efficiency and responsiveness. Thus, the transmission stability of the data transmission process can be improved, the stability of the pulling mechanism and the organization architecture update service can be ensured, and the user experience can be improved.

[0083] Moreover, when the local pulls the organization architecture for the first time, the nodes with the update timestamp after the preset timestamp can be pulled in batches, that is, only the nodes in the organization architecture that have been updated need to be pulled, thereby reducing the amount of data to be pulled and improving the response speed of node pulling. Thus, the transmission stability of the data transmission process can be improved, the stability of the pulling mechanism and the organization architecture update service can be ensured, and the user experience can be improved.

[0084] In some embodiments, the terminal can compare the number of nodes pulled in each batch node_cnt with the first preset number limit_cnt, and when the number of nodes pulled in each batch node_cnt is greater than or equal to the first preset number limit_cnt, it is determined that the terminal has not pulled all the nodes to be pulled, and the pulling request is continued; when the number of nodes pulled in each batch node_cnt is less than the first preset number limit_cnt, it is determined that the terminal has pulled all the nodes to be pulled, and the pulling request does not need to be continued. Thus, the terminal can be prevented from continuing to request after pulling all the nodes to be pulled, thereby saving system resources.

[0085] Figure 4 The step flow of pulling the to-be-pulled nodes in the embodiments of the present application is schematically shown. Figure 4 As shown in the above embodiments, in some embodiments, the pulling of the to-be-pulled nodes in step S330 can further include the following steps S410-S430:

[0086] S410. The to-be-pulled nodes corresponding to each update record are obtained one by one in the order from old to new according to the update timestamp of the update record in the preset update record;

[0087] S420. Detecting whether each to-be-pulled node meets the filtering rule, and taking the to-be-pulled node meeting the filtering rule as a quasi-pulled node;

[0088] S430. Calculating the total number of quasi-pulled nodes, and when the total number of quasi-pulled nodes reaches a first preset number, pulling the first preset number of quasi-pulled nodes.

[0089] Thus, the nodes can be pulled and updated in the order from old to new according to the update timestamps of the update records in the preset update records. Before the pulling and updating, it is necessary to detect whether each to-be-pulled node meets the filtering rule. Thus, the filtering rule of the organization structure for the terminal can be followed in the node pulling process, thereby facilitating the management of the organization structure.

[0090] For example, the filtering rule between the nodes of each member and department in the organization structure can be set. In specific embodiments, the filtering rule can include multiple categories, for example, three categories can be included: 1. The nodes of the hidden department or member will not be displayed in the organization structure pulled by any terminal, and cannot be searched and viewed by any terminal. 2. When the terminal corresponding to the member node under the limited department is updated, only the nodes on the address book of the department can be seen. 3. When the terminal is updated, the nodes of the corresponding limited member or department cannot be pulled and viewed. Thus, although each terminal pulls the nodes and data of the remote organization structure to update the local organization structure of each terminal, the pulled nodes and the obtained local organization structure after the update can be different, which depends on what filtering rule is set for the member node of each terminal by the remote organization structure. Thus, the diversified management of the enterprise organization structure can be achieved.

[0091] In some embodiments, each to-be-pulled node corresponding to each update record can be obtained in the order from old to new according to the update timestamps of the update records in the preset update records, whether each to-be-pulled node meets the filtering rule is detected, the to-be-pulled node meeting the filtering rule is taken as a quasi-pulled node, the total number of quasi-pulled nodes is calculated, and when the total number of quasi-pulled nodes reaches a first preset number, the first preset number of quasi-pulled nodes are pulled.

[0092] In the specific implementation, multiple rules can be configured in parallel in each category of filtering rules. For example, a single enterprise can configure three categories, a total of 300 filtering rules, and each to-be-pulled node needs to pass the detection of 300 filtering rules. It can be understood that in the process of pulling the to-be-pulled node in step S330, it is necessary to detect whether each to-be-pulled node meets the filtering rules, thereby bringing a problem: the number of actual pull nodes in each batch can be much smaller than the to-be-pulled nodes that have undergone filtering rule detection, thereby making the detection number of each batch of pull nodes much larger than the first preset number of nodes in each batch, and the filtering rules can be relatively complex, making the detection time of each to-be-pulled node longer, thereby greatly increasing the time consumption of the process of pulling the to-be-pulled node in step S330. To overcome the above problems, the following Figure 5 The embodiments shown in the flow.

[0093] Figure 5 The step flow of detecting each to-be-pulled node whether it meets the filtering rules and taking the to-be-pulled node meeting the filtering rules as the quasi-pulled node in the embodiment of the application is schematically shown. As Figure 5 shown, on the basis of the above embodiment, in some embodiments, after detecting each to-be-pulled node whether it meets the filtering rules and taking the to-be-pulled node meeting the filtering rules as the quasi-pulled node in step S420, the following steps S510-S520 can be further included:

[0094] S510. Calculate the number of to-be-pulled nodes that have undergone detection;

[0095] S520. When the number of to-be-pulled nodes that have undergone detection reaches the second preset number, pull the quasi-pulled nodes meeting the filtering rules in the second preset number of to-be-pulled nodes.

[0096] The second preset number can be a multiple of the first preset number, for example, the second preset number can be twice the first preset number. That is, when the number of to-be-pulled nodes that have undergone detection reaches the second preset number 2*limit_cnt, even if the number of quasi-pulled nodes meeting the filtering rules in the to-be-pulled nodes does not reach the first preset number limit_cnt, the quasi-pulled nodes are pulled to the terminal in advance to complete the node pulling in this batch, which can avoid that the terminal is not responded for a long time, avoid that the time consumption of a batch of node pulling is too long to cause the interface response time to be unstable, thereby in the case that the organization architecture is large in size and the filtering rules are configured to be relatively complex, the node pulling in each batch can still be completed within a complexity range defined by the second preset number, and then the nodes with an update timestamp earlier than the preset timestamp and meeting the filtering rules are detected and pulled in batches, thereby realizing the update of the local organization architecture.

[0097] In some embodiments, the number of detected to-be-pulled nodes can be calculated, and then when the time cost by the nodes in the current batch for pulling is longer than the preset time, the quasi-pulled nodes meeting the filtering rule among the to-be-pulled nodes are pulled to complete the node pulling in the current batch.

[0098] On the basis of the above embodiments, in some embodiments, after the step S420 of detecting whether each to-be-pulled node meets the filtering rule and taking the to-be-pulled node meeting the filtering rule as a quasi-pulled node, the following step can be further included:

[0099] When all the to-be-pulled nodes are detected, all the quasi-pulled nodes meeting the filtering rule among the to-be-pulled nodes are pulled.

[0100] When all the to-be-pulled nodes are detected, it indicates that the update time stamps in the update flow table are all located after the time stamp of the last pulled organizational structure, and all the to-be-pulled nodes have been detected. At this time, all the quasi-pulled nodes meeting the filtering rule among the to-be-pulled nodes are pulled to the terminal to update the local organizational structure, and the node pulling in the current batch is completed, and the organizational structure update is also completed.

[0101] On the basis of the above embodiments, in some embodiments, after the step S430 of pulling the quasi-pulled node or the step S520 of pulling the quasi-pulled node, the following step can be further included:

[0102] The update time stamp with the latest time among the detected to-be-pulled nodes is taken as the preset time stamp.

[0103] In some embodiments, after the step S430 of pulling the quasi-pulled node, it can be understood that the node pulling in the current batch is completed. At this time, the update time stamp with the latest time among the detected to-be-pulled nodes is taken as the preset time stamp, which can make the to-be-pulled nodes in the next batch of node pulling exclude all the to-be-pulled nodes detected in the current batch, so as to avoid repeated detection of whether the same node meets the filtering rule, thereby avoiding waste of system resources and improving the node pulling efficiency and the organizational structure update efficiency.

[0104] In some embodiments, after the step S520 of pulling the quasi-pulled node, it can be understood that the node pulling in the current batch is completed. At this time, the update time stamp with the latest time among the detected to-be-pulled nodes is taken as the preset time stamp, which can make the to-be-pulled nodes in the next batch of node pulling exclude all the to-be-pulled nodes detected in the current batch, so as to avoid repeated detection of whether the same node meets the filtering rule, thereby avoiding waste of system resources and improving the node pulling efficiency and the organizational structure update efficiency.

[0105] S230. Update the pulled nodes of each batch to the local organization architecture.

[0106] When the terminal receives the pulled nodes of each batch, the pulled nodes of each batch can be updated to the local organization architecture, and the update of the local organization architecture is completed.

[0107] Figure 6 The step flow of updating the pulled nodes of each batch to the local organization architecture in the embodiment of the application is schematically shown. As shown in the figure, Figure 6 on the basis of the above embodiment, in some embodiments, the step of updating the pulled nodes of each batch to the local organization architecture in step S230 can further include the following steps S610-S620:

[0108] S610. When the pulled node has a corresponding original node in the local organization architecture, the original node is covered by the pulled node;

[0109] S620. When the pulled node does not have a corresponding original node in the local organization architecture, a corresponding node is newly created at a corresponding position in the local organization architecture according to the parent node information and the child node information associated with the pulled node.

[0110] When the pulled node has a corresponding original node in the local organization architecture, the original node is covered by the pulled node, and when the pulled node does not have a corresponding original node in the local organization architecture, a corresponding node is newly created at a corresponding position in the local organization architecture according to the parent node information and the child node information associated with the pulled node, thereby the pulled nodes of each batch can be updated to the local organization architecture.

[0111] Figure 7 The step flow after updating the pulled nodes of each batch to the local organization architecture in the embodiment of the application is schematically shown. As shown in the figure, Figure 7 on the basis of the above embodiment, in some embodiments, after updating the pulled nodes of each batch to the local organization architecture in step S230, the following steps S710-S720 can be further included:

[0112] S710. According to the pulled node, the node data corresponding to the pulled node is pulled from the remote organization architecture;

[0113] S720. Update the node data to the local organization architecture.

[0114] The node has a node code corresponding to some nodes, and the nodes pulled in each batch can only include the node code. After the nodes are pulled, the node data corresponding to the pulled nodes can be pulled from the remote organization structure according to the pulled nodes. The node data corresponding to the pulled nodes can include member name, member position, member contact information, member resume, department name, department function, department supervisor and other related data. Therefore, the nodes are pulled in batches, the nodes pulled in each batch are updated into the local organization structure, and then the node data corresponding to the pulled nodes is pulled from the remote organization structure according to the pulled nodes, and the node data is updated into the local organization structure, which can reduce the amount of data pulled in the node pulling process and improve the response speed of the organization structure update. Moreover, steps S710 and S720 can pull the node data in batches asynchronously in the background of the terminal after the nodes pulled in each batch are updated into the local organization structure, so as to reduce the occupancy rate of terminal resources in the organization structure update process and improve the update efficiency of the organization structure update.

[0115] Figure 8 The step flow of updating the node data into the local organization structure in the embodiment of the application is schematically shown. Figure 8 As shown in the above embodiment, in some embodiments, the node data includes summary data and detailed data, and the updating of the node data into the local organization structure in step S720 can further include steps S810-S820:

[0116] S810. Update the summary data of the node data into the corresponding node of the local organization structure;

[0117] S820. Read the detailed data corresponding to each summary data in the remote organization structure in batches, and update the detailed data into the corresponding node of the local organization structure.

[0118] The summary data can include member name, member position, department name, department supervisor and the like, and the detailed data can include member resume, member contact information, department function, department supervisor and other related data. Specifically, the summary data can be a necessary minimum field set for displaying the node, so that the summary data of the node data is updated into the corresponding node of the local organization structure first, and then the detailed data corresponding to each summary data in the remote organization structure is read in batches, and the detailed data is updated into the corresponding node of the local organization structure. The pulling of the summary data and the pulling of the detailed data with large data amount are separated, which can reduce the pulling time required in the summary data pulling process, is conducive to the rapid initialization of the local organization structure through the rapid pulling of the summary data, can improve the response speed of the local organization structure update service process, and improve the user experience.

[0119] In some embodiments, a large enterprise threshold value related to the complexity of the organizational structure can be set for the remote organizational structure, when the number of nodes of the remote organizational structure is greater than the large enterprise threshold value, the summary data of the node data can be updated into the corresponding nodes of the local organizational structure in the manner of steps S810-S820, and then the detailed data corresponding to each summary data in the remote organizational structure is read in batches, and the detailed data is updated into the corresponding nodes of the local organizational structure, so as to update the node data into the local organizational structure, which can improve the response speed of the terminal for pulling the summary data, realize the rapid initialization of the updated local organizational structure according to the summary data, and improve the user experience.

[0120] In summary, the organizational structure updating method provided by the embodiments of the present application acquires the update flow table of the remote organizational structure, takes the first preset number as the maximum value of the number of nodes pulled in each batch, pulls the nodes corresponding to the preset update records on the update flow table in batches until all the nodes corresponding to the preset update records are pulled, and then updates the nodes pulled in each batch to the local organizational structure. Thus, by means of batch incremental pulling, the response speed of node pulling is improved, the local is prevented from being unresponsive for a long time, the update of the organizational structure is realized with high efficiency and responsiveness, the transmission stability of the data transmission process is improved, the stability of the pulling mechanism and the organizational structure updating service is ensured, and the user experience is improved.

[0121] It should be noted that although the steps of the method in the present application are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in this specific order or that all the steps shown must be performed to achieve the desired results. In addition or alternatively, some steps can be omitted, a plurality of steps can be combined into one step, and / or one step can be divided into a plurality of steps, etc.

[0122] The device embodiments of the present application are introduced below, which can be used to execute the organizational structure updating method in the above-mentioned embodiments of the present application. Figure 9 The structure block diagram of the organizational structure updating device provided by the embodiments of the present application is schematically shown. As shown in Figure 9 The organizational structure updating device 900 can include:

[0123] The update flow table acquisition module 910 is configured to acquire the update flow table of the remote organizational structure, and the update flow table is used to store the nodes and update time stamps corresponding to each update record of the remote organizational structure;

[0124] The node batch-pulling module 920 is configured to pull the nodes corresponding to the preset update records on the update log in batches, with a first preset number as the maximum number of nodes pulled in each batch, until all the nodes corresponding to the preset update records are pulled, wherein the preset update records include the update records with update timestamps after a preset timestamp on the update log;

[0125] The node updating module 930 is configured to update the nodes pulled in each batch to the local organization structure.

[0126] In some embodiments of the present application, based on the above embodiments, the node batch-pulling module includes:

[0127] The preset timestamp determination unit is configured to take the timestamp of the last time the organization structure is pulled on the local organization structure as the preset timestamp;

[0128] The node-to-be-pulled determination unit is configured to take the update records with update timestamps after the preset timestamp as the preset update records, and take the nodes corresponding to each update record in the preset update records as the nodes to be pulled;

[0129] The node pulling unit is configured to pull the nodes to be pulled in batches, with the first preset number as the maximum number of nodes pulled in each batch, until all the nodes to be pulled are pulled.

[0130] In some embodiments of the present application, based on the above embodiments, the node pulling unit includes:

[0131] The node-to-be-pulled obtaining sub-unit is configured to obtain the nodes to be pulled corresponding to each update record in the preset update records in the order from old to new according to the update timestamps of the update records in the preset update records;

[0132] The quasi-pulled node determination sub-unit is configured to detect whether each node to be pulled meets the filtering rule, and take the node to be pulled meeting the filtering rule as a quasi-pulled node;

[0133] The first quasi-pulled node pulling unit is configured to calculate the total number of the quasi-pulled nodes, and pull the first preset number of quasi-pulled nodes when the total number of the quasi-pulled nodes reaches the first preset number.

[0134] In some embodiments of the present application, based on the above embodiments, the node pulling unit further includes:

[0135] The node-to-be-pulled calculating sub-unit is configured to calculate the number of the detected nodes to be pulled;

[0136] The second quasi-pull node pulling unit is configured to pull the quasi-pull nodes meeting the filtering rule from the second preset number of the to-be-pulled nodes when the number of the to-be-pulled nodes detected reaches the second preset number.

[0137] In some embodiments of the present application, based on the above embodiments, the node pulling unit further comprises:

[0138] The third quasi-pull node pulling unit is configured to pull the quasi-pull nodes meeting the filtering rule from all the to-be-pulled nodes when all the to-be-pulled nodes are detected.

[0139] In some embodiments of the present application, based on the above embodiments, the organization architecture updating apparatus further comprises:

[0140] The preset timestamp obtaining sub-unit is configured to take the update timestamp of the to-be-pulled node detected as the preset timestamp.

[0141] In some embodiments of the present application, based on the above embodiments, the node updating module comprises:

[0142] The first node updating unit is configured to overwrite the original node with the pulled node when the pulled node has a corresponding original node in the local organization architecture.

[0143] The second node updating unit is configured to newly build a corresponding node in the local organization architecture according to the parent node information and the child node information associated with the pulled node when the pulled node does not have a corresponding original node in the local organization architecture.

[0144] In some embodiments of the present application, based on the above embodiments, the organization architecture updating apparatus further comprises:

[0145] The node data pulling unit is configured to pull the node data corresponding to the pulled node from the remote organization architecture according to the pulled node.

[0146] The node data updating unit is configured to update the node data to the local organization architecture.

[0147] In some embodiments of the present application, based on the above embodiments, the node data comprises summary data and detailed data, and the node data updating unit comprises:

[0148] The summary data updating unit is configured to update the summary data of the node data to the corresponding node of the local organization architecture.

[0149] The detailed data updating unit is configured to read the detailed data corresponding to each summary data in the remote organization architecture in batches, and update the detailed data to the corresponding node of the local organization architecture.

[0150] The specific details of the organization architecture updating apparatus provided in the embodiments of the present application have been described in detail in the corresponding method embodiments, and thus will not be repeated here.

[0151] Figure 10 A structural block diagram of an electronic device for implementing the embodiments of the present application is schematically shown.

[0152] It should be noted that, Figure 10 The electronic device 1000 shown is only one example of an electronic device and should not be taken as limiting the scope of the present embodiments.

[0153] As Figure 10 shown, the electronic device 1000 includes a central processing unit 1001 (CPU) that can perform various appropriate actions and processes according to programs stored in a read-only memory 1002 (ROM) or loaded from a storage portion 1008 into a random access memory 1003 (RAM). Various programs and data required for the operation of the apparatus are also stored in the random access memory 1003. The central processing unit 1001, the read-only memory 1002, and the random access memory 1003 are connected to each other via a bus 1004. An input / output interface 1005 (I / O interface) is also connected to the bus 1004.

[0154] The following components are connected to the input / output interface 1005: an input portion 1006 including a keyboard, a mouse, and the like; an output portion 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), and the like, and a speaker, and the like; a storage portion 1008 including a hard disk, and the like; and a communication portion 1009 including a network interface card such as a local area network card, a modem, and the like. The communication portion 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the input / output interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 1010 as necessary, so that a computer program read therefrom is installed in the storage portion 1008 as necessary.

[0155] In particular, according to embodiments of the present application, the processes described in the various method flowcharts can be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program comprising program code for executing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network by the communication section 1009, and / or installed from the removable media 1011. When the computer program is executed by the central processing unit 1001, various functions defined in the apparatus of the present application are executed.

[0156] It should be noted that the computer readable medium shown in the embodiments of the present application can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may, for example, be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor device, device or apparatus, or any combination of the above. More specific examples of the computer readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution device, device or apparatus. In the present application, the computer readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer readable program code. Such a propagated data signal can take many forms, including but not limited to, an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium can also be any computer readable medium that can send, propagate or transfer a program for use by or in connection with an instruction execution device, device or apparatus. The program code contained on the computer readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, or the like, or any suitable combination of the above.

[0157] The computer program product of the present application can be a computer program including a plurality of program instructions that control at least one processing unit of a computer to implement a set of desired operations. Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors. The computer program product can be upl oaded to the memory of a machine and executed by a processor of the machine to implement the techniques described herein.

[0158] It should be noted that although several modules or units for devices for action execution are mentioned in the foregoing detailed description, such a division into modules or units is not mandatory. Indeed, according to an embodiment of the application, features and functionalities of two or more modules or units described above can be embodied in one module or unit. Conversely, features and functionalities of one module or unit described above can be further divided into several modules or units.

[0159] From the above description of embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software, or by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or network, and includes a plurality of instructions to make a computing device (which can be a personal computer, server, touch terminal, or network device, etc.) execute the methods according to the embodiments of the present application.

[0160] Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the present application cover any and all variations of the application that come within the scope of the present application, along with all of the equivalents thereof. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the application being indicated by the following claims.

[0161] It should be understood that the present application is not limited to the precise construction that has been described above and illustrated in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the present application. The scope of the present application is limited only by the appended claims.

Claims

1. An organization architecture updating method characterized by comprising: The method comprises: obtaining an update log of a remote organization framework, the update log being used to store nodes corresponding to each update record of the remote organization framework and update timestamps; taking a timestamp of the last time when the local organization framework pulls the organization framework as a preset timestamp; taking update records with update timestamps later than the preset timestamp as preset update records, and taking nodes corresponding to each update record in the preset update records as nodes to be pulled; taking a first preset number as a maximum of the number of nodes to be pulled in each batch, and pulling the nodes to be pulled in batches until all the nodes to be pulled are pulled, wherein the preset update records include update records with update timestamps later than the preset timestamp on the update log; the pulling of the nodes to be pulled comprises: obtaining the nodes to be pulled corresponding to each update record in the update records in the preset update records in the order from old to new according to the update timestamps of the update records; detecting whether each node to be pulled meets a filtering rule one by one, and taking the node to be pulled meeting the filtering rule as a node to be pulled; calculating the total number of the nodes to be pulled meeting the filtering rule, and when the total number of the nodes to be pulled meeting the filtering rule reaches the first preset number, pulling the first preset number of nodes to be pulled meeting the filtering rule; calculating the number of the nodes to be pulled that have been detected; and when the number of the nodes to be pulled that have been detected reaches a second preset number, pulling the second preset number of nodes to be pulled meeting the filtering rule; the second preset number is a multiple of the first preset number; wherein the pulling of the nodes to be pulled in batches until all the nodes to be pulled are pulled comprises: comparing the number of nodes to be pulled in each batch with the first preset number, and when the number of nodes to be pulled in each batch is greater than or equal to the first preset number, determining that the terminal has not pulled all the nodes to be pulled, and continuing to request pulling; and when the number of nodes to be pulled in each batch is less than the first preset number, determining that the terminal has pulled all the nodes to be pulled, and there is no need to continue to request pulling; updating the nodes pulled in each batch to the local organization framework of the client; pulling node data corresponding to the nodes to be pulled from the remote organization framework according to the pulled nodes, the node data including summary data and detailed data; when the number of nodes of the remote organization framework is greater than a large enterprise threshold related to the complexity of the organization framework set for the remote organization framework, updating the summary data of the node data to the corresponding nodes of the local organization framework of the client; reading the detailed data corresponding to each summary data in the remote organization framework in batches, and updating the detailed data to the corresponding nodes of the local organization framework of the client.

2. The organizational hierarchy updating method of claim 1, wherein, After the detection of whether each node to be pulled meets the filtering rule one by one and the taking of the node to be pulled meeting the filtering rule as a node to be pulled, the method further comprises: when all the nodes to be pulled have been detected, pulling all the nodes to be pulled meeting the filtering rule.

3. The organizational hierarchy updating method of claim 1, wherein, After pulling the quasi-pull node, the method further comprises: The latest update timestamp in the detected to-be-pulled node is taken as the preset timestamp.

4. The organizational hierarchy updating method of claim 1, wherein, The pulled nodes are updated into the local organization architecture of the client, comprising: When the pulled node has a corresponding original node in the local organization architecture of the client, the original node is overwritten by the pulled node; When the pulled node does not have a corresponding original node in the local organization architecture, a corresponding node is newly created in the corresponding position in the local organization architecture of the client according to the parent node information and the child node information associated with the pulled node.

5. An organization architecture updating apparatus characterized by comprising: Comprise: An update stream table acquisition module configured to acquire an update stream table of a remote organization architecture, wherein the update stream table is used to store nodes and update timestamps corresponding to each update record of the remote organization architecture; A node batch pulling module configured to pull nodes corresponding to preset update records on the update stream table in batches, with a first preset number as the maximum number of nodes per batch, until all nodes corresponding to the preset update records are pulled, wherein the preset update records comprise update records with update timestamps after a preset timestamp on the update stream table, and the preset timestamp is a timestamp of the last time the local organization architecture is pulled; A node updating module configured to update the nodes pulled in batches into a local organization architecture of a client; The node batch pulling module comprises: A preset timestamp determination unit configured to take the timestamp of the last time the local organization architecture is pulled as the preset timestamp; A to-be-pulled node determination unit configured to take update records with update timestamps after the preset timestamp as preset update records, and take nodes corresponding to each update record in the preset update records as to-be-pulled nodes; A node pulling unit configured to pull the to-be-pulled nodes in batches, with the first preset number as the maximum number of nodes per batch, until all the to-be-pulled nodes are pulled; wherein pulling the to-be-pulled nodes in batches until all the to-be-pulled nodes are pulled comprises: comparing the number of nodes pulled in each batch with the first preset number, and when the number of nodes pulled in each batch is greater than or equal to the first preset number, it is determined that the terminal has not pulled all the nodes to be pulled, and the pulling is continued; when the number of nodes pulled in each batch is less than the first preset number, it is determined that the terminal has pulled all the nodes to be pulled, and the pulling is not needed to continue; The node pulling unit comprises: A to-be-pulled node acquisition subunit configured to acquire to-be-pulled nodes corresponding to each update record in the preset update records in the order from old to new according to the update timestamps of the update records in the preset update records; A quasi-pull node determination subunit configured to detect whether the to-be-pulled nodes meet a filtering rule one by one, and take to-be-pulled nodes meeting the filtering rule as quasi-pull nodes; A first quasi-pull node pulling unit is configured to calculate a total number of the quasi-pull nodes, and when the total number of the quasi-pull nodes reaches a first preset number, pull the first preset number of quasi-pull nodes; The node pulling unit further includes: A to-be-pulled node calculating sub-unit configured to calculate a number of the to-be-pulled nodes detected; A second quasi-pull node pulling unit configured to, when the number of the to-be-pulled nodes detected reaches a second preset number, pull quasi-pull nodes that meet the filtering rule from the second preset number of to-be-pulled nodes; the second preset number is a multiple of the first preset number; The apparatus further includes: A node data pulling unit configured to pull, from the remote organization structure, node data corresponding to the pulled nodes according to the pulled nodes, the node data including summary data and detailed data; A node data updating unit configured to update the node data to the local organization structure of the client; The node data updating unit includes: A summary data updating unit configured to, when the number of nodes of the remote organization structure is greater than a large enterprise threshold set for the remote organization structure in relation to organization structure complexity, update the summary data of the node data to corresponding nodes of the local organization structure of the client; A detailed data updating unit configured to read detailed data corresponding to each summary data in the remote organization structure in batches, and update the detailed data to corresponding nodes of the local organization structure of the client.

6. A computer readable medium having stored thereon a computer program, characterized in that, The computer program, when executed by a processor, implements the organization structure updating method of any one of claims 1 to 4.

7. An electronic device, comprising: includes: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the organization structure updating method of any one of claims 1 to 4 via execution of the executable instructions.

8. A computer program product, characterised in that, The computer program product includes computer instructions stored in a computer readable storage medium, a processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the organization structure updating method of any one of claims 1 to 4.

Images