CN117319351A

CN117319351A - Address book management method, device, computer equipment and storage medium

Info

Publication number: CN117319351A
Application number: CN202210696800.6A
Authority: CN
Inventors: 黄铁鸣; 吕阳阳; 黄诗洋; 叶波; 李斌; 曾楚伟
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-06-20
Filing date: 2022-06-20
Publication date: 2023-12-29

Abstract

The application relates to an address book management method, an address book management device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: receiving an address book synchronization request which is initiated by a terminal and aims at an upstream address book and a downstream address book; determining target maintenance information corresponding to the upstream address book and the downstream address book, wherein the target maintenance information at least comprises an upstream and downstream organization node tree, at least one organization member node tree and upstream and downstream configuration rules; determining to-be-updated data matched with a request initiator based on target maintenance information, wherein the to-be-updated data at least comprises member information acquired from an organization architecture tree to which a member to be updated belongs; and feeding the data to be updated back to the terminal so as to instruct the terminal to update the upstream address book and the downstream address book specified by the address book synchronization request based on the data to be updated. By adopting the method, high-efficiency and rapid cross-tissue cooperation can be realized.

Description

Address book management method, device, computer equipment and storage medium

Technical Field

The present invention relates to the field of computer communications technologies, and in particular, to an address book management method, an apparatus, a computer device, a storage medium, and a computer program product.

Background

With the gradual diversification of enterprise business, more and more industries need the mutual cooperation and cooperative cooperation of enterprises in the whole industry chain. With the development and the increasing perfection of industry, there are few, more and hundreds of enterprises in an industry chain, and how to efficiently communicate and cooperate between enterprises becomes a current urgent problem to be solved.

At present, enterprises can communicate with each other through communication software, and in order to record each enterprise cooperated with each other, a corresponding address book is established in the communication software so as to facilitate the mutual communication between the enterprises. For enterprise members participating in collaboration, a full amount of address books are generally built separately, maintained and updated by a server. However, because the address book involves a plurality of enterprises and members, any enterprise needs to perform full-scale synchronization on the address book by the server, such as adding and withdrawing of any enterprise, adding and deleting of members in the enterprise, and the like, when the server maintains the address book, the risk of inconsistent data is caused, and the stability and accuracy of address book synchronization are low. Meanwhile, in the scene of large-scale inter-enterprise collaboration, the address book data required to be maintained by the server is huge, and the efficiency of address book synchronization in the mode is quite low.

Disclosure of Invention

In view of the foregoing, it is desirable to provide an address book management method, apparatus, computer device, computer readable storage medium, and computer program product that can improve the communication efficiency between enterprises.

In one aspect, the application provides an address book management method. The method comprises the following steps:

receiving an address book synchronization request which is initiated by a terminal and aims at an upstream address book and a downstream address book;

determining target maintenance information corresponding to the upstream and downstream address books, wherein the target maintenance information at least comprises an upstream and downstream organization node tree, at least one organization member node tree and upstream and downstream configuration rules;

determining to-be-updated data matched with the request initiator based on the target maintenance information, wherein the to-be-updated data at least comprises member information acquired from an organization architecture tree to which members to be updated belong;

and feeding the data to be updated back to the terminal so as to instruct the terminal to update the upstream address book and the downstream address book specified by the address book synchronization request based on the data to be updated.

On the other hand, the application also provides an address book management device. The device comprises:

the receiving module is used for receiving an address book synchronization request aiming at the upstream address book and the downstream address book, which is initiated by the terminal;

The determining module is used for determining target maintenance information corresponding to the upstream and downstream address books, wherein the target maintenance information at least comprises an upstream and downstream organization node tree, at least one organization member node tree and upstream and downstream configuration rules;

the determining module is further configured to determine, based on the target maintenance information, data to be updated that matches the request initiator, where the data to be updated includes at least member information obtained from an organizational structure tree to which a member to be updated belongs;

and the feedback module is used for feeding the data to be updated back to the terminal so as to instruct the terminal to update the upstream address book and the downstream address book specified by the address book synchronization request based on the data to be updated.

In another aspect, the present application also provides a computer device. The computer device comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the steps of the address book management method when executing the computer program.

In another aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the address book management method described above.

In another aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of the address book management method described above.

According to the address book management method, the address book management device, the computer equipment, the storage medium and the computer program product, the target maintenance information corresponding to the upstream and downstream address books is determined through receiving the address book synchronization request for the upstream and downstream address books initiated by the terminal, and the data to be updated matched with the request initiator is determined based on the target maintenance information and combined with two types of node trees and upstream and downstream configuration rules in the target maintenance information so as to update the locally stored upstream and downstream address books by the terminal. The server does not need to store the full address book data, and the upstream and downstream organization node tree and the member node tree are sequentially synchronized during synchronization, and incremental updated data are returned to the terminal, so that the synchronization efficiency of the upstream and downstream address books is improved. Meanwhile, the data to be updated is the data which is updated in an increment and filtered by rules, so that the accuracy of synchronization is higher, and the privacy safety of the data is effectively protected.

On the other hand, the application also provides a cross-tissue communication method. The method comprises the following steps:

Exposing upstream and downstream management interfaces in an organization communication application;

responding to the synchronous operation for the upstream and downstream address books initiated in the upstream and downstream management interfaces, and sending an address book synchronous request to a server;

receiving data to be updated fed back by a server in response to the address book synchronization request, wherein the data to be updated is determined based on target maintenance information corresponding to the upstream and downstream address books and at least comprises member information acquired from an organization architecture tree to which members to be updated belong, and the target maintenance information at least comprises an upstream and downstream organization node tree, at least one organization member node tree and upstream and downstream configuration rules;

displaying the upstream and downstream address books updated by the data to be updated, wherein the upstream and downstream address books are used for realizing cross-organization communication.

On the other hand, the application also provides a cross-tissue communication device. The device comprises:

the display module is used for displaying the upstream and downstream management interfaces in the organization communication application;

the sending module is used for responding to the synchronous operation for the upstream address book and the downstream address book initiated in the upstream and downstream management interfaces and sending an address book synchronous request to the server;

The receiving module is used for receiving data to be updated fed back by the server in response to the address book synchronization request, the data to be updated is determined and obtained based on target maintenance information corresponding to the upstream address book and the downstream address book, and at least comprises member information acquired from an organization architecture tree to which members to be updated belong, and the target maintenance information at least comprises an upstream organization node tree, a downstream organization node tree, at least one organization member node tree and an upstream configuration rule and a downstream configuration rule;

the display module is further used for displaying the upstream and downstream address books updated by the data to be updated, and the upstream and downstream address books are used for realizing cross-organization communication.

In another aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the steps of the above-described cross-tissue communication method when the processor executes the computer program.

In another aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the above-described cross-fabric communication method.

In another aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of the above-described cross-tissue communication method.

According to the above-mentioned cross-organization communication method, device, computer equipment, storage medium and computer program product, the terminal displays the management interface of the upstream and downstream address books through the organization communication application, and sends the address book synchronization request triggered by the object to the server, so that the server can determine the incrementally updated data according to the request; after receiving the incremental updated data, the terminal updates the locally stored upstream and downstream address books and displays the latest upstream and downstream address books. Therefore, the terminal does not need to store the full amount of upstream and downstream address books again by updating in an increment synchronization mode, the synchronization efficiency of the upstream and downstream address books is higher, the stability is higher, and the problem of inconsistent data is avoided.

Drawings

FIG. 1 is an application environment diagram of an address book management method in one embodiment;

FIG. 2 is a flowchart of an address book management method according to an embodiment;

FIG. 3 is a schematic diagram of an upstream and downstream organization node tree and a member node tree in one embodiment;

FIG. 4 is a schematic diagram of an upstream and downstream organization node tree and a member node tree in another embodiment;

FIG. 5 is a schematic diagram of a flow meter in one embodiment;

FIG. 6 is a schematic diagram of an interface providing cross-organization communication functionality in one embodiment;

FIG. 7 is an interface diagram of a group session in cross-organizational communication in one embodiment;

FIG. 8 is a detailed interface diagram of a group session in one embodiment;

FIG. 9 is an interface diagram of an organization communication application in one embodiment;

FIG. 10 is a schematic diagram of upstream and downstream collaboration in an organization communication application, in accordance with one embodiment;

FIG. 11 is a schematic diagram illustrating an interface between upstream and downstream address books in one embodiment;

FIG. 12 is a schematic diagram of an interface of an upstream and downstream address book according to another embodiment;

FIG. 13 is a schematic diagram of members of an organization in an upstream and downstream address book, according to one embodiment;

FIG. 14 is a schematic diagram illustrating an embodiment of removing a member of an organization in an upstream and downstream address book;

FIG. 15A is a functional block diagram of an address book management method according to one embodiment;

FIG. 15B is a functional block diagram of an address book management method according to another embodiment;

FIG. 16 is a flow diagram of a method of cross-organization communication in one embodiment;

FIG. 17 is a block diagram illustrating an address book management device according to an embodiment;

FIG. 18 is a block diagram of a cross-organization communication device in one embodiment;

fig. 19 is an internal structural view of the computer device in one embodiment.

Detailed Description

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

