User blacklist management method and system based on multi-level deployment architecture

Abstract

The invention discloses a user blacklist management method and system based on a multi-level deployment architecture, and relates to the technical field of information. The method comprises the following steps that a multi-stage communication system containing a user organization is created, and different types of communication software and corresponding user management services and file transmission services are deployed in nodes of each stage in the multi-stage communication system; formulating a user blacklist and communication strategy information corresponding to each level of node in the multi-level communication system based on the user management service; user blacklists and communication strategy information of all levels of nodes are summarized upwards level by level to a center node for collection and combination based on file transmission service; and distributing the collected and combined user blacklist and communication strategy information to each level of node for updating step by step based on a file transmission service. According to the invention, user blacklist management and information transmission of a multi-level deployment architecture are realized, and unnecessary interference to work of a specific user group is avoided.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and more specifically to a user blacklist management method and system based on a multi-level deployment architecture. Background Art

[0002] In the current instant messaging software deployed with multi-level architecture, information exchange between users is mostly done by selecting the target user through organizational structure selection and username query. As the user group expands, information interaction becomes more frequent, which inevitably interferes with the work of specific user groups. Usually, in order to avoid such interference, it can be achieved by blocking on the client, but it requires users to operate by themselves and cannot be effectively deployed in a unified manner.

[0003] Therefore, how to solve the problem of information controllability under a multi-level deployment architecture is an urgent problem to be solved in this field. Summary of the invention

[0004] In view of this, the present invention provides a user blacklist management method and system based on a multi-level deployment architecture, which are used to at least solve some of the technical problems in the background technology.

[0005] In order to achieve the above object, the present invention adopts the following technical solution:

[0006] On one hand, the present invention discloses a user blacklist management method based on a multi-level deployment architecture, comprising the following steps:

[0007] Creating a multi-level communication system including user organizations, wherein each level of nodes in the multi-level communication system is deployed with different types of communication software, as well as corresponding user management services and file transfer services;

[0008] Formulate user blacklists and communication strategy information corresponding to nodes at each level in a multi-level communication system based on user management services;

[0009] Based on the file transfer service, the user blacklist and communication policy information of nodes at all levels are aggregated and merged to the central node step by step;

[0010] Based on the file transfer service, the collected and merged user blacklist and communication policy information are distributed to nodes at all levels for updating.

[0011] Further, in one embodiment, formulating user blacklists and communication strategy information corresponding to nodes at each level in a multi-level communication system based on a user management service specifically includes the following steps:

[0012] Utilize the user management service to set each user in each level of node as a privileged user or a blacklist user, where the privileged user can have one-way communication with any other user except himself; different blacklist users set privileged communication tools or communication methods with which other users can have one-way communication, and set the corresponding reply content of the blacklist user.

[0013] Further, in another embodiment, formulating user blacklists and communication strategy information corresponding to nodes at each level in a multi-level communication system based on a user management service specifically includes the following steps:

[0014] Utilize the user management service to set all users under the same organization in each level of node as privileged users or blacklist users at the same time, where the privileged user can have one-way communication with any other user except himself; different blacklist users set privileged communication tools or communication methods with which other users can have one-way communication, and set the corresponding reply content of the blacklist user.

[0015] Furthermore, based on the file transfer service, the user blacklist and communication strategy information of nodes at all levels are aggregated to the central node step by step, specifically including the following steps:

[0016] Step 101: The user management service of the last node generates a data file of the blacklist and communication strategy information of the node every day and uploads it to the file transfer service of the node;

[0017] Step 102: The upper node starts to use the user management service to pull the latest uploaded data files from the file transfer service of each subordinate node from the bottom to the top every half an hour, stores them in the local database, aggregates the data, merges them with the blacklist and communication policy data of the node, generates a new data file, and uploads it to the file transfer service of the node;

[0018] Step 103: The primary central node finally pulls the latest uploaded data files from the file transfer services of each subordinate secondary node, stores them in the local database to form a complete blacklist and communication policy information, generates a data file with the merged data, and uploads it to the file transfer service of this node.

[0019] Furthermore, based on the file transfer service, the collected and merged user blacklist and communication strategy information are distributed to nodes at all levels for updating, which specifically includes the following steps:

[0020] Step 201: The lower-level nodes pull the complete blacklist and communication policy data files from the upper-level nodes at intervals of half an hour from top to bottom, store them in the local database, and upload them to the file transfer service of the node at the same time;

[0021] Step 202: The last node pulls the complete blacklist and communication strategy data file from the upper node and stores it in the local database.

[0022] Furthermore, in the process of pulling the complete blacklist and communication policy data files from the upper node, each user of the node follows the following steps:

[0023] Step 301: Using the communication software to call the user management service interface, query which users the currently logged-in user can communicate with;

[0024] Step 302: Use the user management service to determine whether the currently logged-in user is a privileged user. If so, return to the list of all users in the entire network and go to step 304. If not, go to step 303.

[0025] Step 303: define and calculate set S1 as: all whitelist users;

[0026] Define and calculate the set S2 as: users in the blacklist who can communicate with the current communication software;

[0027] Define and calculate set S3 as: users in the blacklist who support reply and have actively communicated with the current user within n days;

[0028] Returns the union of set S1, set S2, and set S3, that is, returns the list of users with which the current user can communicate using the current communication software;

[0029] Step 304: The communication software receives and displays the communicable users, and then allows or blocks the sending and receiving of messages.

[0030] Another aspect of the present invention discloses a user blacklist management system based on a multi-level deployment architecture, comprising:

[0031] A multi-level communication system including user organizations, wherein each level of nodes in the multi-level communication system is deployed with different types of communication software, as well as corresponding user management services and file transfer services;

[0032] The multi-level communication system uses user management services to formulate user blacklists and communication strategy information corresponding to nodes at each level;

[0033] Use file transfer services to aggregate user blacklists and communication policy information of nodes at all levels to the central node for aggregation and merging;

[0034] The file transfer service is used to distribute the collected and merged user blacklist and communication policy information to nodes at all levels for updating.

[0035] Preferably, in a specific embodiment, the user blacklist and communication strategy information corresponding to each level of nodes are formulated using the user management service in the following manner:

[0036] The user management service is used to set each user in each level of node as a privileged user or a blacklist user, and privileged communication tools or communication methods that can be used to communicate with different blacklist users are set.

[0037] Preferably, in another specific embodiment, the user blacklist and communication strategy information corresponding to each level of nodes are formulated by using the user management service in the following manner:

[0038] Utilize the user management service to set all users under the same organization in each level of node as privileged users or blacklist users at the same time, and set privileged communication software or communication methods for communicating with different blacklist users.

[0039] Preferably, the user blacklist and communication strategy information of nodes at all levels are aggregated and merged to the central node by using the file transfer service, which specifically includes the following steps:

[0040] Step 101: The user management service of the last node generates a data file of the blacklist and communication strategy information of the node every day and uploads it to the file transfer service of the node;

[0041] Step 102: The upper node starts to use the user management service to pull the latest uploaded data files from the file transfer service of each subordinate node from the bottom to the top every half an hour, stores them in the local database, aggregates the data, merges them with the blacklist and communication policy data of the node, generates a new data file, and uploads it to the file transfer service of the node;

[0042] Step 103: The primary central node finally pulls the latest uploaded data files from the file transfer services of each subordinate secondary node, stores them in the local database to form a complete blacklist and communication policy information, generates a data file with the merged data, and uploads it to the file transfer service of this node.

[0043] Preferably, the user blacklist and communication policy information collected and merged are distributed to each node level for updating by using a file transfer service, which specifically includes the following steps:

[0044] Step 201: The lower-level nodes pull the complete blacklist and communication policy data files from the upper-level nodes at intervals of half an hour from top to bottom, store them in the local database, and upload them to the file transfer service of the node at the same time;

[0045] Step 202: The last node pulls the complete blacklist and communication strategy data file from the upper node and stores it in the local database.

[0046] Preferably, in the process of pulling the complete blacklist and communication policy data file from the upper node, each user of the node follows the following steps:

[0047] Step 301: Using the communication software to call the user management service interface, query which users the currently logged-in user can communicate with;

[0048] Step 302: Use the user management service to determine whether the current user is a privileged user. If the current user is a privileged user, return a list of all users in the entire network and go to step 304. If the current user is not a privileged user, go to step 303.