The address book management method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. In some embodiments, data corresponding to the upstream and downstream address books is stored hierarchically by the server 104, which maintains updates and synchronization of the upstream and downstream address books by maintaining upstream and downstream organization node trees, member node trees organized in the upstream and downstream organization node trees, and upstream and downstream configuration rules. The data storage system may be integrated on the server 104 or may be located on the cloud or other servers. The server 104 receives the address book synchronization request initiated by the terminal 102, determines an upstream address book and a downstream address book to be updated based on the address book synchronization request, further determines target maintenance information corresponding to the upstream address book and the downstream address book, determines a target configuration rule matched with a request initiator of the address book synchronization request according to stored upstream and downstream configuration rules corresponding to the upstream and downstream address books, combines two types of node trees stored in the target maintenance information, and performs screening based on the target configuration rules, thereby obtaining data to be updated corresponding to the request initiator. The server 104 feeds back the data to be updated to the terminal 102. After receiving the data to be updated, the terminal 102 updates the upstream and downstream address books and displays the updated upstream and downstream address books. Thus, the terminal 102 realizes synchronization of the upstream and downstream address books.

The terminal 102 may be, but not limited to, various desktop computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like.

The server 104 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), basic cloud computing services such as big data and artificial intelligence platforms, and the like.

In some embodiments, the terminal may be loaded with APP (Application) applications or applications with inter-organizational communication capabilities, including applications that traditionally need to be installed separately, and applet applications that can be used without downloading an installation.

The terminal is provided with an organization communication application, and the organization can establish an organization internal address book of the organization through the registration account. The address book in the organization refers to data of the organization itself, which is composed of members, departments, labels, organization architecture relations and the like in the organization. Where a member refers to an organization's employee or service account. The division includes at least one member and may further include at least one sub-division. For each organization in the upstream and downstream address books, each organization has its own internal address book.

In the organization communication application, the member can log in the application program through the registration account number and communicate with other members of the same organization included in the organization internal address book, and when participating in the upstream and downstream collaboration, the member can communicate and collaborate with members of other organizations through the upstream and downstream address book.

In some embodiments, as shown in fig. 2, an address book management method is provided, and the method is applied to the server in fig. 1 for illustration, and includes the following steps:

step S202, an address book synchronization request for an upstream address book and a downstream address book initiated by a terminal is received.

The upstream and downstream address books refer to trans-organization address books formed by an upper organization and a lower organization together. Members belonging to different organizations which join in the upstream and downstream address books can communicate and cooperate under the condition of not adding friends. Each of the upstream and downstream address books corresponds to a unique identifier that is used to distinguish the indicated upstream and downstream address book from the other upstream and downstream address books. For example, the unique identifier for identifying one upstream and downstream may be represented by Chainid (upstream and downstream).

The upstream organization is also called an upstream organization, and serves as a creator of the upstream address book, and serves as upstream in the process of industry link collaboration, for example, as an upstream dealer, a brand name party, and the like. The downstream organization is also called a lower-level organization, and after the upstream organization creates the upstream and downstream address books, the downstream organization can be invited to be added into the upstream and downstream address books to cooperate and communicate with the upstream organization. The downstream organization is downstream in the process of industry chain collaboration, for example, a vendor, etc. Typically, an upstream organization typically has a cooperative relationship with a plurality of downstream organizations. Correspondingly, an upstream address book generally comprises an upstream organization, a plurality of downstream organizations and the like.

It should be understood that an organization that is a downstream organization in one upstream and downstream address book may also be an upstream organization in another upstream and downstream address book; similarly, an organization that is an upstream organization in one upstream and downstream address book may also be a downstream organization in another upstream and downstream address book.

Specifically, the object triggers the terminal through an application interface displayed by the application program, the terminal responds to the triggering operation of the object, generates an address book synchronization request for the upstream address book and the downstream address book, and sends the address book synchronization request to the server.

In an exemplary scenario, at least one interactive element is displayed in an application interface presented by the terminal through the application program, where the interactive element can be triggered by the object, so that the application program executes logic encapsulated in a configuration file corresponding to the interactive element. The interactive elements are, for example, virtual buttons, icons, links, or the like. For example, a virtual button or icon for "point this synchronization" is displayed in the application interface, and after the object clicks on the virtual button or icon, the application program executes a process of synchronizing the upstream and downstream address books. For another example, when the object triggers the application program to display the upstream and downstream address books, the terminal generates an address book synchronization request and sends the address book synchronization request to the server to display the updated upstream and downstream address books.

In order to indicate which of the upstream and downstream address books is specific, the address book synchronization request includes at least an upstream and downstream identifier. The server receives an address book synchronization request initiated by the terminal, and extracts upstream and downstream identifiers included in the address book synchronization request, so as to determine upstream and downstream address books to be updated.

Step S204, determining target maintenance information corresponding to the upstream and downstream address book, wherein the target maintenance information at least comprises an upstream and downstream organization node tree, at least one organization member node tree and upstream and downstream configuration rules.

Specifically, the server determines an upstream address book and a downstream address book to be synchronized corresponding to the upstream and downstream identifiers according to the upstream and downstream identifiers in the address book synchronization request. And searching the corresponding stored data for the upstream and downstream address books to be synchronized by the server, and determining target maintenance information corresponding to the upstream and downstream address books. The data corresponding to the upstream address book and the downstream address book are stored in a tree structure, and at least comprise an upstream organization node tree, a downstream organization node tree and a member node tree.

In some embodiments, the upstream and downstream organization node tree characterizes an upstream and downstream relationship between the upstream organization and at least one downstream organization, in which the upstream organization and one or more downstream organizations are stored, the root node is the upstream address book, and the primary node is the upstream organization and each downstream organization, such as the tree structure shown in fig. 3. The specific structure of the upstream and downstream organization node trees is mapped in the computer equipment, and then the upstream and downstream identifications, the organization identifications of the upstream organizations and the organization identifications of the downstream organizations are stored. In some embodiments, for ease of management, the terminal may divide the downstream organization into upstream and downstream packets in response to operation of the object; correspondingly, in the upstream and downstream organization node tree stored by the server, each downstream organization is stored in an upstream and downstream packet, and one upstream and downstream packet is a primary node. For each upstream and downstream packet, the downstream organization contained therein acts as a secondary node, such as the tree structure shown in fig. 4.

Each organization node in the upstream and downstream organization node tree has a corresponding member node tree. In some embodiments, an organization's member node tree characterizes the participating member scope of each organization that participates in the upstream-downstream collaboration. The member node tree includes a plurality of member nodes including departments or members participating in an organization that cooperates upstream and downstream. It should be appreciated that the member node tree of an organization node stored in the upstream and downstream address books is a subset of the organization node's own internal organization architecture tree. The departments participating in the upstream-downstream collaboration include all the members of the departments.

As shown in fig. 3 to fig. 4, in the tree structure corresponding to the upstream and downstream address books, the upper half stores the upstream and downstream organization node trees, and the lower half stores the corresponding member node tree in each organization node. For example, in an upstream-downstream address book, the upstream-downstream organization node tree includes an upstream organization, a downstream organization a, and a downstream organization B. For the downstream organization a, the own organization internal address book includes a department 1, a department 2 and a member 1, wherein the department 1 includes a member 2 and a member 3. Wherein department 1 and member 1 participate in the upstream and downstream collaboration for the upstream and downstream address book. Accordingly, the member node tree of the downstream organization a includes a department 1 and a member 1, and the department 1 further includes a member 2 and a member 3.

In order to finely manage the upstream and downstream address books and reasonably manage the authority between the upstream organization and the downstream organization, the upstream organization is provided with upstream and downstream configuration rules when the upstream and downstream address books are created; correspondingly, the server stores upstream and downstream configuration rules corresponding to the upstream and downstream address books. In some embodiments, the upstream and downstream configuration rules include, but are not limited to, one or more of a configuration scope of an organization, a docking relationship between members in an upstream organization and downstream organizations, and a visible relationship between different members of different organizations, etc. Based on the upstream and downstream configuration rules, the server may determine the docking rights and visible range for each member. The configuration range of an organization indicates members and departments which the organization is configured to join when participating in an upstream and downstream address book in a specific organization. The interfacing relationship between the members in the upstream organization and the downstream organization includes the interfacing relationship between the members in the upstream organization participating in the upstream-downstream collaboration and the downstream organization, and the interfacing relationship between the members in the upstream organization participating in the upstream-downstream collaboration and the members in the downstream organization participating in the upstream-downstream collaboration. The visible relations among different members of different organizations are used for setting the authority of each member, for example, the members in the upstream organization can view departments or members of the downstream organization participating in upstream and downstream collaboration, the downstream organization can only see part of the members in the upstream organization, or can see/not see among the downstream organizations, etc. For example, if the member a in the upstream organization is set to connect to the downstream organization 1 and the member B is set to connect to the downstream organization 2, the member a cannot view the members added to the upstream address book and the downstream address book in the downstream organization 2, and cannot communicate and cooperate with the downstream organization 2. For another example, if the member a in the upstream organization is set to connect the P department and the E department of the downstream organization 1, the member a cannot view the related information of other departments of the downstream organization 1 participating in the upstream-downstream collaboration.

In some embodiments, for an upstream address book and a downstream address book, the server further stores upstream and downstream relationship mapping data, where the upstream and downstream relationship mapping data is used to represent a mapping relationship between an organization and the upstream and downstream address books, and the mapping relationship includes a positive mapping relationship and a reflection relationship. For example, which of the upstream and downstream address books a certain organization joins, which organization is involved in one of the upstream and downstream address books, etc. Illustratively, one or more upstream and downstream address books joined by an organization are represented in the form of a data table, recording one or more of creator, upstream organization initiating invitation, upstream and downstream identification, version number, update time, etc. For another example, one or more organizations added to a certain upstream and downstream address book are represented by a data table.

In some embodiments, for an upstream and downstream address book, the server further stores upstream and downstream address book attribute data, where the upstream and downstream address book attribute data includes, but is not limited to, one or more of an upstream and downstream identifier, a state, a creator, an organization to which the creator belongs, a creation time, a modification time, an upstream and downstream architecture root node, an upstream and downstream name, and upstream and downstream description information.

According to the upstream and downstream configuration rules, the server does not need to store the address book in the organization corresponding to each organization when storing the data corresponding to the upstream and downstream address books, in other words, for the organization of the upstream and downstream address books, the server does not need to store the organization architecture of each organization, and also does not need to store the specific member information of each member of each organization participating in the upstream and downstream collaboration, so that the resource occupation of the server is greatly reduced. Especially, for the ultra-large organization involving tens of thousands or even hundreds of thousands of members, not only is the server resource saved, but also the synchronization efficiency of the upstream address book and the downstream address book is greatly improved.

Step S206, based on the target maintenance information, determining the data to be updated matched with the request initiator, wherein the data to be updated at least comprises member information acquired from an organization architecture tree to which the members to be updated belong.

The data to be updated is the determined organization node to be updated, member node to be updated or member information to be updated corresponding to the member based on the tree structure corresponding to the stored upstream and downstream address book. The member information includes, but is not limited to, account information of the member in the organization communication application, such as one or more of a member name, a job level, a job position, and a contact address. For example, when an organization node changes, corresponding member nodes and member information in the upstream and downstream address books also change. As are member nodes. Therefore, the data to be updated at least includes member information acquired from the organizational structure tree to which the member to be updated belongs. Specifically, the server determines one or more of an organization node to be updated and a member node to be updated according to an upstream and downstream organization node tree and at least one organization member node tree in the target maintenance information. Specifically, for the tree structure corresponding to the upstream and downstream address book, the server traverses the upstream and downstream organization node tree according to the logic sequence from top to bottom, detects the organization nodes in the upstream and downstream organization node tree, detects each organization node in the upstream and downstream organization node tree, acquires the member node tree corresponding to each organization node, and detects the member node in the member node tree.

In other words, the server first searches the upstream and downstream organization node trees in the target maintenance information according to the determined target maintenance information, and determines whether the organization nodes in the upstream and downstream organization node trees change, for example, whether a certain downstream organization node is newly added or a certain downstream organization node is deleted. And when the addition and deletion exist in the organization nodes in the upstream and downstream organization node tree, determining the changed organization nodes as data to be updated. The server then processes each of the organization nodes separately. For each organization node in the upstream and downstream organization node tree, the server determines whether a member node in the member node tree of the organization corresponding to the organization node changes, for example, whether a member is newly added or deleted. When the addition and deletion exists in the member nodes in the member node tree of a certain organization, the member node with variation is determined to be used as the data to be updated. And for all the members corresponding to the determined member nodes to be updated, the server acquires member information corresponding to each member, and takes the member information as data to be updated.

Illustratively, when a downstream organization node is newly added in the upstream and downstream organization node tree, for the newly added downstream organization node, the server obtains the member node tree of the organization corresponding to the newly added downstream organization node, and searches whether the member node in the member node tree of the organization corresponding to the newly added downstream organization node changes.

Illustratively, when a downstream organization node is deleted from the upstream and downstream organization node trees, the server does not need to determine whether the member nodes in the member node tree of its corresponding organization change for the deleted organization node.

Since the visible range of each member is specified in the upstream and downstream configuration rules, after the server determines the data to be updated, the server screens the data to be updated according to the upstream and downstream configuration rules matched with the request initiator, and the data to be updated in the visible range specified by the upstream and downstream configuration rules is used as the data to be updated which is finally fed back to the terminal. Correspondingly, the address book synchronization request also comprises an object identifier, and the object identifier is used for indicating the identity information of the object initiating the request.

In some embodiments, the server may also traverse the two types of node trees and determine specific data to be updated according to the rule corresponding to the object identifier in the upstream and downstream configuration rules under the constraint of the visible range specified by the rule. In other words, the embodiment of the application is not limited to determining all the data to be updated first, then screening according to the upstream and downstream configuration rules to obtain the final data to be updated, or directly determining the final data to be updated under the constraint of the upstream and downstream configuration rules. Step S208, the data to be updated is fed back to the terminal, so as to instruct the terminal to update the upstream address book and the downstream address book specified by the address book synchronization request based on the data to be updated.

Specifically, the server sends the data to be updated to the terminal, and after the terminal receives the data to be updated, the upstream address list and the downstream address list are updated according to the data to be updated and displayed. For example, for the added organization node, displaying a downstream organization corresponding to the added organization node in the updated upstream and downstream address book; and for the deleted organization nodes, removing the corresponding downstream organization in the updated upstream and downstream address book.

In some embodiments, the server determines, according to the target maintenance information, that the upstream and downstream address books locally stored in the terminal are in the latest version, that is, when the upstream and downstream organization node tree, the member node tree of at least one organization, the upstream and downstream configuration rules and the like are unchanged, the server feeds back to the terminal without updating the upstream and downstream address books.

In the address book management method, the target maintenance information corresponding to the upstream and downstream address books is determined by receiving the address book synchronization request for the upstream and downstream address books initiated by the terminal, the target configuration rule matched with the request initiator is determined according to the upstream and downstream configuration rules included in the target maintenance information, and under the constraint of the target configuration rule, the data to be updated is determined and fed back to the terminal by combining two types of node trees in the target maintenance information, so that the terminal can update the locally stored upstream and downstream address books. The server does not need to store the full address book data, and the upstream and downstream organization node tree and the member node tree are sequentially synchronized during synchronization, and incremental updated data are returned to the terminal, so that the synchronization efficiency and accuracy of the upstream and downstream address books are improved.

Because the visible relationships corresponding to each member are different, in some embodiments, the data to be updated is data obtained by filtering the updated data according to the upstream and downstream configuration rules matched with the object identifiers in view of data privacy protection. Accordingly, in some embodiments, determining data to be updated that matches the request originator based on the target maintenance information includes: determining a target configuration rule matched with a request initiator of an address book synchronization request based on the upstream and downstream configuration rules; and the server acquires the data to be updated corresponding to the request initiator according to the upstream and downstream organization node tree and at least one organization member node tree and the target configuration rule.

Specifically, for the upstream and downstream configuration rules corresponding to the upstream and downstream address books, the server searches for a target configuration rule matched with the request initiator in the overall upstream and downstream configuration rules according to the request initiator of the current initiation request, and then updates the target configuration rule under the limitation of the target configuration rule. For example, the upstream and downstream configuration rules are provided with an organization and a visible range which are respectively butted by each member participating in upstream and downstream cooperation, and the server searches the target configuration rules matched with the request initiator in the organization and the visible range, so as to determine data fed back to the terminal.

For example, when creating the upstream and downstream address book, the upstream and downstream configuration rules are set to be that the member a in the upstream organization is in contact with the downstream organization 1, and the member B is in contact with the downstream organization 2, so that the member a cannot view the member added into the upstream and downstream address book in the downstream organization 2, and cannot communicate and cooperate with the downstream organization 2. When the server acquires the address book synchronization request triggered by the member a, after determining that the request initiator is the member a, the server determines a target configuration rule corresponding to the member a according to a preset upstream and downstream configuration rule, that is, the target configuration rule is that the member a abuts against all members in the downstream organization 1, for example, all members in the downstream organization 1 can be seen, and so on.

In the above embodiment, the data to be updated is screened according to the target configuration rule, and the upstream address book and the downstream address book are updated in the visible authority range of the member, so that specific information leakage of organizations is avoided, and the data security and privacy of each organization are effectively protected. Meanwhile, the data are screened to determine final data to be updated, so that the synchronization efficiency of the terminal is improved.

Compared with a common address book, the upstream and downstream address books provided for a plurality of upstream and downstream organizations to perform upstream and downstream collaboration relate to a plurality of organizations and a plurality of members, the authorities of the upstream organization and the downstream organization are different, the authorities of the members are different, and the contents of the upstream and downstream address books which can be checked are different. Besides node variation of downstream organization, departments and node variation of members, information variation of members, change of docking rules and the like trigger update of the upstream address book and the downstream address book, which results in complicated synchronization of the upstream address book and the downstream address book. In order to further ensure accuracy of the upstream address book and the downstream address book during synchronization, in some embodiments, the terminal further stores version information of the upstream address book and the downstream address book, the server stores the latest version information, and when the terminal initiates an address book synchronization request to the server, the server determines data to be updated in combination with the version information.

For this purpose, in some embodiments, the address book synchronization request further carries first version information, and the target maintenance information corresponds to the second version information. The first version information is version information stored locally by the terminal, and the second version information is version information stored by the server. The update time characterized by the first version information is no later than the update time characterized by the second version information. When the terminal sends an address book synchronization request to the server, the terminal simultaneously sends the locally stored first version information so as to enable the server to compare with the stored second version information according to the received version information.