[0049] Step 303: define and calculate set S1 as: all whitelist users;

[0050] Define and calculate the set S2 as: users in the blacklist who can communicate with the current communication software;

[0051] Define and calculate set S3 as: users in the blacklist who support reply and have actively communicated with the current user within n days;

[0052] Returns the union of set S1, set S2, and set S3, that is, returns the list of users with which the current user can communicate using the current communication software;

[0053] Step 304: The communication software receives and displays the communicable users, and then allows or blocks the sending and receiving of messages.

[0054] It can be seen from the above technical solutions that, compared with the prior art, the present invention discloses a user blacklist management method and system based on a multi-level deployment architecture, which has the following beneficial effects:

[0055] (1) The present invention proposes to use user management services to uniformly set information filtering policies, which can be set according to the organizational dimension or the user dimension. After the setting is completed, it can be applied to multiple communication tools to avoid repeated settings and inconsistent policies.

[0056] (2) The present invention utilizes the user management service to provide a data interface to enable the communication software to query user information. In order to reduce the access pressure of the user management service, a special file transfer service is used to realize the transmission of data between different nodes, thereby achieving full network synchronization of user information, blacklist information and communication strategies.

[0057] In a multi-level deployment architecture, the network conditions between nodes are complex and changeable, but the communication between upper and lower level nodes is frequent and the network is often relatively stable. Therefore, for information transmission that does not require high real-time performance, a step-by-step transmission method is adopted. Blacklist information synchronization does not require high real-time performance, and data can be transmitted at regular intervals every day. Data transmission between nodes is carried out in a tree structure, and addressing between services is achieved through domain name services.

[0058] (3) The blacklist information and communication strategies of nodes at all levels are regularly synchronized to the entire network. When users at all levels of nodes use communication tools to communicate across levels and nodes, they call the user management service interface to query the users with whom the currently logged-in user can communicate. The user management service returns which users in the entire network the currently logged-in user can communicate with and which users he cannot communicate with based on the latest synchronized blacklist information and communication strategies. The communication tools then release or block local information sending and receiving. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0060] Figure 1 This is a schematic diagram of the overall structure of the user blacklist management method based on the multi-level deployment architecture provided by the present invention.

[0061] Figure 2 A schematic diagram of the blacklist and communication strategy formulation provided by the present invention.

[0062] Figure 3 A schematic diagram of the network-wide synchronization process of blacklist and communication strategy information provided by the present invention.

[0063] Figure 4 This is a schematic diagram of the information filtering process of nodes at all levels provided by the present invention. DETAILED DESCRIPTION

[0064] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0065] In order to solve the problem of controllable information sending and receiving in instant messaging under a multi-level deployment architecture and avoid unnecessary interference to the work of specific user groups, a design of user blacklist management and usage method based on a multi-level deployment architecture is proposed.

[0066] The system administrator creates a blacklist for each node according to the deployment architecture and formulates communication policy information. After the settings are completed, the blacklist and communication policy information are summarized step by step according to the deployment architecture, and a complete blacklist and communication policy information is generated at the top-level central node. The top-level node then synchronizes the summary information step by step downward to the bottom-level node. Each node filters the user information of the communication software according to the synchronized blacklist and communication policy information, releases the user information that meets the rules, and blocks unnecessary interference.

[0067] The embodiment of the present invention discloses a user blacklist management method based on a multi-level deployment architecture, which mainly formulates user blacklists and communication strategies through nodes at all levels, and then summarizes them to the central node level by level. After the central node gathers and merges, it is distributed to each using node level by level, thereby achieving the purpose of unifying the blacklist of the whole network, unifying the communication strategy, and deploying one point for the whole network.

[0068] 1) Blacklist and communication strategy formulation

[0069] Each node at each level determines the blacklist information of the node users according to their actual situation. The blacklist information is maintained by the system administrators of each node. Users who cannot communicate with them at any time are set to the blacklist, and vice versa. After the setting is completed, the blacklist users will be directly blocked by the system in the communication software and cannot communicate with them. The system retains the whitelist users who can communicate at any time.