Correspondingly, obtaining the data to be updated corresponding to the request initiator comprises the following steps: determining the current latest second version information; determining history maintenance information corresponding to the first version information in the case that the second version information is inconsistent with the first version information; and determining data to be updated, which is matched with a request initiator of the address book synchronization request, based on the difference between the target maintenance information and the history maintenance information.

Specifically, the server determines the latest second version information currently stored, and compares the received first version information with the second version information. And under the condition that the first version information and the second version information are consistent, the fact that the upstream and downstream address books locally stored by the terminal are the latest version is indicated, and the server feeds back to the terminal without updating the upstream and downstream address books.

Under the condition that the first version information and the second version information are inconsistent, the server acquires the historical maintenance information corresponding to the first version information, compares the historical maintenance information with the target maintenance information, determines the place where the target maintenance information is updated compared with the historical maintenance information, and determines corresponding data to be updated according to the place where the target maintenance information is updated. The history maintenance information comprises a history upstream and downstream organization node tree, a history member node tree, a history upstream and downstream configuration rule and the like.

For example, when the upstream and downstream organization node trees in the target maintenance information have a variation compared to the upstream and downstream organization node trees in the history maintenance information, for example, the downstream organization nodes are added, the downstream organization nodes are deleted, or the upstream and downstream packets to which the downstream organization belongs are changed, etc.

For another example, when a member node in the member node tree in the target maintenance information is added, subtracted, or moved (e.g., department change to which the member belongs) as compared to a member node in the member node tree in the history maintenance information.

For another example, when the upstream and downstream configuration rules in the target maintenance information are changed as compared to the upstream and downstream configuration rules in the history maintenance information.

Therefore, the target maintenance information and the history maintenance information are compared, the upstream address book and the downstream address book are updated in an incremental synchronization mode, and as all data are not needed to be synchronized, the synchronization efficiency of the upstream address book and the downstream address book can be greatly improved, the communication data volume between a server and a terminal can be reduced, and synchronization failure caused by network fluctuation is avoided.

In the above embodiment, determining data to be updated that matches the request initiator of the address book synchronization request based on the difference between the target maintenance information and the history maintenance information includes: determining an organization node to be updated according to upstream and downstream configuration rules based on the difference between upstream and downstream organization node trees respectively included in the target maintenance information and the history maintenance information; determining member nodes to be updated according to upstream and downstream configuration rules based on differences between member node trees of at least one organization included in each of the target maintenance information and the history maintenance information; determining the member to be updated at this time at least according to the member node to be updated, and acquiring member information of the member to be updated from an organization architecture tree to which the member to be updated belongs; the organization node to be updated, the member node to be updated and the member information together form the data to be updated.

Specifically, the server compares the organization nodes that have changed between the upstream and downstream organization node trees in the target maintenance information based on the structural differences between the upstream and downstream organization node trees in the history maintenance information. And then screening the obtained changed organization nodes according to the target configuration rules determined in the upstream and downstream configuration rules to obtain the organization nodes to be updated which accord with the target configuration rules.

After the inquiry and detection of the upstream and downstream organization node trees are completed, for any one of the upstream and downstream organization node trees, the server acquires the member node tree of the organization, and compares the member node with the member node tree in the history maintenance information based on the structural difference between the member node tree in the target maintenance information and the member node tree in the history maintenance information. And screening the obtained changed member nodes according to the target configuration rules determined in the upstream and downstream configuration rules to obtain the member nodes to be updated which accord with the target configuration rules.

In one case, the organization nodes in the upstream and downstream organization node tree change, the member nodes in the organization member node tree do not change, and the upstream and downstream configuration rules do not change, so that the server can determine the member nodes to be updated according to the changed organization nodes, and screen according to the target configuration rules in the upstream and downstream configuration rules to determine the members to be updated, which are matched with the request initiator.

In another case, the organization nodes in the upstream and downstream organization node trees change, the member nodes in one or more organization member node trees also change, and the upstream and downstream configuration rules do not change, so that the server can screen all members included in the organization nodes to be updated and members indicated by each member node to be updated according to the organization nodes to be updated and the member nodes to be updated, and obtain the member to be updated after screening the target configuration rules in the upstream and downstream configuration rules.

In another case, the organization nodes in the upstream and downstream organization node tree change, the member nodes in the organization member node tree do not change, and the upstream and downstream configuration rules change, so that the server can determine the member nodes to be updated according to the changed organization nodes, determine the organization nodes and the member nodes affected by the change of the rules according to the latest upstream and downstream configuration rules, and further comprehensively determine the member to be updated.

In another case, the organization nodes of the upstream and downstream organization node trees are not changed, the member nodes in one or more organization member node trees are changed, and the upstream and downstream configuration rules are not changed, so that the server can determine the member nodes to be updated according to the changed member nodes, and can screen according to the target configuration rules in the upstream and downstream configuration rules to determine the member to be updated matched with the request initiator.

In another case, the organization nodes of the upstream and downstream organization node tree are not changed, the member nodes in one or more organization member node trees are changed, and the upstream and downstream configuration rules are changed, so that the server determines the member nodes to be updated according to the changed member nodes, determines the organization nodes or member nodes affected by the change of the rules according to the latest upstream and downstream configuration rules, and further comprehensively determines the member to be updated.

In another case, the organization nodes of the upstream and downstream organization node tree are not changed, the member nodes in the organization member node tree are not changed, and the upstream and downstream configuration rules are changed, so that the server determines the organization nodes or the member nodes affected by the change of the rules according to the latest upstream and downstream configuration rules, and further determines the members to be updated.

In another case, the organization nodes in the upstream and downstream organization node trees change, the member nodes in one or more organization member node trees also change, and the upstream and downstream configuration rules change, so that the server determines the organization nodes to be updated according to the changed organization nodes, determines the member nodes to be updated according to the changed member nodes, and performs screening according to the latest upstream and downstream configuration rules, thereby determining the members to be updated.

After the members to be updated are determined, the server acquires the member information of each member to be updated, and forms the organization node to be updated, the member node to be updated and the member information together into data to be updated and returns the data to the terminal so that the terminal can update the upstream address book and the downstream address book according to the data to be updated.

In the above embodiment, the data to be updated is determined by combining the upstream and downstream configuration rules based on the difference between the target maintenance information and the history maintenance information, so that the whole address book data is not required to be synchronized in full, and the synchronization efficiency of the upstream and downstream address books is improved.

In some embodiments, a first member change version number corresponding to the requestor is included in the first version information. The member change version number is used to indicate the change condition of a specific member, and the change condition includes adding, deleting, moving, and the like of the member. Accordingly, at least according to the member node to be updated, before determining the member to be updated at this time, the method further includes: acquiring a second member change version number which corresponds to the upstream address book and is used for representing the latest version; in the event that the second member change version number does not match the first member change version number, a member to be updated is determined based on a difference between a first range specified by the first member change version number and a second range specified by the second member change version number.

Specifically, for the upstream and downstream address books requested to be synchronized, the server searches for a plurality of second member change version numbers corresponding to the upstream and downstream address books, determines a second member change version number representing the latest version, and compares the received first member change version number with the second member change version number.

And under the condition that the second member change version number is consistent with the first member change version number, the server feeds back to the terminal without updating the upstream and downstream address books when the upstream and downstream address books stored locally by the terminal are the latest version.

In the case where the second member change version number does not coincide with the first member change version number, the server determines a first range specified by the received first member change version number, compares it with a second range specified by the latest second member change version number, and determines a member to be updated based on a difference between the first range and the second range. The member change version number is specified to include a department range and a member range participating in upstream and downstream collaboration in an organization. Correspondingly, the server takes the member indicated by the member node to be updated and the member to be updated determined by the difference between the first range and the second range as the member to be updated at the time according to the member node to be updated.

The member change version number can be used as a running list of each member node change, and the server records the member change version number corresponding to the member node change based on the member nodes stored in the tree structure each time the terminal updates the upstream and downstream address books, so as to form a running list for reference. In the flow table formed by the member change version numbers, each flow record corresponds to one change of the member node, including adding, deleting or changing the position of the node. Each record includes time stamp information, and accordingly, the flow table is arranged according to time sequence.

Illustratively, as shown in fig. 5, for example, in the flow meter, the member change version number 1 corresponds to the change of the division part 1, the member change version number 2 corresponds to the change of the division part 2, the member change version number 3 corresponds to the change of the member number 3, the member change version number 4 corresponds to the change of the member number 4, the member change version number 5 corresponds to the change of the division part 6, and the member change version number 6 corresponds to the change of the member number 5. Each member or department corresponds to an ID (its own ID) and a paramentid (the parent ID corresponding to the node to which it belongs) for indicating the specific indicated upstream and downstream group, department or member.

In the above embodiment, by setting the member change version number, when members participating in any organization in the upstream and downstream address books edit or update the upstream and downstream address books, the latest version can be obtained once, and the subsequent terminal initiates the address book synchronization request to synchronize, so that the efficiency is higher, the update and synchronization are performed according to the comparison of the version numbers, the problem of inconsistent data is avoided, and the accuracy is higher.

In a specific example, the version information may be distinguished by different version numbers according to different situations. Based on the different data update scenarios, the version numbers may include the member change version numbers in the above embodiments, and version numbers reflecting other situations such as upstream and downstream configuration rules, version deletion, etc., as follows

Table 1 shows:

the version number m_multi_version is used for detecting the version number of the change condition of the requester in the internal address book of the organization to which the requester belongs, such as moving an object in the organization, adding and deleting departments and the like.

Since the amount of data may be large at each synchronization, it is necessary to divide into multiple transmissions. Illustratively, the overall data is divided into a plurality of sequences, each sequence corresponding to a version number. In order to record where the current terminal is synchronized, a version number m_hash_version is set, which is used to represent the sequence of the currently pulled address book tree structure in a certain synchronization. Correspondingly, the version number m_hash_version is set to indicate the maximum sequence of the address book tree structure pulled in a certain synchronization.

Wherein, the version number m_last_delete_node_time represents the version number physically deleted at the time of synchronization. This version number may be used for comparison by the server to determine whether to make a full amount of redraw.

The version number m_filter_version is used to characterize the variation of the upstream and downstream configuration rules. The version number m_self_range_version is used for indicating a version number corresponding to a configuration range (department, member) corresponding to an organization to which the requester belongs. The version number m_other_range_version is used to indicate the version number corresponding to the configuration range (department, member) corresponding to the requested organization.

In some embodiments, the method further comprises: responding to an address book creation request initiated by a docking member of an upstream organization, analyzing data carried in the address book creation request to obtain upstream and downstream address book attribute data, upstream and downstream relation mapping data, upstream and downstream organization node trees, member node trees of at least one organization and upstream and downstream configuration rules; and carrying out hierarchical association storage on the upstream and downstream address book attribute data, the upstream and downstream relation mapping data, the upstream and downstream organization node tree, the member node tree of at least one organization and the upstream and downstream configuration rules.

Specifically, the object may be a docking member participating in upstream and downstream collaboration in an upstream organization, and the object may provide an entry for creating an upstream and downstream address book in an application interface that is displayed by the terminal through an application program. By triggering the creation entry, the terminal displays a creation interface of the upstream and downstream address book, wherein the creation interface can be used for the object to edit related data of the upstream and downstream address book, such as upstream and downstream names, upstream and downstream description information and the like. After the terminal acquires the basic data input by the object, generating an address book creation request based on the operation of the object, and sending the address book creation request to the server. The address book creation request comprises basic data of an upstream address book and a downstream address book.

The server receives an address book creation request sent by the terminal, analyzes the address book creation request, extracts data carried in the request, and can be divided into the following steps according to the type of the data: one or more of upstream and downstream address book attribute data, upstream and downstream relationship mapping data, upstream and downstream organization node trees, at least one organization member node tree, upstream and downstream configuration rules, and the like.

The upstream and downstream address book attribute data is used for representing basic information of an upstream and downstream address book, including, but not limited to, one or more of an upstream and downstream identifier, a state, a creator, an organization to which the creator belongs, creation time, modification time, an upstream and downstream architecture root node, an upstream and downstream name, upstream and downstream description information, and the like.

The upstream-downstream relation mapping data are used for representing the mapping relation between the organization and the upstream address book. Illustratively, one or more upstream and downstream address books joined by an organization are represented in the form of a data table, recording one or more of creator, upstream organization initiating invitation, upstream and downstream identification, version number, update time, etc. For another example, one or more organizations added to a certain upstream and downstream address book are represented by a data table.

In the embodiment of the application, the data corresponding to the upstream and downstream address books of different categories are stored and associated in a hierarchical storage mode, for example, in the form of a table and a sub-table. The data of the upstream address book and the downstream address book of different categories can be associated by one or more of upstream identification, downstream identification, organization identification, member identification and the like.

Furthermore, the data corresponding to the upstream address book and the downstream address book are stored in a hierarchical storage mode, the server does not need to store the address book in the organization corresponding to each organization, and only needs to store organization nodes and member nodes which participate in upstream and downstream collaboration, namely an upstream and downstream organization node tree and a member node tree of each organization, and does not need to store the organization architecture of each organization and specific member information. When the upstream address book and the downstream address book are required to be updated, corresponding data are pulled from the internal address book of the organization according to one or more of stored upstream-downstream relation mapping data, upstream-downstream configuration rules and the like, so that the resource occupation of a server is greatly reduced, and a large amount of storage space is saved. Especially, for the very large organization involving tens of thousands or even hundreds of thousands of members, the synchronization efficiency of the upstream address book and the downstream address book is greatly improved.

Based on the upstream and downstream address books, the object may operate in the application to update. Accordingly, in some embodiments, the method further comprises: receiving an update request aiming at an upstream address book and a downstream address book, wherein the update request is initiated by a terminal corresponding to a designated member participating in upstream and downstream collaboration; and updating the locally stored target maintenance information corresponding to the upstream address book and the downstream address book based on the target data carried in the update request.

Specifically, members participating in upstream and downstream collaboration may log in an application through a terminal and view an upstream and downstream address book, where the member range of the upstream and downstream address book that the member can view is a visible range specified by a preset configuration rule. In some embodiments, the authority of each member may be preset, and the member with the authority is a designated member, which may perform editing operations such as adding, deleting, moving, etc. on the upstream address book and the downstream address book; the non-designated member does not have rights. The data generated by the editing operation is target data. The editing operation is, for example, an operation of deleting or adding a department or member participating in the upstream-downstream cooperation, or an operation of moving an existing member to another department. The target data is the data to be synchronized when the subsequent member or other members (which may be members of the same organization or members of other organizations, etc.) initiate the upstream and downstream address book synchronization request.

Accordingly, in response to the update operation of the upstream and downstream address books triggered based on the object, the terminal generates an update request for the operated upstream and downstream address books, and sends the update request to the server. The server receives the update request aiming at the upstream and downstream address books, analyzes the update request, extracts target data carried in the request, and updates target maintenance information locally stored by the server and corresponding to the upstream and downstream address books based on the target data. Therefore, when the follow-up object triggers the synchronization of the upstream address book and the downstream address book and the terminal sends an address book synchronization request, the server can determine the member to be updated according to the difference between the target maintenance information and the historical maintenance information.

In the above embodiment, when the terminal performs the update operation each time, the server updates the target maintenance information according to the update operation, so that when the subsequent terminal initiates the address book synchronization request, the server can determine the data to be updated according to the latest target maintenance information, the accuracy of address book synchronization is higher, and the problem of inconsistent data can be avoided.

In a specific application scenario, efficient upstream and downstream collaboration can be achieved based on the upstream and downstream address book. For example, a conversation may be performed between a member of an upstream organization and a member of a downstream organization without adding friends, or a group conversation may be created and members present in an upstream address book and a downstream address book may be invited to join to communicate and cooperate with each other.

In one scenario, members of the upstream and downstream organizations may initiate or create separate sessions, group sessions, etc. based on the upstream and downstream address books, as shown in fig. 6-8, and a plurality of group sessions may be established based on the upstream and downstream address books, where each group session may include members of the upstream organization, members of one or more downstream organizations, etc. The server sets up the upstream and downstream session identification for the created session, and can support the functions required in the upstream and downstream collaboration for the session carrying the upstream and downstream session identification, such as the read or unread display of the message in the session, the use of group session robots, etc.

In one scenario, members in the upstream and downstream organizations may perform inter-organization collaboration, such as sharing documents, collaboration schedules, shared spaces, online conferences, and sharing applications, based on the upstream and downstream address books, as shown in fig. 9-10. For example, the object may add related members of the downstream organization to authority personnel of the shared document based on the upstream and downstream address books, so as to give the related personnel authority to view, edit, etc. the shared document, thereby realizing efficient communication and collaboration between the upstream and downstream organizations.

In one scenario, based on the upstream and downstream address book, the upstream organization may share application functions to the downstream organization, which may be used in conjunction with the upstream organization after installation. Application functions include, but are not limited to, third party applications, self-building applications, and the like. Illustratively, the step of the upstream organization sharing the application functions to the downstream organization comprises: the object belonging to the upstream organization pulls the application function list with the management authority, initiates application function sharing, and determines the downstream organization to be shared according to the range of the downstream organization to which the object is butted. The server adds the application function to be shared to the application list range of the downstream organization, and configures members and departments participating in the upstream and downstream address books in the downstream organization to the authority personnel range of the application function. The shared application can be managed, updated, etc. by both the subsequent upstream and downstream organizations.

In the upstream and downstream address books displayed by the terminal through the application program, the management operation of the upstream and downstream address books can be realized based on different triggering modes. Management operations include, but are not limited to, one or more of synchronizing, deleting, and modifying rights, etc. For example, in the downstream organization list of the upstream and downstream address books presented by the application interface, the object may trigger the management operation of the selected downstream organization through operations such as touching, clicking, sliding, dragging, and long pressing. For another example, in a specific participating department and member list in an organization in the upstream and downstream address book presented by the application interface, the object may trigger the management operation of the application program on the selected department or member.

Illustratively, as shown in fig. 11, the object triggers the new upstream and downstream address book, and the terminal displays the created upstream and downstream address book through the application program. The names of the upstream and downstream address books can be modified by the object, and the upstream and downstream address books can be deleted according to the operation of the object. As shown in fig. 12, after the upstream and downstream address book is created, the object may also join by inviting the downstream organization. In order to facilitate efficient collaboration and fine management, in the upstream and downstream address books, each downstream organization may also be grouped to form a plurality of upstream and downstream groups.