[0070] However, in actual daily communication, we often encounter many situations, and the communication needs cannot be fully met by simply filtering the blacklist. For example, an important organization or a person at a certain level of node has the authority to communicate with any user at all levels of nodes; when an important user on the blacklist actively communicates with me, I can be allowed to reply or actively communicate with him within a certain time range; a certain node allows sending emails to blacklisted users but cannot use instant messaging tools for real-time chats, etc. The situations of nodes at all levels are different, and their own communication strategies need to be formulated separately. According to actual needs, they can be set according to the organization dimension, and all users under the same node organization can be set uniformly; they can also be set according to the user dimension, that is, for each user on the node.

[0071] 2) Blacklist and communication strategy collection

[0072] In an information system with a multi-level deployment architecture, users often need to communicate across levels and nodes. When communicating, they also need to consider the blacklist and communication strategy information of other nodes. Therefore, the blacklist and communication strategy information formulated by each node needs to be synchronized across the entire network. The blacklist and communication strategy information of nodes at all levels needs to be reported and summarized to the top-level node. Considering the complexity of the network conditions of each node and the pressure of the top-level node, the nodes at all levels are designed to report and summarize step by step, and finally form a complete blacklist and communication strategy information at the top-level node.

[0073] 3) Blacklist and communication strategy issuance

[0074] After a complete blacklist and communication policy information is formed at the top-level node, the information needs to be synchronized to nodes at other levels. Similarly, considering the complexity of the network conditions of each node and the pressure of the top-level node, the design distributes the blacklist and communication policy information to nodes at all levels from top to bottom, so that a complete blacklist and communication policy information is formed at nodes at all levels.

[0075] 4) Information filtering

[0076] The blacklist information and communication strategies of nodes at all levels are regularly synchronized to the user management service of the entire network. When users of nodes at all levels use communication tools to communicate, they call the user management service interface to query the users with whom the currently logged-in user can communicate. The user management service returns which users in the entire network the currently logged-in user can communicate with and which users he cannot communicate with based on the latest synchronized blacklist information and communication strategies. The communication tools then release or block local information sending and receiving.

[0077] The present invention is further described below with reference to the accompanying drawings and embodiments.

[0078] like Figure 1 As shown in the figure, in an information system with a multi-level deployment architecture, communication between users often relies on tool software such as instant messaging tools, emails, notifications, internal forums, etc. The communication tools integrate a common user organizational structure; user management services are used to uniformly manage information such as users, organizational structures, blacklists, and communication strategies, and communication software can query user information by providing data interfaces; in order to reduce the access pressure of user management services, special file transfer services are used to realize data transmission between different nodes, thereby realizing the full network synchronization of user information, blacklist information, and communication strategies. Therefore, in addition to deploying various communication software, each node at each level in the multi-level deployment architecture also needs to deploy user management services and file transfer services.

[0079] 1) Blacklist and communication strategy formulation

[0080] By default, users can only communicate with users outside the blacklist. By setting information filtering policies, more rules can be set to meet actual communication needs.

[0081] Administrators of nodes at all levels formulate blacklists and communication strategies in the user management service. They can set them according to the organizational dimension or the user dimension. Specifically, all users under the same organization at all levels of nodes can be set as privileged users or blacklist users at the same time according to the organizational dimension. You can also set whether each user under each organization at all levels of nodes is a privileged user and whether they are blacklisted users according to the user dimension. If they are on the blacklist, you can further set the tools that other users can use to communicate with them, and whether they are allowed to reply to their messages. The blacklist and communication strategy formulation process of nodes at all levels can be found in the detailed information. Figure 2 .

[0082] 2) Blacklist and communication strategy information are synchronized across the entire network

[0083] like Figure 3 As shown in the figure, in the multi-level deployment architecture, the network conditions between nodes are complex and changeable, but the communication between the upper and lower nodes is frequent and the network is relatively stable. Therefore, for information transmission that does not require high real-time performance, a step-by-step transmission method is adopted. Blacklist information synchronization does not require high real-time performance, and data can be transmitted at regular intervals every day. Data transmission between nodes is carried out in a tree structure, and addressing between services is achieved through domain name services. The process of synchronizing blacklist and communication strategy information across the entire network is as follows: Figure 3 As shown in the figure, it includes two steps: collecting blacklists and communication strategies and issuing and updating blacklists and communication strategies.

[0084] Specifically, based on the file transfer service, the user blacklist and communication strategy information of nodes at all levels are aggregated to the central node (blacklist and communication strategy aggregation), which specifically includes the following steps:

[0085] Step 101: The end-level node user management service generates a data file with the blacklist and communication policy information of the node every day, and uploads it to the file transfer service of the node; preferably, the scheduled upload time can be positioned at 00:00 every morning.

[0086] Step 102: The upper-level node starts to use the user management service to pull the latest uploaded data files from the file transfer services of each subordinate node from the bottom up every half an hour, stores them in the local database, summarizes the data, and merges it with the blacklist and communication policy data of this node to generate a data file, which is uploaded to the file transfer service of this node.

[0087] Step 103: The primary central node finally pulls the latest uploaded data files from the file transfer services of each subordinate secondary node, stores them in the local database to form a complete blacklist and communication policy information, generates a data file with the merged data, and uploads it to the file transfer service of this node.

[0088] The file transfer service is used to distribute the collected and merged user blacklist and communication strategy information to each node level for updating (communication strategy distribution and update), which specifically includes the following steps:

[0089] Step 201: The lower-level nodes pull the complete blacklist and communication policy data files from the upper-level nodes at intervals of half an hour from top to bottom, store them in the local database, and upload them to the file transfer service of the node at the same time;

[0090] Step 202: The last node pulls the complete blacklist and communication strategy data file from the upper node and stores it in the local database.

[0091] So far, the complete blacklist and communication policy information has been synchronized and updated to all nodes. During the data synchronization process, if there is a network interruption or service failure, an alarm log will be generated to remind the operation and maintenance personnel to repair the system in time, and continue to synchronize the latest blacklist and communication policy information in the next cycle after the system is restored.

[0092] 3) Information filtering

[0093] The blacklist information and communication strategies of nodes at all levels are regularly synchronized to the user management service of the entire network. In this step, the current node will pull the complete blacklist and communication strategy data from the upper node, such as Figure 4 As shown, in this process, each user of the current node follows the following steps:

[0094] Step 301: Using the communication software to call the user management service interface, query which users the currently logged-in user can communicate with;

[0095] Step 302: Use the user management service to determine whether the currently logged-in user is a privileged user. If so, return to the list of all users in the entire network, allUsersList, and go to step 304. If not, go to the next step.

[0096] Step 303: define and calculate set S1 as: all whitelist users; define and calculate set S2 as: users in the blacklist who can communicate with the current communication software; define and calculate set S3 as: users in the blacklist who support replies and have actively communicated with the current user within n days; return the union of S1, S2, and S3, that is, the list of users with whom the current user can communicate using the current communication software.

[0097] Step 304: The communication software receives and displays the communicable users, and then allows or blocks the sending and receiving of messages.

[0098] In the above steps, when a user logs in to use the communication software, the communication software queries and displays the list of users who can communicate by calling the user management service interface. The user management service determines which users the currently logged-in user can communicate with based on the blacklist and communication policy information.

[0099] Based on the above method, the present invention also discloses a user blacklist management system based on a multi-level deployment architecture, including:

[0100] A multi-level communication system including user organizations, wherein each level of nodes in the multi-level communication system is deployed with different types of communication software, as well as corresponding user management services and file transfer services;

[0101] The multi-level communication system uses user management services to formulate user blacklists and communication strategy information corresponding to nodes at each level;

[0102] Use file transfer services to aggregate user blacklists and communication policy information of nodes at all levels to the central node for aggregation and merging;

[0103] The file transfer service is used to distribute the collected and merged user blacklist and communication policy information to nodes at all levels for updating.

[0104] In the system, the execution steps of specific functions can refer to the description in the user blacklist management method based on the multi-level deployment architecture.

[0105] The user blacklist management method and system based on a multi-level deployment architecture proposed in the present invention mainly solve the following technical problems.

[0106] (1) Unified blacklist and communication strategy for multiple communication tools

[0107] Communication between users within an organization is often done with the help of instant messaging tools, e-mails, notifications, internal forums and other tool software. A common user organizational structure is integrated into the communication tools. The present invention proposes to use user management services to uniformly manage information such as users, organizational structures, blacklists, and communication strategies, and to enable various communication software to query user information by providing a data interface.

[0108] Generally, by setting a blacklist, users can only communicate with users outside the blacklist. By setting an information filtering policy, more rules can be set to meet actual communication needs. The present invention proposes to use user management services to uniformly set information filtering policies, which can be set according to the organizational dimension or the user dimension. After the setting is completed, it can be applied to multiple communication tools to avoid repeated settings and inconsistent policies.

[0109] (2) Multi-level deployment architecture synchronizes blacklist and communication policy information across the entire network

[0110] An information system with a multi-level deployment architecture uses user management services to provide a data interface to enable communication software to query user information. In order to reduce the access pressure of user management services, a dedicated file transfer service is used to realize data transmission between different nodes, thereby achieving full network synchronization of user information, blacklist information and communication strategies.

[0111] In a multi-level deployment architecture, the network conditions between nodes are complex and changeable, but the communication between upper and lower level nodes is frequent and the network is often relatively stable. Therefore, for information transmission that does not require high real-time performance, a step-by-step transmission method is adopted. Blacklist information synchronization does not require high real-time performance, and data can be transmitted at regular intervals every day. Data transmission between nodes is carried out in a tree structure, and addressing between services is achieved through domain name services.

[0112] (3) Network-wide control information transmission and reception

[0113] The blacklist information and filtering strategies of nodes at all levels are regularly synchronized to the entire network. When users at all levels of nodes use communication tools to communicate across levels and nodes, they call the user management service interface to query the users with whom the currently logged-in user can communicate. The user management service returns which users in the entire network the currently logged-in user can communicate with and which users he cannot communicate with based on the latest synchronized blacklist information and communication strategies. The communication tools then release or block local information sending and receiving.

[0114] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0115] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user blacklist management method based on a multi-level deployment architecture, characterized in that: The following steps are involved: Creating a multi-level communication system including user organizations, wherein each level of nodes in the multi-level communication system is deployed with different types of communication software, as well as corresponding user management services and file transfer services; Formulate user blacklists and communication strategy information corresponding to nodes at each level in a multi-level communication system based on user management services; Based on the file transfer service, the user blacklist and communication policy information of nodes at all levels are aggregated and merged to the central node step by step; Based on the file transfer service, the collected and merged user blacklist and communication policy information are distributed to nodes at all levels for updating.

2. According to claim 1, a user blacklist management method based on a multi-level deployment architecture is characterized in that: Based on the user management service, the user blacklist and communication strategy information corresponding to each level of nodes in the multi-level communication system are formulated, which specifically includes the following steps: Utilize the user management service to set each user in each level of node as a privileged user or a blacklist user, where the privileged user can have one-way communication with any other user except himself; different blacklist users set privileged communication tools or communication methods with which other users can have one-way communication, and set the corresponding reply content of the blacklist user.

3. According to claim 1, a user blacklist management method based on a multi-level deployment architecture is characterized in that: Based on the user management service, the user blacklist and communication strategy information corresponding to each level of nodes in the multi-level communication system are formulated, which specifically includes the following steps: Utilize the user management service to set all users under the same organization in each level of node as privileged users or blacklist users at the same time, where the privileged user can have one-way communication with any other user except himself; different blacklist users set privileged communication tools or communication methods with which other users can have one-way communication, and set the corresponding reply content of the blacklist user.

4. According to claim 1, a user blacklist management method based on a multi-level deployment architecture is characterized in that: Based on the file transfer service, the user blacklist and communication policy information of nodes at all levels are aggregated to the central node step by step, which specifically includes the following steps: Step 101: The user management service of the last node generates a data file of the blacklist and communication strategy information of the node every day and uploads it to the file transfer service of the node; Step 102: The upper node starts to use the user management service to pull the latest uploaded data files from the file transfer service of each subordinate node from the bottom to the top every half an hour, stores them in the local database, aggregates the data, merges them with the blacklist and communication policy data of the node, generates a new data file, and uploads it to the file transfer service of the node; Step 103: The primary central node finally pulls the latest uploaded data files from the file transfer services of each subordinate secondary node, stores them in the local database to form a complete blacklist and communication policy information, generates a data file with the merged data, and uploads it to the file transfer service of this node.

5. According to a user blacklist management method based on a multi-level deployment architecture according to claim 1, it is characterized in that: The combined user blacklist and communication policy information is distributed to nodes at all levels for updating based on the file transfer service, which specifically includes the following steps: Step 201: The lower-level nodes pull the complete blacklist and communication policy data files from the upper-level nodes at intervals of half an hour from top to bottom, store them in the local database, and upload them to the file transfer service of the node at the same time; Step 202: The last node pulls the complete blacklist and communication strategy data file from the upper node and stores it in the local database.

6. A user blacklist management method based on a multi-level deployment architecture according to claim 5, characterized in that: To pull the complete blacklist and communication policy data files from the parent node, each user of the node follows the following steps: Step 301: Using the communication software to call the user management service interface, query which users the currently logged-in user can communicate with; Step 302: Use the user management service to determine whether the currently logged-in user is a privileged user. If so, return to the list of all users in the entire network and go to step 304. If not, go to step 303. Step 303: define and calculate set S1 as: all whitelist users; Define and calculate the set S2 as: users in the blacklist who can communicate with the current communication software; Define and calculate set S3 as: users in the blacklist who support reply and have actively communicated with the current user within n days; Returns the union of set S1, set S2, and set S3, that is, returns the list of users with which the current user can communicate using the current communication software; Step 304: The communication software receives and displays the communicable users, and then allows or blocks the sending and receiving of messages.

7. A user blacklist management system based on a multi-level deployment architecture, characterized in that: include: A multi-level communication system including user organizations, wherein each level of nodes in the multi-level communication system is deployed with different types of communication software, as well as corresponding user management services and file transfer services; The multi-level communication system uses user management services to formulate user blacklists and communication strategy information corresponding to nodes at each level; Use file transfer services to aggregate user blacklists and communication policy information of nodes at all levels to the central node for aggregation and merging; The file transfer service is used to distribute the collected and merged user blacklist and communication policy information to nodes at all levels for updating.

8. The user blacklist management system based on a multi-level deployment architecture according to claim 7 is characterized in that: The file transfer service is used to aggregate the user blacklist and communication policy information of nodes at all levels to the central node for aggregation and merging, which specifically includes the following steps: Step 101: The user management service of the last node generates a data file of the blacklist and communication strategy information of the node every day and uploads it to the file transfer service of the node; Step 102: The upper node starts to use the user management service to pull the latest uploaded data files from the file transfer service of each subordinate node from the bottom to the top every half an hour, stores them in the local database, aggregates the data, merges them with the blacklist and communication policy data of the node, generates a new data file, and uploads it to the file transfer service of the node; Step 103: The primary central node finally pulls the latest uploaded data files from the file transfer services of each subordinate secondary node, stores them in the local database to form a complete blacklist and communication policy information, generates a data file with the merged data, and uploads it to the file transfer service of this node.

9. The user blacklist management system based on a multi-level deployment architecture according to claim 7, characterized in that: The file transfer service is used to distribute the collected and merged user blacklist and communication policy information to each node level for updating, which specifically includes the following steps: Step 201: The lower-level nodes pull the complete blacklist and communication policy data files from the upper-level nodes at intervals of half an hour from top to bottom, store them in the local database, and upload them to the file transfer service of the node at the same time; Step 202: The last node pulls the complete blacklist and communication strategy data file from the upper node and stores it in the local database.

10. The user blacklist management system based on a multi-level deployment architecture according to claim 7, characterized in that: To pull the complete blacklist and communication policy data files from the parent node, each user of the node follows the following steps: Step 301: Using the communication software to call the user management service interface, query which users the currently logged-in user can communicate with; Step 302: Use the user management service to determine whether the currently logged-in user is a privileged user. If so, return to the list of all users in the entire network and go to step 304. If not, go to step 303. Step 303: define and calculate set S1 as: all whitelist users; Define and calculate the set S2 as: users in the blacklist who can communicate with the current communication software; Define and calculate set S3 as: users in the blacklist who support reply and have actively communicated with the current user within n days; Returns the union of set S1, set S2, and set S3, that is, returns the list of users with which the current user can communicate using the current communication software; Step 304: The communication software receives and displays the communicable users, and then allows or blocks the sending and receiving of messages.

Images