In some embodiments, when the object creates the upstream and downstream address book, the terminal may display the internal address book of the organization to which the object belongs, so that the object may select a department or a member added to the upstream and downstream address book. In other embodiments, after the creation of the upstream and downstream address book is completed, the terminal responds to the triggering operation of the object to display the internal address book of the organization to which the object belongs, so that the object can select a part or a member added into the upstream and downstream address book. As shown in fig. 13, for a department or member that has joined an upstream and downstream address book in an organization to which the object belongs, the object may also trigger a delete operation to manage the department or member, as shown in fig. 14.

In a specific example, it is assumed that an upstream address book and a downstream address book include an upstream organization, a downstream organization a and a downstream organization B in an upstream and downstream organization node tree. For the downstream organization a, the own organization internal address book includes a department 1, a department 2 and a member 1, wherein the department 1 includes a member 2 and a member 3. Wherein department 1 and member 1 participate in the upstream and downstream collaboration for the upstream and downstream address book. Accordingly, the member node tree of the downstream organization a includes a department 1 and a member 1, and the department 1 further includes a member 2 and a member 3.

When the method is used for establishing, a terminal responds to an address book establishment request initiated by a butt joint member of an upstream organization, after receiving the address book establishment request, a server analyzes data carried in the address book establishment request to obtain upstream and downstream address book attribute data, upstream and downstream relation mapping data, upstream and downstream organization node trees, at least one organization member node tree and upstream and downstream configuration rules, and the data are stored in a hierarchical association mode. The stored data can be updated and maintained in real time later.

When the terminal initiates an update request, the server receives the update request for the upstream and downstream address books, updates the locally stored target maintenance information corresponding to the upstream and downstream address books in the target data carried in the update request, and then determines the data to be updated based on the target maintenance information for the terminal to update the upstream and downstream address books in response to the address book synchronization request initiated by the terminal. And when the server performs each updating operation, the server records, and forms the updating operation of each time into a running water for subsequent comparison and checking, so that the accuracy and the integrity of the synchronization of the upstream address book and the downstream address book are prevented from being influenced due to missing data.

When the terminal initiates an address book synchronization request, the server receives the address book synchronization request aiming at the upstream and downstream address books, determines data to be updated according to target maintenance information corresponding to the upstream and downstream address books, and feeds the data to be updated back to the terminal. After receiving the data to be updated, the terminal updates the stored upstream and downstream address books based on the data to be updated, thereby realizing the synchronization of the upstream and downstream address books.

In a specific example, as shown in fig. 15A, the terminal sends a version number corresponding to the locally stored upstream and downstream address book to the server, and when the server determines the data to be updated and feeds back the data to the terminal, the server feeds back the latest version number together, and when the terminal is synchronized next time, the terminal sends the version number to the server again, and the server compares the received version number from the terminal with the version number stored by the server itself, so as to determine the data to be updated. Illustratively, the server invokes the address book synchronization service by invoking an address book synchronization interface CGI (Common Gateway Interface, public gateway interface). The address book synchronization service comprises an upstream service and a downstream service, wherein the upstream service and the downstream service correspond to data of an upstream organization node tree and a downstream organization node tree stored by a server. The address book synchronization service also includes an architecture service that corresponds to the data of the organization's member node tree stored by the server. As shown in fig. 15B, when determining the changed member node, the server implements the upstream and downstream services, the architecture service, and the account service by calling the address book synchronization interface according to the stream data. Wherein the account service corresponds to specific member information of each member stored by the server.

In one specific example, the types of version numbers include one or more of a member change version number, a delete version number, a sync tile version number, a docking rule version number, and a configuration range version number. When a terminal performs a deletion operation on an upstream address book and a downstream address book, for example, the server can compare the latest version number stored by the server with the version number uploaded by the terminal to determine the version to be synchronized and whether full synchronization is required. The synchronous slice version number is used for indicating the maximum slice of the data to be updated fed back each time, and the slice is used for indicating the size of the data quantity. For example, X copies of data need to be transferred in one update, and only 1/X of data can be transferred per transfer. Therefore, according to the synchronization fragment version number, the progress of the synchronization of the upstream address book and the downstream address book can be determined. The version number of the docking rule is used for comparing whether the docking rule for the upstream address book and the downstream address book is changed. The configuration scope version number is used for comparing whether the scope of the members participating in the upstream and downstream collaboration changes.

The embodiment of the application can provide high-efficiency cross-organization cooperative communication, especially for large-scale cooperation and conditions involving huge organizations and members, can realize high-efficiency synchronization of the upstream address book and the downstream address book, and improves the accuracy and the integrity of the synchronization of the upstream address book and the downstream address book.

It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order 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 in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiments of the present application further provide a cross-fabric communication method, and in some embodiments, the method is applied to a terminal to perform explanation, as shown in fig. 16, including:

step S1602, the upstream and downstream management interfaces are presented in the organization communication application.

Specifically, the terminal displays the upstream address book and the downstream address book to the object through an application interface of the organization communication application. The object can view the upstream and downstream address books, or edit the upstream and downstream address books, etc. The application interface comprises an upstream and a downstream management interface, and the object can trigger synchronous operation on the upstream and the downstream address books in the upstream and the downstream management interfaces.

In one exemplary scenario, at least one interactive element is exposed in the upstream and downstream management interfaces, which can be triggered by an object to cause an application to execute logic encapsulated in a configuration file corresponding to the interactive element. The interactive elements are, for example, virtual buttons, icons, links, or the like.

Step S1604, in response to the synchronization operation for the upstream and downstream address books initiated in the upstream and downstream management interfaces, sends an address book synchronization request to the server.

Specifically, after triggering the synchronization operation on the upstream and downstream address books in the upstream and downstream management interfaces, the terminal responds to the initiated synchronization operation on the upstream and downstream address books, generates an address book synchronization request, and sends the address book synchronization request to the server. An exemplary embodiment of the present invention provides a method for synchronizing an address book, in which an interactive element prompting an object to synchronize is displayed in an upstream and downstream management interface, when the object triggers the interactive element, a synchronization operation for an upstream and downstream address book is triggered, and a terminal responds to the synchronization operation and sends an address book synchronization request to a server.

In step S1606, the data to be updated fed back by the server in response to the address book synchronization request is received, the data to be updated is determined based on the target maintenance information corresponding to the upstream and downstream address books, and at least includes member information obtained from the organization architecture tree to which the member to be updated belongs, where the target maintenance information includes at least an upstream and downstream organization node tree, at least one organization member node tree, and upstream and downstream configuration rules.

After receiving the address book synchronization request, the server determines an upstream address book and a downstream address book to be synchronized, which correspond to the upstream and downstream identifiers, according to the upstream and downstream identifiers in the address book synchronization request. And searching the corresponding stored data for the upstream and downstream address books to be synchronized by the server, and determining the target maintenance information corresponding to the upstream and downstream address books. The target maintenance information may be based on synchronization operations triggered by other objects and obtain updated data.

The server searches a target configuration rule matched with the request initiator based on the stored upstream and downstream configuration rules, and acquires data to be updated corresponding to the request initiator according to the upstream and downstream organization node tree and at least one organization member node tree and the target configuration rule. Specifically, the server traverses the upstream and downstream organization node trees, detects organization nodes in the upstream and downstream organization node trees, detects each organization node in the upstream and downstream organization node trees respectively, acquires a member node tree corresponding to each organization node, and detects a member node in the member node tree, so as to determine data to be updated. The specific steps are referred to the foregoing embodiments, and are not repeated here.

After determining the data to be updated, the server responds to an address book synchronization request initiated by the terminal and feeds back the data to be updated to the terminal so that the terminal can synchronize and update the upstream address book and the downstream address book based on the data to be updated.

Step S1608, displaying the upstream and downstream address books updated by the data to be updated, wherein the upstream and downstream address books are used for realizing cross-organization communication.

Specifically, after receiving data to be updated sent by the server, the terminal updates the upstream address book and the downstream address book based on the data to be updated. For example, the method includes adding and deleting downstream organization nodes in the upstream and downstream address book based on data to be updated, adding and deleting or moving member nodes of the organization, or updating member information corresponding to specific member nodes, and the like. After updating the upstream and downstream address books, the terminal displays the updated upstream and downstream address books through an application interface of the organization communication application. Members of different organizations can conveniently and rapidly cooperate across the organization upstream and downstream based on the upstream and downstream address books.

According to the above-mentioned cross-organization communication method, the management interface of the upstream address book and the downstream address book is displayed through the organization communication application, and the address book synchronization request triggered by the object is sent to the server, so that the server can determine the incrementally updated data according to the request; after receiving the incremental updated data, the terminal updates the locally stored upstream and downstream address books and displays the latest upstream and downstream address books. Therefore, the terminal does not need to store the full amount of upstream and downstream address books again by updating in an increment synchronization mode, the synchronization efficiency of the upstream and downstream address books is higher, the stability is higher, and the problem of inconsistent data is avoided.

In some embodiments, the method further comprises: responding to a cross-organization communication operation initiated in an organization communication application, and selecting at least one target object from the displayed upstream and downstream address books; a session interface corresponding to a group of at least one target object is presented, the session interface for cross-fabric communication.

Based on the upstream and downstream address book displayed by the organization communication application, members of each organization participating in upstream and downstream collaboration can initiate cross-organization communication so as to realize quick trench-through. Wherein the cross-fabric communication operations include, but are not limited to, individual sessions, group sessions, and the like.

And triggering the cross-organization communication operation by the object in an application interface displayed by the terminal through the organization communication application, and selecting one or more target objects for communication through the cross-organization communication operation by the object. The target object may be a member belonging to the same organization as the object, or may be a member of another organization.

Specifically, the terminal responds to the cross-tissue communication operation and selects at least one target object from the displayed upstream and downstream address books. Under the condition that one target object is selected, the terminal establishes a session between the current object and the target object, and displays a session interface of the session for the two parties to communicate. Under the condition that two or more target objects are selected, the terminal establishes a group session of a group formed by the current object and a plurality of target objects together, and displays a session interface corresponding to the group session so as to enable multi-party inter-organization communication.

As further shown in fig. 6-8, a plurality of group sessions are established based on the upstream address book, and each group session may include members of an upstream organization and members of one or more downstream organizations. The server sets up the upstream and downstream session identification for the created session, and can support the functions required in the upstream and downstream collaboration for the session carrying the upstream and downstream session identification, such as the read or unread display of the message in the session, the use of group session robots, etc.

In the above embodiment, by using the session function provided by the upstream and downstream address books, the members of each organization (for example, the upstream organization and the downstream organization) participating in the upstream and downstream collaboration can perform the cross-organization communication, so that the quick and convenient cross-organization communication can be realized without adding complicated steps such as friends, and the efficiency of the upstream and downstream collaboration is higher.

In some embodiments, the method further comprises: responding to a cross-organization collaboration operation initiated in an organization communication application, and displaying a task collaboration page corresponding to the cross-organization collaboration operation; and responding to the object selection operation triggered by the task collaboration page, and adding at least one target object selected by the object selection operation into the task to be collaborated.

Based on the upstream and downstream address book displayed by the organization communication application, members of each organization participating in upstream and downstream collaboration can initiate a collaboration task across organizations to achieve efficient collaboration. The method comprises the steps that an object triggers cross-organization cooperation operation in an application interface displayed by a terminal through an organization communication application, and the cross-organization cooperation operation is used for indicating the object to perform cross-organization cooperation with other organized objects. Wherein the cross-organization collaboration includes one or more of a cross-organization conference, a cross-organization calendar, and a cross-organization storage space.

Specifically, the terminal responds to a cross-organization collaboration operation initiated by an object, a task collaboration page is displayed, and a plurality of different types of cross-organization collaboration functions are displayed in the task collaboration page. For the cross-organization collaboration function, the object selects one or more target objects based on the upstream and downstream address books, and accordingly, the terminal responds to object selection operation triggered by the task collaboration page to add the target objects to the tasks to be collaborated.

As shown in fig. 9 to 10, for example. For example, the object may initiate tasks of cross-organizational meetings, cross-organizational schedules, and cross-organizational storage waiting for collaboration based on upstream and downstream address books. Taking a cross-organization conference as an example, based on one or more target objects selected by the objects, the terminal responds to the object selection operation to add the selected one or more target objects into the cross-organization conference so as to enable members of a multiparty organization to carry out cross-organization communication.

In the embodiment, by the cross-organization task cooperation function provided based on the upstream and downstream address books, members of each organization participating in the upstream and downstream cooperation can conveniently and quickly perform cross-organization cooperation, and the upstream and downstream cooperation efficiency is higher.

In some embodiments, the method further comprises: responding to an application sharing operation initiated in the organization communication application, and displaying an application sharing interface under the condition that an object currently logged in the organization communication application is a management object; acquiring an application to be shared through an application sharing interface, and displaying at least one target object selected based on an upstream address book and a downstream address book through the application sharing interface; and responding to the sharing confirmation operation, and sharing the application to be shared to the target object.

Based on the upstream and downstream address book displayed by the organization communication application, members of each organization participating in upstream and downstream collaboration can initiate application sharing so as to realize inter-organization collaboration office. For example, an upstream organization may share a third party application or a self-built application to a downstream enterprise for collaborative use by both parties.

In some embodiments, the management authority of each member may be preset, the member with the management authority is a management object, and the management object may perform an application sharing operation; the non-management object does not have management rights. The application sharing operation is used for appointing to carry out corresponding application sharing on the selected target object.

Specifically, the management object triggers an application sharing operation in an application sharing interface displayed by the terminal through the organization communication application. One or more sharable applications are displayed in the application sharing interface. And the terminal responds to the application sharing operation and displays an application sharing interface for the management object to select the application to be shared. After the management object selects the application to be shared, the terminal acquires one or more target objects selected by the management object based on the application sharing interface and displays the target objects so as to confirm the management object. Wherein the target object is a member of other organizations. And under the condition that the management object confirms, the terminal responds to the sharing confirmation operation to share the application to be shared to the target object. Thus, the application can be shared to members of other organizations.

In some embodiments, the terminal responds to the sharing confirmation operation to share the application to be shared to the target object, that is, the terminal sends the related information of the application to be shared to the server, and the server adds the application to be shared to the application in the upstream and downstream address book viewed by the target object.

In some embodiments, the applications governed by the management rights of the individual management objects may be different. For example, the management object a may perform application sharing on the applications 1 to 3, and the management object B may perform application sharing on the applications 4 to 8, or the like. Based on the difference of the management objects, in an application sharing interface displayed by the terminal through the organization communication application, one or more sharable applications displayed are also different.

For example, the management object of the upstream organization may acquire an application with management authority, and determine an application to be shared. After determining the application to be shared, the terminal displays an application sharing interface based on the upstream and downstream address books through the application program so that the management object can select a downstream organization or a department or member of the downstream organization, namely a target object. Under the condition that the management object confirms, the terminal responds to the sharing confirmation operation, relevant information of the application to be shared is sent to the server, the server writes the application to be shared into an application list of a downstream organization, and members and departments participating in an upstream address book and a downstream address book in the downstream organization are configured in the usable range of the application. Members with management rights in the subsequent upstream organization and downstream organization can add and delete the application and manage the usable range of the application.

In the embodiment, through the application sharing function provided based on the upstream address book and the downstream address book, application sharing and collaborative office can be performed between organizations, so that cross-organization collaboration is realized conveniently and rapidly.

In a specific scene, an object views the upstream and downstream address books through an application interface of an organization communication application, and realizes the synchronization and update of the upstream and downstream address books by triggering a synchronization operation in the upstream and downstream management interfaces. For example, one or more interactive elements are displayed in the upstream and downstream management interfaces, and the object triggers the interactive elements to trigger the synchronization of the upstream and downstream address books. After triggering the synchronization operation on the upstream and downstream address books in the upstream and downstream management interfaces, the terminal responds to the initiated synchronization operation on the upstream and downstream address books, generates an address book synchronization request and sends the address book synchronization request to the server. The server responds to the address book synchronization request to determine the data to be updated, and returns the data to the terminal so that the terminal can update the locally stored upstream and downstream address books.

In a specific example, the terminal displays the upstream and downstream management interfaces through the organization communication application, so that the object can perform management operation on the upstream and downstream address books on the upstream and downstream management interfaces. For example, the object may trigger address book synchronization based on the upstream and downstream management interfaces, and the terminal initiates an address book synchronization request and updates the locally stored upstream and downstream address books based on the data to be updated returned by the server. Based on the upstream and downstream address book provided by the organization communication application, the object may initiate a cross-organization communication operation to enable cross-organization communication, such as group sessions, etc.; cross-organization collaboration operations may also be initiated to achieve task collaboration involving multiple parties, such as sharing documents, etc.; application sharing operations may also be initiated to achieve collaborative collaboration of multiple parties.

Based on the same inventive concept, the embodiment of the application also provides an address book management device for realizing the address book management method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation of one or more embodiments of the address book management device provided below may refer to the limitation of the address book management method described above, and will not be repeated here.

In some embodiments, as shown in fig. 17, there is provided an address book management apparatus 1700, including: a receiving module 1701, a determining module 1702, an obtaining module 1703 and a feedback module 1704. Wherein:

and the receiving module 1701 is used for receiving an address book synchronization request for the upstream and downstream address books initiated by the terminal.

The determining module 1702 is configured to determine target maintenance information corresponding to the upstream and downstream address book, where the target maintenance information at least includes an upstream and downstream organization node tree, at least one organization member node tree, and an upstream and downstream configuration rule.

The determining module 1702 is further configured to determine a target configuration rule that matches a request initiator of the address book synchronization request based on the upstream and downstream configuration rules.

And the obtaining module 1703 is configured to obtain data to be updated corresponding to the request initiator according to the upstream and downstream organization node tree and at least one organization member node tree and according to the target configuration rule.

And the feedback module 1704 is configured to feed back the data to be updated to the terminal, so as to instruct the terminal to update the upstream address book and the downstream address book specified by the address book synchronization request based on the data to be updated.

In some embodiments, the upstream and downstream organization node trees characterize upstream and downstream relationships between the upstream organization and at least one downstream organization, the organization's member node trees characterize ranges of participating members of each organization that participate in upstream and downstream collaboration, and the upstream and downstream configuration rules include interfacing relationships between members in the upstream organization and downstream organization, and visible relationships between different members of different organizations.

In some embodiments, the address book synchronization request carries first version information, and the target maintenance information corresponds to second version information. The acquisition module is also used for determining the current latest second version information; determining history maintenance information corresponding to the first version information in the case that the second version information is inconsistent with the first version information; and determining data to be updated, which is matched with a request initiator of the address book synchronization request, based on the difference between the target maintenance information and the history maintenance information.

In some embodiments, the obtaining module is further configured to determine an organization node to be updated according to an upstream and downstream configuration rule based on a difference between an upstream and downstream organization node tree included in each of the target maintenance information and the history maintenance information; determining member nodes to be updated according to upstream and downstream configuration rules based on differences between member node trees of at least one organization included in each of the target maintenance information and the history maintenance information; determining the member to be updated at this time at least according to the member node to be updated, and acquiring member information of the member to be updated from an organization architecture tree to which the member to be updated belongs; the organization node to be updated, the member node to be updated and the member information together form the data to be updated.

In some embodiments, a first member change version number corresponding to the requestor is included in the first version information. The acquisition module is also used for acquiring a second member change version number which corresponds to the upstream address book and the downstream address book and represents the latest version; in the event that the second member change version number does not match the first member change version number, a member to be updated is determined based on a difference between a first range specified by the first member change version number and a second range specified by the second member change version number. And the acquisition module is also used for determining the member to be updated at the time according to the member node to be updated and the member to be updated determined by the difference between the first range and the second range.

In some embodiments, the apparatus further includes a creating module, configured to, in response to an address book creation request initiated by a docking member of an upstream organization, parse data carried in the address book creation request to obtain upstream and downstream address book attribute data, upstream and downstream relationship mapping data, upstream and downstream organization node trees, at least one organization member node tree, and upstream and downstream configuration rules; and carrying out hierarchical association storage on the upstream and downstream address book attribute data, the upstream and downstream relation mapping data, the upstream and downstream organization node tree, the member node tree of at least one organization and the upstream and downstream configuration rules.

In some embodiments, the apparatus further includes an update module, configured to receive an update request for an upstream address book, where the update request is initiated by a terminal corresponding to a designated member participating in upstream-downstream collaboration; and updating the locally stored target maintenance information corresponding to the upstream address book and the downstream address book based on the target data carried in the update request.

All or part of the modules in the address book management device can be realized by software, hardware and 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.

Based on the same inventive concept, the embodiment of the application also provides a cross-tissue communication device for realizing the cross-tissue communication method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitations in one or more embodiments of the cross-organization communication device provided below may be referred to above as limitations of the cross-organization communication method, and will not be described herein.

In some embodiments, as shown in fig. 18, there is provided a cross-fabric communication device 1800 comprising: a presentation module 1801, a transmission module 1802, and a reception module 1803. Wherein:

a presentation module 1801 for presenting the upstream and downstream management interfaces in an organization communication application.

The sending module 1802 is configured to send an address book synchronization request to a server in response to a synchronization operation for an upstream address book and a downstream address book initiated in an upstream and downstream management interface.

The receiving module 1803 is configured to receive data to be updated fed back by the server in response to the address book synchronization request, where the data to be updated is determined based on target maintenance information corresponding to the upstream and downstream address books, and the target maintenance information at least includes an upstream and downstream organization node tree, at least one member node tree of the organization, and an upstream and downstream configuration rule.

The display module 1801 is further configured to display an upstream address book and a downstream address book updated by the data to be updated, where the upstream address book and the downstream address book are used to implement cross-fabric communication.

In some embodiments, the apparatus further comprises a communication module for selecting at least one target object from the presented upstream and downstream address book in response to a cross-fabric communication operation initiated in the fabric communication application; a session interface corresponding to a group of at least one target object is presented, the session interface for cross-fabric communication.

In some embodiments, the apparatus further includes a collaboration module configured to, in response to a cross-organization collaboration operation initiated in the organization communication application, present a task collaboration page corresponding to the cross-organization collaboration operation; and responding to the object selection operation triggered by the task collaboration page, and adding at least one target object selected by the object selection operation into the task to be collaborated.

In some embodiments, the apparatus further includes a sharing module, configured to respond to an application sharing operation initiated in the organization communication application, and display an application sharing interface when an object currently logged into the organization communication application is a management object; acquiring an application to be shared through an application sharing interface, and displaying at least one target object selected based on an upstream address book and a downstream address book through the application sharing interface; and responding to the sharing confirmation operation, and sharing the application to be shared to the target object.

The various modules in the above-described cross-fabric communication device may be implemented in whole or in part by software, hardware, and combinations 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 some embodiments, a computer device is provided, which may be a server or a terminal in the foregoing embodiments. In this embodiment, taking a computer device as a server as an example, the internal structure of the computer device may be as shown in fig. 19. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. 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 equipment is used for storing data corresponding to the upstream address book and the downstream address book. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by the processor, implements a method for address book management, or a method for cross-fabric communication.

It will be appreciated by those skilled in the art that the structure shown in fig. 19 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, 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 some embodiments, 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 some embodiments, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.

In some embodiments, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

It should be noted that, the information (including but not limited to member information, account information, etc.) and the data (including but not limited to data for analysis, stored data, displayed data, etc.) of the upstream and downstream address books related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.

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, database, or other medium used in the various 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, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

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 only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. An address book management method, which is characterized by comprising the following steps:

2. The method of claim 1, wherein the upstream and downstream organization node trees characterize upstream and downstream relationships between an upstream organization and at least one downstream organization, wherein the organization's member node trees characterize ranges of participating members of each organization participating in upstream and downstream collaboration, and wherein the upstream and downstream configuration rules include interfacing relationships between members in the upstream organization and downstream organization, and visible relationships between different members of different organizations.

3. The method of claim 1, wherein the determining, based on the target maintenance information, data to be updated that matches the request originator comprises:

determining a target configuration rule matched with a request initiator of the address book synchronization request based on the upstream and downstream configuration rules;

And obtaining data to be updated corresponding to the request initiator according to the upstream and downstream organization node tree and the member node tree of the at least one organization and the target configuration rule.

4. The method of claim 1, wherein the address book synchronization request carries a first version information, and the target maintenance information corresponds to a second version information;

the determining, based on the target maintenance information, data to be updated that matches the request initiator includes:

determining the current latest second version information;

determining history maintenance information corresponding to the first version information in the case that the second version information is inconsistent with the first version information;

and determining data to be updated, which is matched with a request initiator of the address book synchronization request, based on the difference between the target maintenance information and the history maintenance information.

5. The method of claim 4, wherein determining data to be updated that matches the request originator of the address book synchronization request based on the difference between the target maintenance information and the history maintenance information, comprises:

determining an organization node to be updated according to the upstream and downstream configuration rules based on the difference between upstream and downstream organization node trees respectively included in the target maintenance information and the history maintenance information;

Determining member nodes to be updated according to the upstream and downstream configuration rules based on the difference between the member node trees of at least one organization included in each of the target maintenance information and the history maintenance information;

determining the member to be updated at the time at least according to the member node to be updated, and acquiring member information of the member to be updated from an organization architecture tree to which the member to be updated belongs; the organization node to be updated, the member node to be updated and the member information together form the data to be updated.

6. The method of claim 5, wherein the first version information includes a first member change version number corresponding to the requestor, and wherein the method further includes, before determining the member to be updated at this time based at least on the member to be updated node:

acquiring a second member change version number which corresponds to the upstream address book and is used for representing the latest version;

determining a member to be updated based on a difference between a first range specified by the first member change version number and a second range specified by the second member change version number, if the second member change version number is inconsistent with the first member change version number;

The step of determining the member to be updated at this time at least according to the member node to be updated comprises the following steps:

and determining the member to be updated at this time according to the member node to be updated and the member to be updated determined by the difference between the first range and the second range.

7. The method according to any one of claims 1 to 6, further comprising:

responding to an address book creation request initiated by a docking member of an upstream organization, analyzing data carried in the address book creation request to obtain upstream and downstream address book attribute data, upstream and downstream relation mapping data, upstream and downstream organization node trees, at least one organization member node tree and upstream and downstream configuration rules;

and carrying out hierarchical association storage on the upstream and downstream address book attribute data, the upstream and downstream relation mapping data, the upstream and downstream organization node tree, the member node tree of at least one organization and the upstream and downstream configuration rules.

8. The method according to any one of claims 1 to 6, further comprising:

receiving an update request aiming at the upstream and downstream address books, wherein the update request is initiated by a terminal corresponding to a designated member participating in upstream and downstream collaboration;

And updating the locally stored target maintenance information corresponding to the upstream and downstream address books based on the target data carried in the update request.

9. A method of cross-fabric communication, the method comprising:

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

responding to a cross-organization communication operation initiated in the organization communication application, and selecting at least one target object from the displayed upstream and downstream address books;

A session interface corresponding to a group of the at least one target object is presented, the session interface for cross-fabric communication.

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

responding to a cross-organization collaboration operation initiated in the organization communication application, and displaying a task collaboration page corresponding to the cross-organization collaboration operation;

and responding to the object selection operation triggered by the task collaboration page, and adding at least one target object selected by the object selection operation into the task to be collaborated.

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

responding to application sharing operation initiated in the organization communication application, and displaying an application sharing interface under the condition that an object currently logged in the organization communication application is a management object;

acquiring an application to be shared through the application sharing interface, and displaying at least one target object selected based on an upstream address list and a downstream address list through the application sharing interface;

and responding to the sharing confirmation operation, and sharing the application to be shared to the target object.

13. An address book management apparatus, comprising:

14. A cross-fabric communication device, the device comprising:

15. 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 12 when the computer program is executed.

16. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 12.

17. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any one of claims 1 to 12